Gitiles
Code Review Sign In
gerrit.opencord.org / voltha / 5a2d5694237b9048c622232f1a6ab445213b465c
commit5a2d5694237b9048c622232f1a6ab445213b465c[log] [tgz]
authorRachit Shrivastava <rachit.shrivastava@nokia.com>Mon Jul 17 10:29:20 2017 -0400
committerkhenaidoo Nursimulu <knursimu@ciena.com>Tue Jul 18 13:07:17 2017 -0700
tree2cbaffa0f025a7ccfd9fee403b19e04a439f76ee
parent50ee9acf3cc118ceba7269bce8e915067f4e68bf [diff]
VOL-271: Support itests and utests for WT-385 xPON objects

itests support for the configuration of following WT-385 objects
 - v_ont_ani
 - ont_ani
 - v_enet

Code optimization for the test cases
README.md is updated to reflect the itests

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