Is there a blue print or some set of bugs tagged in some way to tackle? -matt
On Thu, Jan 29, 2015 at 7:01 PM, Michael Still <[email protected]> wrote: > Hi, > > 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 > problem. > > Thoughts welcome. > > Michael > > -- > Rackspace Australia > > _______________________________________________ > Foundation mailing list > [email protected] > http://lists.openstack.org/cgi-bin/mailman/listinfo/foundation >
__________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: [email protected]?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
