VxLAN system test


Luis Gomez
 

Hi Chaudhry,

I finally verified test case 2) "Use OF1.3 tunnel-id match and action to read VxLAN incoming packet tunnel-id and write VxLAN outgoing packet tunnel-id":

First you need to specify in the vxlan TP configuration tunnel-id will be set by openflow, for that just use a body like this example:

{
  "network-topology:termination-point": [
    {
  "ovsdb:options": [
    {
                  "ovsdb:option": "remote_ip",
                  "ovsdb:value" : "192.168.0.10"
    },
    {
                  "ovsdb:option": "key",
                  "ovsdb:value" : "flow"
    }
  ],
          "ovsdb:interface-type": "ovsdb:interface-type-vxlan",
  "ovsdb:name": "vxlanport",
  "tp-id": "vxlanport",
  "ofport": 2
}
    ]
}

Second you can use the following flow bodies to send traffic from/to the tunnel:

From VxLAN tunnel-id 2 to port 1:

<flow xmlns="urn:opendaylight:flow:inventory">
    <priority>2</priority>
    <flow-name>flow1</flow-name>
    <match>
        <tunnel>
            <tunnel-id>2</tunnel-id>
        </tunnel>
        <in-port>openflow:1:2</in-port>
    </match>    
    <id>1</id>
    <table_id>0</table_id>
    <instructions>
        <instruction>
            <order>0</order>
            <apply-actions>
                <action>
                    <order>0</order>
                    <output-action>
                        <output-node-connector>1</output-node-connector>
                    </output-action>
                </action>
            </apply-actions>
        </instruction>
    </instructions>
</flow>

From port 1 to VxLAN tunnel-id 2:

<flow xmlns="urn:opendaylight:flow:inventory">
    <hard-timeout>0</hard-timeout>
    <idle-timeout>0</idle-timeout>
    <priority>2</priority>
    <flow-name>flow2</flow-name>
    <match>
        <in-port>openflow:1:1</in-port>
    </match>    
    <id>2</id>
    <table_id>0</table_id>
    <instructions>
        <instruction>
            <order>0</order>
            <apply-actions>
                <action>
                    <order>0</order>
                    <set-field>
                        <tunnel>
                            <tunnel-id>2</tunnel-id>
                        </tunnel>
                    </set-field>
                </action>
                <action>
                    <order>2</order>
                    <output-action>
                        <output-node-connector>2</output-node-connector>
                    </output-action>
                </action>
            </apply-actions>
        </instruction>
    </instructions>
</flow>

Please work on a system test for this while I verify the next test case 3) "Use OF Nicira extensions to match VxLAN incoming packet tunnel-src and tunnel-id and write VxLAN outgoing packet tunnel-id and tunnel-dst"

BR/Luis


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

So here is my idea for vxlan testing:

- We bring 2 mininet (OVS) VMs
- We start a modified version of mininet that creates 1 switch + 1 host per VM
- We setup VxLAN tunnel using OVSDB REST API

And now 3 use cases to redirect traffic from/to the tunnel:

1) Use a regular OpenFlow port match and action to direct traffic from/to the VxLAN tunnel
2) Use OF1.3 tunnel-id match and action to read VxLAN incoming packet tunnel-id and write VxLAN outgoing packet tunnel-id
3) Use OF Nicira extensions to match VxLAN incoming packet tunnel-src and tunnel-id and write VxLAN outgoing packet tunnel-id and tunnel-dst

- Finally a ping from host to host will verify the VxLAN transport

I will be sending examples of 2) and 3) very shortly (1 is very straight forward).

BR/Luis



On Jul 2, 2015, at 12:15 AM, Chaudhry usama <chaudhryusama@...> wrote:

Yes Ravi, Luis will be back from PTO on 6th of July and sure we will let you know. Thanks



On Thu, Jul 2, 2015 at 7:45 AM, Kenchappa, Ravindra <ravindra.kenchappa@...> wrote:

Hi  Chaudhry / Luis,

 

Thanks.  Is Luis will be on PTO for the whole week? 

 

I am also working with Aswin on SecurityGroups  implementation and hardware l2 gateway design for Be release.   So anytime if you guys want us to work on any automation test case development please let us know.

 

Thanks,

Ravi

 

 

From: Chaudhry usama [mailto:chaudhryusama@...]
Sent: Monday, June 29, 2015 12:58 PM


To: Kenchappa, Ravindra
Cc: Luis Gomez; Suryanarayanan, Aswin
Subject: Re: [ovsdb-dev] Work on CI systems and or bug fixing

 

Hi Ravi,

Good to hear that. Actually Luis is on PTO so he may reply late and he is the one who can answer this question in a better way.

However, I am working on testcase to test the VXLAN port functionality and this will be the last testcase for OVSDB-SouthBound till Lithium release from ourside.

Thanks,

Chaudhry

 

 

On Mon, Jun 29, 2015 at 8:44 AM, Kenchappa, Ravindra <ravindra.kenchappa@...> wrote:

Hi Chaudhry / Luis,

 

Thanks for the help you guys provided to setup the CI locally. 

 

I have loaded the ovsdb-southbound postman collection and browse the API calls. The new RestConf APIs are related to VXlan termination point and you are working on VXLAN related test cases.  Is there any other OVSDB-SouthBound  related feature that I can take up? 

 

Any other OVSDB projected related features that I can take up and start working on added test cases?

 

Please advice?

 

Thanks,

Ravi

 

From: Chaudhry usama [mailto:chaudhryusama@...]
Sent: Wednesday, June 24, 2015 10:29 PM


To: Kenchappa, Ravindra
Cc: Luis Gomez; Suryanarayanan, Aswin
Subject: Re: [ovsdb-dev] Work on CI systems and or bug fixing

 

Great :)

Below is the link of Restconf APIs that are related to OVSDB southbound plugin.
https://github.com/opendaylight/ovsdb/blob/master/resources/commons/OVSDB_Southbound.postman_collection

 

On Wed, Jun 24, 2015 at 8:20 PM, Kenchappa, Ravindra <ravindra.kenchappa@...> wrote:

Thanks Chaudhry,  it worked!

 

I have installed “feature:odl-ovsdb-all” thinking that all of OVSDB module will be installed but after seeing your email I had to install “feature:install odl-ovsdb-openstack” to get it work. Now 37 tests are passing.

Can you let me know where can I find the list of RESTCONF APIs that are related to OVSDB southbound plugin?

 

Regards,

Ravi

 

From: Chaudhry usama [mailto:chaudhryusama@...]
Sent: Wednesday, June 24, 2015 1:24 PM


To: Kenchappa, Ravindra
Cc: Luis Gomez; Suryanarayanan, Aswin
Subject: Re: [ovsdb-dev] Work on CI systems and or bug fixing

 

No i don't see any problem. I am also using the same OVA.

I do the following steps to successfully run the tests.

1) Run the controller and install the karaf feature (feature:install odl-ovsdb-openstack)

2) Wait for few seconds

3) Start the Robot (Southbound_Domain) testsuites with these arguments
-v CONTROLLER:127.0.0.1 -v MININET:127.0.0.1 -v USER_HOME:$HOME -v MININET_USER:mininet

4) It runs successfully.

If you want I can hangout with you to see whats going on.

 

On Wed, Jun 24, 2015 at 11:52 AM, Kenchappa, Ravindra <ravindra.kenchappa@...> wrote:

I used the OVA for setting up the test bed by following the instruction.  https://wiki.opendaylight.org/view/CrossProject:Integration_Group:Test_VMs.   My OVS version is 2.0.3 and the mininet supports OF 1.3. Robot Framework ver is 2.8.6..

 

Do you see any problem here?  Should I manually install all of them?

 

Here is the error I am seeing now:

 

20150624 07:16:45.727 :  INFO :

Argument types are:

<type 'bool'>

Starting test: Southbound Domain.Connection Manager.Make the OVS instacne to listen for connection

20150624 07:16:45.730 :  INFO : Attempting to execute sudo ovs-vsctl del-manager on 127.0.0.1

20150624 07:16:45.731 :  INFO : ${conn_id} = 1

20150624 07:16:45.732 :  INFO : Logging into '127.0.0.1:22' as 'mininet'.

20150624 07:16:46.078 :  INFO :

Read output: Welcome to Ubuntu 14.04.1 LTS (GNU/Linux 3.13.0-43-generic x86_64)

 

* Documentation:  https://help.ubuntu.com/

 

17 packages can be updated.

3 updates are security updates.

 

Last login: Wed Jun 24 04:49:37 2015 from 127.0.0.1

mininet@mininet-vm:~\>

20150624 07:16:46.083 :  INFO : sudo ovs-vsctl del-manager

20150624 07:16:46.097 :  INFO : mininet@mininet-vm:~\>

20150624 07:16:46.098 :  INFO : ${output} = mininet@mininet-vm:~\>

20150624 07:16:46.215 :  INFO : mininet@mininet-vm:~\>

20150624 07:16:46.218 :  INFO : Attempting to execute sudo ovs-vsctl set-manager ptcp:6644 on 127.0.0.1

20150624 07:16:46.221 :  INFO : ${conn_id} = 2

20150624 07:16:46.222 :  INFO : Logging into '127.0.0.1:22' as 'mininet'.

20150624 07:16:46.545 :  INFO :

Read output: Welcome to Ubuntu 14.04.1 LTS (GNU/Linux 3.13.0-43-generic x86_64)

 

* Documentation:  https://help.ubuntu.com/

 

17 packages can be updated.

3 updates are security updates.

 

Last login: Wed Jun 24 07:16:45 2015 from 127.0.0.1

mininet@mininet-vm:~\>

20150624 07:16:46.550 :  INFO : sudo ovs-vsctl set-manager ptcp:6644

20150624 07:16:46.561 :  INFO : mininet@mininet-vm:~\>

20150624 07:16:46.561 :  INFO : ${output} = mininet@mininet-vm:~\>

20150624 07:16:46.680 :  INFO : mininet@mininet-vm:~\>

Ending test:   Southbound Domain.Connection Manager.Make the OVS instacne to listen for connection

 

Thanks,

Ravi

 

From: Chaudhry usama [mailto:chaudhryusama@...]
Sent: Wednesday, June 24, 2015 11:14 AM
To: Kenchappa, Ravindra
Cc: Luis Gomez; Suryanarayanan, Aswin


Subject: Re: [ovsdb-dev] Work on CI systems and or bug fixing

 

Hi Kenchappa,

       

Can you verify the following steps in the link in your environment.
https://wiki.opendaylight.org/view/CrossProject:Integration_Group:Create_System_Test_Environment#Mininet_Environment_Adjustment

 

On Wed, Jun 24, 2015 at 8:25 AM, Kenchappa, Ravindra <ravindra.kenchappa@...> wrote:

Thanks for your response.

 

I have all the following variables set:

·         CONTROLLER: 127.0.0.1

·         MININET: 127.0.0.1

·         USER_HOME:/home/mininet

·         MININET_USER:mininet

·          

But I have to find a way to fix RIDE or test suites using the porxy when trying to establish the connection.   Restarting the VM address the issue and few testcases are failing (may be some ENV issue) and I will figure out that.

 

Thanks,

Ravi

 

From: Luis Gomez [mailto:ecelgp@...]
Sent: Wednesday, June 24, 2015 8:36 AM
To: Kenchappa, Ravindra
Cc: Chaudhry usama; Suryanarayanan, Aswin


Subject: Re: [ovsdb-dev] Work on CI systems and or bug fixing

 

You need to pass default variables explained here:

 

 

BR/Luis

 

 

On Jun 23, 2015, at 7:56 PM, Kenchappa, Ravindra <ravindra.kenchappa@...> wrote:

 

Hi Chaudhry,

 

Good moorning!

 

Thanks.  I was able to setup local  environment for testing Robot tests.  I pulled the latest integration/test suits and installed recent ODL “distribution-karaf-0.3.0-SNAPSHOT”.   The VM where OLD/Robot/mininet is running using NAT as network setting.

 

From the RIDE when I try to execute the “SouthBound Domain” test suite I had few error on few ENV variables are not defined (MININET, MININET_USER etc) . Once this was fixed I was able to run the test.  On the this VM I have set the http_proxy  so the testcase in “Connection Manager : Connect to OVSDB Node” fails because of the following:

 

20150623 09:51:07.617 :  INFO : URL is /restconf/config/network-topology:network-topology/topology/ovsdb:1/node/ovsdb:%2F%2F127.0.0.1:6644

20150623 09:51:07.627 :  INFO : Starting new HTTP connection (1): web-proxy.ind.hp.com

20150623 09:51:13.182 :  INFO : Deprication Warning  Use Put Request in the future

Ending test:   Southbound Domain.Connection Manager.Connect to OVSDB Node

 

Instead of start new HTTP connection to mininet (127.0.0.1) the test tries to connect to proxy.   I removed the proxy from my .bashrc and in /etc/environment but still I see the same error.

 

I will try to restart the VM and see whether it helps.

 

Please let me know what could be the reason for this error.

 

Thanks,

Ravi

 

Starting test: Southbound Domain.Connection Manager.Connect to OVSDB Node

20150623 09:51:07.612 :  INFO : Getting file '<a href="file:///home/mininet/integration/test/csit/variables/ovsdb/connect.json">/home/mininet/integration/test/csit/variables/ovsdb/connect.json</a>'

20150623 09:51:07.613 :  INFO :

${sample} = {

  "network-topology:node": [

        {

              "node-id": "ovsdb://127.0.0.1:61644",

              "connection-info": {

                  "ovsdb:remote-port": 61644,

                  "ovsdb:r...

20150623 09:51:07.615 :  INFO :

${sample1} = {

  "network-topology:node": [

        {

              "node-id": "ovsdb://127.0.0.1:61644",

              "connection-info": {

                  "ovsdb:remote-port": 61644,

                  "ovsdb:r...

20150623 09:51:07.616 :  INFO :

${body} = {

  "network-topology:node": [

        {

              "node-id": "ovsdb://127.0.0.1:6644",

              "connection-info": {

                  "ovsdb:remote-port": 6644,

                  "ovsdb:rem...

20150623 09:51:07.617 :  INFO : URL is /restconf/config/network-topology:network-topology/topology/ovsdb:1/node/ovsdb:%2F%2F127.0.0.1:6644

20150623 09:51:07.627 :  INFO : Starting new HTTP connection (1): web-proxy.ind.hp.com

20150623 09:51:13.182 :  INFO : Deprication Warning  Use Put Request in the future

Ending test:   Southbound Domain.Connection Manager.Connect to OVSDB Node

 

 

raveek@ODL:~$

 

 

 

From: Chaudhry usama [mailto:chaudhryusama@...
Sent: Friday, June 19, 2015 4:41 PM
To: Kenchappa, Ravindra
Cc: Luis Gomez; Suryanarayanan, Aswin
Subject: Re: [ovsdb-dev] Work on CI systems and or bug fixing

 

Hi kenchappa,

                    You can follow this link to setting up your local environment for testing Robot tests.

  Link: https://wiki.opendaylight.org/view/CrossProject:Integration_Group:Create_System_Test_Environment

Regarding list of test cases completed

- Basic CRUD bridge/port methods for a new OVS switch (connection initiated through contoller)

- Basic CRUD bridge/port methods for an existing switch (connection initiated through contoller)

Under-review test case is

-Basic CRUD bridge/port methods (connection initiated through ovs)

I am working on vxlan extension test case. 

 

                 

 

 

On Fri, Jun 19, 2015 at 2:49 PM, Kenchappa, Ravindra <ravindra.kenchappa@...> wrote:

Hi Luis / Chaudhry,

 

To start with I would like to work on OVSDB soutbound CI.   I am not sure whether we have L3 forwarding related test case added, if it is not there and is required I can take that up.   Could you please help me in:

 

·         Setting up local environment   for testing the ROBO test case before  adding it to repo

·         Do we have a list of test case which are automated and pending in southbound

 

I have single node devstack and OLD setup running.  Please send me any info/link that will help me quickly ramp up.

 

Thanks for you co-operation.

 

Regards,

Ravi

 

From: Luis Gomez [mailto:ecelgp@...
Sent: Thursday, June 18, 2015 8:40 AM
To: Kenchappa, Ravindra; integration-dev@...
Cc: ovsdb-dev@...; Kyle Mestery; Armando Migliaccio; Anil Vishnoi


Subject: Re: [ovsdb-dev] Work on CI systems and or bug fixing

 

Hi Ravi,

 

Sorry for not answering before, 2 things:

 

1) Can you make tomorrow’s Thursday integration call at 8AM PST details here [1]? This way you can check all open fronts we have in integration today.

 

2) Regarding OVSDB efforts in integration we have Chaudhry (ODL intern) helping with OVSDB SB plugin suite (the one you pointed out), Alexis and Mohamed (Inocybe) preparing the netvirt suite, and Marcus and Praveen (Intel) doing the perf/scalability test for OVSDB plugin.

 

You can sync with any of these folks if you want to help in any of these areas or you can take a new integration task, for the second is good to attend the weekly call.

 

 

 

On Jun 17, 2015, at 7:48 PM, Kenchappa, Ravindra <ravindra.kenchappa@...> wrote:

 

Hi Luis,

 

Can you send me some details on what are those CI Jenkins jobs we can start looking into and what feature requires additional automated test cases.  I am going through the configuration and of CI job https://jenkins.opendaylight.org/releng/view/ovsdb/job/ovsdb-csit-1node-cds-southbound-all-stable-lithium/  and getting familiar. Please let me know.

 

Thanks,

Ravi

 

From: Kyle Mestery [mailto:mestery@...
Sent: Wednesday, June 17, 2015 7:22 AM
To: Anil Vishnoi; Armando Migliaccio
Cc: Kenchappa, Ravindra; Luis Gomez Palacios; ovsdb-dev@...
Subject: Re: [ovsdb-dev] Work on CI systems and or bug fixing

 

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

 

 

 

 

 




Join z.archive.ovsdb-dev@lists.opendaylight.org to automatically receive all group messages.