Gitiles
Code Review Sign In
gerrit.opencord.org / voltha / abd9c8489b27f1af35d2fdc0deb47c5d816ca0c2
commitabd9c8489b27f1af35d2fdc0deb47c5d816ca0c2[log] [tgz]
authorCraig Lutgen <craig.lutgen@tellabs.com>Thu Nov 15 23:58:27 2018 +0000
committerCraig Lutgen <craig.lutgen@tellabs.com>Tue Dec 11 22:47:23 2018 +0000
tree7172fd472b27b36435a156f4656067aff33ddece
parentbf5ae0c7976a805bac7300968c716c2cf1393732 [diff]
VOL-1023 - Supporting multiple UNI per ONU

Added support for multiple UNIs per ONU by enabling an opt-in parameter in Resource Manager Profile
attribute key "uni_id_start" and "uni_id_end". This represents the 0 based local-device uni
index range. So, for an ONU to support a single UNI, the default (including omitted) value is 0.
To support multiple UNIs per ONU, set "uni_id_end" to the maximum (0-based) index on the ONU.

Plumbed in support throughout for multiple UNIs. Each UNI receives a dedicated TCONT/GEM from
TechProfile and is applied a dedicated MAC Bridge Instance in the ONU. Each UNI is effectively
treated the same whether on the same or different ONUs.

uni_id is used throughout to be the ONU-relative device port number (0-based)
port_no is the logical port number

Change-Id: I443d2322a2d414a358f1e0c629779c4929ce13c8
17 files changed
tree: 7172fd472b27b36435a156f4656067aff33ddece
  1. .dockerignore
  2. .gitignore
  3. .gitreview
  4. BUILD.md
  5. BuildingVolthaUsingVagrantOnKVM.md
  6. DOCKER_BUILD.md
  7. GettingStartedLinux.md
  8. Jenkinsfile
  9. LICENSE.txt
  10. Makefile
  11. README.md
  12. TODO.md
  13. Vagrantfile
  14. alarm-generator/
  15. ansible/
  16. cli/
  17. common/
  18. compose/
  19. consul_config/
  20. dashd/
  21. docker/
  22. docs/
  23. env.sh
  24. envoy/
  25. experiments/
  26. fluentd_config/
  27. install/
  28. k8s/
  29. kafka/
  30. netconf/
  31. netopeer/
  32. nginx_config/
  33. obsolete/
  34. ofagent/
  35. pki/
  36. ponsim/
  37. portainer/
  38. reg_config/
  39. requirements.txt
  40. scripts/
  41. settings.vagrant.nightly-docker.yaml
  42. settings.vagrant.nightly.yaml
  43. settings.vagrant.yaml
  44. setup.mk
  45. setup.py
  46. shovel/
  47. tests/
  48. tmp_integration.md
  49. unum/
  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.