BPGVPN has a hard requirement for Boron SR2. Only allow the BGPVPN features to
be enabled when that ODL version is used.
Change-Id: Iac9599f31e8f6ce53e25b3325d5116ba2e34a7eb
Signed-off-by: Romanos Skiadas <rski@intracom-telecom.com>
Ubuntu 16.04 comes with a new ovs version, satisfying NetVirt's requirements.
The custom ovs is no longer needed when the BGPVNP features are enabled.
Change-Id: Ic23b2a253caa92e5ae42995ac79d5188b5401987
Signed-off-by: Romanos Skiadas <rski@intracom-telecom.com>
Use docker container from integration-packaging project to build
OpenDaylight deb packages. This change introduce support for systemd
and is a part of uplifting plugin to Fuel 10.
Notice: to build plugin with more than one version of ODL
fuel-plugin-builder needs to be installed from sources, this change is
required: https://review.openstack.org/#/c/311031/
Change-Id: Ib6204c1fa71a844fe42b878352bd987c192ee9dd
Signed-off-by: Michal Skalski <mskalski@mirantis.com>
- Make the plugin use Boron SR1 when the bgpvpn features are used
- Make BGPVPN use the odl-netvirt feature
- Make EXPERIMENTAL_TARBALL_LOCATION point to SR1
- Remove the default gateway input for bgpvpn
- Unconditionally enable some features which were disabled for bgpvpn.
Disable the bgpvpn specific environment configurations that were used
in lieu of those features that were disabled for bgpvpn
- Make floating IP work for odl-netvirt-openstack. This is done by
adding a provider_mapping to ovs between physnet1 and br-floating, which
opendaylight uses to configure the networking setup accordingly.
Co-Authored-By: Romanos Skiadas <rski@intracom-telecom.com>
Change-Id: Icdb962dac83d0a68b25914285a0e7d8987daefdc
L2 odl+bgpvpn features are not very stable together
Change-Id: Id52e448bc5816292a11b02e7cdbe4b33f0abe1cd
Signed-off-by: Romanos Skiadas <rski@intracom-telecom.com>
This change only replace Beryllium with Boron. Usage of new features
introduced in Boron is a subject of separate changes.
Change-Id: I3bbdc66cbb0d25ff1ca97cc9a54ecbc053c6c0b8
Signed-off-by: Michal Skalski <mskalski@mirantis.com>
ODL_BORON_TARBALL_LOCATION env variable can be used to point to dedicated
version of ODL for SFC, opendaylight-boron deb package will be created.
Change-Id: Ia9ec2457de82e793b29af494b48c37d567fc7e72
Signed-off-by: Michal Skalski <mskalski@mirantis.com>
Version v2 of the networking-odl driver supposed to resolve race
conditions and better support HA deployments. It is still considered as
experimental and can introduce new problems. It is new option, not the
default choice.
Change-Id: Ied938155b369371c4516cb1496167a6fd1de6c30
Signed-off-by: Michal Skalski <mskalski@mirantis.com>
Register OpenDaylight as a network component, it will be available in
environment creation wizard.
Add task which will register DLUX dashboard inside Fuel Web UI.
Move ODL credentials and jetty port number from puppet manifests to
hiera.
Signed-off-by: Michal Skalski <mskalski@mirantis.com>
Change-Id: I6f347aec73435886d72d734fb7d0deecc065b618
From now on One can choose between 'NetVirt' and 'GBP' classifier.
The default is 'NetVirt'
Change-Id: Ibdcd455f0f43d8ca5364cab60ac2f28860c40916
Signed-off-by: Ferenc Cserepkei <ferenc.cserepkei@ericsson.com>
To enable SDNVPN feature we have to do:
- setup the transport endpoint that it
has the correct ip in ovs and ODL
- Add br-int
- Configure ODL as the controller for br-int
- disable ovsdb feature and enable sdnpvpn feature
- fuel network setup has to be changed
to stick to sdnvpn network concept
Change-Id: I320c9597b4b760f3a7d273aad710b5e43f4ba754
- Support MOS 8.0.
- Move ODL installation and configuration
to main phase of deployment.
- L3 traffic managed by ODL possible when vxlan
tunneling is used.
- Include snapshot of OpenDaylight Beryllium,
stable version not available at this moment.
- Get rid of hardcoded configuration related to specific ODL version.
Now plugin is more elastic and should support a broader
number of ODL versions.
- odl_network_scheme function overrided standard network scheme
so custom network templates are not required.
- ODL is no longer patched to use br-floating bridge
Change-Id: I8d1391817ff3a012697aac487ce9eaea489d8df6
This commit adds Service Function Chaining(SFC) basic installation opportunity
to a Fuel orchestrated openstack cluster. SFC installation is integrated into
fuel-plugin-opendaylight, since it covers orchestration tasks only and
the used SFC is closely tied to the OpenDayLight installation used.
This is the Fuel7 uplift of the original change set.
Change-Id: Ib9b4b8fbd5964453d1a2478abaa74c21849f11d0
Plugin can now be used on Fuel 7.0. It will install and setup
OpenDaylight Lithium SR2 controller together with networking_odl driver.
User can now decided where ODL controller will be installed by assigning
role OPENDAYLIGHT to one of the nodes.
Experimental option of managing L3 traffic by ODL was added. It will
prepare necessary configuration on ODL and Neutron side and also disable
neutron l3 agent. This feature require further development and should be
only enabled by users who know what they are doing.
Change-Id: I99bb9434f0e2baec52748e20551681d63d2bf1ce
Current status:
* OpenDaylight controller is installed on primary controller
* OpenDaylight is set as OVS manager
* VLAN, GRE, VXLAN segmentation supported
* Neutron agent is responsible for L3 traffic
Change-Id: Ibd804940e2c8acc81a1d507b1de964ee97250107
Andreas Jaeger