Gitiles
Code Review Sign In
gerrit.opencord.org / voltha / 8b277c221466fc01481c6899ca6d58ee5bc246bb
commit8b277c221466fc01481c6899ca6d58ee5bc246bb[log] [tgz]
authorRichard Jankowski <rjankows@ciena.com>Tue Dec 19 09:49:27 2017 -0500
committerkhenaidoo Nursimulu <knursimu@ciena.com>Wed Dec 20 18:32:04 2017 +0000
tree28e696e448f3e7ec3d5c53c17958990fdb9ca7a8
parenta9eb021a1d247e458baf1c2654a4b248217588d7 [diff]
[7697]
VOL-582: Update the Voltha core to support either consul or etcd in a kubernetes cluster

This is an initial commit for etcd support by voltha.

Although this code works on a single-node or on a kubernetes cluster, it is NOT ready
for prime time. The integration tests have yet to be written and a kubernetes install
is not yet available.

Change-Id: I666a29a0a68cd7c2ab3c79aff8ccc6e96db96419
5 files changed
tree: 28e696e448f3e7ec3d5c53c17958990fdb9ca7a8
  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. envoy/
  23. experiments/
  24. fluentd_config/
  25. gradle.properties
  26. gradle/
  27. gradlew
  28. gradlew.bat
  29. install/
  30. k8s/
  31. kafka/
  32. netconf/
  33. netopeer/
  34. nginx_config/
  35. obsolete/
  36. ofagent/
  37. pki/
  38. podder/
  39. ponsim/
  40. portainer/
  41. reg_config/
  42. requirements.txt
  43. scripts/
  44. settings.gradle
  45. settings.vagrant.nightly.yaml
  46. settings.vagrant.yaml
  47. setup.mk
  48. setup.py
  49. shovel/
  50. tests/
  51. tmp_integration.md
  52. unum/
  53. vagrant-base/
  54. 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.