Gitiles
Code Review Sign In
gerrit.opencord.org / voltha / b706784b2101bd75737299d44f4d19b2cf53bb1c
commitb706784b2101bd75737299d44f4d19b2cf53bb1c[log] [tgz]
authorZsolt Haraszti <zharaszt@ciena.com>Tue Nov 22 18:11:53 2016 -0800
committerZsolt Haraszti <zharaszt@ciena.com>Mon Nov 28 00:52:54 2016 -0800
treeb3f2c56c4db302f93a0b3ff8dd0c64e36355bb25
parentb49dda9f2fe1d97e40efdf88fa523fc12c0f6abc [diff]
Initial take on persistence support via k/v stores,

This is the initial mechanisms for persistence, supported
by a k/v store. In the initial testing the k/v store
is mcoked by a simple (in-memory) dict, but the concept
will carry to external, replicated, distributed k/v
store options, such as cassandra, redis, or even
consul for small-scale deployments.

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