GET /config/Context/_connection/{uuid} issue

[vkumaev]

We are implementing GET method for /config/Context/_connection/{uuid}. We do not understand formats of the UUID-fields response.

• uuid;
• (_route) localId;
• (_route) _lowerConnection;
• (_connectionPort) localId;
• (_connectionPort) _connectionEndPoint.

At the moment, we form the following response:

{
"_extensions": [],
  "label": [],
  "uuid": "61f0091b-925b-4dfb-ba38-872465063b81",
  "name": [],
  "resourceSpecTarget": null,
  "resourceSpecification": null,
  "direction": "BIDIRECTIONAL",
  "layerProtocolName": null,
  "_route": [
    {
      "_extensions": [],
      "localId": "61f0091b-925b-4dfb-ba38-872465063b81",
      "_lowerConnection": [
        "279783b9-da9b-42d4-a99e-87c1dd26df36",
        "f1281fbd-dbb5-4ca3-a75e-514ef4f0710f"
      ]
    }
  ],
  "_connectionPort": [
    {
      "_extensions": [],
      "localId": "domaincfg:domain1::1",
      "direction": "INPUT",
      "_connectionEndPoint": "domaincfg:domain1::1",
      "role": null
    },
    {
      "_extensions": [],
      "localId": "domaincfg:domain3::1",
      "direction": "OUTPUT",
      "_connectionEndPoint": "domaincfg:domain3::1",
      "role": null
    }
  ],
  "_state": {
    "operationalState": "ENABLED",
    "lifecycleState": "INSTALLED"
  },
  "_node": "TOP"
}

Whether it is correct? Unfortunately we cannot compare it to your response TAPI reference implementation. Because we think the server gives an incorrect answer:

{
  "_connectionPort": [
    {
      "_connectionEndPoint": {
        "_clientNodeEdgePoint": [
          "http://localhost:8080/restconf/config/Context/_topology/_node/node1/_ownedNodeEdgePoint/pe14/"
        ],
        "uuid": "cep1"
      },
      "localId": "cp1"
    },
    {
      "_connectionEndPoint": {
        "_clientNodeEdgePoint": [
          "http://localhost:8080/restconf/config/Context/_topology/_node/node4/_ownedNodeEdgePoint/pe42/"
        ],
        "uuid": "cep2"
      },
      "localId": "cp2"
    },
    {
      "_connectionEndPoint": {
        "_clientNodeEdgePoint": [
          "http://localhost:8080/restconf/config/Context/_topology/_node/node2/_ownedNodeEdgePoint/pe21/"
        ],
        "uuid": "cep3"
      },
      "localId": "cp3"
    }
  ],
  "direction": "BIDIRECTIONAL",
  "layerProtocolName": "OCH",
  "uuid": "concs1"
}

_connection EndPoint UUID formed relative to the topology, it is correct?

[rvilalta]

@karthik-sethuraman to check

My opinion: https://github.com/OpenNetworkingFoundation/Snowmass-ONFOpenTransport/blob/develop/YANG/TapiConnectivity.yang

states that ConnectionPort contains a container for ConnectionEndPoint object, so the complete object needs to be returned. ConnectionEndPoint is not defined in the Topology, but created at the same time of Connection. ConnectionEndPoint includes a reference to NodeEdgePoint.

[karthik-sethuraman]

Related issues #131

Purely based on current agreement/spec, the ConnectionEndPoint is "contained" by the Connection via the ConnectionPort. So the RI is correct (other than the uuid value's string format). It is a separate question/discussion whether ConnectionEndPoint should be a Local or Global Class.

[karthik-sethuraman]

This issue will be tracked as part of #131 discussion

[amazzini]

This issue has been closed due to the lack of activity for more than one year. Please reopen it if follow up is necessary.