[00:21] <Kiall> anyone know what the correct syntax is for cloud-init's mcollective module? Using the example gives an error about not having .iter() (sorry .. dont have the error handy right now!) (smoser maybe?)
[09:07] <kim0> Morning everyone
[09:10] <koolhead11|afk> morning,
[09:13] <TeTeT> hi kim0 , koolhead11|afk o/
[09:13] <obino> o/
[09:14] <koolhead11|afk> hi TeTeT obino  :)
[09:14] <kim0> TeTeT: obino koolhead11|afk yoohoo :)
[09:14] <TeTeT> anyone tested natty with openstack and lxc lately? I tried at release time and it wouldn't work due to cloudinit
[09:14] <kim0> aren't we one big lovely cloudy family :)
[09:14] <TeTeT> obino: hi there
[09:14] <koolhead11|afk> kim0, :D
[09:14] <TeTeT> yeah
[09:14] <obino> :D
[09:16] <obino> TeTeT: I'm not experienced with openstack and lxc, but I don't think the cloud-init problem was fixed, at least from the UDS session I followed
[09:17] <TeTeT> obino: thanks for the update
[09:43] <koolhead11|afk> kim0, can you add openstack book in the topic here :D
[09:44] <kim0> when we can add it to the ubuntu wiki first
[09:45] <koolhead11|afk> kim0, am not the right guy!! :D
[09:45] <kim0> huh ? am or am not :)
[09:45] <koolhead11|afk> kim0, i meant i am not. :D
[09:49] <koolhead11|afk> TeTeT, howdy!!
[14:27] <smoser> Kiall, what ami / release are you using ?
[14:28] <smoser> lynxman is the one who contributed... please open a bug with 'ubuntu-bug' from inside an instance.
[14:28] <Kiall> oo - not sure of the exact build .. maybe a week or so back?
[14:29] <Kiall> sure .. just have to spend more than 5 minutes at it to figure out if its the docs, or code thats wrong :)
[14:45] <smoser> Kiall, ok. so you were using natty , though?
[14:45] <Kiall> yea
[18:43] <smoser> mathiaz, was there something specific you were looking for in lucid update ami ?
[18:43] <mathiaz> smoser: hi!
[18:43] <mathiaz> smoser: not really
[18:43] <smoser> hello to you too
[18:43] <smoser> :)
[18:43] <mathiaz> smoser: I just always need to update all the packages when I start a new instance
[18:43] <smoser> yeah.
[18:44] <mathiaz> smoser: on t1.micro it takes more and more time
[18:44] <mathiaz> smoser: with the number of packages to update
[18:44] <smoser> so... if i didn't suck so much, i think the right update plan at this point is to rlelease a new ami each time a kernel moves into -updates or -security
[18:44] <smoser> which would be ~ every 3 weeks.
[18:44] <mathiaz> smoser: which means it takes more and more time to spin up new instances
[18:44] <smoser> as having to reboot into a new kernel is (i think) unreasonable
[18:44] <smoser> right.
[18:44] <mathiaz> smoser: that would be a great schedule!
[18:45] <smoser> i am accepting patches ... making the whole "release an updated ami" process push button would make it more likely to happen regularly.
[18:45] <smoser> currently it takes probably a day of my time.
[18:46] <smoser> we've gotten a good hunk of the way, with jamespage's work on automated tests from hudson
[18:53] <Kyle__> Which log files show how and why a kvm instance terminated
[19:03] <Kyle__> qqqqqqqqqqqq
[19:03] <Kyle__> WRong window, sorry