[VOL-2055] Use Tech Profile ID to differentiate downstream traffic scheduler
- CreateQueue / RemoveQueue / CreateSched / RemoveSched / FlowAdd updated to include
tech_profile_id to select downstream scheduler.
- A DS scheduler is now identified by the tuple (pon, onu, uni, dir, tech_profile_id)
- voltha_protos v3.3.5 is now referred.
- Unit tests updated.
- VERSION updated.
Change-Id: I399bbb03aa33b61a02da10af0a40d354d44bd5cf
diff --git a/agent/common/core.h b/agent/common/core.h
index 31e10ed..33a9066 100644
--- a/agent/common/core.h
+++ b/agent/common/core.h
@@ -219,7 +219,7 @@
int32_t alloc_id, int32_t network_intf_id,
int32_t gemport_id, const ::openolt::Classifier& classifier,
const ::openolt::Action& action, int32_t priority_value,
- uint64_t cookie, int32_t group_id);
+ uint64_t cookie, int32_t group_id, uint32_t tech_profile_id);
Status FlowRemove_(uint32_t flow_id, const std::string flow_type);
Status Disable_();
Status Reenable_();