--- wikisrc/amazon_ec2.mdwn 2011/02/19 03:42:54 1.22 +++ wikisrc/amazon_ec2.mdwn 2011/02/19 04:34:56 1.23 @@ -77,6 +77,10 @@ These instances are tied to a *region* ( AKI, or *Amazon Kernel Image*, are a specific type of image. It represents the Xen guest para-virtualized kernel, as used by an AMI. Certain AKIs are allowed to boot customized operating systems, e.g. those that are still not officially supported by Amazon. Thanks to [PyGrub](http://wiki.xensource.com/xenwiki/PyGrub), it can boot a kernel that resides inside an AMI's snapshot. +# Using pre-made AMIs + +XXX TODO + # Build-up your NetBSD system ## Fetch and build NetBSD @@ -90,10 +94,17 @@ This tutorial assumes that you will buil [Details regarding on how you can fetch *src* are given in the NetBSD's guide](http://www.netbsd.org/docs/guide/en/chap-fetch.html). Here are the basic commands you should type to build and install NetBSD under */mnt/ec2*: [[!template id=programlisting text=""" -# fetch src.tgz -# decompress -# build toolchain, kernel and distribution -# install in /mnt/ec2 +cd /usr/ +# grab a recent src.tgz file (use curl(1), ftp(1), wget(1), ...) +ftp -a 'http://ftp.netbsd.org/pub/NetBSD/NetBSD-current/tar_files/src.tar.gz' +# Decompress +tar -xzpf src.tar.gz +cd src +# build distribution and kernel +./build.sh -O ../obj -T ../tools -D ../dest -R ../release -m amd64 -U distribution +./build.sh -O ../obj -T ../tools -m amd64 kernel=XEN3_DOMU +# install distribution in /mnt/ec2 +./build.sh -O ../obj -T ../tools -D ../dest -R ../release -U install=/mnt/ec2 """]] # Configuration of your NetBSD EC2 tree @@ -377,10 +388,38 @@ Copyright (c) 1982, 1986, 1989, 1991, 19 The Regents of the University of California. All rights reserved. NetBSD 5.99.45 (XEN3_DOMU) #9: Wed Feb 16 21:14:49 CET 2011 - jym@paris:/home/jym/cvs/obj/sys/arch/amd64/compile/XEN3_DOMU [...] +NetBSD/amd64 (ip-10-112-58-223.ec2.internal) (console) + +login: """]] ## Connect to your NetBSD instance +Connection is similar to the one you used for the Amazon Linux instance, except that you login as "root" instead of "ec2-user": + +[[!template id=programlisting text=""" +$ ec2-describe-instances i-953d72f9 +RESERVATION r-da8021b7 983624114127 default +INSTANCE i-953d72f9 ami-74d0231d ec2-50-16-3-55.compute-1.amazonaws.com ip-10-112-58-223.ec2.internal running <your_ssh_key_pair_name> 0 t1.micro 2011-02-19T04:01:03+0000 us-east-1c aki-427d952b monitoring-disabled 50.16.3.55 10.112.58.223 ebs paravirtual xen +BLOCKDEVICE /dev/sda1 vol-ec3c4a84 2011-02-19T04:01:31.000Z +BLOCKDEVICE /dev/sda2 vol-ee3c4a86 2011-02-19T04:01:31.000Z +$ ssh -i "$EC2_SSH_KEY" root@ec2-50-16-3-55.compute-1.amazonaws.com +The authenticity of host 'ec2-50-16-3-55.compute-1.amazonaws.com (50.16.3.55)' can't be established. +[...] +Thank you for helping us test and improve NetBSD. + +Terminal type is xterm. +We recommend that you create a non-root account and use su(1) for root access. +ip-10-112-58-223# uname -a +NetBSD ip-10-112-58-223.ec2.internal 5.99.45 NetBSD 5.99.45 (XEN3_DOMU) #9: Wed Feb 16 21:14:49 CET 2011 jym@paris:/home/jym/cvs/obj/sys/arch/amd64/compile/XEN3_DOMU amd64 +ip-10-112-58-223# +"""]] + +Done! + ## And now? + +Well, you got a NetBSD instance that is in almost every part similar to what a NetBSD domU can be. You can use this domU to host Internet services, run a database, extend your build farm, or use it as a sandbox. The AMI being built around snapshots, you can play and break your instance in every way you want; just restart one anew if you need to. Don't forget that Amazon will charge acccordingly :) + +Remember, you can query information regarding your AWS account through [[!template id=pkg category=misc name=ec2-api-tools]] package. It is quite easy to use these tools for scripting; for a more elaborate, graphical interface, use the [Amazon Management Console](https://console.aws.amazon.com/ec2/home).