This build includes new features.

Release Features(s)

A new property egress_packet inside flow has been introduced to configure expected packet shape as it is received on the test port.
go eth := flow.EgressPacket().Add().Ethernet() ipv4 := flow.EgressPacket().Add().Ipv4()
A new property metric_tags has been introduced for fields inside headers configured in egress_packet to enable tracking metrics for each applicable value corresponding to a portion of or all bits inside the field.
```
  ipv4Tag := ipv4.Dst().MetricTags().Add()
  ipv4Tag.SetName("flow_ipv4_dst")
  ipv4Tag.SetOffset(24)
  ipv4Tag.SetLength(8)
```
- As of this release, enabling metric_tags is only supported on ethernet.src/dst, ipv4.src/dst, ipv4.tos. Support for more fields shall be added in upcoming releases.
- Limitations:
  - The total number of tracking bits available on an ixia-c Rx port is 12 bits. Out of these some of the bits are needed for tracking flows, example 2 flows need 1 bit, 4 flows need 2 bits, 8 flows need 3 bits etc. The sum of metric_tag.length for each field inside each header configured in egress_packet cannot exceed the remaining bits available on the Rx port.
  - The total number of tracking fields that can be configured across a set of flows which have the same Rx port, is two.
A new property is introduced in get_metrics.flow to fetch tagged metrics.

User can set get_metrics.flow.tagged_metrics.include=false not to include tagged_metrics in the flow_metrics response.
Specific tagged_metrics can be fetched by setting get_metrics.flow.tagged_metrics.filters[i].name.

Supported value for flows[i].metrics.latency.mode is cut_through.
The metric loss in flow metrics is currently not supported.
When flow transmit is started, transmission will be restarted on any existing flows already transmitting packets.
#118

Provide feedback