From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <pve-devel-bounces@lists.proxmox.com>
Received: from firstgate.proxmox.com (firstgate.proxmox.com [IPv6:2a01:7e0:0:424::9])
	by lore.proxmox.com (Postfix) with ESMTPS id 3B1201FF168
	for <inbox@lore.proxmox.com>; Tue,  4 Feb 2025 13:44:51 +0100 (CET)
Received: from firstgate.proxmox.com (localhost [127.0.0.1])
	by firstgate.proxmox.com (Proxmox) with ESMTP id 71DB916246;
	Tue,  4 Feb 2025 13:44:50 +0100 (CET)
Date: Tue, 4 Feb 2025 14:44:09 +0200
To: pve-devel@lists.proxmox.com
MIME-Version: 1.0
Message-ID: <mailman.20.1738673089.293.pve-devel@lists.proxmox.com>
List-Id: Proxmox VE development discussion <pve-devel.lists.proxmox.com>
List-Post: <mailto:pve-devel@lists.proxmox.com>
From: Ivaylo Markov via pve-devel <pve-devel@lists.proxmox.com>
Precedence: list
Cc: Ivaylo Markov <ivaylo.markov@storpool.com>, nikolay.angelov@storpool.com
X-Mailman-Version: 2.1.29
X-BeenThere: pve-devel@lists.proxmox.com
List-Subscribe: <https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel>, 
 <mailto:pve-devel-request@lists.proxmox.com?subject=subscribe>
List-Unsubscribe: <https://lists.proxmox.com/cgi-bin/mailman/options/pve-devel>, 
 <mailto:pve-devel-request@lists.proxmox.com?subject=unsubscribe>
List-Archive: <http://lists.proxmox.com/pipermail/pve-devel/>
Reply-To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>
List-Help: <mailto:pve-devel-request@lists.proxmox.com?subject=help>
Subject: [pve-devel] StorPool storage plugin concerns
Content-Type: multipart/mixed; boundary="===============3491140454191923985=="
Errors-To: pve-devel-bounces@lists.proxmox.com
Sender: "pve-devel" <pve-devel-bounces@lists.proxmox.com>

--===============3491140454191923985==
Content-Type: message/rfc822
Content-Disposition: inline

Return-Path: <ivaylo.markov@storpool.com>
X-Original-To: pve-devel@lists.proxmox.com
Delivered-To: pve-devel@lists.proxmox.com
Received: from firstgate.proxmox.com (firstgate.proxmox.com [212.224.123.68])
	(using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)
	 key-exchange X25519 server-signature RSA-PSS (2048 bits))
	(No client certificate requested)
	by lists.proxmox.com (Postfix) with ESMTPS id 024F3CA5E2
	for <pve-devel@lists.proxmox.com>; Tue,  4 Feb 2025 13:44:49 +0100 (CET)
Received: from firstgate.proxmox.com (localhost [127.0.0.1])
	by firstgate.proxmox.com (Proxmox) with ESMTP id DDFEA1621E
	for <pve-devel@lists.proxmox.com>; Tue,  4 Feb 2025 13:44:18 +0100 (CET)
Received: from mail-wm1-x32e.google.com (mail-wm1-x32e.google.com [IPv6:2a00:1450:4864:20::32e])
	(using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits)
	 key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256)
	(No client certificate requested)
	by firstgate.proxmox.com (Proxmox) with ESMTPS
	for <pve-devel@lists.proxmox.com>; Tue,  4 Feb 2025 13:44:17 +0100 (CET)
Received: by mail-wm1-x32e.google.com with SMTP id 5b1f17b1804b1-4361815b96cso38210835e9.1
        for <pve-devel@lists.proxmox.com>; Tue, 04 Feb 2025 04:44:17 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=storpool.com; s=google; t=1738673050; x=1739277850; darn=lists.proxmox.com;
        h=content-transfer-encoding:organization:subject:from:cc:to
         :content-language:user-agent:mime-version:date:message-id:from:to:cc
         :subject:date:message-id:reply-to;
        bh=yFyHDuctHlinWgsN77KynwHr7pc0Q1Lyx9l1VSZRtbE=;
        b=Vgn8WeiUbcnsxQgxDWZ80UvyHb+g1t0rgNivQ4lobdHpxC/EK9HdbfGTlsXYfdpKqn
         Gt6giSU/RaPX5Jxtn6Z7wJkFoBLxXe/QRDGl4IjqO8IBQhYPy4GhLn5CZnE+eF7/abqd
         /JwitAfdX5DndcdkEBNAPcZsqKSVBn+yz0gHvxWLpp6iJ3LmYMY0fXQtVW303f8QjEzU
         a8ErPzHnSldrhiJ0fSfKeYOAgL9ueWXttFRMiOhDKAWh02cCuRlFRi6WgcKLhOGSJm9t
         2jZWqVsqwcVHdb4DsGaXCaPYw++3nWG194tGQYmJd0VZZKR7b+NlhqfDoLAzVzkYdLBP
         PF2g==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=1e100.net; s=20230601; t=1738673050; x=1739277850;
        h=content-transfer-encoding:organization:subject:from:cc:to
         :content-language:user-agent:mime-version:date:message-id
         :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to;
        bh=yFyHDuctHlinWgsN77KynwHr7pc0Q1Lyx9l1VSZRtbE=;
        b=UOp04E0OnCAPo0p8wbZzIhb5Po4aPzKo0/PtLapylMwASpya/JjYqTQzYaGneUWPxd
         WBMOp6eCBWZr6qFBew1IgN2pysVCjFuRAjFhlDfyKQUimx7LmSJ8vfzXs+i8oD+331u2
         yLQKHnu9GxeJ5MFT/aqUgiZuAjrnYooabBFA3gTWKf03oBaKDhdswFdPU6XyAXzbqAFc
         3eYOvbcMTYJ/EkEfBmev3h6fbWSACCHeljIIOy6HGoaG5al046g0x/SrMcDjWoMoTdQq
         1bMU0cPMzkYecfaKaIGWkiHPt1Wk5wUfIvpe1GhabnZO3ujCTFUR9ieAEnOkQM7sd2tD
         s4eQ==
X-Gm-Message-State: AOJu0YxOZ890Uk1Kx4X17U8hwgg/JgI2pHVrqdg+qMW7kV+dp8RIL8OI
	ja/QQPrBrG2+sD/37uSU/ziQFBC4QgWJ+Xviy5Gjl8iehrv0P/b1pHjP6tWUA0HYcaDOUhYtLjx
	DDlM=
X-Gm-Gg: ASbGncuyrBWAFEpiI+uIcjt87KjN9Mu2efKolcy1UBvlY9jSo42dn86KmpeAkZ5HSgj
	6oj9g143D/vK15hgb3Ajen9GtkTxGiddU/+NllMRzK/JQx7qLMcF/fKD1HTKTFgtxqMYr/0ZoNn
	iTUQr+s5YTOmh4G403p4Vs8MpfaRoBcbtcA5Ih2JLTIJp3smnh2HERKkUShOabws/LLnf6fpIcO
	CAm2IreDAwhloo6w/lsWxFXAeKt7VbkLQW+FA0CcB/fGGLGf9cCN6l08qflaFJB38EJ3EvPygqV
	nMW7KHx9HyRzHI2HgAcenVydWwULUF56RZ7Rku54ji63UMaEOfwCXDaiRbcY0R7U
X-Google-Smtp-Source: AGHT+IGWkbJ9mN4/vaREHnFMVk95STp51rH1fvoLOl6pGpHXPSEKekSNp1cdIuXvi9F1D74Fhz6CvQ==
X-Received: by 2002:a05:600c:190e:b0:434:f2f4:4c07 with SMTP id 5b1f17b1804b1-438dc3c820bmr230625595e9.15.1738673050422;
        Tue, 04 Feb 2025 04:44:10 -0800 (PST)
Received: from ?IPV6:2001:67c:21bc:e:796b:85b4:3761:7320? ([2001:67c:21bc:e:796b:85b4:3761:7320])
        by smtp.gmail.com with ESMTPSA id 5b1f17b1804b1-438e244ecd6sm193499965e9.28.2025.02.04.04.44.09
        (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128);
        Tue, 04 Feb 2025 04:44:10 -0800 (PST)
Message-ID: <26d735ba-da13-4501-8eae-f7e978410c8a@storpool.com>
Date: Tue, 4 Feb 2025 14:44:09 +0200
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
Content-Language: en-US
To: pve-devel@lists.proxmox.com
Cc: nikolay.angelov@storpool.com
From: Ivaylo Markov <ivaylo.markov@storpool.com>
Subject: StorPool storage plugin concerns
Organization: StorPool Storage
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-SPAM-LEVEL: Spam detection results:  0
	AWL                     0.000 Adjusted score from AWL reputation of From: address
	BAYES_00                 -1.9 Bayes spam probability is 0 to 1%
	DKIM_SIGNED               0.1 Message has a DKIM or DK signature, not necessarily valid
	DKIM_VALID               -0.1 Message has at least one valid DKIM or DK signature
	DKIM_VALID_AU            -0.1 Message has a valid DKIM or DK signature from author's domain
	DKIM_VALID_EF            -0.1 Message has a valid DKIM or DK signature from envelope-from domain
	DMARC_PASS               -0.1 DMARC pass policy
	RCVD_IN_DNSWL_NONE     -0.0001 Sender listed at https://www.dnswl.org/, no trust
	SPF_HELO_NONE           0.001 SPF: HELO does not publish an SPF Record
	SPF_PASS               -0.001 SPF: sender matches SPF record

Greetings,

I was pointed here to discuss the StorPool storage plugin[0] with the 
dev team.
If I understand correctly, there is a concern with the our HA watchdog 
daemon, and I'd like to explain the why and how.

As a distributed storage system, StorPool has its own internal 
clustering mechanisms; it can run
on networks that are independent from the PVE cluster one, and thus 
remain unaffected by network
partitions or other problems that would cause the standard PVE watchdog 
to reboot a node.
In the case of HCI (compute + storage) nodes, this reboot can interrupt 
the normal operation of the
StorPool cluster, causing reduced performance or downtime, which could 
be avoided if the host is not restarted.
This is why we do our best to avoid such behavior across the different 
cloud management platforms.

Currently, when our daemon detects an unexpected exit of a resource 
manager, it will SIGKILL PVE
HA services and running VMs on the node, which should prevent 2 
instances of the same VM running at
the same time. PVE services and our block storage client daemon are 
restarted as well.

We're open to discussion and suggestions for our approach and 
implementation.

[0] https://github.com/storpool/pve-storpool

-- 
Ivaylo Markov
Quality & Automation Engineer
StorPool Storage
https://www.storpool.com



--===============3491140454191923985==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

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

--===============3491140454191923985==--