[05:32] <jose> Does Juju have an environment API I can play with? for example, a command that will list all the deployed services, but just service names (not status)
[06:23] <stub> jose: Yes. I don't know where it is documented, but I do know there are python bindings (jujuclient on pypi)
[06:24] <jose> stub: oh, awesome. I'll check later - need to rest a bit now. thanks a bunch!
[10:28] <jamespage> gnuoy, pxc seems unhappy - non-leaders are trying to migrate stuff from local storage
[10:28] <jamespage> debugging that now
[11:17] <bbaqar> Hey Liam
[13:18] <lazyPower> hmm, marcoceppi, tvansteenburgh, aisrael - when yinz get in I have a question about deployer and some bundles, i've managed to build a bundle that only works against deployer in pip - not whats in the ppa. I'm curious about the skew here and what i can do to  resolve this problem.
[13:35] <tvansteenburgh> lazyPower: the ppa is well ahead of pypi right now. probably means there's a regression in a recent commit
[13:36] <lazyPower> ok, is the head of development for deployer still in launchpad?
[13:36] <tvansteenburgh> lazyPower: wait, the juju/stable ppa, or other?
[13:36] <tvansteenburgh> lazyPower: yes
[13:36] <lazyPower> tvansteenburgh: i have both enabled on my system, aiui deployer only lives in the juju/stable ppa
[13:38] <tvansteenburgh> lazyPower: i think there are daily builds too. if you're on stable i'd expect that to match what's on pypi but it sounds like that may not be the case right now
[13:39] <lazyPower> ok, I'll dig a bit deeper and see if i can find whats going on. Thanks for the info tvansteenburgh
[13:40] <tvansteenburgh> lazyPower: np, good luck
[13:44] <lazyPower> aisrael: 1463117 hit fix-committed lastnight \o/
[13:46] <aisrael> lazyPower: excellent!
[14:55] <beisner> tvansteenburgh, do juju-deployer packages follow the juju/devel juju/proposed and juju/stable ppa flow?
[14:56] <tvansteenburgh> beisner: not sure. dpb, you know?
[14:56] <tvansteenburgh> dpb1 ^
[14:56] <beisner> tvansteenburgh, i ask because uosci uses deployer from those ppa sources, and we can exercise proposed packages ahead of landing in stable if so.
[14:56] <dpb1> beisner: no, nothing that complex
[14:57] <dpb1> beisner: we build nightlys from trunk in two ppas
[14:57] <beisner> i'd have to manually kick a job, but would be happy to do that in the interest of validating juju-deployer changes against existing implementations
[14:57] <dpb1> beisner: then every once in a while, marco or someone puts them into juju/stable, then every once in a while they are released into the distro in universe.
[14:58] <beisner> ah i see.
[14:58] <dpb1> beisner: two ppas:
[14:58] <dpb1> https://code.launchpad.net/~ahasenack/+recipe/python-jujuclient-daily
[14:58] <dpb1> https://launchpad.net/~ahasenack/+archive/ubuntu/juju-deployer-daily
[14:59] <dpb1> beisner: personally, I run from those two ppas
[15:00] <beisner> dpb1, ok thanks for the info.  and thanks for being the perpetual deployer gate  ;-)
[15:01] <dpb1> beisner: lol :)
[15:47] <jose> marcoceppi: hey, is there a way to use amulet to test actions? not documented afaics
[16:27] <lazyPower> jose: you can, but its not using amulet syntax sugar
[16:28] <lazyPower> jose: you use subprocess to call the juju action do stanza
[16:29] <jose> lazyPower: huh, good idea. I'm gonna check that and see what I can do on my end. thanks!
[19:29] <ttt_> hi
[19:48] <rick_h_> jcsackett: marcoceppi arosales lazyPower anyone else, we're bringing up new jujucharms.com env and data is loading. Data might be loading (like stats) for some time so if you see any funkiness around that (we've not switched dns yet) that's why and should settle out by tomorrow
[19:48] <lazyPower> ack, thanks rick_h_
[19:49] <jcsackett> rick_h_: think you probably meant to ping jcastro there, not me? ^
[19:49] <rick_h_> jcsackett: ah yea, sorry jcastro ^
[20:17] <arosales> rick_h_, thanks for the fyi
[20:17] <jcastro> noted
[20:27] <bilal> Hi is there any official solution for High availablity OpenStack with multi-controller on juju charm store? Can someone point me towards it. Thanks
[20:54] <Destreyf> Has anyone here used juju to deploy a full open stack system on a single node (for test purposes)
[21:03] <lazyPower> Destreyf: closest i've seen is illustrated here: http://marcoceppi.com/2014/06/deploying-openstack-with-just-two-machines/
[21:04] <lazyPower> Destreyf: but note: the article is a year old, and uses 2 machines
[21:04] <Destreyf> lazyPower: thanks for the link, i hadn't seen this one yet
[21:04] <Destreyf> basically i want to setup a cluster with 3 nodes
[21:04] <Destreyf> i know that's terrible to want
[21:04] <Destreyf> :P
[21:05] <Destreyf> but its only going to serve about 3-4VM's
[21:05] <Destreyf> so its very little usage
[21:05] <lazyPower> do you need the overhead of openstack for that?
[21:05] <lazyPower> juju supports deploy --to kvm:#
[21:05] <Destreyf> well
[21:05] <Destreyf> we need HA
[21:05] <Destreyf> currently using proxmox
[21:05] <lazyPower> 3 nodes will not give you a HA setup
[21:06] <lazyPower> 12 nodes minimum for  a proper openstack, even more for HA
[21:06] <Destreyf> even when stacking services on a single machine?
[21:06] <lazyPower> if you unplug the machine, your stacked services all tank
[21:07] <lazyPower> i'm assuming you're talking having 2 noiva-computes as "HA" and everything else (cinder, glance, keystone, et-al) running off your bootstrap node
[21:07] <Destreyf> The goal was to actually setup 3 servers, with server 1 being teh bootstrap
[21:08] <Destreyf> but also having the rest on it
[21:08] <Destreyf> and possibly telling juju to be multi-node bootstrap
[21:08] <Destreyf> although i haven't actualyl researched that
[21:08] <lazyPower> i dont think thats going to work, but i haven't tried it
[21:09] <Destreyf> :P
[21:09] <Destreyf> thanks for your input
[21:09] <Destreyf> i appreciate it
[21:09] <Destreyf> just trying to find the most effective solution for workable ha
[21:09] <Destreyf> on a 3-4 node setup
[22:01] <mbruzek> ping hazmat
[22:20] <marcoceppi> Destreyf: it's possible, I've been meaning to write a new blog post on it
[22:20] <Destreyf> marcoceppi: that's awesome to hear
[22:20] <Destreyf> i'm actually following your guide
[22:20] <Destreyf> using juju and bootstrap node
[22:20] <Destreyf> to test with single machine
[22:20] <Destreyf> any caveats to note?
[22:23] <Destreyf> marcoceppi: i bound juju-gui to port 8081 by doing juju set juju-gui port="8081"
[22:23] <Destreyf> so that's the only hiccup i could see so-far
[22:24] <marcoceppi> Destreyf: you'll want to use LXC for almost everyhting
[22:24] <marcoceppi> and you can't really co-locate ceph and nova-compute
[22:25] <Destreyf> oh?
[22:25] <marcoceppi> basically, deploy nova-compute to the one machine, then everything else as LXC containers
[22:25] <Destreyf> ceph and compute can't co-locate
[22:25] <Destreyf> so ceph inside of lxc would work though?
[22:25] <marcoceppi> Destreyf: last I checked, that may have changed. Ceph can't run in a LXC container
[22:25] <Destreyf> oh
[22:25] <Destreyf> okay
[22:25] <Destreyf> thanks
[22:26] <marcoceppi> Destreyf: if i have time this weekend I'll give it a go again and blog about it
[22:26] <marcoceppi> nuetron is also a bit sticky
[22:26] <marcoceppi> if you skip neutron, it's a lot easier
[22:26] <marcoceppi> otherwise you'll have to create a custom KVM container with two nics
[22:26] <Destreyf> Yeah i figured neutron would be a pain, but without neutron can't make it HA really can you?
[22:27] <Destreyf> also i had neutron mostly working on my last test run, but juju kept getting stuck installing OpenStack-Dashboard
[22:27] <Destreyf> once everythign else was running outside of containers
[22:27] <Destreyf> just used --to 0
[22:27] <Destreyf> on everything
[22:27] <marcoceppi> Destreyf: nova-compute is --to 0
[22:27] <marcoceppi> everyhting else is basically --to lxc:0
[22:27] <marcoceppi> that will give you containerisation of resources and prevent conflicts
[22:28] <Destreyf> nice, well letting LXC run and install teh rest of the mess right now :P
[22:28] <marcoceppi> Destreyf: you could also use VMAAS
[22:28] <Destreyf> once i have this much done, i'll image the machine and play around with getting ceph into the mix
[22:28] <marcoceppi> where you create a bunch of KVM containers on that one machine and use MAAS to manage the virtualization
[22:29] <Destreyf> marcoceppi: the end goal is to have a 3-4 node openstack setup, we're using a proxmox system right now, but we have too many performance issues to keep using it.
[22:29] <Destreyf> we might also just go with 3 proxmox and 3 ceph nodes instead
[22:29] <Destreyf> if we can't get this working
[22:30] <Destreyf> just would like to reduce the number of nodes to a more power managable number
[22:30] <Destreyf> :P
[22:30] <Destreyf> backup battery only lasts 5 minutes currently
[22:30] <Destreyf> with our 7 nodes
[22:32] <Destreyf> mysql came up
[22:32] <Destreyf> :D
[23:29] <Destreyf> marcoceppi: So my openstack-dashboard doesn't show a public ip other than the ip assigned by lxc