Operating System: All
Platform: All

Please let me know if you need more details about it. In my setup, i just have one chain with one SF in it. I am making the same call that tacker demo makes, but the only difference was that i was setting the name of rsp to the name of SFP.

Investigating...

I cant reproduce this.

I just pulled ODL Carbon master on October 4, 2016 and did the following:

1. Create 1 SF and 1 SFF

2. Create the following SFC:

{
"service-function-chains": {
"service-function-chain": [
{
"name": "sfc-chain-1sf1sff",
"symmetric": true,
"sfc-service-function": [

]
}
]
}
}

3. Create the following SFP:

{
"service-function-paths": {
"service-function-path": [

]
}
}

4. Create the following RSP:

{
"input":

}

5. Dump the flows:

ebrjohn@colorado:~$ sudo ovs-ofctl -O OpenFlow13 dump-flows br-int | awk '

'
OFPST_FLOW (OF1.3)
cookie=0x14, table=0, priority=5 actions=goto_table:1
cookie=0x14, table=1, priority=300,udp,nw_dst=10.0.0.10,tp_dst=6633 actions=output:0
cookie=0x14, table=1, priority=300,udp,in_port=0,tp_dst=6633 actions=LOCAL
cookie=0x14, table=1, priority=250,nsp=28 actions=goto_table:4
cookie=0x14, table=1, priority=250,nsp=8388636 actions=goto_table:4
cookie=0x14, table=1, priority=5 actions=drop
cookie=0x14, table=2, priority=5 actions=goto_table:3
cookie=0x14, table=3, priority=5 actions=goto_table:4
cookie=0x14, table=4, priority=550,nsi=255,nsp=28 actions=load:0xa00000a->NXM_NX_TUN_IPV4_DST[],goto_table:10
cookie=0x14, table=4, priority=550,nsi=255,nsp=8388636 actions=load:0xa00000a->NXM_NX_TUN_IPV4_DST[],goto_table:10
cookie=0x14, table=4, priority=5 actions=goto_table:10
cookie=0xba5eba1100000102, table=10, priority=660,nsi=254,nsp=28,nshc1=0 actions=IN_PORT
cookie=0xba5eba1100000102, table=10, priority=660,nsi=254,nsp=8388636,nshc1=0 actions=IN_PORT
<... skipping the rest of the flows for brevity ...>

6. Query the RSP from the data store:

HTTP GET operational/rendered-service-path:rendered-service-paths/
result: 200
{
"rendered-service-paths": {
"rendered-service-path": [
{
"name": "sfc-path-1sf1sff",
"starting-index": 255,
"service-chain-name": "sfc-chain-1sf1sff",
"sfc-encapsulation": "service-locator:nsh",
"symmetric-path-id": 8388636,
"rendered-service-path-hop": [

],
"parent-service-function-path": "sfc-path-1sf1sff",
"path-id": 28,
"transport-type": "service-locator:vxlan-gpe"
},
{
"name": "sfc-path-1sf1sff-Reverse",
"starting-index": 255,
"service-chain-name": "sfc-chain-1sf1sff",
"sfc-encapsulation": "service-locator:nsh",
"symmetric-path-id": 28,
"rendered-service-path-hop": [

],
"parent-service-function-path": "sfc-path-1sf1sff",
"path-id": 8388636,
"transport-type": "service-locator:vxlan-gpe"
}
]
}
}

As you can see from the results above, the NSP/path-id is the same in both the OpenFlow flows and the RSP.

Brady