Bug 1359181
| Summary: | Docs: RHVH: Add documentation for requires in case of custom partitioning | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Virtualization Manager | Reporter: | Fabian Deutsch <fdeutsch> |
| Component: | Documentation | Assignee: | Tahlia Richardson <trichard> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Byron Gravenorst <bgraveno> |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | 4.0.0 | CC: | fdeutsch, gklein, lsurette, mkalinin, rbalakri, rbarry, srevivo, trichard, ykaul, ylavi |
| Target Milestone: | ovirt-4.0.4 | ||
| 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: | 2016-10-28 00:09:29 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | Docs | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Fabian Deutsch
2016-07-22 12:46:04 UTC
(In reply to Fabian Deutsch from comment #0) > Description of problem: > In the normal flow, users are expected to use auto partitioning when > installing RHVH 4.0. > > However, if a user decides to do custom partitioning, then a few > requirements need to be met: > > 1. LVM thin provisioning needs to be used > 2. / needs to reside on a thin LV So that it will be possible to extend it? > 3. /var needs to be a separate mount point (can be an LV or anything else) >> 2. / needs to reside on a thin LV
> So that it will be possible to extend it?
The primary reason why / is on a thin LV is, that we only need to allocate as many space in the LV's thinpool as really is used by the file-system. This is over-provisioning.
We can do this, because we do not except the root file-system to grow much, however, because customers could install additional rpms we do need to have the ability to allocate more space to the file-system if more space is required (i.e. when additional rpms are installed).
I.e. currently the root file-system of Node is 6GB in size, but we currently only require 1.3GB.
At the end however, yes, you could also resize the file-system
A previous email about custom partitioning also included: * / must be at least 6GB * xfs or ext4 must be used Do these requirements still apply, too? Yes |