Update SOL003 LCM, Performance Management, Fault Management, Indicator... (33cc960e) · Commits · NFV - Network Functions Virtualisation / SOL002-SOL003

src/SOL003/General_Definitions/SOL003_def.yaml

+61 −1

Original line number	Diff line number	Diff line
		@@ -15,6 +15,15 @@ definitions:
		Shall be an absolute URI (i.e. a UTI that contains {apiRoot}).
		$ref: "#/definitions/Uri"

		SupportedProtocolEnum:
		description: Supported protocol by CMF instance.
		type: string
		enum:
		- CMP
		- CMPv2
		- EST
		- SCEP

		NotificationLink:
		description: >
		This type represents a link to a resource in a notification, using an absolute or relative URI.
		@@ -363,6 +372,15 @@ definitions:
		different than the one that has used it before the operation, or by no external CP instance at all.
		Renaming a CPD identifier during the "changeCurrentVnfPkg" operation does not count as moving the related
		"cpConfig" map entries to a new "extCpData" structure.
		* NOTE 5: Subports need not be used for containerized VNFCs. The application container can send and receive IP
		packets with any VLAN tag as long as the network interface to connect to the secondary container cluster
		network has been configured appropriately. Thus, no individual cpConfig, except the one representing the
		trunk, need be modelled to allow traffic tagged with a particular VLAN through the connection point.
		* NOTE 6: In the case that the cloud native template included in the MCIOP describes the set of VNFC instances, for
		containerized VNFCs individual connection points need not be configured for each VNFC instance. It is only
		required to configure one cpConfig per cpdId, not per VNFC instance. The case of using, for a scalable VDU, a
		cloud native template in the MCIOP that describes one single VNFC instance is not specified in the present
		document version.
		type: object
		required:
		- cpdId
		@@ -378,7 +396,7 @@ definitions:
		The key of the map which identifies the individual VnfExtCpConfig entries is of type "IdentifierInVnf"
		and is managed by the NFVO.
		The entries shall be applied by the VNFM according to the rules of JSON Merge Patch (see IETF RFC 7396).
		See notes 2, 3 and 4.
		See notes 2, 3, 4, 5, 6.
		type: object
		additionalProperties:
		$ref: "#/definitions/VnfExtCpConfig"
		@@ -735,6 +753,39 @@ definitions:
		items:
		$ref: "#/definitions/NetAttDefResourceData"

		PaasServiceHandle:
		description: >
		This type provides information enabling the access and use of the PaaS
		Service by the VNF instance. The type and format of the handle depends on
		the form that the PaaS Service is formed. It shall comply with the
		provisions defined in table 4.4.1.19-1.
		type: object
		required:
		- id
		properties:
		id:
		description: >
		Identifier of this PaaS Service handle.
		$ref: "#/definitions/Identifier"
		interfaceInfo:
		description: >
		Information of the interface or interfaces to the PaaS Service
		instance, if applicable, such as the URI of an interface endpoint to
		communicate with the PaaS Service instance.
		$ref: "#/definitions/KeyValuePairs"
		accessInfo:
		description: >
		Authentication credentials for accessing the PaaS Service instance.
		If the PaasServiceHandle structure is part of an HTTP GET response
		payload body, sensitive attributes that are children of this
		attribute (such as passwords) shall not be included.
		$ref: "#/definitions/Identifier"
		extra:
		description: >
		PaaS Service instance-specific additional information. The applicable
		structure, and whether or not this attribute is available.
		$ref: "#/definitions/KeyValuePairs"

		ScaleInfo:
		description: >
		This type represents the scale level of a VNF instance related to a scaling aspect.
		@@ -817,6 +868,14 @@ definitions:
		An identifier with the intention of being globally unique.
		type: string

		ChangeTypeEnum:
		description: Signals the type of change.
		type: string
		enum:
		- ADD
		- REMOVE
		- MODIFY

		DateTime:
		description: >
		Date-time stamp.
		@@ -996,6 +1055,7 @@ definitions:
		CREATE_SNAPSHOT \| Represents the "Create VNF Snapshot" LCM operation.
		REVERT_TO_SNAPSHOT \| Represents the “Revert-To VNF Snapshot" LCM operation.
		CHANGE_VNFPKG \| Represents the "Change current VNF package" LCM operation.
		SELECT_DEPL_MODS \| Represents the “Select VNF deployable modules” LCM operation
		type: string
		enum:
		- INSTANTIATE

src/SOL003/VNFLifecycleManagement/VNFLifecycleManagement.yaml

+74 −0

Original line number	Diff line number	Diff line
		@@ -1244,6 +1244,36 @@ paths:
		504:
		$ref: "../../responses/SOL002SOL003_resp.yaml#/components/responses/504"

		/vnf_snapshots/{vnfSnapshotInfoId}/select_depl_mods:
		#SOL003 location: 5.4.26.2
		parameters:
		- $ref: ../../components/SOL003_params.yaml#/components/parameters/Accept
		- $ref: ../../components/SOL003_params.yaml#/components/parameters/Authorization
		- $ref: ../../components/SOL003_params.yaml#/components/parameters/Version
		post:
		description: \|
		The POST method requests to select deployable modules of a VNF instance and therefore to instantiate or terminate
		VNFC instances according to the selected deployable modules.
		The steps and conditions that apply as the result of successfully executing this method are specified in clause 5.4.1.2.
		requestBody:
		$ref: '#/components/requestBodies/SelectVnfDeployableModulesRequest'
		responses:
		202:
		$ref: '#/components/responses/selectdeployablemodules.Post.202'
		404:
		$ref: "../../responses/SOL002SOL003_resp.yaml#/components/responses/404"
		409:
		$ref: '#/components/responses/IndividualVnfInstance.Delete.409'
		400:
		$ref: "../../responses/SOL002SOL003_resp.yaml#/components/responses/400"
		401:
		$ref: "../../responses/SOL002SOL003_resp.yaml#/components/responses/401"
		403:
		$ref: "../../responses/SOL002SOL003_resp.yaml#/components/responses/403"
		405:
		$ref: "../../responses/SOL002SOL003_resp.yaml#/components/responses/405"
		406:
		$ref: "../../responses/SOL002SOL003_resp.yaml#/components/responses/406"
		components:
		parameters:
		filter_vnf_instances:
		@@ -1544,6 +1574,16 @@ components:
		$ref: "definitions/SOL003VNFLifecycleManagement_def.yaml#/definitions/RevertToVnfSnapshotRequest"
		required: true

		SelectVnfDeployableModulesRequest:
		description: \|
		This type represents request parameters for the "Select VNF deployable modules" operation. It shall comply with the
		provisions defined in table 5.5.2.27-1.
		content:
		application/json:
		schema:
		$ref: "definitions/SOL003VNFLifecycleManagement_def.yaml#/definitions/SelectVnfDeployableModulesRequest"
		required: true

		CreateVnfSnapshotInfoRequest:
		description: \|
		The VNF snapshot resource creation parameters, as defined in clause 5.5.2.20.
		@@ -2046,6 +2086,40 @@ components:
		schema:
		type: string

		selectdeployablemodules.Post.202:
		description: \|
		202 ACCEPTED

		Shall be returned when the request has been accepted for processing.
		The response body shall be empty.The HTTP response shall include a
		"Location" HTTP header that contains the URI of the newly-created "Individual
		VNF LCM operation occurrence" resource corresponding to the operation
		headers:
		Location:
		description: \|
		The resource URI of the created "Individual VNF LCM operation
		occurrence" resource.
		style: simple
		explode: false
		schema:
		type: string
		format: url
		WWW-Authenticate:
		description: \|
		Challenge if the corresponding HTTP request has not provided
		authorization, or error details if the corresponding HTTP request
		has provided an invalid authorization token.
		style: simple
		explode: false
		schema:
		type: string
		Version:
		description: The used API version.
		style: simple
		explode: false
		schema:
		type: string

		ScaleVnfInstance.Post.404:
		description: \|
		404 NOT FOUND

src/SOL003/VNFLifecycleManagement/definitions/SOL003VNFLifecycleManagement_def.yaml

+574 −21

File changed.

Preview size limit exceeded, changes collapsed.