Gitiles
Code Review Sign In
gerrit.opencord.org / voltha / f3593a89733e0447da8df8f8498db4aa830bbb07
commitf3593a89733e0447da8df8f8498db4aa830bbb07[log] [tgz]
authorkhenaidoo <knursimu@ciena.com>Fri Jun 01 16:41:31 2018 -0400
committerkhenaidoo Nursimulu <knursimu@ciena.com>Mon Jun 04 13:26:28 2018 +0000
treebf14a7050038ac8466378334ee1a84de0fded9b4
parent253461fdac252f1e0939d67dc1083e6b66906c5f [diff]
[VOL-909] Add support to add and remove individual flows in voltha
core.

This update implements the logic in the voltha core to populate
only newly added flows or newly deleted flows to the adapters.  In
order for adapters to take advantage of that capability, the adapter
needs to set the accepts_add_remove_flow_updates flag to True when
registering their supported device types and also implements the
remove_from_flow_table() and add_to_flow_table() methods. Example
of these can be found in the ponsim adapter.  The above methods in
the ponsim adapters (one and olt) are not fully implemented as that
would require a change in the actual ponsim devices (a Jira will be
raised to follow-up this work).  Also, since these methods are not
implemented in the ponsim adapters then the accepts_add_remove_flow_updates
flag is set to False for now (the code was tested locally by setting that
flag to True and ensure the implemented logic works).

Additional work will eventually be required to optimized the flow decomposer
logic to decompose only newly added or deleted flows.  This work will
be performed as part of the voltha 2.0 effort.

 Please enter the commit message for your changes. Lines starting

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