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>
This commit is contained in:
Javeria Khan 2016-03-01 11:36:55 -08:00
parent 13cd87f8aa
commit 4b0dd84e27
1 changed files with 3 additions and 3 deletions

View File

@ -78,7 +78,7 @@
- id: post_pg_license
role: ['primary-controller']
required_for: [post_deployment_end, setup-edge, setup-gateway]
required_for: [post_deployment_end, setup-edge]
requires: [post_deployment_start, director-fixes]
type: shell
parameters:
@ -87,7 +87,7 @@
- id: setup-edge
role: ['compute']
required_for: [post_deployment_end]
required_for: [post_deployment_end, setup-gateway]
requires: [post_deployment_start, post_pg_license]
type: puppet
parameters:
@ -98,7 +98,7 @@
- id: setup-gateway
role: ['PLUMgrid-Gateway']
required_for: [post_deployment_end, cleanup_os]
requires: [post_deployment_start, post_pg_license]
requires: [post_deployment_start, setup-edge]
type: puppet
parameters:
puppet_manifest: puppet/manifests/gateway.pp