Versions Compared

Old Version 4

changes.mady.by.user Qihui Zhao

Saved on

compared with

New Version Current

changes.mady.by.user Qihui Zhao

Saved on

Key

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

...

Overview:

Release 11.2022 is the first xgvela release delivered in 2022. It started at June 29 and ends at November 29. Within this release, the team has completed delivering 5 major functions (which have 13 features in total) and code related documents, covered functional testing and deployment verification, and updated architecture doc. Detailed contents are listed below. Besides, the team has made a huge progress on release related procedure establishment.

Projects accomplishment:

ContentsDescription
ProjectCloud native OAM
Release accomplishment

Delivered Functional Features:

  • Targeted on NF management PaaS capabilities, re-designed and implemented a group of functions to deal with operation and management in network functions.
    Jira
    serverLFNetworking Jira
    serverId3c1fbbb1-22c4-3d7c-9507-06bfb67a1be2
    keyXGVELA-11
  • The major delivered functions include configuration management, topology management, performance management, log management, alarm management, and several other supporting functions including authentication and authorization, subscription interface on observability data. :
    • configuration management
      Jira
      serverLFNetworking Jira
      serverId3c1fbbb1-22c4-3d7c-9507-06bfb67a1be2
      keyXGVELA-14
    • topology management
      Jira
      serverLFNetworking Jira
      serverId3c1fbbb1-22c4-3d7c-9507-06bfb67a1be2
      keyXGVELA-34
    • performance management
      Jira
      serverLFNetworking Jira
      serverId3c1fbbb1-22c4-3d7c-9507-06bfb67a1be2
      keyXGVELA-23
    • log management
      Jira
      serverLFNetworking Jira
      serverId3c1fbbb1-22c4-3d7c-9507-06bfb67a1be2
      keyXGVELA-31
    • alarm management
      Jira
      serverLFNetworking Jira
      serverId3c1fbbb1-22c4-3d7c-9507-06bfb67a1be2
      keyXGVELA-27
    • authentication and authorization (supporting functions )
      Jira
      serverLFNetworking Jira
      serverId3c1fbbb1-22c4-3d7c-9507-06bfb67a1be2
      keyXGVELA-21
    • subscription interface on observability data (supporting functions )
      Jira
      serverLFNetworking Jira
      serverId3c1fbbb1-22c4-3d7c-9507-06bfb67a1be2
      keyXGVELA-22
    • Source code can be found at: https://github.com/XGVela/cloud-native-OAM
  • Impelmented helms charts for all the above functions. Files can be found at: https://github.com/XGVela/cloud-native-OAM-builder

Delivered Documentations:

Integration:

  • Successful integration among cloud native OAM functions, Inspur's container platform and CMCC's container platform on Big Cloud. Both of the container platform are using K8S for orchestration.
  • Successful integration among cloud native OAM and network function simulator, which is developed to mimic actions of real network functions.

Tests covered:

As there is no CI/CD pipelines, tests on delivered cloud native OAM functions have been completed in private environment. Quality of delivered codes, helm charts and documentations support users to deploy and use cloud native OAM. Auto testing are scheduled in next release.

Demo:

 https://zoom.us/rec/play/LkSKyqZ3_Q_HpijS7DttZKHgoBJdV0t9ha-B1t-LznuSS3S_v4NUMk3zbjXY6w4x27peCxcaWmscEfri.33jiIuhCpWTPI4jf?startTime=1666701683000&_x_zm_rtaid=rmclgPH8QGW7hqM8_7DxUQ.1668767083254.d9ff365f8a9205e35cc3cfe0385ef925&_x_zm_rhtaid=647

Summit presentation:

Other metrics:

Summary of outstanding accomplishment
  • Functional code delivery. Cloud native OAM supports to provide operation and management functions outside NF, which can help to relief NF developers from putting too much effort on fcaps related developement. Besides, as cloud native OAM is the most commonly functions that can be shared among NFs, providing them through PaaS platform indicates NF are using more capabilities on cloud, which is a good trend for telcos to be more cloud native.
  • Cloud native OAM has been integrated with and verified on two different container environments. This on some degree reflects the portablity of codes.
Delta between planned and actual accomplishmentN/A
Plans for Next Release
  • More telco PaaS functional features delivery
  • Integration among cloud native OAM, CNF (e.g. Free 5GC), other PaaS platform (OKD), and ONAP.
  • Bug fix and doc optimize
  • Update cloud native OAM deployment method


Release management accomplishment:

  • Completed a list of PaaS capability candidates (Projects), which gives a clearer clue on how to develope Telco PaaS and helps to narrow down the community scope.
  • Community run a complete release for the first time. Although the process may not be professional, but it's still a huge accomplishment. For next release, the team will try to get some trainning on release management, and keep optimizing the process.
  • Established release processes by writing a guide Release Process and having Release 11.2022 Schedule.
  • Established project management processes by writing guide on Project Operations and Procedures and Project Proposals procedures.