-
Epic
-
Resolution: Done
-
Major
-
None
-
ui-ovnk2-ipam
-
- Subnet can be specified in the NAD dialog
- IP from the subnet is assigned to each VM requesting it
- The IP is persistent between VM restarts
-
To Do
-
67% To Do, 33% In Progress, 0% Done
-
doc-ready, po-ready
Goal
Allow UI users to specify a subnet of their OVN Kubernetes localnet and L2 overlay network attachment definitions.
User Stories
- As an admin,
I want to specify a subnet when defining a secondary OVN Kubernetes network,
so VMs connected to that get assigned with an IP without developers needing to manage them.
Non-Requirements
- <List of things not included in this epic, to alleviate any doubt raised during the grooming process.>
Notes
- The API is still being designed.
- depends on
-
CNV-24260 [TP] OVN Kubernetes secondary L2 overlay: IPAM
- Backlog
- links to
1.
|
upstream roadmap issue | Closed | Unassigned | ||
2.
|
upstream documentation | Closed | Unassigned | ||
3.
|
upgrade consideration | Closed | Unassigned | ||
4.
|
CEE/PX summary presentation | Closed | Unassigned | ||
5.
|
test plans in polarion | Closed | Unassigned | ||
6.
|
automated tests | Closed | Unassigned | ||
7.
|
downstream documentation merged | Closed | Unassigned |