Gitiles
Code Review Sign In
gerrit.opencord.org / voltha-simolt-adapter / a14c6353ec0ca850e25a187f19ec0476592f9495
commita14c6353ec0ca850e25a187f19ec0476592f9495[log] [tgz]
authorAndrea Campanella <andrea@opennetworking.org>Wed Aug 25 14:35:28 2021 +0200
committerAndrea Campanella <andrea@opennetworking.org>Wed Aug 25 14:35:28 2021 +0200
tree9e2f2233261083bc56647fdf3cf3789839f2e5d7
parent5c68616562d22cc1fd7d9eb70d9fc91b377a7037 [diff]
[VOL-4308] Deprecating repo due to stale state

Change-Id: Idc0c11d58fe17900d809ed718cabde8450040ca7
1 file changed
tree: 9e2f2233261083bc56647fdf3cf3789839f2e5d7
  1. .gitignore
  2. .gitreview
  3. LICENSES/
  4. Makefile
  5. README.md
  6. VERSION
  7. cmd/
  8. docker/
  9. go.mod
  10. go.sum
  11. internal/
  12. vendor/
README.md

DEPRECATED

No Maintenance Intended

VOLTHA 2.3 was the last official set of releases that used the voltha-simolt-adapter repository. From 2.4 onwards the volta-openolt-adapter as the exact same functionality in simulated or physical mode, thus the repo has been deprecated. This codebase is going to be removed after the VOLTHA 2.8 release LTS support ends in December 2022.

How to Build the Golang based Simulated OLT Adapter

Working with Go Dependencies

This project uses Go Modules https://github.com/golang/go/wiki/Modules to manage dependencies. As a local best pratice this project also vendors the dependencies. If you need to update dependencies please follow the Go Modules best practices and also perform the following steps before committing a patch:

go mod tidy
go mod verify
go mod vendor

Building with a Local Copy of voltha-protos or voltha-lib-go

If you want to build/test using a local copy or voltha-protos or voltha-lib-go this can be accomplished by using the environment variables LOCAL_PROTOS and LOCAL_LIB_GO. These environment variables should be set to the filesystem path where the local source is located, e.g.

LOCAL\_PROTOS=$HOME/src/voltha-protos
LOCAL\_LIB\_GO=$HOME/src/voltha-lib-go

When these environment variables are set the vendored versions of these packages will be removed from the vendor directory and replaced by coping the files from the specified locations to the vendor directory. NOTE: this means that the files in the vendor directory are no longer what is in the git repository and it will take manual git intervention to put the original files back.