Gitiles
Code Review Sign In
gerrit.opencord.org / voltha / 5a0ab6279ec2433a7ebd5df3383eb6838e8c1794
commit5a0ab6279ec2433a7ebd5df3383eb6838e8c1794[log] [tgz]
authorRyan Van Gilder <rvangild@ciena.com>Wed Mar 01 16:39:25 2017 -0800
committerkhenaidoo Nursimulu <knursimu@ciena.com>Thu Mar 02 17:29:42 2017 -0800
treef5f2a1d7bb9e36c40214fce166cb3e5dd1f2af76
parentcc6b2e6b901cfb7387bdc217c883cc0cec6ab06f [diff]
Add consul as a config backend

Two backends available, none and consul. Can be set through the
BACKEND environment variable or the --backend flag.
Currently access to consul blocks the reactor. Requests to consul
are cached. In my conversations with Zsolt, we concluded that
blocking the reactor is fine for now to prevent multiple tasks
from modifying the config at the same time. An easier first step
to making it all twisted is to add a write queue. That comes with its
own challenges though. A longer goal would be making the entire config
access inlineCallbacks, possibly with a locking mechanism to prevent
multiple tasks from modifying the config at once.

Change-Id: Ia3132a455ca03123dbb9b2e56c9f4df1202347cd
4 files changed
tree: f5f2a1d7bb9e36c40214fce166cb3e5dd1f2af76
  1. .dockerignore
  2. .gitignore
  3. BUILD.md
  4. GettingStartedLinux.md
  5. Jenkinsfile
  6. LICENSE.txt
  7. Makefile
  8. README.md
  9. TODO.md
  10. Vagrantfile
  11. ansible/
  12. build.gradle
  13. cli/
  14. common/
  15. compose/
  16. dashd/
  17. docker/
  18. docs/
  19. env.sh
  20. experiments/
  21. gradle.properties
  22. gradle/
  23. gradlew
  24. gradlew.bat
  25. kafka/
  26. netconf/
  27. obsolete/
  28. ofagent/
  29. podder/
  30. ponsim/
  31. requirements.txt
  32. scripts/
  33. settings.gradle
  34. setup.mk
  35. setup.py
  36. shovel/
  37. tests/
  38. tmp_integration.md
  39. vagrant-base/
  40. 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.