HVM AMI

[Olivier Delrieu]

Dear All,

We have been using clusters of home-made, paravirtual, S3 based, F11
instances for quite some time now.

We now need to use cluster compute instances. If I am not mistaken, these
have to be HVM & EBS based.

So I am looking for a Fedora AMI that would be HVM & EBS based. I've found
the latest F19 EBS based AMI, but these are paravirtual.

If there is no such instance, is there a way:

- to convert a paravirtual instance into a HVM instance (that would be ideal
as we still need paravirtual instances)

- to build a HVM AMI from scratch (as I did years ago with F11.) ?

Many thanks,

Olivier Delrieu

[Dennis Gilmore]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

El Wed, 28 Aug 2013 18:39:44 +0200
"Olivier Delrieu"  escribió:
> Dear All,
>
> We have been using clusters of home-made, paravirtual, S3 based, F11
> instances for quite some time now.
>
> We now need to use cluster compute instances. If I am not mistaken,
> these have to be HVM & EBS based.
>
> So I am looking for a Fedora AMI that would be HVM & EBS based. I've
> found the latest F19 EBS based AMI, but these are paravirtual.
>
> If there is no such instance, is there a way:
> to convert a paravirtual instance into a HVM instance (that would
>
> be ideal as we still need paravirtual instances)
> to build a HVM AMI from scratch (as I did years ago with F11.) ?

we have not uploaded HVM amis solely because euca2ools doesnt support
it, since we have to use open tooling we can not use amazons. Garret
started on it during f19 when i asked, things failed and it was the
wrong time in the relase to mess around with it. our images should just
work as HVM images, we just need to make sure we can upload them. if
someone can verify that doing to so with euca2ools that would be
awesome.

Dennis
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v2.0.21 (GNU/Linux)
>
> iEYEARECAAYFAlIeLyAACgkQkSxm47BaWfcD+QCgoBvjGmfidGrPVIcUZmcqWRQz
> F8IAnjwLClTOAGm9VvcPGnSPBa/NBHms
> =kQTf
> -----END PGP SIGNATURE-----

[Vitaly Kuznetsov]

"Olivier Delrieu"  writes:
> Dear All,
>
> We have been using clusters of home-made, paravirtual, S3 based, F11
> instances for quite some time now.
>
> We now need to use cluster compute instances. If I am not mistaken,
> these have to be HVM & EBS based.
>
> So I am looking for a Fedora AMI that would be HVM & EBS based. I’ve
> found the latest F19 EBS based AMI, but these are paravirtual.
>
> If there is no such instance, is there a way:
> to convert a paravirtual instance into a HVM instance (that would be
>
> ideal as we still need paravirtual instances)

I can suggest sophisticated way I've used to create F18 HVM AMI for my
own (ami-eeac3187, us-east-1, feel free to use it):

1) Start any existent HVM AMI (I used RHEL)
2) Upload RAW image with fedora
3) Overwrite hard drive with Fedora's data (I don't exactly remember
but I think I was using dd)
4) Sync & reboot -f
5) Create AMI of your instance

Warning: I'm not sure AMI won't have 'RHEL' billing product attached
after all.

[Jay Greguske]

On 08/29/2013 05:19 AM, Vitaly Kuznetsov wrote:
> "Olivier Delrieu"  writes:
> > Dear All,
> >
> > We have been using clusters of home-made, paravirtual, S3 based, F11
> > instances for quite some time now.
> >
> > We now need to use cluster compute instances. If I am not mistaken,
> > these have to be HVM & EBS based.
> >
> > So I am looking for a Fedora AMI that would be HVM & EBS based. I’ve
> > found the latest F19 EBS based AMI, but these are paravirtual.
> >
> > If there is no such instance, is there a way:
> > to convert a paravirtual instance into a HVM instance (that would be
> >
> > ideal as we still need paravirtual instances)
>
> I can suggest sophisticated way I've used to create F18 HVM AMI for my
> own (ami-eeac3187, us-east-1, feel free to use it):
> Start any existent HVM AMI (I used RHEL)
> Upload RAW image with fedora
> Overwrite hard drive with Fedora's data (I don't exactly remember
>
> but I think I was using dd)
> 4) Sync & reboot -f
> 5) Create AMI of your instance
>
> Warning: I'm not sure AMI won't have 'RHEL' billing product attached
> after all.

The createAMI API call *does* maintain the billing product, so you'll
eat the RHEL cost with this method. You could try stopping the instance,
taking an EBS snapshot, and calling ec2-register (or whatever boto's
equivalent is) on that snapshot ID instead of step 4 and 5.

- Jay