config.generator could not handle split configs
Bug #1300546 reported by
Zhi Yan Liu
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Glance |
Fix Released
|
Medium
|
Zhi Yan Liu | ||
oslo-incubator |
Fix Released
|
High
|
Unassigned |
Bug Description
Current config.generator could not handle split configs for the different services within a project, all configurations be collected and save to a single large template file. But for most project, the code repo contains more then one service, like nova repo/project contains nova-api, nova-compute. So the single template file is hard to be used/maintained for separated service. IMO, it will be cool if config.generator could generate separated configs based on service instead of project.
Example of "split configs" is glance-api.conf versus glance-
tags: | added: config |
description: | updated |
Changed in glance: | |
assignee: | nobody → Zhi Yan Liu (lzy-dev) |
Changed in oslo: | |
milestone: | none → juno-2 |
status: | Fix Committed → Fix Released |
Changed in glance: | |
milestone: | none → juno-rc1 |
importance: | Undecided → Medium |
Changed in glance: | |
status: | Fix Committed → Fix Released |
Changed in glance: | |
milestone: | juno-rc1 → 2014.2 |
To post a comment you must log in.
This is blocking Glance's adoption of the config generator, so we need to figure out some solution here.