Gitiles
Code Review Sign In
gerrit.lfbroadband.org / voltha-openolt-adapter / b4c33303a25e8e14088538f08c3420678e531148
commitb4c33303a25e8e14088538f08c3420678e531148[log] [tgz]
authorGirish Gowdra <girish@opennetworking.org>Fri Mar 18 15:07:38 2022 -0700
committerGirish Gowdra <girish@opennetworking.org>Tue Mar 22 12:04:43 2022 -0700
tree7a0e0d1098ff2ff233897003b372e8f8099570eb
parent6c295c6f53c05edf132465b0590cc9c15f6bae14 [diff]
VOL-4670: Fix for flowIDsForGem cache in openolt adapter
          resource manager is not updated on adapter restarts

- The cache flowIDsForGem is empty on adapter restarts.
  So use GetFlowIDsForGem API to update the cache and use it.

VOL-4672: Stale etcd data in openolt adapter after olt device delete

- If OLT device is getting deleted ignore ChildDeviceLost processing.
  The ChildDeviceLost could create entries already cleaned up by
  OLT device delete processing under some race conditions.

Change-Id: I535d9c968acb6bcee897fea49c78362230a52ac9
4 files changed
tree: 7a0e0d1098ff2ff233897003b372e8f8099570eb
  1. .gitignore
  2. .gitreview
  3. .golangci.yml
  4. CODE_OF_CONDUCT.md
  5. Makefile
  6. README.md
  7. VERSION
  8. cmd/
  9. compose/
  10. docker/
  11. go.mod
  12. go.sum
  13. internal/
  14. pkg/
  15. vendor/
README.md

OpenOLT adapter

The OpenOLT adapter connects the VOLTHA core to an OLT device running the OpenOLT agent.

Development make targets

The Makefile contains many commands that are useful in development:

build                     : Alias for 'docker build'
clean                     : Removes any local filesystem artifacts generated by a build
distclean                 : Removes any local filesystem artifacts generated by a build or test run
docker-build-profile      : Build openolt adapter docker image with profiling enabled
docker-build              : Build openolt adapter docker image
docker-kind-load          : Load docker images into a KinD cluster
docker-push               : Push the docker images to an external repository
help                      : Print help for each Makefile target
lint-dockerfile           : Perform static analysis on Dockerfile
lint-mod                  : Verify the Go dependencies
lint                      : Run all lint targets
local-lib-go              : Copies a local version of the voltha-lib-go dependency into the vendor directory
local-protos              : Copies a local version of the voltha-protos dependency into the vendor directory
mod-update                : Update go mod files
sca                       : Runs static code analysis with the golangci-lint tool
test                      : Run unit tests

Some highlights:

  • It's recommended that you run the lint, sca, and test targets before submitting code changes.

  • The docker-* targets for building and pushing Docker images depend on the variables DOCKER_REGISTRY, DOCKER_REPOSITORY, and DOCKER_TAG as described in the CORD documentation

  • If you make changes the dependencies in the go.mod file, you will need to run make mod-update to update the go.sum and vendor directory.

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

If you want to build/test using a local copy of the voltha-protos or voltha-lib-go libraries 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.:

export LOCAL_PROTOS=/path/to/voltha-protos
export LOCAL_LIB_GO=/path/to/voltha-lib-go

Then run make local-protos and/or make local-lib-go as is appropriate to copy them into the vendor directory.

NOTE: That the files in the vendor directory are no longer what is in the most recent commit, and it will take manual git intervention to put the original files back.