Uploaded image for project: 'Logging analytics'
  1. Logging analytics
  2. LOG-462

Post Orchestration Audit - Update SDN-C Context Builder to latest API

XMLWordPrintable

      As an Ops person I would like POMBA to extract additional attributes from SDN-C as defined in the updated Context Builder API.  This is to support addition of data auditing with new Context Builders such as Network Discovery. 

       The latest API is defined

        https://wiki.onap.org/display/DW/POMBA+Context+Builder+Swagger

      The SDNC Context Builder expects serviceInstanceId. It does not accept modelVersionId or modelInvariantId.

       

      This API shall be versioned, as per ONAP versioning strategy. In addition, a URL without the version number embedded in it shall return the latest version.

      The set of fields that are already reported in Network Discovery MUST be supported, but additional fields MAY also be supported so long as the appropriate value is defined for the attribute name in the common model.

      The specific set of fields are

      VNFInstance.vf-module[x].List of vservers
      VNFInstance.vf-module[x].vserver[x].id
      VNFInstance.vf-module[x].vserver[x].name
      VNFInstance.vf-module[x].vserver[x].inMaint
      VNFInstance.vf-module[x].vserver[x].pserver.hostname
      VNFInstance.vf-module[x].vserver[x].image.image-name
      VNFInstance.vf-module[x].vserver[x].prov-status

      and

      Service.List of networks
      Network.id
      Network.name
      Network.isShared
      Network.uuid
      Network.invariantUUID

      Background Information

      With the addition of the Network Discovery context builder, additional attributes will need to be added to the SDNC context so that it can be compared in Validation to the context from ND Context Builder.  The mapping of the ND data can be found at https://wiki.onap.org/display/DW/Context+Builders+Mapping+to+Common+Model.

      Note that for SDN-C, some investigation will be required to establish which of the new ND fields are available and how to map to them.

      Value

      Enables audit of additional information and supports API versioning as necessary

      Success Criteria

       • Compliant to the ask above
      • Support for all ONAP best practices (logging, sonar coverage, etc)
      • Code checked in, use documented on Wiki
      • Demo to working group

      Exclusions

      • Supporting the initial, prototype version of the API as an accessible version. We may wish to call this version 0 for reference though.

            dstangl dstangl
            dkedrosk dkedrosk
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: