[00:21] veenenen, i'm not sure i understand the question [00:21] they should reboot, do they not ? [00:22] yeah, but after the reboot there's no more console [00:22] i can still ssh in though [00:22] I just wanted to make sure that was intended behaviour [00:24] It makes sense to me why that would be, but I just wanted to make sure I wasn't doing anything wrong [00:25] hm.. really, no more console. [00:25] well, I'm not prompted to login [00:25] I guess I still get a console [00:25] hm.. i would have thought youd still get console. [00:26] i can try to test this tomorrow. [00:26] i'd appreciate it if you'd open a bug [00:26] sure [00:26] ideally, just run 'ubuntu-bug cloud-init' from inside the instance [00:26] also, do you always have to boot from the floppy image when running it on kvm? [00:50] nevermind, it just took several minutes for it to show up [00:53] hm... that is strange. [00:53] the reason you boot from a floppy is that what you have is a disk image with no partition table [00:53] so there is no place to put a boot loader [00:53] so the floppy provides that. [00:54] that's what I figured [00:54] i know. [00:54] seriously, floppies. [00:54] :) [00:54] haha [00:54] if you'd like you can do the same thing easily enough with a cdrom [00:55] the floppy image that is there actually doubles as a cdrom (other than it is padded to 2880K) [00:55] you will still likely have to "clean" your image before you put it up on ec2, if you're booting into it and doing things. [00:55] I'm booting it as a cdrom already. virt-install doesn't have the option of floppies [00:55] oh. i'm glad that worked then. [00:56] ie, you will wan to un-set the password and such. there are some other things that 'uncloud-init' does, or that 'cloud-init' does that you'd want to to un-do. [00:56] I was just planning on using the standard ec2-bundle-vol command [00:56] hm.. [00:56] i dont knwo if that would work or not. [00:56] i really apologize for not being able to give as much help here. [00:56] you've been great [00:56] i wish this was better documented or all "just worked" better. [00:57] in general, i don't like the "bundle-vol" approach [00:57] it tries to "un-boot" an image [00:57] i would much prefer modifying a pristine one without booting it. [00:57] ie, extracting, mounting loopback, and either modifying the contents or chroot'ing in and doing things. [00:57] ideally via scripts. [00:58] i do realize, though,t hat people want to do what you want to do [00:58] I just want to get this all working then I can dig in and figure out better ways of doing everything [00:58] yeah. [00:58] i got to run [00:58] good luck. [00:58] thanks for all your help === rberger_ is now known as rberger [07:14] smoser: yes, someone should have tested that. I was on vacation that week, so I can't tell you who. [07:15] smoser: that said, the error is probably not a permanent error [07:15] and not linked specifically to 10.04.1 [07:16] it's generally because it detects two CLCs or two CCs on the same network [07:16] the second one is detected as #2 [15:51] hello all [15:52] i am facing problems in deploying applications to unbuntu cloud [15:52] smby help me.... [15:54] hey i am new t0 irc help me guys...... [16:51] crazy, well, what is your problem ? === sidnei is now known as sidnei-lunch === sidnei-lunch is now known as sidnei [22:33] hmm.. I wonder if we can get newer ec2 utils into maverick to support m1.micro [22:43] SpamapS: What changes need to be made to support t1.micro? [22:44] is it t1.micro? Not sure. Maybe I just need to use the right type... [22:44] I know in the past regions had to be added at the tool level. [22:56] erichammond: ok, so that solves that. :) [22:56] Client.UnsupportedOperation: AMIs with an instance-store root device are not supported for the instance type 't1.micro'. [22:56] so you have to do EBS for micro? :( [22:59] Oh I guess thats because these have more capability.. cool [23:16] also changes had to be made to the fstab to remove mounting sdb [23:16] but that may have been fixed since I started one yesterday [23:28] SpamapS: Yes, t1.micro must be EBS boot, 32- or 64-bit. [23:29] I just got one up and running [23:29] smoser: I suppose that may create a case for a smaller EBS boot volume size than 15GB. [23:29] I may leave it for a while... why not? ;) [23:34] $1.50 per month wasn't that big of a deal when you were paying at least $60 per month for an m1.small, but $1.50 per month is a big percentage increase when you start at $8 per month for t1.small, 3yr reserved. [23:34] It's possible to increase the size of the root EBS volume at run time, but not decrease it. [23:38] even with the 15 GB size it's still in line with the smallest offering at rackspace