Fwd: SEBA/VOLTHA Post Surge Plan of Action
William Snow
From: William Snow <bi...@opennetworking.org>
Date: Mon, May 11, 2020 at 11:25 AM
Subject: SEBA/VOLTHA Post Surge Plan of Action
To: voltha-discuss <voltha-...@opencord.org>, VOLTHA TST <volth...@opennetworking.org>
Cc: Guru M. Parulkar <gu...@opennetworking.org>, Aseem Parikh <as...@opennetworking.org>
SEBA/VOLTHA Community,
SEBA/VOLTHA Plan of Action
Goals (as articulated for the Board in its April 28th meeting):
ONF, operator partners (DT and TT) and key supply-chain members (e.g. Netsia, Radisys, Ciena, Infosys, Adtran) are committed to taking SEBA/VOLTHA to the next level: get it production-ready for deployment in DT and TT networks at scale.
With reduced ONF staffing for SEBA and significantly more work required towards accomplishing MVP 2.0 tasks, it is all the more imperative that responsibility is shared for MVP 2.0 among all the key stakeholders especially among the developers from the key supply-chain members. ONF cannot and should not shoulder all responsibility nor give the appearance of being solely responsible for delivery.
We will continue to use the "things that worked" in the Surge to have some degree of confidence in the path forward. In other words, we don’t plan to return to the pre-surge model of leaving everything up to a voluntary open-source community with little ONF involvement and no clear chain of command with deliverables and milestones defined.
Set clear and transparent communication with operators: understand their requirements and priorities; set expectations in terms of resource requirements vs. what is available and set expectations for deliverables with milestones with associated risks.
Plan of Action
The first step in sharing responsibility is to establish a new SEBA/VOLTHA TST to operate similar to the G5 but with new members representing the main supply chain vendors for DT and TT
The new TST and governance structure is below.
Note that similar to G5, the TST chair can make the final call on technical decisions.
The TST like the G5 will meet more often, have its own private slack channel and create a sense of urgency and shared-responsibility for driving the project forward and following operators needs
Unlike the G5, the TST involves members for Radisys and Netsia, ensuring responsibility for deliverables on TST decisions not just for their respective customers but also the project's overall needs. Too often during the Surge these two companies cared more (or cared first) about their private-forks for their customers, and less about the open-source.
Brigades will continue as before - two have ended, three more will end by June, test-automation and scale brigades will continue, and new ones may be created
The 6-month Surge process we just completed required the assembly of a Surge team - named contributors, promises/asks from their local-managers to not move them to other tasks, individual tracking of each contributor’s progress, reaching out and trying to understand why contributions are lacking for some and trying to help them, and reporting on progress every two weeks for each contributor.
Such a process was deemed necessary at the time of the Surge. It did however have mixed results and created significant overhead for ONF.
Going forward, while we are not looking to "assemble" such a team, the expectation with shared responsibility is that the core-team (top 20 contributors) continues to deliver without rigorous oversight. In other words, Radisys should manage their 8-10 people to deliver on the requirements and Netsia should do the same for their 6-8 people. And the Adtran people working on their adaptors or the omci stack should continue. The same with Infosys and Ciena. And the TST members should "feel" the responsibility to bring this to fruition for both operators, not just their respective customers. Everyone else in the community should work towards similar goals.
Monthly meetings with the operators
Once a month the TST will meet privately with the operators - this must include but is not limited to Cemil from TT and Manuel from DT - too often there were too many absentees in Tiger Team meetings during the Surge. Reducing to once a month should help. Aseem will help coordinate these meetings. ONF leadership (e.g. Bill and Guru) is also invited to these monthly meetings.
These meetings can be used to gauge LOE, figure out resources, set priorities, set expectations on timelines, identify risks and report progress towards operator goals in a smaller, private meeting as opposed to public TST calls every Tuesday.
In the spirit of transparency and shared responsibility, these meetings will report contributions of developers/organizations (without adding overhead) and if any organization or its developers are falling short and some intervention is required.
TST and operators can decide to invite representatives from other supply-chain members or operators as appropriate.
VOLTHA/SEBA Governance
(document is copied below for your convenience - it is here if you wish to add comments)
This governance is in place for May 1st 2020 through April 30th 2021. In April 2021 the governance will be updated to reflect the role of the TST at that time. In this document the term VOLTHA refers to the broader VOLTHA/SEBA project.
TST ROLE
The role of the VOLTHA TST during 2020-2021 will be to
Set technical direction
Make all technical decisions around VOLTHA
Drive a process to prioritize and meet the DT and TT deliverables to allow the operators to move into production with VOLTHA
Form and disband brigades as needed to achieve goals. Select the leader of each brigade.
TST Membership
The TST will have 5* members
Saurav Das, chair (ONF)
David Bainbridge (Ciena)
Amit Ghosh (Radisys)
Mahir Gunyel (TT)
Khen Nursimulu (Ciena)
*The chair may add members to the TST at any time.
The chair of the VOLTHA TST is nominated by ONF. The chair has no term limits, but may be removed/changed by ONF at any time at its discretion.
All members are appointed by the chair and will have 1 year term limits. It is anticipated that the TST will move back to a nomination and voting process in 2021 - but that decision is at the discretion of ONF.
If a TST member changes affiliation during their tenure they may be replaced at the discretion of the chair.
If a TST member leaves the TST it is up to the chair to decide if and when to replace the member.
Decision Making
Decisions are made by the TST chair working with the TST members. It is anticipated that the TST will work toward consensus. If consensus is not reached in a reasonable time as judged by the chair then it is up to the chair to make the decision.
Saurav Das
William Snow
My apologies - the last link had a draft version linked.
From: William Snow <bi...@opennetworking.org>
Date: Mon, May 11, 2020 at 11:25 AM
Subject: SEBA/VOLTHA Post Surge Plan of Action
To: voltha-discuss <voltha-...@opencord.org>, VOLTHA TST <volth...@opennetworking.org>
Cc: Guru M. Parulkar <gu...@opennetworking.org>, Aseem Parikh <as...@opennetworking.org>