Welcome to the VOLTHA Community wiki space. All information on this wiki is publicly accessible. If you would like to contribute to this space, you will need an ONF account: https://www.opennetworking.org/register/
Flexible and agile service adaptation at the cost of commodity servers and whitebox switches VOLTHA introduces the next-generation optical access system architecture, based on SDN/NFV technologies. Disaggregating PON functions to functional modules with open interfaces supports the CORD vision for open source reference implementations to service "Access-as-a-Service" use cases. VOLTHA is a virtual OLT hardware abstraction component that supports the CORD Project objective of multi-vendor, multi-domain "any broadband access as a service" reference implementation for the Central Office. VOLTHA provides isolation between an abstract (vendor agnostic) PON management system, and a set of vendor-specific and white-box PON hardware devices. On its north-bound interface, VOLTHA provides a set of abstract APIs which north-bound systems can interact with the PON networks. On its south-bound side, VOLTHA communicates with PON hardware devices using vendor-specific protocols and protocol extensions through adapters.
Key People and Communication Channels
Technical Steering Team
The technical steering team is responsible for all technical decisions in the project. They are responsible for the content and structure of the code base and for all technical priorities with respect to the code base.
Current TST Members
Jira showSummary false server OpenCORD JIRA serverId bbd1ea60-dfe5-38d4-a09c-a972f47418dc key VOL-3382
|Chip Boling||TiBit||TST Member|
|Saurav Das||ONF||TST Member|
|Matt Jeanneret||AT&T||TST Member|
|Shaun Missett||Radisys||TST Member|
|Khen Nursimulu||Ciena||TST Member|
The mailing lists are the preferred way to get in touch with the project members with any questions, suggestions, or concerns.
- vOLTHA Discussions: https://groups.google.com/a/opencord.org/forum/#!forum/voltha-discuss
- CORD Discussions: https://groups.google.com/a/opencord.org/forum/#!forum/cord-discuss
The CORD Slack is the best way to get quick answers to your questions. Our team is distributed globally, so someone should be available at all times. vOLTHA topics are discussed in the #voltha channel.
Register for a CORD Slack account here: http://slackin.opencord.org
- VOLTHA TST Meetings - Tuesdays at 8am PT.
vOLTHA 2.x Stabilization Brigade - Tuesdays at 7am PT
- Pod Management and VOLTHA FCAPS Brigade - Mondays at 8am PT
NOTE: these meetings are PUBLIC and often RECORDED. The recordings can be found on YouTube:
- vOLTHA: https://www.youtube.com/playlist?list=PLCnPGaNt7C5evyQ-FFwAtbKaUp4cDmINa
- Brigade: Pod Management and VOLTHA FCAPS: https://www.youtube.com/playlist?list=PLCnPGaNt7C5eX0fQAeVwg_dy6o9aZdArs
- Brigade: VOLTHA Stabilization: https://www.youtube.com/playlist?list=PLCnPGaNt7C5eQ7XkeeMJ7nDzDUkOmPoRq
VOLTHA work is done primarily using the brigade structure. Current brigades:
Release and Project Management
Working as an open source community team
- The intended host of this project is the CORD project (opencord.org).
- All source code to be developed via the gerrit system of opencord.
- All parts of VOLTHA will be managed as one git repository (any proprietary plugin code by vendors will be kept in separate repos/places).
- All project documentation must be kept with the git repository (preferably as markdown (*.md) files, with drawings created with preferably Inkscape (has to be editable and PNGs can be redesigned).
- All major changes, decisions, etc., must be done with VOLTHA TST approvals, and pursuant of the CORD project governance rules.
VOLTHA Release Acceleration
- Agile + Continuous Integration - Mandatory Test Driven Development
- Single source code repo with automated build
- Transparency - Everyone should know what is going on
- Design Specs for all major new features - get the team engaged for cross functional support on features (dev, test, doc etc)
- WIKI is the main source of true for documentation, not google docs
- All contributions upstream tracked in JIRA and linked to Gerrit
- Keep JIRA up-to-date to avoid duplication of efforts or gaps in sprint deliverables
Release Model and Cadence
VOLTHA will follow the CORD release model, branching, versioning and tagging best practices found here: Release Management
VOLTHA Release Plans and Notes
|Component / Feature||Release Date||Release Notes||Comments|
|VOLTHA v1.0.0||Sep 12, 2017||VOLTHA v1.0.0 Release Notes||Major release focuses new features and feature enhancements for AT&T POC III requirements building on previous POC I/II features functionality.|
|VOLTHA v1.1.0||Oct 6, 2017||N/A|
Minor release focuses on inclusion of Edge-core ASFvOLT16 XGS-PON OLT Adapter.
ASFvOLT16 design based on Broadcom Maple PON MAC silicon supporting 16x XFP ports of XGS-PON or NG-PON2 (10Gb/10Gb) and four QSFP28 Ethernet uplink ports.
|VOLTHA v1.1.1||Nov 16, 2017||N/A||Maintenance release focuses on bug fixes in preparation for AT&T POC IV / Field Trial|
|VOLTHA v1.2.0||Dec 21, 2017||VOLTHA v1.2.0 Release Notes||Minor release focuses on enhancements to ASFvOLT16 Adapter and support for T&W ONU|
|VOLTHA v1.2.1||March 16, 2018||VOLTHA v1.2.1 Release Notes||Patch release for CORD 5.0 integration, REGID support for ONU Registration and bug fixes.|
|VOLTHA v1.3||April 30, 2018||VOLTHA v1.3 Release Notes||Minor release: migration to Kubernetes, OpenOMCI|
|VOLTHA v1.4||July 22, 2018||Incorporate Celestica OLT adapter; Integration to CORD 6.0; OpenOLT introduction software package|
|VOLTHA v1.5||October 02, 2018||Open_LT: ONU Reboot, Limited Performance Monitoring Stats and Event/Alarm support. brcm_openOMCI_onu adapter|
May 21, 2019
|Major release focuses on Containerized Adapters, restructure of vOLTHA Core, OpenOMCI|
|VOLTHA v2.1||Technology Profiles (port functionality from 1.x), multiple T-CONTs, whitebox OLT in-band management|
|VOLTHA v2.2||Dec 22nd, 2019||VOLTHA v2.2 Release notes|
|VOLTHA v2.3||March 24th, 2020|
|VOLTHA v2.4||June 30th, 2020 |
(planning in progress)
The 2019 election process has two main steps for all positions. Nomination, and voting.
When there is only one nomination for a position, there does not need to be a vote.
The voting community is composed of the following people:
- Steering team members and leads
- Contributors (those who have submitted code which has been reviewed and accepted in the last year)
VOLTHA Voting Community List
Results can be found here.