USER STORIES

• As a developer, I want to split traffic generated by my applications into isolated VLANs
• As a cluster operator, I want to split traffic generated by users into isolated VLANs

In order to support both user stories, we have to support QinQ.

REQUIREMENTS - this will include

• Define new QinQ API on U/S Linux bridge CNI, once it is agreed upon, we can implement it
• In case QinQ (vlan-filtering) is not supported on selected OVS bridge instance, return an explicit error message asking admin to enable it
• Document use-case and usage of this new attribute on U/S CNI repo
• Document this new feature on D/S docs
• Write test plan for this
• Implement test automation on cnv-tests OR kubevirt tier1

NON REQUIREMENTS - this delivery wouldn't include

• Support configuration of qinq/vlan-filtering on kubernetes-nmstate to provide an easy way for users to control it

GROOMING

• Add stories and sort their priority

REFERENCES

https://events.static.linuxfound.org/sites/events/files/slides/LinuxConJapan2015_makita_0_0.pdf

NOTES

OWNERS

Product Management: TBD
Delivery Owner: Cf. assignee
Quality Engineering: Cf. QA contact

DONE CHECKLIST

• DEV - Upstream code and tests merged: <link to meaningful PR or GitHub Issue>
• DEV - Upstream roadmap issue: <link to GitHub Issue>
• DEV - Upstream documentation merged: <link to meaningful PR or GitHub Issue>
• DEV - Downstream build attached to advisory: <link to errata>
• 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>