Description of problem: The user could now configure some of the appliance parameters such its hostname via cloud-init. But the appliance still relies only on DHCP based configuration. Let the user specify a static network configuration for the appliance and provide it over cloud-init. Version-Release number of selected component (if applicable): 3.6 How reproducible: 100% Steps to Reproduce: 1. deploy hosted-engine configuring the appliance via cloud-init 2. 3. Actual results: it simply relies over DHCP Expected results: it should ask about an optional static configuration Additional info: Cloud-init already supports network-interfaces field and it should be able to translate it into the specific format for the guest OS. Example: network-interfaces: | iface eth0 inet static address 192.168.1.10 network 192.168.1.0 netmask 255.255.255.0 broadcast 192.168.1.255 gateway 192.168.1.254 Evaluate if we also want to push an entry for the host in guest /etc/hosts
Verified on ovirt-hosted-engine-setup-1.3.0-0.4.beta.git42eb801.el7ev.noarch Use have possibility to choose static network configuration(ip, DNS, default gateway)
oVirt 3.6.0 has been released on November 4th, 2015 and should fix this issue. If problems still persist, please open a new BZ and reference this one.