Action-Identifier to support vf-module-id
As of now LCM Request Identifier supports
vnf-id, vnfc-name and vserver-id. This change
supports vf-module-id as action identifier
and its value is set in DG context with key
input.action-identifiers.vf-module-id when
invoking DG
Issue-Id : APPC-142
Change-Id: I65d44b073d32e39eaba183b8ce47584441921f3c
Signed-off-by: Kalpesh Chaniyara <kalpeshkumar.chaniyara@amdocs.com>
diff --git a/appc-provider/appc-provider-model/src/main/yang/appc-provider-lcm.yang b/appc-provider/appc-provider-model/src/main/yang/appc-provider-lcm.yang
index b149abe..d72b551 100644
--- a/appc-provider/appc-provider-model/src/main/yang/appc-provider-lcm.yang
+++ b/appc-provider/appc-provider-model/src/main/yang/appc-provider-lcm.yang
@@ -269,6 +269,11 @@
type string;
mandatory false;
}
+ leaf vf-module-id {
+ description "identifies the VF module to which this action is to be applied.";
+ type string;
+ mandatory false;
+ }
leaf vnfc-name {
description "identifies the VNFC to which this action is to be applied. Some
actions apply only to a component within a VNF (e.g. RESTART is