Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in
  • S SOL006
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 10
    • Issues 10
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 1
    • Merge requests 1
  • 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
  • SOL006
  • Issues
  • #35
Closed
Open
Issue created Mar 17, 2021 by ramanathan@ramanathanDeveloper

NFVIFA(20)000201r1_IFA014ed341_fix_Sapd_attribute_associatedCpd

In the current GS, if a SAPD is re-exposing a CPD from a VNF, it is not possible to identify from which VNFD this CPD has to be extracted as two VNFDs may use the same CPDId for different purposes. Replacing associatedCpdId which references VnfExtCpd or PnfExtCpd or Sapd, by associatedCpd which includes CpdInConstituentElement removes the ambiguity. VnfExtCpd or PnfExtCpd or Sapd is referenced by constituentCpdId attribute of CpdInConstituentElement.

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