DEMOS - R8 Honolulu Demos

Description :  A 1-paragraph description of the demo

Demo Team :  list anyone that worked on the demo using wiki "@" tags - Solo submissions are OK

Projects : which ONAP projects are highlighted  e.g.: DCAE, Policy, OOF

Demo Date : use // macro

Logistics : Location of demo, lab resources utilized, etc. as appropriate

Slides :  attach a PDF version slides, or a link to a PDF version of the slidesc

Recording :  attach a the recording of the demo, or a link to the recording - MUST CONTAIN THE DEMO NAME

Wiki Page: link to the ONAP WIKI page for the demo or project if relevant

Description :  The A&AI community delivered extensive updates to the A&AI UI in the Honolulu release. The ability to browse network elements, topology, and form complicated queries with many built in features was implemented. This demo is to showcase the new functionalities delivered as part of the Honolulu release.

Demo Team :  @William Reehil @Venkata Harish Kajur

Projects : A&AI

Demo Date : Sep 3, 2021 

Logistics : Localhost demo (running from gerrit checked out repo on stubs)

Slides :  AAI-UI-ONAP-HONOLULU.pdf

Recording : AAI_UI_UPGRADES_HONOLULU.mp4

Wiki Page: N/A

Description :  This demo was done to showcase E2E Network Slicing use case with ONAP internal RAN and TN NSSMFs and external CORE NSSMF developed in H-Release.

Key features :

The demo covered 3 critical scenarios:

• Creation of a new E2E Network Slice with Core, RAN and TN Slices

• Reuse of an existing E2E Network Slice, and

• Closed Loop Automation based on PM data sent from the RAN Network Functions, for better allocation of RAN resources across different cells.

Highlights :

• This complex use case involved 8 modules of ONAP and was contributed by 7 companies from different geographical locations across the world.

• The RAN Simulator was enhanced to instantiate the RAN network functions, and used to demonstrate the complete flow from ONAP modules, as well as Closed Loop Automation.

• This use case is aligned with the relevant standard bodies such as 3GPP, IETF, TMF and O-RAN.

• The entire demo was executed live in WinLab with 80+ participants (virtually).

Demo Team :  @LIN MENG , @Swaminathan Seetharaman @Saravanan Ayyadurai ,@Ahila P  @Henry Yu , @Milind Jalwadi (Unlicensed) , @Borislav Glozman , @guochuyi  @krishna moorthy , @Reshmasree c ,@Deepika S ,@LUKAI ,  @Niranjana Y , @Former user (Deleted) , @Aleem Raja , @Zhang Min, @Sandeep Shah  @LTE Next Generation , @Hariharan Ramanathan , @Sumithra Sundar, @Keguang He , @Hesam Rahimi , @Former user (Deleted)

Projects : SO, OOF, SDN-C, DCAE, SDC, Policy, UUI and AAI, Simulators

Demo Date : Jun 8, 2021 

Logistics : The demo was given using the lab resources at WinLab, Rutgers University

Slides : E2E_Network_Slicing_Honolulu_Release_Demo.pdf

Recording: E2E_Network_Slicing_Honolulu_Demo_using_ONAP.mp4

Wiki Page: User_Operation_Guide_for_E2E_Network_Slicing

Description:  The goal of this demonstration was to show a successful deployment of an ML model as a DCAE service component(microservice) by taking advantage of the Acumos-ONAP federation. This implies that the ML model as a DCAE service component can access the DMaaP message router's APIs and successfully subscribe and publish to respective Kafka topics for reading test samples and publishing prediction output respectively. Based on this demonstration, the workshop paper - "Realization of an Intrusion Detection use-case in ONAP with Acumos" was presented at the 30th International Conference on Computer Communications and Networks (ICCCN 2021). 

Highlights:

The key features of this demo can be summarized as:

• It highlights the feasibility and reduction of effort during the journey of an ML model from being a Python script to a DMaaP compatible microservice.

• It describes the various involved components from Acumos and DCAE and the workflow or steps that can be followed for an automated conversion and deployment of any ML/AI model written in any of the Acumos supported languages and using corresponding ML tools/libraries into a DCAE service component.

Demo Team: @Shabnam Sultana @Vijay Kumar philippe.dooze@orange.com

Projects:  Acumos, DCAE, DMaaP

Demo Date:  Jul 22, 2021 

Logistics: This demo was accomplished using the Open SDN and NFV Lab(OSNL) at highstreet Technologies GmbH, Berlin.

Slides: Realization of an Intrusion Detection use-case in ONAP with Acumos.pdf

Recording:  Realization of an Intrusion Detection use-case in ONAP with Acumos.mp4

Wiki Page: Realization of an Intrusion Detection use-case in ONAP with Acumos

Description:  During this session, we presented a semi-live demonstration of the latest capabilities for CNF Orchestration, introduced in Guilin (CNF Adapter and Helm type) and developed in Honolulu (CNF Day2 support). The demonstration has shown the CNF/Helm onboarding and deployment process of vFW CNF Use Case which since the Honolulu release is enriched with config-assign/deploy workflow that performs the CNF configuration process. Moreover, the demonstration has shown how to track and validate the deployment status of CNF, and how to fetch information about the status of all resources deployed on the k8s cluster. vFW CNF Use Case plays an important role in ONAP as is demonstrated all the developed features for Native CNF orchestration path and in the same time, it is fully automated giving the ONAP users, interested in CNF deployments, very good ground and base for modifications of automation onboarding scripts for their own use cases.

Highlights: The agenda of the demo is following

• A brief overview of the current state of CNFO implementation

  • Day 0/1 with Helm Package

  • Day 2 Configuration

  • CNF Status

• Introduction of Scenarios available in the vFW CNF Use Case

  1. Simple Instantiation of CNF

  2. Profiling of the CNF deployment

  3. Post-Deployment Configuration of CNF

  4. CNF Healthcheck (can be mixed with #1, #2 and #3)

• Environment setup + insights of the automation scripts

• Scenario 3: Deployment of CNF with post-configuration

  • Explanation of the deployment process

  • Role of CDS in the Day 0/1/2 process

  • Verification of the deployment in the k8s cluster

• Scenario 4: Post-Deployment Healhtcheck on top of Scenario 3

Demo Team:  @Lukasz Rajewski @Michal Chabiera @Seshu Kumar Mudiganti @Konrad Bańka @Grzegorz Wielgosinski 

Projects:  SO, CCSDK/CDS, Multicloud, SDC, AAI, ONAP SDK

Demo Date:  Jun 8, 2021 

Logistics: This demo was presented on the LFN DTF June 2021 Event and is an outcome of the work accomplished for CNFO functionality and delivered for REQ-341 & REQ-458 

Slides: Native CNF Orchestration with Day2 support.pdf

Recording:  Native CNF Orchestration with Day2 support.mp4

Wiki Page: vFW CNF Use Case Description

Description:

The demo shows the work done in Honolulu to unify the Policy Framework and CLAMP projects. It gives a comprehensive demonstration of the Policy Instance UI and the Policy Tosca Model Management UI.

The demo shows how the Policy Instance Management UI allows users to create and manage the life cycles of policies in the Policy Framework. It shows how the UI also supports the deployment (activation) of policies onto PDP groups for use on PDPs in the Policy Framework. It demonstrates policies can be created from Policy Types, their properties being set and amended. It shows the policies being stored and deployed to PDP groups. The demo goes on to show the Policy TOSCA Model Management UI, demonstrating how the UI is used to manage the lifecycle of TOSCA models in the Policy Framework that policies use to set the data types of properties and other entities.

The demo goes on to describe the work done in the TOSCA defined Control Loop POC in Honolulu. It illustrates the flow of the control loop participant architecture and how it will create and manage services. Specifically, this demo shows the use of the control loop runtime's commissioning and instantiation API to trigger the deployment of the PMSH policy through the policy participant and the instantiation of the PMSH service through the DCAE participant. The DCAE participant uses the existing CLAMP backend to send requests and relay responses to the other participants and the runtime. There are several references to the states of the control loop and the control loop elements in this demo. Detail on the specifics of these states can be found here: The ONAP Policy Framework. This demonstration is not to be considered a reflection of the final implemented flow but merely as an indication of the currently implemented progress. The flow of the demo is shown in the image below.

Highlights: The agenda of the demo is following

• Introduction and Flow

• Prerequisites

• Setup CLAMP and MariaDB

• Alterations to CLAMP

• Build CLAMP

• Run and Pre-populate MariaDB

• Start the CLAMP Backend

• Setup and Run DMAAP Simulator

• Clone, Build and Run DMAAP Simulator

• Setup and Run Policy API

• Clone, Build and Run the Policy API

• Setup and Run Participant Runtime

• Setup and Run Policy Participant

• Setup and Run the DCAE Participant

• Setup and Start the Angular UI

• Starting and Monitoring the Deployment

Demo Team: @Sebastien Determe @Gervais-Martial Ngueko @Saul Gill @Liam Fallon @Sirisha Manchikanti @Robertas Rimkus @Former user (Deleted) @Francesco Fiora 

Demo Date:  Apr 19, 2021

Logistics: The demo was presented to the DCAE team including as part of the work completed by the team towards the Honolulu release of Control Loop.

Recording:

CLAMP Policy UI - part1 (policy instance managment)

CLAMP Policy UI - part2 (policy tosca model managment)

Participant Full Pipeline PMSH Deployment Demo - How to run...#DemoVideo

Wiki Page: Participant Full Pipeline PMSH Deployment Demo - How to run...

Slides: