Gitiles
Code Review Sign In
gerrit.opencord.org / voltha / 85f128572377f07111bc381ccd2e0e007be70932
commit85f128572377f07111bc381ccd2e0e007be70932[log] [tgz]
authorZsolt Haraszti <zharaszt@ciena.com>Sat Dec 24 08:30:58 2016 -0800
committerZsolt Haraszti <zharaszt@ciena.com>Mon Dec 26 10:29:55 2016 -0800
tree1cbc648e4a7e38f196ce4187d25d3cabeb329933
parent8017520ce20396dabf017daa33098ec81609a158 [diff]
Many CLI cleanups and flow preintegration

Changes:
- auto-completion for device and logical device IDs
- a set of test CLI commands to push down various flows
  to Voltha (aids test and integration)
- sample code in simulated_olt and onu to show how
  to process incoming bulk flow table
- extended Tibit OLT and ONU code with remaining flow
  directives they need to handle in the PON use-case

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