| === erichammond1 is now known as erichammond | ||
| agussman | Does anyone know where I can get a list of all the kernels ec2 supports? | 15:21 |
|---|---|---|
| koan | I created a Jaunty AMI with vmbuilder, and I launched it successfully with ec2-run-instances. ec2-describe-instances shows it as running and lists an IP address, but I can't ping to it | 16:30 |
| koan | and ec2-get-console-output gives a sensible output, so there's no kernel problem | 16:30 |
| koan | what could be wrong? | 16:31 |
| agussman | koan: It could be blocked by the security settings you specified when you started theimage | 16:34 |
| koan | where can I find these settings? | 16:36 |
| rick_h_ | yea, by default I don't think the images allow icmp requests | 16:36 |
| koan | I can't ssh into the image too | 16:36 |
| rick_h_ | you should be able to ssh into it with the ubuntu user account and key launched with | 16:36 |
| koan | but I did ec2-authorize default -p 22 | 16:36 |
| koan | and I added ssh to --addpkg | 16:36 |
| rick_h_ | you can check the console output with the EC2 web manager to see if there were any errors starting the instance? | 16:37 |
| rick_h_ | you're using keys to ssh correct? | 16:37 |
| rick_h_ | by default it doesn't allow password logins | 16:37 |
| koan | indeed | 16:37 |
| koan | ec2-get-console-output only complains about uvesafb | 16:37 |
| koan | so I really don't see where the problem lies | 16:39 |
| koan | I created the image with sudo vmbuilder xen ubuntu --suite=jaunty --arch=i386 --addpkg ssh unattended-upgrades --ec2 --ec2-cert=$EC2_CERT --ec2-key=$EC2_PRIVATE_KEY --ec2-user=$AWS_USER_ID --ec2-access-key=$AWS_ACCESS_KEY_ID --ec2-secret-key=$AWS_SECRET_ACCESS_KEY --ec2-bucket=lxf-bucket --ec2-prefix=lxf --part lxf-part -o -debug | 16:40 |
| koan | is there a problem with that? | 16:40 |
| agussman | koan: the securtiy settings are specified in the group file that you specify with -g when you run ec2-run-instances | 16:43 |
| koan | agussman: ok, and if I don't specify a group file? | 16:44 |
| agussman | I don't know what the default security settings are, but I think they are very strict | 16:45 |
| koan | ok, but I explicitly allowed port 22, and I can ssh into other AMIs, so I guess that's not the problem | 16:45 |
| agussman | yeah, I'm not too familiar with ec2-authorize, I usually manage my vms using Elasticfox | 16:46 |
| rick_h_ | can you telnet to port 22? | 16:47 |
| rick_h_ | if you can, the port is open, just a matter of correct user/key settings I'd imagine | 16:47 |
| koan | nope I can't | 16:48 |
| agussman | koan: this has some instructions for setting up open ssh, I'm not sure if they still apply though: https://help.ubuntu.com/8.10/serverguide/C/jeos-and-vmbuilder.html | 16:48 |
| koan | agussman: I know that page, I have built Ubuntu JeOS in the past with vmbuilder, but it's not entirely relevant in this case | 16:50 |
| agussman | do you happen to have a link to some good documentation handy? I've been having a heck of a time getting vmbuilder to do what I want | 16:55 |
| koan | do I lack the right firstboot scripts maybe? | 16:55 |
| koan | agussman: well I found Ubuntu's wiki pages invaluable, like the one you referred to | 16:56 |
| koan | I'm now following this page for building an AMI: http://www.bonjoydell.com/blog/2009/05/08/creating-amis-for-amazon-ec2-with-ubuntu/ | 16:56 |
| agussman | koan: thanks for the link, I'll check it out | 17:01 |
| koan | I hope you have more luck than me :) | 17:05 |
| agussman | koan: Did you install ubuntu-vm-builder or python-vm-builder? | 17:15 |
| koan | both | 17:16 |
| koan | strange, now I do exactly the same, but building an intrepid image instead of jaunty, and this even has no kernel output in the console log | 17:20 |
| koan | it really doesn't work, has anyone here a working procedure to create an Ubuntu AMI with vmbuilder? | 18:50 |
| erichammond | koan: I have not been able to build good Ubuntu images for EC2 using vmbuilder yet. The server team is still working on perfecting this process and the documentation. | 19:27 |
| koan | erichammond: thanks for that information, I was just looking at your ec2ubuntu-build-ami script | 19:28 |
| koan | I'm trying it at this moment | 19:28 |
| NoobFukaure | are all of ec2's machines located together in the same geographic location? | 19:40 |
| NoobFukaure | n/m | 19:40 |
| erichammond | NoobFukaure: The first part of this article talks about that: http://alestic.com/2009/07/ec2-availability-zones | 19:40 |
| NoobFukaure | where in the US are the servers hosted? | 19:41 |
| NoobFukaure | ah okay thanks | 19:41 |
| NoobFukaure | fantastic! | 19:41 |
| NoobFukaure | erichammond: thanks! | 19:41 |
| erichammond | Amazon does not give specific details about locations for security reasons. | 19:41 |
| NoobFukaure | makes sense, I'm more interested in "general" locations, mainly for latency | 19:42 |
| erichammond | From their security whitepaper: "AWS data centers are housed in nondescript facilities, and critical facilities have extensive setback and military grade perimeter control berms as well as other natural boundary protection." | 19:43 |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!