Versions Compared

Key

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

...

Tableenhancer
numberOfFixedRows2
numberOfFixedColumns5
decimalMark. (point)


TopicTo be filled in by the program committee only!Requested bySub-C / Joint sessionRequested Duration
(15 min blocks)
notes, links, PDFs

Day

Time Start

Time End

Room

Meeting Logistics
09:0009:15BallroomJoint15Start of session, April 1 & 2
Self Serve Control Loops



Control Loop Subcommittee60Continuation of the work proposal arising from Dublin's Model driven Control Loop Design
CVC



ONAP/OPNFV Compliance120Continuation of CVC platform integration and compliance testing goals
Usecase subcommittee meeting



Usecase subcommittee90f2f meeting for use case and functional requirements - initial ideas for El Alto
Usecase/architecture/closed loop/modelling subcommittee joint meeting



all ONAP subcommittees90big joint meeting on initial priorities for El Alto, how to handle them
ONAP / ZSM introduction209:0012:00BallroomModeling & Arch180Multiple ONAP member organizations have requested that we explore opportunities for alignment and collaboration between our two orgs. This may set the stage for additional unconference sessions during ONS.
 M-SDO Part 1: Modeling2

Breakout 2# Modeling Subcommittee 60 about 80% of topics are related to modeling : Collect issues in ONAP related to M-SDOs
 M-SDO Part 2: ONAP general214:0016:00Ballroom ONAP general 180 about 20% of topics are general to ONAP community like 3GPP SA5/ BBF, Collect issues in ONAP related to M-SDOs, it beter to avoid overlapping with Archcom/Modelcom/Use case/Closed Loop Controll subcommittee
 Modeling subcommittee Meeting2

Breakout 2# modeling subcommittee 120 Regular modeling subcommittee meeting
Orchestration Scenarios



ArchCom60

Summarize requirements from the orchestration scenarios that have been agreed to and decision on how to proceed

https://wiki.onap.org/download/attachments/45300148/OrchestrationScenariosDDF.pptx?version=1&modificationDate=1547101731000&api=v2

Orchestration Scenarios (Application Configuration)



Fernando OliveiraArchcom/Modcom60

Joint meeting to make progress on defining the meaning of application configuration data, how application configuration data is defined during onboarding, how application configuration data is applied to the xNF and how ongoing application configuration data modifications are applied to the VNF during its lifetime

https://wiki.onap.org/download/attachments/45300148/ONAP_GNF_ControllersSOL003.pptx?version=1&modificationDate=1548619943000&api=v2

 Summary or Readout of all subcommittee meeting



 all all 60 we probably need one hour to summarize or readout the output of the meetings
NSD internal representatino





Archcom/modecom

60
Current state, current conclusiosn and next step in the internal representation of the NSD
 Edge Automation through ONAP



 ArchCom90 https://wiki.onap.org/display/DW/Edge+Automation+through+ONAP+-+Distributed+Management+%28ONAP+etc.%29+components
 Controller Evolution



John Ng, VimalArchCom 30 Previously the idea to have a controller personas created from CCSDK, what steps do we want to take for the El Alto release. 
Model Driven ONAP 



Ciaran Johnston ArchCom/modcom 30What focus on Model driven ONAP do we want to have moving forward 
 Service Mesh - next steps



ArchCom 45 Next steps in the service mesh evolution 
Allotted Resource 



ArchCom/ModCom 30 This has been previously presented, time to recap the next steps and actions 
Hierachical Orchestration 



ArchCom 45 This has been worked through previously with a few open issues.  Recap the options and actions to conclude on the next steps. 
non functional reqs kick-off for El Alto



Alla Goldnerall subcommittees60what would be most important non functional requirements to cover in El Alto

Progress on our ongoing TSC Tasks and get feedback about

  • Review Release Engagement Model across Subcommittees
  • How to accelerate the next ONAP Releases?
  • Adopt Tick-Tock Model
  • etc




ALL2 x 30 minsONAP TSC Dashboard: https://jira.onap.org/secure/Dashboard.jspa

2nd ONAP SECCOM F2F meeting





SECCOMFull dayClosed SECCOM meeting focused on risk assessment based on penetration tests results, security priorities for El Alto release.

ONAP SECCOM mini-camp





All180 mins

Session for community to share SECCOM best practices and collect feedback.

We would like to provide as much as possible information to make PTLs and ONAP community life easier in the domain of security: share best practices, explain some questions and analyze answers for CII Badging, present a demo on an efficient usage of NEXUS-IQ tool for known vulnerabilities analysis, review the process for vulnerability management, review answers for Milestone checklists etc. We would like also to propose a discussion on improving SECCOM processes from community perspective.

AAI Data Model in Papyrus



James ForsythModeling30 minReadout on progress and next steps in reverse engineering the AAI data model into Papyrus
ONAP VNF deployment flows status



Eric DebeauModeling & Arch30 min

Session to clarify the current status and future status :

  • paths to deploy VNF (we have may paths paths in Casablanca SO-VIM, SO-MultiCloud, SO-VFC, no SO) and we may have more for Dublin (SO-VNFM...)
  • impacts of service modeling, VNF onboarding
 ONAP VNF deployment flow status



Eric Debeau  Modelling & Arch 30 mins  Session to clarify the current status and future status :
  • paths      to deploy VNF (we have may paths paths in Casablanca SO-VIM,      SO-MultiCloud, SO-VFC, no SO) and we may have more for Dublin (SO-VNFM...)

impacts of service modeling, VNF onboarding

(Consider to merge with orchestration scenarios, if so this can be removed as a seperate topic)

Introduction to use case testing and automation in Windriver Open Lab



Integration teamOpenLab & Usecase60

The introduction is about how Integration team performs the following tasks in Windriver Open Lab:

  • ONAP OOM deployment from scratch
  • Use case testing and ONAP patching
  • Integration Daily CI
  • Use case automation with Robot Framework
Documenting ONAP and Documentation 



ArchCom 30 Open discussion about moving documenting onap forward and what needs to be document, potentially beyond what is ongoing. 


...