| commit | fc0dcda05f8ac17247c54d87f5f5306a86744738 | [log] [tgz] |
|---|---|---|
| author | William Kurkian <wkurkian@cisco.com> | Mon Apr 08 16:54:36 2019 -0400 |
| committer | William Kurkian <wkurkian@cisco.com> | Tue Apr 09 15:37:37 2019 -0400 |
| tree | 9ad457821fdc7c00995d2aa27610536c48bd12e2 | |
| parent | 7bf8443c8c35ed6303dba292469598bd8645473d [diff] |
VOL-1500 VOL-1475 Updated the remaining python containers in voltha-go to use pyvoltha and voltha-protos Changed the build system to have separate flags for local pyvoltha and local protos. Cleared out now unneeded python libraries and protos from voltha-go PonSim was tested by launching the system-test-ponsim.yml and making sure the ponsim enables. This was tested on docker-compose and k8s. Let me know if there are other cases to test. Change-Id: Ie2d5a19900fcfc93b96aba2981efb18fd9e649bb
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.