[pve-devel] [PATCH pve-docs] fix #844: document first VM/CT start-up delay

[Thomas Lamprecht]

On 25/08/2021 15:15, Dylan Whyte wrote:
> adds paragraphs in the respective qm/pct boot order sections, mentioning
> the initial VM/CT startup delay feature.
> 

looks OK content wise but what spoke against placing this in a sub-paragraph to
the "Proxmox Node Management" section:
https://pve.proxmox.com/pve-docs/pve-admin-guide.html#_proxmox_node_management
and then link to it from qm/pct? Would avoid some repetition.

semi-related, that section could expand a bit with mentioning the start/stop-all
commands and maybe the task related ones. And while looking at the `pvenode`
command list output I noticed that we could add a `pvenode task stop <upid>`
subcommand there too, but really unrelated now, just mentioning to avoid
forgetting it and maybe you want to do that in a separate patch ;-)

> Signed-off-by: Dylan Whyte <d.whyte at proxmox.com>
> ---
>  pct.adoc | 10 ++++++++++
>  qm.adoc  |  8 ++++++++
>  2 files changed, 18 insertions(+)
> 
> diff --git a/pct.adoc b/pct.adoc
> index b88569f..deb57ef 100644
> --- a/pct.adoc
> +++ b/pct.adoc
> @@ -433,6 +433,16 @@ always start after those where the parameter is set, and this parameter only
>  makes sense between the machines running locally on a host, and not
>  cluster-wide.
>  
> +In case your containers rely on slow-to-start resources, for example an external
> +NFS server, you can also set a per-node delay between the time {pve} boots and
> +the time the first container boots. This can be achieved by setting the
> +following:
> +
> + pvenode config set --startall-onboot-delay 10
> +
> +where `10` represents the delay in seconds.
> +
> +
>  Hookscripts
>  ~~~~~~~~~~~
>  
> diff --git a/qm.adoc b/qm.adoc
> index c291cb0..7f23ede 100644
> --- a/qm.adoc
> +++ b/qm.adoc
> @@ -923,6 +923,14 @@ start after those where the parameter is set. Further, this parameter can only
>  be enforced between virtual machines running on the same host, not
>  cluster-wide.
>  
> +In case your VMs rely on slow-to-start resources, for example an external NFS
> +server, you can also set a per-node delay between the time {pve} boots and the
> +time the first VM boots. This can be achieved by setting the following:
> +
> + pvenode config set --startall-onboot-delay 10
> +
> +where `10` represents the delay in seconds.
> +
>  
>  [[qm_qemu_agent]]
>  Qemu Guest Agent
>