+.. _vtn-user-guide:
+
Virtual Tenant Network (VTN)
============================
It is implemented as two major components
-- `VTN Manager <#_vtn_manager>`__
+- `VTN Manager`
-- `VTN Coordinator <#_vtn_coordinator>`__
+- `VTN Coordinator`
VTN Manager
~~~~~~~~~~~
"Content-type: application/json" -X GET \
http://localhost:8181/restconf/operational/vtn:vtns
-REST API documentation for VTN Manager, please refer to:
-https://jenkins.opendaylight.org/releng/view/vtn/job/vtn-merge-beryllium/lastSuccessfulBuild/artifact/manager/model/target/site/models/
+REST Conf documentation for VTN Manager, please refer to:
+https://nexus.opendaylight.org/content/sites/site/org.opendaylight.vtn/boron/manager.model/apidocs/index.html
+
VTN Coordinator
~~~~~~~~~~~~~~~
- A configuration file "90-vtn-neutron.xml" will be generated
automatically by following the below steps,
-- Download the latest Beryllium karaf distribution from the below link,
+- Download the latest Boron karaf distribution from the below link,
::
http://www.opendaylight.org/software/downloads
-- cd "distribution-karaf-0.4.0-Beryllium" and run karaf by using the
+- cd "distribution-karaf-0.5.0-Boron" and run karaf by using the
following command "./bin/karaf".
- Install the below feature to generate "90-vtn-neutron.xml"
- Logout from the karaf console and Check "90-vtn-neutron.xml" file
from the following path
- "distribution-karaf-0.4.0-Beryllium/etc/opendaylight/karaf/".
+ "distribution-karaf-0.5.0-Boron/etc/opendaylight/karaf/".
- The contents of "90-vtn-neutron.xml" should be as follows:
''''''''''''''''''''''''''''
- stack.sh prints out Horizon is now available at
- `http://<CONTROL\_NODE\_IP\_ADDRESS>:8080/ <http://<CONTROL_NODE_IP_ADDRESS>:8080/>`__
+ http://<CONTROL\_NODE\_IP\_ADDRESS>:8080/
- Execute the command *sudo ovs-vsctl show* in the control node
terminal and verify if the bridge *br-int* is created.
^^^^^^^^^^^^^^^^^^^^^^^^
- Please visit the OpenDaylight DLUX GUI after stacking all the nodes,
- `http://<ODL\_IP\_ADDRESS>:8181/index.html <http://<ODL_IP_ADDRESS>:8181/index.html>`__.
+ http://<ODL\_IP\_ADDRESS>:8181/index.html.
The switches, topology and the ports that are currently read can be
validated.
http://<controller-ip>:8181/index.html
- **Tip**
+.. tip::
If the interconnected between the Open vSwitch is not seen, Please
bring up the interface for the dataplane manually using the below
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
- Login to
- `http://<CONTROL\_NODE\_IP>:8080/ <http://<CONTROL_NODE_IP>:8080/>`__
+ http://<CONTROL\_NODE\_IP>:8080/
to check the horizon GUI.
.. figure:: ./images/vtn/OpenStackGui.png
and enter the login URL. If you have installed DLUX as a stand-alone,
then the login URL is http://localhost:9000/DLUX/index.html. However if
you have deployed DLUX with Karaf, then the login URL is
-`http://\\<your <http://\<your>`__ IP\\>:8181/dlux/index.html. \* Login
+http://<your IP>:8181/dlux/index.html. \* Login
to the application with user ID and password credentials as admin.
NOTE:admin is the only user type available for DLUX in this release.
DLUX UI does not provide ability to add topology information. The
Topology should be created using an open flow plugin. Controller
stores this information in the database and displays on the DLUX
- page, when the you connect to the controller using openflow.
+ page, when the you connect to the controller using OpenFlow.
.. figure:: ./images/vtn/Dlux_topology.png
:alt: Topology
^^^^^^^^
This page explains how to provision virtual L2 network using VTN
-Manager. This page targets Beryllium release, so the procedure described
+Manager. This page targets Boron release, so the procedure described
here does not work in other releases.
.. figure:: ./images/vtn/How_to_provision_virtual_L2_network.png
command to call the REST API.
- Create a virtual tenant named vtn1 by executing `the update-vtn
- RPC <https://jenkins.opendaylight.org/releng/view/vtn/job/vtn-merge-beryllium/lastSuccessfulBuild/artifact/manager/model/target/site/models/vtn.html#update-vtn>`__.
+ RPC <https://nexus.opendaylight.org/content/sites/site/org.opendaylight.vtn/boron/manager.model/models/vtn.html#update-vtn>`__.
::
- Create a virtual bridge named vbr1 in the tenant vtn1 by executing
`the update-vbridge
- RPC <https://jenkins.opendaylight.org/releng/view/vtn/job/vtn-merge-beryllium/lastSuccessfulBuild/artifact/manager/model/target/site/models/vtn-vbridge.html#update-vbridge>`__.
+ RPC <https://nexus.opendaylight.org/content/sites/site/org.opendaylight.vtn/boron/manager.model/models/vtn-vbridge.html#update-vbridge>`__.
::
- Create two interfaces into the virtual bridge by executing `the
update-vinterface
- RPC <https://jenkins.opendaylight.org/releng/view/vtn/job/vtn-merge-beryllium/lastSuccessfulBuild/artifact/manager/model/target/site/models/vtn-vinterface.html#update-vinterface>`__.
+ RPC <https://nexus.opendaylight.org/content/sites/site/org.opendaylight.vtn/boron/manager.model/models/vtn-vinterface.html#update-vinterface>`__.
::
- Configure two mappings on the created interfaces by executing `the
set-port-map
- RPC <https://jenkins.opendaylight.org/releng/view/vtn/job/vtn-merge-beryllium/lastSuccessfulBuild/artifact/manager/model/target/site/models/vtn-port-map.html#set-port-map>`__.
+ RPC <https://nexus.opendaylight.org/content/sites/site/org.opendaylight.vtn/boron/manager.model/models/vtn-port-map.html#set-port-map>`__.
- The interface if1 of the virtual bridge will be mapped to the port
"s2-eth1" of the switch "openflow:2" of the Mininet.
^^^^^^^^^^^
- You can delete the virtual tenant vtn1 by executing `the remove-vtn
- RPC <https://jenkins.opendaylight.org/releng/view/vtn/job/vtn-merge-beryllium/lastSuccessfulBuild/artifact/manager/model/target/site/models/vtn.html#remove-vtn>`__.
+ RPC <https://nexus.opendaylight.org/content/sites/site/org.opendaylight.vtn/boron/manager.model/models/vtn.html#remove-vtn>`__.
::
^^^^^^^^
This page explains how to test Vlan-map in a multi host scenario using
-mininet. This page targets Beryllium release, so the procedure described
+mininet. This page targets Boron release, so the procedure described
here does not work in other releases.
.. figure:: ./images/vtn/vlanmap_using_mininet.png
- :alt: Example that demonstrates vlanmap testing in Mininet
- Environment
+ :alt: Example that demonstrates vlanmap testing in Mininet Environment
Example that demonstrates vlanmap testing in Mininet Environment
To test vlan-map, execute REST API provided by VTN Manager as follows.
- Create a virtual tenant named vtn1 by executing `the update-vtn
- RPC <https://jenkins.opendaylight.org/releng/view/vtn/job/vtn-merge-beryllium/lastSuccessfulBuild/artifact/manager/model/target/site/models/vtn.html#update-vtn>`__.
+ RPC <https://nexus.opendaylight.org/content/sites/site/org.opendaylight.vtn/boron/manager.model/models/vtn.html#update-vtn>`__.
::
- Create a virtual bridge named vbr1 in the tenant vtn1 by executing
`the update-vbridge
- RPC <https://jenkins.opendaylight.org/releng/view/vtn/job/vtn-merge-beryllium/lastSuccessfulBuild/artifact/manager/model/target/site/models/vtn-vbridge.html#update-vbridge>`__.
+ RPC <https://nexus.opendaylight.org/content/sites/site/org.opendaylight.vtn/boron/manager.model/models/vtn-vbridge.html#update-vbridge>`__.
::
- Configure a vlan map with vlanid 200 for vBridge vbr1 by executing
`the add-vlan-map
- RPC <https://jenkins.opendaylight.org/releng/view/vtn/job/vtn-merge-beryllium/lastSuccessfulBuild/artifact/manager/model/target/site/models/vtn-vlan-map.html#add-vlan-map>`__.
+ RPC <https://nexus.opendaylight.org/content/sites/site/org.opendaylight.vtn/boron/manager.model/models/vtn-vlan-map.html#add-vlan-map>`__.
::
- Create a virtual bridge named vbr2 in the tenant vtn1 by executing
`the update-vbridge
- RPC <https://jenkins.opendaylight.org/releng/view/vtn/job/vtn-merge-beryllium/lastSuccessfulBuild/artifact/manager/model/target/site/models/vtn-vbridge.html#update-vbridge>`__.
+ RPC <https://nexus.opendaylight.org/content/sites/site/org.opendaylight.vtn/boron/manager.model/models/vtn-vbridge.html#update-vbridge>`__.
::
- Configure a vlan map with vlanid 300 for vBridge vbr2 by executing
`the add-vlan-map
- RPC <https://jenkins.opendaylight.org/releng/view/vtn/job/vtn-merge-beryllium/lastSuccessfulBuild/artifact/manager/model/target/site/models/vtn-vlan-map.html#add-vlan-map>`__.
+ RPC <https://nexus.opendaylight.org/content/sites/site/org.opendaylight.vtn/boron/manager.model/models/vtn-vlan-map.html#add-vlan-map>`__.
::
^^^^^^^^^^^
- You can delete the virtual tenant vtn1 by executing `the remove-vtn
- RPC <https://jenkins.opendaylight.org/releng/view/vtn/job/vtn-merge-beryllium/lastSuccessfulBuild/artifact/manager/model/target/site/models/vtn.html#remove-vtn>`__.
+ RPC <https://nexus.opendaylight.org/content/sites/site/org.opendaylight.vtn/boron/manager.model/models/vtn.html#remove-vtn>`__.
::
^^^^^^^^
This page explains how to configure VTN Manager for Service Chaining.
-This page targets Beryllium release, so the procedure described here
+This page targets Boron release, so the procedure described here
does not work in other releases.
.. figure:: ./images/vtn/Service_Chaining_With_One_Service.png
^^^^^^^^^^^^
- Please refer to the `Installation
- Pages <https://wiki.opendaylight.org/view/VTN:Beryllium:Installation_Guide>`__
+ Pages <https://wiki.opendaylight.org/view/VTN:Boron:Installation_Guide>`__
to run ODL with VTN Feature enabled.
- Please ensure Bridge-Utils package is installed in mininet
.. note::
The below commands are for the difference in behavior of Manager in
- Beryllium topology. The Link below has the details for this bug:
+ Boron topology. The Link below has the details for this bug:
https://bugs.opendaylight.org/show_bug.cgi?id=3818.
::
curl --user admin:admin -H 'content-type: application/json' -H 'ipaddr:127.0.0.1' -X PUT http://localhost:8181/restconf/config/vtn-static-topology:vtn-static-topology/static-edge-ports -d '{"static-edge-ports": {"static-edge-port": [ {"port": "openflow:3:3"}, {"port": "openflow:3:4"}, {"port": "openflow:4:3"}, {"port": "openflow:4:4"}]}}'
- Create a virtual tenant named vtn1 by executing `the update-vtn
- RPC <https://jenkins.opendaylight.org/releng/view/vtn/job/vtn-merge-beryllium/lastSuccessfulBuild/artifact/manager/model/target/site/models/vtn.html#update-vtn>`__.
+ RPC <https://nexus.opendaylight.org/content/sites/site/org.opendaylight.vtn/boron/manager.model/models/vtn.html#update-vtn>`__.
::
- Create a virtual bridge named vbr1 in the tenant vtn1 by executing
`the update-vbridge
- RPC <https://jenkins.opendaylight.org/releng/view/vtn/job/vtn-merge-beryllium/lastSuccessfulBuild/artifact/manager/model/target/site/models/vtn-vbridge.html#update-vbridge>`__.
+ RPC <https://nexus.opendaylight.org/content/sites/site/org.opendaylight.vtn/boron/manager.model/models/vtn-vbridge.html#update-vbridge>`__.
::
- Create interface if1 into the virtual bridge vbr1 by executing `the
update-vinterface
- RPC <https://jenkins.opendaylight.org/releng/view/vtn/job/vtn-merge-beryllium/lastSuccessfulBuild/artifact/manager/model/target/site/models/vtn-vinterface.html#update-vinterface>`__.
+ RPC <https://nexus.opendaylight.org/content/sites/site/org.opendaylight.vtn/boron/manager.model/models/vtn-vinterface.html#update-vinterface>`__.
::
- Configure port mapping on the interface by executing `the
set-port-map
- RPC <https://jenkins.opendaylight.org/releng/view/vtn/job/vtn-merge-beryllium/lastSuccessfulBuild/artifact/manager/model/target/site/models/vtn-port-map.html#set-port-map>`__.
+ RPC <https://nexus.opendaylight.org/content/sites/site/org.opendaylight.vtn/boron/manager.model/models/vtn-port-map.html#set-port-map>`__.
- The interface if1 of the virtual bridge will be mapped to the port
"s1-eth2" of the switch "openflow:1" of the Mininet.
- Create interface if2 into the virtual bridge vbr1 by executing `the
update-vinterface
- RPC <https://jenkins.opendaylight.org/releng/view/vtn/job/vtn-merge-beryllium/lastSuccessfulBuild/artifact/manager/model/target/site/models/vtn-vinterface.html#update-vinterface>`__.
+ RPC <https://nexus.opendaylight.org/content/sites/site/org.opendaylight.vtn/boron/manager.model/models/vtn-vinterface.html#update-vinterface>`__.
::
- Configure port mapping on the interface by executing `the
set-port-map
- RPC <https://jenkins.opendaylight.org/releng/view/vtn/job/vtn-merge-beryllium/lastSuccessfulBuild/artifact/manager/model/target/site/models/vtn-port-map.html#set-port-map>`__.
+ RPC <https://nexus.opendaylight.org/content/sites/site/org.opendaylight.vtn/boron/manager.model/models/vtn-port-map.html#set-port-map>`__.
- The interface if2 of the virtual bridge will be mapped to the port
"s2-eth2" of the switch "openflow:2" of the Mininet.
- Create interface if3 into the virtual bridge vbr1 by executing `the
update-vinterface
- RPC <https://jenkins.opendaylight.org/releng/view/vtn/job/vtn-merge-beryllium/lastSuccessfulBuild/artifact/manager/model/target/site/models/vtn-vinterface.html#update-vinterface>`__.
+ RPC <https://nexus.opendaylight.org/content/sites/site/org.opendaylight.vtn/boron/manager.model/models/vtn-vinterface.html#update-vinterface>`__.
::
- Configure port mapping on the interfaces by executing `the
set-port-map
- RPC <https://jenkins.opendaylight.org/releng/view/vtn/job/vtn-merge-beryllium/lastSuccessfulBuild/artifact/manager/model/target/site/models/vtn-port-map.html#set-port-map>`__.
+ RPC <https://nexus.opendaylight.org/content/sites/site/org.opendaylight.vtn/boron/manager.model/models/vtn-port-map.html#set-port-map>`__.
- The interface if3 of the virtual bridge will be mapped to the port
"s2-eth3" of the switch "openflow:2" of the Mininet.
- Create flowcondition named cond\_1 by executing `the
set-flow-condition
- RPC <https://jenkins.opendaylight.org/releng/view/vtn/job/vtn-merge-beryllium/lastSuccessfulBuild/artifact/manager/model/target/site/models/vtn-flow-condition.html#set-flow-condition>`__.
+ RPC <https://nexus.opendaylight.org/content/sites/site/org.opendaylight.vtn/boron/manager.model/models/vtn-flow-condition.html#set-flow-condition>`__.
- For option source and destination-network, get inet address of
host h12(src) and h22(dst) from mininet.
- Flow filter demonstration with DROP action-type. Create Flowfilter in
VBR Interface if1 by executing `the set-flow-filter
- RPC <https://jenkins.opendaylight.org/releng/view/vtn/job/vtn-merge-beryllium/lastSuccessfulBuild/artifact/manager/model/target/site/models/vtn-flow-filter.html#set-flow-filter>`__.
+ RPC <https://nexus.opendaylight.org/content/sites/site/org.opendaylight.vtn/boron/manager.model/models/vtn-flow-filter.html#set-flow-filter>`__.
::
- Create a virtual terminal named vt\_srvc1\_1 in the tenant vtn1 by
executing `the update-vterminal
- RPC <https://jenkins.opendaylight.org/releng/view/vtn/job/vtn-merge-beryllium/lastSuccessfulBuild/artifact/manager/model/target/site/models/vtn-vterminal.html#update-vterminal>`__.
+ RPC <https://nexus.opendaylight.org/content/sites/site/org.opendaylight.vtn/boron/manager.model/models/vtn-vterminal.html#update-vterminal>`__.
::
- Create interface IF into the virtual terminal vt\_srvc1\_1 by
executing `the update-vinterface
- RPC <https://jenkins.opendaylight.org/releng/view/vtn/job/vtn-merge-beryllium/lastSuccessfulBuild/artifact/manager/model/target/site/models/vtn-vinterface.html#update-vinterface>`__.
+ RPC <https://nexus.opendaylight.org/content/sites/site/org.opendaylight.vtn/boron/manager.model/models/vtn-vinterface.html#update-vinterface>`__.
::
- Configure port mapping on the interfaces by executing `the
set-port-map
- RPC <https://jenkins.opendaylight.org/releng/view/vtn/job/vtn-merge-beryllium/lastSuccessfulBuild/artifact/manager/model/target/site/models/vtn-port-map.html#set-port-map>`__.
+ RPC <https://nexus.opendaylight.org/content/sites/site/org.opendaylight.vtn/boron/manager.model/models/vtn-port-map.html#set-port-map>`__.
- The interface IF of the virtual terminal will be mapped to the
port "s3-eth3" of the switch "openflow:3" of the Mininet.
- Create a virtual terminal named vt\_srvc1\_2 in the tenant vtn1 by
executing `the update-vterminal
- RPC <https://jenkins.opendaylight.org/releng/view/vtn/job/vtn-merge-beryllium/lastSuccessfulBuild/artifact/manager/model/target/site/models/vtn-vterminal.html#update-vterminal>`__.
+ RPC <https://nexus.opendaylight.org/content/sites/site/org.opendaylight.vtn/boron/manager.model/models/vtn-vterminal.html#update-vterminal>`__.
::
- Create interface IF into the virtual terminal vt\_srvc1\_2 by
executing `the update-vinterface
- RPC <https://jenkins.opendaylight.org/releng/view/vtn/job/vtn-merge-beryllium/lastSuccessfulBuild/artifact/manager/model/target/site/models/vtn-vinterface.html#update-vinterface>`__.
+ RPC <https://nexus.opendaylight.org/content/sites/site/org.opendaylight.vtn/boron/manager.model/models/vtn-vinterface.html#update-vinterface>`__.
::
- Configure port mapping on the interfaces by executing `the
set-port-map
- RPC <https://jenkins.opendaylight.org/releng/view/vtn/job/vtn-merge-beryllium/lastSuccessfulBuild/artifact/manager/model/target/site/models/vtn-port-map.html#set-port-map>`__.
+ RPC <https://nexus.opendaylight.org/content/sites/site/org.opendaylight.vtn/boron/manager.model/models/vtn-port-map.html#set-port-map>`__.
- The interface IF of the virtual terminal will be mapped to the
port "s4-eth3" of the switch "openflow:4" of the Mininet.
- Create flowcondition named cond\_1 by executing `the
set-flow-condition
- RPC <https://jenkins.opendaylight.org/releng/view/vtn/job/vtn-merge-beryllium/lastSuccessfulBuild/artifact/manager/model/target/site/models/vtn-flow-condition.html#set-flow-condition>`__.
+ RPC <https://nexus.opendaylight.org/content/sites/site/org.opendaylight.vtn/boron/manager.model/models/vtn-flow-condition.html#set-flow-condition>`__.
- For option source and destination-network, get inet address of
host h12(src) and h22(dst) from mininet.
- Create flowcondition named cond\_any by executing `the
set-flow-condition
- RPC <https://jenkins.opendaylight.org/releng/view/vtn/job/vtn-merge-beryllium/lastSuccessfulBuild/artifact/manager/model/target/site/models/vtn-flow-condition.html#set-flow-condition>`__.
+ RPC <https://nexus.opendaylight.org/content/sites/site/org.opendaylight.vtn/boron/manager.model/models/vtn-flow-condition.html#set-flow-condition>`__.
::
- Flow filter demonstration with redirect action-type. Create
Flowfilter in virtual terminal vt\_srvc1\_2 interface IF by executing
`the set-flow-filter
- RPC <https://jenkins.opendaylight.org/releng/view/vtn/job/vtn-merge-beryllium/lastSuccessfulBuild/artifact/manager/model/target/site/models/vtn-flow-filter.html#set-flow-filter>`__.
+ RPC <https://nexus.opendaylight.org/content/sites/site/org.opendaylight.vtn/boron/manager.model/models/vtn-flow-filter.html#set-flow-filter>`__.
- Flowfilter redirects vt\_srvc1\_2 to bridge1-IF2
- Flow filter demonstration with redirect action-type. Create
Flowfilter in vbridge vbr1 interface if1 by executing `the
set-flow-filter
- RPC <https://jenkins.opendaylight.org/releng/view/vtn/job/vtn-merge-beryllium/lastSuccessfulBuild/artifact/manager/model/target/site/models/vtn-flow-filter.html#set-flow-filter>`__.
+ RPC <https://nexus.opendaylight.org/content/sites/site/org.opendaylight.vtn/boron/manager.model/models/vtn-flow-filter.html#set-flow-filter>`__.
- Flow filter redirects Bridge1-IF1 to vt\_srvc1\_1
- Create a virtual terminal named vt\_srvc2\_1 in the tenant vtn1 by
executing `the update-vterminal
- RPC <https://jenkins.opendaylight.org/releng/view/vtn/job/vtn-merge-beryllium/lastSuccessfulBuild/artifact/manager/model/target/site/models/vtn-vterminal.html#update-vterminal>`__.
+ RPC <https://nexus.opendaylight.org/content/sites/site/org.opendaylight.vtn/boron/manager.model/models/vtn-vterminal.html#update-vterminal>`__.
::
- Create interface IF into the virtual terminal vt\_srvc2\_1 by
executing `the update-vinterface
- RPC <https://jenkins.opendaylight.org/releng/view/vtn/job/vtn-merge-beryllium/lastSuccessfulBuild/artifact/manager/model/target/site/models/vtn-vinterface.html#update-vinterface>`__.
+ RPC <https://nexus.opendaylight.org/content/sites/site/org.opendaylight.vtn/boron/manager.model/models/vtn-vinterface.html#update-vinterface>`__.
::
- Configure port mapping on the interfaces by executing `the
set-port-map
- RPC <https://jenkins.opendaylight.org/releng/view/vtn/job/vtn-merge-beryllium/lastSuccessfulBuild/artifact/manager/model/target/site/models/vtn-port-map.html#set-port-map>`__.
+ RPC <https://nexus.opendaylight.org/content/sites/site/org.opendaylight.vtn/boron/manager.model/models/vtn-port-map.html#set-port-map>`__.
- The interface IF of the virtual terminal will be mapped to the
port "s3-eth4" of the switch "openflow:3" of the Mininet.
- Create a virtual terminal named vt\_srvc2\_2 in the tenant vtn1 by
executing `the update-vterminal
- RPC <https://jenkins.opendaylight.org/releng/view/vtn/job/vtn-merge-beryllium/lastSuccessfulBuild/artifact/manager/model/target/site/models/vtn-vterminal.html#update-vterminal>`__.
+ RPC <https://nexus.opendaylight.org/content/sites/site/org.opendaylight.vtn/boron/manager.model/models/vtn-vterminal.html#update-vterminal>`__.
::
- Create interfaces IF into the virtual terminal vt\_srvc2\_2 by
executing `the update-vinterface
- RPC <https://jenkins.opendaylight.org/releng/view/vtn/job/vtn-merge-beryllium/lastSuccessfulBuild/artifact/manager/model/target/site/models/vtn-vinterface.html#update-vinterface>`__.
+ RPC <https://nexus.opendaylight.org/content/sites/site/org.opendaylight.vtn/boron/manager.model/models/vtn-vinterface.html#update-vinterface>`__.
::
- Configure port mapping on the interfaces by executing `the
set-port-map
- RPC <https://jenkins.opendaylight.org/releng/view/vtn/job/vtn-merge-beryllium/lastSuccessfulBuild/artifact/manager/model/target/site/models/vtn-port-map.html#set-port-map>`__.
+ RPC <https://nexus.opendaylight.org/content/sites/site/org.opendaylight.vtn/boron/manager.model/models/vtn-port-map.html#set-port-map>`__.
- The interface IF of the virtual terminal will be mapped to the
port "s4-eth4" of the switch "openflow:4" of the mininet.
- Flow filter demonstration with redirect action-type. Create
Flowfilter in virtual terminal vt\_srvc2\_2 interface IF by executing
`the set-flow-filter
- RPC <https://jenkins.opendaylight.org/releng/view/vtn/job/vtn-merge-beryllium/lastSuccessfulBuild/artifact/manager/model/target/site/models/vtn-flow-filter.html#set-flow-filter>`__.
+ RPC <https://nexus.opendaylight.org/content/sites/site/org.opendaylight.vtn/boron/manager.model/models/vtn-flow-filter.html#set-flow-filter>`__.
- Flow filter redirects vt\_srvc2\_2 to Bridge1-IF2.
- Flow filter demonstration with redirect action-type. Create
Flowfilter in virtual terminal vt\_srvc2\_2 interface IF by executing
`the set-flow-filter
- RPC <https://jenkins.opendaylight.org/releng/view/vtn/job/vtn-merge-beryllium/lastSuccessfulBuild/artifact/manager/model/target/site/models/vtn-flow-filter.html#set-flow-filter>`__.
+ RPC <https://nexus.opendaylight.org/content/sites/site/org.opendaylight.vtn/boron/manager.model/models/vtn-flow-filter.html#set-flow-filter>`__.
- Flow filter redirects vt\_srvc1\_2 to vt\_srvc2\_1.
- To clean up both VTN and flowconditions.
- You can delete the virtual tenant vtn1 by executing `the remove-vtn
- RPC <https://jenkins.opendaylight.org/releng/view/vtn/job/vtn-merge-beryllium/lastSuccessfulBuild/artifact/manager/model/target/site/models/vtn.html#remove-vtn>`__.
+ RPC <https://nexus.opendaylight.org/content/sites/site/org.opendaylight.vtn/boron/manager.model/models/vtn.html#remove-vtn>`__.
::
- You can delete the flowcondition cond\_1 and cond\_any by executing
`the remove-flow-condition
- RPC <https://jenkins.opendaylight.org/releng/view/vtn/job/vtn-merge-beryllium/lastSuccessfulBuild/artifact/manager/model/target/site/models/vtn-flow-condition.html#remove-flow-condition>`__.
+ RPC <https://nexus.opendaylight.org/content/sites/site/org.opendaylight.vtn/boron/manager.model/models/vtn-flow-condition.html#remove-flow-condition>`__.
::
^^^^^^^^
This page explains how to view Dataflows using VTN Manager. This page
-targets Beryllium release, so the procedure described here does not work
+targets Boron release, so the procedure described here does not work
in other releases.
Dataflow feature enables retrieval and display of data flows in the
-openflow network. The data flows can be retrieved based on an openflow
+OpenFlow network. The data flows can be retrieved based on an OpenFlow
switch or a switch port or a L2 source host.
The flow information provided by this feature are
node "openflow:1" and its port "s1-eth1".
- Get the Dataflows information by executing `the get-data-flow
- RPC <https://jenkins.opendaylight.org/releng/view/vtn/job/vtn-merge-beryllium/lastSuccessfulBuild/artifact/manager/model/target/site/models/vtn-flow.html#get-data-flow>`__.
+ RPC <https://nexus.opendaylight.org/content/sites/site/org.opendaylight.vtn/boron/manager.model/models/vtn-flow.html#get-data-flow>`__.
::
particular host by associating a Vbridge to the hosts and configuring
Mac Mapping (mac address) to the Vbridge.
-- This page targets Beryllium release, so the procedure described here
+- This page targets Boron release, so the procedure described here
does not work in other releases.
.. figure:: ./images/vtn/Single_Controller_Mapping.png
follows. It uses curl command to call REST API.
- Create a virtual tenant named Tenant1 by executing `the update-vtn
- RPC <https://jenkins.opendaylight.org/releng/view/vtn/job/vtn-merge-beryllium/lastSuccessfulBuild/artifact/manager/model/target/site/models/vtn.html#update-vtn>`__.
+ RPC <https://nexus.opendaylight.org/content/sites/site/org.opendaylight.vtn/boron/manager.model/models/vtn.html#update-vtn>`__.
::
- Create a virtual bridge named vBridge1 in the tenant Tenant1 by
executing `the update-vbridge
- RPC <https://jenkins.opendaylight.org/releng/view/vtn/job/vtn-merge-beryllium/lastSuccessfulBuild/artifact/manager/model/target/site/models/vtn-vbridge.html#update-vbridge>`__.
+ RPC <https://nexus.opendaylight.org/content/sites/site/org.opendaylight.vtn/boron/manager.model/models/vtn-vbridge.html#update-vbridge>`__.
::
- Configuring Mac Mappings on the vBridge1 by giving the mac address of
host h12 and host h22 as follows to allow the communication by
executing `the set-mac-map
- RPC <https://jenkins.opendaylight.org/releng/view/vtn/job/vtn-merge-beryllium/lastSuccessfulBuild/artifact/manager/model/target/site/models/vtn-mac-map.html#set-mac-map>`__.
+ RPC <https://nexus.opendaylight.org/content/sites/site/org.opendaylight.vtn/boron/manager.model/models/vtn-mac-map.html#set-mac-map>`__.
::
- You can delete the virtual tenant Tenant1 by executing `the
remove-vtn
- RPC <https://jenkins.opendaylight.org/releng/view/vtn/job/vtn-merge-beryllium/lastSuccessfulBuild/artifact/manager/model/target/site/models/vtn.html#remove-vtn>`__.
+ RPC <https://nexus.opendaylight.org/content/sites/site/org.opendaylight.vtn/boron/manager.model/models/vtn.html#remove-vtn>`__.
::
^^^^^^^^
- This page explains how to provision flowfilter using VTN Manager.
- This page targets Beryllium release, so the procedure described here
+ This page targets Boron release, so the procedure described here
does not work in other releases.
- The flow-filter function discards, permits, or redirects packets of
command to call the REST API.
- Create a virtual tenant named vtn1 by executing `the update-vtn
- RPC <https://jenkins.opendaylight.org/releng/view/vtn/job/vtn-merge-beryllium/lastSuccessfulBuild/artifact/manager/model/target/site/models/vtn.html#update-vtn>`__.
+ RPC <https://nexus.opendaylight.org/content/sites/site/org.opendaylight.vtn/boron/manager.model/models/vtn.html#update-vtn>`__.
::
- Create a virtual bridge named vbr1 in the tenant vtn1 by executing
`the update-vbridge
- RPC <https://jenkins.opendaylight.org/releng/view/vtn/job/vtn-merge-beryllium/lastSuccessfulBuild/artifact/manager/model/target/site/models/vtn-vbridge.html#update-vbridge>`__.
+ RPC <https://nexus.opendaylight.org/content/sites/site/org.opendaylight.vtn/boron/manager.model/models/vtn-vbridge.html#update-vbridge>`__.
::
- Create two interfaces into the virtual bridge by executing `the
update-vinterface
- RPC <https://jenkins.opendaylight.org/releng/view/vtn/job/vtn-merge-beryllium/lastSuccessfulBuild/artifact/manager/model/target/site/models/vtn-vinterface.html#update-vinterface>`__.
+ RPC <https://nexus.opendaylight.org/content/sites/site/org.opendaylight.vtn/boron/manager.model/models/vtn-vinterface.html#update-vinterface>`__.
::
- Configure two mappings on the interfaces by executing `the
set-port-map
- RPC <https://jenkins.opendaylight.org/releng/view/vtn/job/vtn-merge-beryllium/lastSuccessfulBuild/artifact/manager/model/target/site/models/vtn-port-map.html#set-port-map>`__.
+ RPC <https://nexus.opendaylight.org/content/sites/site/org.opendaylight.vtn/boron/manager.model/models/vtn-port-map.html#set-port-map>`__.
- The interface if1 of the virtual bridge will be mapped to the port
"s2-eth1" of the switch "openflow:2" of the Mininet.
- Create flowcondition named cond\_1 by executing `the
set-flow-condition
- RPC <https://jenkins.opendaylight.org/releng/view/vtn/job/vtn-merge-beryllium/lastSuccessfulBuild/artifact/manager/model/target/site/models/vtn-flow-condition.html#set-flow-condition>`__.
+ RPC <https://nexus.opendaylight.org/content/sites/site/org.opendaylight.vtn/boron/manager.model/models/vtn-flow-condition.html#set-flow-condition>`__.
- For option source and destination-network, get inet address of
host h1 and h3 from mininet.
- Flow filter demonstration with DROP action-type. Create Flowfilter in
VBR Interface if1 by executing `the set-flow-filter
- RPC <https://jenkins.opendaylight.org/releng/view/vtn/job/vtn-merge-beryllium/lastSuccessfulBuild/artifact/manager/model/target/site/models/vtn-flow-filter.html#set-flow-filter>`__.
+ RPC <https://nexus.opendaylight.org/content/sites/site/org.opendaylight.vtn/boron/manager.model/models/vtn-flow-filter.html#set-flow-filter>`__.
::
- Update the flow filter to pass the packets by executing `the
set-flow-filter
- RPC <https://jenkins.opendaylight.org/releng/view/vtn/job/vtn-merge-beryllium/lastSuccessfulBuild/artifact/manager/model/target/site/models/vtn-flow-filter.html#set-flow-filter>`__.
+ RPC <https://nexus.opendaylight.org/content/sites/site/org.opendaylight.vtn/boron/manager.model/models/vtn-flow-filter.html#set-flow-filter>`__.
::
- To clean up both VTN and flowcondition.
- You can delete the virtual tenant vtn1 by executing `the remove-vtn
- RPC <https://jenkins.opendaylight.org/releng/view/vtn/job/vtn-merge-beryllium/lastSuccessfulBuild/artifact/manager/model/target/site/models/vtn.html#remove-vtn>`__.
+ RPC <https://nexus.opendaylight.org/content/sites/site/org.opendaylight.vtn/boron/manager.model/models/vtn.html#remove-vtn>`__.
::
- You can delete the flowcondition cond\_1 by executing `the
remove-flow-condition
- RPC <https://jenkins.opendaylight.org/releng/view/vtn/job/vtn-merge-beryllium/lastSuccessfulBuild/artifact/manager/model/target/site/models/vtn-flow-condition.html#remove-flow-condition>`__.
+ RPC <https://nexus.opendaylight.org/content/sites/site/org.opendaylight.vtn/boron/manager.model/models/vtn-flow-condition.html#remove-flow-condition>`__.
::
^^^^^^^^
- This page explains how to create specific VTN Pathmap using VTN
- Manager. This page targets Beryllium release, so the procedure
+ Manager. This page targets Boron release, so the procedure
described here does not work in other releases.
.. figure:: ./images/vtn/Pathmap.png
VTN Manager as follows. It uses curl command to call the REST API.
- Create a virtual tenant named vtn1 by executing `the update-vtn
- RPC <https://jenkins.opendaylight.org/releng/view/vtn/job/vtn-merge-beryllium/lastSuccessfulBuild/artifact/manager/model/target/site/models/vtn.html#update-vtn>`__.
+ RPC <https://nexus.opendaylight.org/content/sites/site/org.opendaylight.vtn/boron/manager.model/models/vtn.html#update-vtn>`__.
::
- Create a virtual bridge named vbr1 in the tenant vtn1 by executing
`the update-vbridge
- RPC <https://jenkins.opendaylight.org/releng/view/vtn/job/vtn-merge-beryllium/lastSuccessfulBuild/artifact/manager/model/target/site/models/vtn-vbridge.html#update-vbridge>`__.
+ RPC <https://nexus.opendaylight.org/content/sites/site/org.opendaylight.vtn/boron/manager.model/models/vtn-vbridge.html#update-vbridge>`__.
::
- Create two interfaces into the virtual bridge by executing `the
update-vinterface
- RPC <https://jenkins.opendaylight.org/releng/view/vtn/job/vtn-merge-beryllium/lastSuccessfulBuild/artifact/manager/model/target/site/models/vtn-vinterface.html#update-vinterface>`__.
+ RPC <https://nexus.opendaylight.org/content/sites/site/org.opendaylight.vtn/boron/manager.model/models/vtn-vinterface.html#update-vinterface>`__.
::
- Configure two mappings on the interfaces by executing `the
set-port-map
- RPC <https://jenkins.opendaylight.org/releng/view/vtn/job/vtn-merge-beryllium/lastSuccessfulBuild/artifact/manager/model/target/site/models/vtn-port-map.html#set-port-map>`__.
+ RPC <https://nexus.opendaylight.org/content/sites/site/org.opendaylight.vtn/boron/manager.model/models/vtn-port-map.html#set-port-map>`__.
- The interface if1 of the virtual bridge will be mapped to the port
"s2-eth1" of the switch "openflow:1" of the Mininet.
64 bytes from 10.0.0.2: icmp_seq=3 ttl=64 time=0.101 ms
- Get the Dataflows information by executing `the get-data-flow
- RPC <https://jenkins.opendaylight.org/releng/view/vtn/job/vtn-merge-beryllium/lastSuccessfulBuild/artifact/manager/model/target/site/models/vtn-flow.html#get-data-flow>`__.
+ RPC <https://nexus.opendaylight.org/content/sites/site/org.opendaylight.vtn/boron/manager.model/models/vtn-flow.html#get-data-flow>`__.
::
- Create flowcondition named cond\_1 by executing `the
set-flow-condition
- RPC <https://jenkins.opendaylight.org/releng/view/vtn/job/vtn-merge-beryllium/lastSuccessfulBuild/artifact/manager/model/target/site/models/vtn-flow-condition.html#set-flow-condition>`__.
+ RPC <https://nexus.opendaylight.org/content/sites/site/org.opendaylight.vtn/boron/manager.model/models/vtn-flow-condition.html#set-flow-condition>`__.
- For option source and destination-network, get inet address of
host h1 or host h2 from mininet
- Create pathmap with flowcondition cond\_1 by executing `the
set-path-map
- RPC <https://jenkins.opendaylight.org/releng/view/vtn/job/vtn-merge-beryllium/lastSuccessfulBuild/artifact/manager/model/target/site/models/vtn-path-map.html#set-path-map>`__.
+ RPC <https://nexus.opendaylight.org/content/sites/site/org.opendaylight.vtn/boron/manager.model/models/vtn-path-map.html#set-path-map>`__.
::
curl --user "admin":"admin" -H "Content-type: application/json" -X POST http://localhost:8181/restconf/operations/vtn-path-map:set-path-map -d '{"input":{"tenant-name":"vtn1","path-map-list":[{"condition":"cond_1","policy":"1","index": "1","idle-timeout":"300","hard-timeout":"0"}]}}'
- Create pathpolicy by executing `the set-path-policy
- RPC <https://jenkins.opendaylight.org/releng/view/vtn/job/vtn-merge-beryllium/lastSuccessfulBuild/artifact/manager/model/target/site/models/vtn-path-policy.html#set-path-policy>`__.
+ RPC <https://nexus.opendaylight.org/content/sites/site/org.opendaylight.vtn/boron/manager.model/models/vtn-path-policy.html#set-path-policy>`__.
::
- To clean up both VTN and flowcondition.
- You can delete the virtual tenant vtn1 by executing `the remove-vtn
- RPC <https://jenkins.opendaylight.org/releng/view/vtn/job/vtn-merge-beryllium/lastSuccessfulBuild/artifact/manager/model/target/site/models/vtn.html#remove-vtn>`__.
+ RPC <https://nexus.opendaylight.org/content/sites/site/org.opendaylight.vtn/boron/manager.model/models/vtn.html#remove-vtn>`__.
::
- You can delete the flowcondition cond\_1 by executing `the
remove-flow-condition
- RPC <https://jenkins.opendaylight.org/releng/view/vtn/job/vtn-merge-beryllium/lastSuccessfulBuild/artifact/manager/model/target/site/models/vtn-flow-condition.html#remove-flow-condition>`__.
+ RPC <https://nexus.opendaylight.org/content/sites/site/org.opendaylight.vtn/boron/manager.model/models/vtn-flow-condition.html#remove-flow-condition>`__.
::
This example explains how to test vlan-map in a multi host scenario.
.. figure:: ./images/vtn/vlanmap_using_mininet.png
- :alt: Example that demonstrates vlanmap testing in Mininet
- Environment
+ :alt: Example that demonstrates vlanmap testing in Mininet Environment
Example that demonstrates vlanmap testing in Mininet Environment
::
- Please ensure the firewall settings for port:8181(Beryllium release) or port:8083(Post Beryllium release) and enable the same.
+ Please ensure the firewall settings for port:8181 (Beryllium release) or port:8083 (Post Beryllium release) and enable the same.
**How to debug a REST API returning a failure message?.**
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
1. Please go through the below link to download VSEM Provider zip file,
- https://nexus.opendaylight.org/content/groups/public/org/opendaylight/vtn/application/vtnmanager-vsemprovider/2.0.0-Beryllium/vtnmanager-vsemprovider-2.0.0-Beryllium-bin.zip
+ https://nexus.opendaylight.org/content/groups/public/org/opendaylight/vtn/application/vtnmanager-vsemprovider/1.2.0-Boron/vtnmanager-vsemprovider-1.2.0-Boron-bin.zip
-2. Unzip the vtnmanager-vsemprovider-2.0.0-Beryllium-bin.zip file
+2. Unzip the vtnmanager-vsemprovider-1.2.0-Boron-bin.zip file
anywhere in your SCVMM machine.
3. Stop SCVMM service from **"service manager→tools→servers→select
- OpenDaylight Congestion Control with SCVMM VTN:
https://youtu.be/34YMOTzbNJM
-
Code Review / docs.git / blobdiff