Gitiles
Code Review Sign In
gerrit.opencord.org / voltha-go / ad06fd7e6f5aa160bf7e426911757c8b68fbb23b
commitad06fd7e6f5aa160bf7e426911757c8b68fbb23b[log] [tgz]
authorkhenaidoo <knursimu@ciena.com>Mon Oct 28 12:26:05 2019 -0400
committerkhenaidoo Nursimulu <knursimu@ciena.com>Mon Oct 28 18:15:21 2019 +0000
tree94099499696717a6b6f41d2e985d16f63608220c
parentec1043c0a0b4df59b3f7e4f15dff4c1543d89c1a [diff]
[VOL-2174] Race condition when creating NNI port

This commit fixes the race condition where a the NNI logical port
is not created.  The root cause is that at the time an addport
request is received the parent id of the root device was not set
leadint the addport to believe that it does not exist even if it
does.

Change-Id: Ib9de9f4d3fd74fc142c35a75ba5f9a836985715b
3 files changed
tree: 94099499696717a6b6f41d2e985d16f63608220c
  1. .gitignore
  2. .gitreview
  3. BUILD.md
  4. Makefile
  5. README.md
  6. VERSION
  7. cli/
  8. common/
  9. compose/
  10. docker/
  11. go.mod
  12. go.sum
  13. python/
  14. quickstart.md
  15. ro_core/
  16. rw_core/
  17. tests/
  18. 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.