Description of problem:
The api action via /api/hosts/{host:id}/nics/{nic:id}/attach|rel=attach
is used to attach a network to a nic.
When a non-vm network is configured with address and boot protocol on top of that nic, any new vlan network attached to the nic will inherit that IP and the boot protocol.


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


How reproducible:
always

Steps to Reproduce:
1. Attach a non vm network 'nonvmnet' to 'eth4'.
2. Set an IP address and boot protocol for 'nonvmnet'
3. Attach a vlan network 'vlan1' to 'eth4'

Using python SDK:
nic1 = hostNics.list(name = 'eth4')[0]
nic1 = nic1.attach(action = params.Action(network = params.Network(name = 'nonvmnet')))
nic1.set_ip (params.IP(address = '10.35.10.200', netmask = '255.255.254.0'))
nic1.set_boot_protocol('static')
nic1.update();
nic1.attach(action = params.Action(network = params.Network(name = 'vlan1')))


Actual results:
Notice eth4.1 interface which carries 'vlan1' has the same IP and boot protocol as 'eth4', even it wasn't configured.

Expected results:
eth4.1 interface which carries 'vlan1' shouldn't have any IP address or boot protocol configuration.

Additional info:
The problem resides within the org.ovirt.engine.api.restapi.resource.BackendHostNicResource.doAttachAction which overrides the IP address, boot protocol (and bonding options) unnecessarily.
Also, the AttachNetworkToInterface command allows to be provide an IP address and boot protocol for the new network, however they aren't modelled in the restapi, hence user will have to use another call for the update() in order to set them.