>
>
> Quite seriously: open source projects are absolutely developed for
> their users. Thats the entire proposition of both free and open source
> software and licenses: that users should have the freedom to modify
> things to meet their needs, *and* that users will be building what
> they need in
On 31 January 2015 at 06:18, Eric Windisch wrote:
>>
>> That's a failing of the Nova team that must be addressed. As maintainers
>> it is our job to produce software that meets the needs of our users. We
>> have 35% of users reporting they use this EC2 code, so fixing any problems
>> should be a h
>
>
> That's a failing of the Nova team that must be addressed. As maintainers
> it is our job to produce software that meets the needs of our users. We
> have 35% of users reporting they use this EC2 code, so fixing any problems
> should be a high priority item & these bugs considered release bloc
iewing 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: C
On Thu, Jan 29, 2015 at 2:37 AM, Daniel P. Berrange wrote:
> On Wed, Jan 28, 2015 at 01:39:31PM -0800, Michael Still wrote:
>> On Wed, Jan 28, 2015 at 12:38 PM, Tim Bell wrote:
>> > There are currently 35% of openstack clouds from the survey using
>> > this feature. I would therefore propose that
On 01/28/2015 09:56 PM, Sean Dague wrote:
The following review for Kilo deprecates the EC2 API in Nova -
https://review.openstack.org/#/c/150929/
There are a number of reasons for this. The EC2 API has been slowly
rotting in the Nova tree, never was highly tested, implements a
substantially olde
On Wed, Jan 28, 2015 at 01:39:31PM -0800, Michael Still wrote:
> On Wed, Jan 28, 2015 at 12:38 PM, Tim Bell 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
>>
>>> Tim
>>> > -Original Message-
>>> > From: Christian Berendt [mailto:christ...@berendt.io]
>>> > Sent: 28 January 2015 21:29
>>> > To: openstack-operators@lists.openstack.org
>>> > Subject: Re: [Openstack-operators] Dep
; From: Christian Berendt [mailto:christ...@berendt.io]
>> > Sent: 28 January 2015 21:29
>> > To: openstack-operators@lists.openstack.org
>> > Subject: Re: [Openstack-operators] Deprecation of in tree EC2 API in
>> Nova for
>> > Kilo release
>>
t; > Sent: 28 January 2015 21:29
> > To: openstack-operators@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 ar
On 01/28/2015 09:38 PM, Tim Bell wrote:
> 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 opera
anuary 2015 21:29
>> To: openstack-operators@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 attem
On Wed, Jan 28, 2015 at 08:38:02PM +, Tim Bell 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 n
y 2015 21:29
> To: openstack-operators@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 engag
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'
The following review for Kilo deprecates the EC2 API in Nova -
https://review.openstack.org/#/c/150929/
There are a number of reasons for this. The EC2 API has been slowly
rotting in the Nova tree, never was highly tested, implements a
substantially older version of what AWS has, and currently can
16 matches
Mail list logo
