Gitiles
Code Review Sign In
gerrit.opencord.org / voltha / 29dd1987b0e63d3ba500b8cb92aafd0b0a1b13c9
commit29dd1987b0e63d3ba500b8cb92aafd0b0a1b13c9[log] [tgz]
authorRichard Jankowski <rjankows@ciena.com>Wed Jun 28 13:30:18 2017 -0400
committerkhenaidoo Nursimulu <knursimu@ciena.com>Wed Jun 28 18:38:07 2017 -0700
tree94ba9132317b06816eef2567180e28b40655f079
parentb96ee0a30bcf98ee09208e857bcc172dfee36ff1 [diff]
VOL-211: Integrate a clustered Consul service with all Voltha components that use it

The Dockerfile for the CLI container runs a setup.sh script at container startup.
This script hard-codes the Consul lookup (-L) and endpoint (-C) arguments passed
to /cli/cli/main.py. In Docker swarm mode, Consul is no longer used for service
lookup; instead, Docker's DNS is used. It is desirable that the lookup argument
be specified in the compose file. For v2 -L is supplied and the Voltha gRPC and
SIM endpoints are specified by Consul service name. For v3 -L is withheld and the
Voltha gRPC and SIM endpoints are specified by Docker service name. Therefore, in
addition to a new v3 compose file for use by Docker swarm, the existing v2 compose
file used by the single-node Voltha implementation must be changed.

Change-Id: Ifef3e06ef9479594bfb11328dd1b1004e4f6c74f
4 files changed
tree: 94ba9132317b06816eef2567180e28b40655f079
  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.