Bug 1468519

Summary:	[DOC] Disclaimer, required for controller/Compute Disk Space
Product:	Red Hat OpenStack	Reporter:	Nikhil Shetty <nshetty>
Component:	documentation	Assignee:	Laura Marsh <lmarsh>
Status:	CLOSED CURRENTRELEASE	QA Contact:	RHOS Documentation Team <rhos-docs>
Severity:	high	Docs Contact:
Priority:	medium
Version:	10.0 (Newton)	CC:	dcadzow, dmacpher, jjoyce, jraju, lmarsh, nshetty, sacpatil, srevivo
Target Milestone:	---	Keywords:	Triaged
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-04-17 18:28:32 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Nikhil Shetty 2017-07-07 10:16:02 UTC

Description of problem:We Need Clear Disclaimers in the Section For Controller/Compute hardware Requirements Stating that For Controllers at the time of deployment for 
1) Swift it is recommended to Have 1 TB of SSD Disks on controller
2) For Ceilometer it is recommended to have 500GB of Disk Space Free on controller
3) On Compute If the cu. uses the local Disk, the Instances can take up a lot of disk space


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


How reproducible:NA


Steps to Reproduce:NA
1.
2.
3.

Actual results: https://access.redhat.com/documentation/en-us/red_hat_openstack_platform/11/html-single/director_installation_and_usage/#sect-Controller_Node_Requirements

https://access.redhat.com/documentation/en-us/red_hat_openstack_platform/11/html-single/director_installation_and_usage/#sect-Compute_Node_Requirements

In the above Section We are stating that only 40 GB of free disk space is enough for deployment  which is clearly not something which can be specified at for a Cu. who is New to Openstack And wishes to deploy Openstack for his production Environment will be misguided by the above Statement.

We need to be specific that, in case of Controller We need to have a specific Amount of Disk space after consultation with DFG as to what would be the ideal scenario for having Disk Space or Disk type for their Application/instances



Expected results: We should specify atleast 1TB for controllers & 500 GB for Compute Nodes for any Production.


Additional info: The use cases have been specified in the problem Description Itself

Comment 7 Jaison Raju 2017-07-19 07:16:11 UTC

Hi Dan,

The concern is that the minimum recommended will change as per the planned storage & use of components like gnocchi / ceilometer etc .
The operator should be made aware of the while reviewing installation requirements.
Give me 2days to come up with a good content for this.
will clear needinfo when i do .

Comment 8 Jaison Raju 2017-12-26 11:02:34 UTC

Hi Dan,

I apologize for the delay.
We can close this doc bug.
I noticed the google doc being made for https://bugzilla.redhat.com/show_bug.cgi?id=1468573 .
https://docs.google.com/document/d/1otxdPd4A3no6xMt3GuqBgD4xCNz0swf-pgCSOTllq2g/edit?ts=597f461d#heading=h.8iag3ng4jas6

The section 'Disk Storage and Layout' in doc in progress covers my concerns.
Are we going to add that in all RHOS version docs ?
If so we can close this as duplicate.

Regards,
Jaison R

Comment 9 Dan Macpherson 2017-12-29 06:30:17 UTC

I think we're publishing it for OSP12 only at the moment:

https://access.redhat.com/documentation/en-us/red_hat_openstack_platform/12/html/deployment_recommendations_for_specific_red_hat_openstack_platform_services/

Not 100% if everything in that doc covers previous versions.

Comment 10 Jaison Raju 2018-01-05 07:30:52 UTC

I am okay if atleast the 'Disk Storage and Layout' section is present in RHOS10 docs.

If this is not yet planned , can you do it ?

Comment 11 Dan Macpherson 2018-01-08 11:19:07 UTC

ACK

Comment 12 Lucy Bopf 2018-04-23 02:35:55 UTC

(In reply to Dan Macpherson from comment #11)
> ACK

Dan, should the assignee for this BZ be set to you, or does this need to go back to the queue for scoping?

Comment 16 Lucy Bopf 2018-08-10 04:08:59 UTC

Moving back to 'NEW' to be scoped and reviewed for priority.