Description of problem: In order to configure network using could-init the user must enter IP/NETMASK/GATEWAY. There is no way to add network with 'start on boot' = yes and 'bootproto' = none. Version-Release number of selected component (if applicable): ovirt-engine-3.5.0-0.0.master.20140629172257.git0b16ed7.el6.noarch Actual results: User must enter IP/NETMASK/GATEWAY to add network using could-init Expected results: User can add network without IP/NETMASK/GATEWAY and with 'start on boot'
is this an RFE? you should be able to achieve what you need by using a custom script
But configure interface with bootproto=none and without IP is legit and we should support it without any user script.
I tested the following configuration which should be supported via the rest-api: [ [ "org.ovirt.engine.core.common.businessentities.VmInitNetwork", { "startOnBoot" : false, "name" : "eth0", "bootProtocol" : "STATIC_IP", "ip" : "10.35.7.222", "netmask" : "255.255.254.0", "gateway" : "10.35.7.254", "id" : null } ], [ "org.ovirt.engine.core.common.businessentities.VmInitNetwork", { "startOnBoot" : true, "name" : "eth1", "bootProtocol" : "NONE", "id" : null } ] ] Specifically for the second nic 'eth1' which has a boot protocol 'NONE'. The content of the vm payload is: iface eth0 inet static address 10.35.7.222 netmask 255.255.254.0 gateway 10.35.7.254 iface eth1 inet none auto eth0 eth1 And the result of it on the guest is: [admin@localhost network-scripts]$ cat /etc/sysconfig/network-scripts/ifcfg-eth1 # Created by cloud-init v. 0.7.2 on Tue, 22 Jul 2014 12:59:23 +0000 DEVICE=eth1 ONBOOT=no which is complied with the request of this bug. Since this could be achieved via the rest-api, I don't see why it couldn't be supported by the UI as well.
Assigning to Greg, as this seems like a reasonably easy fix for someone who knows the code; probably what's needed is to have a choice of boot protocol in the GUI similar to that in the API (either using a list box or a radio button) instead of a DHCP checkbox, and flush that data to the backend action parameters.
Verified on - 3.5.0-0.10.master.el6ev
oVirt 3.5 has been released and should include the fix for this issue.