[10:38] <Mmike> Hi, lads. When using amulet, how can I ennumerate/enlist/get/fetch all the deployed units?
[11:16] <gnuoy> jamespage, got a sec for https://code.launchpad.net/~gnuoy/charms/trusty/openstack-dashboard/1420708/+merge/249303 ?
[11:17] <jamespage> gnuoy, what does -t do?
[11:17] <gnuoy> jamespage, it creates a default pin at priority 990 using the specified release string
[11:18] <gnuoy> otherwise precise/universe has priority over precise-updates/cloud-tools/main
[11:19] <gnuoy> and python-six doesn't upgrade
[11:22] <jamespage> gnuoy, remind me what the default priority is?
[11:22] <gnuoy> jamespage, http://paste.ubuntu.com/10171980/
[11:23] <jamespage> gnuoy, hmm - don't we want the version from precise-icehouse though?
[11:23] <gnuoy> jamespage, argh, ok, I'll be back....
[11:37] <gnuoy> jamespage, mp updated
[11:38] <jamespage> gnuoy, looks ok - but I'd probably just add python-six to packages
[11:38] <jamespage> and install in one hit
[11:39] <gnuoy> I was keeping it seperate so it could be removed later since, as you say, the root cause is  a pkg dep error
[11:39] <gnuoy> but I don't feel strongly
[11:47] <gnuoy> jamespage, adding it to packages won't work
[11:47] <gnuoy> as it's filtered on installed packages
[11:48] <jamespage> gnuoy, ah yes - of course
[11:48] <jamespage> gnuoy, +1
[11:48] <gnuoy> ta
[12:26] <hazmat> jamespage: new charmhelper unitdata.py landed might be useful if you need to keep state in charms
[13:28] <lazyPower> Mmike: there's a dictionary of all units in the topolgy exposed by d.sentry.units
[13:29] <lazyPower> d being your deployment object
[13:29] <lazyPower> exit
[14:58] <jcastro> lazyPower, ok how do I find the test results for the mariadb charm?
[15:14] <jcastro> tvansteenburgh, is there a way to see charm test results for one individual charm over time?
[15:15] <tvansteenburgh> jcastro: http://reports.vapour.ws/charm-summary/meteor
[15:15] <jcastro> ah, was in the wrong section then,t hanks
[15:39] <jcastro> marcoceppi, we should probably decide what we'll deploy @ SCALE
[15:39]  * marcoceppi nods
[15:56] <whit> rick_h_, were there any conclusion wrt bundle inheritance?
[15:57] <whit> *s
[15:58] <rick_h_> whit: that what was being asked for was more bundle composition vs inheritance and there's some work with core folks to see if we can think about bundles in a way that would allow that
[15:59] <whit> rick_h_,  composition works though I would imagine better support for what deployer does now would be less churn
[15:59] <whit> but with so few users
[15:59]  * whit shrugs
[16:00] <rick_h_> whit: these were just the feedback there. What they hoped to accomplish wasn't really something inheritance could do
[16:00] <rick_h_> whit: so it was decided just going back and adding inheritance via the bundle definition wasn't going to solve it either
[20:18] <noodles775> Is the m3.small too small for the bootstrap node? Or why is the m1.small the default, but m3.small (which is the recommended transition from m1.small) not an option? http://paste.ubuntu.com/10177609/
[20:23] <jrwren> noodles775: https://bugs.launchpad.net/juju-core/+bug/1373516 ?
[20:23] <mup> Bug #1373516: Switch default instance type from m1.small to t2.small/m3.medium for EC2 provider <ec2-provider> <juju-core:Triaged> <https://launchpad.net/bugs/1373516>
[20:24] <jcastro> lazyPower, https://launchpad.net/ubuntu/vivid/+source/mariadb-5.5
[20:24] <jcastro> we have it for ppc64le
[20:24] <lazyPower> oh nice
[20:24] <lazyPower> my search foo stinks apparently
[20:24] <jcastro> so all that needs to happen is add a config option
[20:24] <jcastro> it took me a while to find it
[20:24] <lazyPower> http://packages.ubuntu.com/search?keywords=mariadb&searchon=names&suite=utopic&section=all
[20:24] <jcastro> that site doesn't show ppc64le
[20:24] <lazyPower> oh boo :(
[20:24] <noodles775> Thanks jrwren
[20:27] <blr> Is there a convention for managing pip download caches in charms? Have source tarballs in files/ so perhaps there?
[21:47] <marcoceppi> blr: you could cache them anywhere in teh charm, I don't think there's any one convention defined
[21:48] <blr> marcoceppi: yep, ended up adding a pip-cache directory under files which the deploy make target updates now. thanks
[22:02] <mwenning> stokachu, ping
[22:05] <stokachu> mwenning: pong
[22:06] <mwenning> stokachu, a customer just pinged me - he's trying to to run an openstack install using a 14.10 LDS server, 14.04 MAAS and 14.04 target machines.
[22:06] <stokachu> cool
[22:07] <mwenning> stokachu, his machines name the NIC interface as 'p1p1' - this causes an error when it tries to create juju-br0
[22:07] <mwenning> ever heard of this?
[22:07] <stokachu> yea there is another bug on gh where it was reported
[22:07] <stokachu> not sure its an installer issue though
[22:07] <mwenning> groovy, what's the bug #
[22:07] <stokachu> mwenning: https://github.com/Ubuntu-Solutions-Engineering/openstack-installer/issues/349
[22:07] <mwenning> :-)
[22:07] <stokachu> should probably create a launchpad bug against juju
[22:08] <mwenning> That was my next question...
[22:08] <stokachu> i haven't looked that far into it so i dont know who to start with first
[22:08] <stokachu> i would assume juju if its configuring the br0 network before a network device rename takes place
[22:09] <stokachu> but that poster never got back to me
[22:09] <mwenning> ok, do you want to create the bug or me?
[22:10] <stokachu> mwenning: go for it if its from a customer
[22:10] <stokachu> ill subscribe the team to it
[22:10] <stokachu> and work with juju guys to reproduce
[22:10] <mwenning> stokachu, ok.  I'm gonna get some data from him, I'll ping you when I get the bug written up
[22:11] <stokachu> mwenning: cool, get a sosreport of his system too
[22:11] <stokachu> attach to the bug
[22:11] <stokachu> mwenning: thanks
[22:13] <mwenning> ah, yes.  does that pull everything in or do you need other stuff?  for example maas wants a tar of /etc/maas/*, etc
[22:13] <stokachu> mwenning: it should pull maas data in as well
[22:13] <stokachu> it checks if its installed and acts on that
[22:13] <mwenning> stokachu, groovy, will do
[22:13] <stokachu> cool man
[22:20] <marcoceppi> mwenning stokachu I think you can outline some of the bridge stuff in juju config
[22:20]  * marcoceppi greps through go src code
[22:46] <stokachu> marcoceppi: cool i need to take a look at that
[22:46] <stokachu> marcoceppi: has something to do with udev device renaming