Gitiles
Code Review Sign In
gerrit.opencord.org / voltha / 8725ea8722118789d4c9cd34a0625b3fdbe002fe
commit8725ea8722118789d4c9cd34a0625b3fdbe002fe[log] [tgz]
authorSergio Slobodrian <sslobodr@ciena.com>Sun Aug 27 23:47:41 2017 -0400
committerkhenaidoo Nursimulu <knursimu@ciena.com>Mon Aug 28 07:06:34 2017 -0700
tree2296a3d6816ea654cc88dc7c5435e031aeefe31d
parentcbe30830ac1495409cfbdeb37a59d2e0523dd33e [diff]
VOL-393 VOL-395 This update implements a replicated filesystem allowing
fluentd logs to be accessible from all cluster servers. The replicated
filesystem also limits the aggregate size of the logs to limit the
amount of disk space that they consume. This update also
creates a barrier filesystem for consul ensuring that the consul data
can't be affected by a disk full condition. Finally, some serious
changes were made to the fluentd clustering implememtation which was
very sub-optimal and wouldn't start correctly 9 times out of 10.
Added improved debygguing log collection that checks if the log file is
still growing before it kills the collection process. Added consul
release 0.9.2 to the production containers list. Removed fluent/fluentd
from containers.cfg. Added configuration options to the installer to set
the size of the barrier files.

Change-Id: I89389d76b081b0e6c3961e62d24277b1d2cf3cfb
15 files changed
tree: 2296a3d6816ea654cc88dc7c5435e031aeefe31d
  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.