On 1/29/2015 7:42 PM, Michael Still wrote:
On Thu, Jan 29, 2015 at 5:15 PM, Michael Still <mi...@stillhq.com> wrote:
There is an ec2 bug tag in launchpad. I would link to it except I am writing
this offline. I will fix that later today.

Ok, now that the 40 seater turbo prop has landed, here we go:


However I think what we've shown is that moving this code out of nova is the
future. I would like to see someone come up with a plan to transition users
to the stackforge project. That seems the best way forward at this point.


On 30 Jan 2015 11:11 am, "matt" <m...@nycresistor.com> wrote:

Is there a blue print or some set of bugs tagged in some way to tackle?


On Thu, Jan 29, 2015 at 7:01 PM, Michael Still <mi...@stillhq.com> wrote:


as you might have read on openstack-dev, the Nova EC2 API
implementation is in a pretty sad state. I wont repeat all of those
details here -- you can read the thread on openstack-dev for detail.

However, we got here because no one is maintaining the code in Nova
for the EC2 API. This is despite repeated calls over the last 18
months (at least).

So, does the Foundation have a role here? The Nova team has failed to
find someone to help us resolve these issues. Can the board perhaps
find resources as the representatives of some of the largest
contributors to OpenStack? Could the Foundation employ someone to help
us our here?

I suspect the correct plan is to work on getting the stackforge
replacement finished, and ensuring that it is feature compatible with
the Nova implementation. However, I don't want to preempt the design
process -- there might be other ways forward here.

I feel that a continued discussion which just repeats the last 18
months wont actually fix the situation -- its time to "break out" of
that mode and find other ways to try and get someone working on this

Thoughts welcome.


Rackspace Australia

Foundation mailing list

Also the spec here:




Matt Riedemann

OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe

Reply via email to