4 * Copyright 2016-2017 RIFT.IO Inc
6 * Licensed under the Apache License, Version 2.0 (the "License");
7 * you may not use this file except in compliance with the License.
8 * You may obtain a copy of the License at
10 * http://www.apache.org/licenses/LICENSE-2.0
12 * Unless required by applicable law or agreed to in writing, software
13 * distributed under the License is distributed on an "AS IS" BASIS,
14 * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
15 * See the License for the specific language governing permissions and
16 * limitations under the License.
23 namespace "urn:etsi:osm:yang:mano-types";
26 import ietf-inet-types {
36 "Update model to support projects.";
41 "Initial revision. This YANG file defines
42 the reusable base types for VNF Management
43 and Orchestration (MANO).";
45 "Derived from earlier versions of base YANG files";
48 typedef meta-data-type {
54 typedef package-type {
55 description "Type of descriptor being on-boarded";
62 typedef parameter-data-type {
70 grouping primitive-parameter-value {
73 "List of parameters to the configuration primitive.";
77 "Name of the parameter.";
83 "Data type associated with the value.";
84 type manotypes:parameter-data-type;
89 "Value associated with the name.";
95 grouping primitive-parameter {
98 "Name of the parameter.";
104 "Data type associated with the name.";
105 type manotypes:parameter-data-type;
109 description "Is this field mandatory";
115 description "The default value for this field";
119 leaf parameter-pool {
120 description "NSD parameter pool name to use for this parameter";
126 "The value should be dimmed by the UI.
127 Only applies to parameters with default values.";
134 "The value should be hidden by the UI.
135 Only applies to parameters with default values.";
141 grouping ui-primitive-group {
142 list parameter-group {
144 "Grouping of parameters which are logically grouped in UI";
149 "Name of the parameter group";
155 "List of parameters for the service primitive.";
157 uses manotypes:primitive-parameter;
161 description "Is this parameter group mandatory";
168 grouping event-config {
171 "Sequence number for the configuration primitive.";
177 "Name of the configuration primitive.";
182 leaf user-defined-script {
184 "A user defined script.";
195 description "Value of the configuration primitive.";
201 grouping image-properties {
204 "Image name for the software image.
205 If the image name is found within the VNF package it will
206 be uploaded to all VIM accounts during onboarding process.
207 Otherwise, the image must be added to the VIM account with
208 the same name as entered here.
213 leaf image-checksum {
215 "Image md5sum for the software image.
216 The md5sum, if provided, along with the image name uniquely
217 identifies an image uploaded to the CAL.
224 grouping vca-relations {
226 description "List of relations between elements in this descriptor.";
231 "Name of the relation.";
238 "List of two elements to be related.
239 Elements to be related are identified by a pair (id, endpoint).
240 The relation will relate (id1, endpoint1) to (id2, endpoint2).";
245 "A string, reference to the element id in the descriptor.
246 It could be a vnfd-id or a vdu-id in a VNFD,
247 or a nsd-id or member-vnf-index in a NSD.";
253 "Endpoint name defining the relation.";
260 grouping vca-metrics {
262 "Information about the VNF or VDU metrics";
264 description "List of VCA related metrics";
268 "Name of the metric, as defined in the Juju charm.";
271 leaf execution-environment-ref {
273 "Leaf reference to the particular execution environment getting that metric";
275 path "../../execution-environment-list/id";
278 leaf execution-environment-metric {
280 "Metric in the execution environment referenced by execution-environment-ref";
284 } // END - grouping vca-metrics
286 grouping configuration-method {
287 choice config-method {
289 "Defines the configuration method for the VNF or VDU.";
292 "Use custom script for configuring the VNF or VDU.
293 This script is executed in the context of
294 Orchestrator (The same system and environment
299 "Script type - currently supported - Scripts confirming to Rift CA plugin";
309 "Configure the VNF or VDU through Juju.";
312 description "Juju charm to use with the VNF or VDU.";
316 description "Is this a proxy charm?";
322 "Type of cloud where the charm will be deployed. It only
323 applies to proxy charms (not native)";
333 case execution-environment-list {
335 "List of Execution Environments to configure or monitor VNF or VDU.";
336 list execution-environment-list {
339 description "Execution environment identifier.";
342 choice execution-environment-model {
343 description "Execution environment model (juju, helm-chart)";
346 "Interact with the VNF or xDU through Juju.";
349 description "Juju charm to use with the VNF or VDU.";
353 description "Is this a proxy charm?";
359 "Type of cloud where the charm will be deployed. It only
360 applies to proxy charms (not native)";
371 "Interact with the VNF or xDU through Helm.";
374 "Helm chart that models the execution environment, in any of the following ways:
375 - <helm-repo>/<helm-chart>
376 - <helm-chart folder name under helm-charts folder in the package>
377 - <helm-chart tgz file (w/ or w/o extension) under helm-charts folder in the package>
378 - <URL_where_to_fetch_chart>
384 "Helm version to use for this helm-chart, v3 by default";
393 leaf metric-service {
395 "Service name in the execution environment. For helm charts, it will be
396 the name of the kubernetes service used by the exporter to expose metrics
397 to the OSM collector.
401 leaf connection-point-ref {
403 "String representing a leaf reference to the particular external connection point
404 This field should match /vnfd:vnfd-catalog/vnfd:vnfd/vnfd:id/vnfd:connection-point/vnfd:name
408 // path "/vnfd:vnfd-catalog/vnfd:vnfd/vnfd:id/vnfd:connection-point/vnfd:name";
417 grouping vca-config-access {
419 container config-access {
422 "Indicates the way to access to the xNF or xDU for VCA configuration.
423 For the moment there is a single way (ssh-access).";
425 container ssh-access {
428 "If the xNF requires ssh and this parameter is set, SSH keys
429 will be injected so that VCA can configure the xNF or xDU via ssh.";
432 description "whether ssh access is needed or not";
438 description "Default user for ssh";
443 } // END - grouping vca-config-access
445 grouping vca-configuration {
447 "Common information in the descriptors for NS, VNF or VDU configuration.
448 Note: If the NS contains multiple instances of the
449 same VNF or VDU, each instance could have a different
452 uses manotypes:configuration-method;
454 list config-primitive {
456 "List of config primitives supported by the
457 configuration agent for this VNF or VDU.";
462 "Name of the config primitive.";
466 leaf execution-environment-ref {
468 "Leaf reference to the particular execution environment";
470 path "../../execution-environment-list/id";
474 leaf execution-environment-primitive {
476 "Name of the primitive in the execution enviroment. If not explicit,
477 the leaf 'name' will be used as the name of the primitive.";
483 "List of parameters to the config primitive.";
485 uses primitive-parameter;
488 leaf user-defined-script {
490 "A user defined script. If user defined script is defined,
491 the script will be executed using bash";
496 list initial-config-primitive {
498 "Initial set of configuration primitives.";
502 "Sequence number for the configuration primitive.";
506 choice primitive-type {
507 case primitive-definition {
510 "Name of the configuration primitive in the execution environment.";
514 leaf execution-environment-ref {
516 "Leaf reference to the particular execution environment";
518 path "../../execution-environment-list/id";
522 uses primitive-parameter-value;
524 leaf user-defined-script {
526 "A user defined script.";
533 list terminate-config-primitive {
535 "Terminate set of configuration primitives.";
539 "Sequence number for the configuration primitive.";
544 "Name of the configuration primitive in the execution environment.";
548 leaf execution-environment-ref {
550 "Leaf reference to the particular execution environment";
552 path "../../execution-environment-list/id";
556 uses primitive-parameter-value;
558 leaf user-defined-script {
560 "A user defined script.";
564 uses manotypes:vca-metrics;
566 } // END - grouping vca-configuration
568 typedef virtual-link-type {
570 "Type of virtual link
571 ELAN: A multipoint service connecting a set of elements
572 ELINE: A point-to-point service connecting two elements
573 L3: A service providing either Layer-3 visibility (IP) between
574 VDUs/VNFs or explicit interconnection between two ELAN VLDs.";
575 // ETREE: A multipoint service connecting one or
576 // more roots and a set of leaves, but
577 // preventing inter-leaf communication.";
586 grouping named-value {
596 typedef http-method {
598 "Type of HTTP operation";
612 "Type of API to fetch monitoring parameters";
621 typedef json-query-method {
623 "The method to extract a value from a JSON response
625 NAMEKEY - Use the name as the key for a non-nested value.
626 JSONPATH - Use jsonpath-rw implementation to extract a value.
627 OBJECTPATH - Use objectpath implementation to extract a value.";
635 typedef param-value-type {
637 "The type of the parameter value";
645 typedef connection-point-type {
647 "Type of connection point
649 // VNIC_ADDR: Virtual NIC Address
650 // PNIC_ADDR: Physical NIC Address
651 // PPORT: Physical Port.";
658 typedef widget-type {
660 "Type of the widget, typically used by the UI.";
671 typedef cpu-feature-type {
673 "Enumeration for CPU features.
675 AES: CPU supports advanced instruction set for
676 AES (Advanced Encryption Standard).
678 CAT: Cache Allocation Technology (CAT) allows
679 an Operating System, Hypervisor, or similar
680 system management agent to specify the amount
681 of L3 cache (currently the last-level cache
682 in most server and client platforms) space an
683 application can fill (as a hint to hardware
684 functionality, certain features such as power
685 management may override CAT settings).
687 CMT: Cache Monitoring Technology (CMT) allows
688 an Operating System, Hypervisor, or similar
689 system management agent to determine the
690 usage of cache based on applications running
691 on the platform. The implementation is
692 directed at L3 cache monitoring (currently
693 the last-level cache in most server and
696 DDIO: Intel Data Direct I/O (DDIO) enables
697 Ethernet server NICs and controllers talk
698 directly to the processor cache without a
699 detour via system memory. This enumeration
700 specifies if the VM requires a DDIO
744 enum REQUIRE_CLFLUSH;
772 enum REQUIRE_PCLMULQDQ;
773 enum PREFER_PCLMULQDQ;
776 enum REQUIRE_MONITOR;
814 enum REQUIRE_TSC_DEADLINE_TIMER;
815 enum PREFER_TSC_DEADLINE_TIMER;
824 enum REQUIRE_FSGSBASE;
825 enum PREFER_FSGSBASE;
838 enum REQUIRE_INVPCID;
853 typedef nfvi-metric-type {
854 description "Type of NFVI metric to be monitored";
856 enum cpu_utilization;
857 enum average_memory_utilization;
860 enum disk_read_bytes;
861 enum disk_write_bytes;
863 enum packets_received;
864 enum packets_in_dropped;
865 enum packets_out_dropped;
869 typedef scaling-trigger {
880 enum post-scale-out {
886 typedef scaling-policy-type {
897 typedef scaling-criteria-operation {
909 container vm-flavor {
912 "Number of VCPUs for the VM.";
918 "Amount of memory in MB.";
924 "Amount of disk space in GB.";
928 } //grouping vm-flavor
930 grouping vm-flavor-name {
931 leaf vm-flavor-name {
932 description "flavor name to be used while creating vm using cloud account";
937 grouping vswitch-epa {
938 container vswitch-epa {
939 leaf ovs-acceleration {
941 "Specifies Open vSwitch acceleration mode.
942 MANDATORY: OVS acceleration is required
943 PREFERRED: OVS acceleration is preferred";
953 "Specifies Open vSwitch hardware offload mode.
954 MANDATORY: OVS offload is required
955 PREFERRED: OVS offload is preferred";
965 grouping hypervisor-epa {
966 container hypervisor-epa {
969 "Specifies the type of hypervisor.
985 description "Specifies the host level EPA attributes.";
988 "Host CPU model. Examples include: SandyBridge,
991 enum PREFER_WESTMERE;
992 enum REQUIRE_WESTMERE;
993 enum PREFER_SANDYBRIDGE;
994 enum REQUIRE_SANDYBRIDGE;
995 enum PREFER_IVYBRIDGE;
996 enum REQUIRE_IVYBRIDGE;
998 enum REQUIRE_HASWELL;
999 enum PREFER_BROADWELL;
1000 enum REQUIRE_BROADWELL;
1001 enum PREFER_NEHALEM;
1002 enum REQUIRE_NEHALEM;
1004 enum REQUIRE_PENRYN;
1006 enum REQUIRE_CONROE;
1007 enum PREFER_CORE2DUO;
1008 enum REQUIRE_CORE2DUO;
1013 description "Host CPU architecture.";
1018 enum REQUIRE_X86_64;
1031 description "Host CPU Vendor.";
1040 leaf cpu-socket-count {
1041 description "Number of sockets on the host.";
1045 leaf cpu-core-count {
1046 description "Number of cores on the host.";
1050 leaf cpu-core-thread-count {
1051 description "Number of threads per cores on the host.";
1057 description "List of CPU features.";
1059 description "CPU feature.";
1060 type cpu-feature-type;
1064 leaf om-cpu-model-string {
1065 description "OpenMANO CPU model string";
1069 list om-cpu-feature {
1071 description "List of OpenMANO CPU features";
1073 description "CPU feature";
1081 grouping guest-epa {
1082 description "EPA attributes for the guest";
1083 container guest-epa {
1084 leaf trusted-execution {
1085 description "This VM should be allocated from trusted pool";
1091 "Memory page allocation size. If a VM requires
1092 hugepages, it should choose LARGE or SIZE_2MB
1093 or SIZE_1GB. If the VM prefers hugepages it
1094 should choose PREFER_LARGE.
1095 LARGE : Require hugepages (either 2MB or 1GB)
1096 SMALL : Doesn't require hugepages
1097 SIZE_2MB : Requires 2MB hugepages
1098 SIZE_1GB : Requires 1GB hugepages
1099 PREFER_LARGE : Application prefers hugepages";
1111 leaf cpu-pinning-policy {
1113 "CPU pinning policy describes association
1114 between virtual CPUs in guest and the
1115 physical CPUs in the host.
1116 DEDICATED : Virtual CPUs are pinned to
1118 SHARED : Multiple VMs may share the
1120 ANY : Any policy is acceptable for the VM";
1128 leaf cpu-thread-pinning-policy {
1130 "CPU thread pinning policy describes how to
1131 place the guest CPUs when the host supports
1133 AVOID : Avoids placing a guest on a host
1135 SEPARATE: Places vCPUs on separate cores,
1136 and avoids placing two vCPUs on
1137 two threads of same core.
1138 ISOLATE : Places each vCPU on a different core,
1139 and places no vCPUs from a different
1140 guest on the same core.
1141 PREFER : Attempts to place vCPUs on threads
1153 container cpu-quota {
1154 description "CPU quota describes the CPU resource allocation policy.
1155 Limit and Reserve values are defined in MHz";
1156 uses allocation-properties;
1161 container mem-quota {
1162 description "Memory quota describes the memory resource allocation policy.
1163 Limit and Reserve values are defined in MB";
1164 uses allocation-properties;
1167 container disk-io-quota {
1168 description "Disk IO quota describes the disk IO operations resource allocation policy.
1169 Limit and Reserve values are defined in IOPS";
1170 uses allocation-properties;
1173 container vif-quota {
1174 description "Virtual interfaces quota describes the virtual interface bandwidth resource allocation policy.
1175 Limit and Reserve values are defined in Mbps";
1176 uses allocation-properties;
1181 "List of pcie passthrough devices.";
1185 "Device identifier.";
1190 "Number of devices to attach to the VM.";
1195 choice numa-policy {
1203 container numa-node-policy {
1205 "This policy defines NUMA topology of the
1206 guest. Specifically identifies if the guest
1207 should be run on a host with one NUMA
1208 node or multiple NUMA nodes. As an example
1209 a guest might need 8 VCPUs and 4 GB of
1210 memory. However, it might need the VCPUs
1211 and memory distributed across multiple
1212 NUMA nodes. In this scenario, NUMA node
1213 1 could run with 6 VCPUs and 3GB, and
1214 NUMA node 2 could run with 2 VCPUs and
1219 "The number of NUMA nodes to expose to the VM.";
1225 "This policy specifies how the memory should
1226 be allocated in a multi-node scenario.
1227 STRICT : The memory must be allocated
1228 strictly from the memory attached
1230 PREFERRED : The memory should be allocated
1231 preferentially from the memory
1232 attached to the NUMA node";
1243 "NUMA node identification. Typically
1251 "List of VCPUs to allocate on
1255 description "List of VCPUs ids to allocate on
1262 "Memory size expressed in MB
1263 for this NUMA node.";
1267 choice om-numa-type {
1269 "OpenMANO Numa type selection";
1277 case paired-threads {
1278 container paired-threads {
1279 leaf num-paired-threads {
1283 list paired-thread-ids {
1285 "List of thread pairs to use in case of paired-thread NUMA";
1313 grouping allocation-properties {
1315 description "Defines the maximum allocation. The value 0 indicates that usage is not limited.
1316 This parameter ensures that the instance never uses more than the defined amount of resource.";
1321 description "Defines the guaranteed minimum reservation.
1322 If needed, the machine will definitely get allocated the reserved amount of resources.";
1327 description "Number of shares allocated.
1328 Specifies the proportional weighted share for the domain.
1329 If this element is omitted, the service defaults to the OS provided defaults";
1334 grouping provider-network {
1335 container provider-network {
1336 description "Container for the provider network.";
1337 leaf physical-network {
1339 "Name of the physical network on which the provider
1344 leaf segmentation_id {
1346 "ID of segregated virtual networks";
1352 grouping http-endpoints {
1353 list http-endpoint {
1355 "List of http endpoints to be used by monitoring params";
1359 description "The HTTP path on the management server";
1364 description "Pick HTTPS instead of HTTP , Default is false";
1370 description "The HTTP port to connect to";
1371 type inet:port-number;
1375 description "The HTTP basic auth username";
1380 description "The HTTP basic auth password";
1384 leaf polling-interval-secs {
1385 description "The HTTP polling interval in seconds";
1392 "Method that the URI should perform.
1393 Deafult action is GET.";
1395 type manotypes:http-method;
1400 description "Custom HTTP headers to put on HTTP request";
1403 description "HTTP header key";
1408 description "HTTP header value";
1415 grouping monitoring-param-aggregation {
1416 typedef aggregation-type {
1418 "aggregation-type, indicates the way to aggregate monitoring-params
1419 (e.g. how to aggregate CPU utilisation of all VNFs belonging to the
1420 same VNF group identified by member-vnf-index; or how to aggregate
1421 memory utilisation of all VDUs belonging to the same VDU group
1422 identified by vdu id)";
1432 leaf aggregation-type {
1433 type aggregation-type;
1437 grouping monitoring-param-ui-data {
1443 description "A tag to group monitoring parameters";
1449 description "Defines the UI Display variant of measured counters.";
1450 type manotypes:widget-type;
1455 description "Measured Counter Units (e.g., Packets, Kbps, Mbps, etc.)";
1460 grouping monitoring-param-value {
1462 type param-value-type;
1466 container numeric-constraints {
1469 "Minimum value for the parameter";
1474 "Maximum value for the parameter";
1479 container text-constraints {
1482 "Minimum string length for the parameter";
1487 "Maximum string length for the parameter";
1492 leaf value-integer {
1494 "Current value for an integer parameter";
1498 leaf value-decimal {
1500 "Current value for a decimal parameter";
1508 "Current value for a string parameter";
1513 grouping control-param {
1514 list control-param {
1516 "List of control parameters to manage and
1517 update the running configuration of the VNF";
1521 description "Identifier for control parameter";
1526 description "Name of a control parameter";
1531 description "A description of the control parameter";
1536 description "A tag to group control parameters";
1542 "Minimum value for the parameter";
1548 "Maximum value for the parameter";
1552 leaf current-value {
1554 "Current value for the parameter";
1560 "Step value for the parameter";
1569 type manotypes:widget-type;
1574 "This is the URL where the operation should be performed.";
1581 "Method that the URI should perform.
1582 Default Action is POST";
1584 type manotypes:http-method;
1590 "This is the operation payload or payload template as stringified
1591 JSON. This field provides the data to be sent for this operation
1599 grouping action-param {
1602 "List of action parameters to
1618 description "A tag to group monitoring parameter";
1624 "This is the URL where to perform the operation";
1630 "This is the method to be performed at the uri.
1631 POST by default for action";
1633 type manotypes:http-method;
1639 "This is the operation payload or payload template to be sent in
1640 the data for this operation call";
1647 grouping input-parameter {
1648 description "List of input parameters that can be specified when instantiating a network service.";
1650 list input-parameter {
1652 "List of input parameters";
1659 "An xpath that specfies which element in a descriptor is to be
1666 "The value that the element specified by the xpath should take when a
1667 record is created.";
1673 grouping input-parameter-xpath {
1674 list input-parameter-xpath {
1676 "List of xpaths to parameters inside the NSD
1677 the can be customized during the instantiation.";
1682 "An xpath that specifies the element in a descriptor.";
1687 description "A descriptive string";
1691 leaf default-value {
1692 description "Default Value for the Input Parameter";
1698 grouping nfvi-metrics {
1702 "Label to show in UI";
1709 "The total number of VCPUs available.";
1715 "The VCPU utilization (percentage).";
1726 "Label to show in UI";
1733 "The amount of memory (bytes) currently in use.";
1739 "The amount of memory (bytes) available.";
1745 "The memory utilization (percentage).";
1756 "Label to show in UI";
1763 "The amount of storage (bytes) currently in use.";
1769 "The amount of storage (bytes) available.";
1775 "The storage utilization (percentage).";
1783 container external-ports {
1786 "Label to show in UI";
1788 default "EXTERNAL PORTS";
1793 "The total number of external ports.";
1798 container internal-ports {
1801 "Label to show in UI";
1803 default "INTERNAL PORTS";
1808 "The total number of internal ports.";
1816 "Label to show in UI";
1818 default "NETWORK TRAFFIC";
1821 container incoming {
1824 "Label to show in UI";
1826 default "INCOMING NETWORK TRAFFIC";
1831 "The cumulative number of incoming bytes.";
1837 "The cumulative number of incoming packets.";
1843 "The current incoming byte-rate (bytes per second).";
1851 "The current incoming packet (packets per second).";
1858 container outgoing {
1861 "Label to show in UI";
1863 default "OUTGOING NETWORK TRAFFIC";
1868 "The cumulative number of outgoing bytes.";
1874 "The cumulative number of outgoing packets.";
1880 "The current outgoing byte-rate (bytes per second).";
1888 "The current outgoing packet (packets per second).";
1897 typedef alarm-severity-type {
1898 description "An indication of the importance or urgency of the alarm";
1906 typedef alarm-metric-type {
1907 description "The type of metrics to register the alarm for";
1909 enum CPU_UTILIZATION;
1910 enum MEMORY_UTILIZATION;
1911 enum STORAGE_UTILIZATION;
1915 typedef alarm-statistic-type {
1917 "Statistic type to use to determine threshold crossing
1928 typedef relational-operation-type {
1930 "The relational operator used to define whether an alarm,
1931 scaling event, etc. should be triggered in certain scenarios,
1932 such as if the metric statistic goes above or below a specified
1935 enum GE; // greater than or equal
1936 enum LE; // less than or equal
1937 enum GT; // greater than
1938 enum LT; // less than
1943 grouping alarm-properties {
1945 description "A human readable string to identify the alarm";
1950 description "A description of this alarm";
1956 "The identifier of the VDUR that the alarm is associated with";
1968 list insufficient-data {
1985 "This flag indicates whether the alarm should be repeatedly emitted
1986 while the associated threshold has been crossed.";
1994 "This flag indicates whether the alarm has been enabled or
2002 description "A measure of the importance or urgency of the alarm";
2003 type alarm-severity-type;
2007 description "The type of metric statistic that is tracked by this alarm";
2008 type alarm-statistic-type;
2013 "The relational operator used to define whether an alarm should be
2014 triggered in certain scenarios, such as if the metric statistic
2015 goes above or below a specified value.";
2016 type relational-operation-type;
2021 "This value defines the threshold that, if crossed, will trigger
2030 "The period defines the length of time (seconds) that the metric
2031 data are collected over in oreder to evaluate the chosen
2038 "Defines the length of time (seconds) in which metric data are
2039 collected in order to evaluate the chosen statistic.";
2044 typedef cloud-account-type {
2045 description "VIM account type";
2049 enum cloudsim_proxy;
2058 grouping host-aggregate {
2059 list host-aggregate {
2060 description "Name of the Host Aggregate";
2065 "Name of the additional information attached to the host-aggregate";
2068 leaf metadata-value {
2070 "Value of the corresponding metadata-key";
2076 grouping placement-group-input {
2078 type manotypes:cloud-account-type;
2080 choice cloud-provider {
2082 container availability-zone {
2083 description "Name of the Availability Zone";
2088 container server-group {
2089 description "Name of the Affinity/Anti-Affinity Server Group";
2094 uses host-aggregate;
2097 leaf aws-construct {
2102 leaf openmano-construct {
2107 leaf vsphere-construct {
2112 leaf mock-construct {
2117 leaf cloudsim-construct {
2124 grouping cloud-config {
2127 description "Used to configure the list of public keys to be injected as part
2128 of ns instantiation";
2131 description "Name of this key pair";
2136 description "Key associated with this key pair";
2143 description "List of users to be added through cloud-config";
2146 description "Name of the user ";
2151 description "The user name's real name";
2157 description "Used to configure the list of public keys to be injected as part
2158 of ns instantiation";
2161 description "Name of this key pair";
2166 description "Key associated with this key pair";
2173 grouping placement-group-info {
2178 "Place group construct to define the compute resource placement strategy
2179 in cloud environment";
2184 description "This is free text space used to describe the intent/rationale
2185 behind this placement group. This is for human consumption only";
2191 "Strategy associated with this placement group
2192 Following values are possible
2193 - COLOCATION: Colocation strategy imply intent to share the physical
2194 infrastructure (hypervisor/network) among all members
2196 - ISOLATION: Isolation strategy imply intent to not share the physical
2197 infrastructure (hypervisor/network) among the members
2204 default "COLOCATION";
2208 grouping ip-profile-info {
2209 description "Grouping for IP-Profile";
2210 container ip-profile-params {
2213 type inet:ip-version;
2217 leaf subnet-address {
2218 description "Subnet IP prefix associated with IP Profile";
2219 type inet:ip-prefix;
2222 leaf gateway-address {
2223 description "IP Address of the default gateway associated with IP Profile";
2224 type inet:ip-address;
2227 leaf security-group {
2228 description "Name of the security group";
2235 description "List of DNS Servers associated with IP Profile";
2236 type inet:ip-address;
2240 container dhcp-params {
2242 description "This flag indicates if DHCP is enabled or not";
2247 leaf start-address {
2248 description "Start IP address of the IP-Address range associated with DHCP domain";
2249 type inet:ip-address;
2253 description "Size of the DHCP pool associated with DHCP domain";
2258 leaf subnet-prefix-pool {
2259 description "VIM Specific reference to pre-created subnet prefix";
2265 grouping ip-profile-list {
2268 "List of IP Profiles.
2269 IP Profile describes the IP characteristics for the Virtual-Link";
2274 description "Name of the IP-Profile";
2279 description "Description for IP profile";
2283 uses ip-profile-info;
2287 grouping config-file {
2288 description "Grouping for files needed to be mounted into an additional drive";
2291 "List of configuration files to be written on an additional drive";
2294 description "Name of the configuration file";
2298 description "Full path of the destination in the guest";
2304 grouping supplemental-boot-data {
2305 description "Grouping for custom vim data";
2306 container supplemental-boot-data {
2307 // uses manotypes:config-file;
2308 leaf boot-data-drive {
2309 description "Some VIMs implement additional drives to host config-files or meta-data";
2316 grouping volume-info {
2317 description "Grouping for Volume-info";
2320 description "Description for Volume";
2325 description "Size of disk in GB";
2329 choice volume-source {
2331 "Defines the source of the volume. Possible options are
2332 1. Ephemeral -- Empty disk
2333 2. Image -- Refer to image to be used for volume
2334 3. Volume -- Reference of pre-existing volume to be used
2344 uses image-properties;
2349 description "Type of disk-bus on which this disk is exposed to guest";
2359 description "The type of device as exposed to guest";
2369 grouping rpc-project-name {
2373 "Project to which this belongs";
2375 path "/osm-project:project/osm-project:name";