yahoo-eng-team team mailing list archive

[OpenStack Infra <1551836@xxxxxxxxxxxxxxxxxx>]

Reviewed:  https://review.openstack.org/265415
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=61e581c7d852a4227df32349f922ba8873784b21
Submitter: Jenkins
Branch:    master

commit 61e581c7d852a4227df32349f922ba8873784b21
Author: Michael Krotscheck <krotscheck@xxxxxxxxx>
Date:   Tue Mar 1 10:49:32 2016 -0800

    Added Keystone and RequestID headers to CORS middleware
    
    This patch makes use of oslo.config's genconfig hooks to add
    nova-specific default config values to the generated configuration.
    It also adds this same method to nova's configuration parsing logic,
    to ensure that these default values are also the ones used at runtime.
    
    Closes-bug: 1551836
    Change-Id: Ic799aea89f681ef8626e996f0357ade388f76ca9


** Changed in: nova
       Status: In Progress => Fix Released

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1551836

Title:
  CORS middleware's latent configuration options need to change

Status in Aodh:
  New
Status in Barbican:
  New
Status in Ceilometer:
  In Progress
Status in Cinder:
  In Progress
Status in cloudkitty:
  New
Status in congress:
  New
Status in Cue:
  New
Status in Designate:
  New
Status in Glance:
  In Progress
Status in heat:
  New
Status in Ironic:
  In Progress
Status in OpenStack Identity (keystone):
  Fix Released
Status in Magnum:
  New
Status in Manila:
  New
Status in Mistral:
  New
Status in Murano:
  New
Status in neutron:
  In Progress
Status in OpenStack Compute (nova):
  Fix Released
Status in oslo.config:
  Fix Released
Status in Sahara:
  In Progress
Status in OpenStack Search (Searchlight):
  In Progress
Status in Solum:
  New
Status in Trove:
  New

Bug description:
  It was pointed out in http://lists.openstack.org/pipermail/openstack-
  dev/2016-February/086746.html that configuration options included in
  paste.ini are less than optimal, because they impose an upgrade burden
  on both operators and engineers. The following discussion expanded to
  all projects (not just those using paste), and the following
  conclusion was reached:

  A) All generated configuration files should contain any headers which the API needs to operate. This is currently supported in oslo.config's generate-config script, as of 3.7.0
  B) These same configuration headers should be set as defaults for the given API, using cfg.set_defaults. This permits an operator to simply activate a domain, and not have to worry about tweaking additional settings.
  C) All hardcoded headers should be detached from the CORS middleware.
  D) Configuration and activation of CORS should be consistent across all projects.

  It was also agreed that this is a blocking bug for mitaka. A reference
  patch has already been approved for keystone, available here:
  https://review.openstack.org/#/c/285308/

To manage notifications about this bug go to:
https://bugs.launchpad.net/aodh/+bug/1551836/+subscriptions