As a developer I would like to use merge.py and pass in Tuskar params
Registered by
Marios Andreou
tripleo-templates are 'complete' - ours are broken down (merge.py takes care of any duplication etc). Need to better understand how this works so we can generate overcloud.yaml using that.
need to work out how to pass (tuskar specific) params into merge.py - like baremetal node id for placement of compute, control etc images onto machines via avaiabilityzone: nova::baremetal
This isn't a blueprint level item IMO - it's simple code hygiene / no duplication. - We have a huge number of blueprints and need to contain that for planning sanity.
Blueprint information
- Status:
- Complete
- Approver:
- None
- Priority:
- Undefined
- Drafter:
- None
- Direction:
- Needs approval
- Assignee:
- Marios Andreou
- Definition:
- Obsolete
- Series goal:
- None
- Implementation:
-
Unknown
- Milestone target:
- None
- Started by
- Completed by
- Robert Collins
Related branches
Related bugs
Sprints
Whiteboard
Addressed by: https:/
WIP : sketch of what using merge.py looks like for tuskar.
(?)
Work Items
Dependency tree
* Blueprints in grey have been implemented.
