commit | 197acc100ab4eab2354ac46700ece874574b3000 | [log] [tgz] |
---|---|---|
author | Girish Gowdra <girish@opennetworking.org> | Mon Aug 16 10:59:45 2021 -0700 |
committer | Girish Gowdra <girish@opennetworking.org> | Mon Aug 16 10:59:45 2021 -0700 |
tree | 51822c4e9f0a522b845a209e6e621d058cbe1097 | |
parent | 199570a1aef07056412e385576fd26db0f38d67e [diff] |
VOL-4251: Delete device immediately after (without any delay) volt-remove-subscriber access leaves stale resources on the OLT device The delete device cleans up everything for the device including the TpInstance even before volt-remove-subscriber-access has completed the processing. The volt-remove-subscriber cleans up scheduler and queues at the end of removing all the flows. But it needs the tp-instance reference to clean up the schedulers and queues, but it has already been deleted. So, it aborts the scheduler/queue cleanup on the OLT and this causes issues when configuring the scheduler again on the OLT during a fresh setup as there are some stale entries on the ONU. The fix here is to force cleanup the resources on the OLT when the ONU device is being deleted on the OLT. Change-Id: I54cd3ef0d5bd41cd901f3bb8917927336b84ea27
The OpenOLT adapter connects the VOLTHA core to an OLT device running the OpenOLT agent.
make
targetsThe 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.
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 manualgit
intervention to put the original files back.