Implement Tripleo Composable Upgrade Job in Tripleo Quickstart

Registered by mathieu bultel

Tripleo composable upgrade is not cover in Tripleo-quickstart yet.

This kind of deployment and test would be really help full for CI and development purpose.
It would allow the developers to work and test their code related to upgrade and allow the CI to test the reviews on Tripleo projects (tripleo-heat-templates, tripleo-common, python-tripleo-client ...).

The workflow of the job would be the following:
1/ deploy a master undercloud, because we don't want to test the Undercloud upgrade in this context. It save some duration of the job, and skip some issues or nits related to the undercloud itself.
2/ get the latest Newton Overcloud images and the stable/newton tripleo-heat-templates sources
3/ Deploy a newton overcloud with the required services (provided by the developer or set up in CI)
4/ Upgrade the newton overcloud to master (or ocata).
5/ Run sanity checks

This kind of workflow is already implemented in tripleo-ci project.

Blueprint information

Status:
Complete
Approver:
Emilien Macchi
Priority:
Medium
Drafter:
mathieu bultel
Direction:
Approved
Assignee:
None
Definition:
Approved
Series goal:
Accepted for queens
Implementation:
Implemented
Milestone target:
milestone icon queens-2
Started by
Emilien Macchi
Completed by
Alex Schultz

Related branches

Sprints

Whiteboard

[2017-12-08] This has been implemented

Tripleo quickstart extras review:
https://review.openstack.org/#/c/416480
Tripleo quickstart review:
https://review.openstack.org/410831

Gerrit topic: https://review.openstack.org/#q,topic:bp/tripleo-composable-upgrade-job,n,z

Addressed by: https://review.openstack.org/439598
    Allow complex upgrade deployment for N to O

Addressed by: https://review.openstack.org/449350
    Download rpm tht package for mixed upgrade

(emilien) status last time I checked was: tripleo quickstart supports upgrades from non-containerized to containerized overclouds but not from non-containerized to on-containerized yet (useful for existing stable branches).

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.