Bug 795906 - File System Size/Layout/Recommendations
Summary: File System Size/Layout/Recommendations
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: CloudForms Common
Classification: Retired
Component: Docs Installation Guide
Version: 1.0.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
Assignee: Dan Macpherson
QA Contact: ecs-bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-02-21 19:10 UTC by james labocki
Modified: 2012-06-07 06:18 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
The CloudForms Cloud Engine needs an elastic file system to expand storage Image Warehouse (iwhd). Without an elastic file system, Image Warehouse might exceed the allocated storage space. Choose one of two options as a solution: 1. Mount a form of elastic storage at /var/lib/iwhd. 2. Mount a form of elastic storage at a user-defined location and change the iwhd path in /etc/iwhd/conf.js A CloudForms Cloud Engine user expands the storage for iwhd using the elastic storage solution.
Clone Of:
Environment:
Last Closed: 2012-06-07 06:18:24 UTC


Attachments (Terms of Use)

Description james labocki 2012-02-21 19:10:38 UTC
Recommendations for filesystem layout are not available. For example, users ran into an issue where / was filled up because IWHD   grew too large. It would be good to allow the IWHD storage path to be   configurable or at least provide guidance on sizing and keeping /var separate. OR BOTH!

Comment 1 Dan Macpherson 2012-02-22 03:58:51 UTC
So if I understand correctly (and to get a better idea of what to do), is this a matter of:

a) Mounting some form of elastic storage at /var/lib/iwhd (or a user-defined directory)

b) If user-defined, include instructions on changing the iwhd path in /etc/iwhd/conf.js

Just need some confirmation that this is the best way to go about it, or if there are any other steps worth mentioning?

Comment 2 Dan Macpherson 2012-03-12 01:06:08 UTC
    Technical note added. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    New Contents:
The CloudForms Cloud Engine User Guide does not contain an elastic file system layout for Image Warehouse (iwhd). Without an elastic file system, Image Warehouse might exceed the allocated storage space. Choose one of two options as a solution:

1. Mount a form of elastic storage at /var/lib/iwhd.

2. Mount a form of elastic storage at a user-defined location and change the iwhd path in /etc/iwhd/conf.js

A CloudForms Cloud Engine expands the storage for iwhd using the elastic storage solution.

Comment 3 Dan Macpherson 2012-03-12 01:07:40 UTC
    Technical note updated. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    Diffed Contents:
@@ -1,7 +1,7 @@
-The CloudForms Cloud Engine User Guide does not contain an elastic file system layout for Image Warehouse (iwhd). Without an elastic file system, Image Warehouse might exceed the allocated storage space. Choose one of two options as a solution:
+The CloudForms Cloud Engine needs an elastic file system to expand storage Image Warehouse (iwhd). Without an elastic file system, Image Warehouse might exceed the allocated storage space. Choose one of two options as a solution:
 
 1. Mount a form of elastic storage at /var/lib/iwhd.
 
 2. Mount a form of elastic storage at a user-defined location and change the iwhd path in /etc/iwhd/conf.js
 
-A CloudForms Cloud Engine expands the storage for iwhd using the elastic storage solution.+A CloudForms Cloud Engine user expands the storage for iwhd using the elastic storage solution.

Comment 4 Dan Macpherson 2012-03-26 23:42:45 UTC
Targeting for 1.0.

Comment 9 Lana Brindley 2012-06-07 06:18:24 UTC
Document is now available on docs.redhat.com. Please raise a new bug for any further issues.

LKB


Note You need to log in before you can comment on or make changes to this bug.