commit | 06e564fa66deefc854c2decfa44c00291a06f6de | [log] [tgz] |
---|---|---|
author | Matteo Scandolo <matteo.scandolo@gmail.com> | Tue Mar 22 15:45:26 2022 -0700 |
committer | Matteo Scandolo <matteo.scandolo@gmail.com> | Wed Mar 23 09:46:01 2022 -0700 |
tree | 5c8f406f8cd6b95a5d363c205162295d409391b2 | |
parent | 68c39e689da41af8346c0c2d39b1719b47679efa [diff] |
[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
This project is designed to aggregate Sadis entries from multiple BBSim instances running on the same kubernetes cluster.
This tool assumes that:
50074
app=bbsim
This component is part of the the VOLTHA project, more informations at: https://docs.voltha.org
helm repo add onf https://charts.opencord.org helm install bbsim-sadis-server onf/bbsim-sadis-server
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