proxmox-mirrors/pve-docs
1
0
Fork 0
mirror of https://git.proxmox.com/git/pve-docs synced 2025-05-01 05:29:33 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity

various minor cleanups

Browse Source
This commit is contained in:
Fabian Grünbichler 2016-09-27 10:58:55 +02:00 committed by Dietmar Maurer
parent 8c9060b162
commit e300cf7dab
3 changed files with 7 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
local-zfs.adoc
View File

@ -158,7 +158,7 @@ GRUB boot loader there. If you use a redundant RAID setup, it installs
the boot loader on all disk required for booting. So you can boot the boot loader on all disk required for booting. So you can boot
even if some disks fail. even if some disks fail.
NOTE: It is not possible to use ZFS as root partition with UEFI NOTE: It is not possible to use ZFS as root file system with UEFI
boot. boot.
@ -242,7 +242,7 @@ As `<device>` it is possible to use more devices, like it's shown in
If you have an pool without cache and log. First partition the SSD in If you have an pool without cache and log. First partition the SSD in
2 partition with `parted` or `gdisk` 2 partition with `parted` or `gdisk`
IMPORTANT: Always use GPT partition tables (gdisk or parted). IMPORTANT: Always use GPT partition tables.
The maximum size of a log device should be about half the size of The maximum size of a log device should be about half the size of
physical memory, so this is usually quite small. The rest of the SSD physical memory, so this is usually quite small. The rest of the SSD

6
pve-firewall.adoc
View File

@ -67,8 +67,8 @@ file system. So those files are automatically distributed to all
cluster nodes, and the `pve-firewall` service updates the underlying cluster nodes, and the `pve-firewall` service updates the underlying
`iptables` rules automatically on changes. `iptables` rules automatically on changes.
You can configure anything using the GUI (i.e. Datacenter -> Firewall, You can configure anything using the GUI (i.e. *Datacenter* -> *Firewall*,
or on a Node -> Firewall), or you can edit the configuration files or on a *Node* -> *Firewall*), or you can edit the configuration files
directly using your preferred editor. directly using your preferred editor.
Firewall configuration files contains sections of key-value Firewall configuration files contains sections of key-value
@ -362,7 +362,7 @@ with a source IP not matching its interface's corresponding ipfilter set will
be dropped. be dropped.
For containers with configured IP addresses these sets, if they exist (or are For containers with configured IP addresses these sets, if they exist (or are
activated via the general `IP Filter` option in the VM's firewall's 'options' activated via the general `IP Filter` option in the VM's firewall's *options*
tab), implicitly contain the associated IP addresses. tab), implicitly contain the associated IP addresses.
For both virtual machines and containers they also implicitly contain the For both virtual machines and containers they also implicitly contain the

4
pvecm.adoc
View File

@ -31,8 +31,8 @@ communication, and such clusters can consist of up to 32 physical nodes
`pvecm` can be used to create a new cluster, join nodes to a cluster, `pvecm` can be used to create a new cluster, join nodes to a cluster,
leave the cluster, get status information and do various other cluster leave the cluster, get status information and do various other cluster
related tasks. The Proxmox Cluster file system (pmxcfs) is used to related tasks. The **P**rox**m**o**x** **C**luster **F**ile **S**ystem (``pmxcfs'')
transparently distribute the cluster configuration to all cluster is used to transparently distribute the cluster configuration to all cluster
nodes. nodes.
Grouping nodes into a cluster has the following advantages: Grouping nodes into a cluster has the following advantages: