Gitiles
Code Review Sign In
gerrit.opencord.org / voltha / 079a7760d770217636b712f03781d370434252f4
commit079a7760d770217636b712f03781d370434252f4[log] [tgz]
authorkhenaidoo <knursimu@ciena.com>Thu Oct 26 21:42:05 2017 -0400
committerkhenaidoo Nursimulu <knursimu@ciena.com>Fri Oct 27 10:41:28 2017 -0700
tree3ce5659254b22479208f4b69450451d78118d120
parent48a6235250ce3f9a6eb7174959a0c924ff828db6 [diff]
[6683] Removing unnecessary files and update gitignore

VOL-507, VOL-463: Protobuf upgrade to 3.3 and Chameleon Removal

Update the Protobuf version from 3.1 to 3.3 to alleviate
a protobuf issue when loading protobuf extensions.  The following
tests have been performed:
- Create a local Vagrant VM
- Voltha ensemble startup and check for errors/exceptions
- Manual compilations of the protos in voltha, ofagent, netconf and
chameleon directory
- Manual tests with ONOS/Voltha/Ponsim using Netconf, Curl and CLI
- Run the integration tests (known issues have Jiras already raised
against them.
- Run the make jenkins-test and make utest-with-coverage

Chameleon has been removed entirely from Voltha projects. Basic tests
have run to verify chameleon dependency has been removed.  Some
documents (like README) will need to be changed under a separate Jiras
as they are referenced in different adapters.  Some integration tests
will also need to be updated as well.

Change-Id: I2b266719a6825fb07ece3a79f7f81881ab3b9761
54 files changed
tree: 3ce5659254b22479208f4b69450451d78118d120
  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.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.