--- wikisrc/amazon_ec2.mdwn 2011/02/19 03:42:54 1.22
+++ wikisrc/amazon_ec2.mdwn 2011/02/23 21:44:38 1.31
@@ -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
+su root -c ./build.sh -O ../obj -T ../tools -D ../dest -R ../release -U -V INSTALLSETS="base etc" install=/mnt/ec2
"""]]
# Configuration of your NetBSD EC2 tree
@@ -105,6 +116,7 @@ Under */mnt/ec2*, edit the files to add
[[!template id=filecontent name=etc/rc.conf text="""
rc_configured=YES
+ec2_init=YES
sshd=YES # for remote shell access to instance
"""]]
@@ -115,16 +127,17 @@ PermitRootLogin without-password
This file is needed if you want to login via the EC2 SSH key pair created previously:
-[[!template id=filecontent name=etc/rc.d/ec2-init text="""
+[[!template id=filecontent name=etc/rc.d/ec2_init text="""
#!/bin/sh
#
-# PROVIDE: amazon-ec2
+# PROVIDE: ec2_init
# REQUIRE: NETWORKING
# BEFORE: LOGIN
$_rc_subr_loaded . /etc/rc.subr
name="ec2_init"
+rcvar=${name}
start_cmd="ec2_init"
stop_cmd=":"
@@ -185,12 +198,12 @@ ptyfs /dev/pts ptyfs rw
procfs /proc procfs rw
EOF
# EC2 startup script (if you installed it)
-if [ -f etc/rc.d/ec2-init ]; then
- chmod 755 etc/rc.d/ec2-init
+if [ -f etc/rc.d/ec2_init ]; then
+ chmod 755 etc/rc.d/ec2_init
fi
"""]]
-You can then proceed to modifying the system living under */mnt/ec2*, so it can fit your needs (adding custom binaries, packages, etc). When done, build the *NetBSD-AMI.img* ffs image, via [[!template id=man name=makefs section=8]], or **nbmakefs**, from the [toolchain](http://www.netbsd.org/docs/guide/en/chap-build.html#chap-build-tools):
+You can then proceed to modifying the system living under */mnt/ec2*, so it can fit your needs (adding custom binaries, packages, etc). When done, build the *NetBSD-AMI.img.gz* ffs image, via [[!template id=man name=makefs section=8]], or **nbmakefs**, from the [toolchain](http://www.netbsd.org/docs/guide/en/chap-build.html#chap-build-tools):
[[!template id=programlisting text="""
$ makefs -t ffs -B le -s 256m -N /mnt/ec2/etc/ -o density=32k NetBSD-AMI.img /mnt/ec2/
@@ -207,7 +220,7 @@ $ gzip -9n NetBSD-AMI.img
# Upload NetBSD to EC2
-We must now upload our NetBSD system to EC2. For that, we will have to create a minimalist EC2 instance, to which we will copy our files to construct our snapshots. For that, we will use an Amazon Linux AMI instance.
+We must now upload our NetBSD system to EC2. For that, we will have to create a minimalist EC2 instance, to which we will copy our files to construct our snapshots. We will use an Amazon Linux AMI instance.
EC2 being localized in geographical regions, you have to carefully choose the AMI identifier you want to use there. This depends on where you want to execute your instance. Amazon Linux AMI IDs are listed on [the main page](http://aws.amazon.com/amazon-linux-ami/) of the project, by regions. Choose ones backed by EBS.
@@ -215,7 +228,7 @@ The examples listed here assume that the
## Create an Amazon Linux instance
-Creating an instance straightforward. Amazon provides [different types of instances](http://aws.amazon.com/ec2/pricing/), with varying levels of billing and reliability. We will use a [*micro* instance](http://aws.amazon.com/ec2/faqs/#How_much_compute_power_do_Micro_instances_provide); its pricing is almost free.
+Creating an instance is straightforward. Amazon provides [different types of instances](http://aws.amazon.com/ec2/pricing/), with varying levels of billing and reliability. We will use a [*micro* instance](http://aws.amazon.com/ec2/faqs/#How_much_compute_power_do_Micro_instances_provide); its pricing is almost free.
[[!template id=programlisting text="""
$ ec2-run-instances ami-74f0061d -t t1.micro -z us-east-1c -k $EC2_SSH_KEYNAME
@@ -270,7 +283,7 @@ GROUP default
PERMISSION default ALLOWS tcp 22 22 FROM CIDR 0.0.0.0/0
"""]]
-We can now upload the kernel and the NetBSD disk image created earlier, *NetBSD-AMI.img*, to our instance host:
+We can now upload the kernel and the NetBSD disk image created earlier, *NetBSD-AMI.img.gz*, to our instance host:
[[!template id=programlisting text="""
# Upload kernel to Linux AMI
@@ -364,7 +377,7 @@ IMAGE ami-74d0231d
You can now start your own NetBSD instance, via:
[[!template id=programlisting text="""
-$ ec2-run-instances ami-74d0231d -t t1.micro -z us-east-1c
+$ ec2-run-instances ami-74d0231d -t t1.micro -z us-east-1c -k $EC2_SSH_KEYNAME
RESERVATION r-08218465 983624114127 default
INSTANCE i-953d72f9 ami-74d0231d pending 0 t1.micro 2011-02-18T02:05:46+0000 us-east-1c aki-4e7d9527 monitoring-disabled
*** Wait a few minutes, micro instances take time to start ***
@@ -377,10 +390,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).