...
| 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 | 180 | about 80% of topics are related to modeling : Collect issues in ONAP related to M-SDOs | |
| M-SDO Part 2: ONAP general | ONAP general | 60 | 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 | |
| Summary or Readout of all subcommittee meeting | all | all | 60 | we probably need one hour to summarize or readout the output of the meetings |