Gitiles
Code Review Sign In
gerrit.opencord.org / voltha-go / 9a4689630eff5834207269a224e3a8652b4407e9
commit9a4689630eff5834207269a224e3a8652b4407e9[log] [tgz]
authorkhenaidoo <knursimu@ciena.com>Wed Sep 19 15:33:13 2018 -0400
committerkhenaidoo <knursimu@ciena.com>Wed Sep 19 15:33:13 2018 -0400
treef5c4c9d341052952e3874083d8091119b7c8789a
parent998f442b69b78dde4d6b16b74b1eb147a0097a23 [diff]
This commit consists of:
1) Update the voltha.proto to remove duplicates between the voltha message and
the CoreInstance.   Since all data will be stored into the clustered KV store
then it makes sense to use a clustered proto message instead of core specific.
Each core will hold a subset of the data, only those it is actively or passively
managing.
2) Add a Makefile into the adapters directory to clearly separate the build of
adapters to the core build.   This is work in progress.
3) Add an initial readme.md into the adapters directory to show how to run ponsim
olt and onu adapters in containers
4) Minor cleanup, mostly around name consistency.

Change-Id: I55155c41b56e95877f8735b536873a87d6ca63b1
18 files changed
tree: f5c4c9d341052952e3874083d8091119b7c8789a
  1. .gitignore
  2. .gitreview
  3. BUILD.md
  4. Makefile
  5. README.md
  6. adapters/
  7. common/
  8. compose/
  9. db/
  10. docker/
  11. kafka/
  12. protos/
  13. rw_core/
  14. tests/
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.