Cover Image


MANO & the Future of CSP Automation

出版商 Heavy Reading 商品編碼 549643
出版日期 內容資訊 英文 16 Pages
商品交期: 最快1-2個工作天內
Back to Top
由於MANO和CSP的自動化的未來 MANO & the Future of CSP Automation
出版日期: 2017年08月29日 內容資訊: 英文 16 Pages

CSP (通訊服務供應商) ,以NFV (網路功能虛擬化) MANO (管理與協調) 的業務的自動化作為目標。


第1章 簡介、主要調查結果

  • 主要調查結果

第2章 進展

  • CSP可使用現有的MANO解決方案
  • CSP對ETSI遵守有異議
  • OpenStack能幹的VIM判明
  • 開放原始碼與標準化機構致力於MANO
    • ECOMP
    • Open-O
    • ONAP
    • OSM
    • ETSI

第3章 持續性問題

  • Multi-Domain Orchestration
  • VNF生活方式管理
  • MANO要素定義/區別
  • 超級規模公共雲端供應商的影響



For communications service providers (CSPs), the journey toward network functions virtualization (NFV) will not end with virtualization. To truly benefit from this transformation, CSPs will need to automate their operations. Management and orchestration (MANO) of the virtual environment will play a key role in this automation. MANO will allow CSPs to automate the configuration of the NFV Infrastructure (NFV-I), service creation and network resource optimization. When this happens, CSPs can achieve both lower opex and improved service agility.

As NFV moves out of proofs of concept and into production, many in the industry are now focusing their attention on how to operationalize NFV, including MANO. Indeed, during the spring conference season, numerous vendors, open source project leaders and CSPs celebrated their triumphs, and soberly described the challenges yet to overcome.

CSPs are forging ahead with NFV despite a lack of standards for the MANO elements. The concerns about OpenStack as the Virtualized Infrastructure Manager (VIM) are largely resolved, with leading CSPs publicly discussing their implementations of it. Most concerns around MANO are less about architecture, and more about implementation. Open source communities such as Open Network Automation Platform (ONAP) and Open Source MANO (OSM) have expanded beyond the original work of the European Telecommunications Standards Institute (ETSI) to ensure that CSPs can create and manage services across virtual and physical domains.

The ETSI NFV Industry Specifications Group (ISG) is also continuing its efforts and collaborates closely with OSM. Many in the industry are also investigating common information models that are needed to ensure the MANO elements can onboard and manage multiple vendors' virtualized network functions (VNFs) in a consistent way from a common architecture. Some CSPs and their suppliers expect that the cloud-native approach used by the hyperscale Web companies will also influence their future MANO architectures.

Most industry players now acknowledge that the industry has mostly coalesced around OpenStack for the VIM. CSPs can get vendor-supported distributions from numerous vendors, with Red Hat, Canonical and Mirantis being the most widely used according to the OpenStack Foundation. In March 2017, an ETSI NFV Specialist Task Force began working on an "OpenStack gap identification" project. In a survey Heavy Reading conducted for the OpenStack Foundation, nearly 75 percent of CSPs said they were actively following the project, and more than a third were contributing to it, as shown in the excerpt below.


MANO & the Future of CSP Automation is published in PDF format.

Table of Contents


  • 1.1 Key Findings


  • 2.1 CSPs Able to Use Existing MANO Solutions in Production
  • 2.2 CSPs Have Different Opinions About ETSI Compliance
  • 2.3 OpenStack Is Proving to Be a Capable VIM
  • 2.4 Open Source & Standards Organizations Working on MANO
    • Enhanced Control, Orchestration, Management and Policy (ECOMP)
    • Open-Orchestrator (Open-O)
    • Open Network Automation Platform (ONAP)
    • Open Source MANO (OSM)
    • ETSI


  • 3.1 Multi-Domain Orchestration
    • Multi-VIM Environments Are Likely
    • Services Require More Than Virtual Resources
  • 3.2 VNF Lifecycle Management
  • 3.3 Definitions of/Distinctions Between MANO Elements
  • 3.4 Impact of Hyperscale Public Cloud Providers


Back to Top