Core pre-pairing.

This requires changes to voltha-helm-charts to work correctly, please consider/merge both patches together.

- Removed existing core pairing/re-pairing logic.
- Removed SetConnection calls to the affinity router, re-routing when cores move is now handled by headless k8s services.  (See voltha-helm-charts change.)
- Reworked deviceId polling, core syncing, and afrouter affinity configuration.  New algorithm has been drastically simplified.
- Removed wait for all RW/RO cores to be up.  Since pairing is no longer handled here, the location of every core doesn't need to be known.
- Removed all references to RO cores, as all configuration now handled by k8s headless services.  (See voltha-helm-charts change.)
- Fixed a bug where the kafka device monitor was incorrectly configuring the affinity router due to a deviceId being passed where a coreId was expected.  Rather hackish solution determines which backend to use from the kafka message's publisher.

Change-Id: I7b1c119b2dd772e2122767d16d1c1d03c387db90
2 files changed
tree: 951a597b8c3f029a1cef70e9dcd51f4bcfefff84
  1. .gitignore
  2. .gitreview
  4. Gopkg.lock
  5. Gopkg.toml
  6. Makefile
  9. adapters/
  10. afrouter/
  11. arouterd/
  12. cli/
  13. common/
  14. compose/
  15. db/
  16. docker/
  17. k8s/
  18. kafka/
  19. python/
  21. ro_core/
  22. rw_core/
  23. tests/
  24. vendor/


What is Voltha?

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:

  • Network as a Switch: It makes a set of connected access network devices to look like a(n abstract) programmable flow device, a L2/L3/L4 switch. Examples:
    • PON as a Switch
    • PON + access backhaul as a Switch
    • xDSL service as a Switch
  • Evolution to virtualization: it can work with a variety of (access) network technologies and devices, including legacy, fully virtualized (in the sense of separation of hardware and software), and in between. Voltha can run on a decice, on general purpose servers in the central office, or in data centers.
  • Unified OAM abstraction: it provides unified, vendor- and technology agnostic handling of device management tasks, such as service lifecycle, device lifecycle (including discovery, upgrade), system monitoring, alarms, troubleshooting, security, etc.
  • Cloud/DevOps bridge to modernization: it does all above while also treating the abstracted network functions as software services manageable much like other software components in the cloud, i.e., containers.

Why 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.

How can you work with Voltha?

While we are still at the early phase of development, you can check out the file to see how you can build it, run it, test it, etc.

How can you help?

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.