Gitiles
Code Review Sign In
gerrit.opencord.org / voltha-go / 802bf36511b0e804a218e20f62cd83378e4b4689
commit802bf36511b0e804a218e20f62cd83378e4b4689[log] [tgz]
authorMatt Jeanneret <mj3580@att.com>Sun Apr 14 20:33:08 2019 -0400
committerMatt Jeanneret <mj3580@att.com>Thu May 02 20:19:31 2019 +0000
treec038cd35c1569f40223d0a9ce104cdb41f9c145c
parentca4c51ea8c4d66470a5ab8a9e4900b7245bdd88f [diff]
VOL-1489: Add uni port id as tunnel id needed for olt flows

When the olt is asked to setup pon resources on the
onu/uni's behalf it needs to know what onu and uni port it
is dealing with for a particular flow.
Typically with flow decomposer the ports on the child
device (uni) are not visible on the parent. But in the case
of olt based flows (at least with BAL?) the parent device
needs to know the uni ports so it can create
gems, alloc id, and queues needed.

This patch adds new openflow tunnel id containing the uni port
to the decomposed flows for use by the adapter.

Change-Id: I0ea701b457ab5cb5877b953f58364d6a7806a58f
3 files changed
tree: c038cd35c1569f40223d0a9ce104cdb41f9c145c
  1. .gitignore
  2. .gitreview
  3. BUILD.md
  4. Gopkg.lock
  5. Gopkg.toml
  6. Makefile
  7. README.md
  8. adapters/
  9. afrouter/
  10. arouterd/
  11. cli/
  12. common/
  13. compose/
  14. db/
  15. docker/
  16. k8s/
  17. kafka/
  18. python/
  19. quickstart.md
  20. ro_core/
  21. rw_core/
  22. tests/
  23. vendor/
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.