public inbox for pve-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: Fiona Ebner <f.ebner@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
	Daniel Kral <d.kral@proxmox.com>
Subject: Re: [pve-devel] [PATCH ha-manager 10/15] sim: resources: add option to limit start and migrate tries to node
Date: Mon, 28 Apr 2025 15:20:24 +0200	[thread overview]
Message-ID: <28ca2817-2a17-4b67-b245-2b40462b776a@proxmox.com> (raw)
In-Reply-To: <20250325151254.193177-12-d.kral@proxmox.com>

Am 25.03.25 um 16:12 schrieb Daniel Kral:
> Add an option to the VirtFail's name to allow the start and migrate fail
> counts to only apply on a certain node number with a specific naming
> scheme.
> 
> This allows a slightly more elaborate test type, e.g. where a service
> can start on one node (or any other in that case), but fails to start on
> a specific node, which it is expected to start on after a migration.
> 
> Signed-off-by: Daniel Kral <d.kral@proxmox.com>

With some nits:

Reviewed-by: Fiona Ebner <f.ebner@proxmox.com>

> ---
>  src/PVE/HA/Sim/Resources/VirtFail.pm | 37 +++++++++++++++++++---------
>  1 file changed, 26 insertions(+), 11 deletions(-)
> 
> diff --git a/src/PVE/HA/Sim/Resources/VirtFail.pm b/src/PVE/HA/Sim/Resources/VirtFail.pm
> index ce88391..fddecd6 100644
> --- a/src/PVE/HA/Sim/Resources/VirtFail.pm
> +++ b/src/PVE/HA/Sim/Resources/VirtFail.pm
> @@ -10,25 +10,36 @@ use base qw(PVE::HA::Sim::Resources);
>  # To make it more interesting we can encode some behavior in the VMID
>  # with the following format, where fa: is the type and a, b, c, ...
>  # are digits in base 10, i.e. the full service ID would be:
> -#   fa:abcde
> +#   fa:abcdef
>  # And the digits after the fa: type prefix would mean:
>  #   - a: no meaning but can be used for differentiating similar resources
>  #   - b: how many tries are needed to start correctly (0 is normal behavior) (should be set)
>  #   - c: how many tries are needed to migrate correctly (0 is normal behavior) (should be set)
>  #   - d: should shutdown be successful (0 = yes, anything else no) (optional)
>  #   - e: return value of $plugin->exists() defaults to 1 if not set (optional)
> +#   - f: limits the constraints of b and c to the nodeX (0 = apply to all nodes) (optional)

Requires us to have exactly this kind of node name for such tests, but
can be fine IMHO.

>  
>  my $decode_id = sub {
>      my $id = shift;
>  
> -    my ($start, $migrate, $stop, $exists) = $id =~ /^\d(\d)(\d)(\d)?(\d)?/g;
> +    my ($start, $migrate, $stop, $exists, $limit_to_node) = $id =~ /^\d(\d)(\d)(\d)?(\d)?(\d)?/g;
>  
>      $start = 0 if !defined($start);
>      $migrate = 0 if !defined($migrate);
>      $stop = 0 if !defined($stop);
>      $exists = 1 if !defined($exists);
> +    $limit_to_node = 0 if !defined($limit_to_node);
>  
> -    return ($start, $migrate, $stop, $exists)
> +    return ($start, $migrate, $stop, $exists, $limit_to_node);
> +};
> +
> +my $should_retry_action = sub {

"action" feels a bit too general to me. It does not apply to all
actions. Also it determines whether the action itself should fail.
Retrying is then just the consequence.

> +    my ($haenv, $limit_to_node) = @_;
> +
> +    my ($node) = $haenv->nodename() =~ /^node(\d)/g;

No need for a regex, you could just check $limit_to_node == 0 early and
then compare with the exactly known value.

> +    $node = 0 if !defined($node);
> +
> +    return $limit_to_node == 0 || $limit_to_node == $node;
>  };
>  
>  my $tries = {
> @@ -53,12 +64,14 @@ sub exists {
>  sub start {
>      my ($class, $haenv, $id) = @_;
>  
> -    my ($start_failure_count) = &$decode_id($id);
> +    my ($start_failure_count, $limit_to_node) = (&$decode_id($id))[0,4];

Style nit: pre-existing, but you can go for $decode_id->()

>  
> -    $tries->{start}->{$id} = 0 if !$tries->{start}->{$id};
> -    $tries->{start}->{$id}++;
> +    if ($should_retry_action->($haenv, $limit_to_node)) {
> +	$tries->{start}->{$id} = 0 if !$tries->{start}->{$id};
> +	$tries->{start}->{$id}++;
>  
> -    return if $start_failure_count >= $tries->{start}->{$id};
> +	return if $start_failure_count >= $tries->{start}->{$id};
> +    }
>  
>      $tries->{start}->{$id} = 0; # reset counts
>  
> @@ -79,12 +92,14 @@ sub shutdown {
>  sub migrate {
>      my ($class, $haenv, $id, $target, $online) = @_;
>  
> -    my (undef, $migrate_failure_count) = &$decode_id($id);
> +    my ($migrate_failure_count, $limit_to_node) = (&$decode_id($id))[1,4];

Same as above

>  
> -    $tries->{migrate}->{$id} = 0 if !$tries->{migrate}->{$id};
> -    $tries->{migrate}->{$id}++;
> +    if ($should_retry_action->($haenv, $limit_to_node)) {
> +	$tries->{migrate}->{$id} = 0 if !$tries->{migrate}->{$id};
> +	$tries->{migrate}->{$id}++;
>  
> -    return if $migrate_failure_count >= $tries->{migrate}->{$id};
> +	return if $migrate_failure_count >= $tries->{migrate}->{$id};
> +    }
>  
>      $tries->{migrate}->{$id} = 0; # reset counts
>  



_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel


  reply	other threads:[~2025-04-28 13:20 UTC|newest]

Thread overview: 71+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-25 15:12 [pve-devel] [RFC cluster/ha-manager 00/16] HA colocation rules Daniel Kral
2025-03-25 15:12 ` [pve-devel] [PATCH cluster 1/1] cfs: add 'ha/rules.cfg' to observed files Daniel Kral
2025-03-25 15:12 ` [pve-devel] [PATCH ha-manager 01/15] ignore output of fence config tests in tree Daniel Kral
2025-03-25 17:49   ` [pve-devel] applied: " Thomas Lamprecht
2025-03-25 15:12 ` [pve-devel] [PATCH ha-manager 02/15] tools: add hash set helper subroutines Daniel Kral
2025-03-25 17:53   ` Thomas Lamprecht
2025-04-03 12:16     ` Fabian Grünbichler
2025-04-11 11:24       ` Daniel Kral
2025-03-25 15:12 ` [pve-devel] [PATCH ha-manager 03/15] usage: add get_service_node and pin_service_node methods Daniel Kral
2025-04-24 12:29   ` Fiona Ebner
2025-04-25  7:39     ` Daniel Kral
2025-03-25 15:12 ` [pve-devel] [PATCH ha-manager 04/15] add rules section config base plugin Daniel Kral
2025-04-24 13:03   ` Fiona Ebner
2025-04-25  8:29     ` Daniel Kral
2025-04-25  9:12       ` Fiona Ebner
2025-04-25 13:30         ` Daniel Kral
2025-03-25 15:12 ` [pve-devel] [PATCH ha-manager 05/15] rules: add colocation rule plugin Daniel Kral
2025-04-03 12:16   ` Fabian Grünbichler
2025-04-11 11:04     ` Daniel Kral
2025-04-25 14:06       ` Fiona Ebner
2025-04-29  8:37         ` Daniel Kral
2025-04-29  9:15           ` Fiona Ebner
2025-05-07  8:41             ` Daniel Kral
2025-04-25 14:05   ` Fiona Ebner
2025-04-29  8:44     ` Daniel Kral
2025-03-25 15:12 ` [pve-devel] [PATCH ha-manager 06/15] config, env, hw: add rules read and parse methods Daniel Kral
2025-04-25 14:11   ` Fiona Ebner
2025-03-25 15:12 ` [pve-devel] [PATCH ha-manager 07/15] manager: read and update rules config Daniel Kral
2025-04-25 14:30   ` Fiona Ebner
2025-04-29  8:04     ` Daniel Kral
2025-03-25 15:12 ` [pve-devel] [PATCH ha-manager 08/15] manager: factor out prioritized nodes in select_service_node Daniel Kral
2025-04-28 13:03   ` Fiona Ebner
2025-03-25 15:12 ` [pve-devel] [PATCH ha-manager 09/15] manager: apply colocation rules when selecting service nodes Daniel Kral
2025-04-03 12:17   ` Fabian Grünbichler
2025-04-11 15:56     ` Daniel Kral
2025-04-28 12:46       ` Fiona Ebner
2025-04-29  9:07         ` Daniel Kral
2025-04-29  9:22           ` Fiona Ebner
2025-04-28 12:26   ` Fiona Ebner
2025-04-28 14:33     ` Fiona Ebner
2025-04-29  9:39       ` Daniel Kral
2025-04-29  9:50     ` Daniel Kral
2025-04-30 11:09   ` Daniel Kral
2025-05-02  9:33     ` Fiona Ebner
2025-05-07  8:31       ` Daniel Kral
2025-03-25 15:12 ` [pve-devel] [PATCH ha-manager 10/15] sim: resources: add option to limit start and migrate tries to node Daniel Kral
2025-04-28 13:20   ` Fiona Ebner [this message]
2025-03-25 15:12 ` [pve-devel] [PATCH ha-manager 11/15] test: ha tester: add test cases for strict negative colocation rules Daniel Kral
2025-04-28 13:44   ` Fiona Ebner
2025-03-25 15:12 ` [pve-devel] [PATCH ha-manager 12/15] test: ha tester: add test cases for strict positive " Daniel Kral
2025-04-28 13:51   ` Fiona Ebner
2025-05-09 11:22     ` Daniel Kral
2025-03-25 15:12 ` [pve-devel] [PATCH ha-manager 13/15] test: ha tester: add test cases for loose " Daniel Kral
2025-04-28 14:44   ` Fiona Ebner
2025-05-09 11:20     ` Daniel Kral
2025-03-25 15:12 ` [pve-devel] [PATCH ha-manager 14/15] test: ha tester: add test cases in more complex scenarios Daniel Kral
2025-04-29  8:54   ` Fiona Ebner
2025-04-29  9:01   ` Fiona Ebner
2025-03-25 15:12 ` [pve-devel] [PATCH ha-manager 15/15] test: add test cases for rules config Daniel Kral
2025-03-25 16:47 ` [pve-devel] [RFC cluster/ha-manager 00/16] HA colocation rules Daniel Kral
2025-04-24 10:12   ` Fiona Ebner
2025-04-01  1:50 ` DERUMIER, Alexandre
2025-04-01  9:39   ` Daniel Kral
2025-04-01 11:05     ` DERUMIER, Alexandre via pve-devel
2025-04-03 12:26     ` Fabian Grünbichler
2025-04-24 10:12     ` Fiona Ebner
2025-04-24 10:12 ` Fiona Ebner
2025-04-25  8:36   ` Daniel Kral
2025-04-25 12:25     ` Fiona Ebner
2025-04-25 13:25       ` Daniel Kral
2025-04-25 13:58         ` Fiona Ebner

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=28ca2817-2a17-4b67-b245-2b40462b776a@proxmox.com \
    --to=f.ebner@proxmox.com \
    --cc=d.kral@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
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal