Day 1: Monday 1st April
(PST) | Almaden Ball Room | Presentations & Recordings | Winchester Room | Presentations & Recordings | University Room | Presentations & Recordings |
|---|---|---|---|---|---|---|
| 09:00 | Opening Logistics | |||||
| 09:15 | All subcommittees - El Alto priorities | |||||
| 09:30 | ||||||
| 09:45 | ||||||
| 10:00 | ||||||
| 10:15 | ||||||
| 10:45 | Architecture / Modelling Joint subcommittee
ONAPARC-269
-
Getting issue details...
STATUS
| Seccom mini-camp | Sharing best practices | |||
11:00 | ||||||
| 11:15 | Security by design | |||||
| 11:30 | Architecture / Modelling Joint subcommittee ONAPARC-475 - Getting issue details... STATUS | |||||
| 11:45 | Seccom mini-camp | Vulnerability Management process review
| ||||
| 13:00 | M-SDO (General) - ETSI NFV | addl Q & A | Seccom mini-camp (cont) | Nexus-IQ and known vulnerabilities analysis | ||
| 13:15 | M-SDO (General) - 3GPP SA5 (Thomas Tovinger) | |||||
| 13:30 | Seccom mini-camp (cont) | CII Badging | ||||
| 13:45 | ||||||
| 14:00 | Controller Design Studio (CDS) | Intent based model driven Provisioning and Configuration Management. Doc, Demo & Next steps | SECCOM 2nd F2F meeting | Dublin goals and status updates | ||
| 14:15 | ||||||
| 14:45 | SECCOM 2nd F2F meeting (cont) | El Alto non-functional requirements | ||||
| 15:00 | ||||||
| 15:15 | M-SDO (General) - TMF Update (Ken Dilbeck) | Credential protection and management | ||||
| 15:30 | ||||||
| 15:45 | ONAP user management & access control big picture | |||||
| 16:15 | All subcommittee - ONAP - ZSM meeting Detailed Agenda:
ONAPARC-476 - Getting issue details... STATUS | |||||
| 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 (PST) | Almaden Ball Room Bridge ONAP1: https://zoom.us/j/763817885 | Winchester Room Bridge ONAP4: https://zoom.us/j/472117560 | University Room Bridge ONAP5: https://zoom.us/j/659197426 | Almaden "A" Bridge ONAP1: https://zoom.us/j/763817885 | Almaden "B" Bridge ONAP2: https://zoom.us/j/396864699 | |||||
| 08:00 | Breakfast | |||||||||
| 08:15 | ||||||||||
| 08:30 | ArchCom ONAPARC-436 - Getting issue details... STATUS | |||||||||
| 08:45 | ||||||||||
| 09:00 | Model driven Control Loop Design - Continue work from Dublin towards El Alto Self Serve Control Loops Agenda: 2019-04-02 Control Loop Sub Committee Weekly Meeting - Silicon Valley Sub Committee Meetings | ArchCom
ONAPARC-320
-
Getting issue details...
STATUS
|
| Case Subcommittee Alla Goldner Release 6 (Frankfurt) proposed use cases and functional requirements | ||||||
| 09:15 | ||||||||||
| 09:30 | ||||||||||
| 09:45 | M-SDO (Modeling) - ETSI NFV | |||||||||
| 10:00 | SecCom F2F | ONAP Security Reuirements | ||||||||
| 10:15 | Break | |||||||||
| 10:30 | DM Progress in Dublin.02.pptx | ONAP Security Reuirements |
| Use Case Subcommittee (cont) | ||||||
| 10:45 | ||||||||||
11:00 | Use Case Testing and Automation | |||||||||
| 11:15 | ||||||||||
| 11:30 | ArchCom Hierarchical Orchestration Presentation - 2019 04 02.pptx ONAPARC-477 - Getting issue details... STATUS |
| ||||||||
| 11:45 | ||||||||||
| 12:00 | Lunch | |||||||||
| 13:00 | SecCom F2F (cont) | ONAP Security Reuirements | ArchCom ONAPARC-478 - Getting issue details... STATUS |
| ||||||
| 13:15 | ||||||||||
| 13:30 |
| |||||||||
| 13:45 | ||||||||||
| 14:00 | DataLake Architecture and Implementation | ArchCom Architecture Findings from documenting Architecture Stephen Terrill ONAPARC-479 - Getting issue details... STATUS |
| |||||||
| 14:15 | ArchCom ONAPARC-234 - Getting issue details... STATUS | |||||||||
| 14:30 | ||||||||||
| 14:45 | Break - BALLROOM RECONFIGURATION | |||||||||
| 15:00 |
|
| ||||||||
| 15:15 | ||||||||||
| 15:30 | ArchCom & ModCom ONAPARC-320 - Getting issue details... STATUS |
| ||||||||
| 15:45 | ||||||||||
| 16:00 | ONAP Release Cadence Proposal |
| ||||||||
| 16:15 | ||||||||||
| 16:30 | Control Loop Subcommittee Summary | |||||||||
| 16:45 | All Subcommittees Summary Each subcommittee chair to prepare |
| ||||||||
| 17:00 | continue | |||||||||
| 17:15 | ||||||||||
| 17:30 | ||||||||||
| 17:45 | ||||||||||
| 18:00 | ||||||||||
| 18:15 | ||||||||||
| 18:30 | x | |||||||||
6 Comments
Stephen Terrill
Hi Kenny, Do you know whether when the Almaden room is partitioned into two rooms - if there will be the possiblity to have remote access and connections?
BR,
Steve
Kenny Paul
Each room should have a mixer that can used independently, so yes.
ravi rao
El Elto Priorities discussion : Can we get a vote from all SPs which feature/component of ONAP is the most wanted and widely accepted one so that community can concentrate on hardening those components. Also this can give us a path on creating well defined APIs and interfaces to these components so that these can be integrated with other third party components.
Marc-Alexandre Choquette
Here are the ones we use the most, (i.e. with the most production experience on) @ Bell:
These are the most critical ones based on our current needs. Then, we are also working with or are in the process of operationalizing:
Ones we keep an eye on based on provided functionality & our needs:
We may also want to consider having project maturity levels - similar to the one CNCF has with its projects (Sandbox/Incubation/Graduated,etc.) to better understand how usable these projects are.
Eric Debeau
Marc-Alexandre Choquette Good idea to follow the maturity levels defined by CNCF.
Stephen Terrill
There are defined maturity levels in ONAP in the technical charter, formally all are currently in incubation. Maybe it is time to discuss which projects are ready to move to the next step. First a criteria needs to be worked through.