Enable validation of services configuration files
Each OpenStack service on each node is parameterized by a set of configuration files describing the value of the various configuration options. Configuration options from distinct nodes are not independent and follow business rules of various kinds. Today administrators take on the control of these rules. Congress could be used to enforce those constraints if the configuration files were available for processing. Although Congress is usually used for more dynamic data coming from running instances, nothing precludes the use of more static data sources.
Blueprint information
- Status:
- Complete
- Approver:
- None
- Priority:
- Medium
- Drafter:
- Valentin Matton
- Direction:
- Approved
- Assignee:
- None
- Definition:
- Approved
- Series goal:
- Accepted for queens
- Implementation:
-
Implemented
- Milestone target:
-
queens-3
- Started by
- Anusha
- Completed by
- Anusha
Related branches
Related bugs
Sprints
Whiteboard
Gerrit topic: https:/
Addressed by: https:/
Agent for configuration file validation
Addressed by: https:/
Datasource for configuration file validation
Addressed by: https:/
Builtins for configuration file validation
Addressed by: https:/
Devstack integration for configuration file validation
Addressed by: https:/
Documentation of the config datasource.
Addressed by: https:/
Add Tempest test for Configuration file validation
