[00:36] <RoAk> kirkland, im thinking on removing the release codename from the config and to only obtained from the cache file where Im storing it. What do you think about this?
[00:39] <RoAk> and to load all the defaults from config file, instead of setting defaults where not set in the code
[02:08] <MTecknology> funkyHat: you still around?
[02:08] <funkyHat> MTecknology: just a bout
[02:08] <funkyHat> s/a b/ab/
[02:09] <MTecknology> funkyHat: I'm getting this now - http://dpaste.com/180694/
[02:09] <funkyHat> MTecknology: ok
[02:09] <funkyHat> That looks fine to me
[02:10] <MTecknology> funkyHat: oh..
[02:10] <MTecknology> OH!
[02:10] <funkyHat> MTecknology: is it working? ⡈)
[02:11] <MTecknology> I sent the message from the wrong addy - that's why the message isn't going through
[02:12] <funkyHat> hehe
[02:13] <MTecknology> funkyHat: DONE!
[02:15] <MTecknology> funkyHat: How can I change the mailman admin email addy?
[02:16] <funkyHat> MTecknology: can't remember, one of the helper scripts can do it
[02:17] <funkyHat> MTecknology: oh, I think it's an option in the web admin interface
[02:17] <funkyHat> in general options
[02:17] <MTecknology> funkyHat: where's the actual admin interface?
[02:18] <funkyHat> http://lists.kalliki.com/mailman/admin/test
[02:23] <MTecknology> funkyHat: oh, I thought there was one interface for more admin
[02:27] <MTecknology> funkyHat: so how can I delete/add lists?
[02:28] <MTecknology> funkyHat: I need to recreate the mailman mailing list - i muffed it up some and that's probably easiest - no need for test either
[02:32] <RoAkSoAx> kirkland, were you able to seen the messages i left you?
[02:35] <kirkland> RoAkSoAx: yeah ... so I was thinking about this more
[02:36] <kirkland> RoAkSoAx: we should talk about your graphical front end
[02:36] <kirkland> RoAkSoAx: because i think that's going to make it a *lot* easier
[02:36] <kirkland> RoAkSoAx: basically, I suggest that we change s/lucid/maverick/ in the Lucid code just before Lucid releases
[02:37] <kirkland> RoAkSoAx: i think the gtk frontend should make the selection of the ubuntu codename *really* easy
[02:38] <lifeless> kirkland: so powernap
[02:38] <RoAkSoAx> kirkland, i was planing to merge my code to obtain the codename into the PyGTK but, still, i would have to hardcode the CACHE if we keep how the configgile is loaded now
[02:38] <kirkland> lifeless: yessir
[02:38] <lifeless> kirkland: is there any reason what it doesn't isn't on by default all the time ?
[02:38] <lifeless> does it have downsides on laptops?
[02:38] <kirkland> lifeless: i run it on all 5 of my mythfrontends
[02:39] <kirkland> lifeless: arguably, it duplicates some of the behavior you get (or can control) with gnome-screensaver and the gnome power utilities
[02:40] <kirkland> lifeless: obviously we don't have those in the Ubuntu Server, so we wrote our own lightweight screensaver/powersaver daemon
[02:40] <lifeless> kirkland: hmm
[02:40] <lifeless> I think where i am coming from is this:
[02:40] <kirkland> lifeless: as it's written right now, powernap simply watches the process table for the presence or absence of a specified list of processes you want to monitor
[02:41] <lifeless>  - only using power when you have something to do
[02:41] <lifeless>  - we do things we don't want to do
[02:41] <lifeless> (such as npviewer.bin never freaking stopping)
[02:41] <kirkland> lifeless: ie, the processes that are running if your system is "doing work", and if they're not running (and haven't been running for a configurable while), then your server is deemed inactive and can powernap
[02:41] <lifeless> and pulseaudio not closign the sound card when there isn't sound to play
[02:41] <kirkland> lifeless: heh
[02:42] <kirkland> lifeless: right, right ...
[02:42]  * kirkland thought lifeless was going to come at it from a tcp port usage perspective :-)
[02:42] <kirkland> (because that's something else that's been on my mind)
[02:42] <lifeless> kirkland: sadly, my keyboard and mouse don't connect over the network
[02:42] <lifeless> be nice to get them all PAN'd up.
[02:43] <kirkland> lifeless: you should enable ssh :-)
[02:43] <lifeless> oh, it is, it is.
[02:44] <RoAkSoAx> kirkland, Anyways, I would love to resolve this so that I don'
[02:44] <RoAkSoAx> don't have to worry about it later
[02:44] <kirkland> lifeless: okay, go on ....
[02:44] <RoAkSoAx> kirkland, would you prefer me to do it both ways so you can take a look at it and give your thoughts?
[02:44] <lifeless> no thats about it
[02:45] <kirkland> lifeless: stand by for one moment
[02:45] <lifeless> just mulling on how to get less idiotic power wastage in our stack
[02:45] <kirkland> RoAkSoAx: okay, let's not dwell on calculating the latest release any longer ...
[02:45] <lifeless> like, epoll timeouts are daft.
[02:45] <kirkland> RoAkSoAx: establish your cache
[02:45] <kirkland> RoAkSoAx: and just make sure that the user can update that cache by selecting the release they want to testdrive through your GTK gui
[02:46] <kirkland> RoAkSoAx: we'll handle the distro-default in the config file just as a parameter
[02:46] <kirkland> RoAkSoAx: we'll SRU twice a year when sabdfl picks his funny adjective/animal combo
[02:46] <kirkland> RoAkSoAx: but each user will pointy/clicky the release they want to test
[02:46] <kirkland> RoAkSoAx: so the flow should look something like:
[02:47] <kirkland>  a) pick distro (Ubuntu, Debian, etc...) -- you work on Ubuntu, but make a framework so that others can submit patches to let this work with Debian, Fedora, and friends
[02:47] <kirkland>  b) pick a version (here's your codename list -- lucid, maverick, etc)
[02:48] <kirkland>  c) pick a flavor (desktop, server, netbook, mythbuntu, etc)
[02:48] <kirkland>  d) pick an arch (amd64, i386)
[02:49] <kirkland> RoAkSoAx: kind of wizard like
[02:49] <RoAkSoAx> kirkland, for each time the user logs in?
[02:50] <kirkland> RoAkSoAx: and also an Edit -> Preferences menu with the rest of the configurable things in /etc/testdriverc
[02:50] <RoAkSoAx> I mean launches the app?
[02:50] <kirkland> RoAkSoAx: only if they choose "wizard"
[02:50] <kirkland> RoAkSoAx: in the Edit -> Preferences tab the user can set their default $distro, $version, $flavor, $arch
[02:51] <RoAkSoAx> kirkland, the preferences menu is already in my mind. The wizard cool idea. though I was kinda thinking the interfae differently
[02:51] <kirkland> RoAkSoAx: okay ... what's your idea?
[02:51] <RoAkSoAx> kirkland, will draw it and send it to you :)
[02:52] <kirkland> RoAkSoAx: sounds good
[02:52] <kirkland> RoAkSoAx: let's track it in a wiki or the blueprint
[02:52] <kirkland> RoAkSoAx: keep as much of this public as possible
[02:52] <kirkland> RoAkSoAx: i suggest a TestdriveGTK wiki page
[02:53] <RoAkSoAx> kirkland, but is basically having different tabs like "Tab Ubuntu" "Tab Kubuntu" "Tab Edubuntu" "Tab Mythbuntu", and each tab separate by: "amd64" "i386"
[02:53] <kirkland> RoAkSoAx: i'd also like to look into getting Testdrive offered as a handler for ISO files, if they're liveCD ISO files
[02:54] <kirkland> RoAkSoAx: such that if you right click on an ISO in nautilus, one of the options is "Run this ISO in Testdrive"
[02:54] <RoAkSoAx> kirkland, yeah Im planing to do that as soon as It's officially announced from the GSoC and I wanna come up with the drawings of the possible interfaces before making it public
[02:54] <kirkland> RoAkSoAx: alrighty ... think about both
[02:55] <kirkland> RoAkSoAx: i think the wizard approach should be relatively straight forward
[02:56] <RoAkSoAx> kirkland, yeah wizard should be easier, but personally I would probably go directly to the main interface because I personally would hate to be using the wizard all the time
[02:56] <RoAkSoAx> would be simpler to have the interface right there after launching the APP
[02:56] <kirkland> RoAkSoAx: alrighty
[02:57] <kirkland> RoAkSoAx: for the images you already have cached, yes, i agree
[02:57] <kirkland> RoAkSoAx: perhaps the wizard is how you add a new iso to your cache the first time
[02:57] <kirkland> RoAkSoAx: once you've run it once, it's cached, then it shows up on the default canvas as a button
[02:57] <kirkland> RoAkSoAx: like a "recently used" document
[02:58] <RoAkSoAx> kirkland, or maybe the wizard can be used whenever we select the tab "Others"
[02:58] <kirkland> RoAkSoAx: okay, how about this ... let's run with the "automotive" theme of Testdrive
[02:58] <kirkland> RoAkSoAx: your default canvas is your "garage"
[02:59] <kirkland> RoAkSoAx: which shows the "vehicles" you have in your garage
[02:59] <kirkland> RoAkSoAx: it's empty, initially
[02:59] <kirkland> RoAkSoAx: when you want to "add a vehicle to your garage for testdriving", you go through the wizard
[02:59] <RoAkSoAx> kirkland, such as add: Ubuntu, other "vehicle" Kubuntu
[02:59] <kirkland> RoAkSoAx: once you've gone through the wizard once, and rsync'd an iso, it shows up as a "vehicle" in your "garage"
[02:59] <RoAkSoAx> and so on
[03:00] <kirkland> RoAkSoAx: a Vehicle is Ubuntu-Lucid-Desktop-amd64
[03:00] <kirkland> RoAkSoAx: or Ubuntu-Hardy-Server-i386
[03:00] <kirkland> RoAkSoAx: or Debian-Sarge-i386
[03:00] <kirkland> RoAkSoAx: or Kubuntu-amd64
[03:00] <kirkland> RoAkSoAx: whatever it takes to describe *one unique ISO*
[03:02] <RoAkSoAx> kirkland, ok, I'll have to think that thru, however, my plan is this: Step 1: getting testdrive modularized (including those changes I was thinking of). Step 2: Version 1.x which includes the "simple" testdrive version. Step 3: Version series 2.x: Add tabs for other distros/Xubuntu versions (kubuntu, mythuntu), and Step4: Version series 3.x could be adding support to add different distributions, and etc etc
[03:03] <RoAkSoAx> and adding wizard and stuff like that
[03:03] <RoAkSoAx> cause I don't want to jump into everything from scratch because it would be painful
[03:03] <RoAkSoAx> if we handle that with versions as Im proposing I do think would be better idea
[03:03] <kirkland> RoAkSoAx: okay
[03:04] <RoAkSoAx> is like "Adding Features"
[03:04] <RoAkSoAx> per release
[03:04] <kirkland> RoAkSoAx: okay, we'll need to set some primary/secondary/tertiary goals for the overall project, but i think something like this should work
[03:05] <kirkland> RoAkSoAx: i hope that the modularization is about 10-15% of the overall work
[03:05] <RoAkSoAx> kirkland, yeah I mean, we don't have to rush features right now.
[03:06] <RoAkSoAx> kirkland, in my opinion modularization is around 60%
[03:06] <kirkland> RoAkSoAx: hmm, then we need to discuss what you mean by modularization
[03:06] <kirkland> RoAkSoAx: i can split it into a couple of functions in a matter of a few hours
[03:06] <kirkland> RoAkSoAx: and then we can make it more object oriented
[03:07] <RoAkSoAx> kirkland, im doing it object oriented right now
[03:07] <RoAkSoAx> kirkland, lp:~andreserl/testdrive/module
[03:07] <kirkland> RoAkSoAx: but i don't see that as taking 2 of the 3 months of this project
[03:07] <RoAkSoAx> kirkland, files "testdrive", "testdrive.py"
[03:07] <RoAkSoAx> kirkland, I was thinking modularization to be done by the end of may, mid june
[03:08] <kirkland> RoAkSoAx: how long are you working on the project, overall?
[03:08] <kirkland> RoAkSoAx: first glance, testdrive.py looks about like I expect it would
[03:09] <RoAkSoAx> kirkland, well this week haven't work more than couple hours due to schoolwork, but i've worked like 10 hours a week for 2/3 weeks
[03:09] <RoAkSoAx> kirkland, im planing to work on it 20+ hours a week when the program starts
[03:09] <kirkland> RoAkSoAx: cool
[03:10] <RoAkSoAx> since right now i'm fed up with schoolwork due to i;m in the last weeks of class, so I have papers, presentations, proejcts due
[03:10] <RoAkSoAx> finals
[03:10] <RoAkSoAx> too
[03:10] <kirkland> RoAkSoAx: okay, so as by the time Maverick opens, I'd like to merge your modularized testdrive pretty much en masse
[03:10] <kirkland> RoAkSoAx: sure thing, i understand ;-)  wasn't too, too long ago I was in college :-P
[03:11] <kirkland> RoAkSoAx: basically by UDS
[03:11] <kirkland> RoAkSoAx: speaking of, are you coming to UDS?
[03:11] <RoAkSoAx> kirkland, hahah yeah I'm sick of college, and Yes I would love to have the modularization done by the UDS so that we can start working in parallel without affecting each others work.
[03:12] <kirkland> RoAkSoAx: great, yeah, so let's set a tentative goal to get the OO code merged by UDS
[03:12] <RoAkSoAx> kirkland, and as of today don't know yet since I've to apply for Visa, will send my docs by friday
[03:12] <kirkland> RoAkSoAx: gotcha
[03:12] <kirkland> RoAkSoAx: we'll plan on holding a testdrive-gtk session at UDS (which you'll just attend remotely, in the worst case)
[03:13] <RoAkSoAx> kirkland, yes I was actually thinking about that today, so I would at least want to have a simple interface for testdrive-gtk by the UDS to show
[03:13] <RoAkSoAx> on that just create the buttons and be able to launch
[03:13] <kirkland> RoAkSoAx: hopefully you and I will have hashed out the basic design before UDS, but we'll put that out for discussion at UDS
[03:14] <kirkland> RoAkSoAx: oh, that's certainly not necessary
[03:14] <kirkland> RoAkSoAx: screen shots or napkin sketches would be sufficient for UDS
[03:14] <kirkland> RoAkSoAx: focus on the modularization/OO code before UDS;  draw up your ideas on a napkin and scan it ;-)
[03:14] <RoAkSoAx> kirkland, i already have an interface that creates the buttons, but haven't added the launch functionalioty yet...  :)
[03:14] <kirkland> RoAkSoAx: alrighty
[03:14] <kirkland> RoAkSoAx: i think we're on the same page
[03:15] <kirkland> RoAkSoAx: did you already create the blueprint?
[03:15] <RoAkSoAx> kirkland, yeah, it is really simple though
[03:15] <kirkland> RoAkSoAx: url?
[03:15] <kirkland> RoAkSoAx: i'd like to capture a few of these points we just discussed in the whiteboard
[03:16] <RoAkSoAx> kirkland, https://blueprints.launchpad.net/testdrive/+spec/gsoc-testdrive-modularization
[03:16] <RoAkSoAx> kirkland, https://blueprints.launchpad.net/testdrive/+spec/gsoc-testdrive-frontend
[03:16] <kirkland> RoAkSoAx: could you rename those to server-maverick-testdrive-modularization and server-maverick-testdrive-frontend ?
[03:17] <kirkland> RoAkSoAx: actually, just the last one, server-maverick-testdrive-frontend
[03:17] <RoAkSoAx> kirkland, what would help me know is if you could take a look to my modularization code so far, and give me your thoughts about it, to see if I'm going in the right path since, to be honest, is been a while since my last OO programming project
[03:17] <kirkland> RoAkSoAx: we shouldn't need a UDS session on the modularization
[03:17] <RoAkSoAx> kirkland, server-maverick or desktop-maverick?
[03:19] <kirkland> RoAkSoAx: make it server-maverick for now ... it might get switched to the desktop team, but i'm on the server team
[03:20] <kirkland> RoAkSoAx: and i'm reporting to my manager our GSoC effort
[03:21] <kirkland> RoAkSoAx: as for your OO, like i said, first glance looks okay;  i haven't run it yet
[03:21] <kirkland> RoAkSoAx: i'm not a python OO expert either, so it might help to put it out for some peer review at some point
[03:21] <kirkland> RoAkSoAx: heck, lifeless might even give it a look over at some point :-)
[03:25] <RoAkSoAx> kirkland, haha ok cool. Anyways, just send you an image to your @ubuntu email with my idea of interface
[03:27] <kirkland> RoAkSoAx: thanks
[03:27] <kirkland> lifeless: alrighty ... so where were we ....  yeah, so powernap ....
[03:28] <kirkland> lifeless: i'm hoping for a UDS session with AmitK
[03:29] <kirkland> lifeless: i'd like to teach powernap how to "do" and "undo" a configurable set of power optimizations when something "happens" or "doesn't happen" as the case may be
[03:29] <funkyHat> MTecknology: rmlist
[03:29] <RoAkSoAx> kirkland, btw... registered the blueprint so i guess i'll have to wait for it to be approved. I'll take notes of todays conversation and put them in the whiteboard of the blueprints I already created
[03:29] <MTecknology> funkyHat: thanks for all of your help :D - This thing is pretty awesome :)
[03:29] <kirkland> RoAkSoAx: i just updated https://blueprints.edge.launchpad.net/testdrive/+spec/gsoc-testdrive-modularization
[03:29] <funkyHat> MTecknology: and newlist or http://lists.kalliki.com/mailman/create
[03:29] <kirkland> RoAkSoAx: added a couple of workitems, and took a note
[03:30] <funkyHat> MTecknology: no problem ⡈)
[03:30] <RoAkSoAx> kirkland, awesome. will do
[03:30] <kirkland> RoAkSoAx: https://blueprints.edge.launchpad.net/testdrive/+spec/server-maverick-testdrive-frontend-gsoc
[03:30] <kirkland> RoAkSoAx: i renamed it for you
[03:31] <RoAkSoAx> kirkland, shouldn't that be registered in Ubuntu for the UDS?
[03:34] <kirkland> RoAkSoAx: i just proposed for the sprint
[03:34] <kirkland> RoAkSoAx: we should try to get one or two of the Design/User-Experience team in that session!
[03:35] <RoAkSoAx> kirkland, Ok will do. I';ll try to draw a better sketch and try to ping someone there eto see what they think
[03:45] <kirkland> RoAkSoAx: thanks
[03:52] <RoAkSoAx> kirkland, btw.. if you plan to run the modularized code you need to also copy testdriverc into /etc since I've changed it to be compatible with config parser
[04:07] <kirkland> RoAkSoAx: still around?
[04:07] <RoAkSoAx> kirkland, yep
[04:08] <kirkland> http://people.canonical.com/~kirkland/testdrive-gtk.html
[04:08] <kirkland> http://people.canonical.com/~kirkland/testdrive-wizard.html
[04:08] <kirkland> RoAkSoAx: ^
[04:08] <RoAkSoAx> kirkland, awesome!!
[04:13] <kirkland> RoAkSoAx: http://people.canonical.com/~kirkland/testdrive-gtk-2.html
[04:14] <kirkland> RoAkSoAx: one more ^
[04:14] <kirkland> RoAkSoAx: that table should be sortable by clicking on any of the tabs across the top
[04:14] <kirkland> RoAkSoAx: might have more fields, like size
[04:14] <kirkland> RoAkSoAx: whatever
[04:14] <kirkland> RoAkSoAx: anyway, that's my 10-minute sketch ;-)
[04:16] <RoAkSoAx> kirkland, that's a good idea. I'll do improvements such as classify them into tabs (as my sketch). However, Im not sure if all that is achievable in 3 months. So, I would guess that we'll first have to define which features we would like to see and then, start implementing from that point
[04:21] <kirkland> RoAkSoAx: agreed; let's use UDS as the pivot point by which we define and prioritize features
[04:21] <kirkland> RoAkSoAx: up until UDS, focus on the foundation
[04:22] <RoAkSoAx> kirkland, I'm, though I'm implementing simple pyGTK stuff to give me some ideas of how the modularization should go to be able to use it in both sides (command line/PyGTK)
[04:23] <kirkland> RoAkSoAx: i see you dropped some of my comments from the whiteboard ... would you please establish a wiki page and move them there, if you don't want them in the whiteboard?
[04:24] <RoAkSoAx> kirkland, did I? probably we edited the whiteboard pretty much at the same time and they got lost since I didn't delete anything :S
[04:25] <kirkland> RoAkSoAx: http://pastebin.ubuntu.com/410843/
[04:26] <RoAkSoAx> kirkland, yep I did those changes when your comments weren't there so I guess we just found a bug in LP :)
[04:27] <kirkland> RoAkSoAx: fair enough ... would you mind grabbing them from that pastebin and chunking them back in, pretty please ;-)
[04:28] <RoAkSoAx> kirkland, done already :)
[04:28] <kirkland> RoAkSoAx: rock on
[04:28] <kirkland> RoAkSoAx: okay, i'm calling it a night
[04:28] <kirkland> RoAkSoAx: later dude
[04:28] <RoAkSoAx> kirkland, have a good one
[06:17] <aaditya> This karmic-server did not come up after reboot. After going through a cumbersome process of bringing a monitor in its range, I see that grub-2 menu has no timer, and hence one must hit the enter key to proceed.
[06:17] <aaditya> Server was rebooted after 120 days and there were apparently 4 kernel updates in the mean time.
[06:18] <aaditya> Is there a way to ensure that such problems don't occur on servers?
[06:30] <aaditya> Searching the forums, it appears to be a common issue.
[07:11] <lukehasnoname> aaditya,  grub by default not having a timer? That's odd
[07:50] <aaditya> lukehasnoname: Based on certain forum posts, I realized that it was due to some failure during previous bootup. Still no clue what that problem was.
[07:52] <aaditya> syslog did not help much and at this time I worked around somehow
[07:52] <aaditya> I also verified that /etc/default/grub was in perfect shape
[07:54] <aaditya> This is precisely the issue: http://ubuntuforums.org/showthread.php?t=1283800
[07:55] <aaditya> grub getting stuck on a server based on one issue is not reasonable in my understanding. It's potentially a huge headache for the sysadmins.
[07:55] <_ruben> hmm .. i have a (long-running) script with output redirection to a logfile which filled up the disk, deleting the logfile wont free the space since the file is still in use, any ideas?
[07:58] <Skaag> how do I install a package from lucid, on karmic?
[07:58] <Skaag> specifically, python-pyinotify
[07:59] <_ruben> the complex method would adding lucid repos + apt pinning, or just download the debs+deps from your favorite repo
[08:01] <Skaag> thanks
[08:43] <alvin> aaditya: look here: bug 420077
[10:02] <binBASH> Hi there. I have a question regarding Ubuntu Enterprise Cloud. Which networking mode I need to configure when I have a dedicated subnet of 4 ips for each node in random ip ranges?
[10:07] <merlijn-> Hi,
[10:08] <merlijn-> I'm trying to upgrade an Ubuntu 8.04 server to latest 10.04 beta, but do-release-update -d keeps suggesting intrepid for upgrade
[10:11] <_ruben> merlijn-: is your 8.04 server fully up to date?
[10:12] <_ruben> merlijn-: and it seems you have it configured to not want to upgrade to lts versions only
[10:12] <merlijn-> yea I think I fixed it now
[10:12] <merlijn-> silly typo in /etc/update-manager/release-upgrades
[10:39] <aaditya> alvin: looks like that's the issue I was dealing with. I've added a comment to the bug.
[10:39] <aaditya> Thanks!
[12:22] <alonswartz> hey folks, is there a resource which lists the latest kernel and ramdisk ids (aki/ari) for the official ubuntu/canonical ec2 images? preferably with their associated versions.
[12:23] <alonswartz> I compiled a list of what looks like the latest versions for the current LTS (Hardy) http://alonswartz.pastebin.com/H9CSdyUv but it would be useful to know their versions
[12:36] <alonswartz> updated the list according to include "official" by ami id's listed on the ec2 starter page
[12:37] <alonswartz> are these kernels/initrds built against the latest xen modules?
[12:50] <linuxboy_> I've got a techie installing ubuntu ina remote location. He is failing at the raid setup screen. Can I ssh in and continue it for him?
[12:57] <alonswartz> the official ec2 hardy amis are 2010-01-28, but the latest xen modules 2.6.24-27 were released on 2010-02-04, does that mean the aki/ari's were compiled against 2.6.24-26 (released on 2009-12-04)?
[13:06] <kirkland> smoser: howdy
[13:08] <binBASH> Hi there. I have a question regarding Ubuntu Enterprise Cloud. Which networking mode I need to configure when I have a dedicated subnet of 4 ips for each node in random ip ranges?
[13:11] <ttx> kirkland: how did your all-night-cloud-image-testing go ?
[13:11] <kirkland> ttx: not so well
[13:12] <binBASH> I wish I could start instances in my cloud :p
[13:12] <kirkland> ttx: only did 9 rounds
[13:12] <kirkland> ttx: i think i overloaded it
[13:12] <binBASH> it says I don't have ips
[13:12] <binBASH> hmm
[13:13] <ttx> kirkland: right... a better test would be to run the with-ramdisk images in parallel with the no-ramdisk
[13:13] <kirkland> ttx: i just changed that and started over
[13:13] <ttx> i don('t thin the with-ramdisk would better succeed in such a test tbh
[13:13] <ttx> binBASH: probably an issue with your range of public IPs
[13:14] <ttx> binBASH: for the first install of UEC I'd suggest following http://testcases.qa.ubuntu.com/Install/ServerUECTopology1
[13:14] <binBASH> ttx: Yeah, could be. I wonder how to configure those. My Provider gives me 4 ips / node. All not on the same ip range.
[13:15] <zul> ttx: ill take the memcached one
[13:15] <binBASH> if I run euca-describe-availability-zones verbose all looks fine though
[13:15] <ttx> binBASH: you can list them rather than using a range
[13:15] <ttx> A,B,C instead of A-D
[13:16] <ttx> zul: ok
[13:16] <binBASH> ttx: Yeah, but how it will detect on which node the vm needs to be started?
[13:16] <ttx> zul: please make sure you can reproduce the issue first, so that you can confirm it's fixed by the patch :)
[13:16] <ttx> zul: also could you cover http://iso.qa.ubuntu.com/qatracker/test/3891 ?
[13:16] <alonswartz> update: nevermind, i found what i was looking for in the ubuntu-on-ec2 ppa
[13:17] <binBASH> ttx: You know the ips are bound to node, and cannot be moved to another one.
[13:17] <ttx> binBASH: hm? The nodes from a given cluster should live on the same network
[13:17] <zul> ttx: sure
[13:18] <binBASH> ttx: So as workaround I would probably need many clusters? ;)
[13:18] <ttx> binBASH: you should run on a private network and properly NAT
[13:19] <ttx> so that you don't have this "4 IP per node" linmit
[13:19] <binBASH> ttx: NAT would be not fine in this case, there is a traffic limit of 2 tb / node.
[13:23] <binBASH> ttx: What I need would be, instances with ip 1.1.1.1-1.1.1.3 can be run on node A, 2.2.2.2-2.2.2.3 can run on node B etc.
[13:23] <binBASH> :)
[13:23] <binBASH> dunno if this is possible however
[13:23] <smoser> kirkland, here. whats up?
[13:24] <kirkland> smoser: wanted you to check the log i sent you
[13:24] <kirkland> smoser: see if you see any aberations
[13:24] <kirkland> glitches in the matrix ;-)
[13:25] <smoser> kirkland, from last night ?
[13:26] <smoser> the one from last night looks reasonable.
[13:26] <kirkland> smoser: yeah
[13:26] <kirkland> smoser: my overnight run aborted
[13:26] <kirkland> smoser: i tried to run 8 instances every time
[13:26] <kirkland> smoser: and i don't think my cloud could handle that
[13:26] <kirkland> smoser: within your logic anyway
[13:27] <smoser> ttx, i didn't bother trying beta 1 without ramdisk as i know it would fail.  i didn't bother trying with ramdisk for current because i have no failures related to content of the image (only to the hypervisor)
[13:28] <smoser> kirkland, can you put that log out somewhere ?
[13:28] <ttx> smoser: we believe that those errors that Dustin and I hit are not linked to the with/noramdisk, but rather to the bad performance of our laptop-based cloud... but having some hard evidence that noramdisk doesn't perform worse than withramdisk would help :)
[13:28] <smoser> i'm just interested in seeing it.
[13:28] <smoser> it seems to me that eucalyptus will return success from euca-run-instances before it really has space, and when it does, gets into bad limbo
[13:29] <smoser> ttx, i believe we've seen zero failures that we can at all relate to the ramdisk-less image
[13:30] <smoser> so, there is no way that with-ramdisk image could perform better
[13:30] <ttx> smoser: ok
[13:30] <smoser> the only thing i've seen as a failure in the image is the metadata service was busted once for me
[13:30] <kirkland> smoser: i've overwritten that log, but it's in my byobu scrollback
[13:30] <kirkland> smoser: i'll copy and paste
[13:30] <smoser> kirkland, no worries.
[13:31] <smoser> i do think that the test case is legit though, and shows general failure of euca under load
[13:33] <kirkland> smoser: http://pastebin.ubuntu.com/411023/
[13:33] <kirkland> smoser: but i agree with ttx, i don't think this is ramdisk related
[13:33] <ttx> smoser: well, general failure of eucalyptus on underpowered hardware, at least
[13:34] <ttx> kirkland: do you like my blog meme idea ?
[13:34] <kirkland> ttx: sure, go for it
[13:35] <kirkland> jiboumans: roaksoax has put together a couple of blueprints for the GSoC testdrive project
[13:35] <kirkland> jiboumans: should we label those server-maverick-testdrive* and set you to the approver?
[13:35] <jiboumans> kirkland: sounds like a great idea
[13:36] <jiboumans> feel free to add -gsoc- to that title if you want to make it a bit more prolific
[13:36] <kirkland> jiboumans: alrighty ... just be warned, they're going to look rather desktopy (putting a GTK frontend on a command line too)
[13:36] <kirkland> jiboumans: right, already includes gsoc too
[13:36] <kirkland> jiboumans: https://blueprints.edge.launchpad.net/testdrive/+spec/server-maverick-testdrive-frontend-gsoc
[13:37] <smoser> kirkland, see on line 194 ot f that pastebin.  that to me is an error in euca
[13:37] <smoser> as euca-describe-images showed 'running' for an instance that had 0.0.0.0 as its IP
[13:37] <kirkland> smoser: no, it didn't ... i manually terminated that one
[13:38] <kirkland> smoser: i looked at your code and didn't see any way to exit out of wait_for_running()
[13:38] <smoser> i think it times out at 600 seconds
[13:38] <ttx> maybe "terminated" isn't terminated enough
[13:39] <smoser> i'm wrong. it never does
[13:39] <smoser> kirkland, you were right.
[13:39] <kirkland> smoser: i only see one break in your while loop in wait_for_running()
[13:39] <kirkland> ttx: i like what smoser has here, though ...
[13:40] <kirkland> ttx: i think you/me/mathiaz/smoser should run some over night stress tests for the next few weeks
[13:40] <kirkland> ttx: firing up random numbers of images, different machine sizes, and different images in combination
[13:40] <ttx> smoser: your script doesn't wait for termination ?
[13:40] <kirkland> ttx: my cloud goes into powersave mode most nights
[13:41] <kirkland> ttx: as i'd expect most of our should
[13:41] <kirkland> ttx: for the next few weeks, i suggest that we run some random stuff overnight
[13:41] <smoser> ttx, it does not check state of instances to make sure they're terminated after terminate-instances
[13:41] <ttx> smoser: it can take some time to go from shutting-down to terminated, in my experience
[13:41] <smoser> but it does/did try 4 times with 10 second sleeps in between on the 'start'
[13:42] <smoser> so if a start returns failure it will just sleep and try again
[13:42] <kirkland> ttx: btw, i'm doing a UEC demo at the Texas Linux Fest this saturday
[13:42] <kirkland> ttx: do you have slides or the video from your similar presentation?
[13:42] <ttx> kirkland: right, you wanted to get my slides
[13:42] <smoser> (obviously that 40 second total should probably be increased)
[13:42]  * ttx uploads
[13:43] <kirkland> smoser: i just set rounds to 1,000,000, and I'm just going to let it run until i need my cloud and ctrl-c it
[13:43] <kirkland> smoser: it's tee'ing to a logfile
[13:43] <ttx> kirkland: http://one.ubuntu.com/p/Vy/
[13:43] <smoser> you should probably redirect stderr to log also
[13:43]  * ttx tries ubuntuone magic
[13:43] <kirkland> smoser: what are the indications of problems?  error?  failure?  what should i grep for?
[13:43] <smoser> oooh, look at ttx with his ubuntu one url. fancy
[13:44] <smoser> "failed reach" is the real failure
[13:44] <kirkland> ttx: thanks
[13:44] <kirkland> ttx: i'm going to do a dry run practice today/tomorrow
[13:44] <ttx> it was already on ubuntuone, so I figured I'd try the "publish with ubuntuone" feature
[13:44] <macno> there is a problem with phpldapadmin on lucid, is this the right place to report it?
[13:44] <ttx> working as designed :)
[13:44] <smoser> kirkland, ttx we should probably dump a bit more into that script to make it more reliable while not necissarily more forgiving.
[13:44] <smoser> a.) wait for terminate
[13:44] <zul> macno: no please report it on launchpad
[13:45] <smoser> b.) wait longer for try-to-start
[13:45] <ttx> kirkland: are you going to have internet access ?
[13:45] <smoser> c.) maybe put warnings/errors somewhere other than stdout
[13:45] <smoser> d.) put a limit on wait-for-run
[13:45] <ttx> kirkland: the ukuug presentation did not have that access, and the installer went into strange network timeout quirks
[13:47]  * ttx stares at the oracle logo in the openoffice splash screen...
[13:48] <kirkland> ttx: i'm not planning on having internet access
[13:48] <kirkland> ttx: i'm planning on bring 2 of the dell 1200's, plus the linksys router
[13:48] <kirkland> ttx: the router would connect and network the 2 laptops
[13:49] <kirkland> ttx: if there is internet access, i can use the router to bridge to the wireless
[13:49] <kirkland> ttx: if not, no big deal, i'm not going to fight with it
[13:49] <kirkland> ttx: i'm also bringing my laptop, and i was planning on bringing a webcam too, that I could point at the other two machines while they install
[13:49] <kirkland> ttx: and 2 usb keys
[13:49] <kirkland> ttx: i'll do the install from usb key
[13:49] <kirkland> ttx: rather than show my preseed magic
[13:50] <ttx> kirkland: just test beforehand how the installer reacts to network-but-no-internet situation... I had to press Cancel at a few file downloads at critical times during the install demo
[13:50] <kirkland> ttx: right, the apt one?
[13:50] <ttx> kirkland: yes, doing it from the USB key tells better how easy it is for everyone to try out
[13:51] <ttx> kirkland: yes. Also the timeserver takes a long time to timeout
[13:51] <kirkland> ttx: definitely
[14:06] <binBASH> someone knows if it's possible to configure dhcpd so it provides an ip range based on mac address?
[14:09] <masu3701>  i have an old pc that i want to use as a server....its a AMD Athlon runin at 1.73 GHz and 512 ram
[14:09] <masu3701> the hd is 30 gb tho
[14:13] <incorrect> oh no, mercurial 1.5 didn't make it into lucid
[14:13] <incorrect> sigh
[14:14] <pmatulis> masu3701: thank you for that info
[14:18] <masu3701> pmatulis: ?
[14:24] <ScottK> ttx: I'm going the i386 server upgrade right now.
[14:24] <ttx> ScottK: ok. zul is running it as well
[14:25] <ScottK> It's the server my IRC runs through, so if I disappear and don't come back, you'll know it didn't go well.
[14:33] <zul> ttx: upgrade passed
[14:51] <ScottK> ttx: Mine passed too.
[14:51] <ttx> one test to go before 100% coverage !
[15:16] <binBASH> ttx: I tried like described in the link posted by you to testcase UEC. The instance keeps pending and won't change to run state :/
[15:21] <hggdh> smoser is the rig availabel?
[15:28] <zul> ttx: can you add this one to your list https://bugs.edge.launchpad.net/ubuntu/+source/apache2/+bug/392759
[15:32] <ttx> zul: ack
[15:32] <zul> ttx: thanks
[15:34] <ScottK> Only 5 bugs filed.  Not a bad upgrade.
[15:35] <smoser> hggdh, have at it.
[15:36] <RoAkSoAx> ttx,  heya
[15:36] <hggdh> smoser: thanks
[15:36] <hggdh> ttx, what about bug 557110 ?
[15:38] <ttx> hggdh: yes, that's a good one
[15:43] <dassouki> i want to create a rule to delete all files in a folder if they've been created moer than an hour ago
[15:45] <Pici> dassouki: A rule?
[15:46] <dassouki> Pici: or a shell script
[15:47] <Pici> dassouki: find can do this, look the -cmin/-mmin tests in the manpage
[15:47] <dassouki> Pici: i was hopping for an automagic solution
[15:47] <zul> ttx: i was able to reproduce the memcached thingy
[15:49] <Pici> dassouki: run the script in a cron job then.  I have similar scripts running here for cleaning up old logfiles (I should use logrotate, but whatever).
[15:50] <dassouki> Pici: that's what i wnt to use it for, a data logger downloads file, however the file is cummulative
[15:50] <dassouki> i just want to delete all the older files
[15:51] <Pici> dassouki: find has arguments that can delete files, or you can use -exec if you want to do something else with them.
[15:52] <dassouki> no just delete them
[16:24] <venmx> hi, im trying to setup ubuntu to deploy over the network with kickstart, but im getting "bad archive error", cant find anything useful on google. can anyone help? my problem is i don't know what part of the ftp to mirror and which part to point the "url" directive in the kickstart.cfg file to?? do i need to mirror the /ubuntu/pool directory and contents too to get the packages?
[16:27] <ttx> kirkland: did you exercise recently the web UI / create users / email notifications / imagestore image registration in UEC ?
[16:33] <ttx> hggdh: how are the beta2 candidate functional tests on the testrig going ?
[16:47] <mdz> smoser, around?
[16:47] <smoser> here
[16:47] <mdz> smoser, hi. quick question on EC2 AMIS
[16:48] <mdz> how many daily builds do we keep around, or have we not started expiring them yet?
[16:48] <smoser> i'm fairly certain the number is 5
[16:48] <smoser> but for you, you may be seeing 90 days worth
[16:48] <smoser> is that your question ?
[16:48] <mdz> smoser, I'm trying to explain the data I see on http://thecloudmarket.com/stats#/by_image_owner
[16:49] <mdz> where it looks like something significant changed on 1 March :-)
[16:50] <smoser> ugh. it appears lfash isn't working properly for me...
[16:50] <smoser> ok. so 2 things explain this
[16:50] <smoser> 1.) right around there we started publishing ebs amis
[16:51] <smoser> 2.) until sometime last week I had no code to privatize/delete ebs amis
[16:52] <kirkland> ttx: very lightly, only
[16:52] <kirkland> ttx: ie, not comprehensively
[16:52] <ttx> kirkland: yes, same for me... I'd suggest to spend a few test cycles on that to make sure we are ok there
[16:52] <ttx> (or find someone that did)
[16:54] <ttx> kirkland: generally I think we are in good shape as far as "installation / running an instance" goes... and we migth have not exercised peripheral features so much
[16:55] <ttx> kirkland: your imagestore question made me think about the rest of the UI things
[16:55] <kirkland> ttx: yeah, it really hasn't been touched
[16:55] <kirkland> ttx: which is perhaps a good thing
[16:56] <ttx> hggdh: around ?
[16:56] <smoser> mdz, ^^ i just verified it the ebs removal code is functional.  I would expect that number of images to settle down to about twice the march 1 level
[16:57] <binBASH> ttx: The instances are running now. It just turned out it takes some time until they are online :p
[16:57] <mdz> smoser, thanks for the explanation
[16:57] <ttx> binBASH: oh yes :)
[16:57] <binBASH> I didn't expect it can take 5 mins
[16:57] <ttx> binBASH: the subsequent ones go faster
[16:58] <ttx> binBASH: but that's about what it takes on relatively slow disks
[16:58]  * ttx remembers the time when it took 20 min
[16:58] <binBASH> I think it's the lan which causes bottleneck
[16:58] <binBASH> only 100 Mbit
[16:58] <binBASH> ;)
[16:58] <venmx> hi... what is the "pool" directory for in the ubuntu rsync/ftp/http archives?
[16:58] <ttx> binBASH: arh, upgrade ;)
[16:58] <binBASH> not possible
[16:58] <binBASH> :/
[16:58] <roy_> How can i remove pear package from server, anyone know this ?
[16:59] <ttx> kirkland: remember when a UEC full test run would take half a day ? funny times :)
[16:59] <binBASH> ttx: I can't select instance type on rightscale though
[16:59] <kirkland> ttx: heh
[17:00] <ttx> binBASH: could you elaborate on that ?
[17:00] <binBASH> ttx: It always launches the smallest instance, can't choose the others.
[17:00] <ttx> kirkland: please see with hggdh on the beta2 candidate functional tests results -- and signoff on them if you're satisfied by the results (by marking the work item done)
[17:01] <kirkland> hggdh: howdy, your b2 tests are done?
[17:01] <ttx> binBASH: not sure that's a bug on our side...
[17:01] <binBASH> on console I can launch others ;)
[17:02] <hggdh> kirkland: going thru topo2 now
[17:02] <binBASH> think it's a rightscale bug
[17:02] <venmx> does anyone have experience with ubuntu netboot installation using a local archive?
[17:02] <hggdh> kirkland: after I am done with it, we can close the tests
[17:02] <kirkland> hggdh: cool, poke me as soon as you're done
[17:02] <hggdh> kirkland: ack
[17:03] <ttx> hggdh: glad to see you're alive :)
[17:03] <ttx> kirkland: your pings work better than mines.
[17:03] <binBASH> ttx: I wonder as well how to get vnc viewer enabled. :)
[17:04] <hggdh> ttx: heh
[17:04] <kirkland> ttx: i ping harder
[17:04] <binBASH> so I can connect to vms when there is no ip
[17:04] <hggdh> weechat is not ringing when I an pinged, so -- if I am busy on another workspace -- I will not know about it
[17:05]  * ttx hugs the new xchat green indicator
[17:06] <hggdh> :-)
[17:06]  * hggdh kicks (lovingly) the bloody weechat GIT
[17:08]  * ttx drinks the traditional release day cognac
[17:25] <AntORG> plex
[17:25] <AntORG> wrong tab
[18:19] <hggdh> kirkland: on topo2, at the rig -- no instaces succeed
[18:26] <kirkland> hggdh: hrm?
[18:26] <kirkland> hggdh: bug?
[18:26] <kirkland> hggdh: something else?
[18:28] <hggdh> kirkland: not sure, actually success rate is at about .05 right now, stressing
[18:28] <hggdh> kirkland: 200 instances
[18:28] <hggdh> I see a lot of ssh timeouts
[18:32] <kirkland> hggdh: hrm, okay, let's get on top of this ...
[18:32] <kirkland> hggdh: anything different between this and topo1 (besides the topology)?
[18:36] <hggdh> kirkland: and apart from the users, not, all the same
[18:46] <zul> ttx: ping one more to add to your list https://bugs.edge.launchpad.net/ubuntu/+source/autofs5/+bug/533029
[18:48] <kirkland> mathiaz: around?
[18:48] <mathiaz> kirkland: not for a long time
[18:49] <mathiaz> kirkland: I'll be back later today though
[18:49] <kirkland> mathiaz: looks like hggdh is having no success with topo2 right now
[18:49] <kirkland> hggdh: can you pastebin your results log?
[18:50] <mathiaz> kirkland: is it the installation that fails or the test run?
[18:52] <kirkland> mathiaz: test runs
[18:52] <kirkland> mathiaz: i think ... hggdh ?
[18:52] <kirkland> hggdh: btw, how do you pronounce hggdh ?
[18:52] <kirkland> "hugduh?
[18:52] <hggdh> kirkland: http://pastebin.ubuntu.com/411159/
[18:53] <hggdh> kirkland: 'haggadah'
[18:53] <hggdh> hugduh is cool, though
[18:53] <kirkland> hggdh: :-D
[18:53] <kirkland> hggdh: okay, so need a bit more than that to determine the cause ....
[18:54] <hggdh> I 'spose, yes ;-)
[18:54] <hggdh> kirkland: want me to upload the log to tamarind?
[18:54] <kirkland> hggdh: sure, put it somewhere i can see
[18:56] <hggdh> kirkland: /home/cerdea/multi_test.log.2010-04-08_125614
[19:01] <smoser> hggdh, what is that pastebin from ?
[19:01] <smoser> ie, what produced it
[19:02] <kirkland> smoser: mathiaz's test framework
[19:02] <smoser> that is fancy smanchy. i'd not seen it. where is it ?
[19:02] <smoser> source ?
[19:03] <kirkland> hggdh: what kind of image do you have registered?
[19:03] <kirkland> smoser: really?  i was kinda wondering why you wrote your own script from scratch :-)
[19:03] <kirkland> smoser: thought you wanted to narrow your testing focus
[19:03] <smoser> i try to pay as little attention as possible
[19:03] <kirkland> smoser: bzr+ssh://bazaar.launchpad.net/~mathiaz/%2Bjunk/uec-testing-scripts/
[19:03] <hggdh> kirkland: uec 20100406.1
[19:03] <smoser> and fully subscribe to the teachings of NIH
[19:03] <smoser> :)
[19:04] <kirkland> smoser: is 20100406.1 the known, good image?
[19:04] <hggdh> smoser this is the output from mathiaz scripts
[19:04] <smoser> 20100407.1
[19:05] <smoser> is what will be beta
[19:05] <smoser> 2
[19:05] <hggdh> smoser: ooooh...
[19:05] <hggdh> I will delete the image, and add this one
[19:05] <kirkland> hggdh: yeah, smoser made it ramdiskless ... we should rerun with that
[19:05] <kirkland> hggdh: cool
[19:05] <smoser> it should make no difference
[19:05] <kirkland> hggdh: let me know when you start getting results
[19:05] <smoser> although there might be some packages difference3 sbetween those 2
[19:05] <hggdh> kirkland: roger
[19:05] <kirkland> hggdh: but i'm not sure that's the problem
[19:06] <hggdh> it does not sound like it...
[19:06] <smoser> fwiw, 20100407.1 is hwat is listed at http://iso.qa.ubuntu.com/qatracker/build/ubuntuserver/all
[19:06] <hggdh> well, when I started, it was not there
[19:06] <smoser> which should generally be "the ultimate source"
[19:06] <smoser> fair
[19:07] <kirkland> smoser: can you grab that log from tamarind?
[19:07] <kirkland> smoser: looks like it's ssh timing out
[19:07] <kirkland> DEBUG:INSTANCE i-43B4084B:Test output: ssh: connect to host 10.55.55.114 port 22: Connection timed out^M
[19:07] <kirkland> smoser: instance marked running
[19:07] <smoser> what does console show ?
[19:08] <kirkland> hggdh: do you have any of these failed instances still running?
[19:08] <kirkland> hggdh: when you get one into the failed state, can you pastebin the output of euca-get-console $INSTANCE_ID ?
[19:09] <hggdh> kirkland: no, all instances were terminated
[19:09] <kirkland> hggdh: okay, thanks
[19:10] <hggdh> smoser: er, http://iso.qa.ubuntu.com/qatracker/build/ubuntuserver/all still lists 20100406.1
[19:11] <smoser> Ubuntu Server UEC i386 (20100407.1)
[19:11] <smoser> Ubuntu Server UEC amd64 (20100407.1)
[19:12] <hggdh> smoser: I stand corrected
[19:16] <hggdh> k downloading the new image now
[19:21] <ttx> kirkland: do we have any known good point with that topology on the testrig ? I.e. post-beta1 tests that would show success ? Or is it the first time it's run ?
[19:21] <hggdh> ok. first run (single, 10 instances, 100% success
[19:22] <hggdh> ttx: all my tests there on beta1 were successfull
[19:22] <smoser> hggdh, fwiw, its identical package list between 20100406.1 and 20100407.1.  The only difference should be the lack of ramdisk.
[19:22] <smoser> (I just compared the manifest.txt in those)
[19:23] <kirkland> ttx: i've run this before
[19:23] <kirkland> ttx: i suspect that something's wrong with hggdh's user setup
[19:23] <kirkland> ttx: he's testing multiple users
[19:23] <hggdh> must have been, somewhere
[19:23] <ttx> hggdh: ok, if you reproduce the issue, try to minimize the changes between the two (for example by running the same cloud image as in beta1). After all you're validating UEC more than the cloud image here
[19:23] <kirkland> hggdh: what's the permissions on their private keys?
[19:24] <hggdh> kirkland: 400, all of them
[19:25] <kirkland> hggdh: hmm, okay ...
[19:25] <ttx> kirkland: re: "something wrong in hggdh's user setup": something that would have changed since beta1 ?
[19:25] <kirkland> hggdh: okay, try with the new image, and lets see what happens
[19:26] <kirkland> ttx: something that's different between how hggdh set up his multiple users, and how I set up my multiple users
[19:26] <kirkland> ttx: and how mathiaz set up his multiple users
[19:26] <ttx> kirkland: if we are to compare results, better use the same technique
[19:27] <ttx> I thought that would be consistent across runs
[19:27] <smoser> we should modify the test suite to grab console output on failure at least, and likely in all cases. its just useful info to have.
[19:29] <hggdh> interesting. I have a running instance i-404B07EF, and euca-get-console-output hangs
[19:29] <kirkland> ttx: right, this is back to the issue mathiaz and I have brought up many times ... there is no Eucalyptus API for automatically creating users
[19:29] <hggdh> smoser: I agree
[19:29] <kirkland> ttx: so the only options right now is for each person to do it manually, each test run
[19:29] <kirkland> ttx: or save and replace the database
[19:29] <ttx> kirkland: understood, thanks for the precision
[19:30] <smoser> hggdh, hangs ?
[19:30] <kirkland> ttx: we can do the latter (mathias does from time to time)
[19:30] <smoser> it does sometime take quite a while
[19:30] <smoser> my experience is at least 6 seconds in most cases.
[19:30] <kirkland> ttx: but that doesn't exercise the bits that create/install/update the database
[19:30] <hggdh> indeed. I actually did it wrong this morning -- did not remove the old user data, and failed on the first test
[19:30] <hggdh> smoser: 408 timeout
[19:31] <smoser> oh. wow. on euca-get-console-output ?
[19:31] <ttx> hggdh: you nuked it pretty badly :)
[19:33] <Petfrogg> hello
[19:34] <hggdh> ttx: I am good at it :-)
[19:34] <hggdh> this is it. I am trashing the current setup and starting from scratch
[19:35] <Petfrogg> i am using a ubuntumachine as the gateway and firewall. Inside i got a couple machines i would like to get directed to if i type in my webbbrowerser on anymachine inside the network. "http://netpet" -> 10.0.0.60. How do i fix that? Should i do it in the firewall?
[19:36] <ttx> hggdh: you have The Gift of QA !
[19:36] <Petfrogg> or should i somehow fix it in the hdcp?
[19:36] <Petfrogg> dhcpd
[19:36] <Petfrogg> or is it a DNS issue?
[19:37] <xperia> hello to all. i have on my ubuntu server the mailserver postfix that is able to recieve and send mails. on the ubuntu server this works great but now i need somehow the possibility to fetch this mails with thunderbird with my laptop from the mailserver. do i need some special configuration for fetching mails with thunderbird ?
[19:39] <hggdh> kirkland: just to be sure, to get up multiple users: (1) get to the web, and create them;(2) for each user: login, download creds; (3) move them all to the CLC
[19:40] <kirkland> hggdh: right
[19:40] <hggdh> kirkland: (4) unzip each bloody cred into the correct place
[19:40] <kirkland> hggdh: right
[19:40] <hggdh> dammit
[19:40] <kirkland> hggdh: ensure perms are right
[19:41] <hggdh> kirkland: it seems they are already unzipped correctly
[19:41] <hggdh> but if they were wrong (perms) I would be unable to use them
[19:42] <hggdh> and, just to be sure: current beta is 20100406.1 (server) and 20100407.1 (uec), correct?
[19:54] <ttx> jdstrand: the change you propose is actually committed as http://github.com/memcached/memcached/commit/d9cd01ede97f4145af9781d448c62a3318952719
[19:56]  * ttx disappears again
[19:57] <jdstrand> ttx: holy cow, it was completely untested
[19:57] <jdstrand> ttx: I hope they tested it
[19:58] <jdstrand> :)
[19:58] <ttx> jdstrand: theirs is slightly different :)
[19:59] <jdstrand> yeah, but still, I wasn't sure of the implications of '4' vs '5', etc, etc,
[19:59] <jdstrand> ultimately, it is on them :)
[20:06] <fine_line> join ubuntuforums
[20:20] <kirkland> hggdh: yes, that looks correct
[20:20] <kirkland> hggdh: any new results from this round?
[20:23] <alienseer23> I had to copy over /var/lib/mysql from another server due to a hdd failure, can someone help me with the permissions/ownership of these files and folders?
[20:23] <alienseer23> is 755 mysql:mysql good for everything in that di9rectory?
[20:28] <hggdh> kirkland: installation takes quite some time...
[20:29] <kirkland> hggdh: oh?  i thought you were just going to re-register the new image?
[20:29] <hggdh> kirkland: no, I had already done that, and it was still hosed
[20:29] <Hypnoz> this script is in /etc/init.d/networking, but it doesn't seem to actually detect these things (like nfs)
[20:29] <Hypnoz> http://paste.ubuntu.com/411198/
[20:29] <Hypnoz> anyone else want to test out that sed | grep line to see if it finds their nfs mount?
[20:29] <hggdh> kirkland: I deceided to start from scratch
[20:30] <hggdh> kirkland: right now installing the SC, and then I can install both NCs at the same time
[20:31] <kirkland> hggdh: cool
[20:33] <sherr> Hypnoz: works for me (karmic)
[20:33] <sherr> NFS mount
[20:34] <Hypnoz> ah you know what, i wasn't removing the -q from grep
[20:34]  * Hypnoz is dump
[20:34]  * Hypnoz is also dumb
[20:35] <RoAkSoAx> kirkland, howdy!! I was thinking... why would we need to select a codename that is not ubuntu+1?? Since I do not think that someone would like to TestDrive an stable release
[20:52] <Hypnoz> man ubuntu networking is flaky
[20:52] <Hypnoz> this is the command /etc/init.d/networking uses to bring down all interfaces...  ifdown -a --exclude=lo
[20:52] <Hypnoz> so you'd think that would work right...
[20:54] <Hypnoz> hmm seems to be an issue with ifdown being able to see interfaces used in a bonded interface
[21:05] <kirkland> RoAkSoAx: i think they might
[21:05] <kirkland> RoAkSoAx: i think i might
[21:06] <kirkland> RoAkSoAx: i use that to check for regressions
[21:06] <kirkland> RoAkSoAx: i think we should default to the development version
[21:06] <RoAkSoAx> kirkland, and "add" any other available release!
[21:06] <kirkland> RoAkSoAx: but maybe someone is running Lucid Ubuntu and wants to try out Lucid Kubuntu
[21:07] <RoAkSoAx> kirkland, right, I didn't think about that but I see your point
[21:11] <jaypur> hi i'm using scp but it's not working, it says that is no such directory, but it exists, can someone help me?
[21:11] <jaypur> i've already moved a filme once but now it's not going
[21:16] <jaypur> no one?
[21:16] <jaypur> =/
[21:18] <jaypur> i got it now
[21:18] <jaypur> bye
[21:25] <hggdh> kirkland: does this ring any bells? http://pastebin.ubuntu.com/411223/
[21:27] <kirkland> hggdh: nope ... smoser ^ ?
[21:27] <smoser> how did you do that color . yuck.
[21:29] <smoser> doesn't ring a bell, but that %s looks wrong :)
[21:29] <hggdh> heh. /me still going full throttle
[21:31] <smoser> hggdh, can you reproduce that ?
[21:32] <hggdh> smoser: anytime :-)
[21:32] <hggdh> smoser: on the current rig install, I mean
[21:32] <smoser> and can you add some --i dont know why you wouldn't get output from the failed uec-publish-image
[21:32] <smoser> tell me where this is, and i'll take a look.
[21:34] <hggdh> smoser: at cempedak
[21:34] <smoser> stop making it so easy for me to help!
[21:34] <smoser> i'm trying to avoid you :)
[21:34] <hggdh> I am already creating quite a reputation...
[21:35]  * hggdh right now is in need of a bit of strong beers
[21:35] <hggdh> s/bit/lot/
[21:37] <RoAkSoAx> hggdh, i wish i could say that :(
[21:38] <hggdh> RoAkSoAx: I wish I could *do* it
[21:38] <RoAkSoAx> hggdh, me too but i can't drink alcohol for the next 3 months at least
[21:40] <hggdh> RoAkSoAx: oh, this is different. I *can*, just will not. Liver is still good, methinks
[21:41] <RoAkSoAx> hggdh, that's why I said I wish i could... cause I cannot even think about it (because I cant even drink it :()
[21:42] <hggdh> RoAkSoAx: think positively. One 3 months (at least)
[21:42] <hggdh> but it still sucks
[21:43] <RoAkSoAx> hggdh, it does!! been 3 months already without being able to drink
[21:45] <smoser> hggdh, ok. so heres the problem/solution
[21:45] <smoser> Image: Failed to find service dispatcher for component=walrusfailed to upload kernel
[21:45] <smoser> is the error you get if you allow the euca-upload-bundle error to get through
[21:46] <smoser> but uec-publish-tarball/uec-publish-image were capturing it and not letting it out on error.
[21:48] <smoser> the reason they weren't letting it out is because the error is going to stdout
[21:48] <hggdh> smoser: walrus is offline?
[21:48] <smoser> if it were going to stderr it would get through
[21:48] <smoser> i dont know aobut that.
[21:49] <hggdh> weird. It is, now
[21:53] <hggdh> smoser: want a bug on stdout/stderr?
[21:54] <smoser> well the bug on stderr is in euca2ools.. you can open it if you'd like. i'd say its low priority.
[21:57] <hggdh> will do, later. Right now I will dig in and find out why the walrus did not get the credentials
[22:01] <hggdh> ah, got it
[22:04] <smoser> hggdh, well, i just pushed a fix/workaround in euc-publish-tarball for the stdout issue.
[22:04] <smoser> it *somehwat* makes sense to send stdout from underlying tools through to the user on failure
[22:04] <smoser> but i would have preferred (and expected) the error messages to stderr
[22:05] <hggdh> I agree, but at least we will get the error messages