-
Type: Bug
-
Status: Resolved (View Workflow)
-
Priority: Medium
-
Resolution: Done
-
Affects Version/s: None
-
Fix Version/s: SEBA-Next
-
Component/s: bbsim
-
Labels:
-
Story Points:3
-
Epic Link:
The new Sadis app:
org.opencord.sadis 3.1.1.SNAPSHOT
use a different config format:
{ "id": "BBSM00000001-1", "nasPortId": "BBSM00000001-1", "circuitId": "BBSM00000001-1", "remoteId": "BBSM00000001-1", "uniTagList": [{ "ponCTag": 900, "ponSTag": 900, "technologyProfileId": 64, "downstreamBandwidthProfile": "Default", "upstreamBandwidthProfile": "Default", "isDhcpRequired": true }
The BBSim sadis server needs to support this configuration too.
ideally we should prefix the endpoints with `v1` for the existing ones and `v2` for the new ones: https://github.com/opencord/bbsim/blob/958d81cf3c05fd53c2e81bb226462cb1ea8b9040/internal/bbsim/responders/sadis/sadis.go#L295-L298
# | Subject | Branch | Project | Status | CR | V |
---|---|---|---|---|---|---|
17689,4 | SEBA-938 New sadis config in bbsim server bump version 18-dev add missing UniTagMatch add missing " Change-Id: I9507b45fdb93f3a2056f55c5ef862bacf50bfe24 | master | bbsim | Status: MERGED | +2 | +1 |