/srv/irclogs.ubuntu.com/2012/01/05/#juju.txt

SpamapShazmat: https://launchpadlibrarian.net/89092620/buildlog_ubuntu-precise-i386.juju_0.5%2Bbzr440-1juju2~precise1_FAILEDTOBUILD.txt.gz00:30
* SpamapS sometimes wonders if the buildds are just too hostile to run juju's test suite inside of00:31
* SpamapS retries it00:33
jelmerSpamapS: urgh, spurious failures suck00:52
jelmerSpamapS: that last failure looks odd - "dictionary changed size during iteration" while you're already taking a list() of the dictionary items to iterate over00:53
SpamapSjelmer: I'd pinpoint it to a precise library problem if I could get the automatic builds to work on oneiric/natty/maverick/lucid ... but the java build-dep causes us to hit the 1G limit about 90% of the time.00:55
jelmerah, bug 693524 ?00:55
_mup_Bug #693524: Daily builds of Java packages fail: "Could not reserve enough space for object heap" <recipe> <Launchpad Auto Build System:Triaged> < https://launchpad.net/bugs/693524 >00:55
SpamapSjelmer: indeed01:03
SpamapSjelmer: most frustrating about that is that because it is seemingly random.. the PPA has 4 different versions of juju in it.01:05
_mup_juju/ssh-known_hosts r467 committed by jim.baker@canonical.com06:03
_mup_Test concurrent update of known_hosts file06:03
_mup_juju/ssh-known_hosts r468 committed by jim.baker@canonical.com06:13
_mup_Cleanup of concurrent process test06:13
wrtpmornin' all08:14
koolhead17hi all09:48
koolhead17jcastro: ping10:08
nijabakoolhead17: would be surprised if jcastro wa already awake, he is east coast based10:10
koolhead17nijaba: sorry, i always get confused with the timezone slaughter :(10:10
TheMuekoolhead17: My little friend here is http://www.worldtimebuddy.com/. Here I've stored the locations of the whole team. ;)11:08
koolhead17TheMue: cool11:10
* hazmat yawns12:43
lynxmanhazmat: whenever you got your coffee with you, what was the file again where the juju client writes its zookeeper node address?14:32
hazmatlynxman, its the key 'provider-state'  in the provider storage14:33
lynxmanhazmat: hmm okay, any recommendation in how to alter it through the command line? :)14:34
hazmatlynxman, um.. there isn't one, what's the problem your trying to solve?15:04
lynxmanhazmat: just continuing on what we talked, trying to instantiate a machine, setup stunnel and a juju client through cloud-init and then connect back to zookeeper through stunnel15:05
hazmatlynxman, ic, so in this case you just want to get the zk addr?15:15
lynxmanhazmat: exactly, just tell to the new instantiated machine "your zookeper is at localhost:37173" for example15:16
lynxmanhazmat: which will be the endpoint of the stunnel connection15:16
hazmatlynxman, it really depends on the provider, typically a machine is setup to launch the agents with zk address.. ie the cli for the agent has JUJU_ZOOKEEPERS environment var set to the address, it doesn't poke directly at the provider storage15:17
lynxmanhazmat: aaah so it'd be as easy as making sure the variable is setup in the permanent environment of the machine then?15:20
hazmatlynxman, for testing sure15:20
lynxmanhazmat: k, the var is a dictionary? "1.2.3.4:1234,2.3.4.5:1234" and such?15:21
hazmatie. you could just launch the agent process and hand it another address, the place where we give the machine agent process its address is in the providers/common/launch.py via cloud-init.. it (the cli or provisioning agent) will poke at the provider-storage to figure out the extant zk servers to setup in cloud-init15:22
hazmatlynxman, its a comma separate string, of the form you just posted15:22
lynxmanhazmat: excellent, many thanks :)15:22
hazmatlynxman, np15:23
wrtphazmat: is there a team meeting today?15:30
hazmatwrtp, good question, we can do one, but i'm not sure we have quorum15:50
hazmatit looks like gustavo, william and myself are on vacation.. i'm game though15:52
wrtphazmat: ah, i wondered who was still on holiday.15:53
TheMuewrtp: I've got to miss the meeting, we've got an important parents' evening here. Our younger daughter has a class trip the next week (no, not to Budapest *lol*).16:33
wrtpTheMue: that's fine - i'd assumed it's not happening anyway16:33
* TheMue too16:34
hazmatwrtp, yeah... let's skip it.. we'll all be around next week in person16:58
wrtphazmat: k16:58
* hazmat takes dog to vet16:58
koolhead17jcastro: around?17:05
jimbakerhazmat, sounds good17:06
jcastrokoolhead17: yo17:07
koolhead17jcastro: am still waiting for mail sir!! :P17:09
jcastrosorry I've been slammed17:09
jcastroI'll do it now17:09
koolhead17jcastro: awesome.17:10
koolhead17jcastro: got it!! :P17:23
* SpamapS works through the juju MIR20:57
SpamapShazmat: have you tried running the txzookeeper test suite? I get quite a few failures on it right now21:22
hazmatSpamapS, checking21:24
hazmatSpamapS, the txzk test suite is a little odd, it requires a running zookeeperd it doesn't manage it the same way that juju does21:24
SpamapShazmat: working on running test suites on all package builds.. but 'trial txzookeeper' is looking pretty gruesome on the precise version21:24
SpamapSoh21:24
hazmatSpamapS, basically apt-get install zookeeperd21:25
SpamapSso just install zookeeperd package an it will start working?21:25
hazmatyup21:25
SpamapSok I can do that.21:25
SpamapSstill getting tons of fail21:27
SpamapSew and it creates a statically named temp dir21:27
SpamapShazmat: ugh, there's a bug in zookeeper where it listens on :::2181 and not 0.0.0.0:218121:28
hazmatSpamapS, it doesn't listen on all ifaces?21:39
hazmatSpamapS, i put in a bug to switch over the txzk tests to manage their own server21:39
_mup_juju/ssh-known_hosts r469 committed by jim.baker@canonical.com21:41
_mup_Test key update in known_hosts21:41
SpamapShazmat: no it doesn't.. bug 888643 ..21:42
_mup_Bug #888643: Zookeeper listen only to IPv6 interface <zookeeper (Ubuntu):Confirmed> < https://launchpad.net/bugs/888643 >21:42
SpamapShazmat: or rather, it does, but only all ipv6 interfaces21:42
SpamapSthere seem to be other problems21:42
SpamapSits creating /var/lib/zookeeper wrong as well21:43
_mup_juju/ssh-known_hosts r470 committed by jim.baker@canonical.com21:43
_mup_Test key update in known_hosts21:43
SpamapSadduser: Warning: The home directory `/var/lib/zookeeper' does not belong to the user you are currently creating.21:43
SpamapSahh21:44
SpamapSthey've listed the dir in the package21:44
* SpamapS fixes21:44
jimbakeroops, way too quick on choosing which command to repeat ;)21:44
SpamapSjimbaker: restoring from backups is just an opportunity to go get coffee. :)21:45
jimbakerSpamapS, ;)21:45
jimbakerrunning our unit tests fully is a perfect amount of time to make some tea, for sure21:46
SpamapSthats true21:47
_mup_juju/ssh-known_hosts r471 committed by jim.baker@canonical.com21:56
_mup_Missing file from prev commit21:56
_mup_juju/ssh-known_hosts r472 committed by jim.baker@canonical.com22:00
_mup_Sample keys use a fake user, not my account22:00
SpamapShazmat: would the txzookeeper tests be destructive to an existing zookeeper or does it use some kind of unique namespace so it won't trash whats already there?22:49
SpamapShazmat: ahh, I see now.. its extremely dangerous!22:50
SpamapShazmat: deletes the entire thing. Doh.22:51
jimbaker SpamapS, could use chroot for zk22:53
SpamapSjimbaker: I'd have to build another chroot, inside my chroot, to install zookeeperd.22:54
jimbakerSpamapS, no i mean in the connection descriptor for zk itself22:54
jimbaker(also called chroot)22:54
SpamapSjimbaker: makes *far* more sense for txzookeeper to spin up its own ephemeral zk and manage it.22:54
jimbakerSpamapS, sure. just an option22:55
SpamapSjimbaker: I don't understand zk or txzk enough to do that. :P .. just going to mark it as affecting the package so we know why we can't run the test suite on build. :)22:55
jimbakerSpamapS, no worries. but it's as simple as changing the connection string to append the desired root for the nodes to be put in22:57
hazmatSpamapS, yeah.. its dangerous, the chroot trick is just a matter of  specifying the connection string  a little different, but per the bug txzk should just setup the zk instance22:57
hazmatits already got the code todo so, just not been rewired into a an appros test layer.22:58
SpamapShazmat: yeah, medium importance.. we'll get to it at some point but its not uber critical since txzk doesn't change that much.22:58
SpamapShazmat: have you taken a close look at the quality fo the 'epsilon' python module used in txaws ?23:23
SpamapShazmat: its kind of abandonware ... the usage is so thin too.. just some date parsing stuff that I'm sure is doable by something already in main... :p23:24
SpamapSactually, wow.. ISO8601 is like, the easiest date format ever to parse.23:26
SpamapSaha.. python-dateutil .. author: Gustavo Niemeyer. :)23:30
nijabalooks like https://code.launchpad.net/~nijaba/charm-tools/peer-replay/+merge/86721 is finally ready to be reviewed. it builds and runs nicely too :)23:32
nijabaif anyone got some spare time to review..23:32
nijabaSpamapS: why do we need charms to work with lucid again?23:35
SpamapSnijaba: we don't need the charms themselves to work with lucid, but charm-tools we do.23:35
SpamapSnijaba: so we can technically just skip the charm helper test suites on anything before oneiric I suppose.23:36
nijabaSpamapS: can you elaborate?  I thought we could only run guests which are oneiric or >23:36
nijabaSpamapS: ah, juju tools, not the helpers need to run on 10.04... makes sense23:37
* SpamapS patches dateutil in for epsilon and jumps for joy when all tests pass.23:41
SpamapSseems like we need to have a txaws release at some point soon.23:47

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