commit | 92da1d021b11353571a0e1a5583588568c089387 | [log] [tgz] |
---|---|---|
author | Shad Ansari <shad@opennetworking.org> | Tue Jun 12 20:42:20 2018 +0000 |
committer | Shad Ansari <shad@opennetworking.org> | Tue Jun 12 20:42:20 2018 +0000 |
tree | 99d1200aa3df380d57ef28d54546930cac6a34fb | |
parent | 928fa93b88702de073ae7f1f8ec37aede581e357 [diff] |
VOL-950: Lookup onu device based on PON-intf_id and onu id The adapter_agent.get_child_device() method is used by OLT adapters to lookup the ONU device. The lookup allows search on ONU ID (and/or ONU serial number). When looking up by ONU ID, this method should also take the PON interface id into consideration since ONU IDs are not unique across PONs. The parent_port_no member of the Device class is used to identify the PON interface that the ONU is connected to. Change-Id: I19478e73157c74e095fb84b327b317539fc10276
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.