|author||Joey Armstrong <firstname.lastname@example.org>||Sun Dec 25 21:45:27 2022 -0500|
|committer||Joey Armstrong <email@example.com>||Thu Dec 29 06:30:40 2022 -0500|
VOL-4917 - voltha-go build and test problems. Makefile makefiles/ ========== o Update copyright notice. o Added a few common makefile libraries. o Added todo.mk to document a few future-fix items. o Added versions.mk used to display build tools and versions. o Added comments and banners to delimit logic and identify log output. o Fixed coverage target, git test -coverprofile requires a disk file. o Strange: 'go mod vendor' will remove vendor/ but the directory is under revision control. [TODO] Delete or checkout from a central repo. o Split long lines with line continuation at shell pipe. o Replace inlined rm -rf calls with make builtin $(RM) -r o Refacor test log names into macros to shorten logic line length. docker/Dockerfile.rw_core ------------------------- o Update copyright notice. o Inline --no-cache with apk calls, networking problems surfaced while running "make build/test" while disconnected from the VPN. o Copy stub go-test-coverage.out file to the docker image, go test -coverprofile was failing w/o a file on disk. o Testing reported a "could not create cpu profile" error. Create a pull request for feedback to see if this is a lingering coverage problem or my laptop cpu is unknown and contributing. Change-Id: I84724682cfd9dbcd08990cef382338f005261184
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:
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.
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.
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.