[01:25]  * lazyPower sticks his finger in magicaltrout's ear
[06:16] <Murf> hi all, can juju talk directly to a dockerd api or via dockerd socket? I would like to use it but dont want to do it with cloud provider accounts etc, just want it to orechestrate my local existing docker environment (sort of like the way rancher connects to dockerd)
[08:37] <kjackal> Hello Juju World!
[08:37] <randlema1> ello
[12:51] <lazyPower> Murf - juju does not have any notion of talking directly to the docker socket, no
[12:51] <lazyPower> Murf - what you can do, is either use KVM and provision those, or with some manual hacking (as simple as applying a profile) you can use lxd.
[12:57] <rick_h_> Murf: it's an interesting idea, but we've always had a problem in that juju needs flexibility to work the way it does.
[12:58] <rick_h_> Murf: to respond to relations, scale out, etc. While do to that with docker you have to rebuild images with different config/properties/etc
[13:01] <magicaltrout> docker makes me want to cry currently :)
[14:27] <webmichael> anyone had a dying charm they can't destroy ? the lxc is gone. even restarted JUJU still shows life: dying
[14:27] <webmichael> destroyed the service first
[15:01] <lazyPower> webmichael - i have encountered this before yes, its typically when an extant relationship is in error state.
[15:01] <jcastro> balloons: your email says you pushed beta14 to the snap store but I'm still on beta13, snap refresh shows no changes
[15:02] <balloons> jcastro, and you are attempting to install juju?
[15:02] <balloons> snap install juju --beta --devmode?
[15:02] <jcastro> I have it installed already
[15:03] <aisrael> any known issues with MAAS 1.9 and Juju 2 beta 14?
[15:03] <aisrael> particularly with machines failing to provision?
[15:04] <jcastro> balloons: oh, iirc you didn't publish in the beta channel before right?
[15:04] <balloons> jcastro, you might have juju-nskaggs installed
[15:04] <jcastro> I do
[15:04] <balloons> and right, I pushed that one to stable
[15:04] <balloons> there's an actuall juju package now, not my namespaced version
[15:04] <jcastro> ok so what do I need to do to get on the right track?
[15:04] <balloons> snap install juju --beta --devmode
[15:04] <jcastro> do I remove juju-nskaggs?
[15:05] <balloons> it's not needed no
[15:05] <balloons> it's my own personal juju I can rev and play with
[15:05] <jcastro> ok
[15:06] <jcastro> alright so I can now just ignore the ppa version and use this modulo bugs right?
[15:08] <jcastro> balloons: ok one last thing, shouldn't /snap/bin/juju take precedence over /usr/bin/juju?
[15:08] <jcastro> I've installed it but I think I am missing something wrt the path
[15:08] <balloons> jcastro, by design it does not
[15:08] <jcastro> ok so I need to explicitly remove the old package then?
[15:08] <balloons> you can change your PATH if you want snaps first, but they are second by default
[15:09] <balloons> you can run /snap/bin/juju if you wish
[15:09] <balloons> if you don't want competition for `juju`, uninstall the debian packages
[15:09]  * jcastro nods, uninstalls
[15:10] <jcastro> I will push for the future with you
[15:11] <jcastro> balloons: hey so tldr, when can we start telling people to use it this way, aka. what's left to not need --devmode?
[15:13] <balloons> jcastro, :-). Your questions should be answered here; https://github.com/juju/juju#building-juju-as-a-snap-package
[15:13] <balloons> it's upstreamed now :-)
[15:14] <jcastro> hah, of course, bash completion
[15:14] <jcastro> because I just got bash completion
[15:15] <jcastro> the balloons giveth, the balloons taketh away.
[15:15] <jcastro> oh, that's for ubuntu-core
[15:16] <balloons> jcastro, bash completion is something that is not likely anytime soon from a snappy perspective. It's inherently insecure
[15:16] <bjf> i'm trying to "juju deploy ubuntu --to fozzie.maas" and nothing appears to be happening. i'm using juju 2.0 and maas 2.0 is my "cloud".
[15:16] <balloons> jcastro, ohh lookey there. We need a better bug, that's a wishlist
[15:16] <bjf> juju says it is deploying the charm but i can see the system is not deployed
[15:17] <bjf> also, juju debug-log is showing no output at all
[15:26] <balloons> jcastro, as far as telling people things, I'm glad you mentioned running juju on gentoo, arch, etc. There's no reason it shouldn't "just work". People can and should adopt snaps with 2.0 - that means now
[15:27] <balloons> jcastro, please push adoption; I'm happy to work on any issues you find. --devmode is acceptable for now, especially on classic systems. Nothing to grimace about imho
[15:29] <petevg> marcoceppi: ping. Specifically, I'm pinging you about wordpress, which you are listed as the maintainer for. I reviewed and approved https://code.launchpad.net/~jamesbeedy/charms/trusty/wordpress/apache2_trusty_fix/+merge/297720, but the charm still lives in the ~charmers namespace.
[15:29] <petevg> Did you have plans for moving it elsewhere?
[15:30] <petevg> Also, do we have a ticket open about the failing tests?
[15:35] <cory_fu> marcoceppi: Also, on an unrelated note, can we query the store for https://jujucharms.com/zookeeper/trusty/1 to verify that the only use of it is https://jujucharms.com/openstack-midonet-liberty/bundle/0/ ?
[15:35] <cory_fu> (actual deploys, not just relations)
[15:50] <magicaltrout> how acceptable is it reply to people trying to sell you "lists", with a simple one line reply "F*** off"
[15:51] <lazyPower> magicaltrout - *waves hand* these are not the scumbags you are looking for
[15:52] <magicaltrout> well the clog up my inbox
[15:52] <magicaltrout> i think i've had 4 today
[16:33] <jcastro> magicaltrout: heya what's the title of your talk at mesoscon?
[17:22] <magicaltrout> jcastro: http://sched.co/7n8J
[17:23] <jcastro> thanks
[17:31] <magicaltrout> thats not up to date though jcastro so it'll be on wednesday
[17:31] <magicaltrout> and pentaho london meetup @ bluefin on thursday
[17:31] <magicaltrout> busy week :P
[17:31] <jcastro> \o/
[19:12] <marcoceppi> cory_fu: we should be able to
[19:12] <marcoceppi> petevg: I'll take it over
[20:43] <cholcombe> lazyPower, did the consul agent relation get removed ?
[20:44] <lazyPower> wut?
[20:44] <mbruzek> cholcombe: I don't think we removed it
[20:45] <cholcombe> mbruzek, hmm ok.
[20:45] <cholcombe> mbruzek, trying to figure out why i can't relate vault to it
[20:46] <mbruzek> and you could relate them before?
[20:46] <cholcombe> it has a consul:consul-agent relation
[20:46] <cholcombe> yeah
[20:46] <cholcombe> but this was prob 6 months ago
[20:48] <lazyPower> cholcombe - were you using icey's consul charm at the time?
[20:48] <cholcombe> lazyPower, i don't think he has a consul charm
[20:48] <icey> lazyPower: I've never published a consul charm
[20:48] <icey> maybe I should have
[20:49] <lazyPower> "never published" - that doesn't mean you weren't working on one
[20:49]  * lazyPower raises an eyebrow
[20:50] <mbruzek> cholcombe: This was a charm written originally by hazmat
[20:50] <icey> lazyPower: I was poking at a fork of the consul one
[20:50] <mbruzek> cholcombe: https://github.com/mbruzek/consul-charm
[20:50] <lazyPower> in either case... https://github.com/ChrisMacNaughton/consul-charm/blob/master/metadata.yaml
[20:51] <lazyPower> neither have a consul-agent relation
[20:51] <mbruzek> cholcombe: I checked history of metadata.yaml I see no such consul-agent relation
[20:51] <cholcombe> :(
[20:51] <cholcombe> alright maybe i'm smoking crack.  i swear this worked before haha
[20:52] <mbruzek> https://github.com/ChrisMacNaughton/juju-interface-consul
[20:52] <mbruzek> That one has a relation
[20:52] <mbruzek> cholcombe: So you were not using the promulgated consul charm 6 months ago.
[20:52] <cholcombe> icey, tsk tsk haha
[20:53] <icey> heh it's an interface, not a charm ;-P
[21:01] <icey> bdx: could you talk to cholcombe about your work on consul + vault?
[22:46] <cholcombe> if you add juju-gui last after adding all your other applications (services) can it not find any of them?