From: "Khaldoon Al Zoubi" <khaldoon.alzoubi@...>
To: "Sam Hague" <shague@...>
Cc: ovsdb-dev@...
Sent: Tuesday, June 30, 2015 3:46:14 PM
Subject: RE: [ovsdb-dev] ODL Inventory

Hi Sam,

The ovsdb loads the config and operational topology correctly, which is good
I need that. But, what is not working for me is that openflowplugin is not
adding switches to inventory.

Thanks.

-----Original Message-----
From: Sam Hague [mailto:shague@...]
Sent: Tuesday, June 30, 2015 12:39 PM
To: Khaldoon Al Zoubi
Cc: ovsdb-dev@...
Subject: Re: [ovsdb-dev] ODL Inventory

Khal,

the openstack modules do not write anything to operational. It relies on the
southbound to do that and openstack listens for those changes when they
happen. After that the openstack netvirt modules will do things like add
bridges, but it is the southbound which will update the operational
topology. If you are looking for the openflow nodes, then the openflowplugin
does that (look in the earlier email where I mentioned that)

1. Did you verify the southbound feature loaded? feature:list -i | grep
ovsdb. look for southbound.
2. Try the postman calls. look in the ovsdb/resources/commons dir for the
southbound postman. Use the "Get config topology" and "get operational
topology" restconf calls and see if you get the ovsdb:1 node.
3. Add the ovs-vsctl set-manager tcp:<odlip>:6640 and verify if the ovsdb
node connected to odl, ovs-vsctl show.
4. Then try the postman calls again to see if the node shows up.

Sam

----- Original Message -----

From: "Khaldoon Al Zoubi" <khaldoon.alzoubi@...>
To: "Sam Hague" <shague@...>
Cc: ovsdb-dev@...
Sent: Tuesday, June 30, 2015 12:27:13 PM
Subject: RE: [ovsdb-dev] ODL Inventory

Hi Sam,

I commented out the openstack bundles in odl-ovsdb-openstack (please see
below) to test if odl-ovsdb-southbound-impl-ui will be able to load the
inventory operational node into datastore. Well, it didn't do it. Is that
mean that the openstack bundles are doing extra work to populate the
inventory? Thanks.

--------
<feature name="odl-ovsdb-openstack" description="OpenDaylight :: OVSDB ::
OpenStack Network Virtualization"
version='${openstack.netvirt.version}'>
<feature version='${mdsal.version}'>odl-mdsal-broker</feature>
<feature
version="${openflowplugin.version}">odl-openflowplugin-nsf-model</feature>
<feature
version="${networkconfig.neutron.version}">odl-neutron-service</feature>
<feature
version="1.1.0-SNAPSHOT">odl-ovsdb-southbound-impl-ui</feature>
<feature
version="${openflowplugin.version}">odl-openflowplugin-flow-services</feature>
<feature
version="${openflowplugin.version}">odl-openflowplugin-nxm-extensions</feature>
<!--
<bundle>mvn:org.opendaylight.ovsdb/utils.servicehelper/${ovsdb.utils.servicehelper.version}</bundle>
<bundle>mvn:org.opendaylight.ovsdb/openstack.net-virt/${openstack.netvirt.version}</bundle>
<bundle>mvn:org.opendaylight.ovsdb/openstack.net-virt-providers/${openstack.netvirt.providers.version}</bundle>
<configfile
finalname="etc/opendaylight/karaf/netvirt-impl-default-config.xml">mvn:org.opendaylight.ovsdb/openstack.net-virt/${project.version}/xml/config</configfile>
<configfile
finalname="etc/opendaylight/karaf/netvirt-providers-impl-default-config.xml">mvn:org.opendaylight.ovsdb/openstack.net-virt-providers/${project.version}/xml/config</configfile>
-->
</feature>


-----Original Message-----
From: Khaldoon Al Zoubi
Sent: Thursday, June 25, 2015 3:45 PM
To: 'Sam Hague'
Cc: ovsdb-dev@...
Subject: RE: [ovsdb-dev] ODL Inventory

Thanks Sam. Actually, this what I thought I need to do (only include
odl-ovsdb-southbound-impl in my features.xml), but I am not sure what part
I
am missing. I believe the devstack & ODL connection works since I am able
to
see neutron elements in datastore when executing commands like (neutron
net-create net-1). So feature odl-neutron-service works.

However, when I am running ODL purely from the OVSDB project it works and I
can see the operational nodes. So, I am missing something in my project.

Thanks Sam as always.

Regards,
Khal


-----Original Message-----
From: Sam Hague [mailto:shague@...]
Sent: Thursday, June 25, 2015 2:41 PM
To: Khaldoon Al Zoubi
Cc: ovsdb-dev@...
Subject: Re: [ovsdb-dev] ODL Inventory

Khal,

the OVSDB southbound plugin [1] will populate the topology with the ovsdb
node information, including the bridges and ports. With devstack as part of
the local.conf config the ODL address is specified. In the final steps of
the stack.sh the OVSDB Manager entry is set to that address and the OVSDB
nodes will connect to ODL. The OVSDB southbound plugin will see that
connection and begin to populate the MDSAL operational datastore - stores
the node, the bridge, the ports as termination points.

From there the netvirt [2] application listens for the operational updates.
netvirt also listens on the neutron events coming from the northbound side.
With these two sets of events netvirt will satisfy the neutron requests.

The openflow nodes inventory is populated via the openflowplugin. When the
OVSDB nodes connect and netvirt sees that it will create the required
bridges, i.e, br-int, and then set the Controller address. Those bridges
will then connect to ODL openflowplugin port and openflowplugin will add
the
switches to the inventory.

So you just need the odl-ovsdb-southbound-impl or
odl-ovsdb-southbound-impl-ui feature to get the southbound plugin which
will
get the inventory for you.

Thanks, Sam

[1] ovsdb/southbound/southbound-impl
[2] ovsdb/openstack

----- Original Message -----

From: "Khaldoon Al Zoubi" <khaldoon.alzoubi@...>
To: ovsdb-dev@...
Sent: Thursday, June 25, 2015 12:15:05 PM
Subject: [ovsdb-dev] ODL Inventory



Hi,



I can’t figure out how OVSDB populate ODL Inventory based on openstack
(i.e.
specifically after ./stack.sh is complete). Also, is there a feature I
can
include in my project to do that.



Thanks much.

Khal

_______________________________________________
ovsdb-dev mailing list
ovsdb-dev@...
https://lists.opendaylight.org/mailman/listinfo/ovsdb-dev

From: "Khaldoon Al Zoubi" <khaldoon.alzoubi@...>
To: "Sam Hague" <shague@...>
Cc: ovsdb-dev@...
Sent: Tuesday, June 30, 2015 3:46:14 PM
Subject: RE: [ovsdb-dev] ODL Inventory

Hi Sam,

The ovsdb loads the config and operational topology correctly, which is good
I need that. But, what is not working for me is that openflowplugin is not
adding switches to inventory.

Thanks.

-----Original Message-----
From: Sam Hague [mailto:shague@...]
Sent: Tuesday, June 30, 2015 12:39 PM
To: Khaldoon Al Zoubi
Cc: ovsdb-dev@...
Subject: Re: [ovsdb-dev] ODL Inventory

Khal,

the openstack modules do not write anything to operational. It relies on the
southbound to do that and openstack listens for those changes when they
happen. After that the openstack netvirt modules will do things like add
bridges, but it is the southbound which will update the operational
topology. If you are looking for the openflow nodes, then the openflowplugin
does that (look in the earlier email where I mentioned that)

1. Did you verify the southbound feature loaded? feature:list -i | grep
ovsdb. look for southbound.
2. Try the postman calls. look in the ovsdb/resources/commons dir for the
southbound postman. Use the "Get config topology" and "get operational
topology" restconf calls and see if you get the ovsdb:1 node.
3. Add the ovs-vsctl set-manager tcp:<odlip>:6640 and verify if the ovsdb
node connected to odl, ovs-vsctl show.
4. Then try the postman calls again to see if the node shows up.

Sam

----- Original Message -----

From: "Khaldoon Al Zoubi" <khaldoon.alzoubi@...>
To: "Sam Hague" <shague@...>
Cc: ovsdb-dev@...
Sent: Tuesday, June 30, 2015 12:27:13 PM
Subject: RE: [ovsdb-dev] ODL Inventory

Hi Sam,

I commented out the openstack bundles in odl-ovsdb-openstack (please see
below) to test if odl-ovsdb-southbound-impl-ui will be able to load the
inventory operational node into datastore. Well, it didn't do it. Is that
mean that the openstack bundles are doing extra work to populate the
inventory? Thanks.

--------
<feature name="odl-ovsdb-openstack" description="OpenDaylight :: OVSDB ::
OpenStack Network Virtualization"
version='${openstack.netvirt.version}'>
<feature version='${mdsal.version}'>odl-mdsal-broker</feature>
<feature
version="${openflowplugin.version}">odl-openflowplugin-nsf-model</feature>
<feature
version="${networkconfig.neutron.version}">odl-neutron-service</feature>
<feature
version="1.1.0-SNAPSHOT">odl-ovsdb-southbound-impl-ui</feature>
<feature
version="${openflowplugin.version}">odl-openflowplugin-flow-services</feature>
<feature
version="${openflowplugin.version}">odl-openflowplugin-nxm-extensions</feature>
<!--
<bundle>mvn:org.opendaylight.ovsdb/utils.servicehelper/${ovsdb.utils.servicehelper.version}</bundle>
<bundle>mvn:org.opendaylight.ovsdb/openstack.net-virt/${openstack.netvirt.version}</bundle>
<bundle>mvn:org.opendaylight.ovsdb/openstack.net-virt-providers/${openstack.netvirt.providers.version}</bundle>
<configfile
finalname="etc/opendaylight/karaf/netvirt-impl-default-config.xml">mvn:org.opendaylight.ovsdb/openstack.net-virt/${project.version}/xml/config</configfile>
<configfile
finalname="etc/opendaylight/karaf/netvirt-providers-impl-default-config.xml">mvn:org.opendaylight.ovsdb/openstack.net-virt-providers/${project.version}/xml/config</configfile>
-->
</feature>


-----Original Message-----
From: Khaldoon Al Zoubi
Sent: Thursday, June 25, 2015 3:45 PM
To: 'Sam Hague'
Cc: ovsdb-dev@...
Subject: RE: [ovsdb-dev] ODL Inventory

Thanks Sam. Actually, this what I thought I need to do (only include
odl-ovsdb-southbound-impl in my features.xml), but I am not sure what part
I
am missing. I believe the devstack & ODL connection works since I am able
to
see neutron elements in datastore when executing commands like (neutron
net-create net-1). So feature odl-neutron-service works.

However, when I am running ODL purely from the OVSDB project it works and I
can see the operational nodes. So, I am missing something in my project.

Thanks Sam as always.

Regards,
Khal


-----Original Message-----
From: Sam Hague [mailto:shague@...]
Sent: Thursday, June 25, 2015 2:41 PM
To: Khaldoon Al Zoubi
Cc: ovsdb-dev@...
Subject: Re: [ovsdb-dev] ODL Inventory

Khal,

the OVSDB southbound plugin [1] will populate the topology with the ovsdb
node information, including the bridges and ports. With devstack as part of
the local.conf config the ODL address is specified. In the final steps of
the stack.sh the OVSDB Manager entry is set to that address and the OVSDB
nodes will connect to ODL. The OVSDB southbound plugin will see that
connection and begin to populate the MDSAL operational datastore - stores
the node, the bridge, the ports as termination points.

From there the netvirt [2] application listens for the operational updates.
netvirt also listens on the neutron events coming from the northbound side.
With these two sets of events netvirt will satisfy the neutron requests.

The openflow nodes inventory is populated via the openflowplugin. When the
OVSDB nodes connect and netvirt sees that it will create the required
bridges, i.e, br-int, and then set the Controller address. Those bridges
will then connect to ODL openflowplugin port and openflowplugin will add
the
switches to the inventory.

So you just need the odl-ovsdb-southbound-impl or
odl-ovsdb-southbound-impl-ui feature to get the southbound plugin which
will
get the inventory for you.

Thanks, Sam

[1] ovsdb/southbound/southbound-impl
[2] ovsdb/openstack

----- Original Message -----

From: "Khaldoon Al Zoubi" <khaldoon.alzoubi@...>
To: ovsdb-dev@...
Sent: Thursday, June 25, 2015 12:15:05 PM
Subject: [ovsdb-dev] ODL Inventory



Hi,



I can’t figure out how OVSDB populate ODL Inventory based on openstack
(i.e.
specifically after ./stack.sh is complete). Also, is there a feature I
can
include in my project to do that.



Thanks much.

Khal

_______________________________________________
ovsdb-dev mailing list
ovsdb-dev@...
https://lists.opendaylight.org/mailman/listinfo/ovsdb-dev

From: "Khaldoon Al Zoubi" <khaldoon.alzoubi@...>
To: "Sam Hague" <shague@...>
Cc: ovsdb-dev@...
Sent: Tuesday, June 30, 2015 12:27:13 PM
Subject: RE: [ovsdb-dev] ODL Inventory

Hi Sam,

I commented out the openstack bundles in odl-ovsdb-openstack (please see
below) to test if odl-ovsdb-southbound-impl-ui will be able to load the
inventory operational node into datastore. Well, it didn't do it. Is that
mean that the openstack bundles are doing extra work to populate the
inventory? Thanks.

--------
<feature name="odl-ovsdb-openstack" description="OpenDaylight :: OVSDB ::
OpenStack Network Virtualization"
version='${openstack.netvirt.version}'>
<feature version='${mdsal.version}'>odl-mdsal-broker</feature>
<feature
version="${openflowplugin.version}">odl-openflowplugin-nsf-model</feature>
<feature
version="${networkconfig.neutron.version}">odl-neutron-service</feature>
<feature version="1.1.0-SNAPSHOT">odl-ovsdb-southbound-impl-ui</feature>
<feature
version="${openflowplugin.version}">odl-openflowplugin-flow-services</feature>
<feature
version="${openflowplugin.version}">odl-openflowplugin-nxm-extensions</feature>
<!--
<bundle>mvn:org.opendaylight.ovsdb/utils.servicehelper/${ovsdb.utils.servicehelper.version}</bundle>
<bundle>mvn:org.opendaylight.ovsdb/openstack.net-virt/${openstack.netvirt.version}</bundle>
<bundle>mvn:org.opendaylight.ovsdb/openstack.net-virt-providers/${openstack.netvirt.providers.version}</bundle>
<configfile
finalname="etc/opendaylight/karaf/netvirt-impl-default-config.xml">mvn:org.opendaylight.ovsdb/openstack.net-virt/${project.version}/xml/config</configfile>
<configfile
finalname="etc/opendaylight/karaf/netvirt-providers-impl-default-config.xml">mvn:org.opendaylight.ovsdb/openstack.net-virt-providers/${project.version}/xml/config</configfile>
-->
</feature>


-----Original Message-----
From: Khaldoon Al Zoubi
Sent: Thursday, June 25, 2015 3:45 PM
To: 'Sam Hague'
Cc: ovsdb-dev@...
Subject: RE: [ovsdb-dev] ODL Inventory

Thanks Sam. Actually, this what I thought I need to do (only include
odl-ovsdb-southbound-impl in my features.xml), but I am not sure what part I
am missing. I believe the devstack & ODL connection works since I am able to
see neutron elements in datastore when executing commands like (neutron
net-create net-1). So feature odl-neutron-service works.

However, when I am running ODL purely from the OVSDB project it works and I
can see the operational nodes. So, I am missing something in my project.

Thanks Sam as always.

Regards,
Khal


-----Original Message-----
From: Sam Hague [mailto:shague@...]
Sent: Thursday, June 25, 2015 2:41 PM
To: Khaldoon Al Zoubi
Cc: ovsdb-dev@...
Subject: Re: [ovsdb-dev] ODL Inventory

Khal,

the OVSDB southbound plugin [1] will populate the topology with the ovsdb
node information, including the bridges and ports. With devstack as part of
the local.conf config the ODL address is specified. In the final steps of
the stack.sh the OVSDB Manager entry is set to that address and the OVSDB
nodes will connect to ODL. The OVSDB southbound plugin will see that
connection and begin to populate the MDSAL operational datastore - stores
the node, the bridge, the ports as termination points.

From there the netvirt [2] application listens for the operational updates.
netvirt also listens on the neutron events coming from the northbound side.
With these two sets of events netvirt will satisfy the neutron requests.

The openflow nodes inventory is populated via the openflowplugin. When the
OVSDB nodes connect and netvirt sees that it will create the required
bridges, i.e, br-int, and then set the Controller address. Those bridges
will then connect to ODL openflowplugin port and openflowplugin will add the
switches to the inventory.

So you just need the odl-ovsdb-southbound-impl or
odl-ovsdb-southbound-impl-ui feature to get the southbound plugin which will
get the inventory for you.

Thanks, Sam

[1] ovsdb/southbound/southbound-impl
[2] ovsdb/openstack

----- Original Message -----

From: "Khaldoon Al Zoubi" <khaldoon.alzoubi@...>
To: ovsdb-dev@...
Sent: Thursday, June 25, 2015 12:15:05 PM
Subject: [ovsdb-dev] ODL Inventory



Hi,



I can’t figure out how OVSDB populate ODL Inventory based on openstack
(i.e.
specifically after ./stack.sh is complete). Also, is there a feature I can
include in my project to do that.



Thanks much.

Khal

_______________________________________________
ovsdb-dev mailing list
ovsdb-dev@...
https://lists.opendaylight.org/mailman/listinfo/ovsdb-dev

From: "Khaldoon Al Zoubi" <khaldoon.alzoubi@...>
To: "Sam Hague" <shague@...>
Cc: ovsdb-dev@...
Sent: Tuesday, June 30, 2015 12:27:13 PM
Subject: RE: [ovsdb-dev] ODL Inventory

Hi Sam,

I commented out the openstack bundles in odl-ovsdb-openstack (please see
below) to test if odl-ovsdb-southbound-impl-ui will be able to load the
inventory operational node into datastore. Well, it didn't do it. Is that
mean that the openstack bundles are doing extra work to populate the
inventory? Thanks.

--------
<feature name="odl-ovsdb-openstack" description="OpenDaylight :: OVSDB ::
OpenStack Network Virtualization"
version='${openstack.netvirt.version}'>
<feature version='${mdsal.version}'>odl-mdsal-broker</feature>
<feature
version="${openflowplugin.version}">odl-openflowplugin-nsf-model</feature>
<feature
version="${networkconfig.neutron.version}">odl-neutron-service</feature>
<feature version="1.1.0-SNAPSHOT">odl-ovsdb-southbound-impl-ui</feature>
<feature
version="${openflowplugin.version}">odl-openflowplugin-flow-services</feature>
<feature
version="${openflowplugin.version}">odl-openflowplugin-nxm-extensions</feature>
<!--
<bundle>mvn:org.opendaylight.ovsdb/utils.servicehelper/${ovsdb.utils.servicehelper.version}</bundle>
<bundle>mvn:org.opendaylight.ovsdb/openstack.net-virt/${openstack.netvirt.version}</bundle>
<bundle>mvn:org.opendaylight.ovsdb/openstack.net-virt-providers/${openstack.netvirt.providers.version}</bundle>
<configfile
finalname="etc/opendaylight/karaf/netvirt-impl-default-config.xml">mvn:org.opendaylight.ovsdb/openstack.net-virt/${project.version}/xml/config</configfile>
<configfile
finalname="etc/opendaylight/karaf/netvirt-providers-impl-default-config.xml">mvn:org.opendaylight.ovsdb/openstack.net-virt-providers/${project.version}/xml/config</configfile>
-->
</feature>


-----Original Message-----
From: Khaldoon Al Zoubi
Sent: Thursday, June 25, 2015 3:45 PM
To: 'Sam Hague'
Cc: ovsdb-dev@...
Subject: RE: [ovsdb-dev] ODL Inventory

Thanks Sam. Actually, this what I thought I need to do (only include
odl-ovsdb-southbound-impl in my features.xml), but I am not sure what part I
am missing. I believe the devstack & ODL connection works since I am able to
see neutron elements in datastore when executing commands like (neutron
net-create net-1). So feature odl-neutron-service works.

However, when I am running ODL purely from the OVSDB project it works and I
can see the operational nodes. So, I am missing something in my project.

Thanks Sam as always.

Regards,
Khal


-----Original Message-----
From: Sam Hague [mailto:shague@...]
Sent: Thursday, June 25, 2015 2:41 PM
To: Khaldoon Al Zoubi
Cc: ovsdb-dev@...
Subject: Re: [ovsdb-dev] ODL Inventory

Khal,

the OVSDB southbound plugin [1] will populate the topology with the ovsdb
node information, including the bridges and ports. With devstack as part of
the local.conf config the ODL address is specified. In the final steps of
the stack.sh the OVSDB Manager entry is set to that address and the OVSDB
nodes will connect to ODL. The OVSDB southbound plugin will see that
connection and begin to populate the MDSAL operational datastore - stores
the node, the bridge, the ports as termination points.

From there the netvirt [2] application listens for the operational updates.
netvirt also listens on the neutron events coming from the northbound side.
With these two sets of events netvirt will satisfy the neutron requests.

The openflow nodes inventory is populated via the openflowplugin. When the
OVSDB nodes connect and netvirt sees that it will create the required
bridges, i.e, br-int, and then set the Controller address. Those bridges
will then connect to ODL openflowplugin port and openflowplugin will add the
switches to the inventory.

So you just need the odl-ovsdb-southbound-impl or
odl-ovsdb-southbound-impl-ui feature to get the southbound plugin which will
get the inventory for you.

Thanks, Sam

[1] ovsdb/southbound/southbound-impl
[2] ovsdb/openstack

----- Original Message -----

From: "Khaldoon Al Zoubi" <khaldoon.alzoubi@...>
To: ovsdb-dev@...
Sent: Thursday, June 25, 2015 12:15:05 PM
Subject: [ovsdb-dev] ODL Inventory



Hi,



I can’t figure out how OVSDB populate ODL Inventory based on openstack
(i.e.
specifically after ./stack.sh is complete). Also, is there a feature I can
include in my project to do that.



Thanks much.

Khal

_______________________________________________
ovsdb-dev mailing list
ovsdb-dev@...
https://lists.opendaylight.org/mailman/listinfo/ovsdb-dev

From: "Khaldoon Al Zoubi" <khaldoon.alzoubi@...>
To: ovsdb-dev@...
Sent: Thursday, June 25, 2015 12:15:05 PM
Subject: [ovsdb-dev] ODL Inventory



Hi,



I can’t figure out how OVSDB populate ODL Inventory based on openstack (i.e.
specifically after ./stack.sh is complete). Also, is there a feature I can
include in my project to do that.



Thanks much.

Khal

_______________________________________________
ovsdb-dev mailing list
ovsdb-dev@...
https://lists.opendaylight.org/mailman/listinfo/ovsdb-dev

From: "Ravindra Kenchappa" <ravindra.kenchappa@...>
To: "Dayavanti Gopal Kamath" <dayavanti.gopal.kamath@...>, "Hema Gopalkrishnan"
<hema.gopalkrishnan@...>, "Vishal Thapar" <vishal.thapar@...>, "Aswin Suryanarayanan"
<aswin.suryanarayanan@...>, "Anil Vishnoi" <vishnoianil@...>, "Flavio Fernandes" <ffernand@...>,
"Sam Hague" <shague@...>, "Chris Wright" <chrisw@...>, "Kyle Mestery" <mestery@...>, "Prem
sankar G" <prem.sankar.g@...>, "Abhijit Kumbhare" <abhijit.kumbhare@...>, "Ravi Sundareswaran"
<ravi.sundareswaran@...>, "Maruti Haridas Kamat" <maruti.kamat@...>, "Swaminathan Vasudevan (PNB
Roseville)" <swaminathan.vasudevan@...>, "afredette@..." <afredette@...>, "Ravi Sabapathy"
<Ravi_Sabapathy@...>, "Yapeng Wu" <Yapeng.Wu@...>, sumit@...
Sent: Friday, June 26, 2015 6:03:57 AM
Subject: RE: OVSDB hardware vtep support

Hi All,

This is regarding the ODL hardware l2gateway implementations. Myself and
Maruti tried to put together a high level architecture diagram and tried to
explain as we understand. Please take a look and we can discuss on any
comments/suggestions in our Tuesday's meeting coming week. Also Maruti
and I are planning to talk about how the hardware l2 gateway feature is
implemented in Kilo.



Discover and establish connection with hardware VTEP:

* ODL OVSDB plug-in will establish an active connection with the device
running ovsdb-server and hw_vtep model in MD-SAL data store is updated. (1)
* Neutron administrator creates an l2-gateway (abstraction of hardware
gateway and its ports/interfaces) - logical resource in neutron.
* Neutron administrator creates a VXLAN network.
* Neutron administrator creates an l2-gateway-connection (binding of
the virtual network with the l2-gateway logical resource)
* The call lands into the L2gw service plugin.
* The L2gw service plugin invokes the l2gw-ODL driver and makes REST
call to the ODL controller
* The ODL controller validates the request against the data present in
the datastore (whether such hardware gateway and such ports really exist).
* ODL northbound REST API also reads the gateway configuration and
updates the hardware_vtep yang model in MD-SAL data store.
* onDatachanged event will be generated and the OVSDB net-virt should
determine ( in MD-SAL data store) the compute nodes which is hosting the
virtual ports and VM macaddress associated to these virtual ports in
gateway configuration. Once all the necessary information is available
appropriated tables of hardware_vtep yang model in MD-SAL data store should
be updated.
* Neutron yang should be updated and onDatachanged event will be
generated which will be consumed by netvirt.
* OnDataChanged OVSDB Southbound plugin should process the
NorthBoundevent and using OVSDB library the appropriate tables in the device
hw_vtep should be updated so that VXLAN tunnel between the hw_vtep and the
compute node will be created. Also VNI<->VLAN binding should be updated on
the device's hw_vtep so that VNI <-> VLAN cross-connect configuration will
be done by the device based on the hw_vtep table updates.
* When a VM is spawned on the neutron side, the VMs details (like IP,
MAC, compute node VTEP IP) is sent by the ODL ML2 plugin to the ODL North
Bound.
* The ODL OVSDB soutbound plugin updates the OVSDB hardware schema
tables the hardware gateway creates a VXLAN tunnel to the compute node based
on this information.
* Whenever a new bare metal server is discovered on the port (for which
VXLAN-VLAN mapping exists), the ODL southbound plugin contacts the compute
node OVS tunnel bridge to create a reverse VXLAN tunnel to the hardware
VTEP.
* OVSDB southbound plug-in should also create VXLAN tunnel on the
compute node whose ports are participating in the gateway configuration.
* With this configuration bare metals(BM) on the physical
infrastructure (underlay) and virtual machines (VM) on the overlay can
participate in the same l2 domain.

Thanks,
Ravi / Maruti


-----Original Appointment-----
From: Dayavanti Gopal Kamath [mailto:dayavanti.gopal.kamath@...]
Sent: Monday, June 22, 2015 9:18 PM
To: Hema Gopalkrishnan; Vishal Thapar; Kenchappa, Ravindra; Suryanarayanan,
Aswin; 'Anil Vishnoi'; 'Flavio Fernandes'; 'Sam Hague'; 'Chris Wright';
'Kyle Mestery'; Prem sankar G; Abhijit Kumbhare; Ravi Sundareswaran; Kamat,
Maruti Haridas; Vasudevan, Swaminathan (PNB Roseville);
'afredette@...'; Ravi_Sabapathy@...; Yapeng.Wu@...;
sumit@...
Subject: OVSDB hardware vtep support
When: Tuesday, June 23, 2015 7:30 PM-8:30 PM (UTC+05:30) Chennai, Kolkata,
Mumbai, New Delhi.
Where: tbd


All,
Looking to hold ongoing meetings in the community forum at 7 am PST on
Tuesdays. Abhijit will send out an invite with the webex details as soon as
phil robb sets it up. If it doesn't come through for tomorrow, we can use
the Ericsson conference. Unfortunately, I cannot post the conf number on the
mailing list, I will share it with this group. So in case we do use it, will
request you to forward the invite to whoever else interested.

Thanks!
daya

From: "Simhon Doctori שמחון דוקטורי" <simhond@...>
To: "Sharon Aicler (saichler)" <saichler@...>
Cc: sharonaz@..., controller-dev@..., yossi@...
Sent: Sunday, June 28, 2015 7:21:38 AM
Subject: Re: [controller-dev] Flows, Ports and Networks are not being removed from ODL with Neutron

Thanks, I will try an earlier release of ODL (such as 0.2.3) and see if same
issue happens there.

I guess the tuntap interfaces on the hypervisor are up to the nova to
create/remove them using the qemu plugin.

On Sun, Jun 28, 2015 at 2:15 PM, Sharon Aicler (saichler) <
saichler@... > wrote:



Hi,
For flows to be added and removed there should be some integration between
the ovsdb & openflowplugin. I do not know if it exist in lithium, hence I
would raise the question to the ovsdb mailer... but AFAIK the way ODL works
is that the flows, ports & bridges should be added via ovsdb plugin for them
to be removed by ovsdb. If neutron is the one adding them then they will be
missing from the configuration store, hence ODL will not be able to remove
them as they are just in the operational store...
Another thought comes to my mind is who removes the tuntap interfaces on the
OVS side? Im guessing OVSDB plugin can remove bridges & ports from OVS, but
who removes the tuntap interfaces from the vm/machine hosting the OVS?

Sent from my Android phone using TouchDown ( www.nitrodesk.com )

-----Original Message-----
From: Simhon Doctori שמחון דוקטורי [ simhond@... ]
Received: Sunday, 28 Jun 2015, 3:46
To: Sharon Aicler (saichler) [ saichler@... ]
CC: controller-dev@... [
controller-dev@... ]; sharonaz@... [
sharonaz@... ]; yossi@... [ yossi@...
]
Subject: Re: [controller-dev] Flows, Ports and Networks are not being removed
from ODL with Neutron

Thanks Sharon,

I will check it for the ports and networks but does the removal of the flows
should also be originated from the ovsdb <--> neutron ?

Simhon.

On Sun, Jun 28, 2015 at 12:42 PM, Sharon Aicler (saichler) <
saichler@... > wrote:



Hi,
I think the ovsdb mailer is a better place to ask this question...

Sent from my Android phone using TouchDown ( www.nitrodesk.com )


-----Original Message-----
From: Simhon Doctori שמחון דוקטורי [ simhond@... ]
Received: Sunday, 28 Jun 2015, 2:26
To: controller-dev@... [
controller-dev@... ]
CC: sharonaz@... [ sharonaz@... ]; yossi barshishat
יוסי ברששת [ yossi@... ]
Subject: [controller-dev] Flows, Ports and Networks are not being removed
from ODL with Neutron

Hi,

We are working with Devstack of integration ODL Helium and Icehouse Openstack
taken from:
https://wiki.opendaylight.org/view/OVSDB:Helium_and_Openstack_on_Fedora20#VMs
.

All works well, but when we remove a VM using the nova delete, or even remove
the entire network using neutron, nothing is removed neither from the OVS
nor from the ODL itself.

It looks like ODL disregards neutron remove requests for some reason. Is this
a known problem for these releases ( distribution-karaf-0.2.1-Helium-SR and
Icehouese ) ?

Any option to make it works ?

Should it be working is latest Opendaylight release ?

--
Regards,

Simhon.



--
Regards,

Simhon.



--
Regards,

Simhon.

_______________________________________________
controller-dev mailing list
controller-dev@...
https://lists.opendaylight.org/mailman/listinfo/controller-dev