[VTN-89] Port mapping was not configured with OpenStack Liberty Created: 26/Nov/15  Updated: 19/Oct/17  Resolved: 12/Feb/16

Status: Resolved
Project: vtn
Component/s: VTN Manager
Affects Version/s: unspecified
Fix Version/s: None

Type: Bug
Reporter: Ananthi Palaniswamy Assignee: Unassigned
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: Other
Platform: Other

External issue ID: 4678

 Description   

Used Openstack Liberty using CentOS 7.1 with latest VTN Manager (Master)

  • Network Creation success
  • PortMap failure

Used running_config application to test portmap. Portmap is not getting listed. Please find the below output for the same,

"vtn": [
{
"name": "68fd509361a906587c6eb01b82b5bd0",
"idleTimeout": 300,
"hardTimeout": 0,
"vtnFlowfilter":

{ "flowfilter": [] }

,
"vbridge": [
{
"name": "b5246ee100e4fd89b50cf8b30fecdd0",
"faults": 0,
"state": -1,
"ageInterval": 600,
"description": "External",
"macentry":

{ "macentry": [] }

,
"brvlan":

{ "vlanmap": [] }

,
"vbrInterface": [
{
"name": "6aecc91fc169614bfafc58b69c15417",
"state": -1,
"entityState": -1,
"description": "",
"enabled": true,
"portmap": {
"node": {},
"port": {},
"mapped": {}
}
},
{
"name": "c39a6973a5a5d64a0b7f16150bf60c2",
"state": -1,
"entityState": -1,
"description": "",
"enabled": true,
"portmap": {
"node": {},
"port": {},

 Comments   
Comment by Ananthi Palaniswamy [ 09/Feb/16 ]

Verified with stable/beryllium the issue doesn't occur.For the created VM instance the port map is getting created.

"vtn": [
{
"name": "97963db13cdd2afbed5b6eab583140c",
"idleTimeout": 300,
"hardTimeout": 0,
"vtnFlowfilter":

{ "flowfilter": [] }

,
"vbridge": [
{
"name": "2c34e4730e87ece86eddc50abe19b70",
"faults": 0,
"state": 1,
"ageInterval": 600,
"description": "private",
"macentry":

{ "macentry": [] }

,
"brvlan":

{ "vlanmap": [] }

,
"vbrInterface": [
{
"name": "00b8d425359f0bf9ced021324721999",
"state": 1,
"entityState": 1,
"description": "",
"enabled": true,
"portmap": {
"node":

{ "type": "OF", "id": "00:00:00:50:56:84:03:ad" }

,
"port":

{ "type": "OF", "id": "5", "name": "tap00b8d425-35" }

,
"mapped":

{ "type": "OF", "id": "5" }

}
}

Hence closing the Bug.

Comment by Venkatrangan Govindarajan [ 10/Feb/16 ]

Same Problem is observed in the recent tests

Stacked

stack@ubuntu-devstack:~$ sudo ovs-vsctl show
05e99c91-f096-47ec-b543-ced32679d910
Manager "tcp:192.168.2.147:6640"
is_connected: true
Bridge br-int
Controller "tcp:192.168.2.147:6653"
is_connected: true
fail_mode: secure
Port br-int
Interface br-int
type: internal
Port "tap75efdc93-b0"
Interface "tap75efdc93-b0"
Port "tap11695f2d-62"
Interface "tap11695f2d-62"
Port "eth1"
Interface "eth1"
ovs_version: "2.3.2"

stack@ubuntu-devstack-compute:~$ sudo ovs-vsctl show
7ed44d13-b24d-4889-92e9-60498280795b
Manager "tcp:192.168.2.147:6640"
is_connected: true
Bridge br-int
Controller "tcp:192.168.2.147:6653"
is_connected: true
fail_mode: secure
Port br-int
Interface br-int
type: internal
Port "tapf89f5ff7-7d"
Interface "tapf89f5ff7-7d"
Port "eth1"
Interface "eth1"
ovs_version: "2.3.2"

Comment by Venkatrangan Govindarajan [ 10/Feb/16 ]

(In reply to Venkatrangan Govindarajan from comment #2)
> Same Problem is observed in the recent tests
>
> Stacked and created some instances, then this was the observation of sudo ovs-vsctl show in control and compute nodes
>
>
> stack@ubuntu-devstack:~$ sudo ovs-vsctl show
> 05e99c91-f096-47ec-b543-ced32679d910
> Manager "tcp:192.168.2.147:6640"
> is_connected: true
> Bridge br-int
> Controller "tcp:192.168.2.147:6653"
> is_connected: true
> fail_mode: secure
> Port br-int
> Interface br-int
> type: internal
> Port "tap75efdc93-b0"
> Interface "tap75efdc93-b0"
> Port "tap11695f2d-62"
> Interface "tap11695f2d-62"
> Port "eth1"
> Interface "eth1"
> ovs_version: "2.3.2"
>
>
>
>
> stack@ubuntu-devstack-compute:~$ sudo ovs-vsctl show
> 7ed44d13-b24d-4889-92e9-60498280795b
> Manager "tcp:192.168.2.147:6640"
> is_connected: true
> Bridge br-int
> Controller "tcp:192.168.2.147:6653"
> is_connected: true
> fail_mode: secure
> Port br-int
> Interface br-int
> type: internal
> Port "tapf89f5ff7-7d"
> Interface "tapf89f5ff7-7d"
> Port "eth1"
> Interface "eth1"
> ovs_version: "2.3.2"

The VTN Configuration is expected to have port mapping for all the tap interfaces, But it was missing the compute node interfaces
Hence the interfaces that were created in the compute node were unable to reach the dhcp

VTN Configuration

{
"vtns": {
"vtn": [
{
"name": "cb0e8e446b58161a8fcd83de4ef9432",
"vtenant-config":

{ "idle-timeout": 300, "hard-timeout": 0 }

,
"vbridge": [
{
"name": "dd85e676f4287f3beff6fed050db1de",
"bridge-status":

{ "state": "UP", "path-faults": 0 }

,
"vbridge-config":

{ "age-interval": 600, "description": "vtn" }

,
"vinterface": [
{
"name": "75efdc93b013d4a9c8973244369f8e1",
"port-map-config":

{ "vlan-id": 0, "port-name": "tap75efdc93-b0", "node": "openflow:52241477026", "port-id": "2" }

,
"vinterface-status":

{ "mapped-port": "openflow:52241477026:2", "state": "UP", "entity-state": "UP" }

,
"vinterface-config":

{ "enabled": true, "description": "" }

},
{
"name": "f89f5ff77db30eab5deb3769603b3fd",
"vinterface-config":

{ "enabled": true, "description": "" }

,
"vinterface-status":

{ "state": "UNKNOWN", "entity-state": "UNKNOWN" }

},
{
"name": "11695f2d6256329bf5b18322dd6858c",
"port-map-config":

{ "vlan-id": 0, "port-name": "tap11695f2d-62", "node": "openflow:52241477026", "port-id": "4" }

,
"vinterface-status":

{ "mapped-port": "openflow:52241477026:4", "state": "UP", "entity-state": "UP" }

,
"vinterface-config":

{ "enabled": true, "description": "" }

}
]
}
]
}
]
}
}

Comment by Ananthi Palaniswamy [ 11/Feb/16 ]

Fixed and pushed the patch to stable/beryllium

https://git.opendaylight.org/gerrit/#/c/34465/2

Comment by Venkatrangan Govindarajan [ 11/Feb/16 ]

Problem: The curent implmentation was always expecting the OpenFlow port for a newly added interface will be available from network topology. Is some cases, the port id was not available and only portname was available.

VTN portmapping works with port ID or portname. The fix will be to work even when portId is not retreived.

After the fix the portmapping looks like this

{
"vtns": {
"vtn": [
{
"name": "d45f236d710fcb5a816b76b18776fa3",
"vtenant-config":

{ "hard-timeout": 0, "idle-timeout": 300 }

,
"vbridge": [
{
"name": "5175a6a853620a19741f35dba2c1258",
"vbridge-config":

{ "age-interval": 600, "description": "vtn" }

,
"bridge-status":

{ "path-faults": 0, "state": "UP" }

,
"vinterface": [
{
"name": "4241135c932caf89354b230347a2146",
"port-map-config":

{ "node": "openflow:49213351597700", "port-name": "tap4241135c-93", "vlan-id": 0 }

,
"vinterface-status":

{ "entity-state": "UP", "mapped-port": "openflow:49213351597700:3", "state": "UP" }

,
"vinterface-config":

{ "enabled": true, "description": "" }

},
{
"name": "cd0bae600ee9b5694a5c78953bfca41",
"port-map-config":

{ "node": "openflow:49213351597700", "vlan-id": 0, "port-id": "2" }

,
"vinterface-status":

{ "entity-state": "UP", "mapped-port": "openflow:49213351597700:2", "state": "UP" }

,
"vinterface-config":

{ "enabled": true, "description": "" }

},
{
"name": "894b8d48513e61980332c525c05231a",
"port-map-config":

{ "node": "openflow:49213349419381", "port-name": "tap894b8d48-51", "vlan-id": 0 }

,
"vinterface-status":

{ "entity-state": "UP", "mapped-port": "openflow:49213349419381:2", "state": "UP" }

,
"vinterface-config":

{ "enabled": true, "description": "" }

}
]
}
]
}
]
}
}

Comment by Ananthi Palaniswamy [ 12/Feb/16 ]

Tested and verified portmap for all tapped interface.

Fixed and pushed the patch to stable/beryllium

https://git.opendaylight.org/gerrit/#/c/34465

and master

https://git.opendaylight.org/gerrit/#/c/34532/

Hence closing the Bug.

Generated at Wed Feb 07 20:48:00 UTC 2024 using Jira 8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d.