On 1/8/2015 1:28 PM, Matt Riedemann wrote:
On 4/25/2014 4:13 AM, Alexandre Levine wrote:
Joe,
In regard to your first question - yes we'll be going in this direction
very soon. It's being discussed with Randy now.
As for the second question - we'd love to participate in fixing it (in
fact
On 4/25/2014 4:13 AM, Alexandre Levine wrote:
Joe,
In regard to your first question - yes we'll be going in this direction
very soon. It's being discussed with Randy now.
As for the second question - we'd love to participate in fixing it (in
fact we've done it for OCS already) and probably
Joe,
In regard to your first question - yes we'll be going in this direction
very soon. It's being discussed with Randy now.
As for the second question - we'd love to participate in fixing it (in
fact we've done it for OCS already) and probably maintaining it but I'm
not sure what it takes
Michael Still wrote:
On Thu, Apr 24, 2014 at 7:39 AM, Joe Gordon joe.gord...@gmail.com wrote:
So no one is seriously discussing moving EC2 out of nova right now. The
issue is that the EC2 code and tempest tests aren't being maintained are
slowly code rotting. The goal of this thread is to
On 04/24/2014 05:12 AM, Thierry Carrez wrote:
Michael Still wrote:
On Thu, Apr 24, 2014 at 7:39 AM, Joe Gordon joe.gord...@gmail.com wrote:
So no one is seriously discussing moving EC2 out of nova right now. The
issue is that the EC2 code and tempest tests aren't being maintained are
slowly
On Thu, 24 Apr 2014 09:10:19 +1000
Michael Still mi...@stillhq.com wrote:
These seem like the obvious places to talk to people about helping us
get this code maintained before we're forced to drop it. Unfortunately
we can't compel people to work on things, but we can make it in their
best
Cristopher,
FYI in regard to
Its the sort of direction that we tried to steer the GCE
API folks in I
cehouse, though I don't know what they ended up doing
We ended up perfectly ok. The project is on Stackforge for some time
https://github.com/stackforge/gce-api. It works.
I believe that
Thanks for bringing this up. We at Reliance are building a team completely
dedicated to make the EC2 API support in OpenStack rock-solid and complete.
Coming from block-storage background, I submitted a few blueprints[1][2][3]
for the volumes stuff, along with the code for them[4][5][6] in the
On Thu, Apr 24, 2014 at 10:10 AM, Alexandre Levine alev...@cloudscaling.com
wrote:
Cristopher,
FYI in regard to
Its the sort of direction that we tried to steer the GCE
API folks in I
cehouse, though I don't know what they ended up doing
We ended up perfectly ok. The project is on
On 04/24/2014 03:32 PM, Rushi Agrawal wrote:
Thanks for bringing this up. We at Reliance are building a team
completely dedicated to make the EC2 API support in OpenStack rock-solid
and complete. Coming from block-storage background, I submitted a few
blueprints[1][2][3] for the volumes stuff,
On Wed, Apr 23, 2014 at 4:47 AM, Sean Dague s...@dague.net wrote:
I've spent a couple of days getting to the bottom of:
Bug 1302774 - Failed to detach volume because of volume not found error
prevents vm teardown
This is an ec2 specific failure path, which mostly looks like a
combination
Sean,
We have a bunch of tempest tests we’re ready to push back that increase
coverage for the EC2 tests. Also, rather than deprecating the EC2 pieces,
which are in use by ~35% of the community, I’d like to recommend we move them
into Stackforge as we did with the GCE APIs. That way
On 04/23/2014 02:47 PM, Randy Bias wrote:
Sean,
We have a bunch of tempest tests we’re ready to push back that increase
coverage for the EC2 tests. Also, rather than deprecating the EC2
pieces, which are in use by ~35% of the community, I’d like to recommend
we move them into Stackforge
On Apr 23, 2014, at 12:04 PM, Sean Dague s...@dague.net wrote:
We have a bunch of tempest tests we’re ready to push back that increase
coverage for the EC2 tests. Also, rather than deprecating the EC2
pieces, which are in use by ~35% of the community, I’d like to recommend
we move them into
On Wed, 2014-04-23 at 11:47 -0700, Randy Bias wrote:
Sean,
We have a bunch of tempest tests we’re ready to push back that
increase coverage for the EC2 tests. Also, rather than deprecating
the EC2 pieces, which are in use by ~35% of the community, I’d like to
recommend we move them into
On Wed, Apr 23, 2014 at 12:39 PM, Randy Bias ran...@cloudscaling.comwrote:
On Apr 23, 2014, at 12:04 PM, Sean Dague s...@dague.net wrote:
We have a bunch of tempest tests we’re ready to push back that increase
coverage for the EC2 tests. Also, rather than deprecating the EC2
pieces, which
On Thu, Apr 24, 2014 at 4:47 AM, Randy Bias ran...@cloudscaling.com wrote:
... I’d like to recommend we move
them into Stackforge as we did with the GCE APIs. That way these can become
optional components installed by those who want to use them. The other
advantage is that they can be
On Thu, Apr 24, 2014 at 7:39 AM, Joe Gordon joe.gord...@gmail.com wrote:
So no one is seriously discussing moving EC2 out of nova right now. The
issue is that the EC2 code and tempest tests aren't being maintained are
slowly code rotting. The goal of this thread is to get some volunteers to
-Original Message-
From: Michael Still [mailto:mi...@stillhq.com]
Sent: Thursday, April 24, 2014 8:10 AM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [nova] [qa] EC2 status and call for assistance
On Thu, Apr 24, 2014 at 7:39 AM
19 matches
Mail list logo
