| commit | 2ba0e0b257821259a6a3dba61478e736abfe68ff | [log] [tgz] |
|---|---|---|
| author | Takahiro Suzuki <takahiro@opennetworking.org> | Fri Jun 05 14:23:03 2020 -0700 |
| committer | Takahiro Suzuki <takahiro@opennetworking.org> | Wed Jun 24 20:53:55 2020 -0700 |
| tree | 386799f6d73e3ced368d92867e70fea2c86c88ae | |
| parent | 9218624c300a41c17af9fe31d4d00509edeb958e [diff] |
[VOL-1348] EPON tech profile support Change-Id: I5dfbc17fe6787f255d22d0b5d640bc636bfb172d
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.