Gitiles
Code Review Sign In
gerrit.opencord.org / voltha / 4ea26639bdfe2c1ebef177080382069b37e5f72e
commit4ea26639bdfe2c1ebef177080382069b37e5f72e[log] [tgz]
authorRichard Jankowski <rjankows@ciena.com>Mon May 14 17:45:38 2018 -0400
committerkhenaidoo Nursimulu <knursimu@ciena.com>Tue May 15 18:38:23 2018 +0000
treebc3b1f99438cc6ecffc5c5527b773ddce7b63b2d
parent1fd9eb2702b722ce12883d5aa5dd4dff29c701a1 [diff]
VOL-794: Assignment lists in etcd not updated correctly in presence of vcore failures

* Fixed coordinator method _sanitize_member_list
* Fixed keys-only GET operation for etcd KV store
* Fixed key DELETE operation for etcd KV store
* Modified vcore manifest to allow a failed pod to be re-spawned on a
  different host but with the same pod name
* Modified zookeeper manifest to allow a failed pod to be re-spawned
  on a different host. With the current manifest, when all 3 zookeeper
  pods are scheduled on the same node and that node fails, none of the
  pods get re-spawned.
* Added NodePort for the Envoy service
* Removed anti-affinity rule from OFAgent and NetConf manifests to allow
  the deployment of multiple pods on the same node

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