Bug 1451653

Summary: [RFE][HE] - HE storage domain should be treated as a regular storage domain.
Product: [oVirt] ovirt-engine Reporter: Yaniv Lavi <ylavi>
Component: BLL.HostedEngineAssignee: Doron Fediuck <dfediuck>
Status: CLOSED WONTFIX QA Contact: Raz Tamir <ratamir>
Severity: high Docs Contact:
Priority: high    
Version: 4.1.2CC: bugs, dfediuck, mavital, mkalinin, msivak, ratamir
Target Milestone: ---Keywords: FutureFeature
Target Release: ---Flags: sbonazzo: ovirt-4.3-
mavital: testing_plan_complete?
rule-engine: planning_ack?
rule-engine: devel_ack?
rule-engine: testing_ack?
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-06-06 13:01:02 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: SLA RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 1386497, 1445199, 1455169, 1517810    
Bug Blocks:    

Description Yaniv Lavi 2017-05-17 08:50:07 UTC 
Description of problem:
The hosted engine storage is currently limited in many ways (can not take master, can not be the first storage in the system) causing issue is several system flows. 
We want to make this storage into a regular storage in the system and have the minimal amount of HE specific limitations.
The considerations of load on this SD should be moved to documentation.
Comment 1 Yaniv Lavi 2017-05-17 14:37:07 UTC 
We should try to define what to note when planning disk placement on this storage to not cause engine downtime as part of this effort.
Comment 2 Allon Mureinik 2017-05-17 22:02:08 UTC 
(In reply to Yaniv Dary from comment #1)
> We should try to define what to note when planning disk placement on this
> storage to not cause engine downtime as part of this effort.

HE's domain should be the least favored target for anything the system determines automatically (master domain, memory volumes, etc). Other than that, disk locations are determined by the user.
Comment 3 Yaniv Kaul 2017-07-05 09:22:01 UTC 
Moving to SLA. Once we implement the new deployment, we expect it to be a regular domain (with the exception of blocking moving it to maintenance from the Engine - a separate bug exists). This bug is a tracker(?) for all activities needed to remove the special treatments throughout the code.
Comment 4 Yaniv Lavi 2017-11-27 14:33:38 UTC 
Why was this moved to 4.3?
Comment 5 Martin Sivák 2017-11-28 12:40:36 UTC 
Because it is too late to make sure all flows work as expected in 4.2.0. We will start removing the restrictions for 4.3 and consider backporting all that are working back to 4.2.z.
Comment 6 Yaniv Lavi 2018-06-06 13:01:02 UTC 
For now closing.
We will remove more limitation as requested from customer.