For those who use Amazon EC2 service and were anxious about having XtraDB ready to launch there is a good news.
We created a public AMI (Amazon Machine Image) with XtraDB release 8 installed on CentOS 5.3.
How to use it.
First make sure it is avaiable.
|
1 2 3 |
$ ec2-describe-images ami-4701e22e IMAGE  ami-4701e22e   xtradb/centos-5.3-x86_64.fs.manifest.xml       834362721059   available      public         x86_64 machine $ |
Run it. It is built for x86_64 plaform, so allowed types are m1.large, m1.xlarge and c1.xlarge
|
1 2 3 |
$ ec2-run-instances ami-4701e22e -t m1.large RESERVATION r-46b3432e 834362721059 default INSTANCE i-ecc74084 ami-4701e22e pending 0 m1.large 2009-10-25T18:31:06+0000 us-east-1c |
Wait till the instance starts
|
1 2 3 4 |
$ ec2-describe-instances i-ecc74084 RESERVATION r-46b3432e 834362721059 default INSTANCE i-ecc74084 ami-4701e22e ec2-75-101-203-143.compute-1.amazonaws.com domU-12-31-39-0A-26-22.compute-1.internal running 0 m1.large 2009-10-25T18:31:06+0000 us-east-1c |
Now it is up and ready.
Is the my.cnf setup optimally for the EC2 instances?
Andrew, it will need workload-specific and image-size-specific configuration.
i also used the XtraDB in my company products! High performace! Thanks
Andrew,
The mentioned image has default mysql options. However in future there will be images tuned for the best performance for specific workloads/instance types.
Hi Guys,
Just tried so take a look at your AMI, but it asks for a root password, so i’m not sure if the AMI is made correctly.
herse’s what i did:
wart$ ec2-run-instances ami-4701e22e -t m1.large -k gsg-keypair
RESERVATION r-30d72d58 701859409573 default
INSTANCE i-04a9226c ami-4701e22e pending gsg-keypair 0 m1.large 2009-11-02T09:32:02+0000 us-east-1d monitoring-disabled
wart$ ec2-describe-instances i-04a9226c
RESERVATION r-30d72d58 701859409573 default
INSTANCE i-04a9226c ami-4701e22e ec2-174-129-76-91.compute-1.amazonaws.com ip-10-242-71-79.ec2.internal running gsg-keypair 0 m1.large 2009-11-02T09:32:02+0000 us-east-1d monitoring-disabled 174.129.76.91 10.242.71.79
wart$ ssh -i gsg-keypair [email protected]
[email protected]‘s password:
I’m seeing the same issue as wart. Seems that there’s something odd with your keypairs on the AMI.
Does this AMI still available ? Thanks !
wow great…..the AMI filesystem is compressed, encrypted, signed, split into a series of 10MB chunks and uploaded into Amazon S3 for storage. An XML manifest file stores information about the AMI, including name, version, architecture, default kernel id, decryption key and digests for all of the filesystem chunks…
Same problem here as wart. Has this image been fixed? It asks for a root password. Thanks!