Browse Source

Make Edge & Gateway Deployment Sequential

- To ensure that Fuel CLI commands work for PG upgrads by
  specifying an end task, the gateway is now deployed
  after edge, so that the later is not missed

Change-Id: Iac2f118cebb3697025291a5942108435d7884014
Signed-off-by: Javeria Khan <javeriak@plumgrid.com>
Javeria Khan 3 years ago
parent
commit
4b0dd84e27
1 changed files with 3 additions and 3 deletions
  1. 3
    3
      deployment_tasks.yaml

+ 3
- 3
deployment_tasks.yaml View File

@@ -78,7 +78,7 @@
78 78
 
79 79
 - id: post_pg_license
80 80
   role: ['primary-controller']
81
-  required_for: [post_deployment_end, setup-edge, setup-gateway]
81
+  required_for: [post_deployment_end, setup-edge]
82 82
   requires: [post_deployment_start, director-fixes]
83 83
   type: shell
84 84
   parameters:
@@ -87,7 +87,7 @@
87 87
 
88 88
 - id: setup-edge
89 89
   role: ['compute']
90
-  required_for: [post_deployment_end]
90
+  required_for: [post_deployment_end, setup-gateway]
91 91
   requires: [post_deployment_start, post_pg_license]
92 92
   type: puppet
93 93
   parameters:
@@ -98,7 +98,7 @@
98 98
 - id: setup-gateway
99 99
   role: ['PLUMgrid-Gateway']
100 100
   required_for: [post_deployment_end, cleanup_os]
101
-  requires: [post_deployment_start, post_pg_license]
101
+  requires: [post_deployment_start, setup-edge]
102 102
   type: puppet
103 103
   parameters:
104 104
     puppet_manifest: puppet/manifests/gateway.pp

Loading…
Cancel
Save