Gitiles
Code Review Sign In
gerrit.opencord.org / voltha / refs/tags/voltha-1.0-rc1
tag2a51e3a6ed7f2c98929fdb60e6c5c8412b9773bf
taggerKim Kempf <kim.kempf@radisys.com>Fri Sep 08 13:29:23 2017 -0700
objectcd51f990872d347f1fd975d71d93cc6eef428185 
Voltha 1.0 Release Candidate 1
commitcd51f990872d347f1fd975d71d93cc6eef428185[log] [tgz]
authorStephane Barbarie <sbarbari@ciena.com>Thu Sep 07 16:37:02 2017 -0400
committerkhenaidoo Nursimulu <knursimu@ciena.com>Fri Sep 08 10:27:51 2017 -0700
treef9b29c828eb54dafd8db03d6846ea082435c1c10
parenta25df1c9a8de4e694953793a32c758c80ba5aaf5 [diff]
VOL-411 Updated broken integration tests
- send REST requests to envoy port 8443
- Added some logic to handle GRPC codes returned in HTTP header
- Updated ofagent compose file to use latest configuration
- Fixed misc problems that prevented a clean execution
- Marked a few test cases as skipped for which i will raise new jiras
- Updated README file for alarm events tests

Amendments:
- Added description in skip statements
- Renamed expected_code to expected_http_code
- Fixed image download test that still had references to REST local path

Change-Id: I740e0ba344e2bcba3415315bb1bd5d8bb6ae1954
17 files changed
tree: f9b29c828eb54dafd8db03d6846ea082435c1c10
  1. .dockerignore
  2. .gitignore
  3. BUILD.md
  4. BuildingVolthaUsingVagrantOnKVM.md
  5. GettingStartedLinux.md
  6. Jenkinsfile
  7. LICENSE.txt
  8. Makefile
  9. README.md
  10. TODO.md
  11. Vagrantfile
  12. ansible/
  13. build.gradle
  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. gradle.properties
  26. gradle/
  27. gradlew
  28. gradlew.bat
  29. install/
  30. kafka/
  31. netconf/
  32. netopeer/
  33. nginx_config/
  34. obsolete/
  35. ofagent/
  36. pki/
  37. podder/
  38. ponsim/
  39. portainer/
  40. reg_config/
  41. requirements.txt
  42. scripts/
  43. settings.gradle
  44. settings.vagrant.yaml
  45. setup.mk
  46. setup.py
  47. shovel/
  48. tests/
  49. tmp_integration.md
  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.