Browse Source

Don't manage bridge mappings in scenario file

The bridge mappings should be managed in the standalone parameters. This
bridge mapping prevents us from being able to change the datacentre
mapping in CI.

Change-Id: I6b5b9db75a11c2347720258a39b03aa28702dbf1
Related-Bug: #1895822
changes/00/757900/4
Alex Schultz 6 months ago
committed by Sergii Golovatiuk
parent
commit
c86fa4fb4e
1 changed files with 0 additions and 1 deletions
  1. +0
    -1
      ci/environments/scenario012-standalone.yaml

+ 0
- 1
ci/environments/scenario012-standalone.yaml View File

@ -28,4 +28,3 @@ parameter_defaults:
NeutronFlatNetworks: datacentre
NeutronNetworkVLANRanges: 'datacentre:500:599,tenant:300:399'
ML2HostConfigs: { "net-ans-br": { "ansible_network_os": "openvswitch", "ansible_host": "127.0.0.1", "ansible_user": "root", "ansible_ssh_private_key_file": "/etc/puppet/ci-key"}}
NeutronBridgeMappings: 'datacentre:br-ex,tenant:br-tenant'

Loading…
Cancel
Save