Open Stack

On 11/30/2017 07:00 PM, hieulq at vn.fujitsu.com wrote:
> Lance,
>
>>> For the Swift project, I don't see oslo.policy in requirements.txt for
>>> now, then not sure they need to implement policy in code and the we got the same
>> thing with Solum.
>> So does that mean these can be removed as well? I'm wondering if there is an official
>> process here, or just a simple sign-off from a project maintainer?
> Swift did not use oslo.policy and use their own mechanism instead, so I guess we can remove Swift along with remaining networking-* plugins as well.
>
> BTW, ceilometer had already deprecated and removed ceilometer API from Q, thus we can also remove ceilometer from the list too. [1]
>
> I have created PR regarding all above changes in [2].
Merged. Thanks for looking into this. New results should be available in
the burndown chart.
> Thanks,
> Hieu.
>
> [1]. https://github.com/openstack/ceilometer/commit/d881dd52289d453b9f9d94c7c32c0672a70a8064
> [2]. https://github.com/lbragstad/openstack-doc-migration-burndown/pull/1
>
>
>> -----Original Message-----
>> From: Lance Bragstad [mailto:lbragstad at gmail.com]
>> Sent: Thursday, November 30, 2017 10:41 PM
>> To: OpenStack Development Mailing List (not for usage questions) <openstack-
>> dev at lists.openstack.org>
>> Subject: Re: [openstack-dev] [all] [tc] Policy Goal Queens-2 Update
>>
>>
>>
>> On 11/29/2017 09:13 PM, daidv at vn.fujitsu.com wrote:
>>> Hi all,
>>>
>>> I just want to share some related things to anyone are interested in.
>>>
>>> For the Neutron projects, I have discussed with them[1] but it is not
>>> really started, they want to consider more about all of networking
>>> projects before and I'm still waiting for the feedback to define the right way to
>> implement policy-in-code for networking projects.
>>> For the other extensions of Neutron, we got some recommendations[2][3]
>>> that we no need to implement policy-in-code into those projects
>>> because we already register policy in Neutron, so I think we can remove neutron-
>> fwaas, neutron-dynamic-routing, neutron-lib or even other networking plugins out of
>> "Not Started" list.
>> Awesome, thanks for the update! I've gone ahead and removed these from the
>> burndown chart [0]. Let me know if there are any others that fall into this category and
>> I'll get things updated in the tracking tool.
>>
>> [0]
>> https://github.com/lbragstad/openstack-doc-migration-
>> burndown/commit/f34c2f56692230f104354240bf0e4378dc0fea82
>>> For the Swift project, I don't see oslo.policy in requirements.txt for
>>> now, then not sure they need to implement policy in code and the we got the same
>> thing with Solum.
>> So does that mean these can be removed as well? I'm wondering if there is an official
>> process here, or just a simple sign-off from a project maintainer?
>>> [1]
>>> http://eavesdrop.openstack.org/irclogs/%23openstack-neutron/%23opensta
>>> ck-neutron.2017-10-31.log.html [2]
>>> http://eavesdrop.openstack.org/irclogs/%23openstack-lbaas/%23openstack
>>> -lbaas.2017-10-06.log.html#t2017-10-06T02:50:10
>>> [3] https://review.openstack.org/#/c/509389/
>>>
>>> Dai
>>>
>>>
>> ___________________________________________________________________
>> ___
>>> ____ 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