Gitiles
Code Review Sign In
gerrit.opencord.org / voltha / c9d89206c5c7bd85fa27518b9fd0e7b61bd24a7f
commitc9d89206c5c7bd85fa27518b9fd0e7b61bd24a7f[log] [tgz]
authorRichard Jankowski <rjankows@ciena.com>Thu Jan 25 10:25:10 2018 -0500
committerRichard Jankowski <rjankows@ciena.com>Thu Jan 25 13:51:06 2018 -0500
tree8afbade78346446c564e1ae367479dee79179712
parent0910489e517c1803f83c88cd7d5e0bf0a9f1e00c [diff]
[8055]
This update adds kubernetes deployment files for the OFagent and fluentd services.

The OFagent calls get_my_containers_name with the assumption that the HOSTNAME
environment variable contains the docker container's ID, which does not appear
to be the case for kuberbetes. In kubernetes a container's HOSTNAME is its pod
name. Feeding a kubernetes pod name into the docker API used by
get_my_containers_name triggers an exception. This is the reason behind the
code changes to OFagent.

The kubernetes config files in this submission still use the old image naming
convention. The names in these and all the other kubernetes deployment files
will be changed to conform to the new convention in a separate update.

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