|author||khenaidoo <firstname.lastname@example.org>||Mon Mar 02 16:01:25 2020 -0500|
|committer||khenaidoo <email@example.com>||Tue Mar 03 10:47:45 2020 -0500|
[VOL-2688] Improve core model performance This commit addresses the low-hanging performance hogs in the core model. In particular, the following changes are made: 1) Remove proto message comparision when it's possible. The proto message deep comparison is quite expensive. 2) Since the Core already has a lock on the device/logicaldevice/ adapters/etc before invoking the model proxy then there is no need for the latter to create an additional lock on these artifacts duting an update 3) The model creates a watch on every artifacts it adds to the KV store. Since in the next Voltha release we will not be using Voltha Core in pairs then there is no point in keeping these watches (these is only 1 Core that will ever update an artifact in the next deployment). This update removes these watch. 4) Additional unit tests has been created, mostly around flows, in an attempt to exercise both the core and the model further. Change-Id: Ieaf1f6b9b05c56e819600bc55b46a05f73b8efcf
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.
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. Please check out the contributing page on the documentation.