From: Alex K <rightkicktech@gmail.com>
To: Proxmox VE user list <pve-user@lists.proxmox.com>
Subject: Re: [PVE-User] Proxmox questions/features
Date: Thu, 8 Jul 2021 10:40:01 +0300 [thread overview]
Message-ID: <CABMULtL50PNMjqe8+7DNh0P3k5Zf27_hFMYq2-voL1V0g1xw2A@mail.gmail.com> (raw)
In-Reply-To: <CABMULt+xJYXFcV41seOqGrAz-5yjWr2NpUcA3hUxh0k3zJ5uaw@mail.gmail.com>
Hi all,
Anyone has any info to share for the below?
Many thanx
On Tue, Jul 6, 2021 at 12:00 PM Alex K <rightkicktech@gmail.com> wrote:
> Hi all,
>
> I've been assessing Proxmox for the last couple of days, coming from a
> previous experience with oVirt. The intent is to switch to this solution if
> most of the features are covered.
>
> The below questions might have been put again, though searching the forum
> or online I was not able to find any specific reference or not sure if the
> feedback is still relevant.
>
> - When adding a gluster volume I see that the UI provides an option for a
> secondary server. In case I have a 3 replica glusterfs setup where I need
> to add two backup servers as below, how can this be defined?
>
> backup-volfile-servers=node1,node2
>
>
> - I've read that qemu does use *libgfapi* when accessing VM disks on
> glusterfs volumes. Can someone confirm this? I tried to find out the VM
> configs that may reference this detail but was not able to do so.
>
> - I have not seen any *load balancing/scheduling* feature being provided
> and looking through the forum it seems that this is still missing. Is there
> any future plan to provide such a feature. By load balancing I mean to
> automatically balance VMs through the available hosts/nodes depending on a
> set policy (CPU load, memory load or other).
>
>
> Thanx for reading and appreciate any feedback,
>
> Alex
>
>
>
>
next prev parent reply other threads:[~2021-07-08 7:40 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-06 9:00 Alex K
2021-07-08 7:40 ` Alex K [this message]
2021-07-08 7:54 ` Alex K
2021-07-08 11:39 ` Lindsay Mathieson
2021-07-08 13:53 ` Alex K
2021-07-08 20:22 ` alexandre derumier
2021-07-09 8:16 ` Mark Schouten
2021-07-11 23:01 ` alexandre derumier
2021-07-14 12:44 ` Alex K
2021-07-20 10:56 ` Alex K
2021-07-20 11:45 ` Gilberto Ferreira
2021-07-20 13:01 ` Alex K
2021-07-20 14:01 ` Alex K
2021-07-24 11:29 ` Alex K
2021-07-24 12:07 ` Gilberto Ferreira
2021-07-09 13:54 ` Alex K
2021-07-08 11:33 ` Lindsay Mathieson
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=CABMULtL50PNMjqe8+7DNh0P3k5Zf27_hFMYq2-voL1V0g1xw2A@mail.gmail.com \
--to=rightkicktech@gmail.com \
--cc=pve-user@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