A unified tool for upgrading TripleO based deployments
In the past we had TripleO upgrades automation spread over several different repositories. This posed a couple of problems like maintaining automation code which does the same thing into multiple places, making it easy to diverge from the official documentation. Moreover each of them were usually tightly coupled to the environment deployment tool . This repository aims to provide a unified tool for upgrading TripleO based deployments by decoupling the upgrade automation code. It will allow users using different deployment tools such as tripleo-quickstart, Infrared or manual to run the upgrade workflow in an automated or semi-automated (by creating scripts containing the upgrade workflow steps which can be manually triggered) manner. Both minor version updates and major version upgrades are going to be covered by this tool.
Blueprint information
- Status:
- Complete
- Approver:
- Emilien Macchi
- Priority:
- High
- Drafter:
- Marius Cornea
- Direction:
- Approved
- Assignee:
- mathieu bultel
- Definition:
- Approved
- Series goal:
- Accepted for rocky
- Implementation:
-
Implemented
- Milestone target:
-
rocky-2
- Started by
- Emilien Macchi
- Completed by
- Emilien Macchi
Related branches
Related bugs
Sprints
Whiteboard
Queens has been released, updating goal for Rocky
[23-Jan-2018] Moving to Rocky at this point. Work is still in progress to use this new Ansible role in TripleO CI. See https:/
Create tripleo-upgrade project:
https:/
https:/
[Oct/5/
[Jan/16/
Gerrit topic: https:/
Addressed by: https:/
WIP: Upgrade UC and OC using tripleo-upgrade role
Gerrit topic: https:/
Addressed by: https:/
Set repo setup release in playbooks
Addressed by: https:/
Provide a way to change docker registry path during mixed upgrade.
Addressed by: https:/
Upgrade UC and OC using tripleo-upgrade role.
Gerrit topic: https:/
Gerrit topic: https:/
Addressed by: https:/
Add tripleo-upgrade to cloned projects for reproducer script
