4 * Copyright 2016 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:ietf:params:xml:ns:yang:nfvo:vnfd";
34 import ietf-yang-types {
38 import ietf-inet-types {
44 "Initial revision. This YANG file defines
45 the Virtual Network Function (VNF)";
47 "Derived from earlier versions of base YANG files";
50 grouping common-connection-point {
52 description "Name of the connection point";
57 description "Identifier for the internal connection points";
62 description "Short name to appear as label in the UI";
67 description "Type of the connection point.";
68 type manotypes:connection-point-type;
70 leaf port-security-enabled {
71 description "Enables the port security for the port";
76 grouping virtual-interface {
77 container virtual-interface {
79 "Container for the virtual interface properties";
83 "Specifies the type of virtual interface
85 VIRTIO : Use the traditional VIRTIO interface.
86 PCI-PASSTHROUGH : Use PCI-PASSTHROUGH interface.
87 SR-IOV : Use SR-IOV interface.
88 E1000 : Emulate E1000 interface.
89 RTL8139 : Emulate RTL8139 interface.
90 PCNET : Emulate PCNET interface.
91 OM-MGMT : Used to specify openmano mgmt external-connection type";
107 "Specifies the virtual PCI address. Expressed in
108 the following format dddd:dd:dd.d. For example
109 0000:00:12.0. This information can be used to
110 pass as metadata during the VM creation.";
116 "Aggregate bandwidth of the NIC.";
122 grouping vnfd-descriptor {
124 description "Identifier for the VNFD.";
129 description "VNFD name.";
135 description "Short name to appear as label in the UI";
140 description "Vendor of the VNFD.";
146 "Vendor logo for the Virtual Network Function";
151 description "Description of the VNFD.";
156 description "Version of the VNFD";
160 uses manotypes:vnf-configuration;
162 container mgmt-interface {
164 "Interface over which the VNF is managed.";
166 choice endpoint-type {
168 "Indicates the type of management endpoint.";
172 "Specifies the static IP address for managing the VNF.";
174 type inet:ip-address;
180 "Use the default management interface on this VDU.";
190 "Use the ip address associated with this connection point.";
193 path "../../connection-point/name";
201 "Port for the management interface.";
202 type inet:port-number;
205 container dashboard-params {
206 description "Parameters for the VNF dashboard";
209 description "The HTTP path for the dashboard";
214 description "Pick HTTPS instead of HTTP , Default is false";
219 description "The HTTP port for the dashboard";
220 type inet:port-number;
228 "List of Internal Virtual Link Descriptors (VLD).
229 The internal VLD describes the basic topology of
230 the connectivity such as E-LAN, E-Line, E-Tree.
231 between internal VNF components of the system.";
234 description "Identifier for the VLD";
239 description "Name of the internal VLD";
244 description "Short name to appear as label in the UI";
249 description "Description of internal VLD.";
254 type manotypes:virtual-link-type;
257 leaf root-bandwidth {
259 "For ELAN this is the aggregate bandwidth.";
263 leaf leaf-bandwidth {
265 "For ELAN this is the bandwidth of branches.";
269 list internal-connection-point {
271 description "List of internal connection points in this VLD";
273 description "reference to the internal connection point id";
275 path "../../../vdu/internal-connection-point/id";
279 uses manotypes:provider-network;
281 description "Extra parameters for VLD instantiation";
283 case vim-network-ref {
284 leaf vim-network-name {
286 "Name of network in VIM account. This is used to indicate
287 pre-provisioned network name in cloud account.";
292 case vim-network-profile {
293 leaf ip-profile-ref {
294 description "Named reference to IP-profile object";
302 uses manotypes:ip-profile-list;
304 list connection-point {
307 "List for external connection points. Each VNF has one
308 or more external connection points that connect the VNF
309 to other VNFs or to external networks. Each VNF exposes
310 connection points to the orchestrator, which can construct
311 network services by connecting the connection points
312 between different VNFs. The NFVO will use VLDs and VNFFGs
313 at the network service level to construct network services.";
315 uses common-connection-point;
319 description "List of Virtual Deployment Units";
323 description "Unique id for the VDU";
328 description "Unique name for the VDU";
333 description "Description of the VDU.";
338 description "Number of instances of VDU";
344 "Specifies the virtual PCI address. Expressed in
345 the following format dddd:dd:dd.d. For example
346 0000:00:12.0. This information can be used to
347 pass as metadata during the VM creation.";
351 uses manotypes:vm-flavor;
352 uses manotypes:guest-epa;
353 uses manotypes:vswitch-epa;
354 uses manotypes:hypervisor-epa;
355 uses manotypes:host-epa;
360 uses manotypes:alarm;
363 uses manotypes:image-properties;
365 choice cloud-init-input {
367 "Indicates how the contents of cloud-init script are provided.
368 There are 2 choices - inline or in a file";
373 "Contents of cloud-init script, provided inline, in cloud-config format";
379 leaf cloud-init-file {
381 "Name of file with contents of cloud-init script in cloud-config format";
387 uses manotypes:supplemental-boot-data;
389 list internal-connection-point {
392 "List for internal connection points. Each VNFC
393 has zero or more internal connection points.
394 Internal connection points are used for connecting
395 the VNF with components internal to the VNF. If a VNF
396 has only one VNFC, it may not have any internal
399 uses common-connection-point;
402 list internal-interface {
404 "List of internal interfaces for the VNF";
409 "Name of internal interface. Note that this
410 name has only local significance to the VDU.";
414 leaf vdu-internal-connection-point-ref {
416 path "../../internal-connection-point/id";
419 uses virtual-interface;
422 list external-interface {
424 "List of external interfaces for the VNF.
425 The external interfaces enable sending
426 traffic to and from VNF.";
431 "Name of the external interface. Note that
432 this name has only local significance to
437 leaf vnfd-connection-point-ref {
439 "Name of the external connection point.";
441 path "../../../connection-point/name";
444 uses virtual-interface;
451 description "Name of the disk-volumes, e.g. vda, vdb etc";
455 uses manotypes:volume-info;
459 list vdu-dependency {
461 "List of VDU dependencies.";
464 leaf vdu-source-ref {
470 leaf vdu-depends-on-ref {
472 "Reference to the VDU on which
473 the source VDU depends.";
480 leaf service-function-chain {
481 description "Type of node in Service Function Chaining Architecture";
492 leaf service-function-type {
494 "Type of Service Function.
495 NOTE: This needs to map with Service Function Type in ODL to
496 support VNFFG. Service Function Type is mandatory param in ODL
497 SFC. This is temporarily set to string for ease of use";
501 uses manotypes:monitoring-param;
503 list placement-groups {
504 description "List of placement groups at VNF level";
507 uses manotypes:placement-group-info;
512 "List of VDUs that are part of this placement group";
513 key "member-vdu-ref";
515 leaf member-vdu-ref {
517 path "../../../vdu/id";
524 container vnfd-catalog {
526 "Virtual Network Function Descriptor (VNFD).";
531 uses vnfd-descriptor;