From: Aaron Lauterer <a.lauterer@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] [PATCH ha-manager 2/2] tools: adapt line lengths of verbose descriptions
Date: Mon, 11 Nov 2024 11:08:12 +0100 [thread overview]
Message-ID: <20241111100812.89152-2-a.lauterer@proxmox.com> (raw)
In-Reply-To: <20241111100812.89152-1-a.lauterer@proxmox.com>
Signed-off-by: Aaron Lauterer <a.lauterer@proxmox.com>
---
src/PVE/HA/Tools.pm | 13 ++++++++++---
1 file changed, 10 insertions(+), 3 deletions(-)
diff --git a/src/PVE/HA/Tools.pm b/src/PVE/HA/Tools.pm
index 09b73f1..0f9e9a5 100644
--- a/src/PVE/HA/Tools.pm
+++ b/src/PVE/HA/Tools.pm
@@ -40,7 +40,8 @@ sub pve_verify_ha_resource_id {
}
PVE::JSONSchema::register_standard_option('pve-ha-resource-id', {
- description => "HA resource ID. This consists of a resource type followed by a resource specific name, separated with colon (example: vm:100 / ct:100).",
+ description => "HA resource ID. This consists of a resource type followed by a resource"
+ ." specific name, separated with colon (example: vm:100 / ct:100).",
typetext => "<type>:<name>",
type => 'string', format => 'pve-ha-resource-id',
});
@@ -57,7 +58,9 @@ sub pve_verify_ha_resource_or_vm_id {
}
PVE::JSONSchema::register_standard_option('pve-ha-resource-or-vm-id', {
- description => "HA resource ID. This consists of a resource type followed by a resource specific name, separated with colon (example: vm:100 / ct:100). For virtual machines and containers, you can simply use the VM or CT id as a shortcut (example: 100).",
+ description => "HA resource ID. This consists of a resource type followed by a resource"
+ ." specific name, separated with colon (example: vm:100 / ct:100). For virtual machines and"
+ ." containers, you can simply use the VM or CT id as a shortcut (example: 100).",
typetext => "<type>:<name>",
type => 'string', format => 'pve-ha-resource-or-vm-id',
});
@@ -75,7 +78,11 @@ sub pve_verify_ha_group_node {
PVE::JSONSchema::register_standard_option('pve-ha-group-node-list', {
description => "List of cluster node names with optional priority.",
- verbose_description => "List of cluster node members, where a priority can be given to each node. A resource bound to a group will run on the available nodes with the highest priority. If there are more nodes in the highest priority class, the services will get distributed to those nodes. The priorities have a relative meaning only. The higher the number, the higher the priority.",
+ verbose_description => "List of cluster node members, where a priority can be given to each"
+ ." node. A resource bound to a group will run on the available nodes with the highest"
+ ." priority. If there are more nodes in the highest priority class, the services will get"
+ ." distributed to those nodes. The priorities have a relative meaning only. The higher the"
+ ." number, the higher the priority.",
type => 'string', format => 'pve-ha-group-node-list',
typetext => '<node>[:<pri>]{,<node>[:<pri>]}*',
});
--
2.39.5
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
next prev parent reply other threads:[~2024-11-11 10:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-11 10:08 [pve-devel] [PATCH ha-manager 1/2] tools: group verbose desc: mention higher number is higher priority Aaron Lauterer
2024-11-11 10:08 ` Aaron Lauterer [this message]
2024-11-11 20:31 ` [pve-devel] applied: " Thomas Lamprecht
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20241111100812.89152-2-a.lauterer@proxmox.com \
--to=a.lauterer@proxmox.com \
--cc=pve-devel@lists.proxmox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox