| commit | aaac7ee1b70085929f99e55aa655fd7b3161863d | [log] [tgz] |
|---|---|---|
| author | Khen Nursimulu <knursimu@ciena.com> | Sun Dec 11 22:03:52 2016 -0500 |
| committer | Zsolt Haraszti <zharaszt@ciena.com> | Mon Dec 12 18:24:35 2016 -0800 |
| tree | 1b8b9748cbc6c3ed124a623903b74046cbc08f24 | |
| parent | 9ad4569b8562999bfb2cad4d6281884d969e8666 [diff] |
This commit consists of: 1) Dockerizing the netconf server 2) Update proto2yang to support module imports 3) Provide a set of yang modules derived from the proto files in voltha. These files as well as the slight mmodifications to the proto files are provided in the experiments/netconf/proto2yang directory 4) Code to automatically pull proto files from voltha into the netconf server, compiles them and produce the yang equivalent files. 5) Add a getvoltha netconf API to provide voltha state information (basic at this time). There is potential to make this generic once we experiment with additional APIs Change-Id: I94f3a1f871b8025ad675d5f9b9b626d1be8b8d36
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.