ORAN SC Amber Release Status and Planning Proposal

O-RAN SC Amber Release Status and Planning Proposal Lusheng Ji (AT&T) O-RAN SC INT Project PTL

O-RAN SC Amber by Numbers (2019 10 16) • 11 projects • INF, O-DU Low, O-DU High, O-CU, Near RT RIC PLT, Near RT RIC APP, Non RT RIC, OAM, SIM • DOC, INT • Wiki, code repo, artifact repo • Mailing lists with ~ 140 subscribers • Regular weekly meetings by To. C, RSAC, and projects • Already > 1 m loc contributed by > 60 contributors from 10 organizations

Time line ] [Project team bug fixing, documentation] Project team development [ Int testing and release gating ] [ Releasing [Project release criteria & planning] hi t. A c ec an oj Br Pr de Co [LF Releasing] ng Today ] 11/18 11/11 11/04 11/02 10/28 10/21 10/14 10/09 Code Freeze [ [Master branch open for project team dev]

Releasing Timeline and Expectations • Code Freeze (11/02) • No development after the code freeze. • Only code changes for bug fixes and documentations on master branch. • Integration and Testing (11/04 – 11/15) • For each project to complete • Bug fixes, CI, and documentation • Completing release criteria check with INT • Complete documentations • Releasing (11/18 -11/23) • To. C: Review project status and go-no-go decision • For each project to complete • Complete documentations • Cut Amber branch from master branch • After this master branch open for additional development • Work with LF on releasing source code and artifacts (container images, libraries, etc) • Released (11/26 -11/30) • Testing released artifacts • failed artifacts plan for maintenance window • Announcement, PR

General Releasing Criteria • Seed code in repos • License and copyright compliance • CI Integration • Automated verify and merge builds • Artifacts built and pushed • Docker image: nexus 3. o-ran-sc. org • Others: Package Cloud • Component functionality • High option: component downloadable and run-able by the INT team in one of the integration labs • Low option: component run-able in contributor’s preferred (e. g. self-provided) environment during a joint demo/testing session with the INT team • Component documented • Working with DOC project in producing readthedocs documentation. • Video recording tutorial for how to: build, config, and run.

INF Project • AAL • • aal/lib (Lenovo): 2 k loc*, C, makefile aal/logic : empty aal/mgmt (Lenovo): <1 k loc*, python aal/virt: empty • IMP • imp/fm (Inspur): 16 k , python, C/C++, YAML, makefile • imp/metal (Inspur): 100 k Lo. C, python, C/C++, YAML, makefile • imp/metal-api: : empty • pti. rtp • pti. rpt (Windriver) <1 k Lo. C, shell, yaml

O-DU O-CU Projects • O-DU Low • r. o-du. phy (Intel): 7 k loc, C/C++, makefile • O-DU High • r. o-du. l 2 (Radisys): 151 k loc, C/C++, makefile • o-cu. sim (Radisys): 41 k loc, C/C++, makefile • O-CU • • scp. ocu. openlte: empty gnb-int. build: empty gnb-int. common: empyty gnb-int. src: empty

Non Realtime RIC • ric-nrt. a 1: empty • ric-nrt. oam: empty • nonrtric (Ericsson): 500 k loc, JSON/Java, onap/sdnc-oam fork? • portal/ric-dashboard • AT&T 26 k loc, Java etc • Ericsson 3 k loc under review

OAM • oam: ONAP container deployment definition, models • scp. oam. modeling: information and data models

SIM • sim: empty • sim. a 1 -interface : empty • sim. e 2 -interface : empty • sim. f 1 -interface : empty • sim. fh-interface : empty • sim. o 1 -interface : empty

Near Realtime RIC Platform and APP • com/*, ric-plt/* ric-app/* (AT&T, Nokia): 900 k loc, C/C++/Go/Python/etc

INT • it/otf (AT&T): 42 k loc, Java, Python, JS • it/dep (AT&T): 17 k loc, shell, yaml (helm charts) • it/test (AT&T): 115 k loc, C/C++, etc. • it/dev: empty • It/int: empty