Hi Alex,
That's great. I think we should start the work without delay.
I have just created the ec2 api sub team wiki page in nova active
sub-teams list.
https://wiki.openstack.org/wiki/Nova#Active_Sub-teams:
https://wiki.openstack.org/wiki/Meetings/EC2API
For the ec2 api weekly meeting, I have
Ok, cool. Looking forward to it.
Best regards,
Alex Levine
On 2/10/15 5:25 AM, M Ranga Swami Reddy wrote:
Hi Alex Levine (you can address me 'Swami'),
Thank you. I have been working on this EC2 APIs quite some time. We
will work closely together on this project for reviews, code cleanup,
Hey M Ranga Swami Reddy (sorry, I'm not sure how to address you shorter
:) ),
After conversation in this mailing list with Michael Still I understood
that I'll do the sub group and meetings stuff, since I lead the ec2-api
in stackforge anyways. Of course I'm not that familiar with these
Hi Alex Levine (you can address me 'Swami'),
Thank you. I have been working on this EC2 APIs quite some time. We
will work closely together on this project for reviews, code cleanup,
bug fixing and other critical items. Currently am looking for our sub
team meeting slot. Once I get the meeting
Hi All,
I will be creating the a sub group in Nova for EC2 APIs and start the
weekly meetings, reviews, code cleanup, etc tasks.
Will update the same on wiki page also soon..
Thanks
Swami
On Fri, Feb 6, 2015 at 9:27 PM, David Kranz dkr...@redhat.com wrote:
On 02/06/2015 07:49 AM, Sean Dague
On 02/06/2015 07:49 AM, Sean Dague wrote:
On 02/06/2015 07:39 AM, Alexandre Levine wrote:
Rushi,
We're adding new tempest tests into our stackforge-api/ec2-api. The
review will appear in a couple of days. These tests will be good for
running against both nova/ec2-api and stackforge/ec2-api. As
On 02/06/2015 07:39 AM, Alexandre Levine wrote:
Rushi,
We're adding new tempest tests into our stackforge-api/ec2-api. The
review will appear in a couple of days. These tests will be good for
running against both nova/ec2-api and stackforge/ec2-api. As soon as
they are there, you'll be more
There seems to be an agreement that people are fine if we improve the
in-tree Nova EC2 API more robust by adding proper Tempest tests to it,
regardless of the way forward (in-Nova-tree vs out-of-tree repo).
But there are also concerns that Tempest is not the right place for these
EC2 API tests.
Rushi,
We're adding new tempest tests into our stackforge-api/ec2-api. The
review will appear in a couple of days. These tests will be good for
running against both nova/ec2-api and stackforge/ec2-api. As soon as
they are there, you'll be more than welcome to add even more.
Best regards,
On 02/05/2015 07:01 AM, Alexandre Levine wrote:
Davanum,
We've added the devstack support. It's in our stackforge repository.
https://github.com/stackforge/ec2-api/tree/master/contrib/devstack
Best regards,
Alex Levine
I've converted it to a devstack external plugin structure in this
On 2015-02-02 14:45:53 +0300 (+0300), Alexandre Levine wrote:
On 2/2/15 12:58 PM, Daniel P. Berrange wrote:
[...]
We need to at least discuss iterate on this a few times
online, so that we can take advantage of the f2f time for any
remaining harder parts of the discussion.
[...]
how do
Davanum,
We've added the devstack support. It's in our stackforge repository.
https://github.com/stackforge/ec2-api/tree/master/contrib/devstack
Best regards,
Alex Levine
On 1/31/15 2:21 AM, Davanum Srinivas wrote:
Alexandre, Randy,
Are there plans afoot to add support to switch on
Alexandre,
very cool. Next step would be what we call a dsvm job that uses this
devstack hook. Example i am most familiar is is nova-docker's
check-tempest-dsvm-docker job:
https://github.com/openstack-infra/project-config/blob/master/jenkins/jobs/nova-docker.yaml
(also see zuul/layout.yaml)
On 2015-02-02 23:29:55 +0300 (+0300), Alexandre Levine wrote:
I'll do that when I've got myself acquainted with the weekly meetings
procedure (haven't actually bumped into it before) :)
[...]
Start from the https://wiki.openstack.org/wiki/Meetings page
preamble and follow the instructions
On Mon, Feb 2, 2015 at 11:01 PM, Alexandre Levine
alev...@cloudscaling.com wrote:
Michael,
I'm rather new here, especially in regard to communication matters, so I'd
also be glad to understand how it's done and then I can drive it if it's ok
with everybody.
By saying EC2 sub team - who did
On 2/2/15 11:15 PM, Michael Still wrote:
On Mon, Feb 2, 2015 at 11:01 PM, Alexandre Levine
alev...@cloudscaling.com wrote:
Michael,
I'm rather new here, especially in regard to communication matters, so I'd
also be glad to understand how it's done and then I can drive it if it's ok
with
On Mon, Feb 02, 2015 at 02:45:53PM +0300, Alexandre Levine wrote:
Daniel,
On 2/2/15 12:58 PM, Daniel P. Berrange wrote:
On Fri, Jan 30, 2015 at 07:57:08PM +, Tim Bell wrote:
Alex,
Many thanks for the constructive approach. I've added an item to the list
for the Ops meetup in
On Fri, Jan 30, 2015 at 07:57:08PM +, Tim Bell wrote:
Alex,
Many thanks for the constructive approach. I've added an item to the list for
the Ops meetup in March to see who would be interested to help.
As discussed on the change, it is likely that there would need to be some
Michael,
I'm rather new here, especially in regard to communication matters, so
I'd also be glad to understand how it's done and then I can drive it if
it's ok with everybody.
By saying EC2 sub team - who did you keep in mind? From my team 3
persons are involved.
From the technical point of
Daniel,
On 2/2/15 12:58 PM, Daniel P. Berrange wrote:
On Fri, Jan 30, 2015 at 07:57:08PM +, Tim Bell wrote:
Alex,
Many thanks for the constructive approach. I've added an item to the list for
the Ops meetup in March to see who would be interested to help.
As discussed on the change,
On 02/02/2015 07:01 AM, Alexandre Levine wrote:
Michael,
I'm rather new here, especially in regard to communication matters, so
I'd also be glad to understand how it's done and then I can drive it if
it's ok with everybody.
By saying EC2 sub team - who did you keep in mind? From my team 3
On 02/02/2015 11:35 AM, Alexandre Levine wrote:
Thank you Sean.
We'll be tons of EC2 Tempest tests for your attention shortly.
How would you prefer them? In several reviews, I believe. Not in one,
right?
Best regards,
Alex Levine
So, honestly, I think that we should probably look at
Thank you Sean.
We'll be tons of EC2 Tempest tests for your attention shortly.
How would you prefer them? In several reviews, I believe. Not in one, right?
Best regards,
Alex Levine
On 2/2/15 6:55 PM, Sean Dague wrote:
On 02/02/2015 07:01 AM, Alexandre Levine wrote:
Michael,
I'm rather
On 02/02/2015 11:35 AM, Alexandre Levine wrote:
Thank you Sean.
We'll be tons of EC2 Tempest tests for your attention shortly.
How would you prefer them? In several reviews, I believe. Not in one,
right?
Best regards,
Alex Levine
So, honestly, I think that we should probably look at
On 02/02/2015 07:01 AM, Alexandre Levine wrote:
Michael,
I'm rather new here, especially in regard to communication matters, so
I'd also be glad to understand how it's done and then I can drive it if
it's ok with everybody.
By saying EC2 sub team - who did you keep in mind? From my team 3
On 2/2/15 8:30 PM, Matthew Treinish wrote:
On Mon, Feb 02, 2015 at 07:35:46PM +0300, Alexandre Levine wrote:
Thank you Sean.
We'll be tons of EC2 Tempest tests for your attention shortly.
How would you prefer them? In several reviews, I believe. Not in one, right?
Let's take a step back for
On Mon, Feb 02, 2015 at 07:35:46PM +0300, Alexandre Levine wrote:
Thank you Sean.
We'll be tons of EC2 Tempest tests for your attention shortly.
How would you prefer them? In several reviews, I believe. Not in one, right?
Let's take a step back for a sec. How many tests and what kind are we
On 2/2/15 7:39 PM, Sean Dague wrote:
On 02/02/2015 11:35 AM, Alexandre Levine wrote:
Thank you Sean.
We'll be tons of EC2 Tempest tests for your attention shortly.
How would you prefer them? In several reviews, I believe. Not in one,
right?
Best regards,
Alex Levine
So, honestly, I think
On 2/2/15 7:04 PM, Sean Dague wrote:
On 02/02/2015 07:01 AM, Alexandre Levine wrote:
Michael,
I'm rather new here, especially in regard to communication matters, so
I'd also be glad to understand how it's done and then I can drive it if
it's ok with everybody.
By saying EC2 sub team - who did
On Mon, Feb 02, 2015 at 08:07:27PM +0300, Alexandre Levine wrote:
On 2/2/15 7:39 PM, Sean Dague wrote:
On 02/02/2015 11:35 AM, Alexandre Levine wrote:
Thank you Sean.
We'll be tons of EC2 Tempest tests for your attention shortly.
How would you prefer them? In several reviews, I believe.
So, its exciting to me that we seem to developing more forward
momentum here. I personally think the way forward is a staged
transition from the in-nova EC2 API to the stackforge project, with
testing added to ensure that we are feature complete between the two.
I note that Soren disagrees with me
Davanum,
Now that the picture with the both EC2 API solutions has cleared up a
bit, I can say yes, we'll be adding the tempest tests and doing devstack
integration.
Best regards,
Alex Levine
On 1/31/15 2:21 AM, Davanum Srinivas wrote:
Alexandre, Randy,
Are there plans afoot to add
Alex,
Very cool. thanks.
-- dims
On Sat, Jan 31, 2015 at 1:04 AM, Alexandre Levine
alev...@cloudscaling.com wrote:
Davanum,
Now that the picture with the both EC2 API solutions has cleared up a bit, I
can say yes, we'll be adding the tempest tests and doing devstack
integration.
Best
Alexandre, Randy,
Are there plans afoot to add support to switch on stackforge/ec2-api
in devstack? add tempest tests etc? CI Would go a long way in
alleviating concerns i think.
thanks,
dims
On Fri, Jan 30, 2015 at 1:24 PM, Bias, Randy randy.b...@emc.com wrote:
As you know we have been
On 1/29/2015 7:42 PM, Michael Still wrote:
On Thu, Jan 29, 2015 at 5:15 PM, Michael Still mi...@stillhq.com wrote:
There is an ec2 bug tag in launchpad. I would link to it except I am writing
this offline. I will fix that later today.
Ok, now that the 40 seater turbo prop has landed, here
As you know we have been driving forward on the stack forge project and
it¹s our intention to continue to support it over time, plus reinvigorate
the GCE APIs when that makes sense. So we¹re supportive of deprecating
from Nova to focus on EC2 API in Nova. I also think it¹s good for these
APIs to
Tim,
We sure we can fix it and we know how. The only problem is to somehow
get a hand with reviewing and approvals speed? Is there any remedy for
this? I've asked Michael already above in the thread, but I don't
presume that it's possible even to allow one of us to become core
reviewer for
Alex,
Many thanks for the constructive approach. I've added an item to the list for
the Ops meetup in March to see who would be interested to help.
As discussed on the change, it is likely that there would need to be some
additional Nova APIs added to support the full EC2 semantics. Thus,
+1 cloudscaling has been pretty involved in ec2 support for openstack for a
long while now.
On Fri, Jan 30, 2015 at 2:27 PM, Alexandre Levine alev...@cloudscaling.com
wrote:
Michael,
Our team can take the effort. We're the ones doing the stackforge EC2 API
and we can maintain the nova's EC2
On Fri, Jan 30, 2015 at 5:21 PM, Davanum Srinivas dava...@gmail.com wrote:
Are there plans afoot to add support to switch on stackforge/ec2-api
in devstack? add tempest tests etc? CI Would go a long way in
alleviating concerns i think.
I would encourage DevStack support to be implemented as
On Thu, 2015-01-29 at 16:01 -0800, Michael Still wrote:
However, we got here because no one is maintaining the code in Nova
for the EC2 API. This is despite repeated calls over the last 18
months (at least).
I'd love to get to the root cause before we jump to look for solutions.
The story we
Michael,
Seems like Wataru from CERN is working on testing EC2.
He is adding Rally scenarios related to EC2:
https://review.openstack.org/#/c/147550/
So at least EC2 will have good functional/perf test coverage.
Best regards,
Boris Pavlovic
On Fri, Jan 30, 2015 at 3:11 AM, matt
There is an ec2 bug tag in launchpad. I would link to it except I am
writing this offline. I will fix that later today.
However I think what we've shown is that moving this code out of nova is
the future. I would like to see someone come up with a plan to transition
users to the stackforge
On Thu, Jan 29, 2015 at 5:15 PM, Michael Still mi...@stillhq.com wrote:
There is an ec2 bug tag in launchpad. I would link to it except I am writing
this offline. I will fix that later today.
Ok, now that the 40 seater turbo prop has landed, here we go:
Is there a blue print or some set of bugs tagged in some way to tackle?
-matt
On Thu, Jan 29, 2015 at 7:01 PM, Michael Still mi...@stillhq.com wrote:
Hi,
as you might have read on openstack-dev, the Nova EC2 API
implementation is in a pretty sad state. I wont repeat all of those
details
45 matches
Mail list logo