Gitiles
Code Review Sign In
gerrit.opencord.org / voltha / 3869d8ddfd092842b6d156b07334ac27f6390eb6
commit3869d8ddfd092842b6d156b07334ac27f6390eb6[log] [tgz]
authorKhen Nursimulu <knursimu@ciena.com>Mon Nov 28 20:44:28 2016 -0500
committerZsolt Haraszti <zharaszt@ciena.com>Sun Dec 04 23:43:10 2016 -0800
tree2950c8c65a4518d86f10d3d9b812a52dbb53533f
parent354487260b26edb93441a72b6e413fe335edd2fc [diff]
This is the initial commit of the netconf server code.  It consists
of the following:
1) The server is built using Twisted Conch
2) It adapted an existing opensource netconf server (https://github.com/choppsv1/netconf)
   to handle some low-level protocols.  The adaptation is mostly around
   using Twisted Conch instead of Python Threads
3) A microservice to interface with Voltha on the SB and Netconf client on
   the NB
4) A set of credentials for the server and clients.  At this time these
   credentials are local and in files.  Additional work is required to
   secure these files
5) A rough-in to handle the rpc requests from Netconf clients
6) Code for initial handshaking is in place (hello)

Change-Id: I1ca0505d0ac35ff06066b107019ae87ae30e38f8
25 files changed
tree: 2950c8c65a4518d86f10d3d9b812a52dbb53533f
  1. .dockerignore
  2. .gitignore
  3. BUILD.md
  4. Dockerfile.base
  5. Dockerfile.base.alpine
  6. Dockerfile.chameleon
  7. Dockerfile.ofagent
  8. Dockerfile.podder
  9. Dockerfile.voltha
  10. GettingStartedLinux.md
  11. Jenkinsfile
  12. LICENSE.txt
  13. Makefile
  14. README.md
  15. Vagrantfile
  16. ansible/
  17. build.gradle
  18. chameleon/
  19. common/
  20. compose/
  21. docs/
  22. env.sh
  23. experiments/
  24. gradle.properties
  25. gradle/
  26. gradlew
  27. gradlew.bat
  28. kafka/
  29. netconf/
  30. obsolete/
  31. ofagent/
  32. podder/
  33. requirements.txt
  34. settings.gradle
  35. setup.mk
  36. setup.py
  37. tests/
  38. vagrant-base/
  39. voltha/
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.