Open Stack

On Thu, Jan 29, 2015 at 1:59 AM, Belmiro Moreira <
moreira.belmiro.email.lists at gmail.com> wrote:

> I completely agree with Tim and Daniel.
> Also, deprecating nova EC2 API without having the community engaged with
> the new stackforge “EC2 standalone service” can lead to a no EC2 support at
> all.
>

Deprecation is not removal though. What we're trying to signal here is that
we think the stackforge project is the way forward in the future. The Nova
EC2 implementation wont be removed until it is demonstrated that it
presents a viable alternative. The purpose of the initial email was to
encourage people to take a look at the stackforge implementation (which it
has achieved), as well as ensuring we are honest with our users about the
quality of the implementation in the Nova code base.

Cheers,
Michael



> On Thu, Jan 29, 2015 at 4:46 AM, Saju M <sajuptpm at gmail.com> wrote:
>
>> I think, new EC2 API also uses EC2 API in the nova for basic operations.
>> Only the new features like VPC is implemented in new EC2 API. So I think we
>> should move it first.
>> On Jan 29, 2015 5:42 AM, "Alex Baretto" <shakamunyi at gmail.com> wrote:
>>
>>> Hi Tim,
>>>
>>> Would you be able to share use cases/experiences with EC2 API to help
>>> with support for your proposals? I am also familiar with multiple OpenStack
>>> clouds using the EC2 API.
>>>
>>> Best,
>>>
>>> -Alex.
>>>
>>> On 28 January 2015 at 12:38, 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.
>>>>
>>>> At CERN, we are highly dependent on this function and while it does not
>>>> provide 100% compatibility, it works pretty well.
>>>>
>>>> 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.
>>>>
>>>> Tim
>>>> > -----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.
>>>> >
>>>> > Christian.
>>>> >
>>>> > _______________________________________________
>>>> > OpenStack-operators mailing list
>>>> > OpenStack-operators at lists.openstack.org
>>>> >
>>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
>>>>
>>>> _______________________________________________
>>>> OpenStack-operators mailing list
>>>> OpenStack-operators at lists.openstack.org
>>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
>>>>
>>>
>>>
>>>
>>> --
>>> Alex Barreto
>>> about.me/shakamunyi
>>> [image: Alex Barreto on about.me]
>>>   <http://about.me/shakamunyi>
>>> <http://about.me/shakamunyi>
>>> (408) 442-4181 o | (415) 307-8594 m <http://about.me/shakamunyi>
>>> <http://about.me/shakamunyi>shakamunyi at gmail.com
>>>
>>>
>>> _______________________________________________
>>> OpenStack-operators mailing list
>>> OpenStack-operators at lists.openstack.org
>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
>>>
>>>
>> _______________________________________________
>> OpenStack-operators mailing list
>> OpenStack-operators at lists.openstack.org
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
>>
>>
>
> _______________________________________________
> OpenStack-operators mailing list
> OpenStack-operators at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
>
>


-- 
Rackspace Australia
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-operators/attachments/20150129/d977556b/attachment.html>