Gitiles
Code Review Sign In
gerrit.opencord.org / voltha / bbe1e09c2aacc235254b09d7ee7d077d0c3221de
commitbbe1e09c2aacc235254b09d7ee7d077d0c3221de[log] [tgz]
authorRichard Jankowski <rjankows@ciena.com>Thu Jan 18 13:48:20 2018 -0500
committerkhenaidoo Nursimulu <knursimu@ciena.com>Thu Jan 18 19:55:03 2018 +0000
treea4b31591027a450ad486065c20b1599e7de0946e
parent9adbc9597fd42c5231dfd2be63abc9f8a3a33833 [diff]
VOL-569: Create kubernetes deployment configuration for each voltha service

This update adds a kubernetes deployment file for netconf.

I tested the netconf service using the CLI that comes with the netopeer container.
That CLI appears to make connections with remote netconf servers at port 830; that
port number appears to be hard-coded. The port of the netconf server, on the other
hand, defaults to 1830. The changes in file netconf/main.py enable the override of
this default by using environment variable NETCONF_PORT. The kubernetes deployment
file for netconf sets the port to 830.

Change-Id: I19f90d6e14f59c855b84aa76bbc41586f3bace37
2 files changed
tree: a4b31591027a450ad486065c20b1599e7de0946e
  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. k8s/
  31. kafka/
  32. netconf/
  33. netopeer/
  34. nginx_config/
  35. obsolete/
  36. ofagent/
  37. pki/
  38. ponsim/
  39. portainer/
  40. reg_config/
  41. requirements.txt
  42. scripts/
  43. settings.gradle
  44. settings.vagrant.nightly.yaml
  45. settings.vagrant.yaml
  46. setup.mk
  47. setup.py
  48. shovel/
  49. tests/
  50. tmp_integration.md
  51. unum/
  52. vagrant-base/
  53. 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.