1. Z.Archive.Ovsdb-Dev
  2. Messages

Expanded

Topics Messages Polls
   Date   
Re: I think I've fixed SecGrps and SecGrpRules

Edward Warnicke <hagbard@...>
 

Vishal,

Good job narrowing it down :)

You've cleared the ML2 driver (messages are getting to ODL)

If you would try it with the neutron northbound dummy-provider which gives good logging of messages received and correctly unmarshalled, we can clear the neutron northbound
and narrow it down to just the provider.

To test with the neutron northbound,

cd neutron
cd karaf/
mvn clean install
cd target/assembly/bin
./karaf

This will bring up the dummy-provider, which just logs messages received.  If you see your messages in the logs there, we know the
neutron northbound has correct behavior :)

Ed


On Wed, Jun 17, 2015 at 6:25 AM, Vishal Thapar <vishal.thapar@...> wrote:

Looks like rest calls are going from ODL Mech driver to ODL for security group as well as VM Port [IP .

 

Neutron log: 3389 and 3402

pcap: Frame 406 and 555.

 

Found this entry in karaf.log:

Line 569: 2015-06-18 01:51:59,928 | INFO  | ntDispatcherImpl | OF13Provider                     | 272 - org.opendaylight.ovsdb.openstack.net-virt-providers - 1.1.0.SNAPSHOT | programLocalRules: could not find ofPort for Port tap1220d276-15 on Node Uri [_value=ovsdb://uuid/b45dcd8f-5e20-42a0-abc0-f1373dc18f6c/bridge/br-int]

 

Relevant entries are line 567 to 570. This is where someone more familiar with OVSDB would be able to help.

 

Regards,

Vishal.

 

 

From: ovsdb-dev-bounces@... [mailto:ovsdb-dev-bounces@...] On Behalf Of Suryanarayanan, Aswin
Sent: 17 June 2015 16:51
To: Anil Vishnoi; Edward Warnicke
Cc: ovsdb-dev@...; groupbasedpolicy-dev@...; Kenchappa, Ravindra; neutron-dev@...


Subject: Re: [ovsdb-dev] I think I've fixed SecGrps and SecGrpRules

 

Thanks Anil for the suggestions.

 

Hi Ed,

 

The logs and pcap are attached in the below link. There are some logs security groups in neutron server log. But I was not able to confirm whether the request reached ODL correctly. I am trying to understand the same.  But no flows related to security groups where  inserted. Let me know if any further logs are required.

 

The log is for the use case  Create Network -> Create Subnet -> Spawn VM.

 

https://drive.google.com/folderview?id=0BzO1nVcl7PumfmczY1lsWjJXSGc0SHVkYlNaYTh6TjdkZk1HazRqdzdCWUpjcFI4UzVIUW8&usp=sharing

 

Thanks and Regards

Aswin

 

From: Anil Vishnoi [mailto:vishnoianil@...]
Sent: Wednesday, June 17, 2015 3:06 AM
To: Edward Warnicke
Cc: Suryanarayanan, Aswin; ovsdb-dev@...; groupbasedpolicy-dev@...; neutron-dev@...; Kenchappa, Ravindra
Subject: Re: [ovsdb-dev] I think I've fixed SecGrps and SecGrpRules

 

I would say just enable the debug log in odl mechanism driver and you will get all the rest call details that it's sending to odl controller. 

 

On Wed, Jun 17, 2015 at 1:00 AM, Edward Warnicke <hagbard@...> wrote:

Aswin,

 

If you could stick the pcap files somwhere like google drive or dropbox and share them that would also be mega useful :)

 

Ed

 

On Tue, Jun 16, 2015 at 12:29 PM, Suryanarayanan, Aswin <aswin.suryanarayanan@...> wrote:

Hi Ed,

 

We checked with break points in  NeutronSecurityRulesNorthbound and NeutronSecurityGroupsNorthbound in neutron ODL. We will analyze with wireshark and get back.

 

Aswin

 

From: Edward Warnicke [mailto:hagbard@...]
Sent: Tuesday, June 16, 2015 11:40 PM
To: Suryanarayanan, Aswin
Cc: ovsdb-dev@...; Kenchappa, Ravindra; neutron-dev@...; groupbasedpolicy-dev@...
Subject: Re: [ovsdb-dev] I think I've fixed SecGrps and SecGrpRules

 

Looping in other interested parties.

 

Ravi,

 

Lets start debugging at the top :)

 

1)  When you create a VM, what call are you expecting to see to ODL, and how are you verifying you don't see it (wireshark, etc)

 

The reason I ask, is because the issue could be in any of the following components:

 

1) Neutron

2) ML2

3) ODL ML2 Driver (in Stackforge)

4) ODL Neutron Northbound (in ODL)

5) The provider

 

Usually, the simplest way to start debugging for me is to answer the question:

 

On the wire, do I see the REST calls I expected.

 

Once we know the answer to that, we can drill further down :)

 

Ed

 

 

 

On Tue, Jun 16, 2015 at 11:44 AM, Suryanarayanan, Aswin <aswin.suryanarayanan@...> wrote:

Hi Ed,

 

Me and Ravi  tired with the devstack kilo with latest code from networking-odl(few changes in neutron as well) along with latest ODL. We observed that when we created a network from horizon we received a call to NeutronSecurityRulesNorthbound  createSecurityRules with empty list. But when we created a vm call didn’t seem to reach Neutron northbound in ODL and no flows where inserted Table 40 or Table 90.  Shouldn’t we have the default rules to be added?  Could you please clarify?  Also when we tried to create SG from horizon UI, none of the call hit the Neutron Security Groups in ODL. Do that require any further changes in networking-odl/neutron?

 

Aswin


_______________________________________________
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



 

--

Thanks

Anil


Re: I think I've fixed SecGrps and SecGrpRules

Vishal Thapar <vishal.thapar@...>
 

Looks like rest calls are going from ODL Mech driver to ODL for security group as well as VM Port [IP .

 

Neutron log: 3389 and 3402

pcap: Frame 406 and 555.

 

Found this entry in karaf.log:

Line 569: 2015-06-18 01:51:59,928 | INFO  | ntDispatcherImpl | OF13Provider                     | 272 - org.opendaylight.ovsdb.openstack.net-virt-providers - 1.1.0.SNAPSHOT | programLocalRules: could not find ofPort for Port tap1220d276-15 on Node Uri [_value=ovsdb://uuid/b45dcd8f-5e20-42a0-abc0-f1373dc18f6c/bridge/br-int]

 

Relevant entries are line 567 to 570. This is where someone more familiar with OVSDB would be able to help.

 

Regards,

Vishal.

 

 

From: ovsdb-dev-bounces@... [mailto:ovsdb-dev-bounces@...] On Behalf Of Suryanarayanan, Aswin
Sent: 17 June 2015 16:51
To: Anil Vishnoi; Edward Warnicke
Cc: ovsdb-dev@...; groupbasedpolicy-dev@...; Kenchappa, Ravindra; neutron-dev@...
Subject: Re: [ovsdb-dev] I think I've fixed SecGrps and SecGrpRules

 

Thanks Anil for the suggestions.

 

Hi Ed,

 

The logs and pcap are attached in the below link. There are some logs security groups in neutron server log. But I was not able to confirm whether the request reached ODL correctly. I am trying to understand the same.  But no flows related to security groups where  inserted. Let me know if any further logs are required.

 

The log is for the use case  Create Network -> Create Subnet -> Spawn VM.

 

https://drive.google.com/folderview?id=0BzO1nVcl7PumfmczY1lsWjJXSGc0SHVkYlNaYTh6TjdkZk1HazRqdzdCWUpjcFI4UzVIUW8&usp=sharing

 

Thanks and Regards

Aswin

 

From: Anil Vishnoi [mailto:vishnoianil@...]
Sent: Wednesday, June 17, 2015 3:06 AM
To: Edward Warnicke
Cc: Suryanarayanan, Aswin; ovsdb-dev@...; groupbasedpolicy-dev@...; neutron-dev@...; Kenchappa, Ravindra
Subject: Re: [ovsdb-dev] I think I've fixed SecGrps and SecGrpRules

 

I would say just enable the debug log in odl mechanism driver and you will get all the rest call details that it's sending to odl controller. 

 

On Wed, Jun 17, 2015 at 1:00 AM, Edward Warnicke <hagbard@...> wrote:

Aswin,

 

If you could stick the pcap files somwhere like google drive or dropbox and share them that would also be mega useful :)

 

Ed

 

On Tue, Jun 16, 2015 at 12:29 PM, Suryanarayanan, Aswin <aswin.suryanarayanan@...> wrote:

Hi Ed,

 

We checked with break points in  NeutronSecurityRulesNorthbound and NeutronSecurityGroupsNorthbound in neutron ODL. We will analyze with wireshark and get back.

 

Aswin

 

From: Edward Warnicke [mailto:hagbard@...]
Sent: Tuesday, June 16, 2015 11:40 PM
To: Suryanarayanan, Aswin
Cc: ovsdb-dev@...; Kenchappa, Ravindra; neutron-dev@...; groupbasedpolicy-dev@...
Subject: Re: [ovsdb-dev] I think I've fixed SecGrps and SecGrpRules

 

Looping in other interested parties.

 

Ravi,

 

Lets start debugging at the top :)

 

1)  When you create a VM, what call are you expecting to see to ODL, and how are you verifying you don't see it (wireshark, etc)

 

The reason I ask, is because the issue could be in any of the following components:

 

1) Neutron

2) ML2

3) ODL ML2 Driver (in Stackforge)

4) ODL Neutron Northbound (in ODL)

5) The provider

 

Usually, the simplest way to start debugging for me is to answer the question:

 

On the wire, do I see the REST calls I expected.

 

Once we know the answer to that, we can drill further down :)

 

Ed

 

 

 

On Tue, Jun 16, 2015 at 11:44 AM, Suryanarayanan, Aswin <aswin.suryanarayanan@...> wrote:

Hi Ed,

 

Me and Ravi  tired with the devstack kilo with latest code from networking-odl(few changes in neutron as well) along with latest ODL. We observed that when we created a network from horizon we received a call to NeutronSecurityRulesNorthbound  createSecurityRules with empty list. But when we created a vm call didn’t seem to reach Neutron northbound in ODL and no flows where inserted Table 40 or Table 90.  Shouldn’t we have the default rules to be added?  Could you please clarify?  Also when we tried to create SG from horizon UI, none of the call hit the Neutron Security Groups in ODL. Do that require any further changes in networking-odl/neutron?

 

Aswin


_______________________________________________
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



 

--

Thanks

Anil

Re: I think I've fixed SecGrps and SecGrpRules

Suryanarayanan, Aswin <aswin.suryanarayanan@...>
 

Thanks Anil for the suggestions.

 

Hi Ed,

 

The logs and pcap are attached in the below link. There are some logs security groups in neutron server log. But I was not able to confirm whether the request reached ODL correctly. I am trying to understand the same.  But no flows related to security groups where  inserted. Let me know if any further logs are required.

 

The log is for the use case  Create Network -> Create Subnet -> Spawn VM.

 

https://drive.google.com/folderview?id=0BzO1nVcl7PumfmczY1lsWjJXSGc0SHVkYlNaYTh6TjdkZk1HazRqdzdCWUpjcFI4UzVIUW8&usp=sharing

 

Thanks and Regards

Aswin

 

From: Anil Vishnoi [mailto:vishnoianil@...]
Sent: Wednesday, June 17, 2015 3:06 AM
To: Edward Warnicke
Cc: Suryanarayanan, Aswin; ovsdb-dev@...; groupbasedpolicy-dev@...; neutron-dev@...; Kenchappa, Ravindra
Subject: Re: [ovsdb-dev] I think I've fixed SecGrps and SecGrpRules

 

I would say just enable the debug log in odl mechanism driver and you will get all the rest call details that it's sending to odl controller. 

 

On Wed, Jun 17, 2015 at 1:00 AM, Edward Warnicke <hagbard@...> wrote:

Aswin,

 

If you could stick the pcap files somwhere like google drive or dropbox and share them that would also be mega useful :)

 

Ed

 

On Tue, Jun 16, 2015 at 12:29 PM, Suryanarayanan, Aswin <aswin.suryanarayanan@...> wrote:

Hi Ed,

 

We checked with break points in  NeutronSecurityRulesNorthbound and NeutronSecurityGroupsNorthbound in neutron ODL. We will analyze with wireshark and get back.

 

Aswin

 

From: Edward Warnicke [mailto:hagbard@...]
Sent: Tuesday, June 16, 2015 11:40 PM
To: Suryanarayanan, Aswin
Cc: ovsdb-dev@...; Kenchappa, Ravindra; neutron-dev@...; groupbasedpolicy-dev@...
Subject: Re: [ovsdb-dev] I think I've fixed SecGrps and SecGrpRules

 

Looping in other interested parties.

 

Ravi,

 

Lets start debugging at the top :)

 

1)  When you create a VM, what call are you expecting to see to ODL, and how are you verifying you don't see it (wireshark, etc)

 

The reason I ask, is because the issue could be in any of the following components:

 

1) Neutron

2) ML2

3) ODL ML2 Driver (in Stackforge)

4) ODL Neutron Northbound (in ODL)

5) The provider

 

Usually, the simplest way to start debugging for me is to answer the question:

 

On the wire, do I see the REST calls I expected.

 

Once we know the answer to that, we can drill further down :)

 

Ed

 

 

 

On Tue, Jun 16, 2015 at 11:44 AM, Suryanarayanan, Aswin <aswin.suryanarayanan@...> wrote:

Hi Ed,

 

Me and Ravi  tired with the devstack kilo with latest code from networking-odl(few changes in neutron as well) along with latest ODL. We observed that when we created a network from horizon we received a call to NeutronSecurityRulesNorthbound  createSecurityRules with empty list. But when we created a vm call didn’t seem to reach Neutron northbound in ODL and no flows where inserted Table 40 or Table 90.  Shouldn’t we have the default rules to be added?  Could you please clarify?  Also when we tried to create SG from horizon UI, none of the call hit the Neutron Security Groups in ODL. Do that require any further changes in networking-odl/neutron?

 

Aswin


_______________________________________________
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



 

--

Thanks

Anil

Re: Work on CI systems and or bug fixing

Kyle Mestery <mestery@...>
 

Armando and I have this underhand now from the OpenStack side. We should have these jobs back and voting ok with running Tempest tests by Friday I anticipate.

On the ODL side, there are real issues there. Flavio has the latest, but we could use help there for sure.

On Tue, Jun 16, 2015 at 4:37 PM, Anil Vishnoi <vishnoianil@...> wrote:
Adding Luis 

On Tue, Jun 16, 2015 at 11:48 PM, Kenchappa, Ravindra <ravindra.kenchappa@...> wrote:

Hi Guys,

Me  and Aswin  are from HP have spent some time to understand the ODL-OVSDB architecture. We wanted to work on security groups and hardware l2 gateway but then we heard that  some help is needed in stabilizing the CI systems.  We  can take up some work on CI system or defect fix . Please let us know whom do we work with to get started.

Thanks,

Ravi

 


_______________________________________________
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


Re: Work on CI systems and or bug fixing

Anil Vishnoi
 

Adding Luis 

On Tue, Jun 16, 2015 at 11:48 PM, Kenchappa, Ravindra <ravindra.kenchappa@...> wrote:

Hi Guys,

Me  and Aswin  are from HP have spent some time to understand the ODL-OVSDB architecture. We wanted to work on security groups and hardware l2 gateway but then we heard that  some help is needed in stabilizing the CI systems.  We  can take up some work on CI system or defect fix . Please let us know whom do we work with to get started.

Thanks,

Ravi

 


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




--
Thanks
Anil

Re: I think I've fixed SecGrps and SecGrpRules

Anil Vishnoi
 

I would say just enable the debug log in odl mechanism driver and you will get all the rest call details that it's sending to odl controller. 

On Wed, Jun 17, 2015 at 1:00 AM, Edward Warnicke <hagbard@...> wrote:
Aswin,

If you could stick the pcap files somwhere like google drive or dropbox and share them that would also be mega useful :)

Ed

On Tue, Jun 16, 2015 at 12:29 PM, Suryanarayanan, Aswin <aswin.suryanarayanan@...> wrote:

Hi Ed,

 

We checked with break points in  NeutronSecurityRulesNorthbound and NeutronSecurityGroupsNorthbound in neutron ODL. We will analyze with wireshark and get back.

 

Aswin

 

From: Edward Warnicke [mailto:hagbard@...]
Sent: Tuesday, June 16, 2015 11:40 PM
To: Suryanarayanan, Aswin
Cc: ovsdb-dev@...; Kenchappa, Ravindra; neutron-dev@...; groupbasedpolicy-dev@...
Subject: Re: [ovsdb-dev] I think I've fixed SecGrps and SecGrpRules

 

Looping in other interested parties.

 

Ravi,

 

Lets start debugging at the top :)

 

1)  When you create a VM, what call are you expecting to see to ODL, and how are you verifying you don't see it (wireshark, etc)

 

The reason I ask, is because the issue could be in any of the following components:

 

1) Neutron

2) ML2

3) ODL ML2 Driver (in Stackforge)

4) ODL Neutron Northbound (in ODL)

5) The provider

 

Usually, the simplest way to start debugging for me is to answer the question:

 

On the wire, do I see the REST calls I expected.

 

Once we know the answer to that, we can drill further down :)

 

Ed

 

 

 

On Tue, Jun 16, 2015 at 11:44 AM, Suryanarayanan, Aswin <aswin.suryanarayanan@...> wrote:

Hi Ed,

 

Me and Ravi  tired with the devstack kilo with latest code from networking-odl(few changes in neutron as well) along with latest ODL. We observed that when we created a network from horizon we received a call to NeutronSecurityRulesNorthbound  createSecurityRules with empty list. But when we created a vm call didn’t seem to reach Neutron northbound in ODL and no flows where inserted Table 40 or Table 90.  Shouldn’t we have the default rules to be added?  Could you please clarify?  Also when we tried to create SG from horizon UI, none of the call hit the Neutron Security Groups in ODL. Do that require any further changes in networking-odl/neutron?

 

Aswin


_______________________________________________
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




--
Thanks
Anil

Re: I think I've fixed SecGrps and SecGrpRules

Edward Warnicke <hagbard@...>
 

Aswin,

If you could stick the pcap files somwhere like google drive or dropbox and share them that would also be mega useful :)

Ed

On Tue, Jun 16, 2015 at 12:29 PM, Suryanarayanan, Aswin <aswin.suryanarayanan@...> wrote:

Hi Ed,

 

We checked with break points in  NeutronSecurityRulesNorthbound and NeutronSecurityGroupsNorthbound in neutron ODL. We will analyze with wireshark and get back.

 

Aswin

 

From: Edward Warnicke [mailto:hagbard@...]
Sent: Tuesday, June 16, 2015 11:40 PM
To: Suryanarayanan, Aswin
Cc: ovsdb-dev@...; Kenchappa, Ravindra; neutron-dev@...; groupbasedpolicy-dev@...
Subject: Re: [ovsdb-dev] I think I've fixed SecGrps and SecGrpRules

 

Looping in other interested parties.

 

Ravi,

 

Lets start debugging at the top :)

 

1)  When you create a VM, what call are you expecting to see to ODL, and how are you verifying you don't see it (wireshark, etc)

 

The reason I ask, is because the issue could be in any of the following components:

 

1) Neutron

2) ML2

3) ODL ML2 Driver (in Stackforge)

4) ODL Neutron Northbound (in ODL)

5) The provider

 

Usually, the simplest way to start debugging for me is to answer the question:

 

On the wire, do I see the REST calls I expected.

 

Once we know the answer to that, we can drill further down :)

 

Ed

 

 

 

On Tue, Jun 16, 2015 at 11:44 AM, Suryanarayanan, Aswin <aswin.suryanarayanan@...> wrote:

Hi Ed,

 

Me and Ravi  tired with the devstack kilo with latest code from networking-odl(few changes in neutron as well) along with latest ODL. We observed that when we created a network from horizon we received a call to NeutronSecurityRulesNorthbound  createSecurityRules with empty list. But when we created a vm call didn’t seem to reach Neutron northbound in ODL and no flows where inserted Table 40 or Table 90.  Shouldn’t we have the default rules to be added?  Could you please clarify?  Also when we tried to create SG from horizon UI, none of the call hit the Neutron Security Groups in ODL. Do that require any further changes in networking-odl/neutron?

 

Aswin


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

 


Re: I think I've fixed SecGrps and SecGrpRules

Suryanarayanan, Aswin <aswin.suryanarayanan@...>
 

Hi Ed,

 

We checked with break points in  NeutronSecurityRulesNorthbound and NeutronSecurityGroupsNorthbound in neutron ODL. We will analyze with wireshark and get back.

 

Aswin

 

From: Edward Warnicke [mailto:hagbard@...]
Sent: Tuesday, June 16, 2015 11:40 PM
To: Suryanarayanan, Aswin
Cc: ovsdb-dev@...; Kenchappa, Ravindra; neutron-dev@...; groupbasedpolicy-dev@...
Subject: Re: [ovsdb-dev] I think I've fixed SecGrps and SecGrpRules

 

Looping in other interested parties.

 

Ravi,

 

Lets start debugging at the top :)

 

1)  When you create a VM, what call are you expecting to see to ODL, and how are you verifying you don't see it (wireshark, etc)

 

The reason I ask, is because the issue could be in any of the following components:

 

1) Neutron

2) ML2

3) ODL ML2 Driver (in Stackforge)

4) ODL Neutron Northbound (in ODL)

5) The provider

 

Usually, the simplest way to start debugging for me is to answer the question:

 

On the wire, do I see the REST calls I expected.

 

Once we know the answer to that, we can drill further down :)

 

Ed

 

 

 

On Tue, Jun 16, 2015 at 11:44 AM, Suryanarayanan, Aswin <aswin.suryanarayanan@...> wrote:

Hi Ed,

 

Me and Ravi  tired with the devstack kilo with latest code from networking-odl(few changes in neutron as well) along with latest ODL. We observed that when we created a network from horizon we received a call to NeutronSecurityRulesNorthbound  createSecurityRules with empty list. But when we created a vm call didn’t seem to reach Neutron northbound in ODL and no flows where inserted Table 40 or Table 90.  Shouldn’t we have the default rules to be added?  Could you please clarify?  Also when we tried to create SG from horizon UI, none of the call hit the Neutron Security Groups in ODL. Do that require any further changes in networking-odl/neutron?

 

Aswin


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

 

Work on CI systems and or bug fixing

Kenchappa, Ravindra <ravindra.kenchappa@...>
 

Hi Guys,

Me  and Aswin  are from HP have spent some time to understand the ODL-OVSDB architecture. We wanted to work on security groups and hardware l2 gateway but then we heard that  some help is needed in stabilizing the CI systems.  We  can take up some work on CI system or defect fix . Please let us know whom do we work with to get started.

Thanks,

Ravi

 

Re: I think I've fixed SecGrps and SecGrpRules

Edward Warnicke <hagbard@...>
 

Looping in other interested parties.

Ravi,

Lets start debugging at the top :)

1)  When you create a VM, what call are you expecting to see to ODL, and how are you verifying you don't see it (wireshark, etc)

The reason I ask, is because the issue could be in any of the following components:

1) Neutron
2) ML2
3) ODL ML2 Driver (in Stackforge)
4) ODL Neutron Northbound (in ODL)
5) The provider

Usually, the simplest way to start debugging for me is to answer the question:

On the wire, do I see the REST calls I expected.

Once we know the answer to that, we can drill further down :)

Ed

 

On Tue, Jun 16, 2015 at 11:44 AM, Suryanarayanan, Aswin <aswin.suryanarayanan@...> wrote:

Hi Ed,

 

Me and Ravi  tired with the devstack kilo with latest code from networking-odl(few changes in neutron as well) along with latest ODL. We observed that when we created a network from horizon we received a call to NeutronSecurityRulesNorthbound  createSecurityRules with empty list. But when we created a vm call didn’t seem to reach Neutron northbound in ODL and no flows where inserted Table 40 or Table 90.  Shouldn’t we have the default rules to be added?  Could you please clarify?  Also when we tried to create SG from horizon UI, none of the call hit the Neutron Security Groups in ODL. Do that require any further changes in networking-odl/neutron?

 

Aswin


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


Re: ODL OVSDB hardware vtep support initial kick-off

Sam Hague
 

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

Re: I think I've fixed SecGrps and SecGrpRules

Suryanarayanan, Aswin <aswin.suryanarayanan@...>
 

Hi Ed,

 

Me and Ravi  tired with the devstack kilo with latest code from networking-odl(few changes in neutron as well) along with latest ODL. We observed that when we created a network from horizon we received a call to NeutronSecurityRulesNorthbound  createSecurityRules with empty list. But when we created a vm call didn’t seem to reach Neutron northbound in ODL and no flows where inserted Table 40 or Table 90.  Shouldn’t we have the default rules to be added?  Could you please clarify?  Also when we tried to create SG from horizon UI, none of the call hit the Neutron Security Groups in ODL. Do that require any further changes in networking-odl/neutron?

 

Aswin

Re: ODL OVSDB hardware vtep support initial kick-off

Abhijit Kumbhare
 

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

Re: ODL OVSDB hardware vtep support initial kick-off

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

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.

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

Flavio Fernandes <ffernand@...>
 


On Jun 15, 2015, at 6:26 AM, Mathieu Lemay <mlemay@...> wrote:

Actually someone is already on this patch coming to integration..



Awesome. Thanks, Mat!

— flavio

Cheers

On Jun 15, 2015 6:22 AM, "Flavio Fernandes" <ffernand@...> wrote:

On Jun 14, 2015, at 5:31 PM, Luis Gomez <ecelgp@...> wrote:

OK I think this sequence of commands and checks can be easily implemented in robot framework, we can discuss further next ovsdb call.


cool!

Do you also have a similar script for L2 forwarding?

I can do that… stay tuned. ;)


BR/Luis



On Jun 12, 2015, at 2:55 AM, Flavio Fernandes <ffernand@...> wrote:


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


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



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

Mathieu Lemay <mlemay@...>
 

Actually someone is already on this patch coming to integration..

Cheers

On Jun 15, 2015 6:22 AM, "Flavio Fernandes" <ffernand@...> wrote:


On Jun 14, 2015, at 5:31 PM, Luis Gomez <ecelgp@...> wrote:

OK I think this sequence of commands and checks can be easily implemented in robot framework, we can discuss further next ovsdb call.


cool!

Do you also have a similar script for L2 forwarding?

I can do that… stay tuned. ;)


BR/Luis



On Jun 12, 2015, at 2:55 AM, Flavio Fernandes <ffernand@...> wrote:


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


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


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

Flavio Fernandes <ffernand@...>
 


On Jun 14, 2015, at 5:31 PM, Luis Gomez <ecelgp@...> wrote:

OK I think this sequence of commands and checks can be easily implemented in robot framework, we can discuss further next ovsdb call.


cool!

Do you also have a similar script for L2 forwarding?

I can do that… stay tuned. ;)


BR/Luis



On Jun 12, 2015, at 2:55 AM, Flavio Fernandes <ffernand@...> wrote:


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


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


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

Luis Gomez
 

OK I think this sequence of commands and checks can be easily implemented in robot framework, we can discuss further next ovsdb call.

Do you also have a similar script for L2 forwarding?

BR/Luis



On Jun 12, 2015, at 2:55 AM, Flavio Fernandes <ffernand@...> wrote:


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


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

RC0 Test Status

George Zhao <George.Y.Zhao@...>
 

Hello,

 

You receive this email because your project hasn’t reported RC0 test status, please take time to do so.

 

RC0 can be downloaded:

https://nexus.opendaylight.org/content/repositories/automatedweeklyreleases-1057/org/opendaylight/integration/distribution-karaf/0.3.0-Lithium-RC0/

 

RC0 test status should be updated:

https://docs.google.com/spreadsheets/d/1KPpO9LH539Vlcoa4RvLa6PPCdLifi5JD-ihRhlybqeo/edit#gid=1072617634

 

thanks,

George

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

Luis Gomez
 

Cool, I will take a look over the weekend.

BR/Luis


On Jun 12, 2015, at 2:55 AM, Flavio Fernandes <ffernand@...> wrote:


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


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

3281 - 3300 of 4855