Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in
  • S SOL005
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 5
    • Issues 5
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Container Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • NFV - Network Functions VirtualisationNFV - Network Functions Virtualisation
  • SOL005
  • Issues
  • #1
Closed
Open
Issue created Aug 21, 2020 by banerjeesu@banerjeesuDeveloper

Swagger file: SOL005NSLifecycleManagement_def.yaml; ns_lcm_op_occ: "statusEnteredTime" should be "stateEnteredTime" to match vnf_lcm_op_occ

The file https://forge.etsi.org/rep/nfv/SOL005/blob/v2.7.1/src/SOL005/NSLifecycleManagement/definitions/SOL005NSLifecycleManagement_def.yaml NsLcmOpOcc has "statusEnteredTime" misspelt.

It should ideally be "stateEnteredTime" to match the corresponding field in VnfLcmOpOcc: https://forge.etsi.org/rep/nfv/SOL002-SOL003/blob/v2.7.1/src/definitions/SOL002SOL003VNFLifecycleManagement_def.yaml

Reference: Attached screenshot from 2.7.1 SOL005 Spec.

The description against 'statusEnteredTime' says, "Date-time when the current state has been entered." Please see that it's referred to as "state" in the descriptions and other field names from NsLcmOpOcc as well, e.g. {'operationState'}. Apart from the specification language aspect, we have the below challenge from implementation and client side.

The dissimilarity of the names in SOL005 and corresponding SOL003/SOL002 model attributes may pose limitations when it comes to client-side/server-side code trying to use the JSON-Object-mapping tools (e.g. ObjectMapper) for invoking/serving APIs across NS and VNF LCM operations. The ObjectMappers need to have field transformation logic (to-and-fro) to map "statusEnteredTime" to "stateEnteredTime" and back while moving between the SOL003 and SOL005 APIs for instance.

Screen_Shot_2020-08-21_at_11.43.35_AM

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking