Gitiles
Code Review Sign In
gerrit.opencord.org / voltha-openolt-adapter / ceea2e043ee8f4b114234056418c6599005f4297
commitceea2e043ee8f4b114234056418c6599005f4297[log] [tgz]
authorMatt Jeanneret <mj3580@att.com>Fri Mar 27 14:19:57 2020 -0400
committerMatt Jeanneret <mj3580@att.com>Mon Mar 30 12:23:45 2020 -0400
tree695807491d25152cdabacdb8d319cf6fa242d9fe
parent868131c6edc9eda73a31bf218ea63c3d93075592 [diff]
VOL-2841: Remove old backward compatible omci message checking code

New onu and openomci library now sends a proper byte array for the
message, so no need to check.

Note, openolt agent still expects the hex string.  Once that
is fixed and both adapter and agent released then the final TODO
can go away.

Also make omci message tracing through openolt a bit easier by
adding the omci transaction id

Change-Id: I79d3519365d3f03d668e4fdc2e5ae9e0d323a96e
1 file changed
tree: 695807491d25152cdabacdb8d319cf6fa242d9fe
  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

How to Build the Golang based OpenOLT Adapter

Working with Go Dependencies

This project uses Go Modules https://github.com/golang/go/wiki/Modules to manage dependencies. As a local best pratice this project also vendors the dependencies. If you need to update dependencies please follow the Go Modules best practices and also perform the following steps before committing a patch:

go mod tidy
go mod verify
go mod vendor

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

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

LOCAL\_PROTOS=$HOME/src/voltha-protos
LOCAL\_LIB\_GO=$HOME/src/voltha-lib-go

When these environment variables are set the vendored versions of these packages will be removed from the vendor directory and replaced by coping the files from the specified locations to the vendor directory. NOTE: this means that the files in the vendor directory are no longer what is in the git repository and it will take manual git intervention to put the original files back.