Open Stack

Michael Still wrote:
> 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?

In the user survey from October 2013, about 30% of respondents claim to
have the EC2 API enabled.

It's not the first time we make the sad observation that noone actually
cares enough about the EC2 API to invest the one FTE that would be
required to maintain it in good shape. That session is up at every
Design Summit, but every time we get various resource pledges that never
pan out.

Now that we have raised the QA bar for hypervisors, plugins and backend
drivers to stay in mainline code, it's only a matter of time until the
EC2 API is held to the same standards... I think it's important that we
keep that API though, so I really hope someone will step up soon.

-- 
Thierry Carrez (ttx)