VimConnectionInfo

VimConnectionInfo

This type represents parameters to connect to a VIM for managing the resources of a VNF instance. This structure is used to convey VIM-related parameters over the Or-Vnfm interface. Additional parameters for a VIM may be configured into the VNFM by means outside the scope of the present document, and bound to the identifier of that VIM.

JSON Example

{
    "vimType": "vimType",
    "vimId": "vimId",
    "extra": {
        "deploymentProfileId": "deploymentProfileId",
        "nodePoolId": "nodePoolId",
        "vimName": "vimName",
        "nodeProfileName": "nodeProfileName",
        "nodePoolName": "nodePoolName"
    },
    "interfaceInfo": "{}",
    "id": "id",
    "accessInfo": "{}"
}

string

id

Required

An identifier with the intention of being globally unique.

string

vimId

Optional

An identifier with the intention of being globally unique.

string

vimType

Required

Discriminator for the different types of the VIM information. The value of this attribute determines the structure of the "interfaceInfo" and "accessInfo" attributes, based on the type of the VIM. The set of permitted values is expected to change over time as new types or versions of VIMs become available. The ETSI NFV registry of VIM-related information provides access to information about VimConnectionInfo definitions for various VIM types. The structure of the registry is defined in Annex C of SOL003.

object

interfaceInfo

Optional

This type represents a list of key-value pairs. The order of the pairs in the list is not significant. In JSON, a set of keyvalue pairs is represented as an object. It shall comply with the provisions defined in clause 4 of IETF RFC 8259. In the following example, a list of key-value pairs with four keys ("aString", "aNumber", "anArray" and "anObject") is provided to illustrate that the values associated with different keys can be of different type.

object

accessInfo

Optional

This type represents a list of key-value pairs. The order of the pairs in the list is not significant. In JSON, a set of keyvalue pairs is represented as an object. It shall comply with the provisions defined in clause 4 of IETF RFC 8259. In the following example, a list of key-value pairs with four keys ("aString", "aNumber", "anArray" and "anObject") is provided to illustrate that the values associated with different keys can be of different type.

vimConnectionInfoExtras

extra

Optional

extra

Property Of

InstantiateVnfRequest

VnfInstance