Gitiles
Code Review Sign In
gerrit.opencord.org / voltha-go / dec9317578c20264c5ab0332fbb8a09cd8da2e57
commitdec9317578c20264c5ab0332fbb8a09cd8da2e57[log] [tgz]
authorRichard Jankowski <rjankows@ciena.com>Tue Feb 12 14:59:28 2019 -0500
committerRichard Jankowski <rjankows@ciena.com>Tue Feb 12 14:59:45 2019 -0500
tree829773d36df576a5977b50bc9f942c1caeab564e
parent0a97e9b7c7d99d30317e358668cd1e5f5709d485 [diff]
VOL-1410: Integration testing between the OFAgent,
          Affinity Router and the Voltha Core
- Added metadata key 'voltha_backend_name' to OFagent's
  ReceivePacketsIn RPC to support northbound streaming of
  packet-in frames through the affinity router toward ONOS.
- Added metadata key 'voltha_backend_name' to OFagent's
  ReceiveChangeEvents RPC to support northbound streaming
  of change-event messages through the affinity router
  toward ONOS.
- Adding missing args to the OFagent Kubernetes manifest.

Change-Id: Ica4af1747f6b7bcd67f662739cbf6f40bf746667
2 files changed
tree: 829773d36df576a5977b50bc9f942c1caeab564e
  1. .gitignore
  2. .gitreview
  3. BUILD.md
  4. Gopkg.lock
  5. Gopkg.toml
  6. Makefile
  7. README.md
  8. adapters/
  9. afrouter/
  10. arouterd/
  11. common/
  12. compose/
  13. db/
  14. docker/
  15. k8s/
  16. kafka/
  17. protos/
  18. python/
  19. ro_core/
  20. rw_core/
  21. tests/
  22. vendor/
README.md

VOLTHA

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 BUILD.md 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.