← Back to team overview

yahoo-eng-team team mailing list archive

[Bug 1458945] [NEW] Use graduated oslo.policy instead of oslo-incubator code

 

Public bug reported:

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.

** Affects: cinder
     Importance: Undecided
         Status: New

** Affects: heat
     Importance: Undecided
         Status: New

** Affects: neutron
     Importance: Undecided
         Status: New

** Affects: nova
     Importance: Undecided
         Status: New

** Affects: swift
     Importance: Undecided
         Status: New

** Changed in: nova
     Assignee: (unassigned) => Samuel de Medeiros Queiroz (samueldmq)

** Also affects: nova
   Importance: Undecided
       Status: New

** Also affects: cinder
   Importance: Undecided
       Status: New

** Also affects: neutron
   Importance: Undecided
       Status: New

** Also affects: heat
   Importance: Undecided
       Status: New

** No longer affects: keystone

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Keystone.
https://bugs.launchpad.net/bugs/1458945

Title:
  Use graduated oslo.policy instead of oslo-incubator code

Status in Cinder:
  New
Status in Orchestration API (Heat):
  New
Status in OpenStack Neutron (virtual network service):
  New
Status in OpenStack Compute (Nova):
  New
Status in OpenStack Object Storage (Swift):
  New

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/cinder/+bug/1458945/+subscriptions


Follow ups

References