Gitiles
Code Review Sign In
gerrit.opencord.org / voltha / 1dd47089f1f0d0290945c5bdb897e6a04c03bfad
commit1dd47089f1f0d0290945c5bdb897e6a04c03bfad[log] [tgz]
authorCraig Lutgen <craig.lutgen@tellabs.com>Tue Oct 23 13:12:26 2018 -0500
committerCraig Lutgen <craig.lutgen@tellabs.com>Mon Oct 29 20:40:46 2018 -0500
treee425748e37c9df3a099857abf03f28531880105e
parentdeaebc9202fe3c156051983ff901bcbefbf55b1e [diff]
VOL-1289 - Update Resource Manager to support per-interface ranges

Updated Resource Manager and OpenOLT to support constructs for managing
resource pools by 1) each interface, 2) by all interfaces that share
a common technology, and 3) by all interfaces on the board.

The OpenOLT agent now supports returning, via DeviceInfo, a list of
1 or more range specifications. Each range corresponds to a unique
technology and identifies which interfaces on the board use that
technology and the start/end specifications for each resource type,
e.g. resource "pool". Options are provided for each pool to
independently be configured for (1) pool-per-interface, (2) pool-
per-technology, or (3) pool-per-device, a.k.a global.

A separate Resource Manager instance is used for each technology
range specification that manages (1) and (2) options. For (3),
one of the Resource Managers (arbitrarily chosen) is designated
as the "global" Resource Manager that is delegated to from
the subordinate RMs for those pools configured for (3) pool-per-
device.

For all pools, the Tech Profile is first read, if present. Then,
the device's technology range specification is overlayed to form a
subset of overlapping ranges. Then, globally-shared pools overalyed
again to form the overlapping ranges amongst all learned DeviceInfo
pools and TechProfile ranges.

Presently, behavior is undefined if no overlapping range exists
between TP and DevInfo ranges.

Backwards compatibility with OpenOLT agent drivers that only
support the original, single technology interface by synthesizing
a single range encompassing all interfaces with the start/end
specifications. In this case, the EdgeCore/BAL limitation for
resource sharing is set for Alloc ID and GEM Port ID.

Change-Id: I507ac013a114950dc0155b98a38406a42e2fba87
5 files changed
tree: e425748e37c9df3a099857abf03f28531880105e
  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.