Loading src/SOL002/VNFLifecycleManagementNotification/definitions/SOL002VNFLifecycleManagementNotification_def.yaml +2 −35 Original line number Diff line number Diff line Loading @@ -182,7 +182,7 @@ definitions: management operation occurrence. type: array items: $ref: "SOL002VNFLifecycleManagementNotification_def.yaml#/definitions/AffectedVirtualCp" $ref: "../../../definitions/SOL002SOL003VNFLifecycleManagement_def.yaml#/definitions/AffectedVirtualCp" changedExtConnectivity: description: > Information about changed external connectivity, if this Loading Loading @@ -212,36 +212,3 @@ definitions: description: > Links to resources related to this notification. $ref: "../../../definitions/SOL002SOL003VNFLifecycleManagement_def.yaml#/definitions/LccnLinks" No newline at end of file AffectedVirtualCp: description: > This type provides information about added, deleted and modified virtual CP instances. type: object required: - cpInstanceId - cpdId - changeType properties: cpInstanceId: description: > dentifier of the virtual CP instance and the related "VirtualCpInfo" structure in "VnfInstance". $ref: "../../../definitions/SOL002SOL003_def.yaml#/definitions/IdentifierInVnf" cpdId: description: > Identifier of the VirtualCpd in the VNFD. $ref: "../../../definitions/SOL002SOL003_def.yaml#/definitions/IdentifierInVnfd" vnfdId: description: > Reference to the VNFD. Shall be present in case of a "change current VNF Package" to identify whether the affected virtual CP instance is associated to a VirtualCpd which is referred from the source or destination VNFD. $ref: "../../../definitions/SOL002SOL003_def.yaml#/definitions/Identifier" changeType: description: > Signals the type of change. type: string enum: - ADDED - REMOVED - MODIFIED No newline at end of file src/definitions/SOL002SOL003VNFLifecycleManagement_def.yaml +117 −0 Original line number Diff line number Diff line Loading @@ -1110,3 +1110,120 @@ definitions: type: array items: $ref: "SOL002SOL003_def.yaml#/definitions/KeyValuePairs" AffectedVirtualCp: description: > This type provides information about added, deleted and modified virtual CP instances. type: object required: - cpInstanceId - cpdId - changeType properties: cpInstanceId: description: > dentifier of the virtual CP instance and the related "VirtualCpInfo" structure in "VnfInstance". $ref: "SOL002SOL003_def.yaml#/definitions/IdentifierInVnf" cpdId: description: > Identifier of the VirtualCpd in the VNFD. $ref: "SOL002SOL003_def.yaml#/definitions/IdentifierInVnfd" vnfdId: description: > Reference to the VNFD. Shall be present in case of a "change current VNF Package" to identify whether the affected virtual CP instance is associated to a VirtualCpd which is referred from the source or destination VNFD. $ref: "SOL002SOL003_def.yaml#/definitions/Identifier" changeType: description: > Signals the type of change. type: string enum: - ADDED - REMOVED - MODIFIED McioInfo: description: > This type provides information about an MCIO representing the set of VNFC instances realized by one or a set of OS containers which have been created based on the same VDU. Within the CISM, an MCIO controller monitors the actual state of an MCIO representing the set of VNFC instances realized by one or a set of OS containers and compare it to the desired state as specified in the respective declarative descriptor. It triggers actions toward the CIS to align the actual to the desired state. Monitoring the actual state includes monitoring the number of MCIO instances available at any specific point in time. In addition, an MCIO controller maintains properties and runtime information on the MCIO instances which have been created based on the same VDU. The McioInfo data structure provides the runtime information on the MCIOs obtained from the MCIO controller. NOTE: There are different types of MCIOs. The set of VNFC instances based on the same VDU is represented by one MCIO, e.g. of type Deployment. Each individual VNFC instance is represented by another type of MCIO, e.g. a POD. Runtime information of the set of OS containers realizing an individual VNFC instance is not part of the McioInfo data structure; such runtime information is provided in the ResourceHandle data structure referenced from the VnfcResourceInfo. The McioInfo does not provide runtime information of a constituent VNFC instance created based on a specific VDU. NOTE 1: The type of MCIO as specified in the declarative descriptor of the MCIO, and that can be read from the CISM. EXAMPLE: In case of MCIOs managed by Kubernetes®, the type of MCIO corresponds to the “kind” property of the declarative descriptor. NOTE 2: If the attribute additionalInfo is present, it may contain runtime information on the actual and desired state of the MCIO(s). NOTE 3: When the container infrastructure service is a Kubernetes® instance, the mcioId is the combined values from the kind and name fields of the Kubernetes resource object, separated by a slash. Example: "Deployment/abcd". NOTE 4: When the container infrastructure service is a Kubernetes® instance, the mcioName is the name field of the resource object. type: object required: - mcioId - mcioName - mcioNamespace - vduId - cismId - mcioType - desiredInstances - availableInstances properties: mcioId: description: > Identifier of this MCIO, created by the CISM. See note 3. $ref: "SOL002SOL003_def.yaml#/definitions/Identifier" mcioName: description: > Human readable name of this MCIO. See note 4. type: string mcioNamespace: description: > Namespace of this MCIO. type: string vduId: description: > Reference to the related VDU in the VNFD applicable to this resource. $ref: "SOL002SOL003_def.yaml#/definitions/IdentifierInVnfd" cismId: description: > Identifier of the CISM managing this MCIO. $ref: "SOL002SOL003_def.yaml#/definitions/Identifier" mcioType: description: > The type of MCIO. Specific values, their semantics and associated MCIO types are defined in clause 5.5.4.9. Additional values are also permitted. See note 1. type: string desiredInstances: description: > Number of desired MCIO instances. type: integer availableInstances: description: > Number of available MCIO instances. type: integer additionalInfo: decription: > Additional information which is specific to the MCIO, its type, and which is available from the CISM. See note 2. $ref: "SOL002SOL003_def.yaml#/definitions/KeyValuePairs" No newline at end of file Loading
src/SOL002/VNFLifecycleManagementNotification/definitions/SOL002VNFLifecycleManagementNotification_def.yaml +2 −35 Original line number Diff line number Diff line Loading @@ -182,7 +182,7 @@ definitions: management operation occurrence. type: array items: $ref: "SOL002VNFLifecycleManagementNotification_def.yaml#/definitions/AffectedVirtualCp" $ref: "../../../definitions/SOL002SOL003VNFLifecycleManagement_def.yaml#/definitions/AffectedVirtualCp" changedExtConnectivity: description: > Information about changed external connectivity, if this Loading Loading @@ -212,36 +212,3 @@ definitions: description: > Links to resources related to this notification. $ref: "../../../definitions/SOL002SOL003VNFLifecycleManagement_def.yaml#/definitions/LccnLinks" No newline at end of file AffectedVirtualCp: description: > This type provides information about added, deleted and modified virtual CP instances. type: object required: - cpInstanceId - cpdId - changeType properties: cpInstanceId: description: > dentifier of the virtual CP instance and the related "VirtualCpInfo" structure in "VnfInstance". $ref: "../../../definitions/SOL002SOL003_def.yaml#/definitions/IdentifierInVnf" cpdId: description: > Identifier of the VirtualCpd in the VNFD. $ref: "../../../definitions/SOL002SOL003_def.yaml#/definitions/IdentifierInVnfd" vnfdId: description: > Reference to the VNFD. Shall be present in case of a "change current VNF Package" to identify whether the affected virtual CP instance is associated to a VirtualCpd which is referred from the source or destination VNFD. $ref: "../../../definitions/SOL002SOL003_def.yaml#/definitions/Identifier" changeType: description: > Signals the type of change. type: string enum: - ADDED - REMOVED - MODIFIED No newline at end of file
src/definitions/SOL002SOL003VNFLifecycleManagement_def.yaml +117 −0 Original line number Diff line number Diff line Loading @@ -1110,3 +1110,120 @@ definitions: type: array items: $ref: "SOL002SOL003_def.yaml#/definitions/KeyValuePairs" AffectedVirtualCp: description: > This type provides information about added, deleted and modified virtual CP instances. type: object required: - cpInstanceId - cpdId - changeType properties: cpInstanceId: description: > dentifier of the virtual CP instance and the related "VirtualCpInfo" structure in "VnfInstance". $ref: "SOL002SOL003_def.yaml#/definitions/IdentifierInVnf" cpdId: description: > Identifier of the VirtualCpd in the VNFD. $ref: "SOL002SOL003_def.yaml#/definitions/IdentifierInVnfd" vnfdId: description: > Reference to the VNFD. Shall be present in case of a "change current VNF Package" to identify whether the affected virtual CP instance is associated to a VirtualCpd which is referred from the source or destination VNFD. $ref: "SOL002SOL003_def.yaml#/definitions/Identifier" changeType: description: > Signals the type of change. type: string enum: - ADDED - REMOVED - MODIFIED McioInfo: description: > This type provides information about an MCIO representing the set of VNFC instances realized by one or a set of OS containers which have been created based on the same VDU. Within the CISM, an MCIO controller monitors the actual state of an MCIO representing the set of VNFC instances realized by one or a set of OS containers and compare it to the desired state as specified in the respective declarative descriptor. It triggers actions toward the CIS to align the actual to the desired state. Monitoring the actual state includes monitoring the number of MCIO instances available at any specific point in time. In addition, an MCIO controller maintains properties and runtime information on the MCIO instances which have been created based on the same VDU. The McioInfo data structure provides the runtime information on the MCIOs obtained from the MCIO controller. NOTE: There are different types of MCIOs. The set of VNFC instances based on the same VDU is represented by one MCIO, e.g. of type Deployment. Each individual VNFC instance is represented by another type of MCIO, e.g. a POD. Runtime information of the set of OS containers realizing an individual VNFC instance is not part of the McioInfo data structure; such runtime information is provided in the ResourceHandle data structure referenced from the VnfcResourceInfo. The McioInfo does not provide runtime information of a constituent VNFC instance created based on a specific VDU. NOTE 1: The type of MCIO as specified in the declarative descriptor of the MCIO, and that can be read from the CISM. EXAMPLE: In case of MCIOs managed by Kubernetes®, the type of MCIO corresponds to the “kind” property of the declarative descriptor. NOTE 2: If the attribute additionalInfo is present, it may contain runtime information on the actual and desired state of the MCIO(s). NOTE 3: When the container infrastructure service is a Kubernetes® instance, the mcioId is the combined values from the kind and name fields of the Kubernetes resource object, separated by a slash. Example: "Deployment/abcd". NOTE 4: When the container infrastructure service is a Kubernetes® instance, the mcioName is the name field of the resource object. type: object required: - mcioId - mcioName - mcioNamespace - vduId - cismId - mcioType - desiredInstances - availableInstances properties: mcioId: description: > Identifier of this MCIO, created by the CISM. See note 3. $ref: "SOL002SOL003_def.yaml#/definitions/Identifier" mcioName: description: > Human readable name of this MCIO. See note 4. type: string mcioNamespace: description: > Namespace of this MCIO. type: string vduId: description: > Reference to the related VDU in the VNFD applicable to this resource. $ref: "SOL002SOL003_def.yaml#/definitions/IdentifierInVnfd" cismId: description: > Identifier of the CISM managing this MCIO. $ref: "SOL002SOL003_def.yaml#/definitions/Identifier" mcioType: description: > The type of MCIO. Specific values, their semantics and associated MCIO types are defined in clause 5.5.4.9. Additional values are also permitted. See note 1. type: string desiredInstances: description: > Number of desired MCIO instances. type: integer availableInstances: description: > Number of available MCIO instances. type: integer additionalInfo: decription: > Additional information which is specific to the MCIO, its type, and which is available from the CISM. See note 2. $ref: "SOL002SOL003_def.yaml#/definitions/KeyValuePairs" No newline at end of file
