+++ This bug was initially created as a clone of Bug #1136329 +++ Description of problem: The current host networking API suffers from various limitations: - A mix of the physical and the logical network configuration - A Cumbersome request format for 'setup networks' - The attach/detach network isn't the RESTFul way to modify the interface - Cannot support a host only network (a network without a physical NIC)
As part of implementing the host network api, we'll introduce a new entity to the API, named Network Attachment. Network Attachment describes the network which is attached to the host. For 3.6 it will be via a network interface only, while future plans are to support an isolated network which isn't attached to any network interface. Since the Network Attachment is the entity for describing a network attachment to the host, and it requires to be associated to an existing network on the data-center, unmanaged networks handling will be done differently than <= ovirt-engine 3.5. Unmanaged networks are networks which are reported by vdsm (hence those networks are reported by libvirt and has the expected prefix of "vdsm-"), but are not identified as networks on the cluster on which the host resides. Till ovirt-engine-3.5.x we allowed the user to remove those networks via the setup-networks dialog on the host level. Since ovirt-engine-3.6, those networks should be cleared automatically by the ovirt-engine in the following scenarios: 1. Moving host between data-centers 2. Moving host between clusters 3. Detaching a network from a cluster 4. Removing a network from a data-center (5. Removing a host from the system ?)
Target release should be placed once a package build is known to fix a issue. Since this bug is not modified, the target version has been reset. Please use target milestone to plan a fix for a oVirt release.
this is an automated message. oVirt 3.6.0 RC3 has been released and GA is targeted to next week, Nov 4th 2015. Please review this bug and if not a blocker, please postpone to a later release. All bugs not postponed on GA release will be automatically re-targeted to - 3.6.1 if severity >= high - 4.0 if severity < high
This bug is not marked for z-stream, yet the milestone is for a z-stream version, therefore the milestone has been reset. Please set the correct milestone or add the z-stream flag.
Re-assigning to the rhev-docs queue so that it can be evaluated by our DPM team.
Assigning to Tahlia for review.
Restoring needinfo.
Content now published in 14.7.1 and 14.7.2 at https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Virtualization/3.6/html/REST_API_Guide/sect-Sub-Collections5.html