TTA PG2202 실무반
ETSI NFV IFA #11 회의 보고
2015.6.23 이종화
ETSI NFV IFA WG #11 회의
IFA WG #11 F2F Meeting
16 June ~ 18 June 2015, San Jose USA Hosted by Cisco
2015년도 회의 일정
NFV#11 (7.28~31, 미국 샌 호세) NFV#12 (10.27~30, 미국 뉴저지)
2
IFA WG
Interface and Functional Architecture WG Streams Leader Stream 1a
Raquel Morera (Verizon)
Stream 1b
Mehmet Ersue (Nokia networks)
Stream 2
ZongNing (Huawei)
3
Work Items 규격 번호
규격 제목
stream
IFA001
Stream2
Acceleration – Overview and Use cases
IFA002
Stream2
Acceleration – VNF Interfaces
IFA003
Stream2
Acceleration – vSwitch Benchmarking
IFA004
Stream2
Acceleration – Management Aspect
IFA005
Stream1B
Or-Vi reference point specification
IFA006
Stream1B
Vi-Vnfm reference point specification
IFA007
Stream1B
Or-Vnfm reference point specification
IFA008
Stream1B
Ve-Vnfm reference point specification
IFA009
Stream1A
MANO Architectural options
IFA010
Stream1A
Mano Functional Requirements
IFA011
Stream1A
VNF Packaging Specification
IFA012
Stream1B
Os-Ma-Nfvo reference point specification – Management and Infor mation model
IFA013
Stream1B
Os-Ma-Nfvo reference point specification
IFA014
Stream1B
Network Service Template
4
Work Plan
NFVIFA(15)000725r4_Planning_Slides_closing_IFA_WG_at_NFV_10 © ETSI 2015. All rights reserved
5
Timelines
6
Current versions of Drafts
7
IFA WG Programs and Dependencies
8
IFA WG #11 주요 논의 내용
Granting Procedures still on-going discussion Extension of VNFD meta data modeling needed Scaling initiate new discussion Architectural Options
Generic VNFM & Multi VNFMs accepted Split NFVO into service Or & resource Or
still on-going discussion
Progress on
Resource management Interface requirements for PM & FM at VNF level & NS level Interface reqs. for NS 9
Granting Procedures (1)
VNF LCM Granting: permission given by the NFVO to the VNFM to perform VNF lifecycle operations VNF LCM Granting procedures: granting request, granting response Granting request must contain the following information:
Two options will be progressed
Resources needed to execute the LCM operation Type of operation requested
VNFM requests VNF LCM granting for LCM operation except Query information NFVO can grant the VNFM to perform VNF LCM operations without further explicit requests based on certain conditions
Granting is mainly used to allow NFVO to
Enforce LCM-related policies for the VNFM and across VNFMs Enforce limitation of resources related to the VNF, group of VNFs or NS Guarantee consistency of Network Services, i.e. avoiding termination of a VNF that is part of a NS unless NS is terminated 10
Option 1 Granting from VNFM (2)
For every VNF LCM operation potentially impacting resources
VNFM issues the granting request with the following information:
Resources impacted by the LCM operation (either needed for the operation or freed by the operation) Type of VNF LCM operation requested VNF for which the request is done
NFVO processes the granting request
Whether requesting resource (i.e. instantiate, scale out) or freeing resources (i.e. terminate, scale in)
Checks policies Checks limitation of resources Check potential impact on existing NS
NFVO returns granting response
Y/N If yes, VIM id and optionally more details, like zone or host (i.e. in case of affinity rules between VNFMs) 11
Option 2 Delegation of granting (3)
NFVO delegates granting to the VNFM to perform VNF LCM operations without further explicit requests based on certain conditions Conditions for delegation of granting Conditions on limitation of resources are met And conditions on policies are met And NFVO policies allow delegation of granting Conditions on limitation of resources for delegation of granting The granularity of the resource limitation is included in the VNFM scope (VNF, or group of VNFs managed by same VNFM). Exclude NS granularity and group of VNFs managed by different VNFMs Or the limitation of resources has been mapped to a quota at VIM level 12
Option 2 Delegation of granting (4)
Open issue: Can some of those policies be delegated to the VIM? Ex: affinity rule for 2 VNFs part of a NS managed by 2 VNFMs, like MRB and MRF Storage must be co-located For sure, affinity rules can be delegated to the VIM, but how to tell VNFM to use those affinity rules for a specific VNFM Delegating policies to the VIM would require to set those policies in the VIM in advance and inform VNFM as part of the delegation on how to use them.
Open issue: Checking potential impact of VNF LCM operation on existing NS cannot be done when granting is delegated
13
Granting Procedures (5)
New terminology
Single Granting: Single VNF LCM granting request by the VNFM to the NFVO – a VNFM makes a request to allocate resources for a given VNF Multiple Granting : the VNFM either request granting to allocate resources for multiple VNFs or the NFVO tells the VNFM (e.g., by setting a policy) that it can allocate resources of multiple VNFs (within some given constraints).
Granting vs VNF-related Resource Management in direct mode: The VNFM invokes directly Resource Management operations towards the VIM indirect mode: The VNFM invokes Resource Management operations towards the NFVO, which in turn invokes them towards the VIM 14
VNFD
(1)
Definition of VNFD Configuration template that describes a VNF in terms of its deployment and operational behavior, and is used in the process of VNF on-boarding and managing the lifecycle of a VNF instance
Only NFVO or VNFM can automatically processes/operate on VNFD
A VNF has VNFCs, which contain internal connection points Virtual Links connect two or more connection points External connection points which are used to connect the VNF to the outside world Are there internal connection points which are not attached to a VNFC?
Referenced by NFVIFA(15)000777_VNFD Progress 15
VNFD
(2)
How do external connection points map to internal connection points? Different proposals Support both
Referenced by NFVIFA(15)000777_VNFD Progress
16
Scaling by VNF vs VNFM
Which functional block decides the action of scaling? Option 1: VNF according to the VNFD Option 2: VNFM based on the resource availability Ve-Vnfm-Vnf
VNF
VNFM
VNFD
auto-scale policy
17
Resource Management
Definition
Resource Zone: A set of NFVI hardware and software resources logically grouped according to physical isolation and redundancy capabilities or to certain administrative policies for the NFVI Resource Pool: Logical grouping of NFVI hardware and software resources
Modification on Information elements
NFVO
VNFM
Or-Vi (IFA006)
Vi-Vnfm (IFA005)
VIM
18
Fault Management – VNF level VNF Lifecycle management VNF Lifecycle Change Notification VNF Performance management VNF Fault management
EM
VNF
Ve-Vnfm-Em
VNFM
Ve-Vnfm-Vnf
VNF Lifecycle management VNF Configuration management VNF Performance management VNF Fault management PG2202 취합 의견을 토대로 제안 및 반영: NFVIFA(15)000615r6_IFA008_Section_5__Reference_point_requirements NFVIFA(15)000622r4_IFA008_Section_5_x_Ve-Vnfm-em_interface_requirements NFVIFA(15)000623r4_IFA008_Section_5_x_Ve-Vnfm-vnf_interface_requirements
19
Fault Management – NS level
Fault information about
Virtualised resources supporting the constituent VNFs for a given Network Service Virtualised resources resources supporting the connectivity of a given Network Service
OSS/BSS
Os-Ma-Nfvo
NFVO
notifyInformation (virtualised resources)
Issues Fault information about VNF and NS?
VIM
20
Additional Information about IFA WG
21
Structure of NFV Groups NFV NFV TSC
NFV NOC NFV EVE WG
Working Group
NFV IFA WG NFV REL WG
NFV TST WG NFV SEC WG
TSC (Technical Steering Committee) NOC (Network Operators Council) EVE (Evolution and Ecosystem) IFA (Interface & Functional Architecture) REL (Reliability) TST (Testing, Implementation & Open source) SEC (Security) 22
Structure of NFV Groups NFV Groups
NFV TSC (Technical Steering Committee)
NFV 표준화 활동 총괄 및 지원 (기술 규격 작업에 대한 모니터링, 워 킹그룹간 협력 또는 조정 작업 등)
다른 표준화 단체와의 협력, 조율 등 지원
NFV NOC
주요 통신사업자들의 요구사항 수렴
(Network Operators Council)
요구사항 반영을 위한 각 워킹그룹의 활동 모니터링 및 가이드 역할
NFV 기술의 진화, 새로운 요구사항 및 에코시스템 발굴
NFV 기능의 인터페이스 및 기능 구조에 대한 규격 개발
기존의 SWA, MANO, INF 워킹그룹이 하나로 합쳐짐
NFV 기능의 오류, 동작 모니터링, 오류 방지 기능이 포함되는 규격
NFV EVE Working Group (Evolution and Ecosystem)
NFV IFA Working Group (Interface & Functional Architecture) NFV REL Working Group
(Reliability)
개발
NFV TST Expert Group (Testing,
Implementation
Open source) NFV SEC Expert Group (Security)
&
기존의 PoC 진행, 개발과 오픈 소스 활용 관련 활동 지원
OPNFV 활동과의 관계를 통해 요구사항 반영 등
NFV 구조에서의 보안 관련 규격 개발
23
Leadership
24
Work Items of WGs EVE WG Report on SDN usage in NFV architectural framework
Report on use cases for MEF Carrier Ethernet Services Infrastructure; Hypervisor Domain specification Report on the review of virtualisation technologies Report on NFVI Node Physical Architecture Guidelines for Multi-Vendor Environment TST WG Editorial revision of NFV PoC Framework
Report on NFV interoperability test methodology Report on Pre-deployment validation of NFV environments and services
25
Work Items of WGs REL WG Study on the Management of NFV Reliability with Scalable Architecture REPORT: Study of models and features for E2E reliability in the NFV architecture
REPORT: Active monitoring and failure detection in NFV environments
SEC WG Attestation for Secure Network Function Virtualization Deployments Network Function Virtualisation (NFV) NFV Security Certificate Management Guidance Security Monitoring for NFV Deployments Expanded problem statement and resolution for LI in NFV
Suggested security and regulatory concerns guide
26
IFA005
The Or-Vi reference point is used for exchanges between NFV Orchestrator and VIM, and supports the following interfaces
(Or-Vi reference point specification)
VNF software image management Virtualised Resources Catalogue Management Virtualised Resources Capacity Management Virtualised Resources Management Virtualised Resources Change Notification Virtualised Resources Performance Management Virtualised Resources Fault Management Policy administration interface NFP management interface
Defines Exposed interfaces VIM and Information elements exchanged 27
IFA006
The Vi-Vnfm reference point is used for exchange of information elements between the Virtualized Infrastructure Manager (VIM) and VNF Manager (VNFM), and the following are the interfaces supported by this reference point:
(Vi-Vnfm reference point specification)
VNF software image management Virtualised resources catalogue management Virtualised resources management Virtualised resources change notification Virtualised resources performance management Virtualised resources fault management
Defines Exposed interfaces VNFM & VIM and Information elements exchanged
28
IFA010
(Mano Functional Requirements)
This document arranges the functional requirement by categorizing the requirements basing on key operational functions of NFV management and Orchestration, which are documented in [NFVMAN001]
VNF life cycle management Network Service (NS) life cycle management VNF information management NS information management Virtualised resource management NFV performance management NFV fault management NFV policy management Security consideration
29
VNF Instantiation
VNF LCM interface is exposed by VNFM VNF LCM interface can be re-exposed by NFVO, that identifies the target VNFM and forward the request 2 major steps in VNF instantiation
Resource allocation VNF Configuration
2 options for management of resource related to VNFs: Performed by the NFVO, acting a global Resource Orchestrator. VNFM requests resources to NFVO that forwards the request for resources to the VIM Performed by the VNFM. VNFM asks the NFVO for granting the VNF LCM request and then directly requests resources to the VIM 30
Simplified VNF Instantiation flow
Option 1: Resource Management performed by NFVO
OSS/BSS
1- Instantiate VNF
NFVO
2- Forward instantiation request To VNFM
EM
6- Notification VNF instantiated
7- Configure VNF application parameters
VNF
3- Request resource allocation for VNF instantiation
VNFM
4- Request resource allocation for VNF instantiation
5- Configure VNF deployment parameters
VIM Request Notifications
31
Simplified VNF Instantiation flow
Option 2: Resource Management performed by VNFM OSS/BSS or any cons umer
NFVO 1b- Instantiate VNF
2- Grant VNF LCM request
1a- Instantiate VNF
EM 5- Notification VNF instantiated 6- Configure VNF application parameters
VNF
4- Configure VNF deployment parameters
VNFM 3- Request resource allocation for VNF instantiation
Request Notifications
VIM
32
Fault management FM Target
Produced by
Faults related to
Virtualised resources
by VIM
virtualised resources managed by the VIM
by VNFM
VNF instances managed by this VNFM
VNF
by VNFM
virtualised resources related to VNF instances managed by this VNFM and application faults provided by the VNF
by VNF
application faults
by NFVO
virtualised resources and application faults
network service
33
FM simplified flow NFVO
OSS/BSS
NS alarms
Alarm correlation and NS impact
VNF alarms
EM
VNF
Correlated Virtualised Resources alarms
Virtualised Resources alarms
VNFM
VNF application alarms
Correlate infrastructur e alarms to VNF
Virtualised Resources Alarms (VNF specific)
Alarms Corrective actions Correlation
VIM
34
NFV Public Web Pages
NFV Technology Page on ETSI WEB www.etsi.org/nfv NFV PoC Page on ETSI WEB www.etsi.org/nfv/nfv-poc
NFV Press Releases
http://www.etsi.org/index.php/news-events/news/700-2013-10etsi-publishes-first-nfv-specifications
http://www.etsi.org/index.php/news-events/news/764-2014-03onf-and-etsi-announce-strategic-collaboration-for-sdn-supportof-nfv
35
[email protected]
36
