[Openstack-operators] Deprecation of in tree EC2 API in Nova for Kilo release
mikal at stillhq.com
Wed Jan 28 21:39:31 UTC 2015
On Wed, Jan 28, 2015 at 12:38 PM, Tim Bell <Tim.Bell at cern.ch> wrote:
> There are currently 35% of openstack clouds from the survey using this feature. I would therefore propose that this be reviewed with the operators in detail before a rapid depreciation is performed. To the best of my knowledge, the new package is not yet in use in production.
The patch itself doesn't actually propose a rapid removal. Its marked
as being "removed in a future release". The reality is that this code
has been largely abandoned for a long time... We're just trying to be
more honest with signalling that to users. So I think we're on the
same page here.
> At CERN, we are highly dependent on this function and while it does not provide 100% compatibility, it works pretty well.
What happens when CERN upgrades to a modern boto and auth doesn't
work? That's been known for at least a week or two and no one has
stepped up to fix it.
> I would therefore propose that the new EC2 API modules are validated in production and at scale before depreciating the existing functions. I think validating, packaging and deploying to a reasonable number of clouds and reviewing it with the operators is a viable target for Kilo. This can then be reviewed in one of the joint developer/operator sessions for feasibility.
Right. That's a thing we need operators to do for us. That's why the
original email was cc'ed to the operators list. Marking the feature as
deprecated is our way of asking operators to actually test the
alternative and start reporting bugs for the problems they find.
>> -----Original Message-----
>> From: Christian Berendt [mailto:christian at berendt.io]
>> Sent: 28 January 2015 21:29
>> To: openstack-operators at lists.openstack.org
>> Subject: Re: [Openstack-operators] Deprecation of in tree EC2 API in Nova for
>> Kilo release
>> On 01/28/2015 08:56 PM, Sean Dague wrote:
>> > Comments are welcomed, but we've attempted to get more people engaged
>> > to address these issues over the last 18 months, and never really had
>> > anyone step up. Without some real maintainers of this code in Nova
>> > (and tests somewhere in the community) it's really no longer viable.
>> I think it is the right decision to remove the EC2 API in Nova.
>> OpenStack-operators mailing list
>> OpenStack-operators at lists.openstack.org
> OpenStack-operators mailing list
> OpenStack-operators at lists.openstack.org
More information about the OpenStack-operators