Introduction

After researching on NFs from different vendors, no matter NFs are PNF, VNF or CNF, they are designed as distributed applications, which usually contains functional modules including interface module, data storage module, operation and management module, NF logic processing modules.

Functional modules' description are as follows. Different NFs from different vendors  may have difference on design and implementation, but they almost follow this similar design paradigm. 

  • Interface Module: module in charge of South-North communication between different NFs, which is usually implemented as load balancer. 
  • NF logic processing modules: modules processing NF service logics. For example AMF contains functions of access management, security management, session management etc., and these functions can be implemented as different NF logic processing modules.
  • Data storage module: module stores NF states, user data and service processing context. Cloud native NF requires network logic processing module is stateless and supports scaling in/out horizontally, which usually results in that the NF data are stored in independent DB.
  • OAM(operation and management) module: module in charge of NF management, configuration, monitoring, etc. 
  • Internal communication module: module support internal communication between differrent modules within a NF.

Among all these functional modules, OAM module is one of the most commonly used module within different NFs, which makes it possible to be shared among NFs as a PaaS service. Providing OAM module as a platform capability can relief the developers from spending too much effort on non-NF logic design and development. So in XGVela release 1, cloud native OAM for NF is planned to be delivered.


Documentation & Training

Link here to any project documentation & training available for your project 


Release Planning & Release Notes

Link here to release notes & release plans.  This information is likely stored in the community jira.  Information should include Release deliverables (per release), Release Milestones (per release), externally consumable APIs, expected incompatibilities w/ other Projects, compatibility w/ previous releases, themes and priorities, requests from other projects, components and any test tool requirements.



Project Facts

Project Creation Date: Use // to set a date 
Primary Contact: Use @name to tag Contacts
Project Lead:  @name
Committers:  This field will need to be maintained by the PTL.  LF is currently working on automating this in the future
  • @name
  • @name
Mailing List:  The project-specific mailing list or xgvela-tsc@lists.xgvela.org
Meetings:  Ensure any meetings listed on the central Meeting page
Repository: Link to Code Repository
Jenkins: Link to Jenkins Silo
Open Bugs: Link to tagged JIRA tickets

Project Working Documents

Task Report

All project pages should be tagged with a label  'projectname-project'  example 'XGVela Operator Framework' is labeled 'operator-project'

This is a necessary step so that action items can be assigned between the PTL and the Committers of the project.  Edit the "Task Report" confluence macro below and change the label field to match your project tag.

Project Files

Project files can be uploaded here.  Please also follow the same steps for assigning a project label.  Update the below macro field with your project label (tag) and remember to that when uploading files they should also be labeled with the same tag so they are easily filtered.  Files that are attached directly to a page with an existing label (tag) 'should' be automatically labeled.