I looked at the Tempest change, it should be landable. I'll sign up for
review on these, as the rest of the patches are pretty straight forward.
-Sean
On 09/05/2014 06:32 PM, Michael Still wrote:
> So, this one is looking for one more core. Any takers?
>
> Michael
>
> On Sat, Sep 6, 2014 at 2:20 AM, Day, Phil <philip....@hp.com> wrote:
>> The corresponding Tempest change is also ready to roll (thanks to Ken'inci):
>> https://review.openstack.org/#/c/112474/1 so its kind of just a question
>> of getting the sequence right.
>>
>> Phil
>>
>>
>>> -----Original Message-----
>>> From: Sean Dague [mailto:s...@dague.net]
>>> Sent: 05 September 2014 17:05
>>> To: openstack-dev@lists.openstack.org
>>> Subject: Re: [openstack-dev] [nova] FFE server-group-quotas
>>>
>>> On 09/05/2014 11:28 AM, Ken'ichi Ohmichi wrote:
>>>> 2014-09-05 21:56 GMT+09:00 Day, Phil <philip....@hp.com>:
>>>>> Hi,
>>>>>
>>>>> I'd like to ask for a FFE for the 3 patchsets that implement quotas for
>>> server groups.
>>>>>
>>>>> Server groups (which landed in Icehouse) provides a really useful anti-
>>> affinity filter for scheduling that a lot of customers woudl like to use,
>>> but
>>> without some form of quota control to limit the amount of anti-affinity its
>>> impossible to enable it as a feature in a public cloud.
>>>>>
>>>>> The code itself is pretty simple - the number of files touched is a side-
>>> effect of having three V2 APIs that report quota information and the need to
>>> protect the change in V2 via yet another extension.
>>>>>
>>>>> https://review.openstack.org/#/c/104957/
>>>>> https://review.openstack.org/#/c/116073/
>>>>> https://review.openstack.org/#/c/116079/
>>>>
>>>> I am happy to sponsor this work.
>>>>
>>>> Thanks
>>>> Ken'ichi ohmichi
>>>>
>>>> _______________________________________________
>>>> OpenStack-dev mailing list
>>>> OpenStack-dev@lists.openstack.org
>>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>>
>>> These look like they are also all blocked by Tempest because it's changing
>>> return chunks. How does one propose to resolve that, as I don't think there
>>> is an agreed path up there for to get this into a passing state from my
>>> reading
>>> of the reviews.
>>>
>>> -Sean
>>>
>>> --
>>> Sean Dague
>>> http://dague.net
>>>
>>> _______________________________________________
>>> OpenStack-dev mailing list
>>> OpenStack-dev@lists.openstack.org
>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>> _______________________________________________
>> OpenStack-dev mailing list
>> OpenStack-dev@lists.openstack.org
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
>
--
Sean Dague
http://dague.net
_______________________________________________
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
