commit | 0c5088c303288cddc9e9d7fddd13533c3f7f5bba | [log] [tgz] |
---|---|---|
author | Matt Jeanneret <mj3580@att.com> | Mon Apr 22 16:16:19 2019 -0400 |
committer | khenaidoo Nursimulu <knursimu@ciena.com> | Wed Apr 24 02:27:45 2019 +0000 |
tree | 9d6d9b7ac16e90ca251e7c1b5907a77813290ff9 | |
parent | ec4ff51a6832eafe606d315ecd74b83efffdac51 [diff] |
VOL-1494: Allow adapter to set of port name This is needed given there are multiple uni per child device serial number and we need the name to be in a format decided by the child device given it knows its ports the best. Practically speaking the onu will now set the name to serialnumber-uniport, i.e: port=4112, portName=BRCM33333333-1 port=4113, portName=BRCM33333333-2 port=4114, portName=BRCM33333333-3 port=4115, portName=BRCM33333333-4 port=4116, portName=BRCM33333333-5 This allows a per-uni lookup in sadis Change-Id: I85fef83973f88cd219421dbe3c9a15ec9b0042a0
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.