Area Name | Area Description | Coordinator Role Description | Reporting Cadence | Date Approved/disapproved | Status | Coordinator |
---|
| Coordinating with LF-IT on issues pertaining to LF infrastructure | The infrastructure coordinator, as TSC delegate, is responsible for deciding repository creation requests and coordinating with LF release engineering staff on other issues pertaining to LF infrastructure and the verification of new Committer requests | Periodic reports to the TSC, as necessary, with the status of repository creations and other issues that may arise | Jan 25, 2018 | Active | Concurrent with the Release Manager at this time |
| 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 | January 14, 2019 | Active | Jim Baker |
| 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 | 5/4/2017 | Active | Concurrent assignment to the Seccom Chair position |
Standards/SDOs | Open source and standard are compliementing each other. Opensource is playing an increasing important role in SDO practice, which could help to gain industry concensus and adoption. The potential standard bodies and topics include: - IETF YANG/NETMOD/NFVRG
- TMF OSS/API/ZOOM
- MEF LSO
- ETSI NFV/MEC
- OASIS TOSCA
- 3GPP
- BBF
| - External Responsibilities:
- Identify members of the ONAP community with existing relationships to external SDOs, and work with them to identify and follow the overlap in interest or practice from standard bodies related to ONAP’s implementation and report to TSC regularly or on demand.
- Develop ONAP collaboration strategy with, coordinate ONAP presence, delegation and participation to identified SDO practices and report to TSC regularly or on demand.
- Internal Responsibilities:
- Work with individual projects in soliciting and identification of related SDO practices.
- Coordinate between implementation project in ONAP and identified SDO practice and report to TSC regularly or on demand.
- Coordinate among multiple implementation projects in ONAP which fall into scope of a given SDO spec and report to TSC regularly or on demand.
| - Regularly each TSC F2F meeting.
- On-demand report based on urgency of the event.
| 05/11/2017 ONAP TSC voted in January 2019 to have area coordinators, not overall SDO/ Open source coordination | Active
| |
| The External Open Source Community Coordinator is responsible for identifying members of the ONAP community with existing relationships to external open source communities, coordinating with them to expedite interactions between members of the ONAP community and those external communities, and reporting to the TSC on those activities. | See Area Description | Monthly | 05/11/2017 ONAP TSC voted in January 2019 to have area coordinators, not overall SDO/ Open source coordination | In-active | TBD - https://lists.onap.org/pipermail/onap-tsc/2017-May/000349.html Logging in ONAP works with Acumos Jira |
---|
server | ONAP JIRA |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
key | TSC-15 |
---|
|
|
AI (ML/DL) area | Coordinate activities aroinf AI (ML/DL) including Acumos, ETSI ENI etc. | - Report progress periodically to ONAP on key area related open source & standards initiatives
- 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 usecase subcommittee
- ONAP security subcommittee
|
|
|
|
5G area | Coordinate activities around 5G, including but not limited to 3GPP, ORAN, ORAN-OSC, IEEE |
|
|
|
Cloud Native area | Coordinate activities around cloud native e.g. K8S + other open source solution linked to container management |
|
|
|
Edge Computing area | Coordinate Edge Computing Activities |
|
|
|
Generic network management activities area | Coordinate all network management activities happenning in 3GPP SA5, ETSI NFV, ETSI ZSM, IETF, BBF |
|
|