"description":"'Type of the LCM operation state represented by this application instance LCM operation occurrence.'",
"examples":["STARTING"]
},
"OperationTypes":{
"title":"OperationTypes",
"enum":["INSTANTIATE","OPERATE","TERMINATE"],
@@ -2660,12 +2647,9 @@
"extendedResourceRequests":{
"type":"array",
"items":{
"type":"object",
"description":"An array of key-value pairs of extended resources required by the container see note.\n",
"additionalProperties":{
"type":"string"
}
}
"$ref":"#/components/schemas/KeyValuePairs"
},
"description":"An array of key-value pairs of extended resources required by the container see note."
},
"cpuResourceLimit":{
"type":"integer",
@@ -2792,10 +2776,9 @@
"vduStorageRequirements":{
"type":"array",
"items":{
"type":"object",
"description":"An array of key-value pairs that articulate the storage deployment requirements."
"$ref":"#/components/schemas/KeyValuePairs"
},
"description":"Array of key-value pair requirements on the storage for the VDU."
"description":"An array of key-value pairs that articulate the storage deployment requirements."
},
"rdmaEnabled":{
"type":"boolean",
@@ -2804,7 +2787,7 @@
"swImageDesc":{
"type":"object",
"$ref":"#/components/schemas/SwImageDesc",
"description":"References the software image to be loaded on the VirtualStorage resource createdbased on this VirtualStorageDesc. Shall be absent when used for virtual disks. See note."
"description":"References the software image to be loaded on the VirtualStorage resource created\nbased on this VirtualStorageDesc. Shall be absent when used for virtual disks. See note.\n"
}
}
},
@@ -2934,7 +2917,8 @@
}
}
},
"KeyValuePair":{
"KeyValuePairs":{
"description":"This data type represents a list of key-value pairs. The order of the pairs in the list is not\nsignificant. In JSON, a set of key-value pairs is represented as an object. It shall comply with\nthe provisions defined in clause 4 of IETF RFC 8259.\n",
"type":"object",
"properties":{
"key":{
@@ -2954,12 +2938,13 @@
"description":"Amount of virtual memory in MB."
},
"virtualMemOversubscriptionPolicy":{
"description":"The memory core oversubscription policy in terms of virtual memory to physical memory on the platform."
"type":"string",
"description":"The memory core oversubscription policy in terms of virtual memory to physical memory\non the platform. The cardinality can be 0 during the allocation request, if no particular\nvalue is requested.\n"
},
"vduMemRequirements":{
"type":"array",
"items":{
"$ref":"#/components/schemas/KeyValuePair"
"$ref":"#/components/schemas/KeyValuePairs"
},
"description":"Array of key-value pair requirements on the memory for the VDU."
},
@@ -2968,6 +2953,7 @@
"description":"Specifies the memory allocation to be cognisant of the relevant process/core allocation."
},
"hugePagesRequirements":{
"type":"string",
"description":"Specifies requirements on the huge pages resources for the virtual memory."
}
}
@@ -2995,13 +2981,11 @@
"vduCpuRequirements":{
"type":"array",
"items":{
"type":"object",
"$ref":"#/components/schemas/KeyValuePairs"
},
"description":"Array of key-value pair requirements on the Compute (CPU) for the VDU."
}
},
"virtualCpuPinning":{
"type":"object",
"description":"The virtual CPU pinning configuration for the virtualised compute resource. See clause 7.1.9.2.4.",
"description":"Geographic area. Shall be absent if the \"civicAddressElement\" attribute is present. The content of this attribute shall follow the provisions for the \"Polygon\" geometry object as defined in IETF RFC 7946 [8], for which the \"type\" member shall be set to the value \"Polygon\". See note."
}
},
@@ -3067,7 +3051,7 @@
"type":"object",
"properties":{
"hostId":{
"type":"object",
"$ref":"#/components/schemas/KeyValuePairs",
"description":"Deployment-specific information to identify a MEC host. See note."
},
"hostName":{
@@ -3075,7 +3059,7 @@
"description":"Human-readable name of MEC host."
}
},
"description":"NOTE: This information can be structured to cater for host identification schemes that are more complex than a simple identifier, e.g. when referring to the structure of an NFVI.\n"
"description":"NOTE: This information can be structured to cater for host identification schemes that are more \ncomplex than a simple identifier, e.g. when referring to the structure of an NFVI.\n"
},
"OperateAppRequest":{
"title":"OperateAppRequest",
@@ -3183,20 +3167,20 @@
"type":"object",
"properties":{
"accessInfo":{
"type":"object",
"description":"'This data type represents a list of key-value pairs. The order of the pairs in the list isnot significant. In JSON, a set of key-value pairs is represented as an object. It shall complywith the provisions defined in clause 4 of IETF RFC 8259'"
"$ref":"#/components/schemas/KeyValuePairs",
"description":"This data type represents a list of key-value pairs. The order of the pairs in the list is\nnot significant. In JSON, a set of key-value pairs is represented as an object. It shall comply\nwith the provisions defined in clause 4 of IETF RFC 8259.\n"
},
"extra":{
"type":"object",
"description":"'This data type represents a list of key-value pairs. The order of the pairs in the list is notsignificant. In JSON, a set of key-value pairs is represented as an object. It shall complywith the provisions defined in clause 4 of IETF RFC 8259'"
"$ref":"#/components/schemas/KeyValuePairs",
"description":"This data type represents a list of key-value pairs. The order of the pairs in the list is not\nsignificant. In JSON, a set of key-value pairs is represented as an object. It shall comply\nwith the provisions defined in clause 4 of IETF RFC 8259.\n"
},
"id":{
"type":"string",
"description":"The identifier of the VIM Connection. This identifier is managed by the MEO."
},
"interfaceInfo":{
"type":"object",
"description":"'This data type represents a list of key-value pairs. The order of the pairs in the list isnot significant. In JSON, a set of key-value pairs is represented as an object. It shallcomply with the provisions defined in clause 4 of IETF RFC 8259'"
"$ref":"#/components/schemas/KeyValuePairs",
"description":"This data type represents a list of key-value pairs. The order of the pairs in the list is\nnot significant. In JSON, a set of key-value pairs is represented as an object. It shall\ncomply with the provisions defined in clause 4 of IETF RFC 8259.\n"
},
"vimId":{
"type":"string",
@@ -3204,7 +3188,7 @@
},
"vimType":{
"type":"string",
"description":"Discriminator for the different types of the VIM information.The value of this attributedetermines the structure of the \"interfaceInfo\" and \"accessInfo\" attributes, based on the typeof the VIM.The set of permitted values is expected to change over time as new types or versionsof VIMs become available."
"description":"Discriminator for the different types of the VIM information.The value of this attribute\ndetermines the structure of the \"interfaceInfo\" and \"accessInfo\" attributes, based on the type\nof the VIM.The set of permitted values is expected to change over time as new types or versions\nof VIMs become available.\n"