IFA007: VNF LCM The Or-Vnfm reference point is used for exchanges between Network Functions Virtualization Orchestrator (NFVO) and Virtualized Network.

Slides:



Advertisements
Similar presentations
ETSI NFV Management and Orchestration - An Overview
Advertisements

FI-WARE – Future Internet Core Platform FI-WARE Cloud Hosting July 2011 High-level description.
OSCAR Project Proposed Project for OPNFV
HA Scenarios.
BoF: Open NFV Orchestration using Tacker
Open Source and Info Models 17 Dec 2015 Bryan Sullivan, AT&T.
Specific SDK Specific SDK NFVO Specific VNFM Specific VNFM VNF Message Queue JSON REST API.
Project Tacker Open Platform for NFV Orchestration V1.1 / 02/16/16.
14 March 2016 Bryan Sullivan, AT&T Artur Tyloch, Canonical
Benoit Claise Mehmet Ersue
Domino: Template Distribution Service Basic Architecture and Brief Background contacts:
Project Tacker Open Platform for NFV Orchestration OPNFV Design Summit.
When RINA Meets NFV Diego R. López Telefónica
Service Design & Onboarding
SDN-O LCM for Mercury Release Key Points and Overview
Open-O SFC.Mgr Proposal
ARC: Definitions and requirements for SO/APP-C/VF-C discussion including call notes Chris Donley July 5, 2017.
ONAP and MEF LSO External API Framework Functional Reference Architecture 12 July 2017 Andy Mayer, Ph.D. © 2016 AT&T Intellectual Property. All rights.
Mapping between NFV model and TOSCA
ETSI NSD Overview & TOSCA model Thinh Nguyenphu, Nokia thinh
VNF Package CSAR Format Tal Halfon, Amdocs Andrei Kojukhov, PhD, Amdocs Aug 3, 2017.
VNF Package CSAR Format Tal Halfon, Amdocs Andrei Kojukhov, PhD, Amdocs Aug 3, 2017.
Orchestration and Controller Alignment for ONAP Release 1
draft-bernini-nfvrg-vnf-orchestration
OPEN-O Modeling Directions (DRAFT 0.6)
ETSI NFV: IFA & SOL specifications list
VNF Package CSAR for ONAP Release 2 – adding Telco grade features Andrei Kojukhov, PhD, Amdocs Oct 6, 2017.
Change Log VNF Package Model Business Compute Req.
OPEN-O Multiple VIM Driver Project Use Cases
ARC: Definitions and requirements for SO/APP-C/VF-C discussion Chris Donley Date , 2017.
ARC 5: Deployment Options Chris Donley
ECOMP Information Model
17 Dec 2015 Bryan Sullivan, AT&T
VNFD and NSD modeling: Rel2 Thinh Nguyenphu, Nokia thinh
A Service Provider using VNF Requirements as prototype text for RFPs to acquire VNFs to run in an ONAP context ONAP.org VNF Requirements Project VNF Provider.
Deployment Flavour as VNF Capability: Alt1_r3
ETSI NSD Overview & TOSCA model Thinh Nguyenphu, Nokia thinh
Instantiation Level, Scaling Aspect, Scale Info
Approach to finalize the TOSCA NFV profile
VoLTE remaining requirements Auto & manual Scaling
DF design as a node type.
Deployment Flavor Model – Challenges and Emerging trends for ONAP adaptation Priya TG, NetCracker Technology.
OASIS TOSCA Report for December ONAP Modeling Workshop
VF-C R2 Feature Planning & Implementation Yan Yang
Christopher Donley Prakash Ramchandran Ulas Kozat
Documenting ONAP components (functional)
ACTN Information Model
DPACC Management Aspects
DF design as a node type (output by Chris and shitao)
DF design as a node type (output by Chris and shitao)
Lixiang,YaoguangWang, ChangMing Bai,
Management and Orchestration in Complex and Dynamic Environment
“Deployment Flavor” Concept Desired End-Goal
VNF Package Model Per ETSI NFV SOL001, SOL004, SOL005
ONAP modeling report shitao.
VDU proposal comparison
VNFD Overview & TOSCA model Thinh Nguyenphu, Nokia thinh
New VDU model proposal.
DF design as a node type (output by Chris and shitao)
ONAP & ETSI NFV converged architecture
Deployment Flavour as VNF Capability: Alt1_r2
NFV adhoc Shitao li.
VDU proposal comparison
Open Source Projects Collaborations with ONAP
NFV adhoc Shitao li.
VNF Package CSAR Format Tal Halfon, Amdocs Andrei Kojukhov, PhD, Amdocs Aug 3, 2017.
SOL003 Adapter Architecture, Technical Debt and Roadmap
GNFC Architecture and Interfaces
Proposed Approach for ONAP Runtime Support of Network Service Onboarding Gil Bullard, AT&T.
TOSCA Orchestration Paradigm
Presentation transcript:

IFA007: VNF LCM The Or-Vnfm reference point is used for exchanges between Network Functions Virtualization Orchestrator (NFVO) and Virtualized Network Function Manager (VNFM) [ETSI GS NFV-IFA 007]. It supports a number of interfaces of which the VNF Lifecycle Management interface is of particular interest (produced by VNFM, consumed by NFVO). On this interface, the following operations are defined: • Create VNF Identifier • Instantiate VNF • Scale VNF • Scale VNF to Level • Change VNF Flavour • Terminate VNF • Delete VNF Identifier • Query VNF • Heal VNF • Operate VNF • Modify VNF Information • Get Operation Status For performing these operations, the VNFM relies on the VNFD, per IFA007. Note: Get Operation Status & Query VNF: There is no special VNFD requirement for this operation.

VNF LCM descriptions Operation Support by VNF Explanation Instantiate VNF Mandatory Allocate virtualised resources, configure them, start the application, trigger configuration of the application. Scale VNF Optional Change the amount of virtualised resources allocated to a VNF. Scale VNF to Level This operation scales an instantiated VNF of a particular DF to a target size. The target size is either expressed as an instantiation level of that DF as defined in the VNFD, or given as a list of scale levels, one per scaling aspect of that DF. Instantiation levels and scaling aspects are declared in the VNFD. Query VNF Obtain runtime information about the VNF instance (VnfInfo). Terminate VNF Terminate the VNF, and release the virtualised resources. Change VNF flavour Change the deployment flavor of the VNF, which typically includes changing the amount of virtualised resources, and the topology. Heal VNF Virtualisation-related corrective actions to repair a faulty VNF, and/or its VNFC instances and internal VNF Virtual Link(s). Operate VNF Start or stop the VNF software. Modify VNF Info Change certain items of the VNF runtime information (VnfInfo). Modify configuration Providing configuration parameters information for a VNF instance   Note: this operation is classified as a “Configuration Management” operation in IFA007. It is not under LCM operation.

modify_configuration tosca.interfaces.nfv.vnf.lifecycle.xxx lifecycle.Basic lifecycle.Healable lifecycle.Scalable lifecycle.Custom instantiate terminate modify_information modify_configuration change_flavour operate heal scale scale_to_level do_something NFV Profile Operations Operations Operations Operations This proposal, [NFV Profile] introduces a set of new TOSCA Interface Types: Basic, Healable, Scalable and Custom. [TOSCA YAML Profile] has introduced create, configure, start, stop, delete. To fulfill IFA007 VNF LCM requirements, the “create” and “delete” operations from [TOSCA YAML Profile] and all of the operation from [NFV Profile] are used. Mapping: “create” operation to a VNF on the network service level is mapped to “Create VNF identifier” + “Instantiate VNF” operations on the Or-Vnfm interface. Instantiate VNF mapped to lifecycle.Basic: instantiate operation from VNFD. Mapping: “delete” operation to a VNF on the network service level is mapped to “Terminate VNF” + “Delete VNF identifier” operation on the Or-Vnfm interface. Terminate VNF mapped to lifecycle.Basic terminate operation from VNFD Mapping: “start” and “stop” operations to a VNF on the network service level is mapped to “Operate VNF” operations on the Or-Vnfm interface. lifecycle.Standard create configure start stop delete TOSCA YAML Operations