Delete Mistral environment after the migration
Once the tripleo-common patch removing the last references to the Mistral environment merges, the Mistral environment can be safely deleted. Related blueprint: stop-using-mistral-env Depends-On: Ieedecf92113142e43925131dcbccc4c0cd5b1a18 Change-Id: Iad819ee27a02ff00baf85304fdd950622cbcef25
This commit is contained in:
parent
a7f2a0a32a
commit
1fdeaafa32
|
@ -1404,10 +1404,7 @@ def _migrate_plans(mistral, swift, plans):
|
|||
env = mistral.environments.get(plan).variables
|
||||
yaml_string = yaml.safe_dump(env, default_flow_style=False)
|
||||
swift.put_object(plan, plan_env_filename, yaml_string)
|
||||
# TODO(jpichon): delete env from Mistral once triple-common
|
||||
# change merges (https://review.openstack.org/#/c/452291/).
|
||||
# Right now plan operations still expect a Mistral environment.
|
||||
# mistral.environments.delete(plan)
|
||||
mistral.environments.delete(plan)
|
||||
|
||||
|
||||
def _create_default_plan(mistral, plans, timeout=360):
|
||||
|
|
|
@ -0,0 +1,9 @@
|
|||
---
|
||||
upgrade:
|
||||
- |
|
||||
The environment configuration for deployments is now stored in a
|
||||
file called ``plan-environment.yaml`` that is stored in Swift
|
||||
together with the templates. Mistral is no longer used to store
|
||||
this data. ``openstack undercloud upgrade`` handles the migration
|
||||
of existing plans automatically, including the deletion of the
|
||||
Mistral environment.
|
Loading…
Reference in New Issue