...
| 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 | |
| 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 | ramki krishnan | ArchCom | 60 | https://wiki.onap.org/display/DW/Edge+Automation+through+ONAP+-+Distributed+Management+%28ONAP+etc.%29+components |
| Controller Evolution | ? | 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 | ? | ArchCom | 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 |
| Allocated Resource | ? | ArchCom/ModeCom | 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 founctional reqs kick-off for El Alto | Alla Goldner | all subcommittees | 60 | what would be most important non functiobal requirements to cover in El Alto |