-
Type:
Task
-
Status: Resolved (View Workflow)
-
Priority:
Medium
-
Resolution: Done
-
Affects Version/s: None
-
Fix Version/s: Next for SEBA 2.0
-
Labels:None
-
Story Points:8
-
Epic Link:
Currently, R-CORD synchronizer responds to the subscriber requests - when SADIS-Server wants to learn the subscriber info, it sends a request to this synchronizer (I guess) - So, there will be a synchronizer that responds to the SADIS-Server when it wants to learn bandwidth-profile. (it is for tech profile integration) – Or, a new synchronizer can be created such as bandwidthprofile-synchronizer.
| # | Subject | Branch | Project | Status | CR | V |
|---|---|---|---|---|---|---|
| 13330,5 | [SEBA-351] Adding bandwidth profiles to the Subscriber and setting up a default one | master | rcord | Status: MERGED | +2 | +1 |
| 13332,7 | [SEBA-351][SEBA-350] Creating a default BandwithPorfile while bringing up the seba-services profile, using the newer sadis-server | master | helm-charts | Status: ABANDONED | 0 | -1 |