Bug 1062610

I think instead of removing network from the host automatically the new pop up window should appear with checkbox, proposing to remove network from all the hosts as well.
So the user can decide if to leave this network on the hosts as unmanaged or to remove it from there during removal from the DC.

Genadi/Martin: Is leaving a network (or turning a network into) unmanaged a valid use-case? or is that something that we would want to block? if the latter - we wouldn't recommend asking the user whether he wants to delete the network from the Host(s) as well - we should simply delete it.

[I am assuming that if the network is in use (e.g. a running(?) VM has a virtual NIC associated with the deleted network) - the removal of the Logical Network will fail]

Einav: Leaving a network as unmanaged is a valid use case and we don't want to block it.
The removal of the network indeed should fail if running or non-running VM is using this network

(In reply to Einav Cohen from comment #2)
> Genadi/Martin: Is leaving a network (or turning a network into) unmanaged a
> valid use-case? or is that something that we would want to block? if the
> latter - we wouldn't recommend asking the user whether he wants to delete
> the network from the Host(s) as well - we should simply delete it.
> 
> [I am assuming that if the network is in use (e.g. a running(?) VM has a
> virtual NIC associated with the deleted network) - the removal of the
> Logical Network will fail]

Unamanged networks can only be removed from the hosts by ovirt-engine.
Unless the user creates a logical network which matches the same network name.

Removing the network from the data-center implies the user wishes not the manage the network from ovirt any more. But it doesn't absolutely express his desire to remove it from the hosts as well (must admit - don't have a concrete justification for that in mind).

We can expose a new parameter to this command which will indicate whether networks should be removed from hosts. The checkbox on the UI will be checked by default. Restapi user will have to set it to 'true' in order to apply the network removal from all of the hosts.

Another scenario for removing unmanaged network from the Host:
When moving Host with network 'red' from one DC to another one (that doesn't or does contain red), the user should be asked if he wants that network on Host in a new DC.
If that network doesn't exist on the new DC it appears today as unmanaged.

when removing a network, need to prompt (in the Remove Network(s) dialog):

"""
NOTE: Host1, Host2, ..., Host<n> are connected to this network. 
what would you like to do?

[o] disconnect the Hosts from the removed network
[ ] keep the Hosts connected to this network (this network will become unmanned in those Hosts). 
"""

for simplicity, we can allow network-removal on only a single network (otherwise, dialog may become cumbersome). 

when moving a Host from one DC to another, and the Host contains network1, network2, ..., network<n> that don't exist in the target DC, need to prompt (in a confirmation dialog): 

"""
NOTE: network1, network2, ..., network<n> are connected to this Host and do not exist in the target Data Center. 
what would you like to do?

[o] disconnect the Host from these networks. 
[ ] keep the networks connected to this Host (these networks will become unmanned in this Host). 
"""
an additional option, if makes sense, may be "[ ] add these networks to the target Data Center / Cluster".

Note that similarly to Bug 1091692, in my opinion the same behavior should be applied to detachment from clusters.

Closing old RFEs, please reopen if still needed.
Patches are always welcomed.