From: Dominik Csapak <d.csapak@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>
Cc: "Jain, Piyush" <piyush.jain@hpe.com>
Subject: Re: [pve-devel] Question about Storage Plug-in and failover architecture
Date: Tue, 27 Aug 2024 13:40:12 +0200 [thread overview]
Message-ID: <73a3a8cf-0ac4-4fd4-adbe-0dd504663ac8@proxmox.com> (raw)
In-Reply-To: <mailman.323.1724157762.302.pve-devel@lists.proxmox.com>
On 8/20/24 14:07, Jain, Piyush via pve-devel wrote:
>
> Hello Team,
>
Hi, sorry for the late answer.
> I am new to the community, and I have few basic questions that I would like to clarify:
>
>
> 1. Can you share details on how to develop a storage plugin for Proxmox?)
Some information can be found here: https://pve.proxmox.com/wiki/Storage_Plugin_Development
If there is some more specific questions, you can ask here on the pve-devel mailing list
> 2. Can you also share some more details how do achieve replication of virtual machines between to different datacentres running Proxmox clusters to provide site failover?
>
currently we only support guest replication only within one cluster and only on zfs
but what do you want to achieve exactly?
with shared storage (as in, available on more hosts in the cluster simultaneously), our ha
stack can fail over the guests to other nodes in case a node looses quorum
so if your storage is 'shared', there shouldn't be anything special to be done
hope this helps
kind regard
Dominik
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
prev parent reply other threads:[~2024-08-27 11:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-20 12:07 Jain, Piyush via pve-devel
2024-08-27 11:40 ` Dominik Csapak [this message]
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=73a3a8cf-0ac4-4fd4-adbe-0dd504663ac8@proxmox.com \
--to=d.csapak@proxmox.com \
--cc=piyush.jain@hpe.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