OCP/Telco Definition of Done
Epic Template descriptions and documentation.

Epic Goal

As an OpenShift on OpenStack administrator, I want to specify static IP assignments to my VMs.

As an OpenShift on OpenStack administrator, I want to completely avoid using a DHCP server for the VMs of my OpenShift cluster.

Why is this important?

Customers want the convenience of IPI deployments for OpenStack without having to use DHCP. As in bare metal, where METAL-1 added this capability, some of the reasons are the security implications of DHCP (customers report that for example depending on configuration they allow any device to get in the network). At the same time IPI deployments only require to our OpenShift installation software, while with UPI they would need automation software that in secure environments they would have to certify along with OpenShift.

Also, when using an external load-balancer, it's very useful to know the IPs in advance so the load-balancer can be populated with the right IPs for the backends.

Acceptance Criteria

• I can specify static IPs for node VMs at install time with IPI

Previous Work

Bare metal related work:

• METAL-1
• https://github.com/openshift/enhancements/blob/master/enhancements/network/baremetal-ipi-network-configuration.md

VSphere related work: https://issues.redhat.com/browse/SPLAT-827

Done Checklist

• CI - CI is running, tests are automated and merged.
• Release Enablement <link to Feature Enablement Presentation>
• DEV - Upstream code and tests merged: <link to meaningful PR or 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>