tripleo deploy multinode
Add support for using openstack tripleo deploy to deploy multinode overclouds. Largely, it is already possible today, however there is some set of features that may not work or be supported, and this blueprint is meant to identify and track those features, as well as add documentation and supporting material.
CI may be a possibility, but it would require adding a multinode job, so is likely not ideal due to resource capacity.
There are some workflows/playbooks that rely on Swift on the undercloud. As Swift won't be present in a multinode deployment using tripleo deploy, this will also track adding the interfaces to those playbooks so that the Swift portion is pluggable with a different mechanism.
Blueprint information
- Status:
- Not started
- Approver:
- None
- Priority:
- Undefined
- Drafter:
- James Slagle
- Direction:
- Needs approval
- Assignee:
- James Slagle
- Definition:
- New
- Series goal:
- Accepted for victoria
- Implementation:
- Unknown
- Milestone target:
- victoria-3
- Started by
- Completed by
Related branches
Related bugs
Sprints
Whiteboard
Gerrit topic: https:/
Addressed by: https:/
Initially set rc to 0, not 1
Addressed by: https:/
Deprecate --standalone argument
Addressed by: https:/
Add --transport argument to tripleo deploy
Addressed by: https:/
Skip hostname check when running in a container
Addressed by: https:/
Use os.path.expanduser to get home dir
Addressed by: https:/
Allow unsafe_writes for /etc/hosts
Work Items
Work items:
Run tripleo deploy in a container: INPROGRESS
Deploy mulitnode with tripleo deploy: INPROGRESS
Add alternatives to swift in playbooks/roles: INPROGRESS