[VOL-4674] Connecting directly to the BBSim POD instead than to the service as that might round-robin to the old instance before it's gone

Change-Id: I79558af733ff29f0c7ee204015f1f64a7895a51c
5 files changed
tree: 5c8f406f8cd6b95a5d363c205162295d409391b2
  1. .gitignore
  2. .gitreview
  3. Makefile
  4. README.md
  5. VERSION
  6. build/
  7. cmd/
  8. deployments/
  9. go.mod
  10. go.sum
  11. internal/
  12. vendor/
README.md

BBSim Sadis Server

This project is designed to aggregate Sadis entries from multiple BBSim instances running on the same kubernetes cluster.

This tool assumes that:

  • The sadis service is exposed on the default port 50074
  • BBSim(s) are deployed with the default label app=bbsim

This component is part of the the VOLTHA project, more informations at: https://docs.voltha.org

Deploy

helm repo add onf https://charts.opencord.org
helm install bbsim-sadis-server onf/bbsim-sadis-server

Configure ONOS to use bbsim-sadis-server

Assuming that bbsim-sadis-server was installed in the default namespace, you can use this configuration to point ONOS to it:

{
  "sadis" : {
    "integration" : {
      "url" : "http://bbsim-sadis-server.default.svc:58080/subscribers/%s",
      "cache" : {
        "enabled" : true,
        "maxsize" : 50,
        "ttl" : "PT1m"
      }
    }
  },
  "bandwidthprofile" : {
    "integration" : {
      "url" : "http://bbsim-sadis-server.default.svc:58080/profiles/%s",
      "cache" : {
        "enabled" : true,
        "maxsize" : 50,
        "ttl" : "PT1m"
      }
    }
  }
}

For more inforation about the sadis application you can refer to: https://github.com/opencord/sadis