Gitiles
Code Review Sign In
gerrit.opencord.org / voltha / 3b31db944a8520034165edf073f569eef49522de
commit3b31db944a8520034165edf073f569eef49522de[log] [tgz]
authorNikolay Titov <nikolay.titov@nokia.com>Wed Aug 02 18:11:33 2017 -0400
committerSireesha Kora <sireesha.kora@nokia.com>Fri Aug 04 13:44:17 2017 -0700
treedf27075335ba29b2d29865cd5060803078ca26cd
parent83916f047aeea8836537059d70f7d726ad4f9dde [diff]
VOL-174: Support configuration of GEMs as per WT-385 and auto-allocation of gemport-ids

 * As an operator, I should be able to provision a GEMPORT object for the ONU and assign to a UNI
 * As an operator, I should be able to retrieve the provisioned GEMPORT

Additional Notes:

 * gemport-ids should be auto-allocated for the GEMPORT object
 * generic IAdapter interface to be provided that will be used by OLT and ONU adapters for GEM port configuration
 * In the best interest of schedules/timing, in the first step(e.g. POC-3 & trial), assume the queueing model to be supported (to be detailed) (i.e. no configuration of queueing model)
 * The concerned OLT and ONU should be configured with the allocated gemport-ids

VOL-173: Support configuration of TCONTs as per WT-385 and auto-allocation of alloc-ids

 * As an operator, I should be able to provision a TCONT for the ONU with an existing traffic descriptor profile
 * As an operator, I should be able to retrieve the provisioned TCONT
 * As an operator, I should be able to change the traffic descriptor profile for a TCONT

Additional Notes:

 * alloc-ids should be allocated for the TCONT
 * generic IAdapter interface to be provided that will be used by OLT and ONU adapters for TCONT/alloc-id/BW configuration
 * In the best interest of schedules/timing, in the first step(e.g. POC-3 & trial), assume the queueing model to be supported (to be detailed) (i.e. no configuration of queueing model)
 * The concerned ONU should receive upstream grants upon provisioning of TCONT for the ONU

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