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
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
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
Role can change during deployment, we need to compare role name with
list of all roles assigned to node.
Change-Id: I02aecfe8ac9cd9ec2ea8569d8bb98eb55fe79749
Although it is not possible to make a cluster of OpenDaylight
controllers in Helium release, we can make services like Dlux and apidoc
explorer become accessible on public vip address.
Change-Id: Id51bdb2f5ebe881155a6432f22d188a364f11177
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