Open Stack

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
> <alevine at cloudscaling.com> 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 <dkranz at redhat.com> 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-request at 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-request at 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-request at 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-request at lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev