From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: 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) server-digest SHA256) (No client certificate requested) by lists.proxmox.com (Postfix) with ESMTPS id 2C0AC73513 for ; Tue, 6 Jul 2021 11:00:40 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 2050027353 for ; Tue, 6 Jul 2021 11:00:40 +0200 (CEST) Received: from mail-ua1-x92d.google.com (mail-ua1-x92d.google.com [IPv6:2607:f8b0:4864:20::92d]) (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 id 8B6D827340 for ; Tue, 6 Jul 2021 11:00:39 +0200 (CEST) Received: by mail-ua1-x92d.google.com with SMTP id f34so8016370uae.4 for ; Tue, 06 Jul 2021 02:00:39 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=wm3nflc1IWVZFt+NN8ys4YE/qF+lKJOH+S9uUrR+D3c=; b=ZPZgOQhmnWA5RFTGvs9XMHtnH9Wwe1vyQjVY1DDzItSsFuaZ7aU8rXD9Y0puKbtwG7 ajAdy6lSR1IZDL6aVE6qB5ZhKE1qdPBuQynYqj72JR97yZuny5loCpOwx3yiUeS6ZQAI F0fJbw3PeZOofGIHaAryo2S/yBsZNfI/Ih3HBwlbMMh8cBuZFJnwhfLFwJF/PWr6857S lqY//7FmBwI3Yk64R/mpRbR6AMEoDsDuru9QMc17Ud3arG1o17UYYrEC2lBN35sXFVa8 cWN0T+Owak910FD5XbTVemCteIXuy3JUOVuPQ+m7pSSD/61W8U5RyN7lIzXcuqTAUZ3c v2wA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=wm3nflc1IWVZFt+NN8ys4YE/qF+lKJOH+S9uUrR+D3c=; b=qRNSHefEULrDm4c3qWGlnOYpgKVGIKzH8AvNavtAm1IRxvjEb9XKT3OQblf2qJDhez 7N6eyhgvm1KiYZbUrCyZ7boOdvO8cS/ixVTjy+WC9Hlz9TGL+cYIRd8AaNXnyQuxW0tn 5W562hQoD+DbNDanaUAAeXeBMGsA7K/Km1KggDlCcytvdLkaTqO50+vV7s/jQ69MsjGC WcoDKXg5zDq+NVGG1puEjLg7n9DFm8r8+2kw6e614lTsTJtiW7SZ1l5aNLTMN4Pfdwz/ O4exWXsXnW7HCmV+cx92TBqnAdpgeQdSxdLMwWQaqgfUbPnBjeW/s5z4+s6jhQ9Ijse8 icuA== X-Gm-Message-State: AOAM531d66hItZQx+15WZxMeVfbzun/EjfX/brzy/ZamynlLB+AmVMdr l05E1bX5zfvKN2PmB+/H04ffs2HOUMfxeAW8XfnZsAkv0Q== X-Google-Smtp-Source: ABdhPJxuTnV2oEga3Ox/RZcfNeCKf3FeEmP/jxHSunW0ugTQmPxX8gLL/95bVl83dAuu6g64E9F99C4ehq9cJBP4RPw= X-Received: by 2002:a9f:23d1:: with SMTP id 75mr14819244uao.99.1625562030931; Tue, 06 Jul 2021 02:00:30 -0700 (PDT) MIME-Version: 1.0 From: Alex K Date: Tue, 6 Jul 2021 12:00:19 +0300 Message-ID: To: Proxmox VE user list X-SPAM-LEVEL: Spam detection results: 0 AWL 0.033 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 FREEMAIL_FROM 0.001 Sender email is commonly abused enduser mail provider HTML_FONT_FACE_BAD 0.001 HTML font face is not a word HTML_MESSAGE 0.001 HTML included in message 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 Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.29 Subject: [PVE-User] Proxmox questions/features X-BeenThere: pve-user@lists.proxmox.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: Proxmox VE user list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 06 Jul 2021 09:00:40 -0000 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