[09:59] <hazmat> niemeyer, g'morning
[09:59] <niemeyer> hazmat: Hey!
[09:59]  * hazmat is up early to take out the afternoon for a dentist
[10:00] <hazmat> fwereade, rog greetings
[10:03] <ejat> morning hazmat
[10:05] <fwereade> mornings :)
[10:11] <rog> hazmat, fwereade, niemeyer: hey!
[10:12] <rog> i saw previous exchange but unity had crashed so i couldn't type anything
[10:12] <rog> guess what, i've installed oneiric
[10:13] <rog> (probably my fault though for trying to tweak things with ccsm)
[11:54] <hazmat> fwereade, thanks for having a  look
[11:54] <hazmat> at the txzk stuff
[12:03] <_mup_> txzookeeper/session-and-conn-fail r62 committed by kapil.foss@gmail.com
[12:03] <_mup_> save the chaos monkey via s/loose/lose ;-)
[12:15] <_mup_> txzookeeper/session-and-conn-fail r63 committed by kapil.foss@gmail.com
[12:15] <_mup_> simplify pass through property, reenable retry function test, use min() instead of condition, per review comments
[12:24] <_mup_> txzookeeper/session-and-conn-fail r64 committed by kapil.foss@gmail.com
[12:24] <_mup_> verify session event sequence per review comment
[12:40] <_mup_> juju/session-expiration r408 committed by kapil.thangavelu@canonical.com
[12:40] <_mup_> incorporate session expiration in process handling and retry client
[14:30] <_mup_> juju/local-repo-log-broken-charm r413 committed by kapil.thangavelu@canonical.com
[14:30] <_mup_> metadata parse enriches yamlerror with path info
[14:46]  * hazmat wishes lp bug search would handle comments
[15:02] <andylockran> hey guys - I'm looking to work out how best to organise a system for managing my ubuntu installations.
[15:03] <andylockran> What resource should I look at to find more about running a management system on my own private infrastructure?
[15:09] <hazmat> andylockran, that sounds like a question better suited to #ubuntu-server .. it depends on what your looking for re 'management', if you mean deployment automation orchestra is nice, if you mean automated machine management, there are a number of closed and opensource tools that might fit the bill from landscape to puppet.. juju itself is focused at a higher level of service management and orchestration
[16:10] <jcastro> SpamapS: hey don't forget to ask scale-buddy of yours about Charm School
[16:11] <jcastro> yes, charm school.
[16:13] <SpamapS> :)
[16:29] <_mup_> Bug #887644 was filed: juju/go: fixes for new error interface <juju:In Progress by rogpeppe> < https://launchpad.net/bugs/887644 >
[16:34] <noodles775> oooh, golang now in juju - I'd not realised it had started already :)
[16:35] <rog> noodles775: early stages yet!
[16:39] <robbiew> noodles775: ...and not targeted for production release in 12.04 ;-)...but should be a sweet tech preview for sure
[16:41] <robbiew> m_3: ping
[17:00]  * hazmat yawns
[17:00] <hazmat> fwereade, reply sent
[17:01]  * hazmat heads off to discover the tender mercy of a dentist
[17:16] <bloodearnest> hey folks
[17:17] <bloodearnest> using lxc provider, juju ssh is giving me an error: "PTY allocation request failed on channel 0"
[17:18] <bloodearnest> it worked fine while at UDS last week
[17:20] <jimbaker> bloodearnest, this seems to be a common problem out there, in terms of googling on that error. i haven
[17:20] <jimbaker> 't seen it myself however
[17:20] <jimbaker> eg, http://blog.asteriosk.gr/2009/02/20/pty-allocation-request-failed-on-channel-0/ discusses this issue
[17:21] <bloodearnest> jimbaker, hey, yeah googling suggests somthing incorrect with /dev/tty setup
[17:21] <bloodearnest> jimbaker: strange thing is it worked all last week fine :(
[17:21] <jimbaker> bloodearnest, precisely. i don't think it has anything to do with our lxc stuff, other than it seems like a possible resource exhaustion issue
[17:22] <bloodearnest> jimbaker: k, I'll try a reboot and see if that clears it up. Been a while anyway... :)
[17:23] <jimbaker> bloodearnest, ok, well that can fix some issues like this, but not ideal of course
[17:23] <jimbaker> but it will tell something
[17:25] <bloodearnest> jimbaker: any other route you'd suggest? I double check running processes, but nothing seemed awry
[17:25] <jimbaker> bloodearnest, from what i read on the problem, that would not be an issue
[17:31] <bloodearnest> jimbaker: lsof | grep lxc tells me that a single lxc-start has /dev/pts/[2-6] open
[17:34] <jimbaker> bloodearnest, but that's a very minimal number of ptys to have open
[17:34] <bloodearnest> jimbaker: yep
[17:43] <_mup_> juju/support-num-units r412 committed by jim.baker@canonical.com
[17:43] <_mup_> Support in juju add-units
[17:52] <bloodearnest> jimbaker: fwiw, reboot didn't help. Fresh environment, trivial charm, still no ssh :(
[17:52] <bloodearnest> jimbaker: gotta EOD, but thanks for your help!
[17:57] <rog> niemeyer: here's a first skeleton of the juju provider-independent tests interface.
[17:57] <rog> http://paste.ubuntu.com/732246/
[17:57] <jimbaker> bloodearnest, just pointing out some possibilities. easier if i had the problem myself :(
[17:57] <rog> comments welcome
[17:58] <niemeyer> rog: I don't understand what the interface is doing there
[17:58] <bloodearnest> jimbaker: sure - thanks anyway :)
[17:58] <rog> niemeyer: it's to enable a given environ provider to run a set of standard juju tests against itself
[17:59] <rog> niemeyer: as we discussed AFAIR
[17:59] <niemeyer> rog: what about testProvider(provider)?
[17:59] <rog> niemeyer: i wanted to do that, but gocheck makes it hard.
[17:59] <niemeyer> rog: It's a function..?
[18:00] <rog> because gocheck registration is global
[18:00] <rog> maybe we could fix that, but i thought i'd try to work within existing constraints first
[18:00] <niemeyer> rog: It's even easier than that..
[18:00] <niemeyer> rog: Create a suite, and simply register it for each provider
[18:01] <niemeyer> rog: Suite(&ProviderSuite{theProvider})
[18:01] <rog> not so easy. but i've no time to do explain now, gotta go.
[18:01] <niemeyer> rog: and all the tests will be run independently with the provider set
[18:01] <niemeyer> rog: Duh
[18:01] <rog> two places need to call TestingT
[18:01] <niemeyer> rog: Nope
[18:02] <rog> because we've got two totally independant sets of tests
[18:02] <niemeyer> rog: They're simply two suites
[18:02] <rog> yes, that's what i want
[18:02] <niemeyer> rog: Suite(&ProviderSuite{provider1})
[18:02] <rog> but who calls TestingT
[18:02] <niemeyer> rog: Suite(&ProviderSuite{provider2})
[18:02] <rog> ?
[18:02] <niemeyer> rog: A single independent function, like all uses of gocheck
[18:03] <rog> should jujutest call TestingT?
[18:03] <rog> i didn't think it should, but perhaps that's the way to go
[18:03] <niemeyer> rog: Not sure about who's jujutest
[18:03] <rog> jujutest is called by a provider
[18:03] <niemeyer> rog: The provider package should do it
[18:04] <niemeyer> rog: I'd have to know more about the structure to help in that case
[18:04] <rog> ok, then how does jujutest register its test suite?
[18:04] <niemeyer> rog: It's feeling more complex than it ought to be..
[18:04] <niemeyer> rog: I don't know who's jujutest
[18:05] <rog> niemeyer: jujutest is the platform-independent testing part of juju
[18:05] <niemeyer> rog: All the tests of juju are platform independent
[18:05] <rog> niemeyer: i don't want it to be part of juju itself because it's only about testing
[18:05] <niemeyer> rog: Let's talk about that when you have more time
[18:05] <rog> yeah, speak tomorrow
[18:06] <niemeyer> rog: Have a good one
[18:30] <rog> niemeyer: will do. and you!
[18:44] <pindonga> hey again, I have an lxc specific question, but maybe you can help me out anyway? I have created an lxc container, which I was able to log in successfully, however after applying updates (it was a fresh lucid install) it now no longer completes booting, and I have no idea how to find out why
[18:45] <pindonga> I managed to get some log output from it, but not very enlightening
[18:45] <pindonga> it looks like if init never spawns the getty processes
[18:46] <pindonga> and I see this:
[18:46] <pindonga> init: ureadahead-other main process (31) terminated with status 4
[18:46] <pindonga> init: console-setup main process (32) terminated with status 1
[18:46] <pindonga> init: ureadahead-other main process (37) terminated with status 4
[19:19] <SpamapS> pindonga: I'm not sure lucid is going to work... LXC was pretty new then.
[19:19] <pindonga> SpamapS, I just found out something interesting
[19:20] <pindonga> I configured network manually with a static address
[19:20] <pindonga> ssh comes up ok
[19:20] <pindonga> but the console does not
[19:20] <pindonga> which even if it's broken works for me
[19:20] <pindonga> I use the lxc container as a glorified chroot :)
[19:20] <SpamapS> pin/whois pindonga
[19:20] <SpamapS> hahahaha doh
[19:20] <pindonga> \o
[19:20]  * pindonga waves
[19:21] <SpamapS> wondered if we met last week ;)
[19:24] <SpamapS> pindonga: so are you running juju inside an LXC container, spawning more LXC containers?
[19:25] <pindonga> no, no *that* crazy :)
[19:25] <pindonga> in the short term I just tried to use juju to manage my lxc instances
[19:25] <pindonga> so I can do development in an isolated environment
[19:26] <pindonga> however, juju+lxc doesn't survive reboots yet
[19:26] <pindonga> so I moved onto just using plain lxc
[19:26] <pindonga> in the long term I want to move all of our infrastructure to juju (lxc locally and openstack for deployments)
[20:01]  * hazmat catches up
[20:04] <hazmat> bloodearnest, so completly allegorical, i had some issues with pty allocation for ssh on lxc, reboots would help.. but once it failed it would never work,  they did effectively disappear though i yanked my virtualbox install and kernel modules.. i'd be curious to look at your lsmod output
[20:10] <hazmat> jimbaker, ping
[20:12] <hazmat> pindonga, this isn't really juju related, but you can start the container with a debug log and pass cli options to /sbin/init (ie. upstart) to verbose log as well, that might help... imo, its probably just better to focus on 11.10 with eye to deploying 12.04 lts ... but if you really want it ;-)
[20:13] <pindonga> hazmat, yes , I was looking at that... thx
[20:27] <jimbaker> hazmat, hi
[20:33] <jimbaker> coffee time, biab
[20:46] <hazmat> jimbaker, priv msg
[21:31] <_mup_> juju/support-num-units r413 committed by jim.baker@canonical.com
[21:31] <_mup_> Support in juju deploy
[22:15] <hazmat> jimbaker, nice
[22:43] <SpamapS> can we make the bot also tell us when trunk is committed to?
[23:23] <_mup_> juju/support-num-units r415 committed by jim.baker@canonical.com
[23:23] <_mup_> PEP8, PyFlakes
[23:48] <_mup_> juju/support-num-units r416 committed by jim.baker@canonical.com
[23:48] <_mup_> Better help output for CLI changes
[23:53] <hazmat> SpamapS, its client side, the code is avail
[23:53] <hazmat> although its erlang as i recall, not sure where its deployed
[23:53] <andylockran> hazmat: thanks for your tip.  Ok - I'll look into that - thanks.
[23:54] <hazmat> SpamapS, https://launchpad.net/mup
[23:56] <hazmat> andylockran, np