Overcloud Upgrades work for Newton
[EDIT: August 2016]: After discussion (partly during the upstream tripleo weekly at http://
For now we will use launchpad bugs to track the lifecycle related work for newton (major upgrades, minor updates and mixed version support). The tag is: https:/
Original bp text below. I will also retarget this bp from n3 now.
=======
This blueprint is intended to act as an umbrella/tracking blueprint for the various items of work related to upgrading your deployment during the Newton cycle. As such it will be targetted to N3, to reflect that it covers the entire cycle. There are a number of dependent blueprints, bugs and reviews that will be tracked here and they can each individually be targetted at particular milestones (most likely N2 at this point).
There are a number of changes coming in Newton which will directly impact upgrades - including the composable services work, tracked at [1] and the move towards an evolved pacemaker architecture for controller services, tracked at [2].
The main items of work identied thus far are then to:
--> adapt the existing workflow to allow upgrade from mitaka to master (newton), at https:/
--> rework the upgrades workflow to a more service oriented approach (versus upgrading of nodes), at https:/
--> ensuring minor version package updates continue to work for newton, at https:/
--> documentation - the existing upgrades workflow is in progress at [3]
--> getting a ci job that exercises the major version upgrades, tracking bug filed at https:/
[1] https:/
[2] https:/
[3] "Upgrade documentation" https:/
Blueprint information
- Status:
- Complete
- Approver:
- Steven Hardy
- Priority:
- Essential
- Drafter:
- Marios Andreou
- Direction:
- Approved
- Assignee:
- Jiří Stránský
- Definition:
- Approved
- Series goal:
- Accepted for newton
- Implementation:
-
Implemented
- Milestone target:
- None
- Started by
- Steven Hardy
- Completed by
- Emilien Macchi
Related branches
Sprints
Work Items
Dependency tree
* Blueprints in grey have been implemented.
