[library] different neutron physical networks

[Eugene Korekin]

Currently, it's impossible to create multiple physnets with Fuel.
This functionality is desired by our partners.

Please provide the ability to define multiple neutron physical networks.

[Sergey Vasilenko (xenolog)]

looks like we should authomate parse of
quantum_settings/L2/phys_nets for dynamically creating physnets and check existings of required bridges.

[Igor Gajsin (igajsin)]

Also this functionality affects to the vmware-dvs plugin. The vmware-dvs driver allows working with multiple physnets but plugin can't use it due to the fact that neutron doesn't provide it.

[Michaël Van de Borne (mikemowgli)]

in Fuel 7, the $phys_nets variable already seems parsed by /etc/puppet/modules/osnailyfacter/modular/openstack-network/openstack-network-controller.pp
However, there are some limitations:
* there can only be 2 physical networks
* they have to be named 'physnet1' and 'physnet2'
* vlan_range from physnet1 isn't parsed, only physnet2 vlan_range is processed
* having phys_nets enabled doesn't seem to enforce l3_agent settings 'external_network_bridge' and 'gateway_external_network_id' to be empty and uncommented (as they should necessarily be in a multi ext net setup)

[Michaël Van de Borne (mikemowgli)]

Moreover, there is a comment in that same openstack-network-controller.pp saying this piece of code should belon to somewhere else.

[Sergey Vasilenko (xenolog)]

Fixed in 8.0 while implementing blueprint: dyn-gen-physnet-set.

[Sergey Vasilenko (xenolog)]

Change-Id: I8acee213a19d26e3d1fc1ad7595ee15d35e97f4d

[Atsuko Ito (yottatsa)]

spec link https://specs.openstack.org/openstack/fuel-specs/specs/8.0/dyn-gen-physnet-set.html

[Mikhail Samoylov (msamoylov)]

Verified in:
[root@nailgun ~]# cat /etc/fuel/version.yaml
VERSION:
  feature_groups:
    - mirantis
  production: "docker"
  release: "8.0"
  api: "1.0"
  build_number: "570"
  build_id: "570"
  fuel-nailgun_sha: "558ca91a854cf29e395940c232911ffb851899c1"
  python-fuelclient_sha: "4f234669cfe88a9406f4e438b1e1f74f1ef484a5"
  fuel-agent_sha: "658be72c4b42d3e1436b86ac4567ab914bfb451b"
  fuel-nailgun-agent_sha: "b2bb466fd5bd92da614cdbd819d6999c510ebfb1"
  astute_sha: "b81577a5b7857c4be8748492bae1dec2fa89b446"
  fuel-library_sha: "c2a335b5b725f1b994f78d4c78723d29fa44685a"
  fuel-ostf_sha: "3bc76a63a9e7d195ff34eadc29552f4235fa6c52"
  fuel-mirror_sha: "fb45b80d7bee5899d931f926e5c9512e2b442749"
  fuelmenu_sha: "78ffc73065a9674b707c081d128cb7eea611474f"
  shotgun_sha: "63645dea384a37dde5c01d4f8905566978e5d906"
  network-checker_sha: "a43cf96cd9532f10794dce736350bf5bed350e9d"
  fuel-upgrade_sha: "616a7490ec7199f69759e97e42f9b97dfc87e85b"
  fuelmain_sha: "d605bcbabf315382d56d0ce8143458be67c53434"

1. Create cluster and download settings for cluster
fuel deployment --env 1 --default

2.On controller and compute add in quantum_settings: L2: phys_nets: following strings
     physnet3:
       bridge: br-prv3
       vlan_range: 1000:1030
and to network_scheme: transformations: following
 - name: br-prv3
   provider: ovs
   action: add-br
3. Upload settings:
fuel deployment --env 1 --upload
4. Deploy cluster
5. Check /etc/neutron/plugins/ml2/ml2_conf.ini

Good output for step 5:
root@node-1:~# cat /etc/neutron/plugins/ml2/ml2_conf.ini | grep physnet3
physical_network_mtus =physnet3:1500,physnet2:1500,physnet1:1500
network_vlan_ranges =physnet3:1040:1050,physnet2:1000:1030,physnet1
bridge_mappings=physnet3:br-prv3,physnet2:br-prv,physnet1:br-floating