-
Type: Sub-task
-
Status: Resolved (View Workflow)
-
Priority: Medium
-
Resolution: Done
-
Affects Version/s: None
-
Fix Version/s: None
-
Component/s: Deprecated - VOLTHA, ofagent-py
-
Labels:None
-
Story Points:8
Both the Upstream and Downstream Bandwidth Profiles can be 'named' and Referenced from a Subscriber Record in the SADIS DB on ONOS.
When the vOLT Appplication uses a Subscriber Record for OpenFlow message generation to VOLTHA the vOLT Application Must read the Bandwidth Profile name and be able to retrieve the Profile from a Database of Bandwidth Profiles. The Named Profile is converted to a Meter and Meter Band(s) and configured on the VOLTHA Instance, and the Flows will reference the Meter.
Note the code should be written to follow the SADIS DB model where it is designed to reference an external database but the DB records can be cached locally.
The Upstream Bandwidth Profile will consist of the following optional components:
EIR (Bits/Sec)
EBS (Bytes)
CIR (Bits/Sec)
CBS (Bits/Sec)
AIR (Bits/Sec)
The Downstream Bandwidth Profile will consist of the following optional components:
EIR (Bits/Sec)
EBS (Bytes)
CIR (Bits/Sec)
CBS (Bits/Sec)
Each bandwidth component will be interpreted as defined in the Technology Profile Whitepaper ([^vOLTHA_Access_Tech_AugmentationV0.6.pdf]
)
- blocks
-
VOL-732 Add Support for Technology Profile reference using a Flow Table ID, and Upstream/Downstream Bandwidth Profile definitions to a Subscriber Record at the ONOS Level.
- Resolved
- is blocked by
-
VOL-542 oltApp: Use Sadis data (if available) for OLT configuration data instead of AccessDevice Configuration
- Resolved