Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • 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 2
    • Issues 2
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Container Registry
    • Infrastructure Registry
  • Analytics
    • Analytics
    • CI/CD
    • Repository
    • Value stream
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • NFV - Network Functions Virtualisation
  • SOL005
  • Issues
  • #12

Closed
Open
Created Jan 13, 2021 by brussev@brussevDeveloper

nsCpHandle attribute.

The nsCpHandle attribute with cardinality 0..1 in NsLinkPortInfo and VnffgInfo data types should have the yaml code generated as type “object” and not type “array” (as it is generated in the SOL005NSLifecycleManagement_def.yaml file of the SOL005 v2.7.1), because the cardinality 0..1 means that attribute is Optional and not an Array.

The NfpInfo data type also has the cpGroup attribute defined as items: $ref: "#/definitions/NsCpHandle" that should be items: $ref: "#/definitions/CpGroupInfo" as defined for NfpData.

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