Gitiles
Code Review Sign In
gerrit.opencord.org / ofagent-go / a98f0dc26e8215703eb8e15091012abfd6692d04
commita98f0dc26e8215703eb8e15091012abfd6692d04[log] [tgz]
authorMatteo Scandolo <matteo.scandolo@gmail.com>Wed May 13 10:39:29 2020 -0700
committerMatteo Scandolo <matteo.scandolo@gmail.com>Wed May 13 10:39:33 2020 -0700
treee370e987722a06575ec6a48d810a13db162f5871
parent3e2b2ce8051e8802e98069413624e978840b2998 [diff]
[VOL-3090] Adding profiler to ofagent-go

Change-Id: I846091a528a54a91af933d3fd6f888fb1d96295f
5 files changed
tree: e370e987722a06575ec6a48d810a13db162f5871
  1. .gitignore
  2. .gitreview
  3. .golangci.yml
  4. LICENSE
  5. Makefile
  6. README.md
  7. VERSION
  8. cmd/
  9. docker/
  10. go.mod
  11. go.sum
  12. internal/
  13. run.sh
  14. vendor/
README.md

Ofagent-go

Ofagent-go provides an OpenFlow management interface for Voltha. It is a rewrite in Golang of the original ofagent that was written in python / twisted. The main driver behind the work was to introduce true concurrency to the agent for performance/scalability reasons.

Building

  1. Outside $GOPATH

    1. Read-only git clone https://github.com/opencord/ofagent-go.git
    2. To Contribute git clone https://gerrit.opencord.org/ofagent-go

  2. Compile go build -mod=vendor -o ./build/ofagent-go

Running

  • Normal Logging
    • ./build/ofagent-go -ofaddress=localhost openflowPort=6653 -volthaAddress=localhost -volthaPort=50057
  • Debug Logging
    • ./build/ofagent-go -debug -ofaddress=localhost openflowPort=6653 -volthaAddress=localhost -volthaPort=50057

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.