Gitiles
Code Review Sign In
gerrit.opencord.org / voltha / 263900e32ee86eb7a7012f8159d1bf50c7ae2c8c
commit263900e32ee86eb7a7012f8159d1bf50c7ae2c8c[log] [tgz]
authorSergio Slobodrian <sslobodr@ciena.com>Fri Jun 16 21:39:04 2017 -0400
committerSergio Slobodrian <sslobodr@ciena.com>Fri Jun 16 21:39:04 2017 -0400
tree2692fb68802e2dd08a88a1f42fa1886a0d9e72b6
parent7bca172f45f4d06f73c379f4b9a64ce1ed56edc4 [diff]
Added the deployment and initialization of base services required for
vOLT-HA. These are consul, zookeeper, and kafka. All services are
deployed in 3 member clusters. voltha is also started as a single
instance to demonstrate that it interacts with the consul cluster and
creates the keys in the KV store as expected.
Added updates to the documentation to ensure it's crystal clear how the
bare metal server needs to be set up.
This update continues to address VOL-6.

Change-Id: I909f2e70b117589ba7e119a9840a2c810a7991cb
10 files changed
tree: 2692fb68802e2dd08a88a1f42fa1886a0d9e72b6
  1. .dockerignore
  2. .gitignore
  3. BUILD.md
  4. BuildingVolthaUsingVagrantOnKVM.md
  5. GettingStartedLinux.md
  6. Jenkinsfile
  7. LICENSE.txt
  8. Makefile
  9. README.md
  10. TODO.md
  11. Vagrantfile
  12. ansible/
  13. build.gradle
  14. cli/
  15. common/
  16. compose/
  17. consul_config/
  18. dashd/
  19. docker/
  20. docs/
  21. env.sh
  22. experiments/
  23. gradle.properties
  24. gradle/
  25. gradlew
  26. gradlew.bat
  27. install/
  28. kafka/
  29. netconf/
  30. netopeer/
  31. nginx_config/
  32. obsolete/
  33. ofagent/
  34. podder/
  35. ponsim/
  36. portainer/
  37. reg_config/
  38. requirements.txt
  39. scripts/
  40. settings.gradle
  41. settings.vagrant.yaml
  42. setup.mk
  43. setup.py
  44. shovel/
  45. tests/
  46. tmp_integration.md
  47. vagrant-base/
  48. 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.