Gitiles
Code Review Sign In
gerrit.opencord.org / voltha / 5431e4ce63877c565c2b105f86c60c5faef97db5
commit5431e4ce63877c565c2b105f86c60c5faef97db5[log] [tgz]
authorkhenaidoo <knursimu@ciena.com>Thu Aug 17 15:05:40 2017 -0400
committerkhenaidoo Nursimulu <knursimu@ciena.com>Fri Aug 18 06:02:15 2017 -0700
tree37e8ed053845a3f72884d97c3891482df84af55f
parent3f3788f8b7014fb922ffad9c54d55b94182bca99 [diff]
This update addresses the following:

1)  Fix an issue with peer grpc connection after a vcore instance
    is recycled.
2)  Set the default peer grpc retry to 0 for improved API performance in a
    cluster
3)  Adjust the logs level in the global_handler and local_handler.
    This basically removes unnecessary and performance impacting
    info logs and set some logs to warning instead of info.
4)  Add a test to detect whether the cluster is in a transient state.
    During that time, the coordinator leader waits until all previously
    running voltha instances are registered in Consul before upading the
    core assignments.  This means that to a previously running vcore will
    remain in the assignment list during the transient period, hence some
    API requests targetted that vcore will fail during that time.  Once
    all expected voltha instances are registered the coordinator leader
    will update the core assignment key, hence subsequent API requests
    should pass.

Change-Id: I918b6af8f9158444d9e612c490972493b9609344
7 files changed
tree: 37e8ed053845a3f72884d97c3891482df84af55f
  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. kafka/
  31. netconf/
  32. netopeer/
  33. nginx_config/
  34. obsolete/
  35. ofagent/
  36. pki/
  37. podder/
  38. ponsim/
  39. portainer/
  40. reg_config/
  41. requirements.txt
  42. scripts/
  43. settings.gradle
  44. settings.vagrant.yaml
  45. setup.mk
  46. setup.py
  47. shovel/
  48. tests/
  49. tmp_integration.md
  50. vagrant-base/
  51. 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.