| Area Name | Area Name and Description | Coordinator Role Description | Reporting Cadence | Date Created | Status | Coordinator | 5G area | Coordinate activities around 5G, including but not limited to 3GPP, ORAN, ORAN-OSC, IEEE | - Drive collaboration with ONAP on key edge open source & standards initiatives
- Concrete near-term & long-term recommendations based on above and other inputs to
- ONAP architecture subcommittee
- ONAP modelling subcommittee
- ONAP requirement subcommittee
- ONAP security subcommittee
| Report progress periodically | Apr. 30, 2019 | Active | Covered by ONAP Requirement Subcommittee
AI (ML/DL) area | Coordinate activities aroinf AI (ML/DL) including Acumos, ETSI ENI etc. | - Drive collaboration with ONAP on key edge open source & standards initiatives
- Concrete near-term & long-term recommendations based on above and other inputs to
- ONAP architecture subcommittee
- ONAP modelling subcommittee
- ONAP requirement subcommittee
- ONAP security subcommittee
| Report progress periodically | Apr. 30, 2019 | Active | Covered by ONAP Requirement Subcommittee |
|---|
Cloud Native area | Coordinate activities around cloud native e.g. K8S + other open source solution linked to container management | - Drive collaboration with ONAP on key edge open source & standards initiatives
- Concrete near-term & long-term recommendations based on above and other inputs to
- ONAP architecture subcommittee
- ONAP modelling subcommittee
- ONAP requirement subcommittee
- ONAP security subcommittee
| Report progress periodically | Apr. 30, 2019 | Active | Covered by ONAP CNF Task Force |
Edge Computing area | Coordinate Edge Computing Activities (incl. O-RAN, LFN Edge, etrc) | - Drive collaboration with ONAP on key edge open source & standards initiatives
- Concrete near-term & long-term recommendations based on above and other inputs to
- ONAP architecture subcommittee
- ONAP modelling subcommittee
- ONAP requirement subcommittee
- ONAP security subcommittee
| Report progress periodically | Apr. 30, 2019 | Active | Covered by ONAP Requirement Subcommittee
ORAN coordinator - TBD
| Coordinate all network management activities happenning in 3GPP SA5, ETSI NFV, ETSI ZSM, IETF, BBF, MEF, TMF | - Drive collaboration with ONAP on key edge open source & standards initiatives
- Concrete near-term & long-term recommendations based on above and other inputs to
- ONAP architecture subcommittee
- ONAP modelling subcommittee
- ONAP requirement subcommittee
- ONAP security subcommittee
| Report progress periodically | Apr. 30, 2019 | Active | 3GPP, SA5, IETF, BBF, MEF, TM Forum, ETSI ZSM - ( open TBD ) Marketing Liaison | Point of contact for ONAP marketing efforts | | As Required | Project launch | Active | Pawel Pawlak |
Release Manager
| To facilitate, monitor and report on all aspects of project development, cross project coordination, and the timely creation of release artifacts according to the ONAP Release plan(s) and schedule(s). | - Work with the ONAP TSC and Project PTLs to create and evolve the ONAP release process.
- Develop document, and maintain release automation tools and tracking artifacts as needed
- Coordinate the cross project release cycle, including intermediate milestones and release candidates, final releases, stable and security updates. - Communicate with Project Technical Leaders, Technical Steering Committee and community at large regarding the status of the release. - Help identify release-blocking issues to keep release process on schedule
- Deliver timely release artifacts (executable(s), documentation, testing output, etc.) | Weekly | Project Launch | Active | David McBride
Open to any member of the community, but currently staffed by the LF due to the lack of candidates put forward by the community LF |
Security Coordinator | Coordinate the creation of security related processes and policies for the ONAP community | Work with community to identify what security processes and procedures are needed to ensure the security posture of the ONAP Project. Drive the the creation and documentation of those processes, policies, and supporting structures (such as needed subcommittees etc). | Weekly | Project Launch | Active | Concurrent assignment to the Seccom Chair position |
