Gitiles
Code Review Sign In
gerrit.opencord.org / voltha / 3f0c9dd9b67b0c3f51d26c47d3054adf5960c896
commit3f0c9dd9b67b0c3f51d26c47d3054adf5960c896[log] [tgz]
authorNikolay Titov <nikolay.titov@nokia.com>Mon Jul 17 17:37:25 2017 -0400
committerkhenaidoo Nursimulu <knursimu@ciena.com>Wed Jul 19 15:18:56 2017 -0700
tree055fff254b9d6b2039de10d4b3c74d6d261aa622
parent60a08d7eb022bfeff34bc52967a7039f0c4f92dd [diff]
VOL-288: Minor fixes for xPON cli in VOLTHA

Fix the following issues detected in the xPON cli:
 * Missing validation for device ID
 * 'show' command to display v_ont_ani, ont_ani
   and v_enet does not work for specific device id

VOL-290: Use interface_stack to implement child-parent relationship for xPON interface objects

Move to an elegant approach to use child-parent relationship for xPON interface objects to
determine the OLT and ONU device id(s) for sending configuration

Change-Id: Ia26154e3fe1fba1a650c6a53f4d5232fb7369ce3

Removing extra characters

Change-Id: I11d1e86bfa8c87c1c00852a469aa5a4e21d5b49c
3 files changed
tree: 055fff254b9d6b2039de10d4b3c74d6d261aa622
  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.