Switch to config-download as the default deployment mechanism

Registered by James Slagle on 2018-02-05

Switch to config-download as the default deployment mechanism. This would mostly just involve defaulting --config-download to True in tripleoclient.

Blueprint information

Status:
Complete
Approver:
James Slagle
Priority:
High
Drafter:
James Slagle
Direction:
Approved
Assignee:
James Slagle
Definition:
Approved
Series goal:
Accepted for rocky
Implementation:
Implemented
Milestone target:
milestone icon rocky-2
Started by
James Slagle on 2018-04-04
Completed by
James Slagle on 2018-04-23

Related branches

Sprints

Whiteboard

Gerrit topic: https://review.openstack.org/#q,topic:bp/config-download-default,n,z

Etherpad for CI jobs: https://etherpad.openstack.org/p/tripleo-ci-config-download

Addressed by: https://review.openstack.org/558927
    Switch to config-download by default

Addressed by: https://review.openstack.org/558925
    Switch to config-download by default

Addressed by: https://review.openstack.org/558931
    Remove adding config-download-environment.yaml

Addressed by: https://review.openstack.org/558965
    Convert remaining multinode jobs to config-download

Addressed by: https://review.openstack.org/559067
    Convert remaining ovb jobs to config-download

Addressed by: https://review.openstack.org/560030
    Convert remaining experimental ovb jobs to config-download

Addressed by: https://review.openstack.org/564315
    Add workflow for plan deployment status

Addressed by: https://review.openstack.org/564341
    overcloud plan deployment status

Addressed by: https://review.openstack.org/568673
    overcloud plan deployment failures

Gerrit topic: https://review.openstack.org/#q,topic:config-download-status,n,z

Addressed by: https://review.openstack.org/639803
    Add workflow for plan deployment status

(?)

Work Items

Dependency tree

* Blueprints in grey have been implemented.

This blueprint contains Public information 
Everyone can see this information.

Subscribers

No subscribers.