[09:24] god morning! [09:24] wait what [09:24] goooooooooooooooooooooooooooooooooooooooood morning! [09:24] better [09:24] * Chipaca fixes the script [09:32] :-) [09:47] i'm going to take a short break and walk the dog [09:47] she hasn't forgiven me doing a release yesterday instead of walking her then [09:48] and it sounds fair to me [09:54] ¡Muy buenos días a todos! [10:00] morning [10:45] hola bthomas [11:50] oh drat [11:51] * Chipaca used to have a morning [12:13] * Chipaca ⇝ runch [12:23] * Chipaca ⇝ really runch now [12:28] * Chipaca ⇝ really *really* runch now [12:28] :-) [12:31] Good morning! [12:35] Morning [12:51] I think https://github.com/canonical/operator/issues/156 is addressed by charmcraft's use of requirements.txt isn't it? [13:34] * bthomas -> lunch [14:03] hola JoseMasson [14:04] Buenas y santas facubatista! ;-P [14:55] reviews appreciated! https://github.com/canonical/charmcraft/pull/179 [14:55] PR charmcraft#179: Added function to load libraries information [16:31] facubatista: standup? [16:31] oops [17:39] * facubatista bbl [18:04] EOW from this neck of the woods, folks. See y'all on Tuesday. Have a good one! [18:34] * facubatista is back [18:46] "not like others who never come back" ;-) [18:57] Hi facubatista bthomas with justinclark we were talking about standardiring messages here: https://github.com/canonical/graylog-operator/pull/2#pullrequestreview-525374741 what do you think about it? [18:57] PR graylog-operator#2: Basic pod configuration [19:00] JoseMasson_, I'm not sure I like the idea of having "prebuilt" messages in the OF to be used when setting state; however +1 to standarize all our messages according to "good rules" (for example: they should start with uppercase and end with a dot) [19:10] facubatista, should we add documentation about this somewhere so it's clear? [19:11] mmm.. that is more "internal to us the team" than a "rule" [19:12] I see [19:13] That makes sense. Thanks [19:36] * facubatista eods [19:36] and eows! [19:37] see you all on Monday [19:48] I think I am inclined to agree with facubatista that we may standardise as a guideline since IMHO enforcing that through prebuilt messages may lead to situation which we have not anticipated, that may require a different message. [20:05] Thanks facundobatista I agree [20:20] JoseMasson_: with regard to you question on how does one ensure that writes to the MongoDB primary server, my current understanding is that this is taken care of by Graylog itself. As long as the Graylog charm sets the "replica_uri" parameter provided by the MongoDB charm, then Graylog will be able to ensure that writes go to the primary. The replica_uri contains the list of all MongoDB servers, and Graylog should be able to di [20:20] which is the primary using the MongoDB API. [20:22] * bthomas disappears into the night [20:22] Thanks bthomas!