|author||Joey Armstrong <firstname.lastname@example.org>||Fri Dec 30 11:44:44 2022 -0500|
|committer||Joey Armstrong <email@example.com>||Fri Dec 30 11:45:30 2022 -0500|
VOL-4836 - Cosmetic edits to trigger a jenkins job. Makefile VERSION db/model/proxy.go db/model/proxy_test.go rw_core/core/adapter/agent.go rw_core/core/adapter/common.go rw_core/core/device/agent_flow.go rw_core/core/device/state/transitions.go rw_core/core/kv.go rw_core/route/device_route.go Change-Id: I7b5be068cca04456ad988d0436079d33d7f05843
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.