Provide additional config with specific parameters per datastore
Now trove has guest_info config, formed and passed through nova file injections.
Current guest_info has datastore and guest_id.
Idea is to bring new kind of config:
it would store datastore specific parameters such mount point, manager, backup strategy and other datastore specific parameters.
Whole process would have next flow:
1. Jinja would load config with parameters with pattern /template/
2. Append it (with guest_id, etc.).
3. Performs file injection via heat/nova
launch.template would substitute guest_info totally.
What the value of such feature:
- Keeping clean main configs.
- Config hierarchy.
- Simple serverside configuring.
Blueprint information
- Status:
- Complete
- Approver:
- None
- Priority:
- Undefined
- Drafter:
- None
- Direction:
- Approved
- Assignee:
- Denis M.
- Definition:
- Obsolete
- Series goal:
- None
- Implementation:
- Slow progress
- Milestone target:
- next
- Started by
- Denis M.
- Completed by
- Nikhil Manchanda
Related branches
Related bugs
Sprints
Whiteboard
Rationale for the BP: for now there are several datastore-specific parameters in trove-guestagen
Gerrit topic: https:/
Addressed by: https:/
Provide guest_info per datastore
Work Items
Dependency tree
* Blueprints in grey have been implemented.