[openstack-dev] [oslo][neutron] oslo.policy: policy_dirs config option, why deprecated?
armamig at gmail.com
Mon Jul 6 19:13:24 UTC 2015
When reading , it seems that Doug is implying there will be the ability
to collate multiple policy.json files together? It would be good to get
this point clarified.
On 3 July 2015 at 22:12, Akihiro Motoki <amotoki at gmail.com> wrote:
> Hi Oslo and Neutron folks,
> Why is policy_dirs option deprecated in oslo.policy?
> In Neutron we have multiple repositories which consist of Neutron services
> and we would like to maintain policy.json separately.
> policy_dirs option looks useful for this purpose.
> == Detail ==
> Neutron project now consists of several repositories and
> they are imported when neutron-server runs.
> There are cases where it makes sense that each repository manages its
> and the neutron-server wants to load all related policy.json files.
> - advanced services have separate repositories and they evolve their API
> - vendor plugins/drivers in separate repositories (can) have
> vendor-specific extension API.
> (It is not a good thing from the point of the current API discussion,
> but we have now.)
> An easy way is to put all related policy.json into a single directory
> lile /etc/neutron/policy.d and specify this to policy_dirs option.
> Looking at oslo.policy (oslo_policy/opts),
> we have a comment policy_dirs option will be removed in M cycle.
> I read the commit message where this message was added but
> I am not sure why it is a problem.
> I would like to know the reason of the deprecation and
> discuss how we can handle our use cases.
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the OpenStack-dev