Gitiles
Code Review Sign In
gerrit.opencord.org / voltha-go / acc718fb3630bf82f901ddfc69bc49aa03e1a255
commitacc718fb3630bf82f901ddfc69bc49aa03e1a255[log] [tgz]
authorkhenaidoo <knursimu@ciena.com>Wed Aug 21 16:21:07 2019 -0400
committerkhenaidoo <knursimu@ciena.com>Wed Aug 21 16:23:19 2019 -0400
tree7d40c69e03a4f32240acb396d8eee0a21f11108c
parent434e2bb92c81113a60fcf4bbec855f7a13a40b0a [diff]
[VOL-1862] rwCore waits for Kafka and KV Store

This commit consists of the following:
1) Make the rw_core wait for kafka and KV Store to be up before
proceeding with its processing.  Previously, rw_core would have
bailed out if kafka/KV was not available. The number of retries
(default=-1, i.e retry forever) and retry interval are both
configurable.

2) Remove a non-json printable variable from the debug log in the
model.

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