Versions Compared

Old Version 22

changes.mady.by.user Alla Goldner

Saved on

compared with

New Version Current

changes.mady.by.user Kenny Paul

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Table of Contents
maxLevel2
minLevel2

External Standard Coordination

External Open Source Community Coordination


Tableenhancer
numberOfFixedRows1
decimalMark. (point)

ONAP Liaisons

Area NameArea Name and DescriptionCoordinator Role DescriptionReporting CadenceDate
Approved/disapproved
CreatedStatusCoordinator

Infrastructure

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, 2018Active

Marketing Liaison

Point of contact for ONAP marketing effortsAs RequiredProject launchActivePawel Pawlak 
Concurrent with the Release Manager at this time

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
January 14, 2019
Project LaunchActive
Jim Baker

David McBride
Open to any member of the community, but currently staffed by the LF 

Security Coordinator

Coordinate the creation of security related processes and policies for the ONAP communityWork 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
Project LaunchActiveConcurrent assignment to the Seccom Chair position

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
serverONAP JIRA
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keyTSC-15

AI (ML/DL) areaCoordinate 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 areaCoordinate activities around 5G, including but not limited to 3GPP, ORAN, ORAN-OSC, IEEECloud Native areaCoordinate activities around cloud native e.g. K8S + other open source solution linked to container managementEdge Computing areaCoordinate Edge Computing ActivitiesGeneric network management activities areaCoordinate all network management activities happenning in 3GPP SA5, ETSI NFV, ETSI ZSM, IETF, BBF, MEF, TMF

...