Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1080366

Summary: [RFE] allow setting up a single Boot Protocol for whole Logical Network
Product: Red Hat Enterprise Virtualization Manager Reporter: David Jaša <djasa>
Component: RFEsAssignee: Nir Yechiel <nyechiel>
Status: CLOSED WONTFIX QA Contact: Meni Yakove <myakove>
Severity: medium Docs Contact:
Priority: low    
Version: 3.4.0CC: danken, djasa, gklein, iheim, lpeer, nyechiel, rbalakri, yeylon
Target Milestone: ---Keywords: FutureFeature
Target Release: ---Flags: nyechiel: Triaged+
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: network
Fixed In Version: Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-11-15 21:47:16 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Network RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description David Jaša 2014-03-25 09:30:08 UTC 
Description of problem:
It's quite likely for all hosts in given DC/Cluster to have the same style of configuration of Boot Protocol of a Logical Network so it makes sense to have this setting in respective Logical Network configuration.

The implementation should IMO follow these points:
1. there should be a new per-network setting for boot protocol - e.g. "undefined" - that would keep current behaviour
2. It should be possible to configure common prefix (netmask) and gateway for Boot Protocol set to Static
3. change of Boot Protocol to DHCP or None could be applied immediately (with automatic fallback to old behaviour if the DHCP fails)
4. change of BP to Static at Required network would turn hosts to non-operational till admin sets up IPs for the hosts
5. all changes to live networks (network configured and running on at least one host) should be confirmed in a separate dialog
6. hosts going to non-operational as a result to change of network BP to Static should be enumerated in the confirmation dialog

This is IMO a matter for discussion:
7. possibility to override network-level setting on particular hosts. It would make sense for various testing but it would also the whole feature more error-prone
8. for non-mgmt networks, assign a range of IPs that could RHEV-M configure on particular host statically

Version-Release number of selected component (if applicable):
RHEV 3.4
Comment 4 Dan Kenigsberg 2015-05-31 15:42:46 UTC 
Closing old bugs. If this issue is considered important to customers, please re-open the bug.