/srv/irclogs.ubuntu.com/2012/06/17/#juju.txt

=== amithkk is now known as amith
=== amith is now known as amithkk
hazmatcharmworld getting rebooted, due to ec2 scheduled downtime, back in a few14:35
imbrandonoh noes!! heh j/k14:46
* m_3 primus on the brain... hoodlyhoodly bass16:06
hazmatand its back16:06
m_3yup... totally screwed my system yesterday grabbing something out of a really old backup... as root :(16:09
* m_3 palms forehead16:09
imbrandonouch16:19
negronjljcastro: ping16:48
negronjlhazmat: ping16:49
negronjlm_3: do you know the maas password for the maas/openstack/juju setup ?16:49
hazmatnegronjl, pong16:53
negronjlhazmat: I'm working with the hardware setup for MaaS and was wondering if you know the password for the admin user16:54
negronjlhazmat: I have tried a few but, I'm sutck16:55
negronjls/sutck/stuck16:55
hazmatnegronjl, let me grep the src16:55
negronjlhazmat: thx16:55
hazmatnegronjl, have you done a createadmin script?16:55
hazmatnegronjl, it looks like that setups the password16:56
negronjlhazmat: no ... the setup should already have one and I don't know what will happen if I make another one16:56
hazmatnegronjl, if your using the sample data..  its admin/test16:57
negronjlhazmat ... I'll check ... brb16:57
negronjlhazmat: aha !!!  thx.16:58
hazmatnegronjl, np16:58
negronjlhazmat: do you happen to know the password for the ubuntu user on the laptop that is serving as the maas server ?17:32
hazmatnegronjl, oh.. you mean the 8box demo cluster?17:38
negronjlhazmat: I have 9 HP box cluster here ( I think 8 live and 1 spare ) and a Dell laptop that is acting as the server.17:38
hazmatnegronjl, no.. robbiew, daviey, adamg, francis would know better17:38
negronjlhazmat: Cool ... I am talking to Daviey as well.17:39
negronjlhazmat: thx for your help though :)17:39
_mup_txzookeeper/errors-with-path r46 committed by kapil.foss@gmail.com19:04
_mup_merge trunk19:04
=== almaisan-away is now known as al-maisan
=== al-maisan is now known as almaisan-away
SpamapSm_3: thanks for trying on the jjj release. You only messed one thing up. odd is "dev", even is "release"22:19
SpamapSm_3: so you should have released 0.12, and bumped to 0.1322:19
m_3SpamapS: gotcha22:34
lifelessso, is there any way to run juju locally without getting new network services (apt-cacher-ng + zookeeper) installed ?23:18
lifelessor do I need to run a kvm instance, and run juju within that ?23:18
m_3lifeless: be careful with the latter option... you can do it, but juju's lxc uses(needs) libvirt's default 192.168.122.0/24 network23:34
m_3lifeless: that works though (we run local provider juju environments _within_ ec2 instances all the time for testing)23:36
m_3don't know about passing new zk/apt-cache addresses into the local provider though... never tried.  I'd imagine it's pretty hard-coded to localhost though23:37
lifelessso, what I'd really like is to be able to shove juju into an lxc and give it a single callback to a 127.0.0.1 only service to fire up more lxc's23:42
lifelessthat would let me run multiple juju environments23:42
lifelessas it is, I'm looking at jorge's howto for juju with lxc and wondering why-bother23:43
lifeless(not why bothwe with juju, why bother with that setup; its very constrained and inflexible, and has overhead (via zk and apt-cacher-ng whether I'm using it or not)23:44
m_3lifeless: like juju local provider with a bootstrapped bootstrap node that houses zk23:46
lifelessright23:46
m_3lifeless: kvm on a non-default libvirt network would do that right now23:46
m_3lifeless: but yeah, I like your idea better... a safer sandbox for lxc.  that wouldn't add extra deps to the base machine.  maybe file a bug?23:48
m_3lifeless: it's closer to how we use the bootstrap node in other providers (ec2) too23:48
lifelesswhat lp projct23:49
lifelessjuju? juju core? juju-ng ?23:50
lifeless :P23:50
lifelessm_3: ^23:50
m_3lifeless: also beware of juju local provider's startup scripts too... https://bugs.launchpad.net/bugs/100655323:50
_mup_Bug #1006553: Juju uses 100% CPU after host reboot <juju:Triaged> < https://launchpad.net/bugs/1006553 >23:50
m_3lp:juju itself23:50
m_3your fix would help box some of those issues too23:52
lifelesshah, so thats exactly the sort of thing I was worried about happening back when the lxc provider was first discussed.23:52
* lifeless buffs his fingers on his chest23:52
m_3yup23:52
m_3:)23:52
m_3there's lots we can do to clean up the local provider23:52
lifelesssomething to be aware of23:55
lifelesssome libvirt configs bridge onto the LAN23:55
m_3right... I've got one that does23:56
lifelessI do that with my non-laptop libvirts, because that lets me access the resulting instances directly and trivially.23:56
m_3grabbing the default is... um... not ideal23:56
m_3I think the answer may be to create a dedicated one on install... there's a bug for that (also using lxcbr not virbr, but that's another bug)23:57
m_3it's incompatible enough with most of my libvirt setups that I created lp:charms/juju23:58
lifelessm_3: https://bugs.launchpad.net/juju/+bug/101443523:59
_mup_Bug #1014435: lxc local provider sandboxing could be more complete <juju:New> < https://launchpad.net/bugs/1014435 >23:59
lifelessfor your editing pleasure23:59
_mup_Bug #1014435 was filed: lxc local provider sandboxing could be more complete <juju:New> < https://launchpad.net/bugs/1014435 >23:59

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!