[00:56] <aisrael> lamont: I might be able to help
[01:53] <lamont> aisrael: I eventually figured it somewhat out
[01:54] <aisrael> lamont: ok. It sounded like you might have been running into this issue: http://askubuntu.com/questions/602527/provide-data-doesnt-send-data-when-required-keys-not-satisfied-juju-charm-usin/602629#602629
[01:55] <lamont> the big challenge is that I have a relation may or may not exist, so I cannot use required_keys for it.  If the other side does use required_keys, then when it finally does provide_data, juju decides that there is no need to run the hook, and we hate life
[01:55] <lamont> it might be that very issue
[01:55] <lamont> my workaround was to stop using required_keys on the side that actually requires the relation to work
[01:57] <lamont> and yes, your explanation there puts it spot on
[02:07] <aisrael> lamont: Excellent. Glad to hear you got it working!
[02:35] <lamont> aisrael: working is a relative term.. .I'm on to the next issues
[07:59] <gnuoy> jamespage, if you get a sec https://pastebin.canonical.com/130192/
[13:27] <jamespage> gnuoy, https://code.launchpad.net/~james-page/charms/trusty/nova-compute/lxd/+merge/257104
[13:27] <jamespage> gnuoy, hey!
[13:32] <mbruzek> arosales: ping  (I know it is early for you)
[13:35] <arosales> mbruzek, omw
[13:44] <jamespage> coreycb, ok so git branches - where are we?
[13:45] <coreycb> jamespage, I'm trying to get around a few issues where python-six and python-netaddr are installed by apt and conflicting with pip dependencies
[13:47] <coreycb> jamespage, I think the problem we're going to continue running into is a mixed bag of apt installed and pip installed packages, and where to draw the line
[13:48] <coreycb> for example, six gets force installed by c-h
[13:48] <jamespage> coreycb, ok - so we need a minimal fix for release today for the impacted charms
[13:48] <coreycb> jamespage, I might have one
[13:48] <jamespage> coreycb, and then we can review whether we use a venv or suchlike going forward
[13:48] <coreycb> yeah
[13:51] <jamespage> coreycb, the git-kilo ones just fixup git support right?
[13:51] <jamespage> for kilo sorry
[13:51] <coreycb> jamespage, let me double check them
[13:54] <coreycb> jamespage, I need to refresh those
[13:54] <jamespage> coreycb, ok lets prioritize this stuff
[13:54] <jamespage> coreycb, nova-cc first
[13:54] <jamespage> and then the kilo-git stuff so long as its not to late - we have to release today and I don't want to compromise that
[13:54] <jamespage> we can stable update a minimal fix if need be
[13:55] <coreycb> jamespage, ok, testing a change for nova-cc now
[14:28] <mwak> o/
[18:28] <moqq> can someone please confirm for me that calling `relation-set -r <some-id-relation>` for a peer relationship from within a config-changed hook should cause all peer units to get a -relation-changed event
[18:52] <marcoceppi_> moqq: it should so long as you actually change a key for your relation settings
[18:53] <moqq> yeah i just realized the realtion values are per-unit and not per-relation, explains the results i’m getting
[18:53] <moqq> thanks
[19:01] <VijayT> Hello
[19:02] <lazyPower> Hello VijayT
[19:54] <marcoceppi_> o/
[22:43] <mattrae> what's the best way to start container started by juju if the container has been shut down?
[23:05] <lazyPower> mattrae: which provider?
[23:05] <lazyPower> is this local, or a cloud host? and is the container type kvm or lxc?
[23:32] <mattrae> lazyPower: using the maas provider.. deployed the lxc container with --to lxc:1 for example. I think i have the command now though
[23:33] <mattrae> lazyPower: looks like i can do lxc-start --daemon --name foo-bar --rcfile /var/lib/lxc/containers/foo-bar/lxc.conf
[23:33] <lazyPower> mattrae: ok, i was going to suggest looking at sudo lxc-ls --fancy, and starting the container with sudo lxc-start -n <name-of-container>
[23:33] <lazyPower> with -d so you dont lose your terminal
[23:33] <lazyPower> but yeah, that works as well :)
[23:33] <mattrae> oh ok, i actually want to start the container the same way that juju starts it
[23:33] <lazyPower> the config should specify the container to auto-restart however.
[23:34] <mattrae> the reason is only because i've changed the lxc config.. and to reload the config i need to stop and start the container afaik
[23:34] <lazyPower> ah - yes.
[23:34] <lazyPower> glad you figured it out though :)
[23:34] <mattrae> yup thanks for your help :)