Commit 49e1524e authored by piscione's avatar piscione
Browse files

SOL005_32: added attributes and notes to VnfLinkPortInfo datamodel

parent 6a85f23a

src/SOL005/NSLifecycleManagement/definitions/SOL005NSLifecycleManagement_def.yaml

+28 −0
Original line number Diff line number Diff line
@@ -1516,6 +1516,11 @@ definitions: 
          (i.e. VNFC CP) instance.

          The value refers to an "extCpInfo" item in the VnfInstance or a

          "vnfcCpInfo" item of a "vnfcResouceInfo" item in the VnfInstance.

          Either cpInstanceId with cpInstanceType set to "EXT_CP" or any combination

          of cpInstanceId with cpInstanceType set to "VNFC_CP" and vipCpInstanceId

          (i.e. one or both of them) shall be present for a VnfLinkPortInfo. In case

          both cpInstanceId with cpInstanceType set to "VNFC_CP" and vipCpInstanceId

          are present, the two different CP instances share the linkport.

        $ref: "#/definitions/IdentifierInVnf"

      cpInstanceType:

        description: >
@@ -1525,10 +1530,33 @@ definitions: 
          Permitted values:

          * VNFC_CP: The link port is connected to a VNFC CP

          * EXT_CP: The link port is associated to an external CP.

          Either cpInstanceId with cpInstanceType set to "EXT_CP" or any combination

          of cpInstanceId with cpInstanceType set to "VNFC_CP" and vipCpInstanceId

          (i.e. one or both of them) shall be present for a VnfLinkPortInfo. In case

          both cpInstanceId with cpInstanceType set to "VNFC_CP" and vipCpInstanceId

          are present, the two different CP instances share the linkport.

        type: string

        enum:

          - VNFC_CP

          - EXT_CP

      vipCpInstanceId:

        description: >

          VIP CP instance of the VNF connected to this link port. May be present.

          Either cpInstanceId with cpInstanceType set to "EXT_CP" or any combination of cpInstanceId with

          cpInstanceType set to "VNFC_CP" and vipCpInstanceId (i.e. one or both of them) shall be present

          for a VnfLinkPortInfo. In case both cpInstanceId with cpInstanceType set to "VNFC_CP" and vipCpInstanceId

          are present, the two different CP instances share the linkport.

          Annex A.4 of ETSI GS NFV-IFA 007 [19] provides examples for configurations where both vipCpInstanceId

          and vnfcCpInstanceId are present (UC#5 and UC#5-b), only vnfcCpInstanceId is present (UC#2), or only

          vipCpInstanceId is present (UC#6 and UC#6-b).

        $ref: "#/definitions/IdentifierInVnf"

      trunkResourceId:

        description: >

          Identifier of the trunk resource in the VIM.

          Shall be present if the present link port corresponds to the parent port that the trunk resource

          is associated with.

          The value of "trunkResourceId" is scoped by the value of "vimConnectionId" in the "resourceHandle" attribute.

        $ref: "#/definitions/IdentifierInVim"



  MonitoringParameter:

    type: object