This page is being made available for groups to begin fleshing out discussion topics for the joint sub-committee meetings. Having a consolidated view will help the subcommittee chairs set the agenda for each session.
room config
NOTE on room configurations for the Program Committee as you develop the schedule for the event.
- Joint Session - Almaden Ballroom, 150 people, round tables The Ballroom can be split into A and B at some point to provide smaller breakout spaces if needed. This will require a "wall pull" reconfiguration during a scheduled break.
It is recommend that large joint sessions be scheduled in a continuous block on Monday for as long as required and then again late on Tuesday for any joint follow-ups and summary sessions. - Breakout #1- Winchested Room, (2nd floor) 50 people, classroom configuration
- Breakout #2 - University Room, (ground floor) 30 people, round tables
- Breakout #3 - Almaden "A", 30 people round tables - unavailable during joint sessions
- Breakout #4 - Almaden "B", 30 people round tables - unavailable during joint sessions
Zoom Bridge Details:
<< kenny to fill in >>
Note to participants:
Please check back on the rooms - they may change as we know more about the participants in each session.
Agenda
Day 1: Monday 1st April
| Time | Almaden | Winchest Room (2nd floor) (50) | Universtity Room (ground floor) (30) | |||
|---|---|---|---|---|---|---|
| Almaden Ball Room (150) | ||||||
| Topic | Presentation | Topic | Presentation | Topic | Presentation | |
| 08:00 | Breakfast & Badges | |||||
| 08:15 | ||||||
| 08:30 | ||||||
| 08:45 | ||||||
| 09:00 | Opening Logistics | |||||
| 09:15 | All subcommittees - Dublin priorities | |||||
| 09:30 | ||||||
| 09:45 | ||||||
| 10:00 | TSC Tasks session 1 (Catherine Lefèvre ) | |||||
| 10:15 | ||||||
| 10:30 | Break | |||||
| 10:45 | Architecture / Modelling Joint subcommittee NSD representation (Thinh Nguyenphu ) | Seccom mini-camp | Sharing best practices | |||
11:00 | ||||||
| 11:15 | Security by design | |||||
| 11:30 | Architecture / Modelling Joint subcommittee Allotted Resource (Gil Bullard ) | |||||
| 11:45 | Vulnerability Management process review | |||||
| 12:00 | Lunch | |||||
| 13:00 | M-SDO (General) - ETSI NFV | Seccom mini-camp (cont) | Nexus-IQ and known vulnerabilities analysis | |||
| 13:15 | M-SDO (General0 - 3GPP SA5 (Thomas Tovinger) | |||||
| 13:30 | M-SDO (General0 - 3GPP SA5 | Seccom mini-camp (cont) | CII Badging | |||
| 13:45 | M-SDO (General) - 3GPP SA5 Q&A | |||||
| 14:00 | M-SDO (General) - BBF (Tim Carey ) | Dublin Controller Design Studio [CDS] - Intent based model driven Provisioning and Configuration Management. | SECCOM 2nd F2F meeting | Dublin goals and status updates | ||
| 14:15 | M-SDO (General) - BBF Q&A (Tim Carey ) | |||||
| 14:30 | Break | |||||
| 14:45 | M-SDO (General) - MEF | CDS (cont) | SECCOM 2nd F2F meeting (cont) | El Alto non-functional requirements | ||
| 15:00 | M-SDO (General) - MEF Q&A | |||||
| 15:15 | M-SDO (General) - TMF Update (Pierre Gauthier) | Available | Credential protection and management | |||
| 15:30 | Available | |||||
| 15:45 | Available | ONAP user management & access control big picture | ||||
| 16:00 | Break | |||||
| 16:15 | All subcommittee - ONAP - ZSM meeting Detailed Agenda to follow | |||||
| 16:30 | ||||||
| 16:45 | ||||||
| 17:00 | ||||||
| 17:15 | ||||||
| 17:30 | ||||||
| 17:45 | ||||||
| 18:00 | ||||||
| 18:15 | ||||||
| 18:30 | ||||||
| 18:45 | ||||||
Day 2: Tuesday 2nd April
| Time | Almaden | Winchest Room (2nd floor) (50) | Universtity Room (ground floor) (30) | |||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Almaden Ball Room (150) | Almaden "A" (30) | Alden "B" (30) | ||||||||
| Topic | Presentation | Topic | Presentation | Topic | Presentation | Topic | Presentation | Topic | Presentation | |
| 08:00 | Breakfast | |||||||||
| 08:15 | ||||||||||
| 08:30 | ArchCom | |||||||||
| 08:45 | ||||||||||
| 09:00 | Model driven Control Loop Design - Continue work from Dublin towards El Alto Self Serve Control Loops | ArchCom Orchestration Scenarios Fernando Oliveira et al | Use Case Subcommittee Alla Goldner | |||||||
| 09:15 | ||||||||||
| 09:30 | M-SDO (Modeling) - ETSI NFV | |||||||||
| 09:45 | ||||||||||
| 10:00 | SecCom F2F | ONAP Security Reuirements | ||||||||
| 10:15 | Break | |||||||||
| 10:30 | ONAP Security Reuirements | ArchCom Edge Automation Ramki et al | Use Case Subcommittee (cont) | |||||||
| 10:45 | ||||||||||
11:00 | Use case testing and Automation Integration Team | |||||||||
| 11:15 | ||||||||||
| 11:30 | ModCom Multiple SDO session Hui Deng to fill in | ArchCom Hierichal Orchestration Gil Bullard | ||||||||
| 11:45 | ||||||||||
| 12:00 | Lunch | |||||||||
| 13:00 | SecCom F2F (cont) | ONAP Security Reuirements | ArchCom | |||||||
| 13:15 | ||||||||||
| 13:30 | ArchCom | |||||||||
| 13:45 | ArchCom | |||||||||
| 14:00 | DataLake | |||||||||
| 14:15 | ArchCom | |||||||||
| 14:30 | ||||||||||
| 14:45 | Break | |||||||||
| 15:00 |
| |||||||||
| 15:15 | ||||||||||
| 15:30 | ArchCom & ModCom | |||||||||
| 15:45 | ||||||||||
| 16:00 | All subcommittees | |||||||||
| 16:15 | ||||||||||
| 16:30 | All Subcommitees Summary Each subcommitte chair to prepare | |||||||||
| 16:45 | continue | |||||||||
| 17:00 | ||||||||||
| 17:15 | ||||||||||
| 17:30 | ||||||||||
| 17:45 | ||||||||||
| 18:00 | ||||||||||
| 18:15 | ||||||||||
| 18:30 | x | |||||||||
The below proposal sheet is no longer active.
| Topic | To be filled in by the program committee only! | Requested by | Sub-C / Joint session | Requested Duration (15 min blocks) | notes, links, PDFs | |||
|---|---|---|---|---|---|---|---|---|
Day | Time Start | Time End | Room | |||||
| Meeting Logistics | 09:00 | 09:15 | Ballroom | Joint | 15 | Start of session, April 1 & 2 | ||
| Self Serve Control Loops | Breakout #1 or 2 (either works) | Control Loop Subcommittee | 60 | Continuation of the work proposal arising from Dublin's Model driven Control Loop Design | ||||
| Usecase subcommittee meeting | Ballroom or Breakout #1 | Usecase subcommittee | 90 | f2f meeting for use case and functional requirements - initial ideas for El Alto | ||||
| Usecase/architecture/closed loop/modelling subcommittee joint meeting | Ballroom | all ONAP subcommittees | 90 | big joint meeting on initial priorities for El Alto, how to handle them | ||||
| ONAP / ZSM introduction | Ballroom | Modeling & Arch | 180 | Multiple 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: Modeling | 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 general | Ballroom | 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 Meeting | Breakout 2# | modeling subcommittee | 120 | Regular modeling subcommittee meeting | ||||
| Orchestration Scenarios | ArchCom | 60 | Summarize requirements from the orchestration scenarios that have been agreed to and decision on how to proceed | |||||
| Orchestration Scenarios (Application Configuration) | Ballroom | Archcom/Modcom | 60 | 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 | ||||
| Summary or Readout of all subcommittee meeting | Ballroom | all | all | 60 | we probably need one hour to summarize or readout the output of the meetings | |||
| NSD internal representatino | Ballroom | Thinh Nguyenphu | Archcom/modecom | 60 | Current state, current conclusiosn and next step in the internal representation of the NSD | |||
| Edge Automation through ONAP | Ballroom or Winchester | ArchCom | 90 | https://wiki.onap.org/display/DW/Edge+Automation+through+ONAP+-+Distributed+Management+%28ONAP+etc.%29+components | ||||
| Controller Evolution | Ballroom or Winchester | John Ng, Vimal | ArchCom | 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 | Ballroom | ArchCom/modcom | 30 | What focus on Model driven ONAP do we want to have moving forward | ||||
| Allotted Resource | Ballroom | ArchCom/ModCom | 30 | This has been previously presented, time to recap the next steps and actions | ||||
| Hierachical Orchestration | Ballrooom or Winchester | 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 | Breakout #1 or 2 (either works) | all subcommittees | 60 | what would be most important non functional requirements to cover in El Alto | ||||
Progress on our ongoing TSC Tasks and get feedback about
| First Session Day1 Second Session Day 2 | 16:00 | 16:30 | University Room | ALL | 2 x 30 mins | ONAP TSC Dashboard: https://jira.onap.org/secure/Dashboard.jspa | |
2nd ONAP SECCOM F2F meeting | SECCOM | Full day | Closed SECCOM meeting focused on risk assessment based on penetration tests results, security priorities for El Alto release. | |||||
ONAP SECCOM mini-camp | All | 180 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 | Modeling | 30 min | Readout on progress and next steps in reverse engineering the AAI data model into Papyrus | |||||
| ONAP VNF deployment flows status | Modeling & Arch | 0 min | Session to clarify the current status and future status :
(merge with orchestration scenarios point) | |||||
| Introduction to use case testing and automation in Windriver Open Lab | Integration team | OpenLab & Usecase | 60 | The introduction is about how Integration team performs the following tasks in Windriver Open Lab:
| ||||
| Documenting ONAP and Documentation | Winchester | ArchCom | 30 | Open discussion about moving documenting onap forward and what needs to be document, potentially beyond what is ongoing. | ||||
| Evolution of ONAP CLI and connection to ONAP and managed elements | Winchester | ArchCom | 30 | Open discussion on Open CLI platfrom in connection with ONAP, PNF and VNF. (during the dublin arch review, this discussion was brougt up at Dublin M3 Architecture Reviews ) | ||||
| Architecture findings from documenting ONAP architecture | Archcom | 30 | List up some of the architecture issues identifiied while going through the process of documenting the ONAP architecture | |||||