-
Epic
-
Resolution: Unresolved
-
Critical
-
None
-
routed-ingress-udn
-
Incidents & Support
-
77
-
- Release note announcing this support
- Downstream test automation verifying that this SDN feature integrates well with VMs (including live migration)
-
Yellow
-
In Progress
-
18% To Do, 9% In Progress, 73% Done
-
Goal
Allow access to primary UDN endpoints through mere routing, with routes advertised using BGP.
This is a CNV tracker for CORENET-4923, implementing RFE-5459. This feature will require re-addressing of VMs on their import to OCP, see OCPSTRAT-1963 if you need to preserve IPs.
Non-Requirements
- <List of things not included in this epic, to alleviate any doubt raised during the grooming process.>
Notes
- <Any additional details or decisions made/needed>
- clones
-
-
- New
-
- depends on
-
-
- Closed
-
-
-
- Closed
-
- is duplicated by
-
-
- Closed
-
- relates to
-
OCPSTRAT-1343 Support of routed ingress for L2 UDN: VM Workloads
-
- In Progress
-
- links to
1.
|
upstream roadmap issue |
|
Closed | 
|
Unassigned |
2.
|
upstream design |
|
Closed |
|
Unassigned |
3.
|
upstream documentation |
|
Closed |
|
Unassigned |
4.
|
upgrade consideration |
|
Closed |
|
Unassigned |
5.
|
CEE/PX summary presentation |
|
Closed |
|
Unassigned |
6.
|
test plans in polarion |
|
Closed |
|
Unassigned |
7.
|
automated tests |
|
New |
|
Unassigned |
8.
|
downstream documentation merged |
|
New |
|
Unassigned |
