No information about type and name of external network (External network in OpenStack Installation Guide for Ubuntu 12.04/14.04 (LTS) - icehouse)

[George Shuklin]

Instruction neutron net-create ext-net --shared --router:external=True is simply will not work in real world.

Normal external networks should specify their name and type, like this:

neutron net-create external1 -- --router:external=true --provider:network_type=flat --provider:physical_network=ext-net1

Whithout --provider, normal (not devstack) installation will fail badly leaving all tenants without network access (because their 'external' networks will be pointing to nothing, not real bridge to real interface).

-----------------------------------
Built: 2014-08-21T22:14:28 00:00
git SHA: d9e3ab1f86d8157cd4a7b0ad5be680aaa300ceb3
URL: http://docs.openstack.org/icehouse/install-guide/install/apt/content/neutron_initial-external-network.html
source File: file:/home/jenkins/workspace/openstack-manuals-tox-doc-publishdocs/doc/install-guide/section_neutron-initial-networks.xml
xml:id: neutron_initial-external-network

[Matt Kassawara (ionosphere80)]

The existing instructions were tested to work with the OVS/GRE configuration in the installation guide. However, they may not work with other configurations.

[George Shuklin (george-shuklin)]

I'm talking about exact GRE networking. How external network (from provider's router) connected to neutron? How neutron knows type of that networks?

This guide will not work anywere outside of devstack and will not work with real-world installation with real routable IPs.

[Matt Kassawara (ionosphere80)]

The installation guide performs a "real" installation of OpenStack, not DevStack. The current instructions for creating networks are tested and work in the environment described in the example architecture. However, your suggestion of defining a flat network in ML2 and creating the ext-net network with provider network flags also works and I may consider it for the next release.