Gitiles
Code Review Sign In
gerrit.opencord.org / voltha / cd22adc23cff59dd5f6a96ec12a5b336036937ec
commitcd22adc23cff59dd5f6a96ec12a5b336036937ec[log] [tgz]
authorZsolt Haraszti <zharaszt@ciena.com>Tue Oct 25 00:13:06 2016 -0700
committerZsolt Haraszti <zharaszt@ciena.com>Fri Oct 28 08:34:51 2016 -0700
treef8884eee569867f43a28b450a6c2242f458f1221
parent862883a240b41c87dc49d956246edd2d37c604e1 [diff]
Packet in/out streaming from ofagent to core
Getting ready for packet streaming

Change-Id: I8d70d4d6ffbb23c0d7ab20582e9afac49f9f6461

Support flow_delete_strict

Change-Id: I5dab5f74a7daddcddfeb8691a3940347cb2fc11b

Packet out halfway plumbed

Change-Id: I799d3f59d42ac9de0563b5e6b9a0064fd895a6f6

refactored async_twisted

Change-Id: I68f8d12ce6fdbb70cee398f581669529b567d94d

Packet in pipeline and ofagent refactoring

Change-Id: I31ecbf7d52fdd18c3884b8d1870f673488f808df
20 files changed
tree: f8884eee569867f43a28b450a6c2242f458f1221
  1. .dockerignore
  2. .gitignore
  3. BUILD.md
  4. Dockerfile.base
  5. Dockerfile.base.alpine
  6. Dockerfile.chameleon
  7. Dockerfile.ofagent
  8. Dockerfile.voltha
  9. GettingStartedLinux.md
  10. Jenkinsfile
  11. LICENSE.txt
  12. Makefile
  13. README.md
  14. Vagrantfile
  15. ansible/
  16. build.gradle
  17. chameleon/
  18. common/
  19. compose/
  20. env.sh
  21. experiments/
  22. gradle.properties
  23. gradle/
  24. gradlew
  25. gradlew.bat
  26. kafka/
  27. obsolete/
  28. ofagent/
  29. podder/
  30. requirements.txt
  31. settings.gradle
  32. setup.mk
  33. setup.py
  34. tests/
  35. voltha/
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.