Re: [openstack-dev] [Sahara][FFE] Requesting exception for Swift trust authentication blueprint

2014-09-09 Thread Sergey Lukjanov
As Thierry said, for Sahara we don't need to find review sponsors. We
discussed the list of bps proposed for rc1 and I've just mailed the
list of approved FFEs for Sahara in juno:

http://lists.openstack.org/pipermail/openstack-dev/2014-September/045448.html

Thanks.

On Fri, Sep 5, 2014 at 7:48 PM, Thierry Carrez  wrote:
> Smaller review teams don't really need to line up core sponsors as much
> as Nova does. As long as Sergey and myself are fine with it, you can go
> for it. I'm +1 on this one becauise it's actually a security bug we need
> to plug before release.
>
> Trevor McKay wrote:
>> Not sure how this is done, but I'm a core member for Sahara, and I
>> hereby sponsor it.
>>
>> On Fri, 2014-09-05 at 09:57 -0400, Michael McCune wrote:
>>> hey folks,
>>>
>>> I am requesting an exception for the Swift trust authentication 
>>> blueprint[1]. This blueprint addresses a security bug in Sahara and 
>>> represents a significant move towards increased security for Sahara 
>>> clusters. There are several reviews underway[2] with 1 or 2 more starting 
>>> today or monday.
>>>
>>> This feature is initially implemented as optional and as such will have 
>>> minimal impact on current user deployments. By default it is disabled and 
>>> requires no additional configuration or management from the end user.
>>>
>>> My feeling is that there has been vigorous debate and discussion 
>>> surrounding the implementation of this blueprint and there is consensus 
>>> among the team that these changes are needed. The code reviews for the bulk 
>>> of the work have been positive thus far and I have confidence these patches 
>>> will be accepted within the next week.
>>>
>>> thanks for considering this exception,
>>> mike
>>>
>>>
>>> [1]: 
>>> https://blueprints.launchpad.net/sahara/+spec/edp-swift-trust-authentication
>>> [2]: 
>>> https://review.openstack.org/#/q/status:open+topic:bp/edp-swift-trust-authentication,n,z
>>>
>>> ___
>>> 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
>>
>
>
> --
> Thierry Carrez (ttx)
>
> ___
> OpenStack-dev mailing list
> OpenStack-dev@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev



-- 
Sincerely yours,
Sergey Lukjanov
Sahara Technical Lead
(OpenStack Data Processing)
Principal Software Engineer
Mirantis Inc.

___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


Re: [openstack-dev] [Sahara][FFE] Requesting exception for Swift trust authentication blueprint

2014-09-05 Thread Thierry Carrez
Smaller review teams don't really need to line up core sponsors as much
as Nova does. As long as Sergey and myself are fine with it, you can go
for it. I'm +1 on this one becauise it's actually a security bug we need
to plug before release.

Trevor McKay wrote:
> Not sure how this is done, but I'm a core member for Sahara, and I
> hereby sponsor it.
> 
> On Fri, 2014-09-05 at 09:57 -0400, Michael McCune wrote:
>> hey folks,
>>
>> I am requesting an exception for the Swift trust authentication 
>> blueprint[1]. This blueprint addresses a security bug in Sahara and 
>> represents a significant move towards increased security for Sahara 
>> clusters. There are several reviews underway[2] with 1 or 2 more starting 
>> today or monday.
>>
>> This feature is initially implemented as optional and as such will have 
>> minimal impact on current user deployments. By default it is disabled and 
>> requires no additional configuration or management from the end user.
>>
>> My feeling is that there has been vigorous debate and discussion surrounding 
>> the implementation of this blueprint and there is consensus among the team 
>> that these changes are needed. The code reviews for the bulk of the work 
>> have been positive thus far and I have confidence these patches will be 
>> accepted within the next week.
>>
>> thanks for considering this exception,
>> mike
>>
>>
>> [1]: 
>> https://blueprints.launchpad.net/sahara/+spec/edp-swift-trust-authentication
>> [2]: 
>> https://review.openstack.org/#/q/status:open+topic:bp/edp-swift-trust-authentication,n,z
>>
>> ___
>> 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
> 


-- 
Thierry Carrez (ttx)

___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


Re: [openstack-dev] [Sahara][FFE] Requesting exception for Swift trust authentication blueprint

2014-09-05 Thread Trevor McKay
Not sure how this is done, but I'm a core member for Sahara, and I
hereby sponsor it.

On Fri, 2014-09-05 at 09:57 -0400, Michael McCune wrote:
> hey folks,
> 
> I am requesting an exception for the Swift trust authentication blueprint[1]. 
> This blueprint addresses a security bug in Sahara and represents a 
> significant move towards increased security for Sahara clusters. There are 
> several reviews underway[2] with 1 or 2 more starting today or monday.
> 
> This feature is initially implemented as optional and as such will have 
> minimal impact on current user deployments. By default it is disabled and 
> requires no additional configuration or management from the end user.
> 
> My feeling is that there has been vigorous debate and discussion surrounding 
> the implementation of this blueprint and there is consensus among the team 
> that these changes are needed. The code reviews for the bulk of the work have 
> been positive thus far and I have confidence these patches will be accepted 
> within the next week.
> 
> thanks for considering this exception,
> mike
> 
> 
> [1]: 
> https://blueprints.launchpad.net/sahara/+spec/edp-swift-trust-authentication
> [2]: 
> https://review.openstack.org/#/q/status:open+topic:bp/edp-swift-trust-authentication,n,z
> 
> ___
> 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