Nokia CloudBand Network Director

Transcription

1 Nokia CloudBand Network Director Product Information Nokia CloudBand Network Director automates and optimizes the management of network services and distributed multivendor NFV environments, allowing simpler management and fast introduction of complex services. Overview Nokia CloudBand Network Director provides the NFV orchestrator function according to the ETSI NFV reference architecture and supports TM Forum ZOOM (Zero touch Orchestration, Operations and Management). The Network Director has a well-defined role within a hierarchy of orchestrators (Figure 1). CloudBand Network Director is ready-to-use software with two main functions. As a resource orchestrator, the Network Director administers, monitors and optimizes NFV infrastructure resources across geographically distributed NFVI nodes. As a network service orchestrator, the system onboards network services and automates their lifecycles, including deployment, monitoring, updates and termination. Benefits Rapid and repeatable introduction of multi-vnf network services Complex and changing service chains are easily created and managed Simplified management of large-scale, multi-tenant, multi-site, multi-vendor NFV platforms Alignment with open source upstream for rapid innovation, lower costs and no vendor lock-in

2 Through the support of TOSCA, an open domain-specific modeling language for network services, as well as an open source workflow engine and an open source policy engine, operators benefit from the rapid pace of open source innovation while getting a carrier-grade product ready for deployment. This is enabled through the extensive experience of the Nokia CloudBand team in building and deploying NFV platforms using open source and standard s, ensuring stability and streamlined operations. The CloudBand team actively contributes and influences open source upstream Figure development 1: Hierarchy to ensure carrier of requirements orchestrators are met. The architecture of the CloudBand Network Director (Figure 2) is based on a set of microservices communicating through REST synchronous messages and an asynchronous message bus. Plug-ins enable the Network Director to work with VNF managers, infrastructure managers, SDN controllers and additional orchestrators from any vendor, ensuring maximum flexibility. The Network Director is pre-integrated with the Nokia CloudBand Application Manager. Nokia Global Services also offer integration services for VNF Managers from other vendors. End-to-end service orchestrator (OSS) Manages end-to-end customer facing and resource facing services across physical and virtual network functions NFV orchestrator CloudBand Network Director Manages network services in the virtual domain, decomposing them into VNFs and VLs (virtual links) VNF Manager Manages the lifecycle of VNFs, decomposing them into VMs and VLs Physical network functions Virtual infrastructure manager SDN controller Virtualizes, manages and monitors compute, storage and network resources on an NFVI node Figure 1: Hierarchy of orchestrators 1 Nokia 2016 <Change information classification in footer> Page 2

3 CloudBand Network Director Figure 2: Logical Architecture GUI Catalog LCM Resource optimization Inventory Platform Operational Tools Disaster Recovery Workflow and Configuration Engine Policy Engine Resource Management Analytics Resource Monitoring Southbound Plugins EMS PNF VNFM SDN OpenStack VMware NFVO Figure 2 Nokia 2: 2016 Logical architecture Resource orchestrator As an NFV resource orchestrator, Network Director offers a global view of all available resources across NFVI nodes, as well as information on how VNFs and network services use these resources. This unique position and insight allows it to manipulate, police, analyze and then optimize the behavior and the utilization of the NFV platform. CloudBand Network Director administers resources such as virtual infrastructure managers (VIM) of multiple NFVI nodes, VNF managers and SDN controllers, which are all treated as resources. The Network Director maintains an inventory and a topology map of the nodes and their resources whether or not the resources have been allocated through the Network Director or through direct VIM calls. The Network Director monitors the overall status and health of these resources and reports this information to higher level operational support systems and human operators. The topology map is used to apply the given policies and to govern VNF and network service lifecycle management (LCM) actions across the platform. Policies can be applied relating to the placement of each resource, such as affinity, priority or quotas. The Network Director accepts or rejects resource requests from VNF managers and other systems based on configurable policies. CloudBand Network Director optimizes the use of resources to achieve higher performance and better use of capacity and recommends placement of VNFs and network services across different NFVI nodes, taking into account specific NFVI characteristics (enhanced platform awareness). Based on resource usage analytics, the Network Director supports NFVI capacity management and planning. By analyzing trends in capacity and DR requirements, CloudBand Network Director can forecast what capacity will be needed. In addition to the planning aspects, the analytics engine suggests better ways of using current capacity. Simulations then predict the outcome of any event affecting capacity, without the need to actually trigger it. Page 3

4 orchestrator A network service or service chain, according to the ETSI NFV definition and the TM Forum ZOOM model, is a collection of network functions connected by a network function forwarding graph. In particular, a network service can be implemented with VNFs and a VNF forwarding graph. The Network Director supports network services as well as single VNFs. As part of network services, VNFs can be connected to other VNFs as well as physical network functions. Typical network service use cases are virtualized enterprise customer premises equipment, including service chaining, Gi-LAN, virtual evolved packet core and Voice over LTE. The Network Director models and orchestrates network services using OASIS TOSCA descriptors and OpenStack Mistral workflows. The Network Director supports onboarding of network services and single VNFs and maintains a catalog of these. Onboarding is achieved by modeling the service as a collection of one or more VNFs connected with a forwarding graph, a set of resource requirements and a collection of workflows describing its lifecycle actions. The resulting model is documented as a cloud service archive (CSAR) and stored in the network service/vnf catalog. The archive contains a manifest file along with service templates and any workflow files and related scripts to customize the VNF or network service life cycle operations. With the Network Director domain-specific modeling language and workflow engine, virtually all network services/network functions can be onboarded without software changes to the Network Director. terminate update onboard deploy monitor Once a network service or function has been onboarded, higher level orchestrators or human operators can trigger the Network Director to deploy or update an instance of the network service as part of the service orchestration process (Figure 3). As a first step of this process, the set of VNFs and VNF forwarding graphs is determined based on a TOSCA template. Then, the Network Director identifies a generic VNF manager, such as CloudBand Application Manager, or VNF-specific VNF managers, to execute the lifecycle of the VNFs. If necessary, an appropriate VNF manager is instantiated. It then instructs the VNF manager to deploy or update and commission the VNFs and commission connected PNFs to work with the VNFs. The Network Director requests an SDN controller to establish the VNF forwarding graph between the network functions. The forwarding graph can be a collection of virtual links with or without service chaining. For Service Chaining use cases, virtual links are configured as defined in the VNF Forwarding Graph (VNFFG). When VNFs are added or removed from a service chain, the virtual links are created, modified or deleted as per the updated VNFFG. When the network service has been deployed and commissioned, control returns to the higher level orchestrator, which is responsible for servicespecific configuration and service activation. 3 Nokia 2016 <Change information classification in footer> Page 4

5 opt CRM OSS NFVO VNFM SDN VNFs VLs Physical PNFs Create end-to-end network service [Orchestrate] Decompose to physical and virtual Create virtual part of service Decompose to individual VNFs Create VNFs Connect CPs opt [Instantiate] Provision physical part opt [Activate] Configure Configure Attach Service deployed CRM OSS NFVO VNFM SDN VNFs VLs Physical PNFs Figure 3: High level deployment flow 4 Nokia 2016 <Change information classification in footer> During the lifetime of the network service, the Network Director captures network service and VNF topology, monitors the health status of the service and scales, heals and updates the service according to policies described in the network service descriptor. Monitoring, assurance and disaster recovery CloudBand Network Director facilitates fault monitoring by tapping into capabilities of various fault management applications such as EMS/ NMS, VIM and VNFM. Faults received from these sources are enriched with information about associated network services to simplify network troubleshooting. Troubleshooting and automatic repair use a common topology and correlation engine based on a root cause analysis tool. CloudBand Network Director, with its lifecycle management engine, supports several automated disaster recovery models that can be described and configured in the network service/vnf descriptor. Page 5

6 Product characteristics Lean NFV network service operation SDN integration for complete NS connectivity needs modeled within NSD Standard descriptor language (TOSCA) and open source workflow engine Analytics and policy engine for optimizing resource utilization of the NFV platform Embedded support for multi-vim/ VNFM/EMS/SDN solution integration Pre-integrated NFV stack with Nokia and multi-vendor components Leverage and contribute to open-source Disaster Recovery (DR) management Automation everywhere, zero touch operations, including networking, monitoring and fault management Generic solution for networking requirements of network services interconnected with the VNFs deployment models across multi-vim/vnf environment Experienced team in influencing & shaping the TOSCA community to meet the requirements of NFV network service descriptors Open-source user extensible tools for controlling NFV platform behavior and usage patterns Plugin architecture enables short integration cycles in a multi-vendor environment Part of a tested and validated end-to-end NFV offering Active involvement in open source initiatives for fast adoption of technologies and no-vendor-lock-in Model and manage disaster recovery as part of NS/VNF lifecycles Product code C R EN Nokia Oyj Karaportti 3 FI Espoo Finland Tel +358 (0) Nokia is a registered trademark of Nokia Corporation. Other product and company names mentioned herein may be trademarks or trade names of their respective owners. Nokia 2016