[14:49] <superxgl> hi all , why my web UI can not open ?
[14:49] <superxgl> i think there is no problem with my cloud environment
[14:53] <superxgl> oh..wait
[14:59] <superxgl> CLC machine can not use static ip address ?
[14:59] <superxgl> i can not access web UI now
[15:15] <TeTeT> smoser: thanks for your testimonial, much appreciated
[15:16] <smoser> sorry it took me a while to get to it. but yeah, good luck. i read through the meeting minutes from last time.
[15:16] <TeTeT> smoser: to be honest I did not prepare my wiki page at all, so it was not a big surprise to get bounced
[15:16] <smoser> right. you came close though
[15:16] <smoser> :)
[15:21] <superxgl> has anyone here had ever ran into this problem ?
[15:22] <TeTeT> superxgl: yeah, I had that too, but it was with Ubuntu 9.10. Haven't seen it since then unless the cluster or cloud controller was bugged and needed a reboot
[15:23] <zul> kim0: i just uploaded a newer version of glance so we should be kosher now (once it has been accepted)
[15:23] <TeTeT> superxgl: but I found no recipe to fix it but to restart
[15:24] <superxgl> TeTeT: oh, every time i run into this problem i have to restart ? hope it not happen again
[15:24] <superxgl> TeTeT : thank you very much . i will have a try .
[15:26] <TeTeT> superxgl: good luck
[15:28] <kim0> zul: glance ? is that different from the openstack with lxc thing ?
[15:28] <zul> kim0: yes...glance is the image proxying thing for openstack
[15:29] <kim0> zul: yeah .. not following .. what's new here ?
[15:30] <kim0> wasn't glance always packaged
[15:30] <zul> kim0: yes its been update to address some packaging bugs
[15:30] <kim0> zul: so new version of glance .. great
[15:31] <zul> kim0: yep
[15:31] <kim0> zul: woohoo :) rock n roll
[15:36] <superxgl> TeTeT: now it works :) tkx
[15:36] <TeTeT> superxgl: :)
[17:43] <koolhead17> kim0:
[17:44] <kim0> koolhead17: hey what's up
[17:45] <koolhead17> how much time we have left 4 the meeting, or is it allready over?
[17:45] <kim0> koolhead17: which one
[17:45] <TeTeT> hggdh: hi, for the automated testing of ubuntu server, where do the tests actually reside?
[17:46] <koolhead17> aah its tueday today. bad me thee weekly meeting here :)
[17:46] <hggdh> TeTeT: I am guessing you are talking about the server tests via jenkins
[17:46] <kim0> koolhead17: hehe yeah its tomorrow
[17:46] <TeTeT> hggdh: yes :) sorry for being unclear
[17:46] <koolhead17> TeTeT: supp
[17:46] <hggdh> TeTeT: heh, no problem
[17:47] <TeTeT> koolhead17: hi there
[17:47] <hggdh> TeTeT: two pieces: (1) a jenkins server (ours is currently under AWS, at http://jenkins.qa.ubuntu-uk.org/;
[17:47] <koolhead17> vmware is all across twitter today.
[17:47] <TeTeT> hggdh: yes, jamespage gave me that url
[17:48] <hggdh> TeTeT: (2) as many jenkins slaves as you can get your hands on
[17:48] <hggdh> TeTeT: the slaves are where the tests are actually run
[17:49] <hggdh> TeTeT: for ISO, it is mostly itaorna and nhanga (at home with me ;-)
[17:49] <TeTeT> hggdh: ok, I take by default the jenkins server hosts two slaves or so.
[17:49] <koolhead17> hggdh: home :)
[17:49] <hggdh> TeTeT: no, the slaves are different servers
[17:49] <hggdh> koolhead17: ain't it cool?
[17:49] <TeTeT> hggdh: http://jenkins.qa.ubuntu-uk.org/job/lucid-server-i386_default/lastCompletedBuild/testReport/test/DefaultTest/testReadWrite/? - where is testReadWrite actually defined?
[17:49] <TeTeT> hggdh: ah, you can set that up in jenkins I take
[17:51] <koolhead17> hggdh: lucky you :P
[17:51]  * koolhead17 missing his home
[17:51] <hggdh> TeTeT: these were one-time runs, pretty much; the ones we are actually running now (i.e. the ones we certainly do have the code) are for natty
[17:52] <TeTeT> hggdh: are they in a package or bazaar branch? E.g. if you want to test a modified server iso for a customer, where would I grab the tests from and see if my changes did damage?
[17:52] <TeTeT> hggdh: it's a theoretical question right now, though - I have no plans for a modified server image ;)
[17:53] <hggdh> TeTeT: they are in bzr, and in a PPA right now, let me get you the links
[17:54] <hggdh> TeTeT: https://code.launchpad.net/~ubuntu-server-iso-testing-dev/ubuntu-server-iso-testing/trunk
[17:55] <TeTeT> hggdh: bummer, lucid's bzr is too old for the branch
[17:55] <hggdh> TeTeT: sic tempora gloria mundi, lucid is too old ;-)
[17:56] <hggdh> TeTeT: but, anyway, you can grab the source from the latest packages
[17:56] <TeTeT> hggdh: I've d/l the branch from my natty system, no worries, thanks
[17:57] <hggdh> TeTeT: anyway: https://launchpad.net/~ubuntu-server-iso-testing-dev/+archive/testing
[17:58] <hggdh> TeTeT: so, what you would need: add more tests to the slave, and add the jobs on the server (and configure the slave on the server)
[17:59] <hggdh> TeTeT: theoretically, nothing prohibits you from using, say, our current jenkins server, and adding your own slave to it to run your stuff
[18:00] <hggdh> TeTeT: last point -- when you get to do it, remember that in our field not much is created, most is copied... have a look at the current jobs, and adapt from there
[18:01] <koolhead17> okey
[18:01] <TeTeT> hggdh: ok. I'm just reading the stuff in the u-s-i-t branch, but I don't really see through it - run-tests.py calls the tests themselves, and executes the stuff in templates/test_cases/*
[18:01] <hggdh> TeTeT: for example, they now cater for cleaning up the slave logs (so that old results do not get saved again and again)
[18:01] <kim0> Is #cloudfoundry an open-source paas ?! seriously
[18:02] <hggdh> TeTeT: most of the times we do an ISO install (preseeded); when the install is complete, we copy the test code in the (virtual) machine
[18:02] <koolhead17> cloud cloud cloud
[18:04] <TeTeT> hggdh: I see that the README tells me to execute it on a jenkins slave with kvm support, so the testing itself is not done in the cloud at all
[18:04] <hggdh> TeTeT: indeed -- we need to test specific features of the ISO, and cannot do that in the cloud
[18:04] <TeTeT> hggdh: do we run similar tests for the images uploaded to amazon by smoser?
[18:04] <hggdh> TeTeT: OTOH, we are moving our EC2 tests to jenkins
[18:04] <hggdh> heh
[18:05] <hggdh> TeTeT: http://jenkins.qa.ubuntu-uk.org/view/natty-ec2/
[18:06] <TeTeT> hggdh: so the tests to the instance are submitted via cloud init (yaml files) and then check stuff of the instance itself?
[18:06] <hggdh> yep
[18:07] <TeTeT> hggdh: nice, thanks for all the info, will relay it tomorrow to my colleagues :)
[18:07] <hggdh> TeTeT: you are most welcome, sir
[23:04] <SpamapS> W: Failed to fetch bzip2:/var/lib/apt/lists/partial/us-west-1.ec2.archive.ubuntu.com_ubuntu_dists_natty_main_source_Sources  Hash Sum mismatch
[23:04] <SpamapS> anybody seen that?
[23:10] <SpamapS> hmm... is it possible (likely?) that the ec2 mirrors are a bit stuck?
[23:10] <SpamapS> Archive-Update-in-Progress-ip-10-161-51-124.us-west-1.compute.internal 04-Apr-2011 04:00
[23:11] <flaccid> probably