[OpenStack Foundation] [openstack-dev] Finding people to work on the EC2 API in Nova
alevine at cloudscaling.com
Fri Jan 30 20:07:32 UTC 2015
We sure we can fix it and we know how. The only problem is to somehow
get a hand with reviewing and approvals speed? Is there any remedy for
this? I've asked Michael already above in the thread, but I don't
presume that it's possible even to allow one of us to become core
reviewer for EC2 part of the nova? Or is it?
On 1/30/15 10:57 PM, Tim Bell wrote:
> Many thanks for the constructive approach. I've added an item to the
> list for the Ops meetup in March to see who would be interested to help.
> As discussed on the change, it is likely that there would need to be
> some additional Nova APIs added to support the full EC2 semantics.
> Thus, there would need to support from the Nova team to enable these
> additional functions. Having tables in the EC2 layer which get out of
> sync with those in the Nova layer would be a significant problem in
> I think this would merit a good slot in the Vancouver design sessions
> so we can also discuss documentation, migration, packaging,
> configuration management, scaling, HA, etc.
> *From:*matt [mailto:matt at nycresistor.com]
> *Sent:* 30 January 2015 20:44
> *To:* Alexandre Levine
> *Cc:* foundation at lists.openstack.org; OpenStack Development Mailing
> List (not for usage questions)
> *Subject:* Re: [OpenStack Foundation] [openstack-dev] Finding people
> to work on the EC2 API in Nova
> +1 cloudscaling has been pretty involved in ec2 support for openstack
> for a long while now.
> On Fri, Jan 30, 2015 at 2:27 PM, Alexandre Levine
> <alevine at cloudscaling.com <mailto:alevine at cloudscaling.com>> wrote:
> Our team can take the effort. We're the ones doing the stackforge
> EC2 API and we can maintain the nova's EC2 in acceptable state for
> the time being as well.
> If you can give us any permissions and leverage to not just
> contribute fixes and tests but also have a say in approval of
> those (maybe to just one of us) then it'll be fast. Otherwise
> it'll happen in due time but our previous attempts to contribute
> some fixes for EC2 API in nova took usually more than half a year
> to get through.
> Best regards
> Alex Levine
> On 1/30/15 3:01 AM, Michael Still 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
> details here -- you can read the thread on openstack-dev for
> However, we got here because no one is maintaining the code in
> 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
> 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
> 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.
> Foundation mailing list
> Foundation at lists.openstack.org <mailto:Foundation at lists.openstack.org>
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Foundation