Gitiles
Code Review Sign In
gerrit.opencord.org / voltha / 26a8c01f0cd1e5599d6243eabd6864a2482d6a17
commit26a8c01f0cd1e5599d6243eabd6864a2482d6a17[log] [tgz]
authorkhenaidoo <knursimu@ciena.com>Fri Jul 07 18:25:47 2017 -0400
committerkhenaidoo Nursimulu <knursimu@ciena.com>Mon Jul 10 08:43:18 2017 -0700
tree1eca714a3f8bb3b183e7f8e6ba6722490ead5e66
parent551646719dadee6eaee852194c586f6e07d8c2e6 [diff]
This update add two arguments to voltha when it gets started:
   1) inter-core-subnet: the subnet to connect to for inter core communication
   2) pon-subnet: the subnet to connect to for PON communication

This requires that the voltha_net is created with a specified subnet and that
subnet is specified in the docker compose file, e.g.:

docker network create --driver overlay --subnet 10.0.1.0/24 voltha_net

And in the compose.yml file add the following options:

      - --inter-core-subnet=10.0.1.0/24
      - --pon-subnet=10.0.1.0/24

This update guarantees that the voltha instance is connected to the correct
network.

Change-Id: I5d29ab54282c4ba9aff5ba165fdb37352cfaa0fd
4 files changed
tree: 1eca714a3f8bb3b183e7f8e6ba6722490ead5e66
  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. experiments/
  23. gradle.properties
  24. gradle/
  25. gradlew
  26. gradlew.bat
  27. install/
  28. kafka/
  29. netconf/
  30. netopeer/
  31. nginx_config/
  32. obsolete/
  33. ofagent/
  34. pki/
  35. podder/
  36. ponsim/
  37. portainer/
  38. reg_config/
  39. requirements.txt
  40. scripts/
  41. settings.gradle
  42. settings.vagrant.yaml
  43. setup.mk
  44. setup.py
  45. shovel/
  46. tests/
  47. tmp_integration.md
  48. vagrant-base/
  49. 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.