XML

Word

Printable

Epic Name:
ovnk-port-mirroring
Acceptance Criteria:
Hide

Downstream test automation

Downstream documentation

Upstream documentation

(must-have) Mirror traffic flowing through a network (bridge/switch/VM-port) into a selected VM

(nice-to-have) Ability to enable this feature per-VM

(nice-to-have) Ability to mirror traffic from multiple sources into a single vNIC
Show
Downstream test automation Downstream documentation Upstream documentation (must-have) Mirror traffic flowing through a network (bridge/switch/VM-port) into a selected VM (nice-to-have) Ability to enable this feature per-VM (nice-to-have) Ability to mirror traffic from multiple sources into a single vNIC
Epic Status:
To Do
Feature Link:
CNV-51212 - Port mirroring
Parent Link:
CNV-51212Port mirroring

Goal

Allow monitoring of VM traffic.

User Stories

As a telecommunication provider,
I need to be able to monitor and record traffic flowing between applications running on my cluster,
so I can analyze the quality and use the data as an evidence in court cases.

<List of things not included in this epic, to alleviate any doubt raised during the grooming process.>

Who	What	Reference
DEV	Upstream roadmap issue (or individual upstream PRs)	<link to GitHub Issue>
DEV	Upstream documentation merged	<link to meaningful PR>
DEV	gap doc updated	<name sheet and cell>
DEV	Upgrade consideration	<link to upgrade-related test or design doc>
DEV	CEE/PX summary presentation	label epic with cee-training and add a <link to your support-facing preso>
QE	Test plans in Polarion	<link or reference to Polarion>
QE	Automated tests merged	<link or reference to automated tests>
DOC	Downstream documentation merged	<link to meaningful PR>

depends on

RFE-6117 Port mirroring in OVN Kubernetes

is cloned by

CNV-28888 OVN Kubernetes multi-homing in CNV: QoS

is related to

CNV-27147 OVN Kubernetes multi-homing in CNV: Seamless live-migration