Open Stack

Hi,

We have a *lot* of configuration knobs in DevStack for Neutron. I am not
a smart man, so I think we may need to wrap our arms around this and
simplify.

Here's an example.

Can you tell me the difference between

PUBLIC_PHYSICAL_NETWORK and PHYSICAL_NETWORK? 

I had a local.conf with the following:

[[local|localrc]]
HOST_IP=203.0.113.2
FLAT_INTERFACE=eth1
PUBLIC_INTERFACE=eth1
FIXED_RANGE=10.0.0.0/24
FLOATING_RANGE=203.0.113.0/24
PUBLIC_NETWORK_GATEWAY=203.0.113.1

disable_service n-net
enable_service q-svc
enable_service q-agt
enable_service q-dhcp
enable_service q-meta
enable_service q-l3

Q_USE_SECGROUP=True
ENABLE_TENANT_VLANS=True
TENANT_VLAN_RANGE=3001:4000
PHYSICAL_NETWORK=default
OVS_PHYSICAL_BRIDGE=br-ex
Q_L3_ENABLED=True
Q_FLOATING_ALLOCATION_POOL=start=203.0.113.3,end=203.0.113.254

Q_USE_PROVIDERNET_FOR_PUBLIC=True


Which causes the following error during creation:

++ neutron net-create public -- --router:external=True --provider:network_type=flat --provider:physical_network=public
++ grep ' id '
++ get_field 2
++ local data field
++ read data
Invalid input for operation: physical_network 'public' unknown for flat provider network.
+ EXT_NET_ID=
+ die_if_not_set 586 EXT_NET_ID 'Failure creating EXT_NET_ID for public'


Because the bridge mappings file is set as:

bridge_mappings = default:br-ex

Now, fixing the --physical_network to be "default", which I defined in
PHYSICAL_NETWORK in local.conf allows the creation.

vagrant at vagrant-ubuntu-trusty-64:~/devstack$ neutron net-create public -- --router:external=True --provider:network_type=flat --provider:physical_network=default
Created a new network:
+---------------------------+--------------------------------------+
| Field                     | Value                                |
+---------------------------+--------------------------------------+
| admin_state_up            | True                                 |
| id                        | c2501278-d77b-4af1-af35-55ad8f864c18 |
| mtu                       | 0                                    |
| name                      | public                               |
| provider:network_type     | flat                                 |
| provider:physical_network | default                              |
| provider:segmentation_id  |                                      |
| router:external           | True                                 |
| shared                    | False                                |
| status                    | ACTIVE                               |
| subnets                   |                                      |
| tenant_id                 | fc618c8151ad4c53b0fccbca89502b8e     |
+---------------------------+--------------------------------------+

Basically, this boils down to the fact that with PHYSICAL_NETWORK,
DevStack populates the bridge_mappings file, while
PUBLIC_PHYSICAL_NETWORK does not.

Confused yet?


-- 
Sean M. Collins