Gitiles
Code Review Sign In
gerrit.opencord.org / voltha-openolt-adapter / 852ad91dcd37d99f483429aae147a8e537963c76
commit852ad91dcd37d99f483429aae147a8e537963c76[log] [tgz]
authorGirish Gowdra <girish@opennetworking.org>Tue May 04 00:05:50 2021 -0700
committerGirish Gowdra <girish@opennetworking.org>Tue May 04 00:05:50 2021 -0700
tree867ee13a63ee694fe503bc86bc67b50e173e1bff
parent011744287fa8f50c30a1c5d69fb99a8329149e06 [diff]
VOL-4053: Fix Reenable of OLT following disable OLT and adapter restart.

- Allow event DeviceDownInd in state deviceStateConnected.
  When the device is disabled it is in state deviceStateDown. When the
  adapter is restarted in this state, the adapter comes back from restart
  and establishes connection to OLT device and moves to deviceStateConnected.
  However given the device was disabled prior to adapter going for
  restart, it triggers a disable again for the device. The OLT
  is already disabled, but acknowledges the disable command with
  an down indication which translates to DeviceDownInd event
  in the device FSM at adapter. Now this event should be allowed
  in the FSM.

Change-Id: I0cbe81f6d393ab6ceca5fa9f847fa4a4acb5f198
4 files changed
tree: 867ee13a63ee694fe503bc86bc67b50e173e1bff
  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.