Project Technical Lead: Julie LORENTZEN, AT&T, Elected 8/27/19
Aaron Byrd. Elected 1/17/19. Aaron Byrd stepped down as PTL on 7/30/2019. Elections for new PTL will be held 8/26/19. Self-Nomination should be completed by 8/23/19.
Project Committers detail:
Initial Committers for a project will be specified at project creation. Committers have the right to commit code to the source code management system for that project.
A Contributor may be promoted to a Committer by the project’s Committers after demonstrating a history of contributions to that project.
Candidates for the project’s Project Technical Leader will be derived from the Committers of the Project. Candidates must self nominate by marking "Y" in the Self Nominate column below by Jan. 16th. Voting will take place January 17th.
Only Committers for a project are eligible to vote for a project’s Project Technical Lead.
Please see Akraino Technical Community Document section 3.1.3 for more detailed information.
|Self Nominate for PTL (Y/N)|
|Mahir Gunyel||Netsiaemail@example.com||Mahir has been working about 19 years in Telco SW domain in different positions like development, architecting , management. He has experience especially on mobile telco networks and protocols.||N|
|Ash Young||Cachengofirstname.lastname@example.org||26 years experience in open source: contributed original code to bootstrap OpenFiler and kernel RAID support; prior iSCSI Enterprise Target maintainer for SuSE community; and original PTL for ONOS Framework project in OPNFV. Most recently led the porting effort of SEBA to support the Arm64 community. Also initiated and led the Arm64 porting of CORD.||Y|
|Jimmy Lafontaine Rivera||Cachengo|
|Zack Williams||ONFemail@example.com||ONF MTS, SEBA Dev team and manager of Jira, CORD platform team||N|
Julie Lorentzen has been with AT&T for 19 years, focusing primarily on optical access architecture and related technologies. She serves as scrum master for ONF’s VOLTHA project. Past experience includes serving as ITU-T editor for OMCI-related work and as FSAN co-chair for the G-PON Interoperability task group.
Upstream SEBA Project information:
SEBA project page (meeting times, mailing list, developer information): https://wiki.opencord.org/display/CORD/SEBA
SEBA Documentation: https://guide.opencord.org/
- Virtualized SEBA installation for testing and development w/o PON access hardware: SEBA-in-a-Box
- Hardware requirements
- API Documentation
For more information, please contact Zack Williams (contact info above), or post on the upstream SEBA project mailing list.
Use Case Details:
New blueprint for fixed wireline access within Telco Appliance Blueprint family
Blueprint Family - Proposed Name
Virtual broadband access (XGS-PON - Higher bandwidth, symmetric version of GPON)
Blueprint proposed Name
SDN Enabled Broadband Access (SEBA)
Scale & Type
3 servers per POD
x86 and Arm (with 8-16 cores each)
Virtual broadband access – vOLT access & aggregation (5000 edge locations)
Less than 1 kW. NEBS and 48V DC
OS - CentOS
Docker 1.13.1 or above / K8 1.10.2 or above- Container Orchestration <update versions>
Under Cloud Orchestration - DANM
Open Network Operating System (ONOS) and XOS
VOLTHA (Virtual Optical Line Terminal Hardware Abstraction – CORD project)
Network Edge Mediator (NEM)
OF & Redfish
Akraino based community blueprint, Full Automation
Cloud layer hardened for production
Current SEBA POD contains network elements, compute nodes, and software components.
Aggregation and management switches
See attachment for additional details