Gitiles
Code Review Sign In
gerrit.opencord.org / voltha-go / c9eb17134f760938dc7dd59f4091458b9f763a30
commitc9eb17134f760938dc7dd59f4091458b9f763a30[log] [tgz]
authorJan Klare <jan.klare@bisdn.de>Wed Nov 01 12:31:22 2023 +0100
committerJan Klare <jan.klare@bisdn.de>Wed Nov 01 13:56:32 2023 +0100
tree37415b0c7fa4a7897485901370e177cd76849b24
parent62d753f5b58a6572b6ee6ef3a23a3dca44945432 [diff]
repair "docker push" in docker-publish make target

* the commit 393daca85 broke the docker-publish make target by removing
  the indentation for the "docker push ..." command
* readd the correct indentation to allow "docker publish" make target to
  upload new image tags
* this change will only fix the behaviour for future releases, all tags
  added between v3.4.0 (last published tag before commit 393daca85) and
  now have not been published
* increase VERSION to v3.4.7 to trigger automatic tagging and jenkins
  docker-build/publish jobs to upload newest release

Signed-off-by: Jan Klare <jan.klare@bisdn.de>
Change-Id: I42e3c9e0ccd1305488c53d158ed99ece1ec1f769
Signed-off-by: Jan Klare <jan.klare@bisdn.de>
2 files changed
tree: 37415b0c7fa4a7897485901370e177cd76849b24
  1. .gitignore
  2. .gitreview
  3. .golangci.yml
  4. BUILD.md
  5. CODE_OF_CONDUCT.md
  6. Makefile
  7. README.md
  8. VERSION
  9. compose/
  10. config.mk
  11. db/
  12. docker/
  13. go.mod
  14. go.sum
  15. makefiles/
  16. quickstart.md
  17. rw_core/
  18. vendor/
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?

You can start by reading the published documentation.
Another great way is to 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. Please check out the contributing page on the documentation.