X-Git-Url: https://osm.etsi.org/gitweb/?p=osm%2FIM.git;a=blobdiff_plain;f=models%2Faugments%2Fcommon-augments.yang;h=0467bc2f2921a9d8dd6020f7ba7443e5bdc9da98;hp=912199c22cedc1aed47baa128875051d51dc57ca;hb=HEAD;hpb=b163567ec3c2b5645f4eebefe0e4bf66af3d0a4c diff --git a/models/augments/common-augments.yang b/models/augments/common-augments.yang index 912199c..18481a9 100644 --- a/models/augments/common-augments.yang +++ b/models/augments/common-augments.yang @@ -20,6 +20,13 @@ module common-augments { namespace "urn:etsi:osm:yang:augments"; prefix "common"; + import etsi-nfv-vnfd { + prefix vnfd; + } + import etsi-nfv-nsd { + prefix nsd; + } + typedef parameter-data-type { type enumeration { enum STRING; @@ -102,10 +109,79 @@ module common-augments { } } - grouping vnfc-relations { + grouping relations-ee { + description + "Information about the execution environment and endpoint for a relation. + The execution environment can be associated to different objects: kdu, vdu, vnf, or ns. + To select the object, the profile-id of the object might be needed: + Reference to a kdu-level execution enviroment: + in the VNFd: the kdu-resource-profile-id is needed. + in the NSd: the kdu-resource-profile-id and vnf-profile-id are needed. + Reference to a vdu-level execution enviroment: + in the VNFd: the vdu-profile-id is needed. + in the NSd: the vdu-profile-id and vnf-profile-id are needed. + Reference to a vnf-level execution enviroment: + in the VNFd: nothing is needed, implicit. + in the NSd: the vnf-profile-id is needed. + Reference to an ns-level execution enviroment: + in the VNFd: cannot be done. + in the NSd: nothing is needed, implicit. + The reference to the execution environment is only mandatory if there is more than one execution environment + in the execution-environment-list of an object. + The endpoint is always needed"; + + leaf vdu-profile-id { + description + "If the execution environment is associated to a vdu object, + this parameter is the reference to the vdu-profile id."; + type leafref { + path "/vnfd:vnfd/vnfd:df/vnfd:vdu-profile/vnfd:id"; + } + } + + leaf kdu-resource-profile-id { + description + "If the execution environment is associated to a kdu resource object, + this parameter is the reference to the kdu-resource-profile id."; + type string; + } + + leaf vnf-profile-id { + description + "If the execution environment is associated to a vnf object, + this parameter is the reference to the vnf-profile id. + Only valid in the NSd. The value is implicit in a VNFd. + To reference an execution environment associated to a vnf object + from the VNFd, none of the profile ids need to be specified."; + type leafref { + path "/nsd:nsd/nsd:nsd/nsd:df/nsd:vnf-profile/nsd:id"; + } + } + leaf execution-environment-ref { + description + "Optional reference to the execution environment id. + Only needed if there is more than one execution environment + in the execution-environment-list of an object."; + type string; + default ""; + } + leaf endpoint { + description + "Endpoint name of the execution environment."; + type string; + } + } + + grouping relations { list relation { description - "List of relations between elements in this descriptor."; + "List of relations between elements in this descriptor. + The relations are used to integrate pairs of execution environments, + that are in charge of the configuration and lifecycle management + of VDUs, VNFs, KDUs, or NSs. + Each relation is formed by a provider and a requirer. + The provider is the execution environment that provides a particular service. + The requirer is the execution environment that requires the service provided by the provider"; key "name"; leaf name { @@ -114,10 +190,20 @@ module common-augments { type string; } - + container provider { + description + "Execution environment that offers an endpoint for a particular service"; + uses relations-ee; + } + container requirer { + description + "Execution environment that uses the service provided by the provider"; + uses relations-ee; + } list entities { description - "List of two elements to be related. + "DEPRECATION NOTICE: use provider and requirer instead. + List of two elements to be related. Elements to be related are identified by a pair (id, endpoint). The relation will relate (id1, endpoint1) to (id2, endpoint2)."; key "id"; @@ -136,6 +222,9 @@ module common-augments { type string; } } + must 'not(entities) or (not(provider) and not(requirer))' { + error-message 'Cannot set both "entities" and "provider/requirer" fields.'; + } } } @@ -259,7 +348,6 @@ module common-augments { description "Helm version to use for this helm-chart, v3 by default"; type enumeration { - enum "v2"; enum "v3"; } default "v3"; @@ -474,6 +562,7 @@ module common-augments { enum GT; // greater than enum LT; // less than enum EQ; // equal + enum NE; // not equal } } @@ -636,6 +725,34 @@ module common-augments { } } + grouping vdu-storage-requirements { + list vdu-storage-requirements { + description + "Array of key-value pairs that articulate the storage + deployment requirements. + + If the storage type is persistent-storage, the following setting + holds the persistent volume upon VM deletion: + key: keep-volume + value: true + + If storage volume can be attached to several VMs, the following setting + will allow it: + key: multiattach + value: true"; + + key "key"; + + leaf key { + type string; + } + + leaf value { + type string; + } + } + } + typedef scaling-trigger { type enumeration { enum pre-scale-in {