Skip to content

NEP timeout parameter is not able to manage it, due to ONF limitation. #341

@latta-siae

Description

@latta-siae

NEP is leveraging ONF lib, js library onf-core-model-ap
https://www.npmjs.com/package/onf-core-model-ap

by the parameter "uuid": "nep-1-2-2-integer-p-003",

        {
          "uuid": "nep-1-2-2-integer-p-003",
          "profile-name": "integer-profile-1-0:PROFILE_NAME_TYPE_INTEGER_PROFILE",
          "integer-profile-1-0:integer-profile-pac": {
            "integer-profile-capability": {
              "integer-name": "responseTimeout",
              "purpose": "Timeout for receiving the response of the filtered ControlConstruct retrieval from the MWDI",
              "unit": "second",
              "minimum": 5,
              "maximum": 2000
            },
            "integer-profile-configuration": {
              "integer-value": 900
            }
          }
        },

This parameter will drive http requests to MWDI.
We found out that onf-core-model-ap doesn't support time out parameter, so then NEP is waiting http response without respect this parameter.

We try to do a workaround to emulate onf lib:
Branch: https://github.com/openBackhaul/NetExplorerProxy/tree/agamennone-siae/monkey-patch-timeout
Code implementation:

RestRequestBuilder.BuildAndTriggerRestRequest = async function (operationClientUuid, method, requestHeader, requestBody, params, timeout) {

This is temporary patch, but is working (not for production environment)

Request is to improve ONF lib to support this feature

Metadata

Metadata

Labels

enhancementNew feature or request

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions