Gitiles
Code Review Sign In
gerrit.opencord.org / voltha / ba9cbd8c494b46da2004c9241296ec53665ae894
commitba9cbd8c494b46da2004c9241296ec53665ae894[log] [tgz]
authorSergio Slobodrian <sslobodr@ciena.com>Thu Jun 22 11:45:49 2017 -0400
committerSergio Slobodrian <sslobodr@ciena.com>Thu Jun 22 11:45:49 2017 -0400
treec2e64f790db5e9b748854ef0d4f303da7989d408
parentd908496fffde59b2f9436d8ab9c2dc9b0cfd9d82 [diff]
VOL-241 VOL-239 VOL-257 VOL-258 This update solves multiple problems
and cleans up the ansible tree somewhat.
VOL-241 Removes the error messages during dependent software installation
VOL-239 Removes the dependency on apt-get -y -f
VOL-257 Adds a config file to specify the docker containers required for
        a production deployment of vOLT-HA
VOL-258 Adds error checking after the voltha VM executes the vOLT-HA
        build to stop on errors rather than continuing and having the
        installer fail much later when docker containers are missing.
- General cleanup of the ansible tree.
  - Removal of ansible centos conditionals since they're not required.
  - Removal of the check for puppet and chef, not required.
- Adds a cleanup script that will remove temporary files added
  during an install so they don't get submitted to the repo by
  accident.

Note there are lots of commented out lines in the ansible scripts.
These will be removed in a subsequent update.

Change-Id: I92da352408dbfed1a05d13a1e10003f169be6a66
25 files changed
tree: c2e64f790db5e9b748854ef0d4f303da7989d408
  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. experiments/
  23. gradle.properties
  24. gradle/
  25. gradlew
  26. gradlew.bat
  27. install/
  28. kafka/
  29. netconf/
  30. netopeer/
  31. nginx_config/
  32. obsolete/
  33. ofagent/
  34. podder/
  35. ponsim/
  36. portainer/
  37. reg_config/
  38. requirements.txt
  39. scripts/
  40. settings.gradle
  41. settings.vagrant.yaml
  42. setup.mk
  43. setup.py
  44. shovel/
  45. tests/
  46. tmp_integration.md
  47. vagrant-base/
  48. 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.