Commit 575f7b4f authored by Pietro Piscione's avatar Pietro Piscione
Browse files

SOL005_10 to SOL005_13 and SOL005_15

parent 4bb86476
Loading
Loading
Loading
Loading
Loading
+64 −5
Original line number Diff line number Diff line
@@ -119,6 +119,29 @@ definitions:
          the healing process, specific to the VNF being healed.
          EXAMPLE: Input parameters to VNF-specific healing procedures.
        $ref: "../../definitions/SOL005_def.yaml#/definitions/KeyValuePairs"
      healingResource:
        description: >
          Indicates the kinds of the virtual resource to be healed.
          Permitted values:
          - VL
          - LINKPORT
          - STORAGE
          - VIRTUALCP
          - COMPUTE
          - OSCONTAINER
          Default value is COMPUTE when the VDUs of the VNF are realized
          by a set of virtual machines and OSCONTAINER when the VDUs of
          the VNF are realized by a set of OS containers.
        type: array
        items:
          type: string
          enum:
            - VL
            - LINKPORT
            - STORAGE
            - VIRTUALCP
            - COMPUTE
            - OSCONTAINER

  TerminateNsRequest:
    description: >
@@ -1191,7 +1214,10 @@ definitions:

          In addition, the provisions in clause 6.7 shall apply.
        $ref: "../../definitions/SOL005_def.yaml#/definitions/KeyValuePairs"

      vnfmId:
        description: >
          Identifier of the VNFM that manages the VNF instance.
        $ref: "../../definitions/SOL005_def.yaml#/definitions/Identifier"

  VirtualCpInfo:
    description: > 
@@ -6620,14 +6646,14 @@ definitions:
      This type represents network address data for a virtual CP. 
      It shall comply with the provisions defined in table 6.5.3.12a-1.
      
      NOTE 1: If the container cluster is set up to be able to configure an external load balancer this address will be
              used, otherwise it will be ignored by the CISM.
      NOTE 1: The loadBalancerIp and the loadBalancerSourceRanges attributes are only used if the CIS cluster is set up to be 
              able to configure an external load balancer. Otherwise it shall be ignored.
      NOTE 2: In case the cluster can configure an external load balancer but no loadBalancerIp is provided the
              container cluster will assign an IP address.
      NOTE 3: The attribute is only relevant if the virtual CP is instantiated in a cluster that supports configuration of IP
              address pools for virtual CPs. Otherwise it shall be ignored. MetalLB is an example of a solution for
              Kubernetes® that supports configuration of address pools for load balancer services.
      NOTE 4: The loadBalancerIp and the addressPoolName attributes shall not be present at the same time.
      NOTE 4: The loadBalancerIp and the addressPoolName and the externalIp attributes shall not be present at the same time.

    type: object
    required:
@@ -6646,6 +6672,11 @@ definitions:
          Fixed address to assign to an external load balancer.
          See notes 1, 2 and 4.
        $ref: "#/definitions/IpAddress"
      externalIp:
        description: >
          An external IP address assigned to the virtual CP. 
          This IP address is not managed by CISM. See note 4.
        $ref: "#/definitions/IpAddress"
      addressPoolName:
        description: >
          Name of an address pool from which the
@@ -6654,6 +6685,22 @@ definitions:
        type: array
        items:
         type: string
      loadBalancerSourceRanges:
        description: >
          List of client IP address ranges allowed to access an external load balancer. See note 1.
        type: object
        required:
        - minAddress
        - maxAddress
        properties:
          minAddress:
            description: >
              Lowest IP address belonging to the range.
            $ref: "#/definitions/IpAddress"
          maxAddress:
            description: >
              Highest IP address belonging to the range.
            $ref: "#/definitions/IpAddress"



@@ -7451,6 +7498,8 @@ definitions:
              identifier.
      NOTE 2: Component mappings are defined in the VNFD in the source or destination package for the relevant change
              path. See clause 7.1.15.2 in ETSI GS NFV-IFA 011.
      NOTE 3: In the current version of the present document, only Rolling uprade and Blue-green upgrade types are supported. 
              The definition of additional upgrade types is left for future specification.
          
    type: object
    required:
@@ -7532,7 +7581,17 @@ definitions:
            instance in delegation mode. Otherwise shall not be
            present
          $ref: "#/definitions/CertificateConfigurationData"

      upgradeType: 
          description: >
            Indicates upgrade type when change the current VNF Package on which a VNF instance is based.
            Permitted values:
            • ROLLING_UPGRADE
            • BLUE_GREEN
            See note 3.
          type: string
          enum:
          - ROLLING_UPGRADE
          - BLUE_GREEN

  DeleteVnfSnapshotData:
    description: >