[00:11] <coreycb> thedac, thx I pushed swift-proxy with tests fixed up
[02:03] <thedac> coreycb: did that get pushed up? I don't see it.
[04:02] <coreycb> thedac, it's pushed up now, along with swift-storage and ceilometer-agent
[12:12] <apuimedo> jamespage: answered your comments in https://code.launchpad.net/~celebdor/charms/trusty/nova-cloud-controller/midonet/+merge/273717
[12:16] <coreycb> gnuoy`, I pushed to the swift-storage status mp again if you want to take a look
[12:17] <gnuoy`> coreycb, will do, thanks
[12:18] <coreycb> gnuoy`, swift-proxy is also ready for re-review
[12:18] <coreycb> gnuoy`, thanks
[12:19] <jamespage> gnuoy`, morning
[12:20] <jamespage> hey apuimedo - will look shortly
[12:20] <apuimedo> thanks jamespage
[12:29] <apuimedo> https://code.launchpad.net/~celebdor/charms/trusty/neutron-api/midonet/+merge/273772 as well
[12:35] <jamespage> apuimedo, erm I can seen any response on either of those two merges?
[12:35] <jamespage> can't rather
[12:38] <apuimedo> mmm
[12:38] <apuimedo> let me check
[12:39] <apuimedo> jamespage: sorry about that, forgot to press save. They should be visible now
[12:39] <jamespage> lol
[12:41] <apuimedo> I'm a launchpad noob :P
[12:55] <jrwren> is there a debugging guide for juju. Something I can follow when juju won't deploy new services or machines and the debug-log output seems to end 10 hours ago?
[14:00] <apuimedo> jamespage: I submitted the fix to charm-helpers to add the missing relation (neutron-api/next will need to be synched again)
[14:02] <jamespage> apuimedo, does MidonetContext get used elsewhere? otherwise lets avoid a ch-sync task and just drop it into the contexts for neuton-api itself
[14:03] <apuimedo> jamespage: at the moment only in neutron-api
[14:03] <jamespage> apuimedo, direct into neutron-api then is fine
[14:03] <apuimedo> jamespage: right. I thought about that too
[14:03] <apuimedo> so I'll put it there :P
[14:03] <apuimedo> thanks
[14:03] <apuimedo> jamespage: anything about the other comments I made?
[14:03] <jamespage> apuimedo, still looking
[14:03] <apuimedo> good, thanks
[14:08] <jamespage> apuimedo, responded on nova-cc - I don't think config gets passed to all templates
[14:09] <apuimedo> mmm, I tested this one like a month ago
[14:09] <jamespage> apuimedo, NovaConfigContext
[14:09] <apuimedo> but I'll test it again
[14:09] <jamespage> does the same thing that you'll need
[14:27] <apuimedo> jamespage: https://code.launchpad.net/~celebdor/charms/trusty/neutron-api/midonet/+merge/273772 should address your comments
[14:30] <jamespage> apuimedo, I'm not sure the relative pathing for key file open calls will work
[14:30] <apuimedo> I'll try it
[14:30] <jamespage> hooks run from the toplevel of the charm
[14:30] <jamespage> apuimedo, it might be better to use the charm_dir function to fully specify it
[14:31] <jamespage> thats in hookenv I think
[14:31] <apuimedo> let's see
[14:31] <apuimedo> I'll read that method up
[14:31] <jamespage> os.path.join(charm_dir(), 'files/midonet.key')
[14:31] <apuimedo> ok
[14:31] <apuimedo> I didn't know about that one ;-)
[14:32] <jamespage> apuimedo, a unit test to cover the changes in neutron_api_utils.py would help validate that one way or the other
[14:32] <jamespage> that should be pretty trivial
[14:33] <apuimedo> what should it cover? installation of the source?
[14:34] <jamespage> apuimedo, it should validate that given plugin == midonet and source being one of mem/midonet, that the right calls are made to add_source
[14:34] <jamespage> just exercise the code paths appropriately
[14:34] <jamespage> apuimedo, also my comment on the neutron.conf changes was wrong
[14:35] <jamespage> the change to the juno file disables loadbalancer and firewall for anything other that midonet
[14:35] <jamespage> I think it needs to reflect the way you did it in the kilo neutron.conf file
[14:35] <jamespage> if midonet
[14:35] <jamespage> else
[14:35] <jamespage> ....
[14:37] <apuimedo> jamespage: it should just be != "midonet"
[14:37] <apuimedo> probably a typo
[14:38] <jamespage> apuimedo, not sure but right now it will regress other plugins
[14:38] <apuimedo> yes
[14:38] <apuimedo> I'll push the fix now
[14:38] <jamespage> apuimedo, I'm assuming that
[14:38] <jamespage> +service_provider = LOADBALANCER:Midonet:midonet.neutron.services.loadbalancer.driver.MidonetLoadbalancerDriver:default
[14:38] <jamespage> 531	
[14:38] <jamespage> does not have juno context then?
[14:39] <apuimedo> I think we did not have our own load balancer then
[14:39] <apuimedo> I'll double check
[14:49] <apuimedo> jamespage: fix pushed
[15:00] <jamespage> apuimedo, I really would like to see unit tests for the code additions to this charm - the new context and the source configuration specifically
[15:00] <jamespage> apuimedo, also can i ask why the username and password is not passed over the midonet relation, and is provided by config instead?
[15:00] <jamespage> I may have already asked that at some point in the past..
[15:00] <jamespage> can't remember
[15:01] <apuimedo> jamespage: It used to be fetched from a charm called midonet-repository that you told me to remove and make the repo configuration be config and not a relation
[15:02] <jamespage> apuimedo, oh - sorry being dumb - that's not the password to access midonet services - just the repos...
[15:02] <apuimedo> midonet-api is not the owner of the repo information
[15:02] <jamespage> apuimedo, I woke up to early
[15:02] <apuimedo> yes
[15:02] <jamespage> sorry
[15:02] <apuimedo> no problem
[15:02]  * jamespage <- jetlagged
[15:03] <apuimedo> where did you fly?
[15:10] <robbiew> Seattle
[15:12] <apuimedo> nice
[15:58] <rbasak> Is there any way to set Juju's default placement? So I don't need to say --to lxc:0 all the time with the manual provider, for example?
[17:58] <jose> jcastro: ping
[17:59] <Icey> is there a way to say that the other side of this relation has to be finished before running?
[18:04] <jose> Icey: could you give a little more context?
[18:04] <Icey> working on a charm that uses the elasticsearch relation
[18:04] <Icey> the elasticsearch charm manages UFW
[18:05] <Icey> our charm is trying to create an index in Elasticsearch but sometimes fails if it's relation-changed hook runs before elasticsearch's has opened up the ports
[18:05] <jose> probably because there's no way for your charm to reach elasticsearch?
[18:05] <jose> try adding a check to see if the port is open before running
[18:09] <Icey> yeah, was just hoping to have more than an infinite loop to wait on the port
[18:10] <jose> Icey: would you mind doing a paste of your relation-changed hook? I wanna check something real quick
[18:14] <Icey> https://github.com/cholcombe973/ceph-metrics-collector/blob/master/hooks/hooks.py#L192
[18:14] <Icey> the part that's failing is in https://github.com/cholcombe973/ceph-metrics-collector/blob/master/hooks/hooks.py#L181
[18:14] <Icey>  / https://github.com/cholcombe973/ceph-metrics-collector/blob/master/hooks/hooks.py#L127
[18:32] <jose> Icey: I think what you need to do there is check if elasticsearch has already set values for the relation, don't just run. your charm is running even though ES is not ready
[18:42] <cholcombe> jose, for relation_get is the unit the ip addr of the ES unit?
[18:43] <jose> huh?
[18:43] <cholcombe> jose, i'm also working on Icey's problem
[18:43] <jose> I know, but what did you mean with your last question?
[18:43] <cholcombe> well you said grab the values that ES is setting with relation_get
[18:44] <jose> yes. elasticsearch will set relation values once the unit is ready for a relaiton
[18:44] <jose> relation*
[18:45] <cholcombe> jose, ok great
[18:45] <jose> tbh, I don't know what those values are since I don't know the interface, but they should be documented somewhere
[18:45] <jose> otherwise, checking the charm source will do
[18:45] <cholcombe> yeah i'm looking
[18:48] <cholcombe> jose, if that relation value isn't set can i return 0 and expect to have my changed hook get called again or is it a one shot deal?
[18:48] <jose> cholcombe: that's right! when the values change it will count as a relation change, meaning that the relation-changed hook will run again
[18:48] <cholcombe> jose, ok cool
[18:48] <cholcombe> i wonder why juju is calling me before the relation values are set
[18:49] <jose> because a relation-joined is followed by a relation-changed
[18:49] <cholcombe> i see
[19:36] <bdx> How's it going everyone?? Are there are any plans in the works for an official repo for layers and interfaces? ....If not, an official general location for interfaces and layers would be sweet, and would also make the development and usage workflow much nicer:-)
[19:40] <bdx> juju-solutions, core: I am getting this error http://paste.ubuntu.com/12726889/ when trying to login with launchpad to http://interfaces.juju.solutions/
[19:43] <bdx> I assume it is because I am not in a group with the correct permissions
[21:00] <asanjar> does anyone know what this error means http://paste.ubuntu.com/12727715/
[21:15] <lazypower> asanjar, o/
[21:15] <lazypower> asanjar, that looks like something went awry with the storage manager. what version of juju?
[21:23] <asanjar> hi lazypower juju --version ==> 1.24.6-vivid-ppc64el
[21:24] <lazypower> asanjar, Storage got a massive revamp in 1.25. If you're not opposed to running from the devel ppa, that error message *should* go away.
[21:26] <asanjar> okay will do