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!
Только зарегистрированные пользователи имеют доступ к сервису!
Для получения аккаунта, обратитесь к администратору.
While apt supports both false/true and yes/no (and maybe more?), the
sources.list manual page documents "Enabled: no", so lets use that
here too.
Drop a duplicate "of" and reword the whole not a bit.
Signed-off-by: Thomas Lamprecht <t.lamprecht@proxmox.com>
The section uses addresses 10.10.10.X and 10.20.20.X in examples and
implicitly assumes they are in disjoint subnets, but does not
explicitly state this.
For better clarity, explicitly mention these are /25 subnets (this
subnet mask is also used in the "Separate Cluster Network" section).
Signed-off-by: Friedrich Weber <f.weber@proxmox.com>
Reviewed-by: Maximiliano Sandoval <m.sandoval@proxmox.com>
Link: https://lore.proxmox.com/20250908145305.112814-1-f.weber@proxmox.com
As already mentioned in the known issues in the roadmap [0], cgroupv2
is the only supported mode in Proxmox VE 9.
To not break any references, because Proxmox VE 8 is not EOL yet, keep
the section about changing the cgroup version.
[0]: https://pve.proxmox.com/wiki/Upgrade_from_8_to_9#cgroup_V1_Removal
Signed-off-by: Fiona Ebner <f.ebner@proxmox.com>
Testing has shown that running corosync (only) over a bond can be
problematic in some failure scenarios and for certain bond modes. The
documentation only discourages bonds for corosync because corosync can
switch between available networks itself, but does not mention other
caveats when using bonds for corosync.
Hence, extend the documentation with recommendations and caveats
regarding bonds for corosync.
Signed-off-by: Friedrich Weber <f.weber@proxmox.com>
Reviewed-by: Mira Limbeck <m.limbeck@proxmox.com>
Link: https://lore.proxmox.com/20250730085836.147270-1-f.weber@proxmox.com/
Add documentation about HA Resource Affinity rules, what effects those
have on the CRS scheduler, and what users can expect when those are
changed.
There are also a few points on the rule conflicts/errors list which
describe some conflicts that can arise from a mixed usage of HA Node
Affinity rules and HA Resource Affinity rules.
Signed-off-by: Daniel Kral <d.kral@proxmox.com>
Link: https://lore.proxmox.com/20250730181428.392906-16-d.kral@proxmox.com
using the new top-level `make tidy` target, which calls perltidy via
our wrapper to enforce the desired style as closely as possible.
Signed-off-by: Thomas Lamprecht <t.lamprecht@proxmox.com>
Often, when one reviews or applies a series that adds new
documentation and UI (e.g., new feature) it's annoying to not be able
to build the UI if it already points to new onlineHelp info
definitions, so add a flag that allows during the hard error into a
warning.
Signed-off-by: Thomas Lamprecht <t.lamprecht@proxmox.com>
- Start by mentioning the preconfigured Ceph repository and what options
there are for using Ceph (HCI and external cluster)
- Link to available installation methods (web-based wizard, CLI tool)
- Describe when and how to upgrade
- Add new attributes to avoid manual editing multiple lines
- Create a table as an overview of Ceph release availability,
maintaining clarity and avoiding duplicated text for each release
- Advise to read the latest version of the corresponding admin guide
- Add a TODO describing what to update occasionally
- List and link to the estimated EOL dates of Ceph releases
- Revise the descriptions of available repository components
- Mention when it makes sense to edit a repository file manually
- Mention upgrading Ceph under "System Software Updates"
Signed-off-by: Alexander Zeidler <a.zeidler@proxmox.com>
Link: https://lore.proxmox.com/20250730180254.320235-1-a.zeidler@proxmox.com
This hides the TOC by default on narrower screens (< 1000 px/dp) and
adds a simple toggle menu to make it pop out.
Most is handled purely through CSS, but to hide the menu when clicking
on links or when there is no TOC at all (e.g., for the index or FAQ)
we need a bit of JavaScript. There just monkey patch the asciidoc TOC
JS function to ensure we get called in the correct moment.
Further, add a modal-like "label" over the content if the TOC menu is
open, clicking on that will also close the TOC, again with pure CSS.
This also tries to improve styling and readability for mobile in
general, while I tested on many sizes, virtual devices in Firefox and
Chromiums developer mode, and also some actual smartphone, it
certainly will not yet be perfect everywhere, but it definitively
should be better than the status quo.
Signed-off-by: Thomas Lamprecht <t.lamprecht@proxmox.com>
This avoids that wide tables where the cell content cannot easily wrap
cause horizontal scrolling for the whole page, rather just cause that
scrolling for the table itself, so wrap in in a div and make that use
overflow-x: auto style.
Signed-off-by: Thomas Lamprecht <t.lamprecht@proxmox.com>
