Date   

Re: sample [raw] output of openstack<->odl communication

Flavio Fernandes <ffernand@...>
 


Added a bash script that will emulate Openstack and OVS, so ODL can be ran ‘standalone’,
while getting events from neutron-nrothbound as well as openvswitch.

The script is located here [1] and here [2].
To work on L3 with ODL, I normally do these [3].

While the script is very much tailored to mimic the steps to create tenant … associate floatingIP,
it can hopefully be useful for other tasks you may need while testing/developing ODL.

Enjoy,

— flavio



[3]: echo 'ovsdb.l3.fwd.enabled=yes' >> ./etc/custom.properties ; rm -rf ./data ; ./bin/karaf
   feature:install odl-ovsdb-openstack
      log:set debug org.opendaylight.ovsdb.openstack.netvirt.impl.NeutronL3Adapter


On Jun 10, 2015, at 6:53 AM, Flavio Fernandes <ffernand@...> wrote:


Added postman collection [1] you can use to repeat these steps.

To emulate creation of ovs ports that go with these steps, look at the description of the entries [2]:
  - Add Neutron Port For dhcp sub1
  - Add Neutron Port For vm1

— flavio





On Jun 9, 2015, at 12:24 PM, Flavio Fernandes <ffernand@...> wrote:

Hi Mat,

In this example, I stack a single o/s node and ran the following commands: [cmds]

It will:
- create tenant, user (lines 8, 9)
- create external net for tenant (line 15)
- create external subnet (line 18)
In context of tenant, it will:
- create tenant router (line 38)
- set router gateway (line 39)
- create tenant internal net and subnet (lines 41, 42)
- create router interface on tenant internal subnet (line 43)
- boot a tenant vm (line 46)
- create floating ip and associate it with tenant vm (lines 48, 50)


A txt for neutron->odl is here [capTxt] a wireshark capture is here [capBin].
If you look at [karaf] karaf.log, you can see a lot of info on how that percolates into odl’s ovsdb netvirt.
A history of ovs commands that happened in the O/S node are here [ovsLog].

The commands used:

- capture to screen:
   sudo tcpdump -Ann -i eth1 tcp port 8080 and 'tcp[13] & 8!=0' | tee tcpdump.txt

- capture to file:
   sudo tcpdump -vv -w tcpdump.cap -i eth1 -s 0 tcp port 8080

- dump ovs history (thanks shague!):
   ovsdb-tool -mm show-log

— flavio

[cmds]: https://gist.github.com/9bc7812997ec629a0518
[console]: https://gist.github.com/84c925de41dba226b986
[capTxt]: https://dl.dropboxusercontent.com/u/86298/simpleNeutronCapture/tcpdump.txt
[capBin]: https://dl.dropboxusercontent.com/u/86298/simpleNeutronCapture/tcpdump.cap
[karaf]: https://dl.dropboxusercontent.com/u/86298/simpleNeutronCapture/karaf.log
[ovsLog]: https://gist.github.com/cd64c801b55cef23a4db



Updated Invitation: OpenDaylight - OPNFV community sync meeting @ Thu Jun 18, 2015 10am - 11am (dneary@redhat.com)

dneary@...
 

This event has been changed.

OpenDaylight - OPNFV community sync meeting

Changed: OpenDaylight - OPNFV monthly sync call
======================================

This is a monthly call to allow integration issues between OpenDaylight and OpenStack in the context of OPNFV to be shared and resolved, and to encourage better communication between OPNFV and the OpenDaylight project.

Agenda this month:
* SFC/GBP in OpenDaylight:
* Gap analysis, common understanding of use-case
* Neutron & Nova needs
* Defining and programming service chains

Dial-in numbers:

US Toll-Free Dial-In Number: 800 451 8679
US local dial-in number: +1 (212) 729-5016

Global Access Numbers Local:

China Domestic Dial-in # 4006205013
China Domestic Dial-in # 8008190132
Finland Helsinki Dial-in # 0923194436
France Paris Dial-in # 0170377140
Germany Berlin Dial-in # 030300190579
Germany Frankfurt Dial-in # 06922222594
Spain Madrid Dial-in # 914146284
Sweden Stockholm Dial-in # 0850513770
United Kingdom Dial-in # 02035746870
United Kingdom LocalCall Dial-in # 08445790678

Global Access Numbers Toll-Free

Australia Dial-in # 1800337169
France Dial-in # 0805632867
Germany Dial-in # 08006647541
India Dial-in # 180030104350
Japan Dial-in # 0120994948
Japan Dial-in # 00531250120
Netherlands Dial-in # 08000222329
Spain Dial-in # 800300524
Sweden Dial-in # 0200896860
Switzerland Dial-in # 0800650077
United Kingdom Dial-in # 08006948057

When
Thu Jun 18, 2015 10am – 11am Eastern Time
Where
Changed: Bluejeans: https://bluejeans.com/820680232 or Intercall Bridge: 915 507 3783# (phone numbers below) (map)
Calendar
dneary@...
Who
Dave Neary - organizer
scott.mansfield@...
raymond.nugent@...
nsowatsk@...
psarwal@...
shanan@...
ganesh@...
azhar.saleem@...
jack.pugaczewski@...
vijamann@...
rovarga@...
sandy.turnbull@...
canio.cillis@...
gmainzer@...
tadi.bhargava@...
carol.sanders@...
mc3124@...
shague@...
paul-andre.raymond@...
james.luhrsen@...
neutron-dev@...
sharis@...
opnfv-tsc@...
dave.hood@...
tapio.tallgren@...
paparao.palacharla@...
peter.pozar@...
vzelcamo@...
iben.rodriguez@...
groupbasedpolicy-dev@...
dominik.schatzmann@...
ovsdb-dev@...
christopher.price@...
daniel.smith@...
gershon.schatzberg@...
dwcarder@...
michael.a.lynch@...
dongkansheng@...
martin.lipka@...
george.y.zhao@...
thinrichs@...
smazziot@...
bh526r@...
yafit.hadar@...
ville.pesonen@...
rapenno@...
controller-dev@...
dirk.kutscher@...
ramkri123@...
michael.shevenell@...
glenn.seiler@...
wangjinzhu@...
tnadeau@...
opnfv-tech-discuss@...
rmoats@...
discuss@...
cficik@...
desilva@...
arobinson@...
mark.szczesniak@...
dayavanti.gopal.kamath@...
sfc-dev@...
zhang.jun3g@...
zxing@...
jiangmk@...
helen.chen@...
chilung@...
ssaxena@...
marc.rapoport@...
kkoushik@...
yunchao.hu@...
mageshkumar@...
bs3131@...
slowe@...
vguntaka@...
laurent.laporte@...
eric.hansander@...
sma@...
nlemieux@...
Keith Burns
daya_k@...
dkutenic@...
fzdarsky@...
john.borz@...
narayana_perumal@...
louis.fourie@...
rbrar@...
dfarrell@...
manohar.sl@...

Going?   Yes - Maybe - No    more options »

Invitation from Google Calendar

You are receiving this courtesy email at the account ovsdb-dev@... because you are an attendee of this event.

To stop receiving future updates for this event, decline this event. Alternatively you can sign up for a Google account at https://www.google.com/calendar/ and control your notification settings for your entire calendar.


Re: extract ovsdb library for use in other projects

Shashank
 

Thanks Sam for the really quick response. I'll take a look at how it's being used. I'll get back with more questions. :)

On Thu, Jun 11, 2015 at 7:47 AM, Sam Hague <shague@...> wrote:
Shashank,

look at the ovsdb/southbound-impl module and see how the ovsdb lib is used. The library is already non-osgi so you just need to use it in the same way as southbound-impl.

Thanks, Sam

----- Original Message -----
> From: "Shashank Shanbhag" <shashank@...>
> To: ovsdb-dev@...
> Sent: Thursday, June 11, 2015 2:18:38 AM
> Subject: [ovsdb-dev] extract ovsdb library for use in other projects
>
> Hello,
> Any pointer would be really helpful.
>
> The opendaylight/ovsdb/library README (on github[0]) mentions that the
> library can be used independently [1]. I'm trying to extract the library out
> into a separate maven artifact to use in projects minus osgi and other
> opendaylight dependencies. What would be the best approach to do this? I see
> osgi as a requirement in org.opendaylight.ovsdb.lib.osgi.
>
> Thanks!
> Shashank
> [0] https://github.com/opendaylight/ovsdb
> [1]
> - library : Contains Schema-independent library that is a reference
> implementation for RFC 7047.
>             This module doesn't depend on any of the Opendaylight components.
>             This library module can also be used independently in a non-OSGi
>             environment.
>
>
> _______________________________________________
> ovsdb-dev mailing list
> ovsdb-dev@...
> https://lists.opendaylight.org/mailman/listinfo/ovsdb-dev
>


Re: extract ovsdb library for use in other projects

Sam Hague
 

Shashank,

look at the ovsdb/southbound-impl module and see how the ovsdb lib is used. The library is already non-osgi so you just need to use it in the same way as southbound-impl.

Thanks, Sam

----- Original Message -----
From: "Shashank Shanbhag" <shashank@...>
To: ovsdb-dev@...
Sent: Thursday, June 11, 2015 2:18:38 AM
Subject: [ovsdb-dev] extract ovsdb library for use in other projects

Hello,
Any pointer would be really helpful.

The opendaylight/ovsdb/library README (on github[0]) mentions that the
library can be used independently [1]. I'm trying to extract the library out
into a separate maven artifact to use in projects minus osgi and other
opendaylight dependencies. What would be the best approach to do this? I see
osgi as a requirement in org.opendaylight.ovsdb.lib.osgi.

Thanks!
Shashank
[0] https://github.com/opendaylight/ovsdb
[1]
- library : Contains Schema-independent library that is a reference
implementation for RFC 7047.
This module doesn't depend on any of the Opendaylight components.
This library module can also be used independently in a non-OSGi
environment.


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


Re: Openstack Integration documentation

Sam Hague
 

Vasanthan,

here are some links for using pure openstack neutron with openvswitch and odl:

[1] https://wiki.opendaylight.org/view/OVSDB_Integration:Main
[2] https://wiki.opendaylight.org/view/OVSDB:Helium_and_Openstack_on_Fedora20
[3] http://www.flaviof.com/blog/work/how-to-odl-with-openstack-part1.html

Helium and Lithium work in much the same way which is probably what you have seen in [2]. The difference in config is really on the OpenStack side. For kilo the ml2 plugins were moved out of tree from neutron so the config is slightly different. [3] link above shows what that looks like for kilo. The main difference is you just point to another repo - networking_odl.

Thanks, Sam

----- Original Message -----
From: "Vasanthan Balasubram" <Vasanthan_Balasubram@...>
To: ovsdb-dev@...
Sent: Thursday, June 11, 2015 7:12:24 AM
Subject: [ovsdb-dev] Openstack Integration documentation

Hi,
Any documentation/procedure to integrate the Openstack (Kilo) with
Opendaylight(Lithium RC0/RC1)?

I planning to setup this environment in multi-node(s) way, (i.e 1 +1
openstack controller & compute node and integrated with opendaylight
controller on another node)

Any help/documents much appreciated.

I can see all documentation/demo's with Openstack with Helinum release.Is
there any difference with Lithium release?

Thanks
Vasanthan

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


Re: Openstack Integration documentation

Edward Warnicke <hagbard@...>
 

Looping in the neutron project and groupbasedpolicy as well.

Ed

On Thu, Jun 11, 2015 at 4:12 AM, <Vasanthan_Balasubram@...> wrote:
Hi,
Any documentation/procedure to integrate the Openstack (Kilo) with Opendaylight(Lithium RC0/RC1)?

I planning to setup this environment in multi-node(s) way, (i.e 1 +1 openstack  controller & compute node and integrated with opendaylight controller on another node)

Any help/documents much appreciated.

I can see all documentation/demo's with Openstack with Helinum release.Is there any difference with Lithium release?

Thanks
Vasanthan

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



Openstack Integration documentation

Vasanthan_Balasubram@...
 

Hi,
Any documentation/procedure to integrate the Openstack (Kilo) with Opendaylight(Lithium RC0/RC1)?

I planning to setup this environment in multi-node(s) way, (i.e 1 +1 openstack  controller & compute node and integrated with opendaylight controller on another node)

Any help/documents much appreciated.

I can see all documentation/demo's with Openstack with Helinum release.Is there any difference with Lithium release?

Thanks
Vasanthan


extract ovsdb library for use in other projects

Shashank
 

Hello,
Any pointer would be really helpful.

The opendaylight/ovsdb/library README (on github[0]) mentions that the library can be used independently [1]. I'm trying to extract the library out into a separate maven artifact to use in projects minus osgi and other opendaylight dependencies. What would be the best approach to do this?  I see osgi as a requirement in org.opendaylight.ovsdb.lib.osgi.

Thanks!
Shashank
[0] https://github.com/opendaylight/ovsdb
[1]
- library : Contains Schema-independent library that is a reference implementation for RFC 7047.
            This module doesn't depend on any of the Opendaylight components.
            This library module can also be used independently in a non-OSGi environment.


Re: [integration-dev] System Test for OVSDB

Luhrsen, Jamo <james.luhrsen@...>
 

good news, ovsdb!

thanks for all the work, Chaudhry.

JamO

On Jun 10, 2015, at 1:35 PM, Luis Gomez <ecelgp@...<mailto:ecelgp@...>> wrote:

Hi ovsdb devs,

You finally got your first system test in CI thanks to our ODL intern Chaudhry:

https://jenkins.opendaylight.org/releng/view/ovsdb/job/ovsdb-csit-1node-cds-southbound-only-stable-lithium/

This test so far covers 2 things:

- Basic CRUD bridge/port methods for a new OVS switch
- Basic CRUD bridge/port methods for an existing switch

I will show and explain this system test the next ovsdb call (I am not sure Chaudhry can make it as he is in IST).

I have also some ideas going forward like testing OpenFlow VxLAN extensions but you will tell me more after the presentation.

BR/Luis

_______________________________________________
integration-dev mailing list
integration-dev@...<mailto:integration-dev@...>
https://lists.opendaylight.org/mailman/listinfo/integration-dev


System Test for OVSDB

Luis Gomez
 

Hi ovsdb devs,

You finally got your first system test in CI thanks to our ODL intern Chaudhry:


This test so far covers 2 things:

- Basic CRUD bridge/port methods for a new OVS switch
- Basic CRUD bridge/port methods for an existing switch

I will show and explain this system test the next ovsdb call (I am not sure Chaudhry can make it as he is in IST).

I have also some ideas going forward like testing OpenFlow VxLAN extensions but you will tell me more after the presentation.

BR/Luis


Re: sample [raw] output of openstack<->odl communication

Flavio Fernandes <ffernand@...>
 


Added postman collection [1] you can use to repeat these steps.

To emulate creation of ovs ports that go with these steps, look at the description of the entries [2]:
  - Add Neutron Port For dhcp sub1
  - Add Neutron Port For vm1

— flavio





On Jun 9, 2015, at 12:24 PM, Flavio Fernandes <ffernand@...> wrote:

Hi Mat,

In this example, I stack a single o/s node and ran the following commands: [cmds]

It will:
- create tenant, user (lines 8, 9)
- create external net for tenant (line 15)
- create external subnet (line 18)
In context of tenant, it will:
- create tenant router (line 38)
- set router gateway (line 39)
- create tenant internal net and subnet (lines 41, 42)
- create router interface on tenant internal subnet (line 43)
- boot a tenant vm (line 46)
- create floating ip and associate it with tenant vm (lines 48, 50)


A txt for neutron->odl is here [capTxt] a wireshark capture is here [capBin].
If you look at [karaf] karaf.log, you can see a lot of info on how that percolates into odl’s ovsdb netvirt.
A history of ovs commands that happened in the O/S node are here [ovsLog].

The commands used:

- capture to screen:
   sudo tcpdump -Ann -i eth1 tcp port 8080 and 'tcp[13] & 8!=0' | tee tcpdump.txt

- capture to file:
   sudo tcpdump -vv -w tcpdump.cap -i eth1 -s 0 tcp port 8080

- dump ovs history (thanks shague!):
   ovsdb-tool -mm show-log

— flavio

[cmds]: https://gist.github.com/9bc7812997ec629a0518
[console]: https://gist.github.com/84c925de41dba226b986
[capTxt]: https://dl.dropboxusercontent.com/u/86298/simpleNeutronCapture/tcpdump.txt
[capBin]: https://dl.dropboxusercontent.com/u/86298/simpleNeutronCapture/tcpdump.cap
[karaf]: https://dl.dropboxusercontent.com/u/86298/simpleNeutronCapture/karaf.log
[ovsLog]: https://gist.github.com/cd64c801b55cef23a4db

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


sample [raw] output of openstack<->odl communication

Flavio Fernandes <ffernand@...>
 

Hi Mat,

In this example, I stack a single o/s node and ran the following commands: [cmds]

It will:
- create tenant, user (lines 8, 9)
- create external net for tenant (line 15)
- create external subnet (line 18)
In context of tenant, it will:
- create tenant router (line 38)
- set router gateway (line 39)
- create tenant internal net and subnet (lines 41, 42)
- create router interface on tenant internal subnet (line 43)
- boot a tenant vm (line 46)
- create floating ip and associate it with tenant vm (lines 48, 50)


A txt for neutron->odl is here [capTxt] a wireshark capture is here [capBin].
If you look at [karaf] karaf.log, you can see a lot of info on how that percolates into odl’s ovsdb netvirt.
A history of ovs commands that happened in the O/S node are here [ovsLog].

The commands used:

- capture to screen:
sudo tcpdump -Ann -i eth1 tcp port 8080 and 'tcp[13] & 8!=0' | tee tcpdump.txt

- capture to file:
sudo tcpdump -vv -w tcpdump.cap -i eth1 -s 0 tcp port 8080

- dump ovs history (thanks shague!):
ovsdb-tool -mm show-log

— flavio

[cmds]: https://gist.github.com/9bc7812997ec629a0518
[console]: https://gist.github.com/84c925de41dba226b986
[capTxt]: https://dl.dropboxusercontent.com/u/86298/simpleNeutronCapture/tcpdump.txt
[capBin]: https://dl.dropboxusercontent.com/u/86298/simpleNeutronCapture/tcpdump.cap
[karaf]: https://dl.dropboxusercontent.com/u/86298/simpleNeutronCapture/karaf.log
[ovsLog]: https://gist.github.com/cd64c801b55cef23a4db


Re: ODL OVSDB hardware vtep support initial kick-off

Garg, Sumit <sumit@...>
 

Sending output of my experimentation to ovsdb-dev.


# This is a script that I had written to document my experimentation
# using 4 machines:
#
# [A]----(b)----[C]----(d)----[E]----(f)----[G]
# [A] - Physical Server #1 (it was actually a Linux end host)
# (b) - IP over Ethernet link connecting server #1 to switch #1
# [C] - Physical Switch #1 with VTEP functionality (in my setup
# this was actually a Linux server with 2 NIC running OVS)
# (d) - VXLAN tunnel over IP over L2 Ethernet.
# [E] - Like [C], but for the other side
# (f) - Like (b), but for the other side
# [G] - like [A], but for the other side
#
# OVS should not be installed on [C] or [E] as part of the OS install.
# When InstallOVS is set to '1', the script downloads and compiles OVS.
# It then installs OVS under ~/Desktop/
#
#
# Disclaimer:
# -----------
# This is not production ready and MUST not be run directly. It makes
# a lot of assumptions about the underlying server & OS.
#
# Please use the script (i.e. the commands listed here-in) as a starting
# point and customize the same as appropriate for your scenario.
#
# Personal, I don't run the script directly. Instead I copy and paste
# the commands one-at-a-time to my console session.
#
# The commands should be run as an oridinary user. sudo is used to get
# root access as needed.




--
Sumit Garg
Extreme Networks
sumit@...
+1 (919) 595-4971







On 6/9/15, 9:56 AM, "Yapeng Wu" <Yapeng.Wu@...> wrote:

Hello, we have interests to work on this part as well. Please include me
in the discussion.

Sumit, can you share the scripts to the ovsdb-dev mailing list?

Thanks,
Yapeng


-----Original Message-----
From: ovsdb-dev-bounces@...
[mailto:ovsdb-dev-bounces@...] On Behalf Of Sam Hague
Sent: Tuesday, June 09, 2015 9:23 AM
To: Dayavanti Gopal Kamath; ovsdb-dev
Cc: Chris Wright; Swaminathan Vasudevan (PNB Roseville)
(swaminathan.vasudevan@...); sumit@...; Maruti Haridas
Kamat (maruti.kamat@...); afredette@...; Ravi Sundareswaran;
Abhijit Kumbhare; Ravi Sabapathy; Aswin' 'Suryanarayanan; Hema
Gopalkrishnan; Ravindra' 'Kenchappa
Subject: Re: [ovsdb-dev] ODL OVSDB hardware vtep support initial kick-off

including ovsdb-dev

----- Original Message -----
From: "Dayavanti Gopal Kamath" <dayavanti.gopal.kamath@...>
To: "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@...)" <maruti.kamat@...>, "Swaminathan Vasudevan
(PNB Roseville) (swaminathan.vasudevan@...)"
<swaminathan.vasudevan@...>, "afredette@..."
<afredette@...>, "Ravi Sabapathy"
<Ravi_Sabapathy@...>, "Ravindra' 'Kenchappa"
<ravindra.kenchappa@...>, sumit@..., "Hema
Gopalkrishnan" <hema.gopalkrishnan@...>, "Vishal Thapar"
<vishal.thapar@...>
Sent: Tuesday, June 9, 2015 12:31:06 AM
Subject: FW: ODL OVSDB hardware vtep support initial kick-off

Thanks for sharing the script and your inputs sumit!

Everyone, that was a good start to the activity.
Here's my notes captured from our discussion, please add as needed -

- Hardware_vtep schema md-sal model scoped to ovsdb project

- Net-virt module updates to support the schema and tie it to
neutron NSF

- AI : Maruti to provide L2-gateway functionality overview,
and
share thoughts on how ODL agent could be implemented after discussing
with Armando etc.

- Initial testing of the project can start with OVS, schema
can be
loaded manually, and the emulator script sumit has attached

- Statistics and L3 support - phase 2

- Need to start work on Project proposal and wiki

- Abhijit to get a webex slot from Phil Robb

Thanks!
daya

From: Garg, Sumit [mailto:sumit@...]
Sent: Monday, June 08, 2015 11:03 PM
To: Dayavanti Gopal Kamath
Subject: Re: ODL OVSDB hardware vtep support initial kick-off

Hello Daya,

I've been working on the hardware_vtep schema at Extreme for sometime.
I'm excited that you guys are undertaking the effort to include
support for this in ODL.

There are two tools in the OVS distribution:

* $OVSROOT/vtep/vtep-ctl - this is C code and is analogous to
ovs-vsctl.
It is a simulator for an NVC (aka controller) and can be used to send
OVSDB commands to populate the hardware_vtep schema (e.g. Create
logical
switches, create MAC entries)
* $OVSROOT/vtep/ovs-vtep - this is a Python script and emulates a
hardware VTEP. It consumes the information in the hardware_vtep
schema and
then programs the OVS dataplane to enable traffic forwarding.
I'm attaching a script that I had written to document my
experimentation using 4 machines:

[A]----(b)----[C]----(d)----[E]----(f)----[G]

[A] - Physical Server #1 (it was actually a Linux end host)
(b) - IP over Ethernet link connecting server #1 to switch #1 [C] -
Physical Switch #1 with VTEP functionality (it was actually a Linux
server with 2 NIC running OVS)
(d) - VXLAN tunnel over IP over L2 Ethernet.
[E] - Like [C], but for the other side
(f) - Like (b), but for the other side [G] - like [A], but for the
other side

OVS should not be installed on [C] or [E] as part of the OS install.
The script downloads and compiles OVS; it then installs OVS under
~/Desktop/

The script makes a lot of assumptions about the underlying OS. So,
please use it carefully. Feel free to forward my email to others.

/Sumit
--

Sumit Garg

Extreme Networks

sumit@...<mailto:sumit@...>

+1 (919) 595-4971


From: Andre Fredette
<afredette@...<mailto:afredette@...>>
Date: Monday, June 8, 2015 at 8:13 AM
To: Sumit Garg
<sumit@...<mailto:sumit@...>>,
Tim Bourne
<tbourne@...<mailto:tbourne@...>>,
Vikram Pendharkar
<vpendharkar@...<mailto:vpendharkar@...
m>>
Subject: Re: ODL OVSDB hardware vtep support initial kick-off

Sumit,

I just added you to the meeting, so you may get a proper invitation.

In any case, you have the pertinent info below.

Andre

On 6/8/15 7:57 AM, Garg, Sumit wrote:
Thanks for the heads-up.

The invite is not opening correctly in my calendar. Can you please
confirm the details:

Toll Free USA: 877-748-5444
PIN: 546875
Passcode: 9084 1259#
Time: 2015-06-08 at 11:00 EDT
--

Sumit Garg

Extreme Networks

sumit@...<mailto:sumit@...>

+1 (919) 595-4971


From: Andre Fredette
<afredette@...<mailto:afredette@...>>
Date: Monday, June 8, 2015 at 7:39 AM
To: Sumit Garg
<sumit@...<mailto:sumit@...>>,
Tim Bourne
<tbourne@...<mailto:tbourne@...>>,
Vikram Pendharkar
<vpendharkar@...<mailto:vpendharkar@...
m>>
Subject: Fwd: ODL OVSDB hardware vtep support initial kick-off

Hello All,

FYI, If Extreme is interested in participating in the effort to add
hardware VTEP support to OpenDaylight, talks are beginning.

Andre

-------- Forwarded Message --------
Subject:

ODL OVSDB hardware vtep support initial kick-off

Date:

Mon, 8 Jun 2015 06:20:22 +0000

From:

Dayavanti Gopal Kamath
<dayavanti.gopal.kamath@...><mailto:dayavanti.gopal.kamath@er
icsson.com>

To:

Kenchappa, Ravindra
<ravindra.kenchappa@...><mailto:ravindra.kenchappa@...>,
Suryanarayanan, Aswin
<aswin.suryanarayanan@...><mailto:aswin.suryanarayanan@...>,
Anil Vishnoi <vishnoianil@...><mailto:vishnoianil@...>,
Flavio Fernandes <ffernand@...><mailto:ffernand@...>,
Sam Hague <shague@...><mailto:shague@...>, Chris Wright
<chrisw@...><mailto:chrisw@...>, Kyle Mestery
<mestery@...><mailto:mestery@...>, Prem sankar G
<prem.sankar.g@...><mailto:prem.sankar.g@...>,
Abhijit Kumbhare
<abhijit.kumbhare@...><mailto:abhijit.kumbhare@...>,
Ravi Sundareswaran
<ravi.sundareswaran@...><mailto:ravi.sundareswaran@...
om>, Kamat, Maruti Haridas
(maruti.kamat@...<mailto:maruti.kamat@...>)
<maruti.kamat@...><mailto:maruti.kamat@...>, Vasudevan,
Swaminathan (PNB Roseville)
(swaminathan.vasudevan@...<mailto:swaminathan.vasudevan@...>)
<swaminathan.vasudevan@...><mailto:swaminathan.vasudevan@...>,
afredette@...<mailto:afredette@...><afredette@...
<mailto:afredette@...>,
Ravi_Sabapathy@...<mailto:Ravi_Sabapathy@...><Ravi_Sabapathy
@dell.com><mailto:Ravi_Sabapathy@...>





________________________________

DISCLAIMER:
This e-mail and any attachments to it may contain confidential and
proprietary material and is solely for the use of the intended
recipient.
Any review, use, disclosure, distribution or copying of this
transmittal is prohibited except by or on behalf of the intended
recipient. If you have received this transmittal in error, please
notify the sender and destroy this e-mail and any attachments and all
copies, whether electronic or printed.


________________________________

DISCLAIMER:
This e-mail and any attachments to it may contain confidential and
proprietary material and is solely for the use of the intended
recipient.
Any review, use, disclosure, distribution or copying of this
transmittal is prohibited except by or on behalf of the intended
recipient. If you have received this transmittal in error, please
notify the sender and destroy this e-mail and any attachments and all
copies, whether electronic or printed.

________________________________

DISCLAIMER:
This e-mail and any attachments to it may contain confidential and proprietary material and is solely for the use of the intended recipient. Any review, use, disclosure, distribution or copying of this transmittal is prohibited except by or on behalf of the intended recipient. If you have received this transmittal in error, please notify the sender and destroy this e-mail and any attachments and all copies, whether electronic or printed.


Re: ODL OVSDB hardware vtep support initial kick-off

Garg, Sumit <sumit@...>
 

Sending to ovsdb-dev:


# This is a script that I had written to document my experimentation
# using 4 machines:
#
# [A]----(b)----[C]----(d)----[E]----(f)----[G]
# [A] - Physical Server #1 (it was actually a Linux end host)
# (b) - IP over Ethernet link connecting server #1 to switch #1
# [C] - Physical Switch #1 with VTEP functionality (in my setup
# this was actually a Linux server with 2 NIC running OVS)
# (d) - VXLAN tunnel over IP over L2 Ethernet.
# [E] - Like [C], but for the other side
# (f) - Like (b), but for the other side
# [G] - like [A], but for the other side
#
# OVS should not be installed on [C] or [E] as part of the OS install.
# When InstallOVS is set to '1', the script downloads and compiles OVS.
# It then installs OVS under ~/Desktop/
#
#
# Disclaimer:
# -----------
# This is not production ready and MUST not be run directly. It makes
# a lot of assumptions about the underlying server & OS.
#
# Please use the script (i.e. the commands listed here-in) as a starting
# point and customize the same as appropriate for your scenario.
#
# Personal, I don't run the script directly. Instead I copy and paste
# the commands one-at-a-time to my console session.
#
# The commands should be run as an oridinary user. sudo is used to get
# root access as needed.



--
Sumit Garg
Extreme Networks
sumit@...
+1 (919) 595-4971








On 6/9/15, 9:56 AM, "Yapeng Wu" <Yapeng.Wu@...> wrote:

Hello, we have interests to work on this part as well. Please include me
in the discussion.

Sumit, can you share the scripts to the ovsdb-dev mailing list?

Thanks,
Yapeng


-----Original Message-----
From: ovsdb-dev-bounces@...
[mailto:ovsdb-dev-bounces@...] On Behalf Of Sam Hague
Sent: Tuesday, June 09, 2015 9:23 AM
To: Dayavanti Gopal Kamath; ovsdb-dev
Cc: Chris Wright; Swaminathan Vasudevan (PNB Roseville)
(swaminathan.vasudevan@...); sumit@...; Maruti Haridas
Kamat (maruti.kamat@...); afredette@...; Ravi Sundareswaran;
Abhijit Kumbhare; Ravi Sabapathy; Aswin' 'Suryanarayanan; Hema
Gopalkrishnan; Ravindra' 'Kenchappa
Subject: Re: [ovsdb-dev] ODL OVSDB hardware vtep support initial kick-off

including ovsdb-dev

----- Original Message -----
From: "Dayavanti Gopal Kamath" <dayavanti.gopal.kamath@...>
To: "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@...)" <maruti.kamat@...>, "Swaminathan Vasudevan
(PNB Roseville) (swaminathan.vasudevan@...)"
<swaminathan.vasudevan@...>, "afredette@..."
<afredette@...>, "Ravi Sabapathy"
<Ravi_Sabapathy@...>, "Ravindra' 'Kenchappa"
<ravindra.kenchappa@...>, sumit@..., "Hema
Gopalkrishnan" <hema.gopalkrishnan@...>, "Vishal Thapar"
<vishal.thapar@...>
Sent: Tuesday, June 9, 2015 12:31:06 AM
Subject: FW: ODL OVSDB hardware vtep support initial kick-off

Thanks for sharing the script and your inputs sumit!

Everyone, that was a good start to the activity.
Here's my notes captured from our discussion, please add as needed -

- Hardware_vtep schema md-sal model scoped to ovsdb project

- Net-virt module updates to support the schema and tie it to
neutron NSF

- AI : Maruti to provide L2-gateway functionality overview,
and
share thoughts on how ODL agent could be implemented after discussing
with Armando etc.

- Initial testing of the project can start with OVS, schema
can be
loaded manually, and the emulator script sumit has attached

- Statistics and L3 support - phase 2

- Need to start work on Project proposal and wiki

- Abhijit to get a webex slot from Phil Robb

Thanks!
daya

From: Garg, Sumit [mailto:sumit@...]
Sent: Monday, June 08, 2015 11:03 PM
To: Dayavanti Gopal Kamath
Subject: Re: ODL OVSDB hardware vtep support initial kick-off

Hello Daya,

I've been working on the hardware_vtep schema at Extreme for sometime.
I'm excited that you guys are undertaking the effort to include
support for this in ODL.

There are two tools in the OVS distribution:

* $OVSROOT/vtep/vtep-ctl - this is C code and is analogous to
ovs-vsctl.
It is a simulator for an NVC (aka controller) and can be used to send
OVSDB commands to populate the hardware_vtep schema (e.g. Create
logical
switches, create MAC entries)
* $OVSROOT/vtep/ovs-vtep - this is a Python script and emulates a
hardware VTEP. It consumes the information in the hardware_vtep
schema and
then programs the OVS dataplane to enable traffic forwarding.
I'm attaching a script that I had written to document my
experimentation using 4 machines:

[A]----(b)----[C]----(d)----[E]----(f)----[G]

[A] - Physical Server #1 (it was actually a Linux end host)
(b) - IP over Ethernet link connecting server #1 to switch #1 [C] -
Physical Switch #1 with VTEP functionality (it was actually a Linux
server with 2 NIC running OVS)
(d) - VXLAN tunnel over IP over L2 Ethernet.
[E] - Like [C], but for the other side
(f) - Like (b), but for the other side [G] - like [A], but for the
other side

OVS should not be installed on [C] or [E] as part of the OS install.
The script downloads and compiles OVS; it then installs OVS under
~/Desktop/

The script makes a lot of assumptions about the underlying OS. So,
please use it carefully. Feel free to forward my email to others.

/Sumit
--

Sumit Garg

Extreme Networks

sumit@...<mailto:sumit@...>

+1 (919) 595-4971




________________________________

DISCLAIMER:
This e-mail and any attachments to it may contain confidential and proprietary material and is solely for the use of the intended recipient. Any review, use, disclosure, distribution or copying of this transmittal is prohibited except by or on behalf of the intended recipient. If you have received this transmittal in error, please notify the sender and destroy this e-mail and any attachments and all copies, whether electronic or printed.


Re: ODL OVSDB hardware vtep support initial kick-off

Yapeng Wu
 

Hello, we have interests to work on this part as well. Please include me in the discussion.

Sumit, can you share the scripts to the ovsdb-dev mailing list?

Thanks,
Yapeng

-----Original Message-----
From: ovsdb-dev-bounces@... [mailto:ovsdb-dev-bounces@...] On Behalf Of Sam Hague
Sent: Tuesday, June 09, 2015 9:23 AM
To: Dayavanti Gopal Kamath; ovsdb-dev
Cc: Chris Wright; Swaminathan Vasudevan (PNB Roseville) (swaminathan.vasudevan@...); sumit@...; Maruti Haridas Kamat (maruti.kamat@...); afredette@...; Ravi Sundareswaran; Abhijit Kumbhare; Ravi Sabapathy; Aswin' 'Suryanarayanan; Hema Gopalkrishnan; Ravindra' 'Kenchappa
Subject: Re: [ovsdb-dev] ODL OVSDB hardware vtep support initial kick-off

including ovsdb-dev

----- Original Message -----
From: "Dayavanti Gopal Kamath" <dayavanti.gopal.kamath@...>
To: "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@...)" <maruti.kamat@...>, "Swaminathan Vasudevan (PNB Roseville) (swaminathan.vasudevan@...)"
<swaminathan.vasudevan@...>, "afredette@..." <afredette@...>, "Ravi Sabapathy"
<Ravi_Sabapathy@...>, "Ravindra' 'Kenchappa"
<ravindra.kenchappa@...>, sumit@..., "Hema
Gopalkrishnan" <hema.gopalkrishnan@...>, "Vishal Thapar"
<vishal.thapar@...>
Sent: Tuesday, June 9, 2015 12:31:06 AM
Subject: FW: ODL OVSDB hardware vtep support initial kick-off

Thanks for sharing the script and your inputs sumit!

Everyone, that was a good start to the activity.
Here's my notes captured from our discussion, please add as needed -

- Hardware_vtep schema md-sal model scoped to ovsdb project

- Net-virt module updates to support the schema and tie it to
neutron NSF

- AI : Maruti to provide L2-gateway functionality overview, and
share thoughts on how ODL agent could be implemented after discussing
with Armando etc.

- Initial testing of the project can start with OVS, schema can be
loaded manually, and the emulator script sumit has attached

- Statistics and L3 support - phase 2

- Need to start work on Project proposal and wiki

- Abhijit to get a webex slot from Phil Robb

Thanks!
daya

From: Garg, Sumit [mailto:sumit@...]
Sent: Monday, June 08, 2015 11:03 PM
To: Dayavanti Gopal Kamath
Subject: Re: ODL OVSDB hardware vtep support initial kick-off

Hello Daya,

I've been working on the hardware_vtep schema at Extreme for sometime.
I'm excited that you guys are undertaking the effort to include
support for this in ODL.

There are two tools in the OVS distribution:

* $OVSROOT/vtep/vtep-ctl - this is C code and is analogous to ovs-vsctl.
It is a simulator for an NVC (aka controller) and can be used to send
OVSDB commands to populate the hardware_vtep schema (e.g. Create logical
switches, create MAC entries)
* $OVSROOT/vtep/ovs-vtep - this is a Python script and emulates a
hardware VTEP. It consumes the information in the hardware_vtep schema and
then programs the OVS dataplane to enable traffic forwarding.
I'm attaching a script that I had written to document my
experimentation using 4 machines:

[A]----(b)----[C]----(d)----[E]----(f)----[G]

[A] - Physical Server #1 (it was actually a Linux end host)
(b) - IP over Ethernet link connecting server #1 to switch #1 [C] -
Physical Switch #1 with VTEP functionality (it was actually a Linux
server with 2 NIC running OVS)
(d) - VXLAN tunnel over IP over L2 Ethernet.
[E] - Like [C], but for the other side
(f) - Like (b), but for the other side [G] - like [A], but for the
other side

OVS should not be installed on [C] or [E] as part of the OS install.
The script downloads and compiles OVS; it then installs OVS under
~/Desktop/

The script makes a lot of assumptions about the underlying OS. So,
please use it carefully. Feel free to forward my email to others.

/Sumit
--

Sumit Garg

Extreme Networks

sumit@...<mailto:sumit@...>

+1 (919) 595-4971


From: Andre Fredette
<afredette@...<mailto:afredette@...>>
Date: Monday, June 8, 2015 at 8:13 AM
To: Sumit Garg
<sumit@...<mailto:sumit@...>>,
Tim Bourne
<tbourne@...<mailto:tbourne@...>>,
Vikram Pendharkar
<vpendharkar@...<mailto:vpendharkar@...
m>>
Subject: Re: ODL OVSDB hardware vtep support initial kick-off

Sumit,

I just added you to the meeting, so you may get a proper invitation.

In any case, you have the pertinent info below.

Andre

On 6/8/15 7:57 AM, Garg, Sumit wrote:
Thanks for the heads-up.

The invite is not opening correctly in my calendar. Can you please
confirm the details:

Toll Free USA: 877-748-5444
PIN: 546875
Passcode: 9084 1259#
Time: 2015-06-08 at 11:00 EDT
--

Sumit Garg

Extreme Networks

sumit@...<mailto:sumit@...>

+1 (919) 595-4971


From: Andre Fredette
<afredette@...<mailto:afredette@...>>
Date: Monday, June 8, 2015 at 7:39 AM
To: Sumit Garg
<sumit@...<mailto:sumit@...>>,
Tim Bourne
<tbourne@...<mailto:tbourne@...>>,
Vikram Pendharkar
<vpendharkar@...<mailto:vpendharkar@...
m>>
Subject: Fwd: ODL OVSDB hardware vtep support initial kick-off

Hello All,

FYI, If Extreme is interested in participating in the effort to add
hardware VTEP support to OpenDaylight, talks are beginning.

Andre

-------- Forwarded Message --------
Subject:

ODL OVSDB hardware vtep support initial kick-off

Date:

Mon, 8 Jun 2015 06:20:22 +0000

From:

Dayavanti Gopal Kamath
<dayavanti.gopal.kamath@...><mailto:dayavanti.gopal.kamath@er
icsson.com>

To:

Kenchappa, Ravindra
<ravindra.kenchappa@...><mailto:ravindra.kenchappa@...>,
Suryanarayanan, Aswin
<aswin.suryanarayanan@...><mailto:aswin.suryanarayanan@...>,
Anil Vishnoi <vishnoianil@...><mailto:vishnoianil@...>,
Flavio Fernandes <ffernand@...><mailto:ffernand@...>,
Sam Hague <shague@...><mailto:shague@...>, Chris Wright
<chrisw@...><mailto:chrisw@...>, Kyle Mestery
<mestery@...><mailto:mestery@...>, Prem sankar G
<prem.sankar.g@...><mailto:prem.sankar.g@...>,
Abhijit Kumbhare
<abhijit.kumbhare@...><mailto:abhijit.kumbhare@...>,
Ravi Sundareswaran
<ravi.sundareswaran@...><mailto:ravi.sundareswaran@...
om>, Kamat, Maruti Haridas
(maruti.kamat@...<mailto:maruti.kamat@...>)
<maruti.kamat@...><mailto:maruti.kamat@...>, Vasudevan,
Swaminathan (PNB Roseville)
(swaminathan.vasudevan@...<mailto:swaminathan.vasudevan@...>)
<swaminathan.vasudevan@...><mailto:swaminathan.vasudevan@...>,
afredette@...<mailto:afredette@...><afredette@...
<mailto:afredette@...>,
Ravi_Sabapathy@...<mailto:Ravi_Sabapathy@...><Ravi_Sabapathy
@dell.com><mailto:Ravi_Sabapathy@...>





________________________________

DISCLAIMER:
This e-mail and any attachments to it may contain confidential and
proprietary material and is solely for the use of the intended recipient.
Any review, use, disclosure, distribution or copying of this
transmittal is prohibited except by or on behalf of the intended
recipient. If you have received this transmittal in error, please
notify the sender and destroy this e-mail and any attachments and all
copies, whether electronic or printed.


________________________________

DISCLAIMER:
This e-mail and any attachments to it may contain confidential and
proprietary material and is solely for the use of the intended recipient.
Any review, use, disclosure, distribution or copying of this
transmittal is prohibited except by or on behalf of the intended
recipient. If you have received this transmittal in error, please
notify the sender and destroy this e-mail and any attachments and all
copies, whether electronic or printed.


Re: ODL OVSDB hardware vtep support initial kick-off

Sam Hague
 

including ovsdb-dev

----- Original Message -----
From: "Dayavanti Gopal Kamath" <dayavanti.gopal.kamath@...>
To: "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@...)" <maruti.kamat@...>, "Swaminathan Vasudevan (PNB Roseville) (swaminathan.vasudevan@...)"
<swaminathan.vasudevan@...>, "afredette@..." <afredette@...>, "Ravi Sabapathy"
<Ravi_Sabapathy@...>, "Ravindra' 'Kenchappa" <ravindra.kenchappa@...>, sumit@..., "Hema
Gopalkrishnan" <hema.gopalkrishnan@...>, "Vishal Thapar" <vishal.thapar@...>
Sent: Tuesday, June 9, 2015 12:31:06 AM
Subject: FW: ODL OVSDB hardware vtep support initial kick-off

Thanks for sharing the script and your inputs sumit!

Everyone, that was a good start to the activity.
Here's my notes captured from our discussion, please add as needed -

- Hardware_vtep schema md-sal model scoped to ovsdb project

- Net-virt module updates to support the schema and tie it to
neutron NSF

- AI : Maruti to provide L2-gateway functionality overview, and
share thoughts on how ODL agent could be implemented after discussing with
Armando etc.

- Initial testing of the project can start with OVS, schema can be
loaded manually, and the emulator script sumit has attached

- Statistics and L3 support - phase 2

- Need to start work on Project proposal and wiki

- Abhijit to get a webex slot from Phil Robb

Thanks!
daya

From: Garg, Sumit [mailto:sumit@...]
Sent: Monday, June 08, 2015 11:03 PM
To: Dayavanti Gopal Kamath
Subject: Re: ODL OVSDB hardware vtep support initial kick-off

Hello Daya,

I've been working on the hardware_vtep schema at Extreme for sometime. I'm
excited that you guys are undertaking the effort to include support for this
in ODL.

There are two tools in the OVS distribution:

* $OVSROOT/vtep/vtep-ctl - this is C code and is analogous to ovs-vsctl.
It is a simulator for an NVC (aka controller) and can be used to send
OVSDB commands to populate the hardware_vtep schema (e.g. Create logical
switches, create MAC entries)
* $OVSROOT/vtep/ovs-vtep - this is a Python script and emulates a
hardware VTEP. It consumes the information in the hardware_vtep schema and
then programs the OVS dataplane to enable traffic forwarding.
I'm attaching a script that I had written to document my experimentation
using 4 machines:

[A]----(b)----[C]----(d)----[E]----(f)----[G]

[A] - Physical Server #1 (it was actually a Linux end host)
(b) - IP over Ethernet link connecting server #1 to switch #1
[C] - Physical Switch #1 with VTEP functionality (it was actually a Linux
server with 2 NIC running OVS)
(d) - VXLAN tunnel over IP over L2 Ethernet.
[E] - Like [C], but for the other side
(f) - Like (b), but for the other side
[G] - like [A], but for the other side

OVS should not be installed on [C] or [E] as part of the OS install. The
script downloads and compiles OVS; it then installs OVS under ~/Desktop/

The script makes a lot of assumptions about the underlying OS. So, please use
it carefully. Feel free to forward my email to others.

/Sumit
--

Sumit Garg

Extreme Networks

sumit@...<mailto:sumit@...>

+1 (919) 595-4971


From: Andre Fredette <afredette@...<mailto:afredette@...>>
Date: Monday, June 8, 2015 at 8:13 AM
To: Sumit Garg <sumit@...<mailto:sumit@...>>,
Tim Bourne
<tbourne@...<mailto:tbourne@...>>, Vikram
Pendharkar
<vpendharkar@...<mailto:vpendharkar@...>>
Subject: Re: ODL OVSDB hardware vtep support initial kick-off

Sumit,

I just added you to the meeting, so you may get a proper invitation.

In any case, you have the pertinent info below.

Andre

On 6/8/15 7:57 AM, Garg, Sumit wrote:
Thanks for the heads-up.

The invite is not opening correctly in my calendar. Can you please confirm
the details:

Toll Free USA: 877-748-5444
PIN: 546875
Passcode: 9084 1259#
Time: 2015-06-08 at 11:00 EDT
--

Sumit Garg

Extreme Networks

sumit@...<mailto:sumit@...>

+1 (919) 595-4971


From: Andre Fredette <afredette@...<mailto:afredette@...>>
Date: Monday, June 8, 2015 at 7:39 AM
To: Sumit Garg <sumit@...<mailto:sumit@...>>,
Tim Bourne
<tbourne@...<mailto:tbourne@...>>, Vikram
Pendharkar
<vpendharkar@...<mailto:vpendharkar@...>>
Subject: Fwd: ODL OVSDB hardware vtep support initial kick-off

Hello All,

FYI, If Extreme is interested in participating in the effort to add hardware
VTEP support to OpenDaylight, talks are beginning.

Andre

-------- Forwarded Message --------
Subject:

ODL OVSDB hardware vtep support initial kick-off

Date:

Mon, 8 Jun 2015 06:20:22 +0000

From:

Dayavanti Gopal Kamath
<dayavanti.gopal.kamath@...><mailto:dayavanti.gopal.kamath@...>

To:

Kenchappa, Ravindra
<ravindra.kenchappa@...><mailto:ravindra.kenchappa@...>,
Suryanarayanan, Aswin
<aswin.suryanarayanan@...><mailto:aswin.suryanarayanan@...>, Anil
Vishnoi <vishnoianil@...><mailto:vishnoianil@...>, Flavio
Fernandes <ffernand@...><mailto:ffernand@...>, Sam Hague
<shague@...><mailto:shague@...>, Chris Wright
<chrisw@...><mailto:chrisw@...>, Kyle Mestery
<mestery@...><mailto:mestery@...>, Prem sankar G
<prem.sankar.g@...><mailto:prem.sankar.g@...>, Abhijit
Kumbhare
<abhijit.kumbhare@...><mailto:abhijit.kumbhare@...>, Ravi
Sundareswaran
<ravi.sundareswaran@...><mailto:ravi.sundareswaran@...>,
Kamat, Maruti Haridas (maruti.kamat@...<mailto:maruti.kamat@...>)
<maruti.kamat@...><mailto:maruti.kamat@...>, Vasudevan, Swaminathan
(PNB Roseville)
(swaminathan.vasudevan@...<mailto:swaminathan.vasudevan@...>)
<swaminathan.vasudevan@...><mailto:swaminathan.vasudevan@...>,
afredette@...<mailto:afredette@...><afredette@...><mailto:afredette@...>,
Ravi_Sabapathy@...<mailto:Ravi_Sabapathy@...><Ravi_Sabapathy@...><mailto:Ravi_Sabapathy@...>





________________________________

DISCLAIMER:
This e-mail and any attachments to it may contain confidential and
proprietary material and is solely for the use of the intended recipient.
Any review, use, disclosure, distribution or copying of this transmittal is
prohibited except by or on behalf of the intended recipient. If you have
received this transmittal in error, please notify the sender and destroy
this e-mail and any attachments and all copies, whether electronic or
printed.


________________________________

DISCLAIMER:
This e-mail and any attachments to it may contain confidential and
proprietary material and is solely for the use of the intended recipient.
Any review, use, disclosure, distribution or copying of this transmittal is
prohibited except by or on behalf of the intended recipient. If you have
received this transmittal in error, please notify the sender and destroy
this e-mail and any attachments and all copies, whether electronic or
printed.


Re: How do I map OVSDB bridge node to openflow node for getting an OVSDB bridge's openflow node ID?

Yang, Yi Y <yi.y.yang@...>
 

Yes, I saw ovsdb provided ofport for port mapping, thank you very much for your help. But I have one more question here, aussume I attached 3 VMs in an ovs bridge, how does ovsdb handle them in ovsdb network topology? Openflow network topology can handle them by l2switch, 3 VMs will have 3 corresponding host nodes in openflow network toplogy. I don’t think ovsdb has the counertparts there. My point is it will be very great if ovsdb network toplogy can have silimiar nodes, how do you think about it.

 

From: alagalah [mailto:alagalah@...]
Sent: Monday, June 08, 2015 1:57 AM
To: Anil Vishnoi; Yang, Yi Y
Cc: ovsdb-dev@...
Subject: Re: [ovsdb-dev] How do I map OVSDB bridge node to openflow node for getting an OVSDB bridge's openflow node ID?

 

FWIW, I pointed Yi to a couple of places in GBP and SFC where we already do this. 

 

From: Anil Vishnoi <vishnoianil@...>
Date: Sunday, June 7, 2015 at 8:18 AM
To: "Yang, Yi Y" <yi.y.yang@...>
Cc: "ovsdb-dev@..." <ovsdb-dev@...>
Subject: Re: [ovsdb-dev] How do I map OVSDB bridge node to openflow node for getting an OVSDB bridge's openflow node ID?

 

Hi Yi,

 

Sorry for the late response. OVSDB southbound plugin store ofport info in operatioanal data store. So you can use that ofport info to figure out port in openflow switch openflow:<datapath-id>:<ovsdb-ofport>.

 

Thanks

Anil

 

On Thu, Jun 4, 2015 at 6:59 PM, Yang, Yi Y <yi.y.yang@...> wrote:

Anil, thank you so much, I checked it again, I can get openflow node ID using datapath-id.

 

Another question is how I map an OVS port like “tap1” to openflow tp id like “openflow:1:2”?

 

In openflow network topology, l2switch can host nodes that connect to openflow switch, but in OVSDB network topology, I can’t get similar piece. It will be very great if ovsdb can add them. Now I can see full network topology by openflow network topology, but OVSDB can’t provide info of VMs connected to ovs bridge.

 

          {

            "node-id": "host:00:00:00:00:00:01",

            "termination-point": [

              {

                "tp-id": "host:00:00:00:00:00:01"

              }

            ],

            "host-tracker-service:id": "00:00:00:00:00:01",

            "host-tracker-service:addresses": [

              {

                "id": 7,

                "mac": "00:00:00:00:00:01",

                "ip": "10.0.0.1",

                "first-seen": 1431084716588,

                "last-seen": 1431084716588

              }

            ],

            "host-tracker-service:attachment-points": [

              {

                "tp-id": "openflow:1:1",

                "corresponding-tp": "host:00:00:00:00:00:01",

                "active": true

              }

            ]

          }

 

From: Anil Vishnoi [mailto:vishnoianil@...]
Sent: Thursday, June 04, 2015 3:53 PM
To: Vishal Thapar
Cc: Yang, Yi Y; ovsdb-dev@...
Subject: Re: [ovsdb-dev] How do I map OVSDB bridge node to openflow node for getting an OVSDB bridge's openflow node ID?

 

Hi Yi/Vishal,

 

Please refer to ./southbound/southbound-api/src/main/yang/ovsdb.yang file. Southbound plugin augment bridge operational data to topology tree

 

    augment "/topo:network-topology/topo:topology/topo:node" {

        description "Augmentation for bridge nodes managed by ovsdb";

        ext:augment-identifier "ovsdb-bridge-augmentation";

        uses ovsdb-bridge-attributes;

    }

 

Ovsdb-bridge-attributes contains operational data of the bridge and it has datapath-id as one of the element.

 

        leaf datapath-id {

            description "Datapath-id of the bridge";

            type datapath-id;

        }

 

You can use this datapath-id to determine the Openflow registration id "openflow:<datapath-id>". 

 

Thanks

Anil

 

On Thu, Jun 4, 2015 at 12:05 PM, Vishal Thapar <vishal.thapar@...> wrote:

+1

 

I’d also like to know answer to this.

 

From:ovsdb-dev-bounces@... [mailto:ovsdb-dev-bounces@...] On Behalf Of Yang, Yi Y
Sent: 04 June 2015 04:44
To: ovsdb-dev@...
Subject: [ovsdb-dev] How do I map OVSDB bridge node to openflow node for getting an OVSDB bridge's openflow node ID?

 

Hello, guys

 

I need to get openflow node ID for an OVSDB bridge node, in my test environment, I can see node info in MDSAL network topology flow:1 anf ovsdb:1 when I add a new bridge by command “sudo ovs-vsctl add-br br1”, I also can see node info in MDSAL inventory, but I can’t see augmentation for node in inventory, I noticed ovsdb/plugin-mdsal-adapter/src/main/yang/ovsdb-node-inventory.yang augmented inventory node:

 

    augment /inv:nodes/inv:node {

        ext:augment-identifier "ovsdb-managed-node";

        // when "/inv:nodes/inv:node/flowcapable:manufacturer = '*'";

        container ovsdb-bridge {

            uses ovsdb-bridge-attributes;

        }

    }

 

    augment /inv:nodes/inv:node {

        ext:augment-identifier "ovsdb-capable-node";

        uses ovsdb-node-attributes;

}

 

Anybody knows why? In karaf, what feature should I install for this. Here are ovsdb features I have installed.

 

opendaylight-user@root>feature:list -i | grep ovsdb

odl-ovsdb-southbound-api              | 1.1.0-SNAPSHOT      | x         | odl-ovsdb-southbound-1.1.0-SNAPSHOT     | OpenDaylight :: southbound :: api

odl-ovsdb-southbound-impl             | 1.1.0-SNAPSHOT      | x         | odl-ovsdb-southbound-1.1.0-SNAPSHOT     | OpenDaylight :: southbound :: impl

odl-ovsdb-southbound-impl-rest        | 1.1.0-SNAPSHOT      | x         | odl-ovsdb-southbound-1.1.0-SNAPSHOT     | OpenDaylight :: southbound :: impl :: REST

odl-ovsdb-southbound-impl-ui          | 1.1.0-SNAPSHOT      | x         | odl-ovsdb-southbound-1.1.0-SNAPSHOT     | OpenDaylight :: southbound :: impl :: UI

opendaylight-user@root>


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



 

--

Thanks

Anil



 

--

Thanks

Anil

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


Re: How do I map OVSDB bridge node to openflow node for getting an OVSDB bridge's openflow node ID?

alagalah <alagalah@...>
 

FWIW, I pointed Yi to a couple of places in GBP and SFC where we already do this. 

From: Anil Vishnoi <vishnoianil@...>
Date: Sunday, June 7, 2015 at 8:18 AM
To: "Yang, Yi Y" <yi.y.yang@...>
Cc: "ovsdb-dev@..." <ovsdb-dev@...>
Subject: Re: [ovsdb-dev] How do I map OVSDB bridge node to openflow node for getting an OVSDB bridge's openflow node ID?

Hi Yi,

Sorry for the late response. OVSDB southbound plugin store ofport info in operatioanal data store. So you can use that ofport info to figure out port in openflow switch openflow:<datapath-id>:<ovsdb-ofport>.

Thanks
Anil

On Thu, Jun 4, 2015 at 6:59 PM, Yang, Yi Y <yi.y.yang@...> wrote:

Anil, thank you so much, I checked it again, I can get openflow node ID using datapath-id.

 

Another question is how I map an OVS port like “tap1” to openflow tp id like “openflow:1:2”?

 

In openflow network topology, l2switch can host nodes that connect to openflow switch, but in OVSDB network topology, I can’t get similar piece. It will be very great if ovsdb can add them. Now I can see full network topology by openflow network topology, but OVSDB can’t provide info of VMs connected to ovs bridge.

 

          {

            "node-id": "host:00:00:00:00:00:01",

            "termination-point": [

              {

                "tp-id": "host:00:00:00:00:00:01"

              }

            ],

            "host-tracker-service:id": "00:00:00:00:00:01",

            "host-tracker-service:addresses": [

              {

                "id": 7,

                "mac": "00:00:00:00:00:01",

                "ip": "10.0.0.1",

                "first-seen": 1431084716588,

                "last-seen": 1431084716588

              }

            ],

            "host-tracker-service:attachment-points": [

              {

                "tp-id": "openflow:1:1",

                "corresponding-tp": "host:00:00:00:00:00:01",

                "active": true

              }

            ]

          }

 

From: Anil Vishnoi [mailto:vishnoianil@...]
Sent: Thursday, June 04, 2015 3:53 PM
To: Vishal Thapar
Cc: Yang, Yi Y; ovsdb-dev@...
Subject: Re: [ovsdb-dev] How do I map OVSDB bridge node to openflow node for getting an OVSDB bridge's openflow node ID?

 

Hi Yi/Vishal,

 

Please refer to ./southbound/southbound-api/src/main/yang/ovsdb.yang file. Southbound plugin augment bridge operational data to topology tree

 

    augment "/topo:network-topology/topo:topology/topo:node" {

        description "Augmentation for bridge nodes managed by ovsdb";

        ext:augment-identifier "ovsdb-bridge-augmentation";

        uses ovsdb-bridge-attributes;

    }

 

Ovsdb-bridge-attributes contains operational data of the bridge and it has datapath-id as one of the element.

 

        leaf datapath-id {

            description "Datapath-id of the bridge";

            type datapath-id;

        }

 

You can use this datapath-id to determine the Openflow registration id "openflow:<datapath-id>". 

 

Thanks

Anil

 

On Thu, Jun 4, 2015 at 12:05 PM, Vishal Thapar <vishal.thapar@...> wrote:

+1

 

I’d also like to know answer to this.

 

From:ovsdb-dev-bounces@... [mailto:ovsdb-dev-bounces@...] On Behalf Of Yang, Yi Y
Sent: 04 June 2015 04:44
To: ovsdb-dev@...
Subject: [ovsdb-dev] How do I map OVSDB bridge node to openflow node for getting an OVSDB bridge's openflow node ID?

 

Hello, guys

 

I need to get openflow node ID for an OVSDB bridge node, in my test environment, I can see node info in MDSAL network topology flow:1 anf ovsdb:1 when I add a new bridge by command “sudo ovs-vsctl add-br br1”, I also can see node info in MDSAL inventory, but I can’t see augmentation for node in inventory, I noticed ovsdb/plugin-mdsal-adapter/src/main/yang/ovsdb-node-inventory.yang augmented inventory node:

 

    augment /inv:nodes/inv:node {

        ext:augment-identifier "ovsdb-managed-node";

        // when "/inv:nodes/inv:node/flowcapable:manufacturer = '*'";

        container ovsdb-bridge {

            uses ovsdb-bridge-attributes;

        }

    }

 

    augment /inv:nodes/inv:node {

        ext:augment-identifier "ovsdb-capable-node";

        uses ovsdb-node-attributes;

}

 

Anybody knows why? In karaf, what feature should I install for this. Here are ovsdb features I have installed.

 

opendaylight-user@root>feature:list -i | grep ovsdb

odl-ovsdb-southbound-api              | 1.1.0-SNAPSHOT      | x         | odl-ovsdb-southbound-1.1.0-SNAPSHOT     | OpenDaylight :: southbound :: api

odl-ovsdb-southbound-impl             | 1.1.0-SNAPSHOT      | x         | odl-ovsdb-southbound-1.1.0-SNAPSHOT     | OpenDaylight :: southbound :: impl

odl-ovsdb-southbound-impl-rest        | 1.1.0-SNAPSHOT      | x         | odl-ovsdb-southbound-1.1.0-SNAPSHOT     | OpenDaylight :: southbound :: impl :: REST

odl-ovsdb-southbound-impl-ui          | 1.1.0-SNAPSHOT      | x         | odl-ovsdb-southbound-1.1.0-SNAPSHOT     | OpenDaylight :: southbound :: impl :: UI

opendaylight-user@root>


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



 

--

Thanks

Anil




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


Re: How do I map OVSDB bridge node to openflow node for getting an OVSDB bridge's openflow node ID?

Anil Vishnoi
 

Hi Yi,

Sorry for the late response. OVSDB southbound plugin store ofport info in operatioanal data store. So you can use that ofport info to figure out port in openflow switch openflow:<datapath-id>:<ovsdb-ofport>.

Thanks
Anil

On Thu, Jun 4, 2015 at 6:59 PM, Yang, Yi Y <yi.y.yang@...> wrote:

Anil, thank you so much, I checked it again, I can get openflow node ID using datapath-id.

 

Another question is how I map an OVS port like “tap1” to openflow tp id like “openflow:1:2”?

 

In openflow network topology, l2switch can host nodes that connect to openflow switch, but in OVSDB network topology, I can’t get similar piece. It will be very great if ovsdb can add them. Now I can see full network topology by openflow network topology, but OVSDB can’t provide info of VMs connected to ovs bridge.

 

          {

            "node-id": "host:00:00:00:00:00:01",

            "termination-point": [

              {

                "tp-id": "host:00:00:00:00:00:01"

              }

            ],

            "host-tracker-service:id": "00:00:00:00:00:01",

            "host-tracker-service:addresses": [

              {

                "id": 7,

                "mac": "00:00:00:00:00:01",

                "ip": "10.0.0.1",

                "first-seen": 1431084716588,

                "last-seen": 1431084716588

              }

            ],

            "host-tracker-service:attachment-points": [

              {

                "tp-id": "openflow:1:1",

                "corresponding-tp": "host:00:00:00:00:00:01",

                "active": true

              }

            ]

          }

 

From: Anil Vishnoi [mailto:vishnoianil@...]
Sent: Thursday, June 04, 2015 3:53 PM
To: Vishal Thapar
Cc: Yang, Yi Y; ovsdb-dev@...
Subject: Re: [ovsdb-dev] How do I map OVSDB bridge node to openflow node for getting an OVSDB bridge's openflow node ID?

 

Hi Yi/Vishal,

 

Please refer to ./southbound/southbound-api/src/main/yang/ovsdb.yang file. Southbound plugin augment bridge operational data to topology tree

 

    augment "/topo:network-topology/topo:topology/topo:node" {

        description "Augmentation for bridge nodes managed by ovsdb";

        ext:augment-identifier "ovsdb-bridge-augmentation";

        uses ovsdb-bridge-attributes;

    }

 

Ovsdb-bridge-attributes contains operational data of the bridge and it has datapath-id as one of the element.

 

        leaf datapath-id {

            description "Datapath-id of the bridge";

            type datapath-id;

        }

 

You can use this datapath-id to determine the Openflow registration id "openflow:<datapath-id>". 

 

Thanks

Anil

 

On Thu, Jun 4, 2015 at 12:05 PM, Vishal Thapar <vishal.thapar@...> wrote:

+1

 

I’d also like to know answer to this.

 

From: ovsdb-dev-bounces@... [mailto:ovsdb-dev-bounces@...] On Behalf Of Yang, Yi Y
Sent: 04 June 2015 04:44
To: ovsdb-dev@...
Subject: [ovsdb-dev] How do I map OVSDB bridge node to openflow node for getting an OVSDB bridge's openflow node ID?

 

Hello, guys

 

I need to get openflow node ID for an OVSDB bridge node, in my test environment, I can see node info in MDSAL network topology flow:1 anf ovsdb:1 when I add a new bridge by command “sudo ovs-vsctl add-br br1”, I also can see node info in MDSAL inventory, but I can’t see augmentation for node in inventory, I noticed ovsdb/plugin-mdsal-adapter/src/main/yang/ovsdb-node-inventory.yang augmented inventory node:

 

    augment /inv:nodes/inv:node {

        ext:augment-identifier "ovsdb-managed-node";

        // when "/inv:nodes/inv:node/flowcapable:manufacturer = '*'";

        container ovsdb-bridge {

            uses ovsdb-bridge-attributes;

        }

    }

 

    augment /inv:nodes/inv:node {

        ext:augment-identifier "ovsdb-capable-node";

        uses ovsdb-node-attributes;

}

 

Anybody knows why? In karaf, what feature should I install for this. Here are ovsdb features I have installed.

 

opendaylight-user@root>feature:list -i | grep ovsdb

odl-ovsdb-southbound-api              | 1.1.0-SNAPSHOT      | x         | odl-ovsdb-southbound-1.1.0-SNAPSHOT     | OpenDaylight :: southbound :: api

odl-ovsdb-southbound-impl             | 1.1.0-SNAPSHOT      | x         | odl-ovsdb-southbound-1.1.0-SNAPSHOT     | OpenDaylight :: southbound :: impl

odl-ovsdb-southbound-impl-rest        | 1.1.0-SNAPSHOT      | x         | odl-ovsdb-southbound-1.1.0-SNAPSHOT     | OpenDaylight :: southbound :: impl :: REST

odl-ovsdb-southbound-impl-ui          | 1.1.0-SNAPSHOT      | x         | odl-ovsdb-southbound-1.1.0-SNAPSHOT     | OpenDaylight :: southbound :: impl :: UI

opendaylight-user@root>


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



 

--

Thanks

Anil




--
Thanks
Anil


I think I've fixed SecGrps and SecGrpRules

Edward Warnicke <hagbard@...>
 

So... I went and tried 

from OpenStack (many thanks Kyle Mestery :) ).

In digging into why that wasn't working I found a bug in Neutron NB and fixed it here:


In my basic checks it appears to work when I test it against dummy-provider in the
neutron project and:

1)  I see the SecGrp messages in the dummy provider in the logs, 
2)  I see successful responses to the SecGrp calls in the pcap I took

So I'm feeling good about it.

Could folks try it out in more complex scenarios?

Ed

3301 - 3320 of 4855