Page tree
Skip to end of metadata
Go to start of metadata

Release D-Best practice update

Release-E

       One step-Orchestration option (VIM + <nfvo+vnfm> as a feature as part of mano-descriptor)

       Two Step-Orchestration Proposal for MANO - 1. Step 1 VIM Orchestration , Step 2 NFVO+SUT orchestration

Use cases to pursue by OPNFV MANO priority: vHelloWorld, vEPC/vIMS, vCPE,L3VPN,Edge Cloud...

Topic Title                        

Options          

OpenBaton                     Open-O => merged to ONAP                      OSM                                                           ECOMP    / ONAP                                                              
1 

MANO Component Configuration

Integration Blocks to opt over OPNFV MANO

OSS/BSS

NFVO       (MANO Func. Req. per IFA010 refer 2c for link below **)

VNFM       (MANO Func. Req. per IFA010 refer **)

OPNFV VIM (MANO Func. Req. per IFA010 refer **)

 External

Main NFVO Module

Opt(gVNFM, JuJu)

Opt(OPNFV,OpenStack)

 External

Main NFVO Module

Opt(gVNFM, JuJu)

Opt (OPNFV,OpenStack)

 

External 

Rift.io

opt(Juju, gFVFM)

OpenStack

AT&T OSS/BSS + App-C / VF-C

ECOMP (Designer Framework) -SDC

ECOPM(Execution Frame....) - NFVi + Multi VIM Broker to Cloud, (A&A)  Inventory

Openstack DC AnalyticsEvents (DCAE)

2

MANO Hierarchy for Catalog/Repos

MANO Configurations

saved in layered

Cat/Repos

files/descriptors

Cat.5/Repo.5

Cat.4/Repo.4

Cat.3/Repo.3

Cat.2/Repo.2

Cat.1/Repo.1

Cat.0/Run time Instance index

Marketplace

Global Catalog

 

 

Glance (Openstack)

Instance Catalog/HEAT

 

Marketplace

GSO

Application/Component

SDN-C Catalog

Glance (Openstack)

Instance Catalog/HEAT

MarketplaceMarketplace
 

 MANO APIs

NB(Service Access Points-Sap)

Os-Ma-nfvo(Os-Em)

Vnfm-Vnf(Vnfm-Em)

Uses Standard ETSI based APIs stage 2.Uses OpenStack APIs and in process to change to OANP APIsUses OpenVIM APISDefining ONAP APIs NB for VF-C and APP-C
  c

 MANO APIs

SB(Endpoints-Ep)

Or-Vi (IFA005), Vnfm-Vi (IFA006)  - **ETSI Published /Draft (stage 3) Specs

Or-Vnfm(IFA007) ,

   SB for Opentack/OPNFV  and commercial vendor VIMS
  d Scenario  Layered on OPNFV VIM

 (FUNCTEST based)

os-openbaton-nosdn-ha

os-openo-nosdn-nofeature migrating  to onap

NANA
3 

 NS Models & NSD

IFA014 ** Figure 6.2.1-1: UML information diagram of NSD

refer IFA014 for NSD Models 

refer IFA013 8.2.2 NsdInfo information element (NSD)

Simple TOOSCASimple TOSCA + YANG TOSCA + YANG
4 

NS LCM

 

Open loop

 

 

Closed loop

Manged by NFVO re per NS

Configure, Dispatch to VNFM and VIM repetitive tasks and finsih.

VNF changes triggers NS change & alarms to NFVO which analyze, process and complete policy /rule based workflow/tasks

    
5 VNFDrefer IFA011 7.1 VNF Descriptor (VNFD)    
6 VNF Package format (IFA011**)

CSAR

TGD

 

    
7 VNF On-boarding MetadataOnboard with Parameters    
8 

LCM Methods supported Hooks. & APIs

Lifecycle

CONFIG  SET/RESET Defaults

INIT

START /RUN

PAUSE/RESTART

SNAPSHOT

SCALE/UP-DOWN

SCALE/IN-OUT

STOP /TERMINATE

CLEANUP

    
9 SDK /Library

SDK for MANO/ Run Times

Dev

Test

Ops

    
10 Tools

Dev

Test

Ops

    
 11 

 Test Modules

 NFVO,VNFM,

NFVI-VIM(OPNFV)

    
 12 

 Test Use Cases

OPNFV,

Upstream

and CVP/Dovetail

vHelloWorld(Models

vIMS (FUNCTEST)

Orchestration

vEPC (FUNCTEST)

vEPC/vIMS (OAI)

L3VPN (SDNVPN)

vCPE(OPEN-O)

Edge Cloud (focusstack/kvm4nfv)

Continuing on VIMS. in OPNFV Release E.Trageted VIMS for Mercury + SUN with OPNFV Release D, before merging to ONAP. targets ; VoLTE & Home vCPE for Amsterdam (A-Release)
  • No labels

1 Comment

  1. We will use this to compare Processes of different MANO Stacks to see we have some Consistency across them for End User Experience, as per Action Item (AI1) in Meeting #18 we bring parts that are relevant to this