-
Feature Request
-
Resolution: Unresolved
-
Undefined
-
None
-
None
-
None
-
None
-
Product / Portfolio Work
-
None
-
False
-
-
None
-
None
-
None
-
-
None
-
None
-
None
-
None
-
None
Goal
Allow users to utilize an external DHCP system to provide IPs for UDN and CUDN.
User Story
As a network administrator, I want to connect a user-defined network (UDN or CUDN; both primary and secondary) to our corporate DHCP server so that IP address allocation for virtual machines (VMs) is automated and managed centrally, ensuring consistency with our enterprise IPAM policies and eliminating manual configuration or extra automation.
Business Justifications
- Improved Automation & Reduced Overhead: This integration eliminates the manual, error-prone process of coordinating IP reservations between the virtualization platform and the IPAM system or network team. It streamlines VM deployment, reduces time, and effort with automation.
- Centralized IPAM as a Single Source of Truth: Most enterprises rely on a central IPAM/DHCP solution (like Infoblox, BlueCat, or Microsoft DHCP) to manage and audit their entire IP space. This feature allows our platform to function as a good citizen within that ecosystem, preventing IP conflicts and ensuring all allocations are tracked in the authoritative system.
- Enhanced Security and Compliance: By enforcing the use of a central DHCP server, organizations can better apply security policies, logging, and access controls related to IP address assignment, aiding in compliance with internal and external regulations.
- relates to
-
CNV-60910 CNV: support for egress(unNATed, BGP?) and ingress for VMs on L2 UDNs without OVN-Kubernetes IPAM
-
- New
-