Skip to content

wurei/voltha

This branch is 2 commits ahead of, 553 commits behind opencord/voltha:master.

Folders and files

NameName
Last commit message
Last commit date

Latest commit

c9fcd15 · Jan 25, 2018
Oct 26, 2017
Nov 15, 2017
Jan 22, 2018
Jan 25, 2018
Aug 24, 2017
Jul 17, 2017
Jan 24, 2018
Jan 19, 2018
Jan 24, 2018
Dec 22, 2016
Jan 19, 2018
Jan 24, 2018
Jan 18, 2018
Jan 16, 2017
Jan 18, 2018
Jun 7, 2017
Oct 27, 2017
Oct 24, 2016
Nov 21, 2017
Jul 7, 2017
Oct 27, 2017
Jan 24, 2018
Jun 6, 2017
Jul 6, 2017
Jan 18, 2017
Jan 19, 2018
Jan 24, 2018
Oct 27, 2017
Jan 23, 2018
Feb 24, 2017
Jan 19, 2018
Jan 19, 2018
Jun 19, 2017
Jan 24, 2018
Oct 26, 2017
Aug 4, 2017
Jan 24, 2018
Sep 22, 2016
Dec 23, 2016
Oct 31, 2017
Dec 10, 2016
Dec 20, 2017
Oct 31, 2017
Oct 31, 2017
Sep 19, 2016
Jan 12, 2018
Dec 23, 2016

Repository files navigation

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.

About

Virtual OLT Hardware Abstraction

Resources

License

Stars

Watchers

Forks

Packages

No packages published

Languages

  • Python 87.2%
  • Shell 8.9%
  • XSLT 2.2%
  • Go 0.8%
  • Makefile 0.5%
  • C 0.4%