Workflows Assuming a Single Plan is Associated with a Single Stack

[Ryan Brady]

The actions and workflows for deploying a stack or deleting a plan assume that a single plan is associated with a single stack name. This doesn't allow an operator to create multiple plans and deploy a stack from a selected plan with a different name. e.g. operator creates and overcloud plan and overcloud-test plan. The user should be able to chose either plan to deploy a stack named 'overcloud'.

If an operator creates a stack named "overcloud" with a given plan, do we need to attempt to keep them from deleting the plan used for a current running stack?

[Ryan Brady (rbrady)]

Possible approach:

 - remove constraint for deleting plan while stack exists
 - add argument to deployment workflow and associated actions for passing stack name

[Ryan Brady (rbrady)]

Proposed patch: https://review.openstack.org/#/c/363950/

[Ryan Brady (rbrady)]

While this bug is specific to "workflows", the validations including the script to run ansible take an argument of a plan and use it for finding a stack as well.

[Ryan Brady (rbrady)]

Please see the discussion in the comments of https://review.openstack.org/#/c/363950/.

This bug needs additional discussion.

[Steven Hardy (shardy)]

Deferring to ocata since this requires further discussion

[OpenStack Infra (hudson-openstack)]

Change abandoned by Ryan Brady (<email address hidden>) on branch: master
Review: https://review.openstack.org/363950
Reason: This needs more planning and discussion. Revisiting later in Ocata.

[Steven Hardy (shardy)]

I'll mark this wontfix as it seems from the discussions folks are OK with coupling a plan to a deployed stack (as opposed to a plan that can be reused, which is what I originally expected).