Open sajith opened 1 year ago
We have the below connection request:
{ "id": "id", "name": "AMLight", "start_time": "2000-01-23T04:56:07.000Z", "end_time": "2000-01-23T04:56:07.000Z", "bandwidth_required": 10, "latency_required": 300, "egress_port": { "id": "urn:sdx:port:amlight.net:A1:1", "name": "Novi100:1", "node": "urn:sdx:node:amlight.net:A1", "status": "up" }, "ingress_port": { "id": "urn:ogf:network:sdx:port:zaoxi:A1:2", "name": "Novi100:2", "node": "urn:ogf:network:sdx:node:zaoxi:A1", "status": "up" } }
When it is solved and broken down against amlight + sax + zaoxi topology descriptions, we get:
{ "urn:ogf:network:sdx:topology:zaoxi.net": { "ingress_port": { "id": "urn:ogf:network:sdx:port:zaoxi:A1:2", "name": "Novi100:2", "short_name": null, "node": "urn:ogf:network:sdx:node:zaoxi:A1", "label_range": null, "status": null, "state": null, "private_attributes": null }, "egress_port": { "id": "urn:ogf:network:sdx:port:zaoxi:B1:1", "name": "Novi01:1", "node": "urn:ogf:network:sdx:node:zaoxi:B1", "short_name": "B1:1", "label_range": [ "100-200", "10001" ], "status": "up" } }, "urn:ogf:network:sdx:topology:sax.net": { "ingress_port": { "id": "urn:ogf:network:sdx:port:sax:B3:1", "label_range": [ "100-200", "1000" ], "name": "Novi02:3", "node": "urn:ogf:network:sdx:node:sax:B3", "short_name": "B3:1", "status": "up" }, "egress_port": { "id": "urn:ogf:network:sdx:port:sax:B1:1", "name": "Novi01:1", "node": "urn:ogf:network:sdx:node:sax:B1", "short_name": "B1:1", "label_range": [ "100-200", "10001" ], "status": "up" } }, "urn:ogf:network:sdx:topology:amlight.net": { "ingress_port": { "id": "urn:sdx:port:amlight:B1:1", "name": "Novi01:1", "node": "urn:sdx:node:amlight.net:B1", "short_name": "B1:1", "label_range": [ "100-200", "10001" ], "status": "up" }, "egress_port": { "id": "urn:sdx:port:amlight.net:A1:1", "name": "Novi100:1", "short_name": null, "node": "urn:sdx:node:amlight.net:A1", "label_range": null, "status": null, "state": null, "private_attributes": null } } }
Notice that properties like label_range are set to null in Zaoxi ingress port and AmLight ingress port descriptions.
label_range
null
Perhaps we do not need all the extra data about each port in the above intermediate breakdown. We probably need just id (port ID) and node (node ID) and not the rest of it.
id
node
We have the below connection request:
When it is solved and broken down against amlight + sax + zaoxi topology descriptions, we get:
Notice that properties like
label_range
are set tonull
in Zaoxi ingress port and AmLight ingress port descriptions.