-
Epic
-
Resolution: Unresolved
-
Undefined
-
None
-
None
-
None
Goal
Allow seamless migration of applications using double-tagging to CNV.
User Stories
- As a cluster admin,
I want CNV to support double-tagging,
so I can isolate my tenants using VLAN, while they can isolate their applications using VLANs,
and at the same time stay connected to the physical network. - As a customer migrating my workloads to CNV,
I want traditional double-tagging support,
I cannot convert all my applications at once to use micro-segmentation or isolated overlay networks.
Non-Requirements
- <...>
Notes
- This functionality should be already present in OVN: https://github.com/ovn-org/ovn/commit/50f4ea011622a63c5ac0eec200c4176b1afe6fb6
Done Checklist
| Who | What | Reference |
|---|---|---|
| DEV | Upstream roadmap issue | <link to GitHub Issue> |
| DEV | Upstream code and tests merged | <link to meaningful PR> |
| 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> |
