Gitiles
Code Review Sign In
gerrit.opencord.org / voltha / 8592a239666129c4f167b79fa03189154c210750
commit8592a239666129c4f167b79fa03189154c210750[log] [tgz]
authorKoray Kokten <koraykokten@netsia.com>Mon Aug 27 07:41:14 2018 +0000
committerkhenaidoo Nursimulu <knursimu@ciena.com>Tue Oct 30 15:45:22 2018 +0000
treecb607a6ea641d45f5346df6cc1866c3c24ec7912
parent65423ce331ffb56ca27e104a85e5a55fe544c4b8 [diff]
733: Insert the description of the change.Need to support Error Checking for consistency – if Meter Reference made then need Meter to exist first before reference.

If Flow Table ID does not resolve to a Technology Profile in KV Store generate an error – initial approach to simplify implementation - the Technology for the Profile will not be used to qualify the lookup.

Initially just do OF agent checks which do not need knowledge available in the adapter i.e. Meter Band Reference requires Meter Band definition first. Any Forward References need error checks (OF Error messages).

OF Agent needs to pass through the Meter/Meter Band programming and the Flow Table ID used to reference the Technology Profile.

The VOLTHA core needs to be able to receive meters from the OFAgent and store them in the appropriate logical device. A new northbound API needs to be added to the core to support this.

Change-Id: Ide776dbcbc04232c1d929a85707fec09e3dedf6f
8 files changed
tree: cb607a6ea641d45f5346df6cc1866c3c24ec7912
  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. alarm-generator/
  15. ansible/
  16. cli/
  17. common/
  18. compose/
  19. consul_config/
  20. dashd/
  21. docker/
  22. docs/
  23. env.sh
  24. envoy/
  25. experiments/
  26. fluentd_config/
  27. install/
  28. k8s/
  29. kafka/
  30. netconf/
  31. netopeer/
  32. nginx_config/
  33. obsolete/
  34. ofagent/
  35. pki/
  36. ponsim/
  37. portainer/
  38. reg_config/
  39. requirements.txt
  40. scripts/
  41. settings.vagrant.nightly-docker.yaml
  42. settings.vagrant.nightly.yaml
  43. settings.vagrant.yaml
  44. setup.mk
  45. setup.py
  46. shovel/
  47. tests/
  48. tmp_integration.md
  49. unum/
  50. vagrant-base/
  51. 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.