Public bug reported: 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/ ** Affects: aodh Importance: Undecided Status: New ** Affects: barbican Importance: Undecided Status: New ** Affects: ceilometer Importance: Undecided Status: New ** Affects: cinder Importance: Undecided Status: New ** Affects: cloudkitty Importance: Undecided Status: New ** Affects: congress Importance: Undecided Status: New ** Affects: cue Importance: Undecided Status: New ** Affects: designate Importance: Undecided Status: New ** Affects: glance Importance: Undecided Status: New ** Affects: heat Importance: Undecided Status: New ** Affects: ironic Importance: Undecided Status: New ** Affects: keystone Importance: Undecided Assignee: Michael (krotscheck) Status: Fix Committed ** Affects: magnum Importance: Undecided Status: New ** Affects: manila Importance: Undecided Status: New ** Affects: mistral Importance: Undecided Status: New ** Affects: murano Importance: Undecided Status: New ** Affects: neutron Importance: Undecided Status: New ** Affects: nova Importance: Undecided Status: New ** Affects: sahara Importance: Undecided Status: New ** Affects: searchlight Importance: Undecided Status: New ** Affects: solum Importance: Undecided Status: New ** Affects: trove Importance: Undecided Status: New ** Also affects: nova Importance: Undecided Status: New ** Also affects: solum Importance: Undecided Status: New ** Also affects: heat Importance: Undecided Status: New ** Also affects: aodh Importance: Undecided Status: New ** Also affects: mistral Importance: Undecided Status: New ** Also affects: designate Importance: Undecided Status: New ** Also affects: searchlight Importance: Undecided Status: New ** Also affects: manila Importance: Undecided Status: New ** Also affects: barbican Importance: Undecided Status: New ** Also affects: congress Importance: Undecided Status: New ** Also affects: neutron Importance: Undecided Status: New ** Also affects: cinder Importance: Undecided Status: New ** Also affects: ceilometer Importance: Undecided Status: New ** Also affects: magnum Importance: Undecided Status: New ** Also affects: sahara Importance: Undecided Status: New ** Also affects: trove Importance: Undecided Status: New ** Also affects: murano Importance: Undecided Status: New ** Also affects: glance Importance: Undecided Status: New ** Also affects: cue Importance: Undecided Status: New ** Also affects: keystone Importance: Undecided Status: New ** Changed in: keystone Status: New => Fix Committed ** Changed in: keystone Assignee: (unassigned) => Michael (krotscheck) ** Also affects: cloudkitty Importance: Undecided Status: New -- 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: New Status in Cinder: New Status in cloudkitty: New Status in congress: New Status in Cue: New Status in Designate: New Status in Glance: New Status in heat: New Status in Ironic: New Status in OpenStack Identity (keystone): Fix Committed Status in Magnum: New Status in Manila: New Status in Mistral: New Status in Murano: New Status in neutron: New Status in OpenStack Compute (nova): New Status in Sahara: New Status in OpenStack Search (Searchlight): New 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 -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp