How to distinguish between egress and ingress flows-
Previously flow.packet were used to configure shape of ingress packets only
There was no clear distinction between ingress and egress packet shapes, and no way to configure latter
Going forward the distinction between ingress and egress flows will be done with flow.ingress_packet and flow.egress_packet.
flow.packet shall be deprecated.
How to track the egress and ingress flows-
Under packet header configuration for each field,
metric_groups has been replaced with metric_tags containing a list of metric_tag consisting of properties name, offset and length.
Under flow metrics request,
metric_groups has been replaced with metric_tags containing a list of filter consisting of tag name and list of corresponding values associated with that tag name
What's pending ?
Description needs to be updated properly. Need feedback from reviewers.
Backwards Compatibility
No breakage in existing tests - flow.packet is deprecated and metric_groups was never implemented.
snappi UTs needs update to replace usage of metric_groups with metric_tags and use ingress packet configuration
Fixes https://github.com/open-traffic-generator/models/issues/230
View proposed changes in documentation
What has changed (and why) ?
How to distinguish between egress and ingress flows-
flow.ingress_packet
andflow.egress_packet
.flow.packet
shall be deprecated.How to track the egress and ingress flows-
metric_groups
has been replaced withmetric_tags
containing a list ofmetric_tag
consisting of properties name, offset and length.metric_groups
has been replaced withmetric_tags
containing a list of filter consisting of tag name and list of corresponding values associated with that tag nameWhat's pending ?
Backwards Compatibility
flow.packet
is deprecated andmetric_groups
was never implemented.Examples
Before
After