Bug 709177

Summary:	Remove non-applicable content related to storage minimums
Product:	Red Hat Enterprise Linux 6	Reporter:	Stephen Gordon <sgordon>
Component:	Documentation	Assignee:	Stephen Gordon <sgordon>
Status:	CLOSED NEXTRELEASE	QA Contact:	ecs-bugs
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	6.2	CC:	jskeoch, mburns
Target Milestone:	rc	Keywords:	Documentation
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	Red_Hat_Enterprise_Linux-Hypervisor_Deployment_Guide-6-en-US-1-22	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2011-10-31 01:07:57 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Bug Depends On:
Bug Blocks:	617060

Description Stephen Gordon 2011-05-31 00:12:53 UTC

Description of problem:

The Hypervisor Deployment Guide goes into some detail about the minimum size required for each partition:

http://documentation-stage.bne.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/6/html-single/Hypervisor_Deployment_Guide/index.html#chap-Deployment_Guide-Requirements_and_limitations_of_Red_Hat_Enterprise_Virtualization_Hypervisors

The rhev-hypervisor 6.x builds however appear to automatically calculate the partition sizes, no opportunity is presented for changing them.

The existing content should be replaced by one overall number representing the minimum amount of storage that must be available as a total.

Version-Release number of selected component (if applicable):

6.1

Comment 1 Stephen Gordon 2011-05-31 00:15:05 UTC

Mike can you confirm:

1) That it is not planned to allow changing of the partition sizes from the installer UI.
2) Whether or not granular configuration will still be supported when parsing in the storage_vol kernel parameter?
3) What the recommended total minimum storage is for rhev-hypervisor 6.1/6.2?

Thanks,

Steve

Comment 3 Mike Burns 2011-05-31 13:21:02 UTC

(In reply to comment #1)
> Mike can you confirm:
> 
> 1) That it is not planned to allow changing of the partition sizes from the
> installer UI.
Correct, no changes in the GUI install

> 2) Whether or not granular configuration will still be supported when parsing
> in the storage_vol kernel parameter?

Yes, storage_vol is still supported for automated installations

> 3) What the recommended total minimum storage is for rhev-hypervisor 6.1/6.2?

Actual minimums
Root (x2) = 256*2=512MB
Config = 5MB
Logging = 5MB (Though i think VDSM actually increases this to 2GB)
Data = 5MB
Swap = 5MB

532 MB actual minimum

Defaults:
Root (x2) = 256*2 = 512MB
Config = 5MB
Logging = 2048MB

Swap is dependent on RAM + and overcommit ratio
RAM        Swap(MB)
<4GB        2048
<16GB       4096
<64GB       8192
else        16384

overcommit defaults to 0.5 and is multiplied by the actual RAM on the machine.

I think the swap calculation is actually documented somewhere in the base RHEL guides, though I'm not sure exactly where

Data, by default takes up the entire rest of the disk.  It is used for upgrades when initiated from RHEV-M, so it should probably be at least 256MB

Comment 4 Stephen Gordon 2011-07-07 22:35:09 UTC

Actual minimums ended up being 8 MB, not 5 MB, as 8 MB is the minimum size of an LV extent. 
 
 * See Section 2.1.
 * See Section 4.2.3 under storage_vol parameter.
 
Red_Hat_Enterprise_Linux-Hypervisor_Deployment_Guide-6-web-en-US-1-17.el6eng

Comment 6 Stephen Gordon 2011-07-15 04:55:36 UTC

 * Section 4.2.3
   - Updated to read 8 MB.

Will stage for review in next push.

Comment 7 Stephen Gordon 2011-07-18 00:56:13 UTC

Staged for QE review:

Red_Hat_Enterprise_Linux-Hypervisor_Deployment_Guide-6-en-US-1-22