Bug 1041538

Summary: [RFE][swift]: Global config module
Product: Red Hat OpenStack Reporter: RHOS Integration <rhos-integ>
Component: RFEsAssignee: RHOS Maint <rhos-maint>
Status: CLOSED UPSTREAM QA Contact:
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: unspecifiedCC: markmc, yeylon
Target Milestone: ---Keywords: FutureFeature
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
URL: https://blueprints.launchpad.net/swift/+spec/config-module
Whiteboard: upstream_milestone_none upstream_status_unknown upstream_definition_new
Fixed In Version: Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-03-19 16:48:52 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description RHOS Integration 2013-12-12 16:51:26 UTC 
Cloned from launchpad blueprint https://blueprints.launchpad.net/swift/+spec/config-module.

Description:

The idea is to make swift use oslo-cfg manager in order to keep consistency between projects.

It is becoming a real issue for some production enviroments that swift has some hardcoded paths to handle configuration and that its configuration parameters are splitted in more files with some extra complexity.

Some of the things that have came out are:

    * https://review.openstack.org/#/c/17004/ and
    * https://bugs.launchpad.net/swift/+bug/1091007 for more info.

For some code examples you can take a look here:

    * https://github.com/openstack/oslo-incubator/blob/master/openstack/common/cfg.py

It'll be important to keep backward compatibility with older swift versions which means, that it wont be a drop in implementation but it'll have to integrate somehow with the older configuration management giving a higher priority to the new structure.

Specification URL (additional information):

None