Versions Compared

Key

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


2021

Company

Functions/Components

implemented by contribution

Running

Platform/

Environment

Source code repos

Description

License committersLanguage

Target

Contribution 

Date

Status
ORAN Alliance WG 6 AAL FECx86 Serveraal_fec/profile

Why

WG6 is considering splitting its AAL FEC specification into two portions to be published together in the July 2021 train – a) a formal specification document published through the normal O-RAN FRAND process that covers stage 1 and stage 2 specifications, and b) a stage 3 API document that covers data structures and programming language level details specific to open source implementations such as DPDK that would be published in ORAN OSC repo under a BSD license and referenced from the formal AAL FEC specification. The purpose is to enable easier ingestion of the ORAN FEC gaps identified by the ORAN community in upstream communities such as DPDK.  


What

To facilitate this split, WG6 co-chairs would like to request an OSC repo titled aal_fec/profile to be created for the above purpose. The purpose of this repository would be to store stage 3 specification documents and in the future, header files as well as test artifacts for the AAL FEC profile. Releases from this repository will be aligned with ORAN specification release trains as we intend to publish the stage 3 specification updates conjointly with the main spec.


License

BSD – we would prefer a BSD license to be compatible with the upstream community (DPDK) with which the spec is to be aligned.

Exception request: BSD

 niall.power@intel.com (PTL)


C/C++
ToC consideration (June/30/21)


2020-2019

Company

Functions/Components

implemented by contribution

Running

Platform/

Environment

Source code repos

Target

Contribution 

Date

Status

repo

name

Description

code

license

committerslanguage
Lenovo

Abstraction Adaptation Layer

OpenStack Hypervisoraal/lib
Apache2

liufeng24@lenovo.com,

lujq1@lenovo.

com 

com 

in progress


done
aal/logic
Apache2

liufeng24@lenovo.com,

lujq1@lenovo.com 

in progress


done
aal/mgmt
Apache2

liufeng24@lenovo.com,

lujq1@lenovo.com 

in progress


done
aal/virt
Apache2

liufeng24@lenovo.com,

lujq1@lenovo.com 

C/C++
in progress

done
China MobileIntegrated eNBx86 Server






InspurInfrastructure monitoringx86 Serverimp/metalHost Configuration ManagementApache2

gaosong.lc@inspur.comliutao.lc01@inspur.comqiaoxj@inspur.com

Python
requested 2019/06/11, LF Ticket #76725
imp/metal-apiHost management interface   Apache2

gaosong.lc@inspur.comliutao.lc01@inspur.comqiaoxj@inspur.com

Python


requested 2019/06/11, LF Ticket #76725
imp/fmHost Fault Monitoring, Detection and RecoveryApache2gaosong.lc@inspur.comliutao.lc01@inspur.comqiaoxj@inspur.com

Python


requested 2019/06/11, LF Ticket #76725
IntelDU layer 1x86 Servero-du/phyO-RAN DU Layer 1Apache 2

zhimin.yuan@intel.com,

 vitaliy

 vitaliy.zakharchenko@intel.comnicolas.chautru@intel.com,

 luis

 luis.farias@intel.com


C/C++
requested 2019/06/11, LF Ticket #76725
RadisysDU layer 2 and layer 3 x86 Servero-duO-RAN DUApache 2

balaji.shankaran@radisys.comsomshekar.ydlapur@radisys.com 

C
requested 2019/06/11, LF Ticket #76725
o-du/l2O-RAN DU Layer 2Apache 2balaji.shankaran@radisys.comsomshekar.ydlapur@radisys.com C
requested 2019/06/11, LF Ticket #76725



Guidelines: 

Seed code preparation:

  1. Check dependency license
    1. Make sure they are compatible with the contribution license
  2. Remove company proprietary and internal information
    1. Internal information may include internal email addresses, URLs, etc
  3. Include LICENSES.txt file at root of the repo
    1. For Apache 2 and Creative Commons 4 licenses:  LICENSES.txt
    2. For O-RAN Software License and Creative Commons 4 licenses: (to be added)
  4. Include license and copyright claim at the beginning of every source code file
    1. For Apache 2 (using language specific code comment format)

...

  1. Completing the columns under "Source code repos"
  2. Review your proposal with the Requirements and Software Architecture committee
  3. ToC approval of the creation and committers
  4. Making request to Linux Foundation

What is a project?

IS / HASIS NOT / DOES NOT
  • A long term endeavor to deliver features across multiple releases
  • Rationalized based upon clear technical and industry benefits
  • Has a clearly defined scope that can be leveraged across many use cases
  • Requires a dedicated content repository
  • A community which acts collectively as a single development entity 
  • Has Committers with expertise in the relevant areas

  • Intended for a single ONAP release 
  • Rationalized based upon convenience for an individual entity
  • Scoped broadly or a collection of unrelated items to satisfy a single use case
  • Something that can exist without having a dedicated repo
  • A fully self-contained internal development team
  • Require Committers with different expertise 


The basic steps for submitting a proposal

...