Gitiles
Code Review Sign In
gerrit.opencord.org / voltha / b9a5f75b53ac16778403ff43a7e4593e28c92f2c
commitb9a5f75b53ac16778403ff43a7e4593e28c92f2c[log] [tgz]
authorZsolt Haraszti <zharaszt@ciena.com>Sat Feb 11 06:07:08 2017 -0800
committerZsolt Haraszti <zharaszt@ciena.com>Sat Feb 11 06:20:31 2017 -0800
tree19ed7b27a9c79d7e505b13c64e4449caff9bf79d
parent353630d18c0d771c12a2b1607b92917eefd8de1f [diff]
Inject per-ONU metadata field for unicast flows

This is a CLI change to mimic a useful ONOS behavior when generating
logical flows for the PON. Specifically, ONOS injects a metadata
field in each flow rule for unicast downstream traffic, namely into
the first of the two flow rules handling the outer tag. The metadata
value is the vlan id of the inner tag. Without this metadata there
is no easily accessible information as to what inner tag that flow
is meant for.

This metadata value can be considered as a "hint" by the OLT adapters
to tie a downstream flow rule to a specific PON link/channel.

This is not an elegant solution, in that it slightly misuses the
metadata field. The more proper long-term solution would be to either
model the PON channels explicitly as flow ports, or use phys-port/port
pairs (the former representing the PON port itself, and the other
representing the logical channel/link on the PON.

It is recommended to switch to the cleaner solution at a later time.

Change-Id: I2a461014d697d01010101010101052609d742d04
3 files changed
tree: 19ed7b27a9c79d7e505b13c64e4449caff9bf79d
  1. .dockerignore
  2. .gitignore
  3. BUILD.md
  4. GettingStartedLinux.md
  5. Jenkinsfile
  6. LICENSE.txt
  7. Makefile
  8. README.md
  9. TODO.md
  10. Vagrantfile
  11. ansible/
  12. build.gradle
  13. cli/
  14. common/
  15. compose/
  16. docker/
  17. docs/
  18. env.sh
  19. experiments/
  20. gradle.properties
  21. gradle/
  22. gradlew
  23. gradlew.bat
  24. kafka/
  25. netconf/
  26. obsolete/
  27. ofagent/
  28. podder/
  29. ponsim/
  30. requirements.txt
  31. scripts/
  32. settings.gradle
  33. setup.mk
  34. setup.py
  35. shovel/
  36. tests/
  37. tmp_integration.md
  38. vagrant-base/
  39. 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.