Gitiles
Code Review Sign In
gerrit.opencord.org / voltha / 656ecc6676367d7483667550fa91046d7a8c0719
commit656ecc6676367d7483667550fa91046d7a8c0719[log] [tgz]
authorZsolt Haraszti <zharaszt@ciena.com>Wed Dec 28 15:08:23 2016 -0800
committerZsolt Haraszti <zharaszt@ciena.com>Thu Dec 29 00:15:43 2016 -0800
tree4f934b1feda7c7032da3a62d09f4e101929ff5fa
parent313c4be4cfc0b0e1bb2551efed6489333b195bfb [diff]
PONSIM: PON simulator with real dataplane handling

This was needed because neither CPQD nor OVS can handle
both zero-tagged packets and 802.1ad (QinQ).

- extensive unittest proves ponsim functional correctness
  (for the common use-cases needed in the PON scenario)
- integrated with frameio and coupled with a rather
  simple gRPC NBI, ponsim can be operated from Voltha
  just like a real PON system
- posim_olt/_onu adapters added to Voltha to work on
  ponsim
- CLI can be used to preprovision and activate a PONSIM
  instance (e.g., preprovision_olt -t ponsim_olt -H localhost:50060)
- Some of olt-oftest:olt-complex testcases can be run on
  the ponsim device (in vagrant/Ubuntu environment),
  but there are some remaining issues to work out:
  - barrier calls in OF do not guaranty that the flow
    is already installed on the device. This is a generic
    issue, not just for ponsim.
  - the whole test framework is inconsistent about zero-
    tagged vs. untagged frames at the ONUs, while ponsim
    is rather pedantica and does exactly what was defined
    in the flows.

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