Bug 1683075
Summary: | [DOC] Clarity on increasing the size of /var/log in RHHI4Virt deployment document. | ||
---|---|---|---|
Product: | [Red Hat Storage] Red Hat Gluster Storage | Reporter: | Mugdha Soni <musoni> |
Component: | doc-Deploying_RHHI | Assignee: | Laura Bailey <lbailey> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | Mugdha Soni <musoni> |
Severity: | high | Docs Contact: | |
Priority: | unspecified | ||
Version: | rhhiv-1.6 | CC: | asriram, lbailey, musoni, rcyriac, rhs-bugs, sankarshan, sasundar, seamurph |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2019-05-20 04:18:50 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: | |||
Bug Depends On: | |||
Bug Blocks: | 1663200 |
Description
Mugdha Soni
2019-02-26 08:27:13 UTC
This changes comes as part of deployment enhancement and attaching this doc bug to the associated doc RFE tracker @Anjana, could you provide devel_ack on this one ? Already we have warning on minimum requirement of 15 GB for /var/log Now we need to emphasize, the available space of /var/log should be 15GB as requirement, else the validation during deployment will fail This is a inflight bug and doesn't qualify to be RFE, though the parent change came in from deployment enhancement RFE (In reply to SATHEESARAN from comment #1) > This changes comes as part of deployment enhancement and attaching this doc > bug to the associated doc RFE tracker > > @Anjana, could you provide devel_ack on this one ? > Already we have warning on minimum requirement of 15 GB for /var/log > > Now we need to emphasize, the available space of /var/log should be 15GB as > requirement, > else the validation during deployment will fail Emphasis on available space to be at least 15 GB is good. But I am not sure we should add the steps to increase the size as provided in Comment 0 (In reply to Rejy M Cyriac from comment #3) > > Emphasis on available space to be at least 15 GB is good. > > But I am not sure we should add the steps to increase the size as provided > in Comment 0 This is for ease of use purpose, the commands will be helpful for customers to directly increase the size of the /var/log/ LV @Rejy, Do you expect that these commands should be already known for the admin/customer ? (In reply to Laura Bailey from comment #4) > Is this done as part of the ansible installation script, or is it something > users need to do manually? User have to do it manually. They have to resize the /var/log/ LV such a way, the available space is 15GB > What is the distinction between ensuring that /var/log is at least 15GB on > install, and ensuring that it has 15GB available on install? I'm not sure > what the difference is here. > > Mugdha, can you clarify? By default /var/log is the mounted filesytem with a LV for it. The default size of /var/log comes around 7GB. We have a not to increase it to 15GB. Take for example, size of /var/log is 15GB But now, we are not sure, all that 15GB is available or consumed by some other logs say ovirt logs. Say, by the time the user goes for RHHI-V deployment, /var/log/ is 11GB full, which means only 4GB is available. This adds the risk. So the newly added deployment validation, always checks for available space of 15GB and that needs to be emphasized in the document (In reply to SATHEESARAN from comment #6) > (In reply to Rejy M Cyriac from comment #3) > > > > Emphasis on available space to be at least 15 GB is good. > > > > But I am not sure we should add the steps to increase the size as provided > > in Comment 0 > > This is for ease of use purpose, the commands will be helpful for customers > to > directly increase the size of the /var/log/ LV > > @Rejy, Do you expect that these commands should be already known for the > admin/customer ? I would expect that only the steps specific to RHHI-V be documented in the RHHI-V guide. If the steps are generic and related to components at RHEL, such as LVM, the ideal way would be to point the admin to the relevant section of the RHEL guide. |