Versions Compared

Version Old Version 1 New Version 2
Changes made by

Michela Bevilacqua

Michela Bevilacqua

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.



Members

Kickoff Materials

VZDeploymentOptions.pptx

Meeting Information

Weekly meeting: Mondays at 9am ET.

https://zoom.us/j/722438866

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

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

Second weekly meeting: Thursday at 6pm ET (Not currently active)

https://zoom.us/j/663496207
One tap mobile: +16699006833,,663496207# US (San Jose)                +16465588656,,663496207# US (New York)

Next meetings on April 29 at 9 am ET





Kickoff Materials/Background

Meeting Information

Meetings when needed

Next meetings in week 18 to be called .

Agenda:


Discussion on El Alto targeted Jira ARCH Subcommittee jira Stories: 

Jira Legacy
serverSystem Jira

serverId4733707d-2057-3a0f-ae5e-4fd8aff50176keyONAPARC-403 Jira LegacyserverSystem Jira

columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyONAPARC-

388
  • Jira Legacy
    serverSystem Jira
    serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
    keyONAPARC-389
  • Jira Legacy
    serverSystem Jira
    serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
    keyONAPARC-390
  • Jira Legacy
    serverSystem Jira
    serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
    keyONAPARC-482
  • Jira Legacy
    serverSystem Jira
    serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
    keyONAPARC-483
  • Jira Legacy
    serverSystem Jira
    serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
    keyONAPARC-484

    • Presentation from Samsung Ranny Haiby on SOL002 interface 

    View file
    nameONAP-SOL00X-Samsung-proposal-ver.3.1.pptx
    height150

    470


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

    Future

    Continue review of the requirements for El Alto Release

    View file
    nameOrchestrationScenariosEF2F.pptx
    height150

    Continue discussion on Application Configuration for ETSI MANO VNFs.

    View file
    nameApplicationConfigElAlto.pdf
    height150

    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. Does 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 

    Implications/Requirements

    External VNFM scenarios (ONAP acting as an OSS/NFVO):
    Gliffy
    nameONAP-SOL003-VNFM
    pagePin2
    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) 
  •  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)
  • 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

    Objectives

    • Identify target architecture for LCM API consolidation across different Controller : APPC, SDNC including CDS

    • Identify migration path need

    • Identify ONAP reccomendations in case of

      • -a new LCM operation

      • -a new UC/sw contribution with current LCM operations

    • El Alto/Frankfurt way forward


    To Do's

    •  

      Identify Target Architecture

    •  

      El Alto improvements identifications

    •  

      Frankfurt overall impacts

    •  

      MIgration Path need for APPC/SDNC

    •  

      LCM API evolution rules

    •  

      Identify component candidates for CCSDK


    Target Architecture

    Image Added

    • SO/Policy communicate to GnfC using grpc via Self Service API.

    El Alto improvements

    • External SOL003 Adapter as an Independent deployable component

    Frankfurt step

    Image Added

    Description

    Frankfurt impacts

    Contributions...