| commit | cc40904e208892dea8e1a2a73b52e6465d3c6d59 | [log] [tgz] |
|---|---|---|
| author | khenaidoo <knursimu@ciena.com> | Fri Oct 11 14:25:02 2019 -0400 |
| committer | khenaidoo <knursimu@ciena.com> | Tue Oct 15 10:36:26 2019 -0400 |
| tree | 98a412b8bba4c365158a1ec081d50fe4d74fb338 | |
| parent | b31893f83a6911c8a559aff4aeeddb8012aa2357 [diff] |
[VOL-1997] Remove transaction timeout for a non-active rw_core This commit cleans up the transaction processing between two cores in a pair. It prevents the core not processing the request to grab the request based on a timeout only. Since this update heavily relies on the etcd mechanism then customized local tests (not unit as could not find a full-featured etcd mock) were run against it as well as some basic manual tests with kind-voltha. There is a TODO item in this commit to implement a peer-probe mechanism to guarantee that a core in a pair has actually died before a switch over is done. Minor updates after first review. Comments updates after second review Change-Id: Ifc1442471595a979b39251535b8ee9210e1a52df
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.