Cannot deliver Fedora 15 appliance to EC2 with EBS or S3 plugins (eu-west-1 availability zone)
unknow Jun 7, 2011 4:08 AMHi,
I've recently been trying BoxGrinder because I need to create a new Fedora-powered server on Amazon EC2 for each new release of Fedora. I'm currently trying to create an appliance for Fedora 15.
Although the appliance building process seems to work with no errors, I was unable to deliver the appliance to the cloud. Note that I need the appliance to run in the eu-west availability zone.
Can anyone please help me solve this problem or direct me to relevant documentation?
EBS delivery plugin
I have successfully launched a meta appliance in the us-east zone and created an EBS-based AMI in that zone. However, if I try to specify the availability_zone parameter in the configuration, I get the following error:
F, [2011-06-05T10:45:45.642256 #19926] FATAL -- : RuntimeError: You selected eu-west-1b avaibility zone, but your instance is running in us-east-1d zone. Please change avaibility zone in plugin configuration file to us-east-1d (see http://boxgrinder.org/tutorials/boxgrinder-build-plugins/#EBS_Delivery_Plugin) or use another instance in eu-west-1b zone to create your EBS AMI.
I'm not sure I understand the use of this parameter if it can't be different than the availability zone the instance is running in.
There are no meta appliances provided for other zones either. Is there an easy way to create an EBS-backed AMI in another zone that us-east?
S3 delivery plugin
Since I've already converted instance-store AMIs to EBS-backed AMIs, I also tried to deliver the appliance with the S3 plugin. However, I always get this error:
I, [2011-06-05T10:56:14.471182 #20044] INFO -- : Image converted to EC2 format.
T, [2011-06-05T10:56:14.471416 #20044] TRACE -- : Moving 'build/appliances/x86_64/fedora/15/my_server-f15/ec2-plugin/tmp/my_server-f15.ec2' deliverable to target destination 'build/appliances/x86_64/fedora/15/my_server-f15/ec2-plugin/my_server-f15.ec2'...
D, [2011-06-05T10:56:14.472618 #20044] DEBUG -- : Platform plugin executed.
T, [2011-06-05T10:56:14.474719 #20044] TRACE -- : Checking if 'my_server-f15/fedora/15/2.0/x86_64/my_server-f15.ec2.manifest.xml' path exists in my_server...
T, [2011-06-05T10:56:14.474926 #20044] TRACE -- : Path doesn't exist!
F, [2011-06-05T10:56:14.475447 #20044] FATAL -- : Errno::ENOENT: No such file or directory - build/appliances/x86_64/fedora/15/my_server-f15/s3-plugin/ami/my_server-f15.ec2.manifest.xml
The problem seemed similar to this post (http://community.jboss.org/message/558438), but trying the proposed solution did not change anything. I have ensured that the AMI tools are installed and working properly, but the error remains.
My appliance definition file
name: my_server
summary: my_server AMI with Fedora 15
version: 2
os:
name: fedora
version: 15
hardware:
partitions:
"/":
size: 10
My .boxgrinder/config file
plugins:
s3:
access_key: YYYY # (required)
secret_access_key: YYYY # (required)
bucket: my_bucket # (required)
account_number: YYYY # (required)
cert_file: /root/.ec2/cert-YYYY.pem # required only for ami type
key_file: /root/.ec2/pk-YYYY.pem # required only for ami type
region: eu-west-1b
availability_zone: eu-west-1b
ebs:
access_key: YYYY # (required)
secret_access_key: YYYY # (required)
account_number: YYYY # (required)
availability_zone: eu-west-1b
region: eu-west-1b
Title updated by unknow