Details
-
Bug
-
Status: Resolved
-
Resolution: Done
-
unspecified
-
None
-
None
-
Operating System: All
Platform: All
-
3965
Description
Creating a bridge using the JSON below works. But any subsequent SFF/bridge is not created properly. Port and other information is not created, only a naked bridge.
{
"service-function-forwarders": {
"service-function-forwarder": [
{
"name": "SFF1",
"service-node": "OVSDB2",
"service-function-forwarder-ovs:ovs-bridge":
,
"service-function-dictionary": [
{
"name": "firewall-72",
"type": "service-function-type:firewall",
"sff-sf-data-plane-locator":
}
],
"sff-data-plane-locator": [
{
"name": "sfc-tun2",
"data-plane-locator":
,
"service-function-forwarder-ovs:ovs-options":
}
]
},
{
"name": "SFF2",
"service-node": "OVSDB2",
"service-function-forwarder-ovs:ovs-bridge":
,
"service-function-dictionary": [
{
"name": "dpi-74",
"type": "service-function-type:dpi",
"sff-sf-data-plane-locator":
}
],
"sff-data-plane-locator": [
{
"name": "sfc-tun4",
"data-plane-locator":
,
"service-function-forwarder-ovs:ovs-options":
}
]
}
]
}
}
Changing the SFF name, bridge and issuing another PUT does not properly create a bridge in OVS. IT can be seen below that only the bridge (br3, br4) was created, no ports, no options.
sfc-demo@sfc-demo:~$ sudo ovs-vsctl show
fcdf098c-17d8-4f32-ba0f-c74d960b8d19
Manager "tcp:192.168.1.18:6640"
is_connected: true
Bridge "sw2"
Controller "tcp:192.168.1.18:6653"
is_connected: true
Port "sw2"
Interface "sw2"
type: internal
Port "sfc-tun2"
Interface "sfc-tun2"
type: vxlan
options:
Bridge "sw3"
Controller "tcp:192.168.1.18:6653"
is_connected: true
Port "sw3"
Interface "sw3"
type: internal
Bridge "sw4"
Controller "tcp:192.168.1.18:6653"
is_connected: true
Port "sw4"
Interface "sw4"
type: internal