[00:03] <marcoceppi> oy, magicaltrout, you're in dc and you didn't tell me! :)
[00:15] <magicaltrout> not any more marcoceppi sadly
[00:15] <magicaltrout> flew home last friday
[00:16] <magicaltrout> out there helping track down human traffickers and gun smugglers on the dark web... as one does
[00:25] <petevg> magicatrout: we both managed to snub marcoceppi.
[00:25] <petevg> Whoops.
[00:26] <petevg> ^ magicaltrout (without typos in your handle, this time)
[00:30] <magicaltrout> yeah mine involved minimal social activity, and lots of crazy shit i didn't understand
[00:30] <magicaltrout> i have since enrolled myself on a deep learning course
[00:37] <marcoceppi> cool, well if you're ever back in DC hit me up
[00:38] <magicaltrout> i shall be marcoceppi
[00:38] <magicaltrout> probably march
[00:38] <magicaltrout> i'll prod you when i find out
[00:38] <marcoceppi> magicaltrout: cool, hopefully I'll also be in town ;)
[00:40] <bdx> marcoceppi: should we be including a reference to datadog in the interfaces?
[00:41] <bdx> marcoceppi: erggg, *in the datadog state interface name
[00:41] <bdx> jeeezee - s/state/stat/
[00:42] <bdx> e.g. interface-php-fpm-stats
[00:43] <bdx> should we make it a convention to possibly have 'interface-datadog-<integration-name>' for all of the integrations?
[00:43] <bdx> since there will be alot of them
[00:44] <bdx> I feel like it will be confusing if we don't signify datadog in there somehow ... bc the names of the majority of the integrations are alto the names of juju charms
[00:51] <marcoceppi> bdx: other than datadog being a reference implementation, there's really nothing datadog specific
[00:58] <bdx> marcoceppi: nice, that makes sense.... so then these interfaces could be applicable to other use cases hopefully
[00:58] <marcoceppi> bdx: that's the plan
[00:59] <marcoceppi> bdx: I hope to do a sysdig implementation using a few of these
[00:59] <marcoceppi> as a proof of concept
[01:00] <bdx> ahh ... Sysdig looks like they are blasting native container support
[01:00] <marcoceppi> bdx: yeah, I'm interested in it for kubernetes
[01:02] <bdx> I figured as much ... from a high level ... it looks like they rolled a bunch of cli monitoring tools into one place .. cool ... no gui tho?
[01:03] <bdx> sysdig looks really cool ... I'll have to dig into it
[01:07] <bdx> I see now, sysdig doesn't log data really, it more or less gives you a realtime (and for some things historical) view into the system through a centralized ui - very useful
[01:10] <marcoceppi> bdx: yeah, you can then tap that into sysdig cloud, their saas
[01:30] <lazyPower> sysdig cloud is *intense*
[05:20] <Ankammarao> Hi i am facing browser issue with z ubuntu , getting the error like "Segmentation fault (core dumped)"
[09:21] <kjackal>  Good morinig Juju world
[10:03] <deanman> Good morning !
[10:19] <Ankammarao> kwmonroe,Hi Good morning
[10:20] <Ankammarao> kwmonroe i have some firefox browser issue, we are charming IBM products
[10:21] <Ankammarao> kwmonroe can you help me regarding the browser issue on ubuntu z machine
[11:01] <deanman> j #EliteBNC
[11:02] <magicaltrout> indeed!
[11:04] <deanman> sticky fingers
[11:29] <kjackal> magicaltrout: are you still in the EU?
[11:29] <kjackal> magicaltrout: How is the car project going :)
[11:30] <kjackal> Ankammarao: kwmonroe will be available later today. If there is anything I can help you with let me know
[11:31] <Ankammarao> kjackal Hi
[11:32] <Ankammarao> kjackal, having issue with firefox in ubuntu z terminal
[11:32] <magicaltrout> yeah kjackal I'm sat in the frozen heartlands.... mostly known as the east of england
[11:33] <Ankammarao> kjackal getting error when run firefox in the terminal "Segmentation fault (core dumped)"
[11:34] <kjackal> Ankammarao: is this the case with other browsers as well?
[11:35] <kjackal> Ankammarao: does not seem to be a juju related issue. Is it?
[11:35] <Ankammarao> kjackal we have tried with chromium browser to install but getting error
[11:36] <Ankammarao> kjackal yeah its related to ubuntu machine i guess
[11:38] <kjackal> Ankammarao: I do not know much about the firefox build on Z
[11:38] <kjackal> Ankammarao: however I would recomend you asking in #ubuntu-powerpc
[11:39] <Ankammarao> kjackal thank you
[11:39] <kjackal> Ankammarao: here is a list of IRC channels we have. You might find a better match https://wiki.ubuntu.com/IRC/ChannelList
[11:40] <Ankammarao> kjackal i will check it thanks
[11:41] <kjackal> magicaltrout: Ahhh very nice. The alternative would have been a life-threatening desert (LA) where coconuts would ruin your brand new tesla :)
[11:54] <magicaltrout> this is true kjackal
[12:19] <marcoceppi> stub: will this work?
[12:20] <marcoceppi> stub: http://paste.ubuntu.com/23588297/
[12:21] <marcoceppi> stub: mainly, can I set access to 'pg_stat_database' and is that how you would interact with the results
[12:21] <stub> marcoceppi: That looks correct
[12:21] <marcoceppi> \o/ about to test, so we'll see ;)
[12:21] <stub> marcoceppi: oh... pg_stat_database is a view inside every database, not a database itself.
[12:22] <stub> marcoceppi: but it should work... it just creates an empty database called pg_stat_database for your client to connect to.
[12:23] <stub> marcoceppi: And you probably need to pass in the database name to configure_integration (psql.maser.dbname, which in this case will be 'pg_stat_database' because that is what you asked for)
[12:25] <marcoceppi> stub: according to the setup guide: create user datadog with password '<bleh>'; grant SELECT ON pg_stat_database to datadog
[12:25] <marcoceppi> trying to replicate this using the pgsql interface, but maybe that's not possible?
[12:25] <stub> marcoceppi: You would do that after connecting to the database you want to use
[12:26] <marcoceppi> stub: well, I want all databases
[12:26] <marcoceppi> stub: the documentation has no parameter for "database"
[12:27] <stub> marcoceppi: datadog needs to connect to a database and run selects on the pg_stat_database table. In this case, it doesn't matter what dbname you use.
[12:27] <stub> marcoceppi: So...
[12:27] <stub> marcoceppi: In configure_db, I'd set_database('datadog') since that is unlikely to conflict with anything else
[12:28] <stub> marcoceppi: And ...
[12:29] <stub> marcoceppi: in configure_postgresql_integration pass 'dbname': pgsql.master.dbname
[12:30] <stub> marcoceppi: For the charm to do the grant, it needs an administrative connection. And if you give it an administrative connection, it doesn't need the grant run.
[12:30] <stub> marcoceppi: So just relate it to db-admin instead of db and you might be done
[12:33] <stub> (I should have called the set_database method set_dbname to avoid confusion. The setting on the relation is 'database', which I inherited. But in the PostgreSQL world it is usually referred to as dbname)
[12:33] <marcoceppi> no worries
[12:34] <marcoceppi> trying with db-admin
[12:34] <marcoceppi> thanks!
[12:34] <stub> np.
[12:39] <stub> marcoceppi: if you get that working, try it with a non-administrative connection. The grant should be unnecessary, at least with modern versions of PostgreSQL. I'm able to query it as an unprivileged user here
[12:40] <stub> (some views are protected, like pg_stat_activity, but pg_stat_database doesn't contain any sensitive information and seems to be public)
[12:41] <marcoceppi> stub: cool, will give it a go
[12:58] <slrocketchat> marcoceppi:  used the layer-mongodb in our chat charm - but the default 2.6.10 instance needs an `rs.initiate()` from mongo shell before being functional ... is there anyway to set that by default?
[13:02] <marcoceppi> slrocketchat: mongodb charm is missing replicaset support, it's the last thing needed
[13:03] <slrocketchat> marcoceppi:  thanks!
[13:03] <marcoceppi> slrocketchat: I've got a stub for it, but I need help completing it, happy to collab on it
[13:04] <marcoceppi> slrocketchat: I started mapping that out here https://github.com/marcoceppi/layer-mongodb/blob/master/lib/charms/layer/mongodb.py#L101
[13:05] <marcoceppi> I just never was able to get replicasets to come online in a stable fashion
[13:06] <slrocketchat> marcoceppi:  happy to take a look.  all the docker solution i see uses tricky unreliable time delay strategies.  But we only need the single instance as a primary (because Rocket.Chat acts as secondary and parses oplog) so our requirements are non-typical.
[13:07] <marcoceppi> slrocketchat: well, Juju as a third party, does a "leadership" election. I'm happy to pilot a lot of the code, I just need someone with better mongo experience than me to help me figure out the pitfalls
[13:14] <magicaltrout> multicontainer docker stuff, still makes me sad, so i'm not surprised its flaky! ;)
[13:15] <slrocketchat> marcoceppi:  we can definitely help to put the layer through the grinder .. once we complete the charm it is expected to be widely deployed in varied configuations :)
[13:16] <marcoceppi> slrocketchat: well I love rocket chat, so happy to work with you all :)
[13:16]  * magicaltrout googles rocket chat.. i clearly live in a cave
[13:17] <slrocketchat> marcoceppi:  goes both ways - we enjoy having gurus around us, solving problems that we hit in seconds with no run arounds :+1:
[14:39] <deanman> Hi, quick question, might have stumbled on this before but don't recall. Shouldn't newly created models be inheriting same configuration of default?
[14:44] <lazyPower> deanman: only if you juju set-model-defaults
[14:44] <lazyPower> deanman: othewrise juju set-model-config only applies to the currently selected model
[14:46] <deanman> lazyPower, during bootstrapping i configured http proxy and that was passed to defalt. When i created a new one it wasn't inherited. Should i manually configure every new model or is there a better way ?
[14:46] <lazyPower> deanman: i'm fairly certain the bootstrap constraints only apply at time of bootstrap in juju2. marcoceppi can you fact check my statement above? ^
[14:47] <deanman> No worries, just want to make sure whether there is a quick way to copy defaults from one model to another.
[14:47] <lazyPower> deanman: i'm pretty certain you want to set-model-defaults then
[14:49] <deanman> `juju set-model-defaults` does not exist on my 2.0.1
[14:49] <deanman> newer command addition ?
[14:51] <deanman> got it, `model-defaults`
[14:53] <deanman> no way to pass a file that has pre-configured the key-value configurations?
[14:59] <marcoceppi> deanman: you can
[15:00] <marcoceppi> deanman: you should be able to
[15:01] <lazyPower> deanman: doesn't look like it has support for feeding a file. That looks like a bug/feature-request to me.
[15:03] <deanman> ok thank you, i''ll file two feature requests then, one to be able to carry over configuration passed during bootstrap and a second to be able to load configuration to a model using a file.
[15:05] <SimonKLB> trying to co-locate two charms on the same machine but i'm getting into trouble with mis-matching python libs - would it be a good idea to try to run charms in separate virtual envs?
[15:09] <marcoceppi> SimonKLB: which charms?
[15:09] <SimonKLB> marcoceppi: my own and cs:~chris.macnaughton/influxdb-4
[15:09] <marcoceppi> SimonKLB: if they're reactive charms, you can turn on the "enable_venv" option during build time so that their libs (or at least one of their libs) is in a venv
[15:09] <SimonKLB> marcoceppi: neat! :)
[15:09] <marcoceppi> SimonKLB: https://github.com/juju-solutions/layer-basic#layer-configuration
[15:10] <SimonKLB> thanks!
[15:10] <marcoceppi> SimonKLB: cheers
[15:16] <deanman> lazyPower, got them filed as bugs but its the same process for features right?
[15:20] <lazyPower> deanman: correct
[15:20] <lazyPower> SimonKLB: did you file
[15:20] <lazyPower> https://bugs.launchpad.net/charms/+source/elasticsearch/+bug/1646904 ?
[15:20] <mup> Bug #1646904: ElasticSearch fails at peer-relation-joined <elasticsearch (Juju Charms Collection):New> <https://launchpad.net/bugs/1646904>
[15:27] <SimonKLB> lazyPower: thats not me
[15:31] <lazyPower> SimonKLB: k, i didnt think so but was just checking
[20:44] <skay_> hey any mojo person around? I'm building a spec, and the secrets phase seems to have deposited my secrets as expected, but my charm didn't get configured with the values in the secrets file
[22:21] <petevg> cory_fu: https://github.com/juju-solutions/matrix/issues/36
[22:34] <cory_fu> petevg: Replied.  But testing bundles from the charm store is no longer supported at all, and you're attempting to test the current directory as a bundle.  We should probably improve that error message
[22:36] <petevg> cory_fu: I didn't realize that we were officially dropping support. That's fine .. we just need to revise the tests to reflect.
[22:43] <magicaltrout> get with the times petevg !!!
[22:43] <petevg> magicaltrout: I'm so behind.
[22:43] <magicaltrout> me too.... =/
[22:44]  * petevg sheds a single tear
[22:44] <magicaltrout> on the plus side, I have one of my guys working on charms now, so i might actually get some stuff with tests, reviewed etc
[22:44] <magicaltrout> stranger things have happened
[22:45] <magicaltrout> although today I am writing a test suite to test our docker containers......
[22:45]  * magicaltrout also sheds a tear
[22:45] <petevg> One step forward ...
[22:46] <petevg> Though hooray for testing, regardless :-)
[22:46] <magicaltrout> lol, as long as I don't have to write... tests....
[22:46] <magicaltrout> he's working on drill though, I want to get some authentication running in it, but once its done, we'll get some tests in and it reviewed then hopefully you guys can utilising it in your big data bundles
[22:47] <magicaltrout> -ing +e
[22:47] <cory_fu> bcsaller: If the deploy task encounters a critical error, how can it signal that the test should abort?  Returning False makes it hang on the other rules
[22:51] <petevg> magicaltrout: I look forward to playing around with it :-)
[22:59] <magicaltrout> liar
[23:16] <cory_fu> petevg, bcsaller: https://github.com/juju-solutions/matrix/pull/37
[23:18] <petevg> cory_fu: code looks good to me.
[23:18] <petevg> Thank you :-)
[23:19] <petevg> Merged.
[23:19] <cory_fu> petevg: Thanks
[23:19] <petevg> np
[23:20] <petevg> cory_fu, bcsaller: I experimented with integrating the "subordinate okay" stuff more organically into the typing, but I wound up just making monstrosities.
[23:20] <cory_fu> bcsaller: I went with pre-validating the path instead of aborting more cleanly when the deploy failed, but I'm still curious how we would perform a "clean" abort if we needed to.
[23:21] <bcsaller> cory_fu: I think i have some outstanding code for that. let me see if it still works
[23:21] <cory_fu> bcsaller: That also came up when I was working on the ubuntui changes.  I was going to add a Cancel button but I couldn't figure out how to make it actually abort
[23:25] <petevg> cory_fu, bcsaller: shouldn't it be something like loop.stop(), model.disconnect(), loop.close()? (I guess you may not have access to the model to disconnect it, and the disconnect method may not work after you call loop.stop ...)
[23:40] <bdx> I see now, sysdig doesn't log data really, it more or less gives you a realtime (and for some things historical) view into the system through a centralized ui - very useful
[23:41] <bdx> aawwwweee