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 leaf metric-service {
386 "Service name in the execution environment. For helm charts, it will be
387 the name of the kubernetes service used by the exporter to expose metrics
388 to the OSM collector.
392 leaf connection-point-ref {
394 "String representing a leaf reference to the particular external connection point
395 This field should match /vnfd:vnfd-catalog/vnfd:vnfd/vnfd:id/vnfd:connection-point/vnfd:name
399 // path "/vnfd:vnfd-catalog/vnfd:vnfd/vnfd:id/vnfd:connection-point/vnfd:name";
408 grouping vca-config-access {
410 container config-access {
413 "Indicates the way to access to the xNF or xDU for VCA configuration.
414 For the moment there is a single way (ssh-access).";
416 container ssh-access {
419 "If the xNF requires ssh and this parameter is set, SSH keys
420 will be injected so that VCA can configure the xNF or xDU via ssh.";
423 description "whether ssh access is needed or not";
429 description "Default user for ssh";
434 } // END - grouping vca-config-access
436 grouping vca-configuration {
438 "Common information in the descriptors for NS, VNF or VDU configuration.
439 Note: If the NS contains multiple instances of the
440 same VNF or VDU, each instance could have a different
443 uses manotypes:configuration-method;
445 list config-primitive {
447 "List of config primitives supported by the
448 configuration agent for this VNF or VDU.";
453 "Name of the config primitive.";
457 leaf execution-environment-ref {
459 "Leaf reference to the particular execution environment";
461 path "../../execution-environment-list/id";
465 leaf execution-environment-primitive {
467 "Name of the primitive in the execution enviroment. If not explicit,
468 the leaf 'name' will be used as the name of the primitive.";
474 "List of parameters to the config primitive.";
476 uses primitive-parameter;
479 leaf user-defined-script {
481 "A user defined script. If user defined script is defined,
482 the script will be executed using bash";
487 list initial-config-primitive {
489 "Initial set of configuration primitives.";
493 "Sequence number for the configuration primitive.";
497 choice primitive-type {
498 case primitive-definition {
501 "Name of the configuration primitive in the execution environment.";
505 leaf execution-environment-ref {
507 "Leaf reference to the particular execution environment";
509 path "../../execution-environment-list/id";
513 uses primitive-parameter-value;
515 leaf user-defined-script {
517 "A user defined script.";
524 list terminate-config-primitive {
526 "Terminate set of configuration primitives.";
530 "Sequence number for the configuration primitive.";
535 "Name of the configuration primitive in the execution environment.";
539 leaf execution-environment-ref {
541 "Leaf reference to the particular execution environment";
543 path "../../execution-environment-list/id";
547 uses primitive-parameter-value;
549 leaf user-defined-script {
551 "A user defined script.";
555 uses manotypes:vca-metrics;
557 } // END - grouping vca-configuration
559 typedef virtual-link-type {
561 "Type of virtual link
562 ELAN: A multipoint service connecting a set of elements
563 ELINE: A point-to-point service connecting two elements
564 L3: A service providing either Layer-3 visibility (IP) between
565 VDUs/VNFs or explicit interconnection between two ELAN VLDs.";
566 // ETREE: A multipoint service connecting one or
567 // more roots and a set of leaves, but
568 // preventing inter-leaf communication.";
577 grouping named-value {
587 typedef http-method {
589 "Type of HTTP operation";
603 "Type of API to fetch monitoring parameters";
612 typedef json-query-method {
614 "The method to extract a value from a JSON response
616 NAMEKEY - Use the name as the key for a non-nested value.
617 JSONPATH - Use jsonpath-rw implementation to extract a value.
618 OBJECTPATH - Use objectpath implementation to extract a value.";
626 typedef param-value-type {
628 "The type of the parameter value";
636 typedef connection-point-type {
638 "Type of connection point
640 // VNIC_ADDR: Virtual NIC Address
641 // PNIC_ADDR: Physical NIC Address
642 // PPORT: Physical Port.";
649 typedef widget-type {
651 "Type of the widget, typically used by the UI.";
662 typedef cpu-feature-type {
664 "Enumeration for CPU features.
666 AES: CPU supports advanced instruction set for
667 AES (Advanced Encryption Standard).
669 CAT: Cache Allocation Technology (CAT) allows
670 an Operating System, Hypervisor, or similar
671 system management agent to specify the amount
672 of L3 cache (currently the last-level cache
673 in most server and client platforms) space an
674 application can fill (as a hint to hardware
675 functionality, certain features such as power
676 management may override CAT settings).
678 CMT: Cache Monitoring Technology (CMT) allows
679 an Operating System, Hypervisor, or similar
680 system management agent to determine the
681 usage of cache based on applications running
682 on the platform. The implementation is
683 directed at L3 cache monitoring (currently
684 the last-level cache in most server and
687 DDIO: Intel Data Direct I/O (DDIO) enables
688 Ethernet server NICs and controllers talk
689 directly to the processor cache without a
690 detour via system memory. This enumeration
691 specifies if the VM requires a DDIO
735 enum REQUIRE_CLFLUSH;
763 enum REQUIRE_PCLMULQDQ;
764 enum PREFER_PCLMULQDQ;
767 enum REQUIRE_MONITOR;
805 enum REQUIRE_TSC_DEADLINE_TIMER;
806 enum PREFER_TSC_DEADLINE_TIMER;
815 enum REQUIRE_FSGSBASE;
816 enum PREFER_FSGSBASE;
829 enum REQUIRE_INVPCID;
844 typedef nfvi-metric-type {
845 description "Type of NFVI metric to be monitored";
847 enum cpu_utilization;
848 enum average_memory_utilization;
851 enum disk_read_bytes;
852 enum disk_write_bytes;
854 enum packets_received;
855 enum packets_in_dropped;
856 enum packets_out_dropped;
860 typedef scaling-trigger {
871 enum post-scale-out {
877 typedef scaling-policy-type {
888 typedef scaling-criteria-operation {
900 container vm-flavor {
903 "Number of VCPUs for the VM.";
909 "Amount of memory in MB.";
915 "Amount of disk space in GB.";
919 } //grouping vm-flavor
921 grouping vm-flavor-name {
922 leaf vm-flavor-name {
923 description "flavor name to be used while creating vm using cloud account";
928 grouping vswitch-epa {
929 container vswitch-epa {
930 leaf ovs-acceleration {
932 "Specifies Open vSwitch acceleration mode.
933 MANDATORY: OVS acceleration is required
934 PREFERRED: OVS acceleration is preferred";
944 "Specifies Open vSwitch hardware offload mode.
945 MANDATORY: OVS offload is required
946 PREFERRED: OVS offload is preferred";
956 grouping hypervisor-epa {
957 container hypervisor-epa {
960 "Specifies the type of hypervisor.
976 description "Specifies the host level EPA attributes.";
979 "Host CPU model. Examples include: SandyBridge,
982 enum PREFER_WESTMERE;
983 enum REQUIRE_WESTMERE;
984 enum PREFER_SANDYBRIDGE;
985 enum REQUIRE_SANDYBRIDGE;
986 enum PREFER_IVYBRIDGE;
987 enum REQUIRE_IVYBRIDGE;
989 enum REQUIRE_HASWELL;
990 enum PREFER_BROADWELL;
991 enum REQUIRE_BROADWELL;
993 enum REQUIRE_NEHALEM;
998 enum PREFER_CORE2DUO;
999 enum REQUIRE_CORE2DUO;
1004 description "Host CPU architecture.";
1009 enum REQUIRE_X86_64;
1022 description "Host CPU Vendor.";
1031 leaf cpu-socket-count {
1032 description "Number of sockets on the host.";
1036 leaf cpu-core-count {
1037 description "Number of cores on the host.";
1041 leaf cpu-core-thread-count {
1042 description "Number of threads per cores on the host.";
1048 description "List of CPU features.";
1050 description "CPU feature.";
1051 type cpu-feature-type;
1055 leaf om-cpu-model-string {
1056 description "OpenMANO CPU model string";
1060 list om-cpu-feature {
1062 description "List of OpenMANO CPU features";
1064 description "CPU feature";
1072 grouping guest-epa {
1073 description "EPA attributes for the guest";
1074 container guest-epa {
1075 leaf trusted-execution {
1076 description "This VM should be allocated from trusted pool";
1082 "Memory page allocation size. If a VM requires
1083 hugepages, it should choose LARGE or SIZE_2MB
1084 or SIZE_1GB. If the VM prefers hugepages it
1085 should choose PREFER_LARGE.
1086 LARGE : Require hugepages (either 2MB or 1GB)
1087 SMALL : Doesn't require hugepages
1088 SIZE_2MB : Requires 2MB hugepages
1089 SIZE_1GB : Requires 1GB hugepages
1090 PREFER_LARGE : Application prefers hugepages";
1102 leaf cpu-pinning-policy {
1104 "CPU pinning policy describes association
1105 between virtual CPUs in guest and the
1106 physical CPUs in the host.
1107 DEDICATED : Virtual CPUs are pinned to
1109 SHARED : Multiple VMs may share the
1111 ANY : Any policy is acceptable for the VM";
1119 leaf cpu-thread-pinning-policy {
1121 "CPU thread pinning policy describes how to
1122 place the guest CPUs when the host supports
1124 AVOID : Avoids placing a guest on a host
1126 SEPARATE: Places vCPUs on separate cores,
1127 and avoids placing two vCPUs on
1128 two threads of same core.
1129 ISOLATE : Places each vCPU on a different core,
1130 and places no vCPUs from a different
1131 guest on the same core.
1132 PREFER : Attempts to place vCPUs on threads
1144 container cpu-quota {
1145 description "CPU quota describes the CPU resource allocation policy.
1146 Limit and Reserve values are defined in MHz";
1147 uses allocation-properties;
1152 container mem-quota {
1153 description "Memory quota describes the memory resource allocation policy.
1154 Limit and Reserve values are defined in MB";
1155 uses allocation-properties;
1158 container disk-io-quota {
1159 description "Disk IO quota describes the disk IO operations resource allocation policy.
1160 Limit and Reserve values are defined in IOPS";
1161 uses allocation-properties;
1164 container vif-quota {
1165 description "Virtual interfaces quota describes the virtual interface bandwidth resource allocation policy.
1166 Limit and Reserve values are defined in Mbps";
1167 uses allocation-properties;
1172 "List of pcie passthrough devices.";
1176 "Device identifier.";
1181 "Number of devices to attach to the VM.";
1186 choice numa-policy {
1194 container numa-node-policy {
1196 "This policy defines NUMA topology of the
1197 guest. Specifically identifies if the guest
1198 should be run on a host with one NUMA
1199 node or multiple NUMA nodes. As an example
1200 a guest might need 8 VCPUs and 4 GB of
1201 memory. However, it might need the VCPUs
1202 and memory distributed across multiple
1203 NUMA nodes. In this scenario, NUMA node
1204 1 could run with 6 VCPUs and 3GB, and
1205 NUMA node 2 could run with 2 VCPUs and
1210 "The number of NUMA nodes to expose to the VM.";
1216 "This policy specifies how the memory should
1217 be allocated in a multi-node scenario.
1218 STRICT : The memory must be allocated
1219 strictly from the memory attached
1221 PREFERRED : The memory should be allocated
1222 preferentially from the memory
1223 attached to the NUMA node";
1234 "NUMA node identification. Typically
1242 "List of VCPUs to allocate on
1246 description "List of VCPUs ids to allocate on
1253 "Memory size expressed in MB
1254 for this NUMA node.";
1258 choice om-numa-type {
1260 "OpenMANO Numa type selection";
1268 case paired-threads {
1269 container paired-threads {
1270 leaf num-paired-threads {
1274 list paired-thread-ids {
1276 "List of thread pairs to use in case of paired-thread NUMA";
1304 grouping allocation-properties {
1306 description "Defines the maximum allocation. The value 0 indicates that usage is not limited.
1307 This parameter ensures that the instance never uses more than the defined amount of resource.";
1312 description "Defines the guaranteed minimum reservation.
1313 If needed, the machine will definitely get allocated the reserved amount of resources.";
1318 description "Number of shares allocated.
1319 Specifies the proportional weighted share for the domain.
1320 If this element is omitted, the service defaults to the OS provided defaults";
1325 grouping provider-network {
1326 container provider-network {
1327 description "Container for the provider network.";
1328 leaf physical-network {
1330 "Name of the physical network on which the provider
1335 leaf segmentation_id {
1337 "ID of segregated virtual networks";
1343 grouping http-endpoints {
1344 list http-endpoint {
1346 "List of http endpoints to be used by monitoring params";
1350 description "The HTTP path on the management server";
1355 description "Pick HTTPS instead of HTTP , Default is false";
1361 description "The HTTP port to connect to";
1362 type inet:port-number;
1366 description "The HTTP basic auth username";
1371 description "The HTTP basic auth password";
1375 leaf polling-interval-secs {
1376 description "The HTTP polling interval in seconds";
1383 "Method that the URI should perform.
1384 Deafult action is GET.";
1386 type manotypes:http-method;
1391 description "Custom HTTP headers to put on HTTP request";
1394 description "HTTP header key";
1399 description "HTTP header value";
1406 grouping monitoring-param-aggregation {
1407 typedef aggregation-type {
1409 "aggregation-type, indicates the way to aggregate monitoring-params
1410 (e.g. how to aggregate CPU utilisation of all VNFs belonging to the
1411 same VNF group identified by member-vnf-index; or how to aggregate
1412 memory utilisation of all VDUs belonging to the same VDU group
1413 identified by vdu id)";
1423 leaf aggregation-type {
1424 type aggregation-type;
1428 grouping monitoring-param-ui-data {
1434 description "A tag to group monitoring parameters";
1440 description "Defines the UI Display variant of measured counters.";
1441 type manotypes:widget-type;
1446 description "Measured Counter Units (e.g., Packets, Kbps, Mbps, etc.)";
1451 grouping monitoring-param-value {
1453 type param-value-type;
1457 container numeric-constraints {
1460 "Minimum value for the parameter";
1465 "Maximum value for the parameter";
1470 container text-constraints {
1473 "Minimum string length for the parameter";
1478 "Maximum string length for the parameter";
1483 leaf value-integer {
1485 "Current value for an integer parameter";
1489 leaf value-decimal {
1491 "Current value for a decimal parameter";
1499 "Current value for a string parameter";
1504 grouping control-param {
1505 list control-param {
1507 "List of control parameters to manage and
1508 update the running configuration of the VNF";
1512 description "Identifier for control parameter";
1517 description "Name of a control parameter";
1522 description "A description of the control parameter";
1527 description "A tag to group control parameters";
1533 "Minimum value for the parameter";
1539 "Maximum value for the parameter";
1543 leaf current-value {
1545 "Current value for the parameter";
1551 "Step value for the parameter";
1560 type manotypes:widget-type;
1565 "This is the URL where the operation should be performed.";
1572 "Method that the URI should perform.
1573 Default Action is POST";
1575 type manotypes:http-method;
1581 "This is the operation payload or payload template as stringified
1582 JSON. This field provides the data to be sent for this operation
1590 grouping action-param {
1593 "List of action parameters to
1609 description "A tag to group monitoring parameter";
1615 "This is the URL where to perform the operation";
1621 "This is the method to be performed at the uri.
1622 POST by default for action";
1624 type manotypes:http-method;
1630 "This is the operation payload or payload template to be sent in
1631 the data for this operation call";
1638 grouping input-parameter {
1639 description "List of input parameters that can be specified when instantiating a network service.";
1641 list input-parameter {
1643 "List of input parameters";
1650 "An xpath that specfies which element in a descriptor is to be
1657 "The value that the element specified by the xpath should take when a
1658 record is created.";
1664 grouping input-parameter-xpath {
1665 list input-parameter-xpath {
1667 "List of xpaths to parameters inside the NSD
1668 the can be customized during the instantiation.";
1673 "An xpath that specifies the element in a descriptor.";
1678 description "A descriptive string";
1682 leaf default-value {
1683 description "Default Value for the Input Parameter";
1689 grouping nfvi-metrics {
1693 "Label to show in UI";
1700 "The total number of VCPUs available.";
1706 "The VCPU utilization (percentage).";
1717 "Label to show in UI";
1724 "The amount of memory (bytes) currently in use.";
1730 "The amount of memory (bytes) available.";
1736 "The memory utilization (percentage).";
1747 "Label to show in UI";
1754 "The amount of storage (bytes) currently in use.";
1760 "The amount of storage (bytes) available.";
1766 "The storage utilization (percentage).";
1774 container external-ports {
1777 "Label to show in UI";
1779 default "EXTERNAL PORTS";
1784 "The total number of external ports.";
1789 container internal-ports {
1792 "Label to show in UI";
1794 default "INTERNAL PORTS";
1799 "The total number of internal ports.";
1807 "Label to show in UI";
1809 default "NETWORK TRAFFIC";
1812 container incoming {
1815 "Label to show in UI";
1817 default "INCOMING NETWORK TRAFFIC";
1822 "The cumulative number of incoming bytes.";
1828 "The cumulative number of incoming packets.";
1834 "The current incoming byte-rate (bytes per second).";
1842 "The current incoming packet (packets per second).";
1849 container outgoing {
1852 "Label to show in UI";
1854 default "OUTGOING NETWORK TRAFFIC";
1859 "The cumulative number of outgoing bytes.";
1865 "The cumulative number of outgoing packets.";
1871 "The current outgoing byte-rate (bytes per second).";
1879 "The current outgoing packet (packets per second).";
1888 typedef alarm-severity-type {
1889 description "An indication of the importance or urgency of the alarm";
1897 typedef alarm-metric-type {
1898 description "The type of metrics to register the alarm for";
1900 enum CPU_UTILIZATION;
1901 enum MEMORY_UTILIZATION;
1902 enum STORAGE_UTILIZATION;
1906 typedef alarm-statistic-type {
1908 "Statistic type to use to determine threshold crossing
1919 typedef relational-operation-type {
1921 "The relational operator used to define whether an alarm,
1922 scaling event, etc. should be triggered in certain scenarios,
1923 such as if the metric statistic goes above or below a specified
1926 enum GE; // greater than or equal
1927 enum LE; // less than or equal
1928 enum GT; // greater than
1929 enum LT; // less than
1934 grouping alarm-properties {
1936 description "A human readable string to identify the alarm";
1941 description "A description of this alarm";
1947 "The identifier of the VDUR that the alarm is associated with";
1959 list insufficient-data {
1976 "This flag indicates whether the alarm should be repeatedly emitted
1977 while the associated threshold has been crossed.";
1985 "This flag indicates whether the alarm has been enabled or
1993 description "A measure of the importance or urgency of the alarm";
1994 type alarm-severity-type;
1998 description "The type of metric statistic that is tracked by this alarm";
1999 type alarm-statistic-type;
2004 "The relational operator used to define whether an alarm should be
2005 triggered in certain scenarios, such as if the metric statistic
2006 goes above or below a specified value.";
2007 type relational-operation-type;
2012 "This value defines the threshold that, if crossed, will trigger
2021 "The period defines the length of time (seconds) that the metric
2022 data are collected over in oreder to evaluate the chosen
2029 "Defines the length of time (seconds) in which metric data are
2030 collected in order to evaluate the chosen statistic.";
2035 typedef cloud-account-type {
2036 description "VIM account type";
2040 enum cloudsim_proxy;
2049 grouping host-aggregate {
2050 list host-aggregate {
2051 description "Name of the Host Aggregate";
2056 "Name of the additional information attached to the host-aggregate";
2059 leaf metadata-value {
2061 "Value of the corresponding metadata-key";
2067 grouping placement-group-input {
2069 type manotypes:cloud-account-type;
2071 choice cloud-provider {
2073 container availability-zone {
2074 description "Name of the Availability Zone";
2079 container server-group {
2080 description "Name of the Affinity/Anti-Affinity Server Group";
2085 uses host-aggregate;
2088 leaf aws-construct {
2093 leaf openmano-construct {
2098 leaf vsphere-construct {
2103 leaf mock-construct {
2108 leaf cloudsim-construct {
2115 grouping cloud-config {
2118 description "Used to configure the list of public keys to be injected as part
2119 of ns instantiation";
2122 description "Name of this key pair";
2127 description "Key associated with this key pair";
2134 description "List of users to be added through cloud-config";
2137 description "Name of the user ";
2142 description "The user name's real name";
2148 description "Used to configure the list of public keys to be injected as part
2149 of ns instantiation";
2152 description "Name of this key pair";
2157 description "Key associated with this key pair";
2164 grouping placement-group-info {
2169 "Place group construct to define the compute resource placement strategy
2170 in cloud environment";
2175 description "This is free text space used to describe the intent/rationale
2176 behind this placement group. This is for human consumption only";
2182 "Strategy associated with this placement group
2183 Following values are possible
2184 - COLOCATION: Colocation strategy imply intent to share the physical
2185 infrastructure (hypervisor/network) among all members
2187 - ISOLATION: Isolation strategy imply intent to not share the physical
2188 infrastructure (hypervisor/network) among the members
2195 default "COLOCATION";
2199 grouping ip-profile-info {
2200 description "Grouping for IP-Profile";
2201 container ip-profile-params {
2204 type inet:ip-version;
2208 leaf subnet-address {
2209 description "Subnet IP prefix associated with IP Profile";
2210 type inet:ip-prefix;
2213 leaf gateway-address {
2214 description "IP Address of the default gateway associated with IP Profile";
2215 type inet:ip-address;
2218 leaf security-group {
2219 description "Name of the security group";
2226 description "List of DNS Servers associated with IP Profile";
2227 type inet:ip-address;
2231 container dhcp-params {
2233 description "This flag indicates if DHCP is enabled or not";
2238 leaf start-address {
2239 description "Start IP address of the IP-Address range associated with DHCP domain";
2240 type inet:ip-address;
2244 description "Size of the DHCP pool associated with DHCP domain";
2249 leaf subnet-prefix-pool {
2250 description "VIM Specific reference to pre-created subnet prefix";
2256 grouping ip-profile-list {
2259 "List of IP Profiles.
2260 IP Profile describes the IP characteristics for the Virtual-Link";
2265 description "Name of the IP-Profile";
2270 description "Description for IP profile";
2274 uses ip-profile-info;
2278 grouping config-file {
2279 description "Grouping for files needed to be mounted into an additional drive";
2282 "List of configuration files to be written on an additional drive";
2285 description "Name of the configuration file";
2289 description "Full path of the destination in the guest";
2295 grouping supplemental-boot-data {
2296 description "Grouping for custom vim data";
2297 container supplemental-boot-data {
2298 // uses manotypes:config-file;
2299 leaf boot-data-drive {
2300 description "Some VIMs implement additional drives to host config-files or meta-data";
2307 grouping volume-info {
2308 description "Grouping for Volume-info";
2311 description "Description for Volume";
2316 description "Size of disk in GB";
2320 choice volume-source {
2322 "Defines the source of the volume. Possible options are
2323 1. Ephemeral -- Empty disk
2324 2. Image -- Refer to image to be used for volume
2325 3. Volume -- Reference of pre-existing volume to be used
2335 uses image-properties;
2340 description "Type of disk-bus on which this disk is exposed to guest";
2350 description "The type of device as exposed to guest";
2360 grouping rpc-project-name {
2364 "Project to which this belongs";
2366 path "/osm-project:project/osm-project:name";