Gitiles
Code Review Sign In
gerrit.opencord.org / voltha / 91730da3a686e7b2ebb74316aaed366ff58fae81
commit91730da3a686e7b2ebb74316aaed366ff58fae81[log] [tgz]
authorZsolt Haraszti <zharaszt@ciena.com>Mon Dec 12 12:54:38 2016 -0800
committerZsolt Haraszti <zharaszt@ciena.com>Mon Dec 12 18:27:27 2016 -0800
tree70be87f6d78c9965b160e8864d8c6613ca1aa4bd
parent83fab675a96de3bb966fe3c5612b7a301948ff89 [diff]
Reintegrate with olt-oftest

* Added updated notes on how to run voltha with olt-oftest
  in fake_dataplane mode (for now)
* Relocated test_flow_decompose to unittest
* Added new comprehensive unit test for LogicalDeviceAgent.
  Note that this class covers the following important
  business logic:
  * handling flow_mod and group_mod requests coming from the
    NBI
  * building route table and default flows/groups tables
    for the physical devices
  * performs flow decomposition from the logical device
    flows/groups to the physical device flows/groups
  All three functions are covered by tests now.
* Many small fixes/imporvements pciked up by the tests.

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