Bug 1377304

Summary: Provider network support (VLAN and Flat) for E/W and external networks
Product: Red Hat OpenStack Reporter: Josh Hershberg <jhershbe>
Component: opendaylightAssignee: Josh Hershberg <jhershbe>
Status: CLOSED ERRATA QA Contact: Itzik Brown <itbrown>
Severity: unspecified Docs Contact:
Priority: high    
Version: 10.0 (Newton)CC: itbrown, jhershbe, jschluet, lpeer, lruzicka, mkolesni, nyechiel, tfreger
Target Milestone: asyncKeywords: FutureFeature, TechPreview, ZStream
Target Release: 10.0 (Newton)   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: opendaylight-5.2.0-6.el7ost Doc Type: If docs needed, set a value
Doc Text:
Users can define existing physical networks to integrate them into their OpenStack and OpenDaylight environment. This feature can be beneficial in private OpenStack deployments, because it is possible to configure virtual machines to connect directly to a pre-defined network.
 Story Points: ---
Clone Of: Environment:
N/A
Last Closed: 2017-03-23 16:14:48 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Bug Depends On: 1422092    
Bug Blocks: 1427436    

Description Josh Hershberg 2016-09-19 12:05:04 UTC 
OpenStack Neutron currently has a feature referred to as "provider
networks". This is used as a way to define existing physical networks
that you would like to integrate into your environment.

In the simplest case, it can be used in environments where they have no
interest in tenant networks. Instead, they want all VMs hooked up
directly to a pre-defined network in their environment. This use case
is actually popular for private OpenStack deployments.

Neutron's current OVS agent that runs on network nodes and hypervisors
has this configuration entry:

bridge_mappings = physnet1:br-eth1,physnet2:br-eth2[...]

This is used to name your physical networks and the bridge used to
access that physical network from the local node.

Defining a provider network via the Neutron API via the neutron
command looks like this:

$ neutron net-create physnet1 --shared \
> --provider:physical_network external \
> --provider:network_type flat

A provider network can also be defined with a VLAN ID:

$ neutron net-create physnet1-101 --shared \
> --provider:physical_network external \
> --provider:network_type vlan \
> --provider:segmentation_id 101
Comment 2 lpeer 2016-09-25 07:55:12 UTC 
This functionality would be available in ODL Boron release which would not be included in OSP-10 GA. We'll release it at a later async release.
Comment 5 Itzik Brown 2017-01-24 11:02:26 UTC 
Added Fixed-in version opendaylight-5.2.0-2.el7ost
Comment 15 Itzik Brown 2017-03-06 13:03:14 UTC 
Verified with:
opendaylight-5.2.0-6.el7ost.noarch
Comment 17 errata-xmlrpc 2017-03-23 16:14:48 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHBA-2017-0840.html