[13:45] <rick_h_> mbruzek: lazyPower either of you tinker with the ceph charm much?
[13:46] <mbruzek> rick_h_: I am sorry I haven't used it in quite some time.
[13:46] <mbruzek> rick_h_: Why do you ask?
[13:46] <rick_h_> mbruzek: hitting an error on deploy and google-fu not finding much so I'm assuming it's a 'you're using it wrong' pebkac and not sure
[13:47] <rick_h_> ah, I did use it wrong nvm
[13:48] <mbruzek> rick_h_: The openstack guys would probably use that charm more often, jamespage or beisner
[13:48] <rick_h_> mbruzek: rgr, most of uk and such is out so you were my fallback :)
[13:49] <mbruzek> rick_h_: good luck.  I am willing to help, if you want me to take a look at error message or something
[13:49] <rick_h_> mbruzek: all good, have something to try again with so we'll see
[13:49] <mbruzek> rick_h_: OK. just let me know
[13:51]  * mbruzek loves being the fall back guy
[13:52] <mbruzek> that means someday I will be the primary guy
[13:52] <rick_h_> hah
[18:33] <lazyPower> rick_h_: sorry about the delay
[18:33] <lazyPower> looking @ the openstack move now
[18:36] <lazyPower> rick_h_: just for clarity - we need this https://code.launchpad.net/~charmers/charms/bundles/openstack/bundle - moved to openstack-base correct?
[19:14] <rick_h_> lazyPower: yes please
[19:18] <lazyPower> ack
[19:33] <lazyPower> beisner: ping
[19:33] <beisner> hi lazyPower, heading out to take the kiddos to the dentist now.  biab
[19:33] <lazyPower> ack, cheers
[19:35] <lazyPower> rick_h_: moved to https://launchpad.net/~charmers/charms/bundles/openstack-basic/bundle/ - renamed the toplevel bundle from 'openstack' to 'basic' 
[19:35] <lazyPower> rick_h_: i'm assuming we want to eradicate the existing repository?
[19:36] <rick_h_> lazyPower: so I think this will create openstack-basic-basic
[19:36] <rick_h_> since the name doesn't match the repo
[19:36] <lazyPower> ok, so rename to openstack-basic?
[19:36] <rick_h_> lazyPower: yes please
[19:36] <lazyPower> ack, 1 sec
[19:38] <lazyPower> ok, corrected and pushed.
[19:38] <rick_h_> lazyPower: ty
[19:38] <rick_h_> lazyPower: will watch to make sure it's ingested/etc. 
[19:38] <rick_h_> lazyPower: as for removing the old one, yes we should. Especially from the ~charmers space. 
[19:38] <lazyPower> ok, do we want to wait for this bundle to ingest before we nuke?
[19:38] <lazyPower> or just go ahead and nuke it
[19:39] <rick_h_> lazyPower: naw, I think it's safe to take care of now while you ahve time
[19:39] <rick_h_> it won't nuke it from the charmstore so folks can still get at it
[19:39] <rick_h_> so nuking the bzr repo won't do a lot as that's 'moved' and accessible
[19:39] <lazyPower> ok. Thanks rick_h_ - i'll send an email to the list about this update as well just to cover all the bases
[19:39] <lazyPower> cheers :)
[19:40] <rick_h_> lazyPower: rgr, please note this is due to the upcomning openstack topics page and feel free to link to it on the QA site to get get people excited and take the sting off the move
[19:40] <rick_h_> lazyPower: let me know if you need a hand with the email, or my original one, etc. Happy to help this be a happy smooth thing vs a pita hopefully
[19:42] <lazyPower> rick_h_: i see a title that doesn't make much sense to me just below the landscape ss
[19:42] <lazyPower> What to make things even easier? <- should this be Want?
[19:43] <lazyPower> on the topic page - http://qa.storefront.theblues.io:6543/openstack
[19:44] <rick_h_> lazyPower: +1 will file a bug
[19:44] <rick_h_> actually, kadams54 sorry man. Can you do the one word fix pre-release please?
[19:44] <rick_h_> ^
[19:45] <rick_h_> kadams54: I promise you can skip a few steps this time if you want since it's a trivial one word change :)
[19:46] <rick_h_> hah he ran away on us
[19:46] <lazyPower> Seems legit :D
[19:47] <rick_h_> well he was just creating the release tarball for things and will have to rebuild it and such 
[19:47] <lazyPower> http://paste.ubuntu.com/10753494/
[19:47] <lazyPower> if you want to proof the mail before i hit send
[19:48] <rick_h_> looking
[19:49] <rick_h_> "there is a url collision"
[19:49] <lazyPower> ah good call
[19:49] <rick_h_> lazyPower: but sounds good
[19:49] <kadams54> rick_h_: Back. Sure, I'll put that in.
[19:49] <rick_h_> ty for the update, and feel free to add a "if you have any questions please feel free to ping rick_h in irc or file a but at https://github.com/CanonicalLtd/jujucharms.com/issues
[19:49] <rick_h_> kadams54: ty kind sir
[19:50] <rick_h_> and ty lazyPower for the keen eye making the release look that much better...like we almost know what we're doing :)
[19:50] <lazyPower> Anytime gents :)
[19:51] <lazyPower> i sent the mail before i got the note about filing bugs - next time i'll get a poper footer in there however. 
[19:52] <rick_h_> lazyPower: all good
[19:52]  * lazyPower wanders back to the kubernetes corner to hax on an elastic container farm
[19:52] <rick_h_> wheee
[19:52] <rick_h_> lazyPower: you see the kubernetes news today around the coreos stuff?
[19:52] <lazyPower> i didn't - have a link handy?
[19:53] <rick_h_> http://www.zdnet.com/article/coreos-is-bringing-googles-kubernetes-to-the-enterprise/ is one example
[19:53] <rick_h_> http://techcrunch.com/2015/04/06/coreos-raises-12m-funding-round-led-by-google-ventures-to-bring-kubernetes-to-the-enterprise/ has the $$ in it
[19:53] <lazyPower> hmm... interesting play
[19:54] <lazyPower> "but if you'd rather focus on doing your job, CoreOS's Tectonic looks to be the better way to invest your time. "  -- welp, looks like we need to reach out to Steven about juju and what we're doing over here in our camp
[19:54] <rick_h_> :)
[19:55] <rick_h_> I was waiting for someone from around the company to send an email to folks around this one
[19:55] <rick_h_> has 'product managers required reading material' a bit all over the news
[19:55] <rick_h_> especially with 'commercial kubernetes' in there as well
[19:55] <lazyPower> What bothers me, is we're getting a good sized handfull of individual "orchestrators" - with ends of sidewalk
[19:55] <lazyPower> Ambari and Tectonic to name 2
[19:56] <lazyPower> why orchestrate silos when you can orchestrate the entire infra?