Annotation of wikisrc/amazon_ec2.mdwn, revision 1.42

1.1       wiki        1: [[!toc]]
                      2: 
                      3: # Introduction
                      4: 
1.21      wiki        5: This tutorial aims at showing how you can build, setup, upload and launch NetBSD under the [Amazon EC2](http://aws.amazon.com/ec2/) service. We will first give some brief explanations on how you can obtain an AWS account, and what you will need to run NetBSD under EC2. Then, at your convenience, you will be able to start with pre-made images, or roll-out your own.
1.1       wiki        6: 
1.3       wiki        7: # Subscribe to AWS (Amazon Web Services)
                      8: 
                      9: If you already have an account for [Amazon Web Services](http://aws.amazon.com/), and you are a registered user for EC2 service, you can directly jump to section [What do you need to know](#index2h2). If not, keep reading.
1.1       wiki       10: 
1.3       wiki       11: ## Quick overview
1.1       wiki       12: 
1.3       wiki       13: Before you can start playing with Amazon EC2, you have to create an account on Amazon Web Services, of which EC2, the Elastic Compute Cloud, is part. This is fairly straightforward, and done in two steps:
1.1       wiki       14: 
1.3       wiki       15: 1. you "sign-up" directly on [Amazon Web Services](http://aws.amazon.com/) home-page. This is where you enter your credentials, and confirm your AWS account registration.
                     16: 1. you sign-up to EC2 through [EC2 AWS home-page](http://aws.amazon.com/ec2/). You will be asked some more information, like a credit card (for billing), and a phone-number, for account validation.
1.1       wiki       17: 
1.16      wiki       18: ## What do you need to know?
1.1       wiki       19: 
1.3       wiki       20: EC2 uses different types of credentials. In addition to your login and password, you need an access key, a X.509 certificate (with its private key), and a pair of RSA keys, for remote SSH access.
                     21: 
                     22: These can be created through the [Security Credentials](https://aws-portal.amazon.com/gp/aws/developer/account/index.html?ie=UTF8&action=access-key) page (also accessible from the [Account](http://aws.amazon.com/account/) page):
                     23: 
                     24: 1. create the access key. Keep a secured copy of the ID and its associated secret value. These will be used by various scripts later on to perform certain EC2 actions.
                     25: 1. note down your account number (different from your access key ID!). This identifier can usually be obtained in the right top part of the page; it is a serie of numbers, separated with dashes: XXXX-XXXX-XXXX.
                     26: 1. create, or upload, a X.509 certificate, in PEM format. Keep the private key in a safe place.
1.9       wiki       27: 1. lastly, generate Amazon EC2 key pairs that will be used for SSH access. This step will be performed through the [Amazon Management Console](https://console.aws.amazon.com/ec2/home). Note down the SSH Key Pair Name you chose.
1.3       wiki       28: 
1.1       wiki       29: ### Keep your credentials!
                     30: 
1.3       wiki       31: The different credentials created above will be used in various places of EC2, and by a myriad of commands. You are advised to keep them easily accessible, while still reasonably secure regarding their access. Most EC2 tools expect them to be find through a set of environment variables.
                     32: 
1.9       wiki       33: For convenience, you could store them under a *.ec2* directory inside your *$HOME*:
1.3       wiki       34: 
                     35: [[!template id=programlisting text="""
                     36: $ ls .ec2/                                                                
                     37: cert-SOMERANDOMKEY.pem # the X.509 certificate
1.5       wiki       38: id_rsa.ec2             # private RSA SSH key
                     39: id_rsa.ec2.pub         # public RSA SSH key
1.3       wiki       40: pk-SOMERANDOMKEY.pem   # the private key associated to the certificate
                     41: """]]
                     42: 
                     43: then set the environment accordingly:
                     44: 
                     45: [[!template id=programlisting text="""
                     46: export EC2_PRIVATE_KEY=$HOME/.ec2/pk-SOMERANDOMKEY.pem
                     47: export EC2_CERT=$HOME/.ec2/cert-SOMERANDOMKEY.pem
                     48: export EC2_SSH_KEY=$HOME/.ec2/id_rsa.ec2
1.9       wiki       49: export EC2_SSH_KEYNAME=<your_ssh_key_pair_name>
1.3       wiki       50: export EC2_ACCOUNT_NUM=XXXX-XXXX-XXXX
                     51: export EC2_ACCESS_KEY=MYACCESSKEYID
                     52: export EC2_SECRET_KEY=MYSECRETACCESSKEY
                     53: """]]
                     54: 
                     55: Please note that the rest of the tutorial will assume that these variables are set.
                     56: 
1.16      wiki       57: ## Installing EC2 API tools
1.9       wiki       58: 
                     59: NetBSD provides EC2 API tools, to ease EC2 account management a little bit. The package is found inside [pkgsrc](http://www.pkgsrc.org), under [[!template id=pkg category=misc name=ec2-api-tools]].
                     60: 
                     61: [[!template id=programlisting text="""
                     62: cd /usr/pkgsrc/misc/ec2-api-tools
                     63: make ACCEPTABLE_LICENSES+=amazon-software-license install
                     64: """]]
                     65: 
                     66: Package depends on Java, so build will take some time to finish. While it builds, just continue reading.
                     67: 
1.16      wiki       68: ## EC2 vocabulary -- last notes
1.3       wiki       69: 
                     70: Before starting to play with EC2, you need to be familiar with the EC2 vocabulary used throughout this tutorial.
                     71: 
                     72: Briefly said, EC2 uses [Xen](http://www.xen.org) as virtualization solution. So, in essence, all operating systems that support Xen para-virtualization can theoretically run inside EC2, as a domU. This is the case for NetBSD; however, please note that only amd64 is currently supported. Work is on-going to support 32 bits for EC2.
                     73: 
                     74: All operating systems are run as *instances*, which are, as their name implies, the instantiation of a specific AMI, or *Amazon Machine Image*. An AMI is an image built from specific *snapshots* of *volumes*. The volumes are part of [Elastic Block Storage](http://aws.amazon.com/ebs/) (or EBS for short), which is another service offered by AWS, distinct from EC2.
1.1       wiki       75: 
1.9       wiki       76: These instances are tied to a *region* (a geographical location; typically US East, US West, Europe West, etc.). Each region has *availability zones*, which can be compared to a sub-region, each one being physically distinct from another. Regions are identified by a name, like *us-east-1*, *eu-west-1*. Same goes for availability zones, usually with the region's name as prefix: *us-east-1a*, *us-east-1b*, and so forth. Note that resources are **not** shared between zones, so if you transfer data from one zone to another, you will be charged for it.
                     77: 
1.3       wiki       78: 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.
1.1       wiki       79: 
1.23      wiki       80: # Using pre-made AMIs
                     81: 
1.34      wiki       82: The following AMIs are publicly available. You can use them to [start a NetBSD instance](#index11h2) quickly, without needing to build your image by hand.
                     83: 
                     84: <table>
                     85: <tr>
                     86:   <th>NetBSD version</th>
1.39      wiki       87:   <th>us-east-1 (Virginia)</th>
                     88:   <th>us-west-1 (N. California)</th>
                     89:   <th>eu-west-1 (Ireland)</th>
                     90:   <th>ap-southeast-1 (Singapore)</th>
                     91:   <th>ap-northeast-1 (Tokyo)</th>
1.34      wiki       92: </tr>
                     93: <tr>
1.42    ! wiki       94:   <th>NetBSD 5.1</th>
1.34      wiki       95:   <td>
                     96:       32 bits: <strong></strong><br/>
1.39      wiki       97:       64 bits: <strong>ami-06b4466f</strong>
                     98:   </td>
                     99:   <td>
                    100:       32 bits: <strong></strong><br/>
                    101:       64 bits: <strong>ami-99f7a7dc</strong>
1.34      wiki      102:   </td>
                    103:   <td>
                    104:       32 bits: <strong></strong><br/>
1.39      wiki      105:       64 bits: <strong>ami-cfa296bb</strong>
1.34      wiki      106:   </td>
                    107:   <td>
                    108:       32 bits: <strong></strong><br/>
1.39      wiki      109:       64 bits: <strong>ami-04e49a56</strong>
1.34      wiki      110:   </td>
                    111:   <td>
                    112:       32 bits: <strong></strong><br/>
1.41      wiki      113:       64 bits: <strong>ami-dc1bb0dd</strong>
1.34      wiki      114:   </td>
                    115: </tr>
                    116: <tr>
                    117:   <th>NetBSD-HEAD (5.99.45)</th>
                    118:   <td>
                    119:       32 bits: <strong></strong><br/>
                    120:       64 bits: <strong></strong>
                    121:   </td>
                    122:   <td>
                    123:       32 bits: <strong></strong><br/>
                    124:       64 bits: <strong></strong>
                    125:   </td>
                    126:   <td>
                    127:       32 bits: <strong></strong><br/>
                    128:       64 bits: <strong></strong>
                    129:   </td>
                    130:   <td>
                    131:       32 bits: <strong></strong><br/>
                    132:       64 bits: <strong></strong>
                    133:   </td>
1.39      wiki      134:   <td>
                    135:       32 bits: <strong></strong><br/>
                    136:       64 bits: <strong></strong>
                    137:   </td>
1.34      wiki      138: </tr>
                    139: </table>
1.23      wiki      140: 
1.17      wiki      141: # Build-up your NetBSD system
1.1       wiki      142: 
1.6       wiki      143: ## Fetch and build NetBSD
1.1       wiki      144: 
1.6       wiki      145: EC2 does not provide direct access to console. As a consequence, we cannot rely on it for installation, especially via [[!template id=man name=sysinst section=8]]. We must therefore build and install NetBSD in a separate directory, and configure it manually, before upload.
1.1       wiki      146: 
1.9       wiki      147: This tutorial assumes that you will build the system under */mnt/ec2*.
1.1       wiki      148: 
1.21      wiki      149: /!\Please note that you will need the [[!template id=man name=makefs section=8]] tool later in the process, so you can build a file system image that can be uploaded to Amazon EC2. You are therefore advised to perform the installation directly under a living NetBSD system, or in case your are not, to fetch the *src* tree to build the toolchain, which will contain the **nbmakefs** utility.
1.1       wiki      150: 
1.21      wiki      151: [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*:
                    152: 
                    153: [[!template id=programlisting text="""
1.23      wiki      154: cd /usr/
                    155: # grab a recent src.tgz file (use curl(1), ftp(1), wget(1), ...)
                    156: ftp -a 'http://ftp.netbsd.org/pub/NetBSD/NetBSD-current/tar_files/src.tar.gz'
                    157: # Decompress
                    158: tar -xzpf src.tar.gz
                    159: cd src
                    160: # build distribution and kernel
1.28      wiki      161: ./build.sh -O ../obj -T ../tools -D ../dest -R ../release -m amd64 -U distribution
1.23      wiki      162: ./build.sh -O ../obj -T ../tools -m amd64 kernel=XEN3_DOMU
                    163: # install distribution in /mnt/ec2
1.32      wiki      164: su root ./build.sh -O ../obj -T ../tools -D ../dest -R ../release -U -V INSTALLSETS="base etc" install=/mnt/ec2
1.21      wiki      165: """]]
1.6       wiki      166: 
1.16      wiki      167: # Configuration of your NetBSD EC2 tree
1.6       wiki      168: 
1.9       wiki      169: /!\This part assumes that you have a non-configured NetBSD system extracted under */mnt/ec2*; that is, it should have not been modified through [[!template id=man name=sysinst section=8]], nor by you.
1.6       wiki      170: 
1.9       wiki      171: Under */mnt/ec2*, edit the files to add (or modify) these lines:
1.6       wiki      172: 
                    173: [[!template id=filecontent name=etc/rc.conf text="""
                    174: rc_configured=YES
                    175: 
1.26      wiki      176: ec2_init=YES
1.6       wiki      177: sshd=YES # for remote shell access to instance
                    178: """]]
                    179: 
                    180: [[!template id=filecontent name=etc/ssh/sshd_config text="""
                    181: # Allows root to login via authentication keys
                    182: PermitRootLogin without-password
                    183: """]]
                    184: 
1.22      wiki      185: This file is needed if you want to login via the EC2 SSH key pair created previously:
1.21      wiki      186: 
1.26      wiki      187: [[!template id=filecontent name=etc/rc.d/ec2_init text="""
1.21      wiki      188: #!/bin/sh
                    189: #
1.26      wiki      190: # PROVIDE: ec2_init
1.21      wiki      191: # REQUIRE: NETWORKING
                    192: # BEFORE:  LOGIN
                    193: 
                    194: $_rc_subr_loaded . /etc/rc.subr
                    195: 
                    196: name="ec2_init"
1.26      wiki      197: rcvar=${name}
1.21      wiki      198: start_cmd="ec2_init"
                    199: stop_cmd=":"
                    200: 
1.22      wiki      201: METADATA_URL="http://169.254.169.254/latest/meta-data/"
                    202: SSH_KEY_URL="public-keys/0/openssh-key"
                    203: HOSTNAME_URL="hostname"
                    204: 
1.21      wiki      205: SSH_KEY_FILE="/root/.ssh/authorized_keys"
                    206: 
                    207: ec2_init()
                    208: {
                    209:         (
                    210:         umask 022
                    211:         # fetch the key pair from Amazon Web Services
1.22      wiki      212:         EC2_SSH_KEY=$(ftp -o - "${METADATA_URL}${SSH_KEY_URL}")
1.21      wiki      213: 
                    214:         if [ -n "$EC2_SSH_KEY" ]; then
                    215:                 # A key pair is associated with this instance, add it
                    216:                 # to root 'authorized_keys' file
                    217:                 mkdir -p $(dirname "$SSH_KEY_FILE")
1.22      wiki      218:                 touch "$SSH_KEY_FILE"
1.21      wiki      219:                 cd $(dirname "$SSH_KEY_FILE")
                    220: 
1.22      wiki      221:                 grep -q "$EC2_SSH_KEY" "$SSH_KEY_FILE"
                    222:                 if [ $? -ne 0 ]; then
                    223:                         echo "Setting EC2 SSH key pair: ${EC2_SSH_KEY##* }"
1.21      wiki      224:                         echo "$EC2_SSH_KEY" >> "$SSH_KEY_FILE"
                    225:                 fi
                    226:         fi
1.22      wiki      227: 
                    228:         # set hostname
                    229:         HOSTNAME=$(ftp -o - "${METADATA_URL}${HOSTNAME_URL}")
                    230:         echo "Setting EC2 hostname: ${HOSTNAME}"
                    231:         echo "$HOSTNAME" > /etc/myname
                    232:         hostname "$HOSTNAME"
1.21      wiki      233:         )
                    234: }
                    235: 
1.22      wiki      236: load_rc_config $name
                    237: run_rc_command "$1"
1.21      wiki      238: """]]
                    239: 
                    240: Create various files and directories:
1.6       wiki      241: 
1.8       wiki      242: [[!template id=programlisting text="""
                    243: cd /mnt/ec2
1.21      wiki      244: # Add proc and kern directories
1.22      wiki      245: mkdir grub kern proc
1.21      wiki      246: # EC2 network configuration, via DHCP
                    247: echo "dhcp" > etc/ifconfig.xennet0
                    248: # Basic fstab entries
1.8       wiki      249: cat > etc/fstab << EOF
1.6       wiki      250: /dev/xbd1a /        ffs    rw 1 1
1.22      wiki      251: /dev/xbd0a /grub    ext2fs rw 2 2
1.6       wiki      252: kernfs     /kern    kernfs rw
                    253: ptyfs      /dev/pts ptyfs  rw
                    254: procfs     /proc    procfs rw
1.8       wiki      255: EOF
1.21      wiki      256: # EC2 startup script (if you installed it)
1.26      wiki      257: if [ -f etc/rc.d/ec2_init ]; then
1.33      wiki      258:     chmod 555 etc/rc.d/ec2_init
1.21      wiki      259: fi
1.6       wiki      260: """]]
                    261: 
1.24      wiki      262: 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):
1.9       wiki      263: 
                    264: [[!template id=programlisting text="""
1.37      wiki      265: $ makefs -t ffs -B le -s 256m -N /mnt/ec2/etc/ -o density=32k /tmp/NetBSD-AMI.img /mnt/ec2/ 
1.9       wiki      266: Calculated size of `NetBSD-AMI.img': 268435456 bytes, 7345 inodes
                    267: Extent size set to 8192
                    268: NetBSD-AMI.img: 256.0MB (524288 sectors) block size 8192, fragment size 1024
                    269:         using 5 cylinder groups of 53.88MB, 6896 blks, 1728 inodes.
                    270: super-block backups (for fsck -b #) at:
                    271:      32, 110368, 220704, 331040, 441376,
                    272: Populating `NetBSD-AMI.img'
                    273: Image `NetBSD-AMI.img' complete
                    274: $ gzip -9n NetBSD-AMI.img
                    275: """]]
1.1       wiki      276: 
1.17      wiki      277: # Upload NetBSD to EC2
1.1       wiki      278: 
1.24      wiki      279: 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.
1.9       wiki      280: 
1.18      wiki      281: 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.
1.9       wiki      282: 
                    283: The examples listed here assume that the instances run in **US East**, within the **c** zone (e.g. **us-east-1c**). To have a list of EC2 regions, you can use the command **ec2-describe-regions**, and **ec2-describe-availability-zones** for availability zones.
                    284: 
1.17      wiki      285: ## Create an Amazon Linux instance
1.9       wiki      286: 
1.24      wiki      287: 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.
1.9       wiki      288: 
                    289: [[!template id=programlisting text="""
                    290: $ ec2-run-instances ami-74f0061d -t t1.micro -z us-east-1c -k $EC2_SSH_KEYNAME
                    291: RESERVATION     r-1ab61377      983624114127    default
                    292: INSTANCE        <strong>i-5babe737</strong>      ami-74f0061d                    pending &lt;your_ssh_key_pair_name&gt;  0               t1.micro        2011-02-17T23:15:04+0000        us-east-1c      aki-427d952b                    monitoring-disabled                                     ebs                                     paravirtual     xen     
                    293: """]]
                    294: 
                    295: Use the instance identifier **i-XXXXXXX** to query the instance state via **ec2-describe-instances**. It will take some time to launch:
1.6       wiki      296: 
1.9       wiki      297: [[!template id=programlisting text="""
                    298: $ sleep 5 && ec2-describe-instances i-5babe737 | grep running
                    299: $ sleep 5 && ec2-describe-instances i-5babe737 | grep running
                    300: INSTANCE        i-5babe737      ami-74f0061d    <strong>ec2-67-202-24-108.compute-1.amazonaws.com</strong>       ip-10-99-86-193.ec2.internal    running &lt;your_ssh_key_pair_name&gt;  0               t1.micro        2011-02-17T23:22:37+0000        us-east-1c      aki-427d952b                    monitoring-disabled     67.202.24.108   10.99.86.193                    ebs
                    301: """]]
1.1       wiki      302: 
1.17      wiki      303: ## Create and attach your NetBSD volumes
1.1       wiki      304: 
1.9       wiki      305: We will have to create and attach two EBS volumes:
                    306: 
                    307: 1. one to contain the Grub *menu.lst* config file, as well as the NetBSD kernel.
                    308: 1. the other one will contain the root file-system.
                    309: 
                    310: [[!template id=programlisting text="""
                    311: <strong>ec2-create-volume -s 1 -z us-east-1c</strong> # 1GiB -- will be used for Grub and kernel
                    312: VOLUME  vol-24f88d4c    1               us-east-1c      creating        2011-02-18T00:06:21+0000
                    313: <strong>ec2-create-volume -s 5 -z us-east-1c</strong> # 5GiB -- will contain the root file-system
                    314: VOLUME  vol-36f88d5e    5               us-east-1c      creating        2011-02-18T00:06:32+0000
                    315: *** Wait until both volumes are marked as "available" ***
                    316: <strong>ec2-describe-volumes vol-24f88d4c vol-36f88d5e</strong>
                    317: VOLUME  vol-36f88d5e    5               us-east-1c      available       2011-02-18T00:06:32+0000
                    318: VOLUME  vol-24f88d4c    1               us-east-1c      available       2011-02-18T00:06:21+0000
                    319: # Attach them under /dev/sdf and /dev/sdg respectively
                    320: <strong>ec2-attach-volume vol-36f88d5e -i i-5babe737 -d "/dev/sdf"</strong> # root file-system
                    321: ATTACHMENT      vol-36f88d5e    i-5babe737      /dev/sdf        attaching       2011-02-18T00:13:53+0000
                    322: <strong>ec2-attach-volume vol-24f88d4c -i i-5babe737 -d "/dev/sdg"</strong> # Grub and kernel
                    323: ATTACHMENT      vol-24f88d4c    i-5babe737      /dev/sdg        attaching       2011-02-18T00:14:02+0000
                    324: *** Wait until both volumes are "attached" ***
                    325: <strong>ec2-describe-volumes vol-24f88d4c vol-36f88d5e</strong>
                    326: VOLUME  vol-36f88d5e    5               us-east-1c      in-use  2011-02-18T00:06:32+0000
                    327: ATTACHMENT      vol-36f88d5e    i-5babe737      /dev/sdf        attached        2011-02-18T00:14:00+0000
                    328: VOLUME  vol-24f88d4c    1               us-east-1c      in-use  2011-02-18T00:06:21+0000
                    329: ATTACHMENT      vol-24f88d4c    i-5babe737      /dev/sdg        attached        2011-02-18T00:14:10+0000
                    330: """]]
                    331: 
1.16      wiki      332: ## Snapshots!
1.2       wiki      333: 
1.19      wiki      334: Before we can connect to our brand new instance, we have to allow connections on SSH port (22) through the AWS EC2 firewall:
                    335: 
                    336: [[!template id=programlisting text="""
1.35      wiki      337: $ ec2-authorize default -p 22 --region us-east-1
1.19      wiki      338: GROUP           default 
                    339: PERMISSION              default ALLOWS  tcp     22      22      FROM    CIDR    0.0.0.0/0
                    340: """]]
                    341: 
1.24      wiki      342: We can now upload the kernel and the NetBSD disk image created earlier, *NetBSD-AMI.img.gz*, to our instance host:
1.9       wiki      343: 
                    344: [[!template id=programlisting text="""
                    345: # Upload kernel to Linux AMI
1.21      wiki      346: rsync -aPv -e "ssh -i $EC2_SSH_KEY" /usr/obj/sys/arch/amd64/compile/XEN3_DOMU/netbsd \
1.9       wiki      347:         ec2-user@ec2-67-202-24-108.compute-1.amazonaws.com:
                    348: # Upload disk image
                    349: rsync -aPv -e "ssh -i $EC2_SSH_KEY" NetBSD-AMI.img.gz \
                    350:         ec2-user@ec2-67-202-24-108.compute-1.amazonaws.com:
                    351: """]]
                    352: 
1.17      wiki      353: Then, log in to the instance, via its name. We will format and mount the Grub partition, create the *menu.lst* file, then copy files to their respective partitions.
                    354: 
                    355: [[!template id=programlisting text="""
                    356: $ ec2-describe-instances i-5babe737
                    357: INSTANCE        i-5babe737      ami-74f0061d    <strong>ec2-67-202-24-108.compute-1.amazonaws.com</strong>       ip-10-99-86-193.ec2.internal    running &lt;your_ssh_key_pair_name&gt;  0               t1.micro        2011-02-17T23:22:37+0000        us-east-1c      aki-427d952b                    monitoring-disabled     67.202.24.108   10.99.86.193                    ebs
1.9       wiki      358: $ ssh -i "$EC2_SSH_KEY" ec2-user@ec2-67-202-24-108.compute-1.amazonaws.com
                    359: [...]
                    360: [ec2-user@ip-10-99-86-193 ~]$ sudo su
                    361: [root@ip-10-99-86-193 ec2-user]# mkdir /mnt/grub
                    362: [root@ip-10-99-86-193 ec2-user]# mkfs.ext2 /dev/sdg
                    363: [...]
                    364: [root@ip-10-99-86-193 ec2-user]# mount /dev/sdg /mnt/grub/
                    365: [root@ip-10-99-86-193 ec2-user]# mkdir -p /mnt/grub/boot/grub/
                    366: [root@ip-10-99-86-193 ec2-user]# cat > /mnt/grub/boot/grub/menu.lst << EOF
1.12      wiki      367: default=0
                    368: timeout=0
                    369: hiddenmenu
                    370: 
                    371: title NetBSD AMI
                    372: root (hd0)
                    373: kernel /boot/netbsd root=xbd1
1.9       wiki      374: EOF
                    375: [root@ip-10-99-86-193 ec2-user]# mv netbsd /mnt/grub/boot/
                    376: [root@ip-10-99-86-193 ec2-user]# umount /dev/sdg
                    377: [root@ip-10-99-86-193 ec2-user]# gunzip < NetBSD-AMI.img.gz | dd of=/dev/sdf bs=32k
1.10      wiki      378: [root@ip-10-99-86-193 ec2-user]# sync
1.9       wiki      379: """]]
                    380: 
1.16      wiki      381: ## Shutdown the Linux instance
1.1       wiki      382: 
1.10      wiki      383: We now have to detach volumes, snapshot them, then we shutdown the Linux instance.
                    384: 
                    385: [[!template id=programlisting text="""
                    386: # ec2-detach-volume vol-36f88d5e
                    387: ATTACHMENT      vol-36f88d5e    i-5babe737      /dev/sdf        detaching       2011-02-18T00:14:00+0000
                    388: # ec2-detach-volume vol-24f88d4c
                    389: ATTACHMENT      vol-24f88d4c    i-5babe737      /dev/sdg        detaching       2011-02-18T00:14:10+0000
                    390: # ec2-create-snapshot vol-36f88d5e
                    391: SNAPSHOT        <strong>snap-deef2bb2</strong>   vol-36f88d5e    pending 2011-02-18T01:17:59+0000                983624114127    5
                    392: # ec2-create-snapshot vol-24f88d4c
                    393: SNAPSHOT        <strong>snap-8aef2be6</strong>   vol-24f88d4c    pending 2011-02-18T01:18:10+0000                983624114127    1
                    394: # ec2-terminate-instances i-5babe737
                    395: INSTANCE        i-5babe737      running shutting-down
                    396: """]]
                    397: 
1.16      wiki      398: # Playing with your first NetBSD instance
                    399: 
1.6       wiki      400: ## Create your first NetBSD AMI
1.1       wiki      401: 
1.10      wiki      402: An AMI requires multiples components to be registered: the snapshots IDs we made in the previous chapter, as well as a specific AKI: the one that can chain-load Xenified kernels through PyGrub.
                    403: 
1.18      wiki      404: /!\ AKIs are entitled to the same conditions as AMIs: their IDs are region-specific. So choose one carefully, or you will not be able to launch your NetBSD instance later!
1.10      wiki      405: 
                    406: The list of AKIs that suits our situation can be obtained with the following command:
                    407: 
                    408: [[!template id=programlisting text="""
                    409: # Obtain all kernel images (AKI) for region US East, for which manifest location contains pv-grub (for PyGrub)
                    410: # ec2-describe-images -a --region=us-east-1 -F image-type=kernel -F manifest-location=*pv-grub*
                    411: IMAGE   aki-407d9529    ec2-public-images/pv-grub-hd0-V1.01-i386.gz.manifest.xml        amazon  available       public          i386    kernel                          instance-store  paravirtual     xen
1.15      wiki      412: <strong>IMAGE   aki-427d952b    ec2-public-images/pv-grub-hd0-V1.01-x86_64.gz.manifest.xml      amazon  available       public          x86_64  kernel                          instance-store  paravirtual     xen</strong>
1.10      wiki      413: IMAGE   aki-4c7d9525    ec2-public-images/pv-grub-hd00-V1.01-i386.gz.manifest.xml       amazon  available       public          i386    kernel                          instance-store  paravirtual     xen
1.15      wiki      414: IMAGE   aki-4e7d9527    ec2-public-images/pv-grub-hd00-V1.01-x86_64.gz.manifest.xml     amazon  available       public          x86_64  kernel                          instance-store  paravirtual     xen
1.10      wiki      415: """]]
                    416: 
1.15      wiki      417: Pick the one with the correct architecture (x86_64 here). **hd0** are for AMIs where the snapshot contains no partition (where the volume is itself the whole partition), while **hd00** are for snapshots partitioned in a classical way (via MBR). Choose **hd0** AKIs. In this case, that will be **aki-427d952b**.
1.13      wiki      418: 
                    419: We can proceed to the creation of our AMI, with:
1.10      wiki      420: 
1.14      wiki      421: 1. */dev/sda1* as Grub partition (*/dev/sdg*, snapshot **snap-8aef2be6** of volume **vol-24f88d4c**)
                    422: 1. */dev/sda2* as root file-system (*/dev/sdf*, snapshot **snap-deef2bb2** of volume **vol-36f88d5e**)
1.10      wiki      423: 
                    424: [[!template id=programlisting text="""
1.20      wiki      425: $ ec2-register -a x86_64 --kernel aki-427d952b --region us-east-1 \
1.10      wiki      426:     -b "/dev/sda1=snap-8aef2be6" -b "/dev/sda2=snap-deef2bb2" -n "NetBSD-x86_64-current" \
                    427:     -d "&lt;add your own description here&gt;
1.11      wiki      428: IMAGE   <strong>ami-74d0231d</strong>
1.10      wiki      429: """]]
                    430: 
1.16      wiki      431: ## Launch your first instance
1.1       wiki      432: 
1.10      wiki      433: You can now start your own NetBSD instance, via:
                    434: 
                    435: [[!template id=programlisting text="""
1.27      wiki      436: $ ec2-run-instances ami-74d0231d -t t1.micro -z us-east-1c -k $EC2_SSH_KEYNAME
1.10      wiki      437: RESERVATION     r-08218465      983624114127    default
                    438: INSTANCE        <strong>i-953d72f9</strong>      ami-74d0231d                    pending         0               t1.micro        2011-02-18T02:05:46+0000        us-east-1c      aki-4e7d9527                    monitoring-disabled
1.11      wiki      439: *** Wait a few minutes, micro instances take time to start ***
                    440: # Query console output for your new instance
1.10      wiki      441: $ ec2-get-console-output i-953d72f9
1.15      wiki      442: Copyright (c) 1996, 1997, 1998, 1999, 2000, 2001, 2002, 2003, 2004, 2005,
                    443:     2006, 2007, 2008, 2009, 2010, 2011
                    444:     The NetBSD Foundation, Inc.  All rights reserved.
                    445: Copyright (c) 1982, 1986, 1989, 1991, 1993
                    446:     The Regents of the University of California.  All rights reserved.
                    447: 
                    448: NetBSD 5.99.45 (XEN3_DOMU) #9: Wed Feb 16 21:14:49 CET 2011
1.10      wiki      449: [...]
1.23      wiki      450: NetBSD/amd64 (ip-10-112-58-223.ec2.internal) (console)
                    451: 
                    452: login: 
1.10      wiki      453: """]]
                    454: 
1.15      wiki      455: ## Connect to your NetBSD instance
1.1       wiki      456: 
1.23      wiki      457: Connection is similar to the one you used for the Amazon Linux instance, except that you login as "root" instead of "ec2-user":
                    458: 
                    459: [[!template id=programlisting text="""
                    460: $ ec2-describe-instances i-953d72f9
                    461: RESERVATION     r-da8021b7      983624114127    default
                    462: INSTANCE        i-953d72f9      ami-74d0231d    <strong>ec2-50-16-3-55.compute-1.amazonaws.com</strong>  ip-10-112-58-223.ec2.internal   running &lt;your_ssh_key_pair_name&gt;  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     
                    463: BLOCKDEVICE     /dev/sda1       vol-ec3c4a84    2011-02-19T04:01:31.000Z        
                    464: BLOCKDEVICE     /dev/sda2       vol-ee3c4a86    2011-02-19T04:01:31.000Z        
                    465: $ ssh -i "$EC2_SSH_KEY" root@ec2-50-16-3-55.compute-1.amazonaws.com
                    466: The authenticity of host 'ec2-50-16-3-55.compute-1.amazonaws.com (50.16.3.55)' can't be established.
                    467: [...]
                    468: Thank you for helping us test and improve NetBSD.
                    469: 
                    470: Terminal type is xterm.
                    471: We recommend that you create a non-root account and use su(1) for root access.
                    472: ip-10-112-58-223# uname -a
                    473: 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
                    474: ip-10-112-58-223# 
                    475: """]]
                    476: 
                    477: Done!
                    478: 
1.1       wiki      479: ## And now?
1.23      wiki      480: 
                    481: 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 :)
                    482: 
                    483: 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).

CVSweb for NetBSD wikisrc <wikimaster@NetBSD.org> software: FreeBSD-CVSweb