SOL003_31: VnfInstance data type updated

            set to true, auto-healing is currently enabled. If set to false,

            auto-healing is currently disabled.

          These configurable properties can be initialized with default values

          from the VNFD (see note 4) or with values passed in the InstantiateVnfRequest

          structure (see clause 5.5.2.4).

          Configurable properties initialized with default values from the VNFD can be

          updated with values passed in the InstantiateVnfRequest structure.

          from the VNFD.

          Configurable properties can be modified with values passed in the request

          structures of certain LCM operations, such as the InstantiateVnfRequest 

          structure.

          Further, these configurable properties can be created, modified or

          deleted with the PATCH method.

          NOTE: Upon creation of the VnfInstance structure, the VNFM shall create and initialize all child attributes 

          of "vnfConfigurableProperties", "metadata" and "extensions" that were declared in the VNFD with a defined

          initial value. The defined initial values can be declared in the VNFD, and/or, in case of "metadata", 

          obtained from the "CreateVnfRequest" structure. Child attributes of "vnfConfigurableProperties", "metadata" 

          and "extensions" that have no defineddeclared initial value shall not be created, in order to be consistent 

          with the semantics of the JSON Merge Patch method (see IETF RFC 7396) that interprets null values as deletion 

          request.

        $ref: "../../../definitions/SOL002SOL003_def.yaml#/definitions/KeyValuePairs"

      vimConnectionInfo:

        description: >

              $ref: "../../../definitions/SOL002SOL003VNFLifecycleManagement_def.yaml#/definitions/ExtVirtualLinkInfo"

          extManagedVirtualLinkInfo:

            description: >

              External virtual links the VNF instance is connected to.

              Information about the externally-managed internal VLs of the VNF instance.

              NOTE: It is possible to have several ExtManagedVirtualLinkInfo for the same 

              VNF internal VL in case of a multi-site VNF spanning several VIMs. The set of 

              ExtManagedVirtualLinkInfo corresponding to the same VNF internal VL shall indicate 

              so by referencing to the same VnfVirtualLinkDesc and externally-managed multi-site 

              VL instance (refer to clause 5.5.3.3).

            type: array

            items:

              $ref: "../../../definitions/SOL002SOL003VNFLifecycleManagement_def.yaml#/definitions/ExtManagedVirtualLinkInfo"

          The declaration of metadata in the VNFD can optionally contain the specification of initial values.

          The VNFM shall accept requests to write metadata that are not declared in the VNFD.

          These attributes can be initialized with default values from the VNFD or with values

          passed in the CreateVnfRequest structure (see clause 5.5.2.3).

          passed in the CreateVnfRequest structure (see clause 5.4.2.3.1).

          This attributeThese attributes can be created, modified or removed with the PATCH method.

          ETSI GS NFV-SOL 001 specifies the structure and format of the VNFD based on TOSCA specifications.

          Modifying the values of these attributes has no direct effect on the VNF instance; however, the modified

          attribute values can be considered during subsequent VNF lifecycle management operations, which means that

          the modified values can indirectly affect the configuration of the VNF instance.

          These attributes can be initialized with default values from the VNFD or with values passed in the

          InstantiateVnfRequest structure (see clause 5.5.2.4).

          Attributes initialized with default values from the VNFD can be updated with values passed in the

          InstantiateVnfRequest structure.

          These attributes can be initialized with default values from the VNFD.

          These attributes can be modified with values passed in the request structures of certain LCM operations, 

          such as the InstantiateVnfRequest structure.

          Further, these attributes can be created, modified or deleted with the PATCH method.

          Upon creation of the VnfInstance structure, the VNFM shall create and initialize all child attributes

          of "vnfConfigurableProperties", "metadata" and "extensions" that were declared in the VNFD with

          a defined initial value. Child attributes of "vnfConfigurableProperties", "metadata" and "extensions"

          that have no declared initial value shall not be created, in order to be consistent with the semantics

          of the JSON Merge Patch method (see IETF RFC 7396) that interprets null values as deletion request.

        $ref: "../../../definitions/SOL002SOL003_def.yaml#/definitions/KeyValuePairs"

          NOTE: Upon creation of the VnfInstance structure, the VNFM shall create and initialize all child attributes 

          of "vnfConfigurableProperties", "metadata" and "extensions" that were declared in the VNFD with a defined

          initial value. The defined initial values can be declared in the VNFD, and/or, in case of "metadata", 

          obtained from the "CreateVnfRequest" structure. Child attributes of "vnfConfigurableProperties", "metadata" 

          and "extensions" that have no defineddeclared initial value shall not be created, in order to be consistent 

          with the semantics of the JSON Merge Patch method (see IETF RFC 7396) that interprets null values as deletion 

          request.

      _links:

        description: >

          Links to resources related to this resource.