Gitiles
Code Review Sign In
gerrit.opencord.org / voltha-openonu-adapter-go / 01e726ef9aadeed7ca90ea7ddbabdd64e74cce3c
commit01e726ef9aadeed7ca90ea7ddbabdd64e74cce3c[log] [tgz]
authormpagenko <michael.pagenkopf@adtran.com>Fri Oct 23 09:45:29 2020 +0000
committermpagenko <michael.pagenkopf@adtran.com>Tue Oct 27 08:58:51 2020 +0000
tree57b4a5ed3c5fbeb215964062b6f29bb612a2dc69
parentbef4e5444bbbe566f6d1a9c2988692f225469675 [diff]
[VOL-3437] Implement (incremental) flow config removal with according OMCI VLAN configuration and some further code corrections and smaller functional extensions -> version 0.1.13-dev135, now merged with [VOL-3586] und included correction for missing Techprofile configuration at disable/enable procedure

Signed-off-by: mpagenko <michael.pagenkopf@adtran.com>
Change-Id: I438a72867d5da83c505a30169d7d5aba8f8ee8c2
9 files changed
tree: 57b4a5ed3c5fbeb215964062b6f29bb612a2dc69
  1. .gitignore
  2. .gitreview
  3. .golangci.yml
  4. Makefile
  5. README.md
  6. VERSION
  7. cmd/
  8. docker/
  9. go.mod
  10. go.sum
  11. internal/
  12. pkg/
  13. templates/
  14. vendor/
README.md

How to Build the Golang based OpenONU Adapter

NOTE that this is a work in progress. A functional version is yet to come.

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.