Gitiles
Code Review Sign In
gerrit.opencord.org / voltha / 33d6a8e4e1be63022a1730c4949adcc041e456b3
commit33d6a8e4e1be63022a1730c4949adcc041e456b3[log] [tgz]
authorlcui <lcui@cigtech.com>Tue Aug 28 12:51:38 2018 -0700
committerLin Cui <lcui@cigtech.com>Mon Nov 26 04:36:29 2018 +0000
tree1c6d2e31c9350adf4c8e7e17d62cd6df1a4a01aa
parent8d811fdb25d643344f7a97175055fb2dc4cad69f [diff]
VOL-184 ONU software upgrade based on OpenOMCI framework

    ** Implement OMCI download software procedure with two state machine:
    1. Software OMCI downloading state machine
    2. Activate software image state machine, which includes OMCI software download and OMCI software activation
    3. Add OMCI message/frames for Start/End/DownloadSection/ActiveImage/CommitImage

    ** Change OMCI_CC.send to support:
    1. Send OMCI messages without waiting for response (Download Section)
    2. Add timeout handler to support retry max 3 times on timeout
    3. Add a clock(reactor) in contructor to support automation test with robotframwork
       RobotFramework use global reactor to loop run all test cases.
       It will conflict with the reactor in VOLTHA classes.
       The solution is to assign a reactor when create VOLTHA classes so that they will share
       the same reactor and make RobotFramework works.
       If reactor is not assigned VOLTHA classes will use default global reactor.
       So it is back-compitable and won't have impact on other code

    ** OMCI download/activate task are exclusive True to avoid blocking by OMCI PM/Alarm STM/tasks

    ** Log is detailed for debug at current stage; and will improve after functions are fully verified

    ** Add test cases based on RobotFramework
    1. Test cases for Software download
    2. Mock Adapter/Mock ONU are used in the test cases

    ** Implement relative commands:
         img_dnld_request
         img_dnld_status
         img_dnld_cancel
         img_activate

Change-Id: I1796fd694f312378facbcd441bfc15ee7c093d91
23 files changed
tree: 1c6d2e31c9350adf4c8e7e17d62cd6df1a4a01aa
  1. .dockerignore
  2. .gitignore
  3. .gitreview
  4. BUILD.md
  5. BuildingVolthaUsingVagrantOnKVM.md
  6. DOCKER_BUILD.md
  7. GettingStartedLinux.md
  8. Jenkinsfile
  9. LICENSE.txt
  10. Makefile
  11. README.md
  12. TODO.md
  13. Vagrantfile
  14. alarm-generator/
  15. ansible/
  16. cli/
  17. common/
  18. compose/
  19. consul_config/
  20. dashd/
  21. docker/
  22. docs/
  23. env.sh
  24. envoy/
  25. experiments/
  26. fluentd_config/
  27. install/
  28. k8s/
  29. kafka/
  30. netconf/
  31. netopeer/
  32. nginx_config/
  33. obsolete/
  34. ofagent/
  35. pki/
  36. ponsim/
  37. portainer/
  38. reg_config/
  39. requirements.txt
  40. scripts/
  41. settings.vagrant.nightly-docker.yaml
  42. settings.vagrant.nightly.yaml
  43. settings.vagrant.yaml
  44. setup.mk
  45. setup.py
  46. shovel/
  47. tests/
  48. tmp_integration.md
  49. unum/
  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.