Thanks Eric, this worked perfect.

On Jun 22, 2015, at 12:05 PM, Multanen, Eric W <eric.w.multanen@...> wrote:

A command like this:

 

sudo ovs-vsctl remove open_vswitch . external-id "opendaylight-iid"

 

will remove the instance id setting from the open_vswitch table.

 

From: ovsdb-dev-bounces@... [mailto:ovsdb-dev-bounces@...] On Behalf Of Luis Gomez
Sent: Monday, June 22, 2015 12:00 PM
To: Edward Warnicke
Cc: ovsdb-dev
Subject: Re: [ovsdb-dev] OVSDB node-id

 

OK makes sense, I will just need to find a way to reset the id in my local OVS to reproduce the CI behavior.

 

BR/Luis

 

 

On Jun 22, 2015, at 11:54 AM, Edward Warnicke <hagbard@...> wrote:

 

Luis,

 

That could be it... if you create an OVSDB node with that instance id from ODL, disconnect ODL (or restart it) and reconnect.  It will believe the iid stored in OVSDB rather than constructing a new one.

 

Ed

 

On Mon, Jun 22, 2015 at 12:50 PM, Luis Gomez <ecelgp@...> wrote:

I am thinking because my OVS was previously accessed from ODL, maybe something is written in the OVS that changes the behavior when the OVS connects to controller. The VMs in CI are fresh new every test and that could explain the difference.

 

BR/Luis

 

 

On Jun 22, 2015, at 11:42 AM, Luis Gomez <ecelgp@...> wrote:

 

open_vswitch table dump in my local system:

 

mininet@mininet-vm:~\> sudo ovs-vsctl list open_vswitch

_uuid               : 8625e529-b120-425d-ae73-39757be6e38b

bridges             : [6713f071-3c2d-4eb5-9ad3-cc286882b1e1, 81cd2db3-6cec-47c2-85ae-0277aaa3f191, d73933ff-8761-46c2-b1a4-4294431cb9f6, f188038b-155b-4976-bb60-f36bb13b8f17]

cur_cfg             : 205828

db_version          : "7.3.0"

external_ids        : {opendaylight-iid="/network-topology:network-topology/network-topology:topology[network-topology:topology-id='ovsdb:1']/network-topology:node[network-topology:node-id='ovsdb://127.0.0.1:6644']", system-id="2a99951a-5a22-4b09-9bc9-68cfd2a36cd5"}

manager_options     : [4a640c37-39b6-4644-b0a5-08260c8a91ff]

next_cfg            : 205828

other_config        : {}

ovs_version         : "2.0.2"

ssl                 : []

statistics          : {}

system_type         : Ubuntu

system_version      : "14.04-trusty"

 

 

 

On Jun 22, 2015, at 11:18 AM, Anil Vishnoi <vishnoianil@...> wrote:

 

Luis,

 

On your local machine, can you try 'ovsdb-client dump' command. It will dump all the tables of ovsdb database and in those table look for Open_Vswitch table and see if there is a string "ovsdb://127.0.0.1:6644” in any column.

 

Thanks

Anil

 

On Mon, Jun 22, 2015 at 11:39 PM, Luis Gomez <ecelgp@...> wrote:

Yes

 

On Jun 22, 2015, at 10:37 AM, Anil Vishnoi <vishnoianil@...> wrote:

 

Luis in both the case connection is initiated from OVS?

 

On Mon, Jun 22, 2015 at 10:54 PM, Luis Gomez <ecelgp@...> wrote:

Hi Anil,

 

I have tested RC2 and also latest integration distribution from Nexus in my setup and I still see OVSDB id in the form of "node-id": "ovsdb://127.0.0.1:6644”. However in ODL CI I see the other format, I am not sure what is going on…

 

BR/Luis

 

On Jun 21, 2015, at 11:08 PM, Anil Vishnoi <vishnoianil@...> wrote:

 

Patches in question were merged on 2nd june (one of them was https://git.opendaylight.org/gerrit/#/c/21448/). So if you are running integration build, you need to pull the latest code integration repo and build it. 

 

On Mon, Jun 22, 2015 at 11:32 AM, Chaudhry usama <chaudhryusama@...> wrote:

I was using the 18th June Lithium Artifact on my local VM. Not sure about the one used in ODL rackspace VM. You modified the code recently ?

 

On Mon, Jun 22, 2015 at 10:41 AM, Anil Vishnoi <vishnoianil@...> wrote:

The second version i the correct one, we recently modified the code to use bridge uuid as it's node id and not the <ip>:<port>. Are you running same ovsdb code on both the machines?

 

On Mon, Jun 22, 2015 at 11:03 AM, Luis Gomez <ecelgp@...> wrote:

Hi ovsdb devs,

 

We have question regarding ovsdb node-id:

 

- When we initiate an ovsdb connection from the OVS to ODL using local VM we get an ovsdb node-id like: "node-id": "ovsdb://127.0.0.1:6644” (ovsdb IP and tcp port)

 

However:

 

- When we do the same using ODL rackspace VM we get a node-id like: "node-id": "ovsdb://uuid/bb719b63-34ea-4586-a328-bd2f7bd6e5f7” 

 

Can anyone explain this difference in node-id representation?

 

BR/Luis

 

 

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

 

-- 

Thanks

Anil

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

 

 

-- 

Thanks

Anil

 

 

-- 

Thanks

Anil

 

 

-- 

Thanks

Anil

 

 

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

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

I am thinking because my OVS was previously accessed from ODL, maybe something is written in the OVS that changes the behavior when the OVS connects to controller. The VMs in CI are fresh new every test and that could explain the difference.

BR/Luis

On Jun 22, 2015, at 11:42 AM, Luis Gomez <ecelgp@...> wrote:

open_vswitch table dump in my local system:

mininet@mininet-vm:~\> sudo ovs-vsctl list open_vswitch

_uuid               : 8625e529-b120-425d-ae73-39757be6e38b

bridges             : [6713f071-3c2d-4eb5-9ad3-cc286882b1e1, 81cd2db3-6cec-47c2-85ae-0277aaa3f191, d73933ff-8761-46c2-b1a4-4294431cb9f6, f188038b-155b-4976-bb60-f36bb13b8f17]

cur_cfg             : 205828

db_version          : "7.3.0"

external_ids        : {opendaylight-iid="/network-topology:network-topology/network-topology:topology[network-topology:topology-id='ovsdb:1']/network-topology:node[network-topology:node-id='ovsdb://127.0.0.1:6644']", system-id="2a99951a-5a22-4b09-9bc9-68cfd2a36cd5"}

manager_options     : [4a640c37-39b6-4644-b0a5-08260c8a91ff]

next_cfg            : 205828

other_config        : {}

ovs_version         : "2.0.2"

ssl                 : []

statistics          : {}

system_type         : Ubuntu

system_version      : "14.04-trusty"

On Jun 22, 2015, at 11:18 AM, Anil Vishnoi <vishnoianil@...> wrote:

Luis,

On your local machine, can you try 'ovsdb-client dump' command. It will dump all the tables of ovsdb database and in those table look for Open_Vswitch table and see if there is a string "ovsdb://127.0.0.1:6644” in any column.

Thanks

Anil

On Mon, Jun 22, 2015 at 11:39 PM, Luis Gomez <ecelgp@...> wrote:

Yes

On Jun 22, 2015, at 10:37 AM, Anil Vishnoi <vishnoianil@...> wrote:

Luis in both the case connection is initiated from OVS?

On Mon, Jun 22, 2015 at 10:54 PM, Luis Gomez <ecelgp@...> wrote:

Hi Anil,

I have tested RC2 and also latest integration distribution from Nexus in my setup and I still see OVSDB id in the form of "node-id": "ovsdb://127.0.0.1:6644”. However in ODL CI I see the other format, I am not sure what is going on…

BR/Luis

On Jun 21, 2015, at 11:08 PM, Anil Vishnoi <vishnoianil@...> wrote:

Patches in question were merged on 2nd june (one of them was https://git.opendaylight.org/gerrit/#/c/21448/). So if you are running integration build, you need to pull the latest code integration repo and build it. 

On Mon, Jun 22, 2015 at 11:32 AM, Chaudhry usama <chaudhryusama@...> wrote:

I was using the 18th June Lithium Artifact on my local VM. Not sure about the one used in ODL rackspace VM. You modified the code recently ?

On Mon, Jun 22, 2015 at 10:41 AM, Anil Vishnoi <vishnoianil@...> wrote:

The second version i the correct one, we recently modified the code to use bridge uuid as it's node id and not the <ip>:<port>. Are you running same ovsdb code on both the machines?

On Mon, Jun 22, 2015 at 11:03 AM, Luis Gomez <ecelgp@...> wrote:

Hi ovsdb devs,

We have question regarding ovsdb node-id:

- When we initiate an ovsdb connection from the OVS to ODL using local VM we get an ovsdb node-id like: "node-id": "ovsdb://127.0.0.1:6644” (ovsdb IP and tcp port)

However:

- When we do the same using ODL rackspace VM we get a node-id like: "node-id": "ovsdb://uuid/bb719b63-34ea-4586-a328-bd2f7bd6e5f7” 

Can anyone explain this difference in node-id representation?

BR/Luis

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

--

Thanks

Anil

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

--

Thanks

Anil

--

Thanks

Anil

--

Thanks

Anil

I am thinking because my OVS was previously accessed from ODL, maybe something is written in the OVS that changes the behavior when the OVS connects to controller. The VMs in CI are fresh new every test and that could explain the difference.

BR/Luis

On Jun 22, 2015, at 11:42 AM, Luis Gomez <ecelgp@...> wrote:

open_vswitch table dump in my local system:

mininet@mininet-vm:~\> sudo ovs-vsctl list open_vswitch

_uuid               : 8625e529-b120-425d-ae73-39757be6e38b

bridges             : [6713f071-3c2d-4eb5-9ad3-cc286882b1e1, 81cd2db3-6cec-47c2-85ae-0277aaa3f191, d73933ff-8761-46c2-b1a4-4294431cb9f6, f188038b-155b-4976-bb60-f36bb13b8f17]

cur_cfg             : 205828

db_version          : "7.3.0"

external_ids        : {opendaylight-iid="/network-topology:network-topology/network-topology:topology[network-topology:topology-id='ovsdb:1']/network-topology:node[network-topology:node-id='ovsdb://127.0.0.1:6644']", system-id="2a99951a-5a22-4b09-9bc9-68cfd2a36cd5"}

manager_options     : [4a640c37-39b6-4644-b0a5-08260c8a91ff]

next_cfg            : 205828

other_config        : {}

ovs_version         : "2.0.2"

ssl                 : []

statistics          : {}

system_type         : Ubuntu

system_version      : "14.04-trusty"

On Jun 22, 2015, at 11:18 AM, Anil Vishnoi <vishnoianil@...> wrote:

Luis,

On your local machine, can you try 'ovsdb-client dump' command. It will dump all the tables of ovsdb database and in those table look for Open_Vswitch table and see if there is a string "ovsdb://127.0.0.1:6644” in any column.

Thanks

Anil

On Mon, Jun 22, 2015 at 11:39 PM, Luis Gomez <ecelgp@...> wrote:

Yes

On Jun 22, 2015, at 10:37 AM, Anil Vishnoi <vishnoianil@...> wrote:

Luis in both the case connection is initiated from OVS?

On Mon, Jun 22, 2015 at 10:54 PM, Luis Gomez <ecelgp@...> wrote:

Hi Anil,

I have tested RC2 and also latest integration distribution from Nexus in my setup and I still see OVSDB id in the form of "node-id": "ovsdb://127.0.0.1:6644”. However in ODL CI I see the other format, I am not sure what is going on…

BR/Luis

On Jun 21, 2015, at 11:08 PM, Anil Vishnoi <vishnoianil@...> wrote:

Patches in question were merged on 2nd june (one of them was https://git.opendaylight.org/gerrit/#/c/21448/). So if you are running integration build, you need to pull the latest code integration repo and build it. 

On Mon, Jun 22, 2015 at 11:32 AM, Chaudhry usama <chaudhryusama@...> wrote:

I was using the 18th June Lithium Artifact on my local VM. Not sure about the one used in ODL rackspace VM. You modified the code recently ?

On Mon, Jun 22, 2015 at 10:41 AM, Anil Vishnoi <vishnoianil@...> wrote:

The second version i the correct one, we recently modified the code to use bridge uuid as it's node id and not the <ip>:<port>. Are you running same ovsdb code on both the machines?

On Mon, Jun 22, 2015 at 11:03 AM, Luis Gomez <ecelgp@...> wrote:

Hi ovsdb devs,

We have question regarding ovsdb node-id:

- When we initiate an ovsdb connection from the OVS to ODL using local VM we get an ovsdb node-id like: "node-id": "ovsdb://127.0.0.1:6644” (ovsdb IP and tcp port)

However:

- When we do the same using ODL rackspace VM we get a node-id like: "node-id": "ovsdb://uuid/bb719b63-34ea-4586-a328-bd2f7bd6e5f7” 

Can anyone explain this difference in node-id representation?

BR/Luis

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

--

Thanks

Anil

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

--

Thanks

Anil

--

Thanks

Anil

--

Thanks

Anil

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

Luis,

On your local machine, can you try 'ovsdb-client dump' command. It will dump all the tables of ovsdb database and in those table look for Open_Vswitch table and see if there is a string "ovsdb://127.0.0.1:6644” in any column.

Thanks

Anil

On Mon, Jun 22, 2015 at 11:39 PM, Luis Gomez <ecelgp@...> wrote:

Yes

On Jun 22, 2015, at 10:37 AM, Anil Vishnoi <vishnoianil@...> wrote:

Luis in both the case connection is initiated from OVS?

On Mon, Jun 22, 2015 at 10:54 PM, Luis Gomez <ecelgp@...> wrote:

Hi Anil,

I have tested RC2 and also latest integration distribution from Nexus in my setup and I still see OVSDB id in the form of "node-id": "ovsdb://127.0.0.1:6644”. However in ODL CI I see the other format, I am not sure what is going on…

BR/Luis

On Jun 21, 2015, at 11:08 PM, Anil Vishnoi <vishnoianil@...> wrote:

Patches in question were merged on 2nd june (one of them was https://git.opendaylight.org/gerrit/#/c/21448/). So if you are running integration build, you need to pull the latest code integration repo and build it. 

On Mon, Jun 22, 2015 at 11:32 AM, Chaudhry usama <chaudhryusama@...> wrote:

I was using the 18th June Lithium Artifact on my local VM. Not sure about the one used in ODL rackspace VM. You modified the code recently ?

On Mon, Jun 22, 2015 at 10:41 AM, Anil Vishnoi <vishnoianil@...> wrote:

The second version i the correct one, we recently modified the code to use bridge uuid as it's node id and not the <ip>:<port>. Are you running same ovsdb code on both the machines?

On Mon, Jun 22, 2015 at 11:03 AM, Luis Gomez <ecelgp@...> wrote:

Hi ovsdb devs,

We have question regarding ovsdb node-id:

- When we initiate an ovsdb connection from the OVS to ODL using local VM we get an ovsdb node-id like: "node-id": "ovsdb://127.0.0.1:6644” (ovsdb IP and tcp port)

However:

- When we do the same using ODL rackspace VM we get a node-id like: "node-id": "ovsdb://uuid/bb719b63-34ea-4586-a328-bd2f7bd6e5f7” 

Can anyone explain this difference in node-id representation?

BR/Luis

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

--

Thanks

Anil

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

--

Thanks

Anil

--

Thanks

Anil

--

Thanks

Anil

Yes

On Jun 22, 2015, at 10:37 AM, Anil Vishnoi <vishnoianil@...> wrote:

Luis in both the case connection is initiated from OVS?

On Mon, Jun 22, 2015 at 10:54 PM, Luis Gomez <ecelgp@...> wrote:

Hi Anil,

I have tested RC2 and also latest integration distribution from Nexus in my setup and I still see OVSDB id in the form of "node-id": "ovsdb://127.0.0.1:6644”. However in ODL CI I see the other format, I am not sure what is going on…

BR/Luis

On Jun 21, 2015, at 11:08 PM, Anil Vishnoi <vishnoianil@...> wrote:

Patches in question were merged on 2nd june (one of them was https://git.opendaylight.org/gerrit/#/c/21448/). So if you are running integration build, you need to pull the latest code integration repo and build it. 

On Mon, Jun 22, 2015 at 11:32 AM, Chaudhry usama <chaudhryusama@...> wrote:

I was using the 18th June Lithium Artifact on my local VM. Not sure about the one used in ODL rackspace VM. You modified the code recently ?

On Mon, Jun 22, 2015 at 10:41 AM, Anil Vishnoi <vishnoianil@...> wrote:

The second version i the correct one, we recently modified the code to use bridge uuid as it's node id and not the <ip>:<port>. Are you running same ovsdb code on both the machines?

On Mon, Jun 22, 2015 at 11:03 AM, Luis Gomez <ecelgp@...> wrote:

Hi ovsdb devs,

We have question regarding ovsdb node-id:

- When we initiate an ovsdb connection from the OVS to ODL using local VM we get an ovsdb node-id like: "node-id": "ovsdb://127.0.0.1:6644” (ovsdb IP and tcp port)

However:

- When we do the same using ODL rackspace VM we get a node-id like: "node-id": "ovsdb://uuid/bb719b63-34ea-4586-a328-bd2f7bd6e5f7” 

Can anyone explain this difference in node-id representation?

BR/Luis

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

--

Thanks

Anil

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

--

Thanks

Anil

--

Thanks

Anil

Hi Anil,

I have tested RC2 and also latest integration distribution from Nexus in my setup and I still see OVSDB id in the form of "node-id": "ovsdb://127.0.0.1:6644”. However in ODL CI I see the other format, I am not sure what is going on…

BR/Luis

On Jun 21, 2015, at 11:08 PM, Anil Vishnoi <vishnoianil@...> wrote:

Patches in question were merged on 2nd june (one of them was https://git.opendaylight.org/gerrit/#/c/21448/). So if you are running integration build, you need to pull the latest code integration repo and build it. 

On Mon, Jun 22, 2015 at 11:32 AM, Chaudhry usama <chaudhryusama@...> wrote:

I was using the 18th June Lithium Artifact on my local VM. Not sure about the one used in ODL rackspace VM. You modified the code recently ?

On Mon, Jun 22, 2015 at 10:41 AM, Anil Vishnoi <vishnoianil@...> wrote:

The second version i the correct one, we recently modified the code to use bridge uuid as it's node id and not the <ip>:<port>. Are you running same ovsdb code on both the machines?

On Mon, Jun 22, 2015 at 11:03 AM, Luis Gomez <ecelgp@...> wrote:

Hi ovsdb devs,

We have question regarding ovsdb node-id:

- When we initiate an ovsdb connection from the OVS to ODL using local VM we get an ovsdb node-id like: "node-id": "ovsdb://127.0.0.1:6644” (ovsdb IP and tcp port)

However:

- When we do the same using ODL rackspace VM we get a node-id like: "node-id": "ovsdb://uuid/bb719b63-34ea-4586-a328-bd2f7bd6e5f7” 

Can anyone explain this difference in node-id representation?

BR/Luis

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

--

Thanks

Anil

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

--

Thanks

Anil

Could we get this added to the central ODL Google Calendar as well?

Ed

On Mon, Jun 22, 2015 at 9:34 AM, Abhijit Kumbhare <abhijitkoss@...> wrote:

more details » OVSDB VTEP meeting Will update the Webex when Phil is able to provide it. When Weekly from 7am to 8am on Tuesday Pacific Time Where Webex to be provided by Phil (map) Calendar abhijitkoss@... Who • Abhijit Kumbhare - organizer • Philip Robb • shague@... • ovsdb-dev@... Going?   All events in this series:   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. Forwarding this invitation could allow any recipient to modify your RSVP response. Learn more at https://support.google.com/calendar/answer/37135#forwarding

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

more details » OVSDB VTEP meeting Will update the Webex when Phil is able to provide it. When Weekly from 7am to 8am on Tuesday Pacific Time Where Webex to be provided by Phil (map) Calendar abhijitkoss@... Who • Abhijit Kumbhare - organizer • Philip Robb • shague@... • ovsdb-dev@... Going?   All events in this series:   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. Forwarding this invitation could allow any recipient to modify your RSVP response. Learn more at https://support.google.com/calendar/answer/37135#forwarding

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

Either time is good with me. Sam

Sent from my Verizon Wireless 4G LTE smartphone

-------- Original message --------

From: Abhijit Kumbhare

Date:06/16/2015 12:53 PM (GMT-05:00)

To: Dayavanti Gopal Kamath

Cc: "Garg, Sumit" ,Yapeng Wu ,Sam Hague ,ovsdb-dev ,Chris Wright ,"Swaminathan Vasudevan (PNB Roseville) (swaminathan.vasudevan@...)" ,Ravindra' 'Kenchappa ,"Maruti Haridas Kamat (maruti.kamat@...)" ,afredette@...,Abhijit Kumbhare ,Ravi Sundareswaran ,Hema Gopalkrishnan ,Ravi Sabapathy ,Aswin' 'Suryanarayanan

Subject: Re: [ovsdb-dev] ODL OVSDB hardware vtep support initial kick-off

I am fine with Tuesday 7 am Pacific.

On Tue, Jun 16, 2015 at 1:58 AM, Dayavanti Gopal Kamath <dayavanti.gopal.kamath@...> wrote:

All,
We may need to take up a Tuesday 7 am pacific slot for the hardware vtep meeting. The Monday 8 am pacific slot is currently booked, and we need to check if it can be freed up for this meeting.
Wanted to do a quick survey of key contributors if they have any strong preferences, that cannot be accommodated by reschedules of other meetings. If it turns out that Monday is much more convenient, we will need to discuss with phil robb and others again. Please respond.

Thanks!
daya

-----Original Message-----
From: Garg, Sumit [mailto:sumit@...]

Sent: Tuesday, June 09, 2015 8:51 PM
To: Yapeng Wu; Sam Hague; Dayavanti Gopal Kamath; ovsdb-dev
Cc: Chris Wright; Swaminathan Vasudevan (PNB Roseville) (swaminathan.vasudevan@...); Maruti Haridas Kamat (maruti.kamat@...); afredette@...; Ravi Sundareswaran; Abhijit Kumbhare; Ravi Sabapathy; Aswin' 'Suryanarayanan; Hema Gopalkrishnan; Ravindra' 'Kenchappa
Subject: Re: ODL OVSDB hardware vtep support initial kick-off

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@...
>> o
>> 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@...
>> o
>> 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@e
>> r
>> 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@ericsson.
>> c
>> 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@...
>> m
>> ><mailto:afredette@...>,
>> Ravi_Sabapathy@...<mailto:Ravi_Sabapathy@...><Ravi_Sabapath

>> y @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.

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

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

I was using the 18th June Lithium Artifact on my local VM. Not sure about the one used in ODL rackspace VM. You modified the code recently ?

On Mon, Jun 22, 2015 at 10:41 AM, Anil Vishnoi <vishnoianil@...> wrote:

The second version i the correct one, we recently modified the code to use bridge uuid as it's node id and not the <ip>:<port>. Are you running same ovsdb code on both the machines?

On Mon, Jun 22, 2015 at 11:03 AM, Luis Gomez <ecelgp@...> wrote:

Hi ovsdb devs,

We have question regarding ovsdb node-id:

- When we initiate an ovsdb connection from the OVS to ODL using local VM we get an ovsdb node-id like: "node-id": "ovsdb://127.0.0.1:6644” (ovsdb IP and tcp port)

However:

- When we do the same using ODL rackspace VM we get a node-id like: "node-id": "ovsdb://uuid/bb719b63-34ea-4586-a328-bd2f7bd6e5f7” 

Can anyone explain this difference in node-id representation?

BR/Luis

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

--

Thanks

Anil

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