yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #34621
[Bug 1458945] Re: Use graduated oslo.policy instead of oslo-incubator code
** Changed in: neutron
Status: Fix Committed => Fix Released
** Changed in: neutron
Milestone: None => liberty-1
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1458945
Title:
Use graduated oslo.policy instead of oslo-incubator code
Status in OpenStack Key Management (Barbican):
Fix Committed
Status in OpenStack Telemetry (Ceilometer):
Fix Released
Status in Cinder:
In Progress
Status in OpenStack Congress:
Fix Committed
Status in OpenStack Image Registry and Delivery Service (Glance):
Fix Released
Status in Orchestration API (Heat):
Fix Released
Status in OpenStack Dashboard (Horizon):
Fix Released
Status in OpenStack Bare Metal Provisioning Service (Ironic):
Fix Released
Status in OpenStack Identity (Keystone):
Fix Released
Status in MagnetoDB - key-value storage service for OpenStack:
Confirmed
Status in OpenStack Magnum:
New
Status in Manila:
New
Status in Mistral:
Invalid
Status in Murano:
Fix Committed
Status in OpenStack Neutron (virtual network service):
Fix Released
Status in OpenStack Compute (Nova):
Confirmed
Status in Rally:
Invalid
Status in OpenStack Data Processing (Sahara):
Fix Released
Status in OpenStack Object Storage (Swift):
Invalid
Status in Openstack Database (Trove):
Invalid
Bug description:
The Policy code is now be managed as a library, named oslo.policy.
If there is a CVE level defect, deploying a fix should require
deploying a new version of the library, not syncing each individual
project.
All the projects in the OpenStack ecosystem that are using the policy
code from oslo-incubator should use the new library.
To manage notifications about this bug go to:
https://bugs.launchpad.net/barbican/+bug/1458945/+subscriptions
References