SetupNetwork feature is missing a very important update implementation. VDSM is able to receive nics collection which describe which nics will be updated and handle only those nics. This implementation is missing from backend. It automatically treat missing nics as nics we would like to remove. A very buggy scenario would be, missing mgmt network. The idea is to send (via REST API) a collection which contain only the interfaces (nics) we would like to update. This is actually an UPDATE collection procedure. it could be added as a different action: http://engine ip:port/hosts/id/nics/updatenetworks
Roy, can you remind me what was the reason/s not implementing setupnetworks via PUT?
setupnetworks is a creation API, it builds networks and removes others by sending the FULL desired topology to the backend. PUT shall allow you to send a small portion of the topology for update i.e PUT /api/hosts/{id}/nics host_nics host_nic name: em1.300 boot_protocol: dynamic
Closing old bugs. If this issue is still relevant/important in current version, please re-open the bug.