Internet Working Group W. Xu Y. Jiang C. Zhou Huawei Internet Draft Intended status: Standards Track Expires: March 2014 September 25, 2013 Data Models for Network Functions Virtualization draft-xjz-nfv-model-datamodel-00.txt Status of this Memo This Internet-Draft is submitted to IETF in full conformance with the provisions of BCP 78 and BCP 79. Internet-Drafts are working documents of the Internet Engineering Task Force (IETF), its areas, and its working groups. Note that other groups may also distribute working documents as Internet-Drafts. Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress." The list of current Internet-Drafts can be accessed at http://www.ietf.org/ietf/1id-abstracts.txt The list of Internet-Draft Shadow Directories can be accessed at http://www.ietf.org/shadow.html This Internet-Draft will expire on March 25, 2013. Copyright Notice Copyright (c) 2013 IETF Trust and the persons identified as the document authors. All rights reserved. This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of Xu, et al Expires March 25, 2014 [Page 1] Internet-Draft Problem Statement of NFV Model September 2013 the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License. Abstract This document provides some YANG data models for Network Functions Virtualization (NFV). Table of Contents 1. Introduction ............................................. 2 2. Conventions used in this document ......................... 2 3. Terminology .............................................. 3 4. Virtual Network Function Description Overview ............. 4 4.1. the VNFD Component ..................................... 4 4.2. NFVD Data model ........................................ 4 5. NFVD YANG Module......................................... 5 6. Security Considerations ................................... 8 7. IANA Considerations ....................................... 8 8. References ............................................... 8 8.1. Normative References ................................... 8 8.2. Informative References ................................. 8 9. Acknowledgments .......................................... 9 1. Introduction YANG [RFC6020] is a data modeling language used to model configuration and state data manipulated by the Network Configuration Protocol (NETCONF) [RFC6241]. A small set of built-in data types are defined in [RFC6020], a collection of common data types are further defined in [RFC6991]. This document defines a YANG [RFC6020] data model for Network Functions Virtualization (NFV). 2. Conventions used in this document The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in [RFC2119]. Expires March 25, 2014 [Page 2] Internet-Draft Problem Statement of NFV Model September 2013 3. Terminology CMS: Cloud Management System. Network Function (NF): A functional building block within an operator's network infrastructure, which has well-defined external interfaces and a well-defined functional behaviour. NF set: A collection of NFs with unspecified connectivity between them. Network Functions Virtualization Orchestrator (NFVO): a function that deploys, operates, manages, and coordinates VNFs and the respective NFVI. The Orchestrator has control and visibility of all VNF running inside the NFVI. Network Functions Virtualization Infrastructure (NFVI): the totality of all hardware and software components that constitute the environment in which VNFs are deployed, managed and executed. The NFVI includes resources for computation, networking and storage. Physical Network Function (PNF): An implementation of a NF via a tightly coupled software and hardware system. Virtual Machine (VM): A program and configuration of part of a host computer server. Note that the Virtual Machine inherits the properties of its host computer server e.g. location, network interfaces. Virtualised Network Function (VNF): An implementation of an executable software program that constitutes the whole or a part of an NF and can be deployed on a virtualisation infrastructure. VNF Descriptor (VNFD): A configuration template that describes a VNF in terms of its deployment and operational behavior, and is used in the process of on-boarding and instantiating a VNF. The deployment behavior describes the NFV Infrastructure resources that a VNF instance requires whereas the operational behavior describes the VNF instance topology and VNF instance lifecycle operations. VNF Forwarding Graph: A graph specified by a Network Service Provider of bi-directional logical links connecting NF nodes where at least one node is a VNF through which network traffic is directed. NFV Service: A network service utilizing NFs, where at least some NFs are VNFs. A VNF Forwarding Graph is an example of such a service. Expires March 25, 2014 [Page 3] Internet-Draft Problem Statement of NFV Model September 2013 4. Virtual Network Function Descriptor (VNFD) 4.1. VNFD Components The main objective of VNF modeling will include: - Basic VNF attributes: VNF name, function description, sharing or non-sharing attribute. - Deployment attributes: environment requirements of VNF deployment such as the number of VMs, virtual CPU, memory and disk requirements, image of each VM, and QoS requirements such as bandwidth and delay of VNF. - Operational attributes: which defines the operational and management behavior, such as start, stop, pause, migration and etc. - Interface attributes: external interface, such as interface type, configuration parameters of these interfaces. 4.2. NFVD Data Model NFNode is defined as a basic class of VNF data type. +--rw NFNode +--rw basicProperties | +--rw name string | +--rw description string | +--rw producer string +--rw deployment | +--rw VMUsed enumeration | +--rw image uri | +--rw vResource Expires March 25, 2014 [Page 4] Internet-Draft Problem Statement of NFV Model September 2013 | +--rw vCPU yang:uint16 | +--rw vMemory yang:uint64 | +--rw vDisk yang:uint64 +--rw operations | +--rw action enumeration +--rw interfaces +--rw interface * [name] +--rw name string +--rw type string 5. YANG Module for VNFD Module of ietf-yang-nfv-types will include the following new types. Container NFNode { container basicProperties { leaf name { type string; } leaf description { type string; } leaf producer { type string; } leaf sharing { type enumeration { enum non-sharing { Expires March 25, 2014 [Page 5] Internet-Draft Problem Statement of NFV Model September 2013 value "0"; description "The NF is shared"; } enum sharing { value "1"; description "The NF is not shared"; } } } } container deployment { leaf VMUsed { type enumeration { enum Single-VM { value "0"; description "Deployed on a single VM"; } enum Multi-VMs { value "1"; description "Deployed on multiple VMs"; } } } container vResource { leaf vCPU { type uint16; } leaf vMemory { type uint64; Expires March 25, 2014 [Page 6] Internet-Draft Problem Statement of NFV Model September 2013 } leaf vDisk { type uint64; } } leaf-list image { type uri; } } container operation { leaf-list action { type enumeration { enum start; enum stop; enum pause; enum migrate; } } } container interfaces { container interface { leaf name { type string; } leaf type { type enumeration { enum ethernet { value 1; Expires March 25, 2014 [Page 7] Internet-Draft Problem Statement of NFV Model September 2013 } enum ip { value 2; } } } } } } 6. Security Considerations TBD. 7. IANA Considerations TBD. 8. References 8.1. Normative References [RFC6020] Schoenwaelder,J., RFC 6020, YANG - A Data Modeling Language for the Network Configuration Protocol (NETCONF), 2010 [RFC6991] Schoenwaelder,J.,RFC 6991, Common YANG Data Types, 2013 8.2. Informative References Xu, W., Jiang, Y., Zhou, C., draft-xjz-nfv-model-problem-statement-00 Expires March 25, 2014 [Page 8] Internet-Draft Problem Statement of NFV Model September 2013 9. Acknowledgments TBD Authors' Addresses Weiping Xu Huawei Technologies Co., Ltd. Bantian, Longgang district Shenzhen 518129, China Yuanlong Jiang Huawei Technologies Co., Ltd. Bantian, Longgang district Shenzhen 518129, China Email: jiangyuanlong@huawei.com Cathy Zhou Huawei Technologies Co., Ltd. Bantian, Longgang district Shenzhen 518129, China Expires March 25, 2014 [Page 9]