Open Stack

> -----Original Message-----
> From: Michael Still [mailto:mikal at stillhq.com]
> Sent: Thursday, April 24, 2014 8:10 AM
> To: OpenStack Development Mailing List (not for usage questions)
> Subject: Re: [openstack-dev] [nova] [qa] EC2 status and call for assistance
> 
> On Thu, Apr 24, 2014 at 7:39 AM, Joe Gordon <joe.gordon0 at gmail.com> wrote:
> 
> > So no one is seriously discussing moving EC2 out of nova right now. The
> > issue is that the EC2 code and tempest tests aren't being maintained are
> > slowly code rotting. The goal of this thread is to get some volunteers to
> > work on EC2.
> >
> > "I'd like to see if there are any more people interested in keeping these
> > interfaces functional (by contributing both on the nova and tempest
> > sides). If so, great!"
> 
> Sure, but if this code continues being ignored, then I don't see how
> we have a choice long term.
> 
> So a few questions:
> 
>  - who currently ships a private cloud with EC2 enabled?
>  - who has a public cloud with EC2 enabled?
> 
> These seem like the obvious places to talk to people about helping us
> get this code maintained before we're forced to drop it. Unfortunately
> we can't compel people to work on things, but we can make it in their
> best interests.
> 
> A followup question as well -- there's a proposal to implement the
> Nova v2 API on top of the v3 API. Is something similar possible with
> EC2? Most of the details of EC2 have fallen out of my brain, but I'd
> be very interested in if such a thing is possible.

The difference between v2 and v3 is not so big, and it is easy to
implement v2 API on top of v3 API. However EC2 API is very different
from v2/v3 API, so I think it is difficult to implement EC2 API on top
of v3 API.

Ex) Create a keypair
  EC2[1]:
    https://ec2.amazonaws.com/?Action=CreateKeyPair
    &KeyName=my-key-pair
    &AUTHPARAMS

  v2[2]:
    http://{nova-api}/v2/​{tenant_id}​/os-keypairs
    {
        "keypair": {
            "name": "keypair-dab428fe-6186-4a14-b3de-92131f76cd39",
            "public_key": "ssh-rsa AAAAB3Nza[..]== Generated by Nova"
        }
    }

I feel it would be nice to keep current EC2 implementation if necessary.


Thanks
Ken'ichi Ohmichi
---
[1]: http://docs.aws.amazon.com/AWSEC2/latest/APIReference/ApiReference-query-CreateKeyPair.html
[2]: http://api.openstack.org/api-ref-compute-v2-ext.html