|author||Matt Jeanneret <email@example.com>||Sun Apr 14 20:33:08 2019 -0400|
|committer||Matt Jeanneret <firstname.lastname@example.org>||Thu May 02 20:19:31 2019 +0000|
VOL-1489: Add uni port id as tunnel id needed for olt flows When the olt is asked to setup pon resources on the onu/uni's behalf it needs to know what onu and uni port it is dealing with for a particular flow. Typically with flow decomposer the ports on the child device (uni) are not visible on the parent. But in the case of olt based flows (at least with BAL?) the parent device needs to know the uni ports so it can create gems, alloc id, and queues needed. This patch adds new openflow tunnel id containing the uni port to the decomposed flows for use by the adapter. Change-Id: I0ea701b457ab5cb5877b953f58364d6a7806a58f
Voltha aims to provide a layer of abstraction on top of legacy and next generation access network equipment for the purpose of control and management. Its initial focus is on PON (GPON, EPON, NG PON 2), but it aims to go beyond to eventually cover other access technologies (xDSL, Docsis, G.FAST, dedicated Ethernet, fixed wireless).
Key concepts of Voltha:
Control and management in the access network space is a mess. Each access technology brings its own bag of protocols, and on top of that vendors have their own interpretation/extension of the same standards. Compounding the problem is that these vendor- and technology specific differences ooze way up into the centralized OSS systems of the service provider, creating a lot of inefficiencies.
Ideally, all vendor equipment for the same access technology should provide an identical interface for control and management. Moreover, there shall be much higher synergies across technologies. While we wait for vendors to unite, Voltha provides an increment to that direction, by confining the differences to the locality of access and hiding them from the upper layers of the OSS stack.
While we are still at the early phase of development, you can check out the BUILD.md file to see how you can build it, run it, test it, etc.
Contributions, small and large, are welcome. Minor contributions and bug fixes are always welcome in form of pull requests. For larger work, the best is to check in with the existing developers to see where help is most needed and to make sure your solution is compatible with the general philosophy of Voltha.