On 03/10/15 21:59, Andrew Stuart wrote:
Colin Percival created his own EC2 import volume for importing FreeBSD images.
http://www.daemonology.net/blog/2014-11-26-missing-importvolume-documentation.html
It uploads a volume to EC2, takes a snapshot and registers the snapshot as an
AMI - these are the essential steps required to convert for example a local Xen
HVM image to run as an EC2 HVM image.
Thanks for investigating, but can you explicitly state the relationship
between the tool you discovered and the Rumprun unikernel? I can make
various semi-educated guesses, but for example people finding your mail
from the archives via websearch might not be able to do the same.
namely,
to cast the spell:
assuming your Xen HVM image is hvmbootimage.img
create an S3 named myimportbucketname (S3 bucket names must be unique so you’ll
need your own bucket name)
bsdec2-image-upload/bsdec2-image-upload hvmbootimage.img hvmbootimage.img
hvmbootimage.img us-west-1 myimportbucketname awskeys.txt
Is hvmbootimage.img something created by our build/config procedures,
and if yes, how?
thanks
