Orchestration Scenarios (Copy)

Owned by Chaker Al-Hakim
Last updated: Apr 28, 2020
9 min read

Members

Kickoff Materials

VZDeploymentOptions.pptx

Meeting Information

Weekly meeting: Mondays at 1200 UTC, 5AM PT, 8AM ET, 2PM CET, 5:30 PM India, 8PM China.

https://zoom.us/j/722438866

One tap mobile: +16699006833,,722438866#  US (San Jose)            +16465588656,,722438866# US (New York)

====================

Agenda for meeting on April 27, 2020

  1. Review ofVF2F meeting
  2. Other Topics?

Agenda for meeting on April 20, 2020

  1. Discuss presentation for VF2F meeting
  2. Other Topics?

Meeting recording: OrchestrationScenarios-20200420 1210-1.mp4

Agenda for meeting on April 13, 2020

  1. Other Topics?

Meeting recording: zoom_0.mp4

Agenda for meeting on April 6, 2020

  1. Adapter naming discussion
  2. Common components among the SOL adapters
  3. Continue on SOL001 AID discussion
  4. Other Topics?

Meeting recording:

Agenda for meeting on March 30, 2020

  1. Continue on SOL001 AID DM for VNF & NS discussion
  2. Update on SOL002, SOL003, SOL005 Adapters

March 30 recording: zoom_0.mp4.zip  Had to zip to get the file uploaded.

Agenda for meeting on March 23, 2020

  1. Continue on SOL001 AID DM for VNF & NS discussion
  2. Other Topics?

March 23 recording: zoom_0.mp4

Agenda for meeting on March 16, 2020

  1. SDC Guilin enhancements (Requirements, Epics and User stories) for ETSI package management - Byung (20 minutes)
  2. Meeting time discussion/poll for whether to move this meeting to 1200 UTC/8am ET for the duration of the daylight/summer time.
  3. Start SOL001 AID DM for NS and VNF Discussion
  4. Other topics

March 16 recording: zoom_0.mp4

Agenda for meeting on March 9, 2020

  1. IFA WG presentation on the IFA040 technical overview and others (30 minutes) - IFA WG FEAT17 CNF Presentation
  2. (Postponed) SDC Guilin enhancements (Requirements, Epics and User stories) for ETSI package management - Byung (20 minutes)
  3. other topics

March 9 recording: zoom_0.mp4

Agenda for meeting on March 2, 2020

  1. Presentation for NFV Release 2 Testing; API Conformance Testing Specification (ETSI Robot Test cases for testing SOL002/SOL003/SOL005, and all resources) by Pierre Lynch
    1. the latest draft: https://docbox.etsi.org/ISG/NFV/Open/Drafts/TST010_API_Conformance_Testing/NFV-TST010v241_0013.docx
    2. Robot test cases: https://forge.etsi.org/rep/nfv/api-tests
    3. Presentation slide deck: 
    4. The Plugtest information: https://www.etsi.org/events/1683-nfv-mec-plugtests
  2. SDC Requirement Discussions for Guilin
    1. Guilin release - functional requirements proposed list
  3. SDC-ETSI Catalog Manager direct interface - update

Agenda for meeting on February 24, 2020

  1. Recap ETSI NFV SOL presentation and follow-up actions
  2. Need alternate host for Mar 2
  3. ETSI NFV TST010 robot tests for SOL002/SOL003/005 testsuite:https://docbox.etsi.org/ISG/NFV/Open/Drafts/TST010_API_Conformance_Testing/NFV-TST010v241_0013.docx, https://forge.etsi.org/rep/nfv/api-tests
  4. Review updated Guilin requirements Guilin release - functional requirements proposed list
  5. Other??

Feb 24 recording: zoom_0.mp4

Agenda for meeting on February 17, 2020

  1. ETSI Catalog Manager proposal Byung-Woo Jun
  2. Review presentation for ETSI NFV SOL WG meeting on Feb 18, 2020
  3. SOL005 Adapter Status Sambasiva R Kokkirala
  4. SOL003 Adapter Status
  5. Review proposed requirements that Fernando Oliveiraentered for Guilin release - functional requirements proposed list
  6. Any other topics?

Feb 17 recording: zoom_0.mp4

Agenda for meeting on February 3, 2020

  1. ETSI Specification Update - Thinh Nguyenphu (Unlicensed)
  2. SOL005 Adapter Status - Verizon Team 
  3. SOL002 Adapter Status - Miroslaw Medrek
  4. SOL003 Adapter Status - Byung-Woo Jun  (May not be able to attend)
  5. Discuss ETSI Alignment presentation to ETSI at NFVSOL #128 2/18-2/20

Feb 3 recording: zoom_0.mp4

Agenda for meeting on December 23

  1. Discuss presentation for Prague DDF
  2. SOL003 Adapter in SO discussion

Dec 23 recording: zoom_0.mp4

Agenda for meeting on December 16

  1. Discuss ETSI Alignment presentation for Prague DDF
  2. Status of SOL002 contribution
  3. SOL003 Adapter Plugin for APP-C 

Agenda for Meeting on December 9

  1. Discussion on ETSI Alignment tasks for Guilin Release - Byung-Woo Jun
  2. SOL002 presentation - Miroslaw Medrek

Dec 09 recording:zoom_0.mp4

No Meeting on December 2 due to no agenda items

  1. Please let me know if you have an agenda item for Dec 9

Agenda for Meeting on August 26th 8am ET

  1. Discussion on the ETSI Alignment Architecture, ETSI Alignment Support, and scope for Frankfurt
  2. ETSI Package Management (Onboarding and Distribution), ETSI Package Management
  3. Other Topics

No meeting on September 2 due to US and India holidays

Agenda for Meeting on September 9th 8 am ET

  1. SOL005 Adapter Architecture and Operations for Frankfurt
    1. SOL004/SOL001 NS Onboarding and Distribution
    2. SOL005 Adapter Architecture, Design and Code Review
    3. SOL005 NBI Use cases and Use of API-Fabric for SOL005 NBI
  2. SOL002 Adapter High Level Discussion
  3. SOL004 Package Security - finalize the scope
  4. SOL003 Adapter Operations

Agenda for Meeting on September 16th 8 am ET

  1. ONAP-ETSI Catalog Manager & SO ETSI Catalog Management, ETSI Catalog Management
    1. CMCC will present the ONAP-ETSI Catalog Manager
    2. Team will discuss So ETSI Catalog Management by leveraging the ONAP-ETSI Catalog Manager
  2. ETSI Package Management
    1. SOL007 NS support
    2. SOL004 VNF/PNF support
  3. HPA support in the ETSI-Alignment & Granting with HPA, SOL003 Adapter Granting Section
    1. the presentation plan is under discussion with Intel and Ericsson
    2. VNF Level Homing requests are under discussion
  4. SOL002 Adapter Architecture and Operations for Frankfurt
    1. the presentation plan is under discussion with Samsung

Additional Discussion Topics for next meetings

  1. SOL003/SOL005/SOL002 Adapter Operations, SOL003 Adapter, SOL005 Adapter, SOL002 Adapter
  2. SOL001 VNFD Internal Representation (to SDC AID DM), SOL001 Mapping to SDC AID DM
  3. SOL001 NSD Internal Representation (to SDC Service), SOL001 Mapping to SDC AID DM
    1. Initial input, Internal NSD representation (Copy)
  4. SOL002 Adapter Deployment Location - APPC?
  5. Communication Security - AAF-based ONAP ETSI Adapters and external SVNFM/NFVO
  6. Vendor VNF Requirements (is ONAP-compliance required? on VES Event support and others)
  7. Application Configuration options via ETSI standards (e.g, through VNFM) or OSS/BSS/EM to VNF
  8. CNF support and Granting impact for Kubernetes-based Resource Management 
  9. Other Topics...

Agenda for Meeting on  August 19 9am ET - Done

  1. Discussion on scope of this task force
  2. Alternate Host for next 4 weeks as Fred will be away.
    1. Byung-Woo Jun (Ericsson) will cover Fred for next 4 weeks
  3. Other Topics?

==============================

Future

Continue review of the requirements for Frankfurt Release

Continue discussion on Application Configuration for ETSI MANO VNFs.

CDS directly to SOL003 instead of APP-C?

Future topics:

  1. Discussion on whether ETSI NFV VNF SOL003 should be a Controller or Adapter.  ONAP_GNF_ControllersSOL003.pptx
  2. Should VNF deploy/scale  (LCM actions)  be GNFC actions?
  3. How would this apply to containers?
  4. Please add any topics that you think should be included.

Assumptions:

  1. Operator has already deployed ETSI SOL003 compliant VNF Manager(s)
  2. Operator has already deployed ETSI SOL005 compliant NFVO(s)
  3. Operator has existing Service Assurance tools that VNF(s) interact with
  4. Operator is currently using proprietary mechanisms to configure NFs
  5. Operator has used above mechanisms to deploy SOL001/SOL004 compliant VNFs
  6. Operator has multiple VIMs; with different HW capabilities and configurations
  7. Operator desires to integrate ONAP into the existing environment

Objectives

  • Examine orchestration scenarios in order to determine if new architectural requirements are necessary
  • Develop recommendations for composition of the ONAP Service DM (How does the ETSI NFV SOL001 Network Service Descriptor supported?)
  • Develop recommendations for interfaces between the orchestration elements (OSS, SO, VF-C, VNFM, NFVO)
  • Develop recommendations for how ONAP controllers work with external orchestration elements (NFVO, VNFM, EMS)
  • Develop recommendations for how external Service Assurance interacts with DCAE and Policy
  • Develop recommendations on breaking ONAP into more modular consumable pieces (Margaret)

To Do's

  • Recommendation on whether an ONAP should support an E2E Service  that is composed of xNFs that are orchestrated by separate orchestrators (SO,  SO + external VNFM, VF-C, external NFVO) for next Arch meeting (Nov 13)
  •  Mapping of SOL005 APIs to ONAP NBI
  • Develop scenarios with stories about how ONAP could be used in near term brownfield  legacy environment Fernando Oliveira
  • Develop scenarios with stories about how a legacy environment could migrate off of a brownfield legacy environment towards a ONAP native model Fernando Oliveira
  • Describe how ONAP DCAE could be integrated with legacy Service Assurance platform Fernando Oliveira
  • Describe how legacy inventory system would interact with ONAP A&AI
  • Develop scenarios for how Application Configuration could be supported with enhanced SOL001 VNF-D using an external SOL003 compliant VNF Manager Fernando Oliveira 

Scope

GeneralDublinFrankfurtGuilin












Implications/Requirements

  1. External VNFM scenarios (ONAP acting as an OSS/NFVO):

    1. ONAP needs to ingest and save (without modification) a SOL004 CSAR package for later consumption by a SOL003 compliant VNF Manager (VNFSDK, SDC)
      1.  Original CSAR contents need to be preserved since some VNF Managers validate the manifest signatures of each file in the CSAR
    2. ONAP needs to ingest and interpret a SOL001 compliant VNF Descriptor in order to design an ONAP Service (VNFSDK, SDC)
    3. ONAP needs to understand resource requirements in the VNF-D for each deployment and scaling level (SO, A&AI, OOF)
      1. ONAP needs a way to ingest or create a VIM tenant/project space (SO, SOL003 Adapter, Multi-Cloud/VIM)
      2. ONAP needs to inventory  the VIM tenant/project resources and capacity (A&AI, Multi-Cloud/VIM)
      3. ONAP needs to confirm that the VIM resources (vCPU, RAM, Storage, Network, EPA (SR-IOV, GPU, Pinnned CPU, Locked RAM, ..), ...) necessary for the deployment or scale operation are available (SO, A&AI, OOF)
      4. Such resources should be reserved if the VIM has that capability (OOF, Multi-Cloud)
    4. ONAP needs to have a SOL003 compliant SBI (SOL003 Adapter, APP-C, VF-C, GNF-C, SO))
    5. ONAP needs a mechanism for specifying that a VNF instance should be runtime managed by a particular VNFM type (design time)  and instance (run time) (SDC, OOF, SO)
      1. This likely also applies to other external controllers
    6. ONAP needs to have a way to inventory a VNF that was deployed using an external VNFM and which instance of the VNFM (A&AI, SO, SOL003 Adapter, VF-C) 
  2.  External NFVO scenarios (ONAP acting as an OSS or hierarchical Service Orchestrator):
    1. ONAP needs to ingest and save (without modification) a SOL004 CSAR package for later consumption by a SOL005 compliant NFVO (VNFSDK, SDC)
    2. ONAP needs to ingest and interpret a SOL001 compliant VNF Descriptor in order to design an ONAP Service (VNFSDK, SDC)
    3. ONAP needs to have an SBI that can be used to manage external Service(s) (SO, SOL005 Adapter)
      1. ETSI NFV MANO SOL005 Os-Ma-nfvo interface
        1. ONAP needs to be able to convert an ONAP Service into a SOL001 compliant Network Service Descriptor (SOL005 Adapter)
      2. VF-C "internal SOL005" interface
      3. ONAP Service NBI
      4. Open Source Mano (OSM) NBI
    4. ONAP needs a mechanism for specifying that a service should be runtime managed by an external NFVO (SDC, SO, A&AI)
    5. ONAP needs to have a way to inventory a Service that was deployed and managed by an external Service Orchestrator (A&AI, SO, SOL005 Adapter)
    6. ONAP needs a way to ingest and save (without modification) a SOL007 Network Service Package) (VNFSDK, SDC)
    7. ONAP needs to ingest and interpret a SOL001 compliant Network Service Descriptor (SDC, SO)
      1. Possibly translating it into an ONAP Service
    8. ONAP needs to be able to design a hierarchical Service that references zero or more VNFs along with one or more "sub-services" (Alloted Resources??) (SDC, SO)
  3. VNF Application Configuration over SOL003 ModifyVnfInfo interface using an External vendor specific VNF Manager
    1. ONAP needs to ingest and interpret a SOL001 compliant VNF Descriptor that includes ConfigurableProperties (VNFSDK, SDC)
    2. ONAP needs to present these ConfigurableProperties in the design of an ONAP Service (SDC)
    3. Upon Service deployment, ONAP needs to pass the application ConfigurableProperties along with the related values to the external VNFM that was used to deploy the VNF using the SOL003 ModifyVnfInfo interface (SO, APP-C, SOL003 Adapter)
    4. As part of a Change Management operation, ONAP needs to pass the updated ConfigurableProperties and new values to the  external VNFM that was used to deploy the VNF using the SOL003 ModifyVnfInfo interface (SO, APP-C, SOL003 Adapter)
    5. As part of an ONAP recovery operation, ONAP needs to query the VNF to get the current state and values of the ConfigurableProperties using the external VNFM that was used to deploy the VNF using the SOL003 Query interface (SO, APP-C, SOL003 Adapter)

Contributions...

Recording of call 11/12/2018: double_click_to_convert_01.zoom

Recording of call Dec 17, 2018: [Onap-arc] Orchestration Scenarios and implications on modeling weekly-20181217 1404-1.mp4

VZDeploymentOptionLegacy.pptx

Updated with Application configuration and Hierarchical Service (VNF + NS): VZDeploymentOptionLegacy.pptx

https://docbox.etsi.org/ISG/NFV/Open/Other/Tutorials/Tutorials-201810_SDN_NFV_World_Congress-The_Haque/ETSI_NFV_Layer123_VNF%20Configuration-v2_RX15009.pdf

Recording of Dec 20, 2018 call: [Onap-arc] Orchestration Scenarios Discussion on ETSI VNFD ConfigurableProperties-20181220 1806-1.mp4

OrchestrationScenariosDDF.pptx

ONAP_GNF_ControllersSOL003.pptx

ApplicationConfigElAlto.pdf

OrchestrationScenariosEF2F.pdf

Meeting Notes and Recordings

DateNotesRecording
August 12, 2019
  1. Move Meeting time one hour Earlier
None
August 19, 2019
  1. Need coordination between API Fabric work and the ONAP SOL005 NBI Adapter
  2. Need to add APP-C block into the ETSI diagram
  3. Need follow-up on how the SOL003 LCN and Indicator interfaces flow through the SOL003 Adapter
    1. May need to bring detail the GNF-C flows and how that would replace the direct SOL003 Adapter interface from SO
  4. For package security, the SDC will validate the vendor package.  The original package will be saved in the ONAP ETSI catalog and passed to the any external VNFM, VF-C or external NFVO which may also do validate the package independently
  5. Frankfurt scope table added with initial scope proposal

OrchestrationScenariosAug19.mp4

audio_only.m4a

August 26, 2019
  1. Discussion on the ETSI Alignment Architecture, ETSI Alignment Support, and scope for Frankfurt
    1. Went over the meeting topics for the next meetings, as scope discussions
    2. For now, SOL007 package onboarding is out of scope
    3. Use of GNFC for ETSI Alignment is under discussion, most likely out of scope
    4. Verizon will go over the SOL005 Adapter architecture, design and use cases at the next meeting 
    5. CMCC will go over the ONAP-ETSI Catalog Manager at the next meeting
    6. Samsung will present the SOL002 Adapter use cases and design soon
    7. It would be possible that VNFs are not compliant. For that, Connections between the DCAE and VNF through the SOL003 Adapter need to be enhanced. We may need another component which can translate SOL002/SOL003 APIs to VES event. Will discuss it further.
  2. No meeting next Monday due to US and India holidays

OrchestrationScenariosAug26.mp4

September 9, 2019
  1. Verizon presented the SOL005 Adapter architecture and use cases
    1. SOL005 Adapter architecture refactoring was discussed (decouple it from the current SO VFC adapter architecturally)
    2. NS Package handling was discussed.
      1. Support of SOL007 (NS package) was discussed.
      2. Thinh suggested to use SOL007 for NS Package, and SDC PTL will be contacted for SDC SOL007 support in Frankfurt
  2. Samsung presented the SOL002 Adapter use cases
  3. Next week, the team will discuss HPA, HPA-based Granting, VNF-Level Homing, CMCC ONAP-ETSI Catalog Management

OrchestrationScenariosSept9.mp4

September 16, 2019
  1. SOL007 is proposed for NS packages.
    1. SDC needs to be enhanced to handle SOL007 package onboarding and distribution
    2. it would be similar to SOL004 package onboarding and distribution
    3. Some impacts on SO and VFC are discussed
    4. Editing vendor NSDs at SDC was raised. Do we allow this editing and how to distribute the enhanced vendor NSDs?
  2. SOL004 is used for VNF and PNF packages.
    1. SDC already supports SOL004 package onboarding and distribution
    2. Editing vendor VNFD/PNFD at SDC was raised. Do we allow this editing and how to distribute the enhanced vendor VNFDs/PNFDs?
  3. Package Security was discussed
    1. ONAP will handle vendor package security (signature and certificate); SDC does not generate its own signature and certificate for SDC AID DM
    2. This issue will be discussed separately in a future meeting
  4. ONAP-ETSI Catalog Manager use cases and design were presented
    1. SO will invoke the Catalog Manager APIs to initiate NS, VNF and PNF packages by sending the csar id.
    2. The Catalog Manager will get the package files from SDC
    3. The Catalog Manager provides package management APIs for the SOL003/SOL005 Adapters
  5. Samsung presented SOL002 Adapter use cases
  6. HPA and Granting
    1. To centralize HPA, all the granting and allocation decisions should go through OOF
    2. Currently, OOF supports service-level homing request APIs, 
    3. For bottom-up VNF requests (e.g., close loop, scaling/healing requests that are initiated by VNF), the vnf-level homing request APIs should be supported since those requests do not have service association. 
    4. OOF internal graph might need to be enhanced to support reverse search from the VNF.
    5. Use cases were presented to the OOF team, and we will discuss more off-line

OrchestrationScenariosSept16.mp4