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 the
On 31 January 2015 at 06:18, Eric Windisch e...@windisch.us 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
On Wed, Jan 28, 2015 at 01:39:31PM -0800, Michael Still wrote:
On Wed, Jan 28, 2015 at 12:38 PM, Tim Bell tim.b...@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
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.
On Thu, Jan 29, 2015 at 4:46 AM, Saju M sajup...@gmail.com wrote:
I think, new EC2 API also uses EC2
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
On Thu, Jan 29, 2015 at 1:59 AM, Belmiro Moreira
moreira.belmiro.email.li...@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.
On Thu, Jan 29, 2015 at 2:37 AM, Daniel P. Berrange berra...@redhat.com 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 tim.b...@cern.ch wrote:
There are currently 35% of openstack clouds from the survey using
this feature. I
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
On Wed, Jan 28, 2015 at 12:38 PM, Tim Bell tim.b...@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
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
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 new
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.b...@cern.ch wrote:
There are currently 35% of openstack
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
13 matches
Mail list logo
