IF YOU WOULD LIKE TO GET AN ACCOUNT, please write an
email to Administrator. User accounts are meant only to access repo
and report issues and/or generate pull requests.
This is a purpose-specific Git hosting for
BaseALT
projects. Thank you for your understanding!
Только зарегистрированные пользователи имеют доступ к сервису!
Для получения аккаунта, обратитесь к администратору.
Authored by: Thomas Lamprecht <t.lamprecht@proxmox.com>
Co-Authored by: Oguz Bektas <o.bektas@proxmox.com>
Signed-off-by: Oguz Bektas <o.bektas@proxmox.com>
...for a cluster to work, as we can corosync can use multicast to
from the totem ring and we then can use that to communicate the other
nodes cluster IP.
Signed-off-by: Thomas Lamprecht <t.lamprecht@proxmox.com>
ddouble words found with /(\b\S+\b)\s+\b\1\b/
(the silver searcher `ag` can find matches even with newlines in
between without extra flags)
Adapt some wording when touching the lines.
Signed-off-by: Thomas Lamprecht <t.lamprecht@proxmox.com>
VMID conflict are not the main problem, and some users could think
that they can handle VMID conflict them self and thus do not separate
the storages. Therefore mention the locking over cluster boundary
problem too.
Signed-off-by: Thomas Lamprecht <t.lamprecht@proxmox.com>
* do not add `pvecm status` when we talk about `pvecm nodes`
* do not say twice to login to a cluster member node for the same command set
* move the big danger warning in the middle of operations, so it might not
be skipped
The "Remove Cluster configuration" section is outdated and has also
missing steps (e.g. stopping corosync before removing its config)
We have the information in the pvecm.adoc (Cluster Manager) so delete
the howto and reference the one from pvecm instead.
Signed-off-by: Thomas Lamprecht <t.lamprecht@proxmox.com>
It should be clear that the VMs you have now on the node should be those you
want there after the separation.
The sentence is not quite correct and more confusing remove it.
Signed-off-by: Thomas Lamprecht <t.lamprecht@proxmox.com>
Describe separate cluster network, the redundant ring protocol, the
requirements for a cluster network and how to edit and trouble shoot the
corosync config
Signed-off-by: Thomas Lamprecht <t.lamprecht@proxmox.com>
especially:
- filesystem -> file system
- mountpoint -> mount point
- lxc -> LXC
- pve -> PVE
- it's -> its (where appropriate)
- VM´s -> VMs (and similar)
- Ressource -> Resource
- maximal -> maximum or at most
- format of section headers and block headers
reformat most existing 'text' as either `text` or ``text''
reformat most existing "text" as either ``text'' or `text`
reformat 'x' as `x`
harmonize bullet list syntax to use '*' instead of '-'
