[02:50] <arystar> will someone help me my pc wont boot I have an amd Athlon ii x4 630
[04:30] <_mup_> Bug #1191651 was filed: Juju logs don't rotate. <juju:New> <https://launchpad.net/bugs/1191651>
[14:07] <dpb1> marcoceppi: jcastro: nice work on the discourse beta.  I'm already loving it.
[14:08] <jcastro> I dig it too
[14:08] <jcastro> there's a charm!
[14:09] <dpb1> yay!
[14:21] <jcastro> hey jamespage
[14:21] <jamespage> jcastro, hey
[14:21] <jcastro> you're on review duty this week btw
[14:22] <jamespage> jcastro, thanks for the reminder
[14:22] <jcastro> no worries, I am reasonably certain no one reads the topic
[14:23] <jcastro> https://code.launchpad.net/~patrick-hetu/charms/precise/gunicorn/python-rewrite/+merge/167088
[14:23] <jcastro> also this isn't in the queue but it should be, if you could do that one first it would be <3
[14:24] <jamespage> jcastro, won't get to it today
[14:24] <jcastro> sinzui: ^^ that branch is ready for another review but didn't make it into the queue, no idea why
[14:24] <jamespage> jcastro, doing some ceph/nova-compute benching marking stuff
[14:24] <jcastro> jamespage: yeah that's fine I just wanted it on top
[14:25] <sinzui> jcastro, I see, and It has been 2 weeks.
[14:25] <sinzui> I am reporting a bug
[14:26] <jcastro> sinzui: want to talk Queue 2.0 today?
[14:26] <sinzui> interesting, staging and m.jc.com agree, so there is something about that Mp that confuses the review queue proc.
[14:27] <sinzui> jcastro, I can in a few hours
[14:27]  * jcastro nods
[14:30] <jcastro> m_3: you've reviewed that charm before so if you want to steal it from jamespage I am sure he will not complain
[14:45] <FunnyLookinHat> Ok guys - do any of you know if there's a way to dump the requests being made with juju-core?  I _really_ need to see what the distance is between JuJu and Rackspace... they're bought in to getting things working, but they need debug information to explain the 411 Content Length errors keeping me from auth'ing
[14:45] <FunnyLookinHat> I'm not seeing anything useful in goose unfortunately... and things _seem_ to be setup correctly
[15:23] <noodles785> wedgwood_: when you've time, I made the changes you requested, let me know if there's anything else: https://code.launchpad.net/~michael.nelson/charm-helpers/add-declarative-support/+merge/168961
[15:29] <noodles785> ]
[15:35] <m_3> jcastro: ack on gunicorn
[15:57] <MarkDude> Where can I go on LP to also request the Unicorn fix?
[15:57] <MarkDude> :D
[15:58]  * MarkDude has a few questions on Juju and some of the cli functionality
[15:58] <MarkDude> Mostly in regards to getting some work with it in Fedora
[16:00]  * MarkDude has not forgotten or stopped making plans. We have an idea with my local group of trying to use Juju in combination with Kickstart ( the way to "script" with the new improved Anaconda installer
[16:01] <MarkDude> Between having kickstart make installs easier, I want to see about having it install Juju at start. After that - most likely using some cli charms to make the system close to out of ther box usable
[16:03]  * MarkDude will do a formal letter with my title and crap later, but was hoping to an idea of how much work might be needed to use cli of Juju. This is pretty much all work that will be done by Fedora folks. 
[16:04]  * MarkDude did not have  package sponsor to make the work *effective* on my side. I now have access to package folks that like the idea of making "bridges with other projects". Yay, Penguin family \o
[16:52] <MarkDude> So far most of the licenses look compatible with the legal restrictions: Jenkins, Go language, salt-minion etc
[18:34] <Campbell> Anyone had any success with the OpenStack quantum-gateway charm? I
[18:34] <Campbell> I'm having problems getting it to deploy
[18:55] <Mage_Dude> When doing a MAAS install, you need two users correct? One for MAAS admin, and then other 'users', but at least one to use JuJu? Or does the MAAS admin also require a single node to run a 'JuJu server' (not even sure what _I_ mean by that)? I'm a little unclear why the default MAAS install takes up a node and who needs to 'own' it.
[19:11] <jcastro> marcoceppi: do you have a link to the charm school video you guys did on Fri?
[19:14] <marcoceppi> jcastro: http://www.youtube.com/watch?v=nLYisPONBDc
[19:48] <jcastro> negronjl: for your next mongodb charm idea: http://www.kchodorow.com/blog/2013/03/06/databases-dragons/
[20:22] <negronjl> jcastro: interesting .. I'll look into it.
[21:23] <sigmaone> hi
[21:25] <marcoceppi> sigmaone: hello o/
[21:25] <sigmaone> Where can I buy a phone ubuntu in Sudan
[21:26] <sigmaone> ^~^
[21:26] <jcastro> hi, this channel is for Juju, which is a server technology
[21:26] <jcastro> you want #ubuntu-touch for phone stuff
[21:27] <sigmaone> ya
[21:43] <Mage_Dude> Juju doesn't really work with virtualized environments does it?
[21:43] <sarnold> o_O
[21:43] <sarnold> that's the whole point :)
[21:44] <Mage_Dude> So there's no way to trial it?
[21:44] <jcastro> I think he means a virtualization provider
[21:45] <jcastro> if you use juju .7 you can use containers to try it
[21:45] <sarnold> Mage_Dude: charms I developed for lxc on my laptop deployed fine to amazon ec2 instances; I didn't use the free micro.t1 instances at amazon because those take for every to even deploy an OS, but you could...
[21:45] <jcastro> but for example I want a vagrant provider and so on.
[21:46] <Mage_Dude> It seems that it doesn't even deploy a single node. I've tried 13.04, 12.04 and neither of them, if you follow the instructions online, actual finish provisioning the node and allow Juju to work.
[21:47] <jcastro> which instructions are you following?
[21:47] <jcastro> out of curiosity, as we currently are in-progress for a doc transition
[21:47] <Mage_Dude> https://juju.ubuntu.com/docs/getting-started.html
[21:48] <Mage_Dude> I've tried the simplest command possible, 'juju --version'. And even that doesn't run...
[21:48] <jcastro> sigh
[21:48] <jcastro> those instructions are incorrect
[21:49] <jcastro> https://juju.ubuntu.com/get-started/
[21:49] <jcastro> Mage_Dude: if you remove/purge "juju" and install juju-core
[21:49] <sarnold> jcastro: what's wrong with them? :) those were the ones I used..
[21:49] <jcastro> "juju version" should work
[21:50] <jcastro> wrong PPA
[21:51] <jcastro> thumper: please, hurry. This two Juju nightmare is punching users in the face. :-/
[21:51] <thumper> jcastro: working on it dude
[21:52] <jcastro> Mage_Dude: so basically we're in the middle of a transition between major version of juju and you're seeing the worst possible combination right now
[21:53] <Mage_Dude> jcastro: I wish I'd known but, thanks for at least working on it. It just sucks to have lost a week to fiddling with it.
[21:53] <jcastro> oh man dude, say something waaaay earlier
[21:54] <Mage_Dude> I certainly don't want to be the lmgtfy guy. (But it is funny to see every single link purple for searches related to maas/juju)
[21:54] <sarnold> hehe
[21:55] <jcastro> no, you may bother me at any time
[21:55] <jcastro> all the time to get you on your feet
[21:55] <jcastro> we can at least help you get some time back
[21:55] <jcastro> no one in this channel will ever tell you to LMGTFY
[21:55] <jcastro> we're here to help save you time, not steal it
[21:56] <jcastro> but at least getting you on juju 1.11.x will get you on stuff that is improving very quickly
[21:56] <Mage_Dude> Well, I'll at least see you at OSCON and hope to be not sucky at this by that time to really learn some tricks and stuff
[21:58] <jcastro> we certainly owe you some consolation beers.
[22:00] <Mage_Dude> Portland is a good place for that.
[22:00] <Mage_Dude> In the install it says use the juju-1.10.0 alternative, should I use 1.11.0?
[22:01] <marcoceppi> Mage_Dude: 1.11.0, the installation instructions should say 1.10 or above
[22:01]  * marcoceppi goes to update that doc
[22:02] <Mage_Dude> marcoceppi: Just the getting started part it mentions the 1.10.0 vs the 0.7
[22:03] <marcoceppi> Mage_Dude: yeah, it really should be 1.X vs 0.7, 0.7 is probably going to be the last 0.x release (old code version)
[22:03] <Mage_Dude> sudo apt-get install juju-core
[22:03] <Mage_Dude> Ha ha!
[22:03] <marcoceppi> Mage_Dude: exactly!
[22:03] <marcoceppi> ;)
[22:03] <jcastro> make sure to check the update-alternatives too
[22:05] <Mage_Dude> No alternatives for juju?
[22:06] <Mage_Dude> But juju version shows 1.11
[22:06] <jcastro> if you have both installed it'll give you the option to switch back and forth
[22:06] <jcastro> ok, you're good to go then!
[22:20] <Mage_Dude> No tools available.
[22:24] <marcoceppi> Mage_Dude: are you deploying on to ARM?
[22:24] <Mage_Dude> marcoceppi: Nope, nor to AWS.
[22:25] <marcoceppi> Mage_Dude: just (i386|amd_64) with MaaS?
[22:25] <mwhudson> Mage_Dude: could be https://bugs.launchpad.net/juju-core/+bug/1172973
[22:25] <Mage_Dude> Yeah reading through it now, but still don't understand a fix. Do I need to fake AWS keys?
[22:25] <mwhudson> i think you need actual AWS keys
[22:26] <mwhudson> (which is why the bug is critical i guess...)
[22:27] <marcoceppi> Looks like it's being actively worked on too
[22:32] <Mage_Dude> Well, I did get the command failed: access-key: expected nothing, got nothing (not sure why that's bad...) I'll try again in the morning.