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-relationships {
225 container vca-relationships {
227 description "List of relations between VCA componets.";
229 key "requires provides";
233 "Name of the required relation.";
239 "Name of the provided relation.";
246 grouping vca-metrics {
248 "Information about the VNF or VDU metrics";
250 description "List of VCA related metrics";
254 "Name of the metric, as defined in the Juju charm.";
258 } // END - grouping vca-metrics
260 grouping configuration-method {
261 choice config-method {
263 "Defines the configuration method for the VNF or VDU.";
266 "Use custom script for configuring the VNF or VDU.
267 This script is executed in the context of
268 Orchestrator (The same system and environment
273 "Script type - currently supported - Scripts confirming to Rift CA plugin";
283 "Configure the VNF or VDU through Juju.";
286 description "Juju charm to use with the VNF or VDU.";
290 description "Is this a proxy charm?";
294 uses manotypes:vca-relationships;
300 grouping ns-configuration {
302 "Information about NS configuration. Note:
303 In the future this should be equivalent to vca-configuration
306 uses manotypes:configuration-method;
309 grouping vca-configuration {
311 "Information about the VNF or VDU configuration. Note:
312 If the NS contains multiple instances of the
313 same VNF or VDU, each instance could have a different
316 uses manotypes:configuration-method;
318 list config-primitive {
320 "List of config primitives supported by the
321 configuration agent for this VNF or VDU.";
326 "Name of the config primitive.";
332 "List of parameters to the config primitive.";
334 uses primitive-parameter;
337 leaf user-defined-script {
339 "A user defined script. If user defined script is defined,
340 the script will be executed using bash";
345 list initial-config-primitive {
347 "Initial set of configuration primitives.";
351 "Sequence number for the configuration primitive.";
355 choice primitive-type {
356 case primitive-definition {
359 "Name of the configuration primitive.";
363 uses primitive-parameter-value;
365 leaf user-defined-script {
367 "A user defined script.";
374 list terminate-config-primitive {
376 "Terminate set of configuration primitives.";
380 "Sequence number for the configuration primitive.";
385 "Name of the configuration primitive.";
389 uses primitive-parameter-value;
391 leaf user-defined-script {
393 "A user defined script.";
397 uses manotypes:vca-metrics;
399 } // END - grouping vca-configuration
401 typedef virtual-link-type {
403 "Type of virtual link
404 ELAN: A multipoint service connecting a set of VNFs
405 ELINE: For a simple point to point connection
406 // between a VNF and the existing network.
407 // ETREE: A multipoint service connecting one or
408 // more roots and a set of leaves, but
409 // preventing inter-leaf communication.";
417 grouping named-value {
427 typedef http-method {
429 "Type of HTTP operation";
443 "Type of API to fetch monitoring parameters";
452 typedef json-query-method {
454 "The method to extract a value from a JSON response
456 NAMEKEY - Use the name as the key for a non-nested value.
457 JSONPATH - Use jsonpath-rw implementation to extract a value.
458 OBJECTPATH - Use objectpath implementation to extract a value.";
466 typedef param-value-type {
468 "The type of the parameter value";
476 typedef connection-point-type {
478 "Type of connection point
480 // VNIC_ADDR: Virtual NIC Address
481 // PNIC_ADDR: Physical NIC Address
482 // PPORT: Physical Port.";
489 typedef widget-type {
491 "Type of the widget, typically used by the UI.";
502 typedef cpu-feature-type {
504 "Enumeration for CPU features.
506 AES: CPU supports advanced instruction set for
507 AES (Advanced Encryption Standard).
509 CAT: Cache Allocation Technology (CAT) allows
510 an Operating System, Hypervisor, or similar
511 system management agent to specify the amount
512 of L3 cache (currently the last-level cache
513 in most server and client platforms) space an
514 application can fill (as a hint to hardware
515 functionality, certain features such as power
516 management may override CAT settings).
518 CMT: Cache Monitoring Technology (CMT) allows
519 an Operating System, Hypervisor, or similar
520 system management agent to determine the
521 usage of cache based on applications running
522 on the platform. The implementation is
523 directed at L3 cache monitoring (currently
524 the last-level cache in most server and
527 DDIO: Intel Data Direct I/O (DDIO) enables
528 Ethernet server NICs and controllers talk
529 directly to the processor cache without a
530 detour via system memory. This enumeration
531 specifies if the VM requires a DDIO
575 enum REQUIRE_CLFLUSH;
603 enum REQUIRE_PCLMULQDQ;
604 enum PREFER_PCLMULQDQ;
607 enum REQUIRE_MONITOR;
645 enum REQUIRE_TSC_DEADLINE_TIMER;
646 enum PREFER_TSC_DEADLINE_TIMER;
655 enum REQUIRE_FSGSBASE;
656 enum PREFER_FSGSBASE;
669 enum REQUIRE_INVPCID;
684 typedef nfvi-metric-type {
685 description "Type of NFVI metric to be monitored";
687 enum cpu_utilization;
688 enum average_memory_utilization;
691 enum disk_read_bytes;
692 enum disk_write_bytes;
694 enum packets_received;
695 enum packets_dropped;
699 typedef scaling-trigger {
710 enum post-scale-out {
716 typedef scaling-policy-type {
727 typedef scaling-criteria-operation {
739 container vm-flavor {
742 "Number of VCPUs for the VM.";
748 "Amount of memory in MB.";
754 "Amount of disk space in GB.";
758 } //grouping vm-flavor
760 grouping vm-flavor-name {
761 leaf vm-flavor-name {
762 description "flavor name to be used while creating vm using cloud account";
767 grouping vswitch-epa {
768 container vswitch-epa {
769 leaf ovs-acceleration {
771 "Specifies Open vSwitch acceleration mode.
772 MANDATORY: OVS acceleration is required
773 PREFERRED: OVS acceleration is preferred";
783 "Specifies Open vSwitch hardware offload mode.
784 MANDATORY: OVS offload is required
785 PREFERRED: OVS offload is preferred";
795 grouping hypervisor-epa {
796 container hypervisor-epa {
799 "Specifies the type of hypervisor.
815 description "Specifies the host level EPA attributes.";
818 "Host CPU model. Examples include: SandyBridge,
821 enum PREFER_WESTMERE;
822 enum REQUIRE_WESTMERE;
823 enum PREFER_SANDYBRIDGE;
824 enum REQUIRE_SANDYBRIDGE;
825 enum PREFER_IVYBRIDGE;
826 enum REQUIRE_IVYBRIDGE;
828 enum REQUIRE_HASWELL;
829 enum PREFER_BROADWELL;
830 enum REQUIRE_BROADWELL;
832 enum REQUIRE_NEHALEM;
837 enum PREFER_CORE2DUO;
838 enum REQUIRE_CORE2DUO;
843 description "Host CPU architecture.";
861 description "Host CPU Vendor.";
870 leaf cpu-socket-count {
871 description "Number of sockets on the host.";
875 leaf cpu-core-count {
876 description "Number of cores on the host.";
880 leaf cpu-core-thread-count {
881 description "Number of threads per cores on the host.";
887 description "List of CPU features.";
889 description "CPU feature.";
890 type cpu-feature-type;
894 leaf om-cpu-model-string {
895 description "OpenMANO CPU model string";
899 list om-cpu-feature {
901 description "List of OpenMANO CPU features";
903 description "CPU feature";
912 description "EPA attributes for the guest";
913 container guest-epa {
914 leaf trusted-execution {
915 description "This VM should be allocated from trusted pool";
921 "Memory page allocation size. If a VM requires
922 hugepages, it should choose LARGE or SIZE_2MB
923 or SIZE_1GB. If the VM prefers hugepages it
924 should choose PREFER_LARGE.
925 LARGE : Require hugepages (either 2MB or 1GB)
926 SMALL : Doesn't require hugepages
927 SIZE_2MB : Requires 2MB hugepages
928 SIZE_1GB : Requires 1GB hugepages
929 PREFER_LARGE : Application prefers hugepages";
941 leaf cpu-pinning-policy {
943 "CPU pinning policy describes association
944 between virtual CPUs in guest and the
945 physical CPUs in the host.
946 DEDICATED : Virtual CPUs are pinned to
948 SHARED : Multiple VMs may share the
950 ANY : Any policy is acceptable for the VM";
958 leaf cpu-thread-pinning-policy {
960 "CPU thread pinning policy describes how to
961 place the guest CPUs when the host supports
963 AVOID : Avoids placing a guest on a host
965 SEPARATE: Places vCPUs on separate cores,
966 and avoids placing two vCPUs on
967 two threads of same core.
968 ISOLATE : Places each vCPU on a different core,
969 and places no vCPUs from a different
970 guest on the same core.
971 PREFER : Attempts to place vCPUs on threads
983 container cpu-quota {
984 description "CPU quota describes the CPU resource allocation policy.
985 Limit and Reserve values are defined in MHz";
986 uses allocation-properties;
991 container mem-quota {
992 description "Memory quota describes the memory resource allocation policy.
993 Limit and Reserve values are defined in MB";
994 uses allocation-properties;
997 container disk-io-quota {
998 description "Disk IO quota describes the disk IO operations resource allocation policy.
999 Limit and Reserve values are defined in IOPS";
1000 uses allocation-properties;
1003 container vif-quota {
1004 description "Virtual interfaces quota describes the virtual interface bandwidth resource allocation policy.
1005 Limit and Reserve values are defined in Mbps";
1006 uses allocation-properties;
1011 "List of pcie passthrough devices.";
1015 "Device identifier.";
1020 "Number of devices to attach to the VM.";
1025 choice numa-policy {
1033 container numa-node-policy {
1035 "This policy defines NUMA topology of the
1036 guest. Specifically identifies if the guest
1037 should be run on a host with one NUMA
1038 node or multiple NUMA nodes. As an example
1039 a guest might need 8 VCPUs and 4 GB of
1040 memory. However, it might need the VCPUs
1041 and memory distributed across multiple
1042 NUMA nodes. In this scenario, NUMA node
1043 1 could run with 6 VCPUs and 3GB, and
1044 NUMA node 2 could run with 2 VCPUs and
1049 "The number of NUMA nodes to expose to the VM.";
1055 "This policy specifies how the memory should
1056 be allocated in a multi-node scenario.
1057 STRICT : The memory must be allocated
1058 strictly from the memory attached
1060 PREFERRED : The memory should be allocated
1061 preferentially from the memory
1062 attached to the NUMA node";
1073 "NUMA node identification. Typically
1081 "List of VCPUs to allocate on
1085 description "List of VCPUs ids to allocate on
1092 "Memory size expressed in MB
1093 for this NUMA node.";
1097 choice om-numa-type {
1099 "OpenMANO Numa type selection";
1107 case paired-threads {
1108 container paired-threads {
1109 leaf num-paired-threads {
1113 list paired-thread-ids {
1115 "List of thread pairs to use in case of paired-thread NUMA";
1143 grouping allocation-properties {
1145 description "Defines the maximum allocation. The value 0 indicates that usage is not limited.
1146 This parameter ensures that the instance never uses more than the defined amount of resource.";
1151 description "Defines the guaranteed minimum reservation.
1152 If needed, the machine will definitely get allocated the reserved amount of resources.";
1157 description "Number of shares allocated.
1158 Specifies the proportional weighted share for the domain.
1159 If this element is omitted, the service defaults to the OS provided defaults";
1164 grouping provider-network {
1165 container provider-network {
1166 description "Container for the provider network.";
1167 leaf physical-network {
1169 "Name of the physical network on which the provider
1174 leaf segmentation_id {
1176 "ID of segregated virtual networks";
1182 grouping ns-service-primitive {
1183 list service-primitive {
1185 "Network service level service primitives.";
1191 "Name of the service primitive.";
1197 "List of parameters for the service primitive.";
1200 uses manotypes:primitive-parameter;
1203 list parameter-group {
1205 "Grouping of parameters which are logically grouped in UI";
1210 "Name of the parameter group";
1216 "List of parameters for the service primitive.";
1218 uses manotypes:primitive-parameter;
1222 description "Is this parameter group mandatory";
1228 list vnf-primitive-group {
1230 "List of service primitives grouped by VNF.";
1232 key "member-vnf-index-ref";
1233 leaf member-vnf-index-ref {
1235 "Reference to member-vnf within constituent-vnfds";
1241 "A reference to a vnfd. This is a
1243 ../../../../nsd:constituent-vnfd
1244 + [nsd:id = current()/../nsd:id-ref]
1246 NOTE: An issue with confd is preventing the
1247 use of xpath. Seems to be an issue with leafref
1248 to leafref, whose target is in a different module.
1249 Once that is resolved this will switched to use
1265 description "Index of this primitive";
1270 description "Name of the primitive in the VNF primitive ";
1276 leaf user-defined-script {
1278 "A user defined script.";
1284 grouping http-endpoints {
1285 list http-endpoint {
1287 "List of http endpoints to be used by monitoring params";
1291 description "The HTTP path on the management server";
1296 description "Pick HTTPS instead of HTTP , Default is false";
1302 description "The HTTP port to connect to";
1303 type inet:port-number;
1307 description "The HTTP basic auth username";
1312 description "The HTTP basic auth password";
1316 leaf polling-interval-secs {
1317 description "The HTTP polling interval in seconds";
1324 "Method that the URI should perform.
1325 Deafult action is GET.";
1327 type manotypes:http-method;
1332 description "Custom HTTP headers to put on HTTP request";
1335 description "HTTP header key";
1340 description "HTTP header value";
1347 grouping monitoring-param-aggregation {
1348 typedef aggregation-type {
1350 "aggregation-type, indicates the way to aggregate monitoring-params
1351 (e.g. how to aggregate CPU utilisation of all VNFs belonging to the
1352 same VNF group identified by member-vnf-index; or how to aggregate
1353 memory utilisation of all VDUs belonging to the same VDU group
1354 identified by vdu id)";
1364 leaf aggregation-type {
1365 type aggregation-type;
1369 grouping monitoring-param-ui-data {
1375 description "A tag to group monitoring parameters";
1381 description "Defines the UI Display variant of measured counters.";
1382 type manotypes:widget-type;
1387 description "Measured Counter Units (e.g., Packets, Kbps, Mbps, etc.)";
1392 grouping monitoring-param-value {
1394 type param-value-type;
1398 container numeric-constraints {
1401 "Minimum value for the parameter";
1406 "Maximum value for the parameter";
1411 container text-constraints {
1414 "Minimum string length for the parameter";
1419 "Maximum string length for the parameter";
1424 leaf value-integer {
1426 "Current value for an integer parameter";
1430 leaf value-decimal {
1432 "Current value for a decimal parameter";
1440 "Current value for a string parameter";
1445 grouping control-param {
1446 list control-param {
1448 "List of control parameters to manage and
1449 update the running configuration of the VNF";
1453 description "Identifier for control parameter";
1458 description "Name of a control parameter";
1463 description "A description of the control parameter";
1468 description "A tag to group control parameters";
1474 "Minimum value for the parameter";
1480 "Maximum value for the parameter";
1484 leaf current-value {
1486 "Current value for the parameter";
1492 "Step value for the parameter";
1501 type manotypes:widget-type;
1506 "This is the URL where the operation should be performed.";
1513 "Method that the URI should perform.
1514 Default Action is POST";
1516 type manotypes:http-method;
1522 "This is the operation payload or payload template as stringified
1523 JSON. This field provides the data to be sent for this operation
1531 grouping action-param {
1534 "List of action parameters to
1550 description "A tag to group monitoring parameter";
1556 "This is the URL where to perform the operation";
1562 "This is the method to be performed at the uri.
1563 POST by default for action";
1565 type manotypes:http-method;
1571 "This is the operation payload or payload template to be sent in
1572 the data for this operation call";
1579 grouping input-parameter {
1580 description "List of input parameters that can be specified when instantiating a network service.";
1582 list input-parameter {
1584 "List of input parameters";
1591 "An xpath that specfies which element in a descriptor is to be
1598 "The value that the element specified by the xpath should take when a
1599 record is created.";
1605 grouping input-parameter-xpath {
1606 list input-parameter-xpath {
1608 "List of xpaths to parameters inside the NSD
1609 the can be customized during the instantiation.";
1614 "An xpath that specifies the element in a descriptor.";
1619 description "A descriptive string";
1623 leaf default-value {
1624 description "Default Value for the Input Parameter";
1630 grouping nfvi-metrics {
1634 "Label to show in UI";
1641 "The total number of VCPUs available.";
1647 "The VCPU utilization (percentage).";
1658 "Label to show in UI";
1665 "The amount of memory (bytes) currently in use.";
1671 "The amount of memory (bytes) available.";
1677 "The memory utilization (percentage).";
1688 "Label to show in UI";
1695 "The amount of storage (bytes) currently in use.";
1701 "The amount of storage (bytes) available.";
1707 "The storage utilization (percentage).";
1715 container external-ports {
1718 "Label to show in UI";
1720 default "EXTERNAL PORTS";
1725 "The total number of external ports.";
1730 container internal-ports {
1733 "Label to show in UI";
1735 default "INTERNAL PORTS";
1740 "The total number of internal ports.";
1748 "Label to show in UI";
1750 default "NETWORK TRAFFIC";
1753 container incoming {
1756 "Label to show in UI";
1758 default "INCOMING NETWORK TRAFFIC";
1763 "The cumulative number of incoming bytes.";
1769 "The cumulative number of incoming packets.";
1775 "The current incoming byte-rate (bytes per second).";
1783 "The current incoming packet (packets per second).";
1790 container outgoing {
1793 "Label to show in UI";
1795 default "OUTGOING NETWORK TRAFFIC";
1800 "The cumulative number of outgoing bytes.";
1806 "The cumulative number of outgoing packets.";
1812 "The current outgoing byte-rate (bytes per second).";
1820 "The current outgoing packet (packets per second).";
1829 typedef alarm-severity-type {
1830 description "An indication of the importance or urgency of the alarm";
1838 typedef alarm-metric-type {
1839 description "The type of metrics to register the alarm for";
1841 enum CPU_UTILIZATION;
1842 enum MEMORY_UTILIZATION;
1843 enum STORAGE_UTILIZATION;
1847 typedef alarm-statistic-type {
1849 "Statistic type to use to determine threshold crossing
1860 typedef relational-operation-type {
1862 "The relational operator used to define whether an alarm,
1863 scaling event, etc. should be triggered in certain scenarios,
1864 such as if the metric statistic goes above or below a specified
1867 enum GE; // greater than or equal
1868 enum LE; // less than or equal
1869 enum GT; // greater than
1870 enum LT; // less than
1875 grouping alarm-properties {
1877 description "A human readable string to identify the alarm";
1882 description "A description of this alarm";
1888 "The identifier of the VDUR that the alarm is associated with";
1900 list insufficient-data {
1917 "This flag indicates whether the alarm should be repeatedly emitted
1918 while the associated threshold has been crossed.";
1926 "This flag indicates whether the alarm has been enabled or
1934 description "A measure of the importance or urgency of the alarm";
1935 type alarm-severity-type;
1939 description "The type of metric statistic that is tracked by this alarm";
1940 type alarm-statistic-type;
1945 "The relational operator used to define whether an alarm should be
1946 triggered in certain scenarios, such as if the metric statistic
1947 goes above or below a specified value.";
1948 type relational-operation-type;
1953 "This value defines the threshold that, if crossed, will trigger
1962 "The period defines the length of time (seconds) that the metric
1963 data are collected over in oreder to evaluate the chosen
1970 "Defines the length of time (seconds) in which metric data are
1971 collected in order to evaluate the chosen statistic.";
1976 typedef cloud-account-type {
1977 description "VIM account type";
1981 enum cloudsim_proxy;
1990 grouping host-aggregate {
1991 list host-aggregate {
1992 description "Name of the Host Aggregate";
1997 "Name of the additional information attached to the host-aggregate";
2000 leaf metadata-value {
2002 "Value of the corresponding metadata-key";
2008 grouping placement-group-input {
2010 type manotypes:cloud-account-type;
2012 choice cloud-provider {
2014 container availability-zone {
2015 description "Name of the Availability Zone";
2020 container server-group {
2021 description "Name of the Affinity/Anti-Affinity Server Group";
2026 uses host-aggregate;
2029 leaf aws-construct {
2034 leaf openmano-construct {
2039 leaf vsphere-construct {
2044 leaf mock-construct {
2049 leaf cloudsim-construct {
2056 grouping cloud-config {
2059 description "Used to configure the list of public keys to be injected as part
2060 of ns instantiation";
2063 description "Name of this key pair";
2068 description "Key associated with this key pair";
2075 description "List of users to be added through cloud-config";
2078 description "Name of the user ";
2083 description "The user name's real name";
2089 description "Used to configure the list of public keys to be injected as part
2090 of ns instantiation";
2093 description "Name of this key pair";
2098 description "Key associated with this key pair";
2105 grouping placement-group-info {
2110 "Place group construct to define the compute resource placement strategy
2111 in cloud environment";
2116 description "This is free text space used to describe the intent/rationale
2117 behind this placement group. This is for human consumption only";
2123 "Strategy associated with this placement group
2124 Following values are possible
2125 - COLOCATION: Colocation strategy imply intent to share the physical
2126 infrastructure (hypervisor/network) among all members
2128 - ISOLATION: Isolation strategy imply intent to not share the physical
2129 infrastructure (hypervisor/network) among the members
2136 default "COLOCATION";
2140 grouping ip-profile-info {
2141 description "Grouping for IP-Profile";
2142 container ip-profile-params {
2145 type inet:ip-version;
2149 leaf subnet-address {
2150 description "Subnet IP prefix associated with IP Profile";
2151 type inet:ip-prefix;
2154 leaf gateway-address {
2155 description "IP Address of the default gateway associated with IP Profile";
2156 type inet:ip-address;
2159 leaf security-group {
2160 description "Name of the security group";
2167 description "List of DNS Servers associated with IP Profile";
2168 type inet:ip-address;
2172 container dhcp-params {
2174 description "This flag indicates if DHCP is enabled or not";
2179 leaf start-address {
2180 description "Start IP address of the IP-Address range associated with DHCP domain";
2181 type inet:ip-address;
2185 description "Size of the DHCP pool associated with DHCP domain";
2190 leaf subnet-prefix-pool {
2191 description "VIM Specific reference to pre-created subnet prefix";
2197 grouping ip-profile-list {
2200 "List of IP Profiles.
2201 IP Profile describes the IP characteristics for the Virtual-Link";
2206 description "Name of the IP-Profile";
2211 description "Description for IP profile";
2215 uses ip-profile-info;
2219 grouping config-file {
2220 description "Grouping for files needed to be mounted into an additional drive";
2223 "List of configuration files to be written on an additional drive";
2226 description "Name of the configuration file";
2230 description "Full path of the destination in the guest";
2236 grouping supplemental-boot-data {
2237 description "Grouping for custom vim data";
2238 container supplemental-boot-data {
2239 // uses manotypes:config-file;
2240 leaf boot-data-drive {
2241 description "Some VIMs implement additional drives to host config-files or meta-data";
2248 grouping volume-info {
2249 description "Grouping for Volume-info";
2252 description "Description for Volume";
2257 description "Size of disk in GB";
2261 choice volume-source {
2263 "Defines the source of the volume. Possible options are
2264 1. Ephemeral -- Empty disk
2265 2. Image -- Refer to image to be used for volume
2266 3. Volume -- Reference of pre-existing volume to be used
2276 uses image-properties;
2281 description "Type of disk-bus on which this disk is exposed to guest";
2291 description "The type of device as exposed to guest";
2301 grouping rpc-project-name {
2305 "Project to which this belongs";
2307 path "/osm-project:project/osm-project:name";