Gitiles
Code Review Sign In
gerrit.opencord.org / voltha / 15274590011ce59a1d70dffe136a0e5ff43457bd
commit15274590011ce59a1d70dffe136a0e5ff43457bd[log] [tgz]
authorRichard Jankowski <rjankows@ciena.com>Tue Dec 12 15:52:37 2017 -0500
committerRichard Jankowski <rjankows@ciena.com>Tue Dec 12 15:52:37 2017 -0500
tree71685abd7d3e0a26db687c3e9fc32b0df3454809
parentd582367242e7b39a7501637d3f596e99f8da62b5 [diff]
VOL-580: Update envoy to support either consul or etcd in a kubernetes cluster

Envoy is refactored such that it interworks with either consul or etcd. The refactoring
should not have changed any of envoy's behaviour with consul. The update was tested with
only the vcli, envoy, vcore, and KV-store (consul or etcd) containers:
- tested with consul on a kubernetes 3-node cluster
- tested with etcd on a kubernetes 3-node cluster
- tested with consul on a 3-node docker swarm
- container and node failure testing not performed

This update enables some experimentation of envoy in the kubernetes environment.
There is more work to be done.  Future updates could:
- replace the current polling of etcd's assignment key with an asynchronous technique
- make use of data consistency options in etcd get requests
- make greater use of object orientation

Change-Id: Ia22893cdf331967eee4d13e060fd2c5ba7adb321
3 files changed
tree: 71685abd7d3e0a26db687c3e9fc32b0df3454809
  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.