Gitiles
Code Review Sign In
gerrit.opencord.org / voltha-openolt-adapter / 945e401f2e009f0196c517e51cffc7502287fcc0
commit945e401f2e009f0196c517e51cffc7502287fcc0[log] [tgz]
authorMatteo Scandolo <matteo.scandolo@gmail.com>Thu Dec 12 14:16:11 2019 -0800
committerMatteo Scandolo <matteo.scandolo@gmail.com>Tue Feb 11 11:25:01 2020 -0800
treeb8771d427d2e952917de5270387a8a81b05f4b6d
parent3d2a8f96b00d554236ed094c1d8f7eff2afb9c50 [diff]
[VOL-2364] handle sub-sequent onuDiscoveryIndication

If ChildDeviceDetected times out then the device never receives the
"enable" call. With this patch we are allowing the device to send a new
discovery indication to retry the process (the OpenOlt agent keeps
sending discovery until an "enable" call is received for that device)

Change-Id: I6a2f5d5e9b0a001361bdca1feb14ca22cf092138
10 files changed
tree: b8771d427d2e952917de5270387a8a81b05f4b6d
  1. .gitignore
  2. .gitreview
  3. .golangci.yml
  4. CODE_OF_CONDUCT.md
  5. Makefile
  6. README.md
  7. VERSION
  8. adaptercore/
  9. compose/
  10. config/
  11. docker/
  12. go.mod
  13. go.sum
  14. main.go
  15. main_test.go
  16. mocks/
  17. vendor/
README.md

How to Build the Golang based OpenOLT 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.