Gitiles
Code Review Sign In
gerrit.opencord.org / voltha / 61c2e9814b3fed34c3b9a0124690f8f54b145ff6
commit61c2e9814b3fed34c3b9a0124690f8f54b145ff6[log] [tgz]
authorGamze Abaka <gamze.abaka@netsia.com>Wed Feb 14 11:03:36 2018 +0000
committerkhenaidoo Nursimulu <knursimu@ciena.com>Thu Apr 05 13:55:56 2018 +0000
tree39b52572d946e6bc10bd12e80ce855dbf33b4346
parent3b67e335b91ec1efd547d2111195337b05952354 [diff]
When we use voltha-onos docker, onos sends clear_actions instruction to voltha ofagent component. voltha ofagent component doesnt handle this instruction type and creates an exception:
20180124T125506.456 ERROR of_protocol_handler.handle_flow_mod_request
{e: <class 'loxi.of13.instruction.clear_actions'>, event: failed-to-convert, exception: Traceback (most recent call last): File "/ofagent/ofagent/of_protocol_handler.py", line 122, in handle_flow_mod_request grpc_req = to_grpc(req) File "/ofagent/ofagent/converter.py", line 52, in to_grpc return converter(loxi_object) File "/ofagent/ofagent/converter.py", line 244, in loxi_flow_mod_to_ofp_flow_mod instructions=[to_grpc(i) for i in lo.instructions]) File "/ofagent/ofagent/converter.py", line 51, in to_grpc converter = to_grpc_converters[cls] KeyError: <class 'loxi.of13.instruction.clear_actions'>, instance_id: compose_ofagent_1}
As a conclusion, we see the flows at pending_add state when we check them at Onos cli.

Change-Id: Icde46ba15dccaa2d25920d5d5d104baf88bdd22b
3 files changed
tree: 39b52572d946e6bc10bd12e80ce855dbf33b4346
  1. .dockerignore
  2. .gitignore
  3. BUILD.md
  4. BuildingVolthaUsingVagrantOnKVM.md
  5. DOCKER_BUILD.md
  6. GettingStartedLinux.md
  7. Jenkinsfile
  8. LICENSE.txt
  9. Makefile
  10. README.md
  11. TODO.md
  12. Vagrantfile
  13. ansible/
  14. cli/
  15. common/
  16. compose/
  17. consul_config/
  18. dashd/
  19. docker/
  20. docs/
  21. env.sh
  22. envoy/
  23. experiments/
  24. fluentd_config/
  25. install/
  26. k8s/
  27. kafka/
  28. netconf/
  29. netopeer/
  30. nginx_config/
  31. obsolete/
  32. ofagent/
  33. pki/
  34. ponsim/
  35. portainer/
  36. reg_config/
  37. requirements.txt
  38. scripts/
  39. settings.vagrant.nightly-docker.yaml
  40. settings.vagrant.nightly.yaml
  41. settings.vagrant.yaml
  42. setup.mk
  43. setup.py
  44. shovel/
  45. tests/
  46. tmp_integration.md
  47. unum/
  48. vagrant-base/
  49. 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.