update
This commit is contained in:
@@ -16,6 +16,10 @@ interactive menu. Update availability is checked in the background and cached;
|
||||
updates are installed only when explicitly selected or requested with
|
||||
`tapm update`.
|
||||
|
||||
Use `tapm V2` to switch an installed copy to the published V2 branch for
|
||||
testing, and `tapm main` to switch it back. The command refuses to switch when
|
||||
local changes, local-only commits, or diverged branch history would be at risk.
|
||||
|
||||
The required iDSSYS Defaults repository is handled separately: it is
|
||||
automatically refreshed before launch when its last successful check is more
|
||||
than four hours old. If the remote is unavailable, the installed copy is used.
|
||||
@@ -34,7 +38,7 @@ The menu script also supports these direct actions:
|
||||
```text
|
||||
pulse Install Pulse monitoring
|
||||
rmm Install the ConnectWise RMM agent
|
||||
omsa Install Dell OpenManage Server Administrator
|
||||
omsa Install legacy Dell OMSA on supported PowerEdge x30/x40 hosts
|
||||
glances Install Glances
|
||||
acronis Install the Acronis agent
|
||||
post-install Run the ProxMenux post-install configuration
|
||||
@@ -66,3 +70,15 @@ portal without changing ProxMenu.
|
||||
|
||||
The Keepalived deployment additionally requires a healthy, quorate Proxmox
|
||||
cluster and passwordless root SSH between cluster nodes.
|
||||
|
||||
The legacy Dell OMSA installer is limited to supported PowerEdge x30/x40
|
||||
systems running Proxmox VE 9 on Debian 13 (Trixie), amd64.
|
||||
|
||||
CPU compatibility detection previews cluster-wide QEMU VM and template
|
||||
changes before applying the ProxCLMC recommendation through the Proxmox CLI.
|
||||
Running VMs are not restarted automatically.
|
||||
|
||||
Maintenance evacuation leaves HA-managed guests under Proxmox HA control.
|
||||
Remaining shared-storage guests are routed to online, non-maintenance nodes
|
||||
with the required storage, while local-storage guests are gracefully shut
|
||||
down. HA node-affinity preferences are honored when an eligible node exists.
|
||||
|
||||
Reference in New Issue
Block a user