Bug 1887500

Description of problem:
The hosted engine setup requires subnet ranges with no NAT;

for example;

- 192.168.0.1 = Gateway
- 192.168.0.10 = Host
- 192.168.0.11 = Hosted Engine

This works well on local networks, but on an OVH dedicated host where you don't have internal subnets, this causes issues.

an example single server from OVH will come with;

- 55.55.55.55/32 = Gateway
- 66.66.66.66/32 = Host
- 77.77.77.73/29 = 16block of ips...

whilst it is possible to juggle the ip's around to have;

- 55.55.55.55 = Gateway
- 77.77.77.73 = Host
- 77.77.77.74 = Hosted Engine

there is nothing the user can do to change the Gateway, the gateway will always remain outside of the allocated subnet.

I've not tried it but an offline install using temporary internal ip subnets should be possible over ip-kvm, however that's alot of work.

It would be nice if the installer did not restrict / impose / validate the IP address of the gatway, so as to allow the gateway to exist outside of the environment's subnet.

Version-Release number of selected component (if applicable):


How reproducible:
follow installer, and try to use a gateway outside the subnet range for the env.

Steps to Reproduce:
1. follow installer
2. choose gatway outside of env subnet
3.

Actual results:
installer informs user to select a gw within the same subnet.

Expected results:
inaller allows the user to select any gw.

Additional info: