Browse Source

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
tags/7.2.0
Julie Pichon 1 year ago
parent
commit
1fdeaafa32

+ 1
- 4
instack_undercloud/undercloud.py View File

@@ -1404,10 +1404,7 @@ def _migrate_plans(mistral, swift, plans):
1404 1404
             env = mistral.environments.get(plan).variables
1405 1405
             yaml_string = yaml.safe_dump(env, default_flow_style=False)
1406 1406
             swift.put_object(plan, plan_env_filename, yaml_string)
1407
-            # TODO(jpichon): delete env from Mistral once triple-common
1408
-            # change merges (https://review.openstack.org/#/c/452291/).
1409
-            # Right now plan operations still expect a Mistral environment.
1410
-            # mistral.environments.delete(plan)
1407
+            mistral.environments.delete(plan)
1411 1408
 
1412 1409
 
1413 1410
 def _create_default_plan(mistral, plans, timeout=360):

+ 9
- 0
releasenotes/notes/stop-using-mistral-env-41e6d19d999791dd.yaml View File

@@ -0,0 +1,9 @@
1
+---
2
+upgrade:
3
+  - |
4
+    The environment configuration for deployments is now stored in a
5
+    file called ``plan-environment.yaml`` that is stored in Swift
6
+    together with the templates. Mistral is no longer used to store
7
+    this data. ``openstack undercloud upgrade`` handles the migration
8
+    of existing plans automatically, including the deletion of the
9
+    Mistral environment.

Loading…
Cancel
Save