...
* setup working directory for the bundle which will be excluded from the bundle
sudo mkdir /image
* Bundle local VM , will take 1-2 hours ..., you may need to specify the kernel & ramdisk (values below worked in November 2010) also the 64-bit VM is generated below, use -r i386 for the 32-bit image.
>sudo euca-bundle-vol -c $EC2_CERT -k $EC2_PRIVATE_KEY -u $EC2_USER_ID --ec2cert $EUCALYPTUS_CERT -d /image -e /image --no-inherit -r x86_64 --kernel eki-AEC117E0 --ramdisk eri-175C1933
OUTPUT:
....
Part: image.part.245
Part: image.part.246
Part: image.part.247
Generating manifest
* uplad bundle to Eucalyptus with name 'star-vm-SL10c-ubuntu-i386', will take many hours depending on connection & total size
> sudo euca-upload-bundle -a $EC2_ACCESS_KEY -s $EC2_SECRET_KEY --url $S3_URL --ec2cert $EUCALYPTUS_CERT -m /image/image.manifest.xml -b star-vm-SL10c-ubuntu-64bit -m /image/image.manifest.xml
OUTPUT:
....
Uploading part: image.part.246
Uploading part: image.part.247
Uploaded image as star-vm-SL10c-ubuntu-i386/image.manifest.xml
* register 'star-vm-SL10c-ubuntu-i386' with Eucalyptus
> euca-register -a $EC2_ACCESS_KEY -s $EC2_SECRET_KEY --url $EC2_URL star-vm-SL10c-ubuntu-64bit/image.manifest.xml
OUTPUT:
{_}IMAGE emi-344D1244{_}
Potential problems:
- synchronization of local clock, can be fixed with command
> sudo ntpdate hickory.nersc.gov - check check if key-pair generation succeded, list content of 'balewski-euca.private' if it does not look like a valid key and you can't find the old key you can remove the old public key from Eucalyptus using command *euca-delete-keypair
...
* query existing images:
> euca-describe-images | grep emi | grep -i ubuntu
OUTPUT:
IMAGE emi-39DF160F ubuntu-image-bucket/ubuntu.9-04.x86-64.img.manifest.xml admin available public x86_64 machine
...
* launch an instance
> euca-run-instances -k balewski-euca emi-39DF160F
OUTPUT:
RESERVATION r-470107EF balewski balewski-default
INSTANCE i-31D50646 emi-39DF160F 0.0.0.0 0.0.0.0 pending balewski-euca 2010-10-22T16:05:53.609Z eki-AEC117E0 eri-175C1933
* check if instance is running (after few minutes, depends on the size of the image)
> euca-describe-instances i-31D50646
OUTPUT:
RESERVATION r-470107EF balewski default
INSTANCE i-31D50646 emi-39DF160F 128.55.56.51 192.168.4.2 running balewski-euca 0 m1.small 2010-10-22T16:05:53.609Z euca eki-AEC117E0 eri-175C1933
* Set security group prior to connecting to the instance (see 'Potential problems' above - private key may be wrong.)
> euca-authorize -P tcp -p 22 -s 0.0.0.0/0 default
OUTPUT:
GROUP default
PERMISSION default ALLOWS tcp 22 22 FROM CIDR 0.0.0.0/0
* Connect to the instance
> ssh -i ./balewski-euca.private root@128.55.56.57
* Terminate instance
> euca-terminate-instances i-31D50646
OUTPUT:
INSTANCE i-31D50646
after ~10 seconds the same command results with nothing