Issue#1 - Clarify sequencing rules for LIfeCycleManagementScript events between external and internal (!55) · Merge requests · NFV - Network Functions Virtualisation / SOL006

src/yang/etsi-nfv-common.yang

+13 −0

Changes for src/yang/etsi-nfv-common.yang: 13 added lines, 0 removed lines.
Original line number	Diff line number	Diff line
		@@ -393,6 +393,19 @@ submodule etsi-nfv-common {
		}
		}

		typedef external-lifecycle-management-script-event {
		type enumeration {
		enum "instantiation";
		enum "scaling";
		enum "healing";
		enum "termination";
		enum "vnf-flavour-change";
		enum "vnf-operation-change";
		enum "vnf-ext-conn-change";
		enum "vnfinfo-modification";
		}
		}

		grouping local-affinity-or-anti-affinity-rule {
		list local-affinity-or-anti-affinity-rule {
		key "type scope";

+16 −1

Changes for src/yang/etsi-nfv-vnf.yang: 16 added lines, 1 removed line.
Original line number	Diff line number	Diff line
		@@ -2977,10 +2977,25 @@ submodule etsi-nfv-vnf {
		}

		leaf-list event {
		type union {
		type internal-lifecycle-management-script-event;
		type external-lifecycle-management-script-event;
		}
		description
		"Describes VNF lifecycle event(s) or an external stimulus
		detected on a VNFM reference point.";
		detected on a VNFM reference point.

		If the event is of type
		internal-lifecycle-management-script-event, then depending
		on whether the event is of type start-* or end-*, the
		script associated with the VNF LCM operation needs to be
		executed before the event, or after the event,
		respectively.

		On the other hand, if the event is of type
		external-lifecycle-management-script-event, then the
		script associated with the event needs to be executed
		for the given VNF LCM operation.";
		reference
		"GS NFV IFA011: Section 7.1.13 LifeCycleManagementScript
		information element";