Because we branched tripleoclient before other TripleO projects,
some changes in THT broke tripleoclient from stable/newton, and we need
to backport a serie of patches together otherwise they will never pass
CI.
Backport #1:
NTP arg should be optional when specified in an environment
For HA deploy, NTP parameter presence is made mandatory, but it should
be optional if NtpServer parameter has been provided via environment yaml.
Closes-Bug: 1577928
(cherry picked from commit 3ef0a4b889)
Backport #2:
Add 'openstack overcloud plan create' command
This uses the new Mistral actions and workflows to create a
plan with the tripleo heat templates. Templates can either
be provided by the user or the default templates on the
undercloud can be used.
Closes-Bug: #1616014
(cherry picked from commit 2c0fecf69c)
Backport #3:
Update the 'overcloud deploy --templates' command to use Mistral
This is a backwards compatible version of the deploy command
which uses the new Mistral workflows to power the deploy.
Depends-On: I7a61bf6fb71cc4a26aaf4322f2215683aafe20f3
(cherry picked from commit c03ed23272)
Backport #4:
Get template contents from plan, not local path
This allows the new overcloud.j2.yaml format, which is
rendered to create the overcloud.yaml file in the swift
plan via the tripleo.process_templates action
Note it may be valid to modify the roles_data prior to an update,
so we need a plan update workflow that can re-run the process_templates
step.
Partially-Implements: blueprint custom-roles
(cherry picked from commit 2898e7595f)
Backport #5:
Update plan files when re-deploying
When doing a second deploy we need to update the plan templates to match those
passed into the deploy command. The cleanest way to do this is to remove the
existing files in swift and then upload the new files.
Closes-Bug: #1620932
(cherry picked from commit 943f550415)
Change-Id: I55862204ef71f69bc88c79fe2259f7cb8365699b
98656b5717