[SFC-114] Operational state of RSP/SFP doesn't reflect scheduling algorithm

Wed, 14 Oct 2015 10:06:26 +0000

RSP:
{
"rendered-service-paths": {
"rendered-service-path": [
{
"name": "SFCGBP-Path-RSP-Reverse",
"parent-service-function-path": "SFCGBP-Path",
"rendered-service-path-hop": [

{ "hop-number": 0, "service-index": 255, "service-function-forwarder-locator": "sfc-tun4", "service-function-name": "dpi-74", "service-function-forwarder": "SFF2" }

{ "hop-number": 1, "service-index": 254, "service-function-forwarder-locator": "sfc-tun2", "service-function-name": "firewall-72", "service-function-forwarder": "SFF1" }

],
"service-chain-name": "SFCGBP",
"path-id": 8388735,
"starting-index": 255,
"symmetric-path-id": 127,
"transport-type": "service-locator:vxlan-gpe"
}
]
}
}

SFP:
{
"service-function-paths-state": {
"service-function-path-state": [
{
"name": "SFCGBP-Path",
"sfp-rendered-service-path": [

{ "name": "SFCGBP-Path-RSP-Reverse" }

{ "name": "SFCGBP-Path-RSP" }

]
}
]
}
}

SFC:
{
"service-function-chains": {
"service-function-chain": [
{
"name": "SFCGBP",
"symmetric": true,
"sfc-service-function": [

{ "name": "firewall-abstract1", "type": "service-function-type:firewall" }

{ "name": "dpi-abstract1", "type": "service-function-type:dpi" }

]
}
]
}
}

If a default scheduling algorithm is being used, it should be enumerated in operational state.

OpenDaylight JIRA

[SFC-114] Operational state of RSP/SFP doesn't reflect scheduling algorithm