[04:19] <ctlaugh_> If I follow instructions and do NOT specify an admin password for the keystone charm when I deploy it, how do I figure out what it is so that I can use it for authentication later?
[04:21] <ctlaugh_> beisner: I'm still looking at this Openstack deployment trying to figure out what in the world is going on.  Is there a chance that something (in the charm(s), etc) that could have changed affecting how it gets deployed?  I have a simple set of scripts (I can share if necessary) that deploys the charms, creates relations between them, and that's about it.  I used them repeatedly earlier this year with no
[04:22] <ctlaugh_> trouble at all.  Now, I can't get a Juju-deployed Openstack to work.
[08:24] <cory_fu> bloodearnest: https://github.com/niedbalski/juju-deployerizer
[08:28] <bloodearnest> cory_fu, awesome, thanks
[09:29] <lazyPower> blahdeblah: just got confirmation. You're invited to tomorrow's lesson if you're still up for it
[09:46] <mgz> cory_fu: got it, runSSHKeyImport in apiserver/keymanager/keymanager.go cn generate more error results than import keys
[09:57] <lazyPower> mgz: so we know whats causing the panic now?
[09:57] <cory_fu> mgz: It can generate more results, error or not, because there are more than one key per user.  But to make the functionality work, it has to return more results, since the keyInfo is what's used to write the valid keys as well
[09:58] <cory_fu> So I definitely should have reved the api as well.  :/
[09:59] <cory_fu> lazyPower: Yeah, it's my change like I thought at first
[09:59] <lazyPower> doh
[09:59] <lazyPower> allright, at least we know whats going on. Appreciate the attention on that bug :)
[10:00] <cory_fu> mgz: Even worse (or better, depending on your point of view), the mismatch in result count could cause it to report an incorrect key as the source of the error without panicing
[10:01] <cory_fu> The only time it will panic is if the one in error is near the end of the result list and there was at least one ID that had multiple keys
[12:22] <francokaerntna> Hello, I am using the CLI to upload a bundle, but I only get the error, that the command 'juju bundle' is not known. I have the latest version of juju (1.22.1-0) and juju-quickstart (2.0.1) installed. Can anybody tell me how to deploy a bundle through the CLI?
[12:22] <lazyPower> francokaerntna: surely  juju-quickstart bundlename.yaml should get you running if the bundle is valid
[12:23] <lazyPower> francokaerntna: its a positionial argument to juju-quickstart, and you can get detailed help from juju-quickstart -h
[12:25] <francokaerntna> lazyPower: ok, I will try that. But the docu clearly states 'juju bundle proof ..' https://jujucharms.com/docs/1.22/charms-bundles
[12:26] <lazyPower> francokaerntna: thats a completely different utility coming from the charm-tools package :)
[12:26] <lazyPower> juju-quickstart is it's own project as well, and has different nomenclature
[12:26] <lazyPower> so if you're missing juju bundle, and would like to proof it - apt-get install charm-tools
[12:29] <francokaerntna> lazyPower: thank you! Now it's working
[12:44] <lazyPower> Glad to hear it :)
[13:04] <francokaerntna> I'm trying to deploy the openstack charm on 3 maas hosts. Is it enough to edit the bundle.yaml (add 'to: "lxc:X"' where X is a number from 0 to 3) file and then run juju-quickstart?
[13:42] <lazyPower> francokaerntna: it can be you need a bare-minimum of 2 machines to deploy openstack
[13:42] <lazyPower> 1 to warehouse all the ancilliary services, and 1 to dedicate to your VM host
[13:43] <lazyPower> see http://marcoceppi.com/2014/06/deploying-openstack-with-just-two-machines/ as a jumping off point.
[14:11] <francokaerntna> lazyPower: ok. But that one is without quantum. And I tried adding it afterwards but it didn't work. Can you give me some assistance?
[15:39] <francokaerntna> anybody experience with deploying neutron into openstack with juju?
[15:41] <lazyPower> francokaerntna: i know you have a limitation on the number of machines
[15:41] <lazyPower> but we do have a bundle for this in the store: https://jujucharms.com/openstack
[15:42] <lazyPower> you should be able to derive  what needs to be done from either the README or the bundle.
[15:42] <lazyPower> blahdeblah: ping
[15:44] <francokaerntna> lazyPower: I tried to deploy the openstack-base one, but it will always try to acquire 17 machines. Do you mean I should download the configuration, change the base.yaml file (so that every service contains a 'to: lxc:X' field) and then deploy with juju-quickstart?
[15:45] <lazyPower> Thats an option
[15:48] <francokaerntna> lazyPower: sorry, I read your answer to quick. I will try to humanly parse the configs and reproduce what's written in them.
[15:49] <lazyPower> well, you can also use thebundle
[15:49] <lazyPower> adding to: lxc:# shoudl work
[15:49] <lazyPower> its no different using the bundle than deploying by hand, and arguably less error prone :)
[18:24] <jshieh> Hey, has anyone had a chance to look at the Power PPA bugs listed under:
[18:24] <jshieh> https://bugs.launchpad.net/charms/+bugs?field.tag=ppc64el
[19:28] <jcastro> jose, hey do you think you can host the hangout today? I am having some display/xorg issues today and my laptop isn't very reliable
[19:40] <jcastro> https://plus.google.com/events/c4t2adthcqk723kbd6j6otr1orc
[19:40] <jcastro> can everyone see that event?
[19:48] <marcoceppi_> yes
[20:04] <jcastro> marcoceppi_, paste the URL in here
[20:06] <marcoceppi_> https://plus.google.com/hangouts/_/hoaevent/AP36tYdOBGmgZLcV7P1GJ_IWCxHj3S0wWsTbC4UXQy5bAJ5EgrAriQ?authuser=0&hl=en
[20:07] <marcoceppi_> If you want to watch, https://plus.google.com/events/c7kaoc26rs816cpf14mrpnpuiio
[20:09] <marcoceppi_> jcastro: http://youtu.be/WWGJpRtZ2H0
[20:14] <lazyPower> To anyone following along the hangout on air and wants the release notes: https://lists.ubuntu.com/archives/juju/2015-March/005118.html
[20:40] <jcastro> https://jujucharms.com/docs/stable/reference-release-notes
[20:40] <beisner> o/ popping in and out whilst testing a ton o stuff.
[20:40] <beisner>    ++tabular lazyPower !
[20:41] <lazyPower> aww yeah
[20:41] <lazyPower> tabular  = godmode for watching your deployments
[20:41] <lazyPower> cheats++ :D
[20:41] <lazyPower> make sure you hi5 katco for landing that bit of awesomeness
[20:51] <lazyPower> https://insights.ubuntu.com/2015/04/16/expediting-local-isolation-with-docker-and-juju/ - if anyone wanted to review the charm context switching on insights
[21:15] <jw4> lazyPower: great article... thanks
[23:01] <blahdeblah> lazyPower: pong - Saw your comment on https://bugs.launchpad.net/bugs/999439; I haven't got back to it this week.  Is there a way I can force a run through the testing regime to see results without you guys having to review & approve?
[23:01] <mup> Bug #999439: Need charm for quassel-core <new-charm> <Juju Charms Collection:In Progress by paulgear> <https://launchpad.net/bugs/999439>