Re: [openstack-dev] [OpenStack Foundation] Finding people to work on the EC2 API in Nova

[M Ranga Swami Reddy]

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 already sent the voting sheet
to openstack-dev mailing list. Based on the majority,
we will fix the meeting time.
(http://lists.openstack.org/pipermail/openstack-dev/2015-February/056446.html)

PS: Will update the https://wiki.openstack.org/wiki/Meetings page,
once the meeting time finalized.

Thanks
Swami

On Tue, Feb 10, 2015 at 2:15 PM, Alexandre Levine
 wrote:
> 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,
>> bug fixing and other critical items. Currently am looking for our sub
>> team meeting slot. Once I get the meeting slot will update the wiki
>> with meeting details along with the first meeting agenda. Please feel
>> free to add more to the meeting agenda.
>>
>> Thanks
>> Swami
>>
>> On Mon, Feb 9, 2015 at 9:50 PM, Alexandre Levine
>>  wrote:
>>>
>>> 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 processes
>>> in
>>> nova yet, so if you're sure that you want to take the lead for nova's
>>> part
>>> of EC2, I won't be objecting much. Please let me know what you think.
>>>
>>> Best regards,
>>>Alex Levine
>>>
>>>
>>> On 2/9/15 4:41 PM, M Ranga Swami Reddy wrote:

 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  wrote:
>
> 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 soon as
>>> they are there, you'll be more than welcome to add even more.
>>>
>>> Best regards,
>>>  Alex Levine
>>>
>> Honestly, I'm more more pro having the ec2 tests in a tree that isn't
>> Tempest. Most Tempest reviewers aren't familiar with the ec2 API,
>> their
>> focus has been OpenStack APIs.
>>
>> Having a place where there is a review team that is dedicated only to
>> the EC2 API seems much better.
>>
>>   -Sean
>>
> +1
>
>And once similar coverage to the current tempest ec2 tests is
> achieved,
> either by copying from tempest or creating anew, we should remove the
> ec2
> tests from tempest.
>
>-David
>
>
>
>
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe:
> openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


 __
 OpenStack Development Mailing List (not for usage questions)
 Unsubscribe:
 openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
 http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>>
>>>
>>>
>>>
>>> __
>>> OpenStack Development Mailing List (not for usage questions)
>>> Unsubscribe:
>>> openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>> __
>> OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

__
OpenStack Development Mailing List (not for usage quest

Re: [openstack-dev] [OpenStack Foundation] Finding people to work on the EC2 API in Nova

[Alexandre Levine]

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,
bug fixing and other critical items. Currently am looking for our sub
team meeting slot. Once I get the meeting slot will update the wiki
with meeting details along with the first meeting agenda. Please feel
free to add more to the meeting agenda.

Thanks
Swami

On Mon, Feb 9, 2015 at 9:50 PM, Alexandre Levine
 wrote:

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 processes in
nova yet, so if you're sure that you want to take the lead for nova's part
of EC2, I won't be objecting much. Please let me know what you think.

Best regards,
   Alex Levine


On 2/9/15 4:41 PM, M Ranga Swami Reddy wrote:

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  wrote:

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 soon as
they are there, you'll be more than welcome to add even more.

Best regards,
 Alex Levine


Honestly, I'm more more pro having the ec2 tests in a tree that isn't
Tempest. Most Tempest reviewers aren't familiar with the ec2 API, their
focus has been OpenStack APIs.

Having a place where there is a review team that is dedicated only to
the EC2 API seems much better.

  -Sean


+1

   And once similar coverage to the current tempest ec2 tests is achieved,
either by copying from tempest or creating anew, we should remove the ec2
tests from tempest.

   -David




__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe:
openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev



__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev



__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [OpenStack Foundation] Finding people to work on the EC2 API in Nova

[M Ranga Swami Reddy]

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 slot will update the wiki
with meeting details along with the first meeting agenda. Please feel
free to add more to the meeting agenda.

Thanks
Swami

On Mon, Feb 9, 2015 at 9:50 PM, Alexandre Levine
 wrote:
> 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 processes in
> nova yet, so if you're sure that you want to take the lead for nova's part
> of EC2, I won't be objecting much. Please let me know what you think.
>
> Best regards,
>   Alex Levine
>
>
> On 2/9/15 4:41 PM, M Ranga Swami Reddy wrote:
>>
>> 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  wrote:
>>>
>>> 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 soon as
> they are there, you'll be more than welcome to add even more.
>
> Best regards,
> Alex Levine
>
 Honestly, I'm more more pro having the ec2 tests in a tree that isn't
 Tempest. Most Tempest reviewers aren't familiar with the ec2 API, their
 focus has been OpenStack APIs.

 Having a place where there is a review team that is dedicated only to
 the EC2 API seems much better.

  -Sean

>>> +1
>>>
>>>   And once similar coverage to the current tempest ec2 tests is achieved,
>>> either by copying from tempest or creating anew, we should remove the ec2
>>> tests from tempest.
>>>
>>>   -David
>>>
>>>
>>>
>>>
>>> __
>>> OpenStack Development Mailing List (not for usage questions)
>>> Unsubscribe:
>>> openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>> __
>> OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [OpenStack Foundation] Finding people to work on the EC2 API in Nova

[Alexandre Levine]

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 
processes in nova yet, so if you're sure that you want to take the lead 
for nova's part of EC2, I won't be objecting much. Please let me know 
what you think.


Best regards,
  Alex Levine

On 2/9/15 4:41 PM, M Ranga Swami Reddy wrote:

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  wrote:

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 soon as
they are there, you'll be more than welcome to add even more.

Best regards,
Alex Levine


Honestly, I'm more more pro having the ec2 tests in a tree that isn't
Tempest. Most Tempest reviewers aren't familiar with the ec2 API, their
focus has been OpenStack APIs.

Having a place where there is a review team that is dedicated only to
the EC2 API seems much better.

 -Sean


+1

  And once similar coverage to the current tempest ec2 tests is achieved,
either by copying from tempest or creating anew, we should remove the ec2
tests from tempest.

  -David



__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev



__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [OpenStack Foundation] Finding people to work on the EC2 API in Nova

[M Ranga Swami Reddy]

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  wrote:
> 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 soon as
>>> they are there, you'll be more than welcome to add even more.
>>>
>>> Best regards,
>>>Alex Levine
>>>
>> Honestly, I'm more more pro having the ec2 tests in a tree that isn't
>> Tempest. Most Tempest reviewers aren't familiar with the ec2 API, their
>> focus has been OpenStack APIs.
>>
>> Having a place where there is a review team that is dedicated only to
>> the EC2 API seems much better.
>>
>> -Sean
>>
> +1
>
>  And once similar coverage to the current tempest ec2 tests is achieved,
> either by copying from tempest or creating anew, we should remove the ec2
> tests from tempest.
>
>  -David
>
>
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [OpenStack Foundation] Finding people to work on the EC2 API in Nova

[David Kranz]

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 soon as
they are there, you'll be more than welcome to add even more.

Best regards,
   Alex Levine


Honestly, I'm more more pro having the ec2 tests in a tree that isn't
Tempest. Most Tempest reviewers aren't familiar with the ec2 API, their
focus has been OpenStack APIs.

Having a place where there is a review team that is dedicated only to
the EC2 API seems much better.

-Sean


+1

 And once similar coverage to the current tempest ec2 tests is 
achieved, either by copying from tempest or creating anew, we should 
remove the ec2 tests from tempest.


 -David


__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [OpenStack Foundation] Finding people to work on the EC2 API in Nova

[Sean Dague]

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 than welcome to add even more.
> 
> Best regards,
>   Alex Levine
> 

Honestly, I'm more more pro having the ec2 tests in a tree that isn't
Tempest. Most Tempest reviewers aren't familiar with the ec2 API, their
focus has been OpenStack APIs.

Having a place where there is a review team that is dedicated only to
the EC2 API seems much better.

-Sean

-- 
Sean Dague
http://dague.net

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [OpenStack Foundation] Finding people to work on the EC2 API in Nova

[Alexandre Levine]

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,
  Alex Levine


On 2/6/15 3:20 PM, Rushi Agrawal wrote:
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. While I am not mature enough with testing 
methodologies to comment on what is good vs bad, I am seeing a problem 
if we start blocking new EC2 Tempest tests, and ask to move them 
out-of-Tempest first. This will particularly hurt the EC2-code-in-Nova 
camp (which includes me) who have seemingly been given a lifeline 
until the next summit to prove they care about in-tree EC2 code.


So I just wanted to know what does concerned people think about this 
problem. On solution I can see is allow tests to be added to Tempest 
for now, and then make the switch post-summit. I am hoping moving 
tests out of Tempest at-once wouldn't be a tough job (mostly tidying 
import statements?).


Regards,
Rushi Agrawal
Cloud Engineer,
Reliance Jio Infocomm

On 5 February 2015 at 19:41, Sean Dague > wrote:


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
review
- https://review.openstack.org/#/c/153206/

so that will make using this as simple as

enable_plugin ec2-api https://github.com/stackforge/ec2-api

Once that merges.

-Sean

--
Sean Dague
http://dague.net

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe:
openstack-dev-requ...@lists.openstack.org?subject:unsubscribe

http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev





__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [OpenStack Foundation] Finding people to work on the EC2 API in Nova

[Rushi Agrawal]

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. While I am not mature enough with testing methodologies to
comment on what is good vs bad, I am seeing a problem if we start blocking
new EC2 Tempest tests, and ask to move them out-of-Tempest first. This will
particularly hurt the EC2-code-in-Nova camp (which includes me) who have
seemingly been given a lifeline until the next summit to prove they care
about in-tree EC2 code.

So I just wanted to know what does concerned people think about this
problem. On solution I can see is allow tests to be added to Tempest for
now, and then make the switch post-summit. I am hoping moving tests out of
Tempest at-once wouldn't be a tough job (mostly tidying import
statements?).

Regards,
Rushi Agrawal
Cloud Engineer,
Reliance Jio Infocomm

On 5 February 2015 at 19:41, Sean Dague  wrote:

> 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 review
> - https://review.openstack.org/#/c/153206/
>
> so that will make using this as simple as
>
> enable_plugin ec2-api https://github.com/stackforge/ec2-api
>
> Once that merges.
>
> -Sean
>
> --
> Sean Dague
> http://dague.net
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [OpenStack Foundation] Finding people to work on the EC2 API in Nova

[Sean Dague]

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 review
- https://review.openstack.org/#/c/153206/

so that will make using this as simple as

enable_plugin ec2-api https://github.com/stackforge/ec2-api

Once that merges.

-Sean

-- 
Sean Dague
http://dague.net

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [OpenStack Foundation] Finding people to work on the EC2 API in Nova

[Jeremy Stanley]

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 you usually do those online discussions? I mean what is the
> tooling?

You're doing it right now.

But also, comments on review.openstack.org for your proposed spec,
ad hoc discussions in appropriate IRC channels[1] and possibly more
officially in weekly IRC meetings[2].

[1] https://wiki.openstack.org/wiki/IRC
[2] https://wiki.openstack.org/wiki/Meetings
-- 
Jeremy Stanley

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [OpenStack Foundation] Finding people to work on the EC2 API in Nova

[Davanum Srinivas]

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)

thanks,
dims

On Thu, Feb 5, 2015 at 7: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
>
> On 1/31/15 2:21 AM, Davanum Srinivas wrote:
>>
>> 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  wrote:
>>>
>>> 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 be able to iterate outside of the standard release cycle.
>>>
>>>
>>>
>>> --Randy
>>>
>>> VP, Technology, EMC Corporation
>>> Formerly Founder & CEO, Cloudscaling (now a part of EMC)
>>> +1 (415) 787-2253 [google voice]
>>> TWITTER: twitter.com/randybias
>>> LINKEDIN: linkedin.com/in/randybias
>>> ASSISTANT: ren...@emc.com
>>>
>>>
>>>
>>>
>>>
>>>
>>> On 1/29/15, 4:01 PM, "Michael Still"  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 here -- you can read the thread on openstack-dev for detail.

 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).

 So, does the Foundation have a role here? The Nova team has failed to
 find someone to help us resolve these issues. Can the board perhaps
 find resources as the representatives of some of the largest
 contributors to OpenStack? Could the Foundation employ someone to help
 us our here?

 I suspect the correct plan is to work on getting the stackforge
 replacement finished, and ensuring that it is feature compatible with
 the Nova implementation. However, I don't want to preempt the design
 process -- there might be other ways forward here.

 I feel that a continued discussion which just repeats the last 18
 months wont actually fix the situation -- its time to "break out" of
 that mode and find other ways to try and get someone working on this
 problem.

 Thoughts welcome.

 Michael

 --
 Rackspace Australia

 ___
 Foundation mailing list
 foundat...@lists.openstack.org
 http://lists.openstack.org/cgi-bin/mailman/listinfo/foundation
>>>
>>>
>>>
>>> __
>>> OpenStack Development Mailing List (not for usage questions)
>>> Unsubscribe:
>>> openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>>
>>
>
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev



-- 
Davanum Srinivas :: https://twitter.com/dims

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [OpenStack Foundation] Finding people to work on the EC2 API in Nova

[Alexandre Levine]

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 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  wrote:

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 be able to iterate outside of the standard release cycle.



--Randy

VP, Technology, EMC Corporation
Formerly Founder & CEO, Cloudscaling (now a part of EMC)
+1 (415) 787-2253 [google voice]
TWITTER: twitter.com/randybias
LINKEDIN: linkedin.com/in/randybias
ASSISTANT: ren...@emc.com






On 1/29/15, 4:01 PM, "Michael Still"  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 here -- you can read the thread on openstack-dev for detail.

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).

So, does the Foundation have a role here? The Nova team has failed to
find someone to help us resolve these issues. Can the board perhaps
find resources as the representatives of some of the largest
contributors to OpenStack? Could the Foundation employ someone to help
us our here?

I suspect the correct plan is to work on getting the stackforge
replacement finished, and ensuring that it is feature compatible with
the Nova implementation. However, I don't want to preempt the design
process -- there might be other ways forward here.

I feel that a continued discussion which just repeats the last 18
months wont actually fix the situation -- its time to "break out" of
that mode and find other ways to try and get someone working on this
problem.

Thoughts welcome.

Michael

--
Rackspace Australia

___
Foundation mailing list
foundat...@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/foundation


__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev






__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [OpenStack Foundation] Finding people to work on the EC2 API in Nova

[Jeremy Stanley]

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 linked from it.
-- 
Jeremy Stanley

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [OpenStack Foundation] Finding people to work on the EC2 API in Nova

[Alexandre Levine]

On 2/2/15 11:15 PM, Michael Still wrote:

On Mon, Feb 2, 2015 at 11:01 PM, 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 persons
are involved.

I see the sub team as the way of keeping the various organisations who
have expressed interest in helping pulling in the same direction. I'd
suggest you pick a free slot on our meeting calendar and run an irc
meeting there weekly to track overall progress.


I'll do that when I've got myself acquainted with the weekly meetings 
procedure (haven't actually bumped into it before) :)



 From the technical point of view the transition plan could look somewhat
like this (sequence can be different):

1. Triage EC2 bugs and fix showstoppers in nova's EC2.
2. Contribute Tempest tests for EC2 functionality and employ them against
nova's EC2.
3. Write spec for required API to be exposed from nova so that we get full
info.
4. Triage and fix all of the existing nova's EC2 bugs worth fixing.
5. Set up Tempest testing of the stackforge/ec2 (if that's possible).
6. Communicate and discover all of the existing questions and problematic
points for the switching from existing EC2 API to the new one. Provide
solutions or decisions about them.
7. Do performance testing of the new stackforge/ec2 and provide fixes if any
bottlenecks come up.
8. Have all of the above prepared for the Vancouver summit and discuss the
situation there.

This sounds really good to me -- this is the sort of thing you'd be
tracking against in that irc meeting, although presumably you'd
negotiate as a group exactly what the steps are and who is working on
what.

Do you see transitioning users to the external EC2 implementation as a
final step in this list? I know you've only gone as far as Vancouver
here, but I want to be explicit about the intended end goal.


Yes, that's correct. The very final step though would be cleaning up 
nova from the EC2 stuff. But you're right, the major goal would be to 
make external EC2 API production-ready and to have all of the necessary 
means for users to seamlessly transition (no downtimes, no instances 
recreation required).

So I can point at least three distinct major milestones here:

1. EC2 API in nova is back and revived (no showstoppers, all of the 
currently employed functionality safe and sound, new tests added to 
check and ensure that).

2. External EC2 API is production-ready.
3. Nova is relieved of the EC2 stuff.

Vancouver is somewhere in between 1 and 3.



Michael, I am still wondering, who's going to be responsible for timely
reviews and approvals of the fixes and tests we're going to contribute to
nova? So far this is the biggest risk. Is there anyway to allow some of us
to participate in the process?

Sean has offered here, for which I am grateful. Your team as it forms
should also start reviewing each other's work, as that will reduce the
workload somewhat for Sean and other cores.


We've already started.


I think given the level of interest here we can have a serious
discussion at Vancouver about if EC2 should be nominated as a priority
task for the L release, which is our more formal way of cementing this
at the beginning of a release cycle.

Thanks again to everyone who has volunteered to help out with this.
35% of our users are grateful!

Michael



On 2/2/15 2:46 AM, Michael Still wrote:

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 here, but that's ok -- I'd like to
see us work through that as a team based on the merits.

So... It sounds like we have an EC2 sub team forming. How do we get
that group meeting to come up with a transition plan?

Michael

On Sun, Feb 1, 2015 at 4:12 AM, Davanum Srinivas 
wrote:

Alex,

Very cool. thanks.

-- dims

On Sat, Jan 31, 2015 at 1:04 AM, Alexandre Levine
 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 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 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 
wrote:

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 b

Re: [openstack-dev] [OpenStack Foundation] Finding people to work on the EC2 API in Nova

[Michael Still]

On Mon, Feb 2, 2015 at 11:01 PM, 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 persons
> are involved.

I see the sub team as the way of keeping the various organisations who
have expressed interest in helping pulling in the same direction. I'd
suggest you pick a free slot on our meeting calendar and run an irc
meeting there weekly to track overall progress.

> From the technical point of view the transition plan could look somewhat
> like this (sequence can be different):
>
> 1. Triage EC2 bugs and fix showstoppers in nova's EC2.
> 2. Contribute Tempest tests for EC2 functionality and employ them against
> nova's EC2.
> 3. Write spec for required API to be exposed from nova so that we get full
> info.
> 4. Triage and fix all of the existing nova's EC2 bugs worth fixing.
> 5. Set up Tempest testing of the stackforge/ec2 (if that's possible).
> 6. Communicate and discover all of the existing questions and problematic
> points for the switching from existing EC2 API to the new one. Provide
> solutions or decisions about them.
> 7. Do performance testing of the new stackforge/ec2 and provide fixes if any
> bottlenecks come up.
> 8. Have all of the above prepared for the Vancouver summit and discuss the
> situation there.

This sounds really good to me -- this is the sort of thing you'd be
tracking against in that irc meeting, although presumably you'd
negotiate as a group exactly what the steps are and who is working on
what.

Do you see transitioning users to the external EC2 implementation as a
final step in this list? I know you've only gone as far as Vancouver
here, but I want to be explicit about the intended end goal.

> Michael, I am still wondering, who's going to be responsible for timely
> reviews and approvals of the fixes and tests we're going to contribute to
> nova? So far this is the biggest risk. Is there anyway to allow some of us
> to participate in the process?

Sean has offered here, for which I am grateful. Your team as it forms
should also start reviewing each other's work, as that will reduce the
workload somewhat for Sean and other cores.

I think given the level of interest here we can have a serious
discussion at Vancouver about if EC2 should be nominated as a priority
task for the L release, which is our more formal way of cementing this
at the beginning of a release cycle.

Thanks again to everyone who has volunteered to help out with this.
35% of our users are grateful!

Michael


> On 2/2/15 2:46 AM, Michael Still wrote:
>>
>> 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 here, but that's ok -- I'd like to
>> see us work through that as a team based on the merits.
>>
>> So... It sounds like we have an EC2 sub team forming. How do we get
>> that group meeting to come up with a transition plan?
>>
>> Michael
>>
>> On Sun, Feb 1, 2015 at 4:12 AM, Davanum Srinivas 
>> wrote:
>>>
>>> Alex,
>>>
>>> Very cool. thanks.
>>>
>>> -- dims
>>>
>>> On Sat, Jan 31, 2015 at 1:04 AM, Alexandre Levine
>>>  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 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 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 
> wrote:
>>
>> 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 be able to iterate outside of the standard release cycle.
>>
>>
>>
>> --Randy
>>
>> VP, Technology, EMC Corporation
>> Formerly Founder & CEO, Cloudscaling (now a part of EMC)
>> +1 (415) 787-2253 [google voice]
>> TWITTER: twitter.com/randybias
>> LINKEDIN: linkedin.com/in/randybias
>> ASSISTANT: ren...@emc.com
>>
>>
>>
>>
>>
>>
>> On 1/29/15, 4:01 PM, "Michael Still"  wrote:
>>
>>> Hi,
>>>
>>> as you might have read on openstack-dev, the Nova EC2 API

Re: [openstack-dev] [OpenStack Foundation] Finding people to work on the EC2 API in Nova

[Alexandre Levine]

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 a sec. How many tests and what kind are we talking
about here?
We've got our root in /tempest/thirdparty/aws/ec2 (which we considered a 
better naming than boto) and it works via botocore (so no boto in any case).

12 files with 79 API tests.
However we've got additionally some amount of complex scenario tests as 
well, unfortunately using boto, not botocore. Most of them though are 
about VPC stuff so those we'll run against our stackforge's EC2 only.


Please let us know where and how to put it.


I'm thinking it might be better to not just try and dump all this stuff in
tempest. While in the past we've just dumped all of this in tempest, moving
forward I don't think that's what we want to be doing. The current ec2 tests
have always felt out of place to me in tempest and historically haven't been
maintained as well as the other tests. If we're talking about ramping up the ec2
testing we probably should look at migrating everything elsewhere, especially
given that it just essentially nova testing. I see 2 better options here: we
either put the tests in the tree for the project with the ec2 implementation, or
we create a new repo like tempest-ec2 for testing this. In either case we'll
leverage tempest-lib to make sure the bits your existing testing is relying on
are consumable outside of the tempest repo.

-Matt Treinish



On 2/2/15 6:55 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 you keep in mind? From my team 3
persons are involved.

 From the technical point of view the transition plan could look somewhat
like this (sequence can be different):

1. Triage EC2 bugs and fix showstoppers in nova's EC2.
2. Contribute Tempest tests for EC2 functionality and employ them
against nova's EC2.
3. Write spec for required API to be exposed from nova so that we get
full info.
4. Triage and fix all of the existing nova's EC2 bugs worth fixing.
5. Set up Tempest testing of the stackforge/ec2 (if that's possible).
6. Communicate and discover all of the existing questions and
problematic points for the switching from existing EC2 API to the new
one. Provide solutions or decisions about them.
7. Do performance testing of the new stackforge/ec2 and provide fixes if
any bottlenecks come up.
8. Have all of the above prepared for the Vancouver summit and discuss
the situation there.

Michael, I am still wondering, who's going to be responsible for timely
reviews and approvals of the fixes and tests we're going to contribute
to nova? So far this is the biggest risk. Is there anyway to allow some
of us to participate in the process?

I am happy to volunteer to shephard these reviews. I'll try to keep an
eye on them, and if something is blocking please just ping me directly
on IRC in #openstack-nova or bring them forward to the weekly Nova meeting.

-Sean



__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [OpenStack Foundation] Finding people to work on the EC2 API in Nova

[Matthew Treinish]

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. Not in one,
> >>right?
> >>
> >>Best regards,
> >>   Alex Levine
> >So, honestly, I think that we should probably look at getting the ec2
> >tests out of the Tempest tree as well and into a more dedicated place.
> >Like as part of the stackforge project tree. Given that the right
> >expertise would be there as well. It could use tempest-lib for some of
> >the common parts.
> >
> > -Sean
> We tried to find out about tempest-lib, asked Keichi Ohmichi, but it seems
> that's still work in progress. Can you point us somewhere where we can
> understand how to employ this technology.

Tempest-lib is the effort to break out useful pieces from the tempest repo so
that they have stable interfaces and can easily be consumed externally.
Right now it only has some basic functionality in it, but we are working on
expanding it more constantly. If there is a needed feature from inside the
tempest repo which is currently missing from the lib we can work together on
migrating it over faster. 

> So the use cases will be:
> 
> 1. Be able to run the suit against EC2 in nova.
> 2. Be able to run the suit against stackforge/EC2.
> 3. Use that for gating for both repos.

These 3 things are really independent of tempest-lib. There more about how you
configure the test suite to be run. (in general and in the CI) Tempest-lib is
just a library which has the common functionality from tempest that is
generally useful outside of the tempest repo and won't help with how you
configure things to run.

But, if your tests are only interacting with things only through the API 1 and
2 should be as simple as pointing it at different endpoints.

> 
> Additional complication here is that some of the tests will have to skipped
> because of functionality absence or because of bugs in nova's EC2 but should
> be employed against stackforge's version.
> 
> Could you advice how to achieve such effects?

This also is just a matter of how you setup and configure your test jobs and the
test suite. It would be the same pretty much wherever the tests end up. When you
get a test suite setup I can help with setting things up to make this simpler.

If you join the #openstack-qa channel on freenode and we can work through 
exactly
what you're trying to accomplish with a higher throughput.

-Matt Treinish

> 
> >
> >>On 2/2/15 6:55 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 you keep in mind? From my team 3
> persons are involved.
> 
>   From the technical point of view the transition plan could look
> somewhat
> like this (sequence can be different):
> 
> 1. Triage EC2 bugs and fix showstoppers in nova's EC2.
> 2. Contribute Tempest tests for EC2 functionality and employ them
> against nova's EC2.
> 3. Write spec for required API to be exposed from nova so that we get
> full info.
> 4. Triage and fix all of the existing nova's EC2 bugs worth fixing.
> 5. Set up Tempest testing of the stackforge/ec2 (if that's possible).
> 6. Communicate and discover all of the existing questions and
> problematic points for the switching from existing EC2 API to the new
> one. Provide solutions or decisions about them.
> 7. Do performance testing of the new stackforge/ec2 and provide fixes if
> any bottlenecks come up.
> 8. Have all of the above prepared for the Vancouver summit and discuss
> the situation there.
> 
> Michael, I am still wondering, who's going to be responsible for timely
> reviews and approvals of the fixes and tests we're going to contribute
> to nova? So far this is the biggest risk. Is there anyway to allow some
> of us to participate in the process?
> >>>I am happy to volunteer to shephard these reviews. I'll try to keep an
> >>>eye on them, and if something is blocking please just ping me directly
> >>>on IRC in #openstack-nova or bring them forward to the weekly Nova
> >>>meeting.
> >>>
> >>> -Sean
> >>>
> >>
> >>__
> >>OpenStack Development Mailing List (not for usage questions)
> >>Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> >>http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> >
> 
> 
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-

Re: [openstack-dev] [OpenStack Foundation] Finding people to work on the EC2 API in Nova

[Matthew Treinish]

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 talking
about here?

I'm thinking it might be better to not just try and dump all this stuff in
tempest. While in the past we've just dumped all of this in tempest, moving
forward I don't think that's what we want to be doing. The current ec2 tests
have always felt out of place to me in tempest and historically haven't been
maintained as well as the other tests. If we're talking about ramping up the ec2
testing we probably should look at migrating everything elsewhere, especially
given that it just essentially nova testing. I see 2 better options here: we
either put the tests in the tree for the project with the ec2 implementation, or
we create a new repo like tempest-ec2 for testing this. In either case we'll
leverage tempest-lib to make sure the bits your existing testing is relying on
are consumable outside of the tempest repo.

-Matt Treinish


> On 2/2/15 6:55 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 you keep in mind? From my team 3
> >>persons are involved.
> >>
> >> From the technical point of view the transition plan could look somewhat
> >>like this (sequence can be different):
> >>
> >>1. Triage EC2 bugs and fix showstoppers in nova's EC2.
> >>2. Contribute Tempest tests for EC2 functionality and employ them
> >>against nova's EC2.
> >>3. Write spec for required API to be exposed from nova so that we get
> >>full info.
> >>4. Triage and fix all of the existing nova's EC2 bugs worth fixing.
> >>5. Set up Tempest testing of the stackforge/ec2 (if that's possible).
> >>6. Communicate and discover all of the existing questions and
> >>problematic points for the switching from existing EC2 API to the new
> >>one. Provide solutions or decisions about them.
> >>7. Do performance testing of the new stackforge/ec2 and provide fixes if
> >>any bottlenecks come up.
> >>8. Have all of the above prepared for the Vancouver summit and discuss
> >>the situation there.
> >>
> >>Michael, I am still wondering, who's going to be responsible for timely
> >>reviews and approvals of the fixes and tests we're going to contribute
> >>to nova? So far this is the biggest risk. Is there anyway to allow some
> >>of us to participate in the process?
> >I am happy to volunteer to shephard these reviews. I'll try to keep an
> >eye on them, and if something is blocking please just ping me directly
> >on IRC in #openstack-nova or bring them forward to the weekly Nova meeting.
> >
> > -Sean
> >
> 
> 
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


pgp0JOfRz8arI.pgp
Description: PGP signature
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [OpenStack Foundation] Finding people to work on the EC2 API in Nova

[Alexandre Levine]

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 you keep in mind? From my team 3
persons are involved.

 From the technical point of view the transition plan could look somewhat
like this (sequence can be different):

1. Triage EC2 bugs and fix showstoppers in nova's EC2.
2. Contribute Tempest tests for EC2 functionality and employ them
against nova's EC2.
3. Write spec for required API to be exposed from nova so that we get
full info.
4. Triage and fix all of the existing nova's EC2 bugs worth fixing.
5. Set up Tempest testing of the stackforge/ec2 (if that's possible).
6. Communicate and discover all of the existing questions and
problematic points for the switching from existing EC2 API to the new
one. Provide solutions or decisions about them.
7. Do performance testing of the new stackforge/ec2 and provide fixes if
any bottlenecks come up.
8. Have all of the above prepared for the Vancouver summit and discuss
the situation there.

Michael, I am still wondering, who's going to be responsible for timely
reviews and approvals of the fixes and tests we're going to contribute
to nova? So far this is the biggest risk. Is there anyway to allow some
of us to participate in the process?

It would also be really helpful if there were reviews from you team on
any ec2 touching code.

https://review.openstack.org/#/q/file:%255Enova/api/ec2.*+status:open,n,z

There currently are only a few patches which touch ec2 that are ec2
function/bug related, and mostly don't have any scored reviews.
Especially this series -
https://review.openstack.org/#/q/status:open+project:openstack/nova+branch:master+topic:bp/ec2-volume-and-snapshot-tags,n,z


Which is a month old with no scoring.


Yes, we'll start looking there as well.


-Sean


Best regards,
   Alex Levine

On 2/2/15 2:46 AM, Michael Still wrote:

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 here, but that's ok -- I'd like to
see us work through that as a team based on the merits.

So... It sounds like we have an EC2 sub team forming. How do we get
that group meeting to come up with a transition plan?

Michael

On Sun, Feb 1, 2015 at 4:12 AM, Davanum Srinivas 
wrote:

Alex,

Very cool. thanks.

-- dims

On Sat, Jan 31, 2015 at 1:04 AM, Alexandre Levine
 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 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 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 
wrote:

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 be able to iterate outside of the standard release cycle.



--Randy

VP, Technology, EMC Corporation
Formerly Founder & CEO, Cloudscaling (now a part of EMC)
+1 (415) 787-2253 [google voice]
TWITTER: twitter.com/randybias
LINKEDIN: linkedin.com/in/randybias
ASSISTANT: ren...@emc.com






On 1/29/15, 4:01 PM, "Michael Still"  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 here -- you can read the thread on openstack-dev for detail.

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).

So, does the Foundation have a role here? The Nova team has
failed to
find someone to help us resolve these issues. Can the board perhaps
find resources as the representatives of some of the largest
contributors to OpenStack? Could the Foundation employ someone to
help
us our here?

I suspect the correct plan is to work on getting the stackforge
replacement finished, and ensuring that it is feature compatible
with
the Nova implementation. However, I don't want to preempt the design
process -- there might be other ways forward here.

I feel that a continued discussion which just repeats the last 18
months wont actually fix the situation -- its time to "break out" of
that mode and find other ways to try and get someone working on this
problem.

Thoughts welc

Re: [openstack-dev] [OpenStack Foundation] Finding people to work on the EC2 API in Nova

[Alexandre Levine]

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 that we should probably look at getting the ec2
tests out of the Tempest tree as well and into a more dedicated place.
Like as part of the stackforge project tree. Given that the right
expertise would be there as well. It could use tempest-lib for some of
the common parts.

-Sean
We tried to find out about tempest-lib, asked Keichi Ohmichi, but it 
seems that's still work in progress. Can you point us somewhere where we 
can understand how to employ this technology.

So the use cases will be:

1. Be able to run the suit against EC2 in nova.
2. Be able to run the suit against stackforge/EC2.
3. Use that for gating for both repos.

Additional complication here is that some of the tests will have to 
skipped because of functionality absence or because of bugs in nova's 
EC2 but should be employed against stackforge's version.


Could you advice how to achieve such effects?




On 2/2/15 6:55 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 you keep in mind? From my team 3
persons are involved.

  From the technical point of view the transition plan could look
somewhat
like this (sequence can be different):

1. Triage EC2 bugs and fix showstoppers in nova's EC2.
2. Contribute Tempest tests for EC2 functionality and employ them
against nova's EC2.
3. Write spec for required API to be exposed from nova so that we get
full info.
4. Triage and fix all of the existing nova's EC2 bugs worth fixing.
5. Set up Tempest testing of the stackforge/ec2 (if that's possible).
6. Communicate and discover all of the existing questions and
problematic points for the switching from existing EC2 API to the new
one. Provide solutions or decisions about them.
7. Do performance testing of the new stackforge/ec2 and provide fixes if
any bottlenecks come up.
8. Have all of the above prepared for the Vancouver summit and discuss
the situation there.

Michael, I am still wondering, who's going to be responsible for timely
reviews and approvals of the fixes and tests we're going to contribute
to nova? So far this is the biggest risk. Is there anyway to allow some
of us to participate in the process?

I am happy to volunteer to shephard these reviews. I'll try to keep an
eye on them, and if something is blocking please just ping me directly
on IRC in #openstack-nova or bring them forward to the weekly Nova
meeting.

 -Sean



__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev





__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [OpenStack Foundation] Finding people to work on the EC2 API in Nova

[Boris Pavlovic]

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 getting the ec2
> tests out of the Tempest tree as well and into a more dedicated place.
> Like as part of the stackforge project tree. Given that the right
> expertise would be there as well. It could use tempest-lib for some of
> the common parts.



Rally team would be happy to accept some of tests, and as well we support
in tree plugins.
So part of tests (that are only for hardcore functional testing and not
reusable in reallife)
can stay in tree of ec2-api.

Best regards,
Boris Pavlovic


On Mon, Feb 2, 2015 at 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 that we should probably look at getting the ec2
> tests out of the Tempest tree as well and into a more dedicated place.
> Like as part of the stackforge project tree. Given that the right
> expertise would be there as well. It could use tempest-lib for some of
> the common parts.
>
> -Sean
>
> >
> > On 2/2/15 6:55 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 you keep in mind? From my team 3
> >>> persons are involved.
> >>>
> >>>  From the technical point of view the transition plan could look
> >>> somewhat
> >>> like this (sequence can be different):
> >>>
> >>> 1. Triage EC2 bugs and fix showstoppers in nova's EC2.
> >>> 2. Contribute Tempest tests for EC2 functionality and employ them
> >>> against nova's EC2.
> >>> 3. Write spec for required API to be exposed from nova so that we get
> >>> full info.
> >>> 4. Triage and fix all of the existing nova's EC2 bugs worth fixing.
> >>> 5. Set up Tempest testing of the stackforge/ec2 (if that's possible).
> >>> 6. Communicate and discover all of the existing questions and
> >>> problematic points for the switching from existing EC2 API to the new
> >>> one. Provide solutions or decisions about them.
> >>> 7. Do performance testing of the new stackforge/ec2 and provide fixes
> if
> >>> any bottlenecks come up.
> >>> 8. Have all of the above prepared for the Vancouver summit and discuss
> >>> the situation there.
> >>>
> >>> Michael, I am still wondering, who's going to be responsible for timely
> >>> reviews and approvals of the fixes and tests we're going to contribute
> >>> to nova? So far this is the biggest risk. Is there anyway to allow some
> >>> of us to participate in the process?
> >> I am happy to volunteer to shephard these reviews. I'll try to keep an
> >> eye on them, and if something is blocking please just ping me directly
> >> on IRC in #openstack-nova or bring them forward to the weekly Nova
> >> meeting.
> >>
> >> -Sean
> >>
> >
> >
> >
> __
> > OpenStack Development Mailing List (not for usage questions)
> > Unsubscribe:
> openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
> --
> Sean Dague
> http://dague.net
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [OpenStack Foundation] Finding people to work on the EC2 API in Nova

[Sean Dague]

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 getting the ec2
tests out of the Tempest tree as well and into a more dedicated place.
Like as part of the stackforge project tree. Given that the right
expertise would be there as well. It could use tempest-lib for some of
the common parts.

-Sean

> 
> On 2/2/15 6:55 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 you keep in mind? From my team 3
>>> persons are involved.
>>>
>>>  From the technical point of view the transition plan could look
>>> somewhat
>>> like this (sequence can be different):
>>>
>>> 1. Triage EC2 bugs and fix showstoppers in nova's EC2.
>>> 2. Contribute Tempest tests for EC2 functionality and employ them
>>> against nova's EC2.
>>> 3. Write spec for required API to be exposed from nova so that we get
>>> full info.
>>> 4. Triage and fix all of the existing nova's EC2 bugs worth fixing.
>>> 5. Set up Tempest testing of the stackforge/ec2 (if that's possible).
>>> 6. Communicate and discover all of the existing questions and
>>> problematic points for the switching from existing EC2 API to the new
>>> one. Provide solutions or decisions about them.
>>> 7. Do performance testing of the new stackforge/ec2 and provide fixes if
>>> any bottlenecks come up.
>>> 8. Have all of the above prepared for the Vancouver summit and discuss
>>> the situation there.
>>>
>>> Michael, I am still wondering, who's going to be responsible for timely
>>> reviews and approvals of the fixes and tests we're going to contribute
>>> to nova? So far this is the biggest risk. Is there anyway to allow some
>>> of us to participate in the process?
>> I am happy to volunteer to shephard these reviews. I'll try to keep an
>> eye on them, and if something is blocking please just ping me directly
>> on IRC in #openstack-nova or bring them forward to the weekly Nova
>> meeting.
>>
>> -Sean
>>
> 
> 
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


-- 
Sean Dague
http://dague.net

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [OpenStack Foundation] Finding people to work on the EC2 API in Nova

[Alexandre Levine]

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 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 view the transition plan could look somewhat
like this (sequence can be different):

1. Triage EC2 bugs and fix showstoppers in nova's EC2.
2. Contribute Tempest tests for EC2 functionality and employ them
against nova's EC2.
3. Write spec for required API to be exposed from nova so that we get
full info.
4. Triage and fix all of the existing nova's EC2 bugs worth fixing.
5. Set up Tempest testing of the stackforge/ec2 (if that's possible).
6. Communicate and discover all of the existing questions and
problematic points for the switching from existing EC2 API to the new
one. Provide solutions or decisions about them.
7. Do performance testing of the new stackforge/ec2 and provide fixes if
any bottlenecks come up.
8. Have all of the above prepared for the Vancouver summit and discuss
the situation there.

Michael, I am still wondering, who's going to be responsible for timely
reviews and approvals of the fixes and tests we're going to contribute
to nova? So far this is the biggest risk. Is there anyway to allow some
of us to participate in the process?

I am happy to volunteer to shephard these reviews. I'll try to keep an
eye on them, and if something is blocking please just ping me directly
on IRC in #openstack-nova or bring them forward to the weekly Nova meeting.

-Sean




__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [OpenStack Foundation] Finding people to work on the EC2 API in Nova

[Sean Dague]

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
> persons are involved.
> 
> From the technical point of view the transition plan could look somewhat
> like this (sequence can be different):
> 
> 1. Triage EC2 bugs and fix showstoppers in nova's EC2.
> 2. Contribute Tempest tests for EC2 functionality and employ them
> against nova's EC2.
> 3. Write spec for required API to be exposed from nova so that we get
> full info.
> 4. Triage and fix all of the existing nova's EC2 bugs worth fixing.
> 5. Set up Tempest testing of the stackforge/ec2 (if that's possible).
> 6. Communicate and discover all of the existing questions and
> problematic points for the switching from existing EC2 API to the new
> one. Provide solutions or decisions about them.
> 7. Do performance testing of the new stackforge/ec2 and provide fixes if
> any bottlenecks come up.
> 8. Have all of the above prepared for the Vancouver summit and discuss
> the situation there.
> 
> Michael, I am still wondering, who's going to be responsible for timely
> reviews and approvals of the fixes and tests we're going to contribute
> to nova? So far this is the biggest risk. Is there anyway to allow some
> of us to participate in the process?

It would also be really helpful if there were reviews from you team on
any ec2 touching code.

https://review.openstack.org/#/q/file:%255Enova/api/ec2.*+status:open,n,z

There currently are only a few patches which touch ec2 that are ec2
function/bug related, and mostly don't have any scored reviews.
Especially this series -
https://review.openstack.org/#/q/status:open+project:openstack/nova+branch:master+topic:bp/ec2-volume-and-snapshot-tags,n,z


Which is a month old with no scoring.

-Sean

> 
> Best regards,
>   Alex Levine
> 
> On 2/2/15 2:46 AM, Michael Still wrote:
>> 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 here, but that's ok -- I'd like to
>> see us work through that as a team based on the merits.
>>
>> So... It sounds like we have an EC2 sub team forming. How do we get
>> that group meeting to come up with a transition plan?
>>
>> Michael
>>
>> On Sun, Feb 1, 2015 at 4:12 AM, Davanum Srinivas 
>> wrote:
>>> Alex,
>>>
>>> Very cool. thanks.
>>>
>>> -- dims
>>>
>>> On Sat, Jan 31, 2015 at 1:04 AM, Alexandre Levine
>>>  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 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 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 
> wrote:
>> 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 be able to iterate outside of the standard release cycle.
>>
>>
>>
>> --Randy
>>
>> VP, Technology, EMC Corporation
>> Formerly Founder & CEO, Cloudscaling (now a part of EMC)
>> +1 (415) 787-2253 [google voice]
>> TWITTER: twitter.com/randybias
>> LINKEDIN: linkedin.com/in/randybias
>> ASSISTANT: ren...@emc.com
>>
>>
>>
>>
>>
>>
>> On 1/29/15, 4:01 PM, "Michael Still"  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 here -- you can read the thread on openstack-dev for detail.
>>>
>>> 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).
>>>
>>> So, does the Foundation have a role here? The Nova team has
>>> failed to
>>> find someone to help us resolve these issues. Can the board perhaps
>>> find resources as the representatives of some of the largest
>>> contributors to OpenStack? Could the Foundation employ someone to
>>> help
>>> us our here?
>

Re: [openstack-dev] [OpenStack Foundation] Finding people to work on the EC2 API in Nova

[Sean Dague]

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
> persons are involved.
> 
> From the technical point of view the transition plan could look somewhat
> like this (sequence can be different):
> 
> 1. Triage EC2 bugs and fix showstoppers in nova's EC2.
> 2. Contribute Tempest tests for EC2 functionality and employ them
> against nova's EC2.
> 3. Write spec for required API to be exposed from nova so that we get
> full info.
> 4. Triage and fix all of the existing nova's EC2 bugs worth fixing.
> 5. Set up Tempest testing of the stackforge/ec2 (if that's possible).
> 6. Communicate and discover all of the existing questions and
> problematic points for the switching from existing EC2 API to the new
> one. Provide solutions or decisions about them.
> 7. Do performance testing of the new stackforge/ec2 and provide fixes if
> any bottlenecks come up.
> 8. Have all of the above prepared for the Vancouver summit and discuss
> the situation there.
> 
> Michael, I am still wondering, who's going to be responsible for timely
> reviews and approvals of the fixes and tests we're going to contribute
> to nova? So far this is the biggest risk. Is there anyway to allow some
> of us to participate in the process?

I am happy to volunteer to shephard these reviews. I'll try to keep an
eye on them, and if something is blocking please just ping me directly
on IRC in #openstack-nova or bring them forward to the weekly Nova meeting.

-Sean

-- 
Sean Dague
http://dague.net

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [OpenStack Foundation] Finding people to work on the EC2 API in Nova

[Alexandre Levine]

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 view the transition plan could look 
somewhat like this (sequence can be different):


1. Triage EC2 bugs and fix showstoppers in nova's EC2.
2. Contribute Tempest tests for EC2 functionality and employ them 
against nova's EC2.
3. Write spec for required API to be exposed from nova so that we get 
full info.

4. Triage and fix all of the existing nova's EC2 bugs worth fixing.
5. Set up Tempest testing of the stackforge/ec2 (if that's possible).
6. Communicate and discover all of the existing questions and 
problematic points for the switching from existing EC2 API to the new 
one. Provide solutions or decisions about them.
7. Do performance testing of the new stackforge/ec2 and provide fixes if 
any bottlenecks come up.
8. Have all of the above prepared for the Vancouver summit and discuss 
the situation there.


Michael, I am still wondering, who's going to be responsible for timely 
reviews and approvals of the fixes and tests we're going to contribute 
to nova? So far this is the biggest risk. Is there anyway to allow some 
of us to participate in the process?


Best regards,
  Alex Levine

On 2/2/15 2:46 AM, Michael Still wrote:

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 here, but that's ok -- I'd like to
see us work through that as a team based on the merits.

So... It sounds like we have an EC2 sub team forming. How do we get
that group meeting to come up with a transition plan?

Michael

On Sun, Feb 1, 2015 at 4:12 AM, Davanum Srinivas  wrote:

Alex,

Very cool. thanks.

-- dims

On Sat, Jan 31, 2015 at 1:04 AM, Alexandre Levine
 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 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 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  wrote:

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 be able to iterate outside of the standard release cycle.



--Randy

VP, Technology, EMC Corporation
Formerly Founder & CEO, Cloudscaling (now a part of EMC)
+1 (415) 787-2253 [google voice]
TWITTER: twitter.com/randybias
LINKEDIN: linkedin.com/in/randybias
ASSISTANT: ren...@emc.com






On 1/29/15, 4:01 PM, "Michael Still"  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 here -- you can read the thread on openstack-dev for detail.

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).

So, does the Foundation have a role here? The Nova team has failed to
find someone to help us resolve these issues. Can the board perhaps
find resources as the representatives of some of the largest
contributors to OpenStack? Could the Foundation employ someone to help
us our here?

I suspect the correct plan is to work on getting the stackforge
replacement finished, and ensuring that it is feature compatible with
the Nova implementation. However, I don't want to preempt the design
process -- there might be other ways forward here.

I feel that a continued discussion which just repeats the last 18
months wont actually fix the situation -- its time to "break out" of
that mode and find other ways to try and get someone working on this
problem.

Thoughts welcome.

Michael

--
Rackspace Australia

___
Foundation mailing list
foundat...@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/foundation



__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe:
openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev





__
OpenStack Development Mailing List (not for usage questions

Re: [openstack-dev] [OpenStack Foundation] Finding people to work on the EC2 API in Nova

[Daniel P. Berrange]

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 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, there would need 
> >>to support
> >>from the Nova team to enable these additional functions.  Having tables in 
> >>the EC2
> >>layer which get out of sync with those in the Nova layer would be a 
> >>significant
> >>problem in production.
> >Adding new APIs to Nova to support out of tree EC2 impl is perfectly 
> >reasonsable.
> >Indeed if there is data needed by EC2 that Nova doesn't provide already, 
> >chances
> >are that providing this data woudl be useful to other regular users / client 
> >apps
> >too. Just really needs someone to submit a spec with details of exactly which
> >functionality is missing. It shouldnt be hard for Nova cores to support it, 
> >given
> >the desire to see the out of tree EC2 impl take over & in tree impl removed.
> 
> We'll do the spec shortly.
> >
> >>I think this would merit a good slot in the Vancouver design sessions so we 
> >>can
> >>also discuss documentation, migration, packaging, configuration management,
> >>scaling, HA, etc.
> >I'd really strongly encourage the people working on this to submit the
> >detailed spec for the new APIs well before the Vancouver design summit.
> >Likewise at lesat document somewhere the thoughts on upgrade paths plans.
> >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.
> 
> We'll see about that also when all of the subjects we can think of or get
> questions about are covered somewhere in docs or specs. By the way - how do
> you usually do those online discussions? I mean what is the tooling?

I just mean discussions on this mailing list, or in the gerrit reviews
for the spec and/or patches

Regards,
Daniel
-- 
|: http://berrange.com  -o-http://www.flickr.com/photos/dberrange/ :|
|: http://libvirt.org  -o- http://virt-manager.org :|
|: http://autobuild.org   -o- http://search.cpan.org/~danberr/ :|
|: http://entangle-photo.org   -o-   http://live.gnome.org/gtk-vnc :|

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [OpenStack Foundation] Finding people to work on the EC2 API in Nova

[Alexandre Levine]

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, it is likely that there would need to be some 
additional
Nova APIs added to support the full EC2 semantics. Thus, there would need to 
support
from the Nova team to enable these additional functions.  Having tables in the 
EC2
layer which get out of sync with those in the Nova layer would be a significant
problem in production.

Adding new APIs to Nova to support out of tree EC2 impl is perfectly 
reasonsable.
Indeed if there is data needed by EC2 that Nova doesn't provide already, chances
are that providing this data woudl be useful to other regular users / client 
apps
too. Just really needs someone to submit a spec with details of exactly which
functionality is missing. It shouldnt be hard for Nova cores to support it, 
given
the desire to see the out of tree EC2 impl take over & in tree impl removed.


We'll do the spec shortly.



I think this would merit a good slot in the Vancouver design sessions so we can
also discuss documentation, migration, packaging, configuration management,
scaling, HA, etc.

I'd really strongly encourage the people working on this to submit the
detailed spec for the new APIs well before the Vancouver design summit.
Likewise at lesat document somewhere the thoughts on upgrade paths plans.
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.


We'll see about that also when all of the subjects we can think of or 
get questions about are covered somewhere in docs or specs. By the way - 
how do you usually do those online discussions? I mean what is the tooling?


Regards,
Daniel

Best regards,
  Alex Levine


__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [OpenStack Foundation] Finding people to work on the EC2 API in Nova

[Daniel P. Berrange]

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 
> additional
> Nova APIs added to support the full EC2 semantics. Thus, there would need to 
> support
> from the Nova team to enable these additional functions.  Having tables in 
> the EC2
> layer which get out of sync with those in the Nova layer would be a 
> significant
> problem in production.

Adding new APIs to Nova to support out of tree EC2 impl is perfectly 
reasonsable.
Indeed if there is data needed by EC2 that Nova doesn't provide already, chances
are that providing this data woudl be useful to other regular users / client 
apps
too. Just really needs someone to submit a spec with details of exactly which
functionality is missing. It shouldnt be hard for Nova cores to support it, 
given
the desire to see the out of tree EC2 impl take over & in tree impl removed.

> I think this would merit a good slot in the Vancouver design sessions so we 
> can
> also discuss documentation, migration, packaging, configuration management,
> scaling, HA, etc.

I'd really strongly encourage the people working on this to submit the
detailed spec for the new APIs well before the Vancouver design summit.
Likewise at lesat document somewhere the thoughts on upgrade paths plans.
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.

Regards,
Daniel
-- 
|: http://berrange.com  -o-http://www.flickr.com/photos/dberrange/ :|
|: http://libvirt.org  -o- http://virt-manager.org :|
|: http://autobuild.org   -o- http://search.cpan.org/~danberr/ :|
|: http://entangle-photo.org   -o-   http://live.gnome.org/gtk-vnc :|

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [OpenStack Foundation] Finding people to work on the EC2 API in Nova

[Michael Still]

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 here, but that's ok -- I'd like to
see us work through that as a team based on the merits.

So... It sounds like we have an EC2 sub team forming. How do we get
that group meeting to come up with a transition plan?

Michael

On Sun, Feb 1, 2015 at 4:12 AM, Davanum Srinivas  wrote:
> Alex,
>
> Very cool. thanks.
>
> -- dims
>
> On Sat, Jan 31, 2015 at 1:04 AM, Alexandre Levine
>  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 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 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  wrote:

 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 be able to iterate outside of the standard release cycle.



 --Randy

 VP, Technology, EMC Corporation
 Formerly Founder & CEO, Cloudscaling (now a part of EMC)
 +1 (415) 787-2253 [google voice]
 TWITTER: twitter.com/randybias
 LINKEDIN: linkedin.com/in/randybias
 ASSISTANT: ren...@emc.com






 On 1/29/15, 4:01 PM, "Michael Still"  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 here -- you can read the thread on openstack-dev for detail.
>
> 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).
>
> So, does the Foundation have a role here? The Nova team has failed to
> find someone to help us resolve these issues. Can the board perhaps
> find resources as the representatives of some of the largest
> contributors to OpenStack? Could the Foundation employ someone to help
> us our here?
>
> I suspect the correct plan is to work on getting the stackforge
> replacement finished, and ensuring that it is feature compatible with
> the Nova implementation. However, I don't want to preempt the design
> process -- there might be other ways forward here.
>
> I feel that a continued discussion which just repeats the last 18
> months wont actually fix the situation -- its time to "break out" of
> that mode and find other ways to try and get someone working on this
> problem.
>
> Thoughts welcome.
>
> Michael
>
> --
> Rackspace Australia
>
> ___
> Foundation mailing list
> foundat...@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/foundation



 __
 OpenStack Development Mailing List (not for usage questions)
 Unsubscribe:
 openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
 http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>>
>>>
>>>
>>
>>
>> __
>> OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
>
> --
> Davanum Srinivas :: https://twitter.com/dims
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev



-- 
Rackspace Australia

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [OpenStack Foundation] Finding people to work on the EC2 API in Nova

[Davanum Srinivas]

Alex,

Very cool. thanks.

-- dims

On Sat, Jan 31, 2015 at 1:04 AM, Alexandre Levine
 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 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 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  wrote:
>>>
>>> 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 be able to iterate outside of the standard release cycle.
>>>
>>>
>>>
>>> --Randy
>>>
>>> VP, Technology, EMC Corporation
>>> Formerly Founder & CEO, Cloudscaling (now a part of EMC)
>>> +1 (415) 787-2253 [google voice]
>>> TWITTER: twitter.com/randybias
>>> LINKEDIN: linkedin.com/in/randybias
>>> ASSISTANT: ren...@emc.com
>>>
>>>
>>>
>>>
>>>
>>>
>>> On 1/29/15, 4:01 PM, "Michael Still"  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 here -- you can read the thread on openstack-dev for detail.

 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).

 So, does the Foundation have a role here? The Nova team has failed to
 find someone to help us resolve these issues. Can the board perhaps
 find resources as the representatives of some of the largest
 contributors to OpenStack? Could the Foundation employ someone to help
 us our here?

 I suspect the correct plan is to work on getting the stackforge
 replacement finished, and ensuring that it is feature compatible with
 the Nova implementation. However, I don't want to preempt the design
 process -- there might be other ways forward here.

 I feel that a continued discussion which just repeats the last 18
 months wont actually fix the situation -- its time to "break out" of
 that mode and find other ways to try and get someone working on this
 problem.

 Thoughts welcome.

 Michael

 --
 Rackspace Australia

 ___
 Foundation mailing list
 foundat...@lists.openstack.org
 http://lists.openstack.org/cgi-bin/mailman/listinfo/foundation
>>>
>>>
>>>
>>> __
>>> OpenStack Development Mailing List (not for usage questions)
>>> Unsubscribe:
>>> openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>>
>>
>
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev



-- 
Davanum Srinivas :: https://twitter.com/dims

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [OpenStack Foundation] Finding people to work on the EC2 API in Nova

[Alexandre Levine]

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 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  wrote:

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 be able to iterate outside of the standard release cycle.



--Randy

VP, Technology, EMC Corporation
Formerly Founder & CEO, Cloudscaling (now a part of EMC)
+1 (415) 787-2253 [google voice]
TWITTER: twitter.com/randybias
LINKEDIN: linkedin.com/in/randybias
ASSISTANT: ren...@emc.com






On 1/29/15, 4:01 PM, "Michael Still"  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 here -- you can read the thread on openstack-dev for detail.

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).

So, does the Foundation have a role here? The Nova team has failed to
find someone to help us resolve these issues. Can the board perhaps
find resources as the representatives of some of the largest
contributors to OpenStack? Could the Foundation employ someone to help
us our here?

I suspect the correct plan is to work on getting the stackforge
replacement finished, and ensuring that it is feature compatible with
the Nova implementation. However, I don't want to preempt the design
process -- there might be other ways forward here.

I feel that a continued discussion which just repeats the last 18
months wont actually fix the situation -- its time to "break out" of
that mode and find other ways to try and get someone working on this
problem.

Thoughts welcome.

Michael

--
Rackspace Australia

___
Foundation mailing list
foundat...@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/foundation


__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev






__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [OpenStack Foundation] Finding people to work on the EC2 API in Nova

[Dean Troyer]

On Fri, Jan 30, 2015 at 5:21 PM, Davanum Srinivas  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 an external plugin
in the stackforge repo directly if they want to do the integration.  This
would allow local devstack runs to use it directly even if it doesn't get
in to the CI gate.

Most of the EC2 exercises in DevStack are broken and I plan to go ahead and
remove them soon, plus disabling n-crt and n-obj which both only exist to
support euca2ools bundling.

dt

-- 

Dean Troyer
dtro...@gmail.com
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [OpenStack Foundation] Finding people to work on the EC2 API in Nova

[Davanum Srinivas]

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  wrote:
> 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 be able to iterate outside of the standard release cycle.
>
>
>
> --Randy
>
> VP, Technology, EMC Corporation
> Formerly Founder & CEO, Cloudscaling (now a part of EMC)
> +1 (415) 787-2253 [google voice]
> TWITTER: twitter.com/randybias
> LINKEDIN: linkedin.com/in/randybias
> ASSISTANT: ren...@emc.com
>
>
>
>
>
>
> On 1/29/15, 4:01 PM, "Michael Still"  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 here -- you can read the thread on openstack-dev for detail.
>>
>>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).
>>
>>So, does the Foundation have a role here? The Nova team has failed to
>>find someone to help us resolve these issues. Can the board perhaps
>>find resources as the representatives of some of the largest
>>contributors to OpenStack? Could the Foundation employ someone to help
>>us our here?
>>
>>I suspect the correct plan is to work on getting the stackforge
>>replacement finished, and ensuring that it is feature compatible with
>>the Nova implementation. However, I don't want to preempt the design
>>process -- there might be other ways forward here.
>>
>>I feel that a continued discussion which just repeats the last 18
>>months wont actually fix the situation -- its time to "break out" of
>>that mode and find other ways to try and get someone working on this
>>problem.
>>
>>Thoughts welcome.
>>
>>Michael
>>
>>--
>>Rackspace Australia
>>
>>___
>>Foundation mailing list
>>foundat...@lists.openstack.org
>>http://lists.openstack.org/cgi-bin/mailman/listinfo/foundation
>
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev



-- 
Davanum Srinivas :: https://twitter.com/dims

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [OpenStack Foundation] Finding people to work on the EC2 API in Nova

[Matt Riedemann]

On 1/29/2015 7:42 PM, Michael Still wrote:

On Thu, Jan 29, 2015 at 5:15 PM, Michael Still  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:

https://bugs.launchpad.net/nova/+bugs?field.tag=ec2


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 project. That seems the best way forward at this point.

Thanks,
Michael

On 30 Jan 2015 11:11 am, "matt"  wrote:


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  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 here -- you can read the thread on openstack-dev for detail.

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).

So, does the Foundation have a role here? The Nova team has failed to
find someone to help us resolve these issues. Can the board perhaps
find resources as the representatives of some of the largest
contributors to OpenStack? Could the Foundation employ someone to help
us our here?

I suspect the correct plan is to work on getting the stackforge
replacement finished, and ensuring that it is feature compatible with
the Nova implementation. However, I don't want to preempt the design
process -- there might be other ways forward here.

I feel that a continued discussion which just repeats the last 18
months wont actually fix the situation -- its time to "break out" of
that mode and find other ways to try and get someone working on this
problem.

Thoughts welcome.

Michael

--
Rackspace Australia

___
Foundation mailing list
foundat...@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/foundation











Also the spec here:

https://review.openstack.org/#/c/147882/

--

Thanks,

Matt Riedemann


__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [OpenStack Foundation] Finding people to work on the EC2 API in Nova

[Bias, Randy]

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 be able to iterate outside of the standard release cycle.



--Randy

VP, Technology, EMC Corporation
Formerly Founder & CEO, Cloudscaling (now a part of EMC)
+1 (415) 787-2253 [google voice]
TWITTER: twitter.com/randybias
LINKEDIN: linkedin.com/in/randybias
ASSISTANT: ren...@emc.com






On 1/29/15, 4:01 PM, "Michael Still"  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 here -- you can read the thread on openstack-dev for detail.
>
>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).
>
>So, does the Foundation have a role here? The Nova team has failed to
>find someone to help us resolve these issues. Can the board perhaps
>find resources as the representatives of some of the largest
>contributors to OpenStack? Could the Foundation employ someone to help
>us our here?
>
>I suspect the correct plan is to work on getting the stackforge
>replacement finished, and ensuring that it is feature compatible with
>the Nova implementation. However, I don't want to preempt the design
>process -- there might be other ways forward here.
>
>I feel that a continued discussion which just repeats the last 18
>months wont actually fix the situation -- its time to "break out" of
>that mode and find other ways to try and get someone working on this
>problem.
>
>Thoughts welcome.
>
>Michael
>
>-- 
>Rackspace Australia
>
>___
>Foundation mailing list
>foundat...@lists.openstack.org
>http://lists.openstack.org/cgi-bin/mailman/listinfo/foundation


__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [OpenStack Foundation] Finding people to work on the EC2 API in Nova

[Alexandre Levine]

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 EC2 part of the nova? Or is it?


Best regards,
  Alex Levine

On 1/30/15 10:57 PM, 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 additional Nova APIs added to support the full EC2 semantics. 
Thus, there would need to support from the Nova team to enable these 
additional functions.  Having tables in the EC2 layer which get out of 
sync with those in the Nova layer would be a significant problem in 
production.


I think this would merit a good slot in the Vancouver design sessions 
so we can also discuss documentation, migration, packaging, 
configuration management, scaling, HA, etc.


Tim

*From:*matt [mailto:m...@nycresistor.com]
*Sent:* 30 January 2015 20:44
*To:* Alexandre Levine
*Cc:* foundat...@lists.openstack.org; OpenStack Development Mailing 
List (not for usage questions)
*Subject:* Re: [OpenStack Foundation] [openstack-dev] Finding people 
to work on the EC2 API in Nova


+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 
mailto: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 in acceptable state for
the time being as well.
If you can give us any permissions and leverage to not just
contribute fixes and tests but also have a say in approval of
those (maybe to just one of us) then it'll be fast. Otherwise
it'll happen in due time but our previous attempts to contribute
some fixes for EC2 API in nova took usually more than half a year
to get through.

Best regards
  Alex Levine

On 1/30/15 3:01 AM, Michael Still 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 here -- you can read the thread on openstack-dev for
detail.

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).

So, does the Foundation have a role here? The Nova team has
failed to
find someone to help us resolve these issues. Can the board
perhaps
find resources as the representatives of some of the largest
contributors to OpenStack? Could the Foundation employ someone
to help
us our here?

I suspect the correct plan is to work on getting the stackforge
replacement finished, and ensuring that it is feature
compatible with
the Nova implementation. However, I don't want to preempt the
design
process -- there might be other ways forward here.

I feel that a continued discussion which just repeats the last 18
months wont actually fix the situation -- its time to "break
out" of
that mode and find other ways to try and get someone working
on this
problem.

Thoughts welcome.

Michael

___
Foundation mailing list
foundat...@lists.openstack.org 
http://lists.openstack.org/cgi-bin/mailman/listinfo/foundation



__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [OpenStack Foundation] Finding people to work on the EC2 API in Nova

[Tim Bell]

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, there would 
need to support from the Nova team to enable these additional functions.  
Having tables in the EC2 layer which get out of sync with those in the Nova 
layer would be a significant problem in production.



I think this would merit a good slot in the Vancouver design sessions so we can 
also discuss documentation, migration, packaging, configuration management, 
scaling, HA, etc.


Tim

From: matt [mailto:m...@nycresistor.com]
Sent: 30 January 2015 20:44
To: Alexandre Levine
Cc: foundat...@lists.openstack.org; OpenStack Development Mailing List (not for 
usage questions)
Subject: Re: [OpenStack Foundation] [openstack-dev] Finding people to work on 
the EC2 API in Nova

+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 
mailto: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 in acceptable state for the time being as well.
If you can give us any permissions and leverage to not just contribute fixes 
and tests but also have a say in approval of those (maybe to just one of us) 
then it'll be fast. Otherwise it'll happen in due time but our previous 
attempts to contribute some fixes for EC2 API in nova took usually more than 
half a year to get through.

Best regards
  Alex Levine

On 1/30/15 3:01 AM, Michael Still 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 here -- you can read the thread on openstack-dev for detail.

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).

So, does the Foundation have a role here? The Nova team has failed to
find someone to help us resolve these issues. Can the board perhaps
find resources as the representatives of some of the largest
contributors to OpenStack? Could the Foundation employ someone to help
us our here?

I suspect the correct plan is to work on getting the stackforge
replacement finished, and ensuring that it is feature compatible with
the Nova implementation. However, I don't want to preempt the design
process -- there might be other ways forward here.

I feel that a continued discussion which just repeats the last 18
months wont actually fix the situation -- its time to "break out" of
that mode and find other ways to try and get someone working on this
problem.

Thoughts welcome.

Michael

___
Foundation mailing list
foundat...@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/foundation

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [OpenStack Foundation] Finding people to work on the EC2 API in Nova

[matt]

+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 
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 in acceptable state for the time being
> as well.
> If you can give us any permissions and leverage to not just contribute
> fixes and tests but also have a say in approval of those (maybe to just one
> of us) then it'll be fast. Otherwise it'll happen in due time but our
> previous attempts to contribute some fixes for EC2 API in nova took usually
> more than half a year to get through.
>
> Best regards
>   Alex Levine
>
> On 1/30/15 3:01 AM, Michael Still 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 here -- you can read the thread on openstack-dev for detail.
>>
>> 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).
>>
>> So, does the Foundation have a role here? The Nova team has failed to
>> find someone to help us resolve these issues. Can the board perhaps
>> find resources as the representatives of some of the largest
>> contributors to OpenStack? Could the Foundation employ someone to help
>> us our here?
>>
>> I suspect the correct plan is to work on getting the stackforge
>> replacement finished, and ensuring that it is feature compatible with
>> the Nova implementation. However, I don't want to preempt the design
>> process -- there might be other ways forward here.
>>
>> I feel that a continued discussion which just repeats the last 18
>> months wont actually fix the situation -- its time to "break out" of
>> that mode and find other ways to try and get someone working on this
>> problem.
>>
>> Thoughts welcome.
>>
>> Michael
>>
>>
>
> ___
> Foundation mailing list
> foundat...@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/foundation
>
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [OpenStack Foundation] Finding people to work on the EC2 API in Nova

[Stefano Maffulli]

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 hear is that EC2 is important and according to the user
survey there are users that seem to be using OpenStack's EC2 code. Nova
developers point out though that the EC2 code is broken and unusable. So
something is out of whack: either user report are more 'wishes' than
usage or the openstack code is not as bad or someone else is feeding
these users good code (that is not in openstack repositories) or
something else.

I would suggest that we start by reaching out to these users. 

Which questions shall we ask them? I'd start from:

* where did you get the EC2 API: vanilla openstack (version, etc) or via
a vendor? which vendor?
* how do you use the EC2 code? Anecdotes are enough I think at this
point.


Tim and user committee: do you think I or Tom can get the list of
respondents to the user survey who declared to use EC2 so we can ask
them more questions?

If not, we can start by asking on the operators list and blog posts and
wait for someone to come forward.




__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [OpenStack Foundation] Finding people to work on the EC2 API in Nova

[Michael Still]

On Thu, Jan 29, 2015 at 5:15 PM, Michael Still  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:

https://bugs.launchpad.net/nova/+bugs?field.tag=ec2

> 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 project. That seems the best way forward at this point.
>
> Thanks,
> Michael
>
> On 30 Jan 2015 11:11 am, "matt"  wrote:
>>
>> 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  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 here -- you can read the thread on openstack-dev for detail.
>>>
>>> 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).
>>>
>>> So, does the Foundation have a role here? The Nova team has failed to
>>> find someone to help us resolve these issues. Can the board perhaps
>>> find resources as the representatives of some of the largest
>>> contributors to OpenStack? Could the Foundation employ someone to help
>>> us our here?
>>>
>>> I suspect the correct plan is to work on getting the stackforge
>>> replacement finished, and ensuring that it is feature compatible with
>>> the Nova implementation. However, I don't want to preempt the design
>>> process -- there might be other ways forward here.
>>>
>>> I feel that a continued discussion which just repeats the last 18
>>> months wont actually fix the situation -- its time to "break out" of
>>> that mode and find other ways to try and get someone working on this
>>> problem.
>>>
>>> Thoughts welcome.
>>>
>>> Michael
>>>
>>> --
>>> Rackspace Australia
>>>
>>> ___
>>> Foundation mailing list
>>> foundat...@lists.openstack.org
>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/foundation
>>
>>
>



-- 
Rackspace Australia

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [OpenStack Foundation] Finding people to work on the EC2 API in Nova

[Michael Still]

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 project. That seems the best way forward at this
point.

Thanks,
Michael
On 30 Jan 2015 11:11 am, "matt"  wrote:

> 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  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 here -- you can read the thread on openstack-dev for detail.
>>
>> 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).
>>
>> So, does the Foundation have a role here? The Nova team has failed to
>> find someone to help us resolve these issues. Can the board perhaps
>> find resources as the representatives of some of the largest
>> contributors to OpenStack? Could the Foundation employ someone to help
>> us our here?
>>
>> I suspect the correct plan is to work on getting the stackforge
>> replacement finished, and ensuring that it is feature compatible with
>> the Nova implementation. However, I don't want to preempt the design
>> process -- there might be other ways forward here.
>>
>> I feel that a continued discussion which just repeats the last 18
>> months wont actually fix the situation -- its time to "break out" of
>> that mode and find other ways to try and get someone working on this
>> problem.
>>
>> Thoughts welcome.
>>
>> Michael
>>
>> --
>> Rackspace Australia
>>
>> ___
>> Foundation mailing list
>> foundat...@lists.openstack.org
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/foundation
>>
>
>
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [OpenStack Foundation] Finding people to work on the EC2 API in Nova

[Boris Pavlovic]

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  wrote:

> 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  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 here -- you can read the thread on openstack-dev for detail.
>>
>> 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).
>>
>> So, does the Foundation have a role here? The Nova team has failed to
>> find someone to help us resolve these issues. Can the board perhaps
>> find resources as the representatives of some of the largest
>> contributors to OpenStack? Could the Foundation employ someone to help
>> us our here?
>>
>> I suspect the correct plan is to work on getting the stackforge
>> replacement finished, and ensuring that it is feature compatible with
>> the Nova implementation. However, I don't want to preempt the design
>> process -- there might be other ways forward here.
>>
>> I feel that a continued discussion which just repeats the last 18
>> months wont actually fix the situation -- its time to "break out" of
>> that mode and find other ways to try and get someone working on this
>> problem.
>>
>> Thoughts welcome.
>>
>> Michael
>>
>> --
>> Rackspace Australia
>>
>> ___
>> Foundation mailing list
>> foundat...@lists.openstack.org
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/foundation
>>
>
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [OpenStack Foundation] Finding people to work on the EC2 API in Nova

[matt]

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  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 here -- you can read the thread on openstack-dev for detail.
>
> 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).
>
> So, does the Foundation have a role here? The Nova team has failed to
> find someone to help us resolve these issues. Can the board perhaps
> find resources as the representatives of some of the largest
> contributors to OpenStack? Could the Foundation employ someone to help
> us our here?
>
> I suspect the correct plan is to work on getting the stackforge
> replacement finished, and ensuring that it is feature compatible with
> the Nova implementation. However, I don't want to preempt the design
> process -- there might be other ways forward here.
>
> I feel that a continued discussion which just repeats the last 18
> months wont actually fix the situation -- its time to "break out" of
> that mode and find other ways to try and get someone working on this
> problem.
>
> Thoughts welcome.
>
> Michael
>
> --
> Rackspace Australia
>
> ___
> Foundation mailing list
> foundat...@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/foundation
>
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev