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.
| Topic | Requested by | Sub-C / Joint session | Duration (15 min blocks) | notes, links, PDFs |
|---|---|---|---|---|
| Meeting Logistics | Joint | 15 | Start of session, April 1 & 2 | |
| Self Serve Control Loops | Control Loop Subcommittee | 60 | Continuation of the work proposal arising from Dublin's Model driven Control Loop Design | |
| CVC | ONAP/OPNFV Compliance | 120 | Continuation of CVC platform integration and compliance testing goals | |
| Usecase subcommittee meeting | Usecase subcommittee | 90 | f2f meeting for use case and functional requirements - initial ideas for El Alto | |
| Usecase/architecture/closed loop/modelling subcommittee joint meeting | all ONAP subcommittees | 90 | big joint meeting on initial priorities for El Alto, how to handle them | |
| ONAP / ZSM introduction | 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 | 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 | 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 | 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) | Fernando Oliveira | 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 | 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 | ArchCom | 90 | https://wiki.onap.org/display/DW/Edge+Automation+through+ONAP+-+Distributed+Management+%28ONAP+etc.%29+components | |
| Controller Evolution | 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 | Ciaran Johnston | ArchCom/modcom | 30 | What 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 Goldner | 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
| 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 | James Forsyth | Modeling | 30 min | Readout on progress and next steps in reverse engineering the AAI data model into Papyrus |
| ONAP VNF deployment flows status | Eric Debeau | Modeling & Arch | 30 min | Session to clarify the current status and future status :
|
| ONAP VNF deployment flow status | Eric Debeau | Modelling & Arch | 30 mins | Session to clarify the current status and future status :
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 team | OpenLab & Usecase | 60 | The introduction is about how Integration team performs the following tasks in Windriver Open Lab:
|
| Documenting ONAP and Documentation | ArchCom | 30 | Open discussion about moving documenting onap forward and what needs to be document, potentially beyond what is ongoing. |