Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

provisioning: add some more information about the partitioning #390

Merged
merged 1 commit into from
Mar 25, 2024
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 6 additions & 4 deletions docs/guides/deploy-guide/provisioning.md
Original file line number Diff line number Diff line change
Expand Up @@ -54,19 +54,21 @@ is possible without network connectivity.
* Dedicated disks may be provided for `/var/lib/docker` on the controller nodes. In this case, do not
use an LV for `/var/lib/docker` but the devices provided for it.
* Do not configure devices that are not required for the operating system.
* The use of own file systems for the following mountpoints is recommended. The size of the individual partitions
is minimal. Depending on the node type, the individual partitions should be made larger. This applies in
particular to `/var/lib/docker`. On controllers at least 100 GByte should be used.
* The use of own file systems for the following mountpoints is recommended. The size of the partitions/LVs
is minimal. Depending on the node type, the partitions/LVs should be made larger.
* `/` (10 GByte, logical volume `root`)
* `/home` (2 GByte, logical volume `home`)
* `/tmp` (5 GByte, logical volume `tmp`)
* `/var/lib/ceph` (50 GByte, logical volume `ceph`) (optional for storage nodes)
* `/var/lib/docker` (30 GByte, logical volume `docker`, do not set the `nosuid` flag on `/var/lib/docker`)
* When using XFS as the file system for `/var/lib/docker`, note the following: Running on XFS without `d_type` support
causes Docker to skip the attempt to use the `overlay` or `overlay2` driver.
* 100 GB should be used on a control node at the beginning.
* `/var/lib/docker` must be extended later during operation depending on the node type. You do this
in operation when you can see how many logs etc. are generated.
* `/var/log/audit` (1 GByte, logical volume `audit`)
* `/var` (10 GByte, logical volume `var`)
* `swap` (min 8 GByte, logical volume `swap`)
* `swap` (8 GByte, logical volume `swap`)
* Choose `No automatic updates`.
* Choose `OpenSSH server` as software to install.
* **Do not install any other software component.** Everything you need will be installed later by OSISM.
Expand Down
Loading