Skip to end of metadata
Go to start of metadata

The TSC Charter identifies individuals to aid the TSC and TSC Chairperson in coordinating various activities for the technical community.  This page lists the area of coordination and the person currently fulfilling the role.

ONAP Liaisons

Area NameArea Name and DescriptionCoordinator Role DescriptionReporting CadenceDate CreatedStatusCoordinator

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 periodicallyApr. 30, 2019Active

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, 2019ActiveCovered 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 periodicallyApr. 30, 2019ActiveCovered 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 periodicallyApr. 30, 2019Active

Covered by ONAP Requirement Subcommittee

ORAN (Swaminathan Seetharaman )


EUAG Liaison

ONAP representative to LFN's End User Advisory Group
  • Work with the EUAG and ONAP TSC on alignment of requirements and communications. 
  • Must be a member of the EUAG
  • Expected to attend the LFN MAC meeting.
As requiredApr. 5, 2018ActiveLei Huang

Generic network management activities area

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 periodicallyApr. 30, 2019ActiveMagnus Buhrgard

Infrastructure

Coordinating
with LF-IT on issues pertaining to LF
infrastructure

 infrastructure-coordinator@onap.org

The Infrastructure Coordinators (2 individuals), act as the TSC delegates 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
Active

Marketing Liaison

Point of contact for ONAP marketing effortsAs RequiredProject launchActiveDavide Cherubini

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.)

WeeklyProject LaunchActive

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 

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).WeeklyProject LaunchActiveConcurrent assignment to the Seccom Chair position


  • No labels

4 Comments

  1. Acumos/ONAP coordination -  TSC-15 - Getting issue details... STATUS

    CD, Security infrastructure with LF -  TSC-25 - Getting issue details... STATUS TSC-32 - Getting issue details... STATUS

  2. Should the area coordinators  have a specific list of Opensource communities they are responsible for coordinating with on behalf of the ONAP TSC ?

  3. 1 Speaking for ex-SDO coordinator, we learned that there are too many SDOs in this world, they all want to build the relationship with ONAP community, but when we come to the community to ask whether you have any issues related to SDO, there are only 2-3 SDOs (ETSI NFV / 3GPP SA5), here is the example for this year: Collect issues in ONAP related to M-SDOs. why we need so many coordiantors but without any issues from ONAP communities.

    2 some SDOs who just come to ONAP community and made the contribution without any coordinations like TMF API which shows very good example in the open source community, we need more coders other than too many coordiantors.

    3 When we talked about 5G, there are always 3 pillars, Radio PNF/ Slicing/ Mobile Edge computing, it seems current proposal are trying to divide 5G into 3 parts,   network management which is key component of slicing in 5G