| commit | af66b0fd2cfe870494d19046995601db963537c1 | [log] [tgz] |
|---|---|---|
| author | Girish Gowdra <girish@opennetworking.org> | Wed Sep 09 15:50:39 2020 -0700 |
| committer | Matteo Scandolo <matteo.scandolo@gmail.com> | Mon Sep 14 14:33:17 2020 -0700 |
| tree | 1bcbfc93e33062721cbe60f08cdf69a0312c40a9 | |
| parent | 7fcebe2f74d9e3ec316edc122bbdf61ac7dcca87 [diff] |
Cherry-picking VOL-3419 and releasing 2.5.6 VOL-3419: OpenOLT adapter at scale constantly takes more that 10 seconds to react to flows The patch addresses the following - Create OpenOltFlowMgr per PON port (instead of one instance for the whole OLT device earlier) - Create a separate OpenOltGroupMgr - currently one instance for the whole OLT device - Remove redundant global lock around getting ONU-ID in DeviceHandler module as there exists a separate per-pon-port lock in ResourceManager module which suffices the required synchronization - Remove redundant locks in OpenOltFlowMgr module to serialize FlowDelete before FlowAdd - Rename divideAndAddFlow to processAddFlow. "divideAndAddFlow" was used in 1.x voltha days and had a different meaning and the name seems to have been blindly ported to 2.x adapter and does not make sense anymore Change-Id: I99827963cf242f1db0c27943c97bd05b749ae129
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-goIf 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
vendordirectory are no longer what is in the most recent commit, and it will take manualgitintervention to put the original files back.