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!
Только зарегистрированные пользователи имеют доступ к сервису!
Для получения аккаунта, обратитесь к администратору.
this is a bit ugly, because pveperf is not an instance of
PVE::CLIHandler - the actual installed man page is still
generated via the pod data contained in
pve-manager/bin/pveperf ...
explain that we ship smartmontools, basic usage of smartctl
default behaviour of smartd, and where to get more information
Signed-off-by: Dominik Csapak <d.csapak@proxmox.com>
like in the appendix - otherwise this reads really strange,
especially for tools like "pveceph" and "pvesubscription",
where the content is just one sentence, which is not
mentioning the binary at all.
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>
As inheritance is a property of paths, so it makes sense to
make them a subsection of them.
The permissions paragraph in what used to be a 'terms and
definitions' section now doesn't fit in and is redundant now
that there's a general introduction paragraph.
It now gets more technical to finish the documentation of
the permission checks found in the API documentation, and is
the final section about the various parts making up the
access control lists.
As they provide an overview of predefined roles and give an
idea of what kind of permissions are available, they fit
better right after the new general permission introduction.
You now first read about users, learning the fact that
they're part of groups and realms, which are described
afterwards.
This seems more natural then starting with realms and then
describing users in a "Terms and Definitions" section.
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>
