株式会社グローバルインフォメーション
TEL: 044-952-0102
市場調査レポート

MANOとCSPによる自動化の将来

MANO & the Future of CSP Automation

発行 Heavy Reading 商品コード 549643
出版日 ページ情報 英文 16 Pages
納期: 即日から翌営業日
価格
本日の銀行送金レート: 1USD=109.06円で換算しております。
Back to Top
MANOとCSPによる自動化の将来 MANO & the Future of CSP Automation
出版日: 2017年08月29日 ページ情報: 英文 16 Pages
概要

CSP (通信サービスプロバイダー) は、NFV (ネットワーク機能仮想化) MANO (管理とオーケストレーション) による業務の自動化を目指しています。

当レポートでは、MANOとCSPによる自動化の将来について検証して、体系的な情報を提供しています。

第1章 イントロダクション・主な調査結果

  • 主な調査結果

第2章 進捗状況

  • CSPは既存のMANOソリューションを使用可能
  • CSPはETSIコンプライアンスに異論がある
  • OpenStackは有能なVIMであることが判明
  • オープンソースと標準化機構はMANOに取り組んでいる
    • ECOMP
    • Open-O
    • ONAP
    • OSM
    • ETSI

第3章 継続的な問題

  • マルチドメインオーケストレーション
  • 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.

image1

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

Table of Contents

1. INTRODUCTION & KEY FINDINGS

  • 1.1 Key Findings

2. PROGRESS

  • 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. CONTINUING CONCERNS

  • 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

TERMS OF USE

Back to Top