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)) (No client certificate requested) by lists.proxmox.com (Postfix) with ESMTPS id B1908744EB for ; Thu, 8 Jul 2021 22:22:15 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id A44661CB8B for ; Thu, 8 Jul 2021 22:22:15 +0200 (CEST) Received: from mail-ej1-x636.google.com (mail-ej1-x636.google.com [IPv6:2a00:1450:4864:20::636]) (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 C59111CB75 for ; Thu, 8 Jul 2021 22:22:13 +0200 (CEST) Received: by mail-ej1-x636.google.com with SMTP id i20so11885575ejw.4 for ; Thu, 08 Jul 2021 13:22:13 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=odiso-com.20150623.gappssmtp.com; s=20150623; h=message-id:subject:from:to:date:in-reply-to:references:user-agent :mime-version; bh=DtRdlsjX44sThBokRZ931Amm47QlvV1U6mRWDoujJfU=; b=h8XCpSDydLYtbf0LbDx6IYENCiK5H01V29hPIEKW+Vc+oTtfpA5l6VqYaJubpdNExO /+xR9Q53bYFWzhwfA/YM86xsEhTBdPIC+n2eyAg2dS3p0D85vPJ+pyvLkVrG4btwovop +wbL6nKzYUG0cdHtA9kkva0/4jE20DwbfXM4C8D+evxIXjbc5kVcwKJlY2xC3mwyLtI2 juaSSZvhIM473mho5jaSYpWBhWKT0svgtEIPDEAz98HPoHvWzkjykgvVW87cZcpH1Gq8 uL7bQWlkzFMrsPH2JMZ4nNRymrEbkO7xuh3uSS2ytzxpTF9i6IdQdvMxfD9dIIOqSUU4 n6kg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:message-id:subject:from:to:date:in-reply-to :references:user-agent:mime-version; bh=DtRdlsjX44sThBokRZ931Amm47QlvV1U6mRWDoujJfU=; b=Qi+dDVrHEzXOk/RSYRFHdQAC8WBw/PZO4rz/e49AFlhegNB1bWb2W1sMIBUoqtW9BY XeU5k6BmqS1WnMhL7jUHrix+h/EG22y44UEGk6BbS79RVO5s/a5KJEAVmQTr6vzg9A/u A8qqQNppIwNNiRVPjHevQ/DqJh/RoCNG7YN96DynN5IF7xHZkFr7jjYcArIZYUoGjxdy wGBJU03nPaVOeJVz4UFHYA6gOPFsn1yvMDYCe4Ex9l38pEjjo2pM5nYtZ5ZXjBHdwM76 fIaluxPB6cb3/hsFsFY9trLWgrelFSoHU8khXiLxODhsUDJ2Z4+cVRTTNxdwmaMdIHgW /YBg== X-Gm-Message-State: AOAM532h2712vTlKUYPIjQcwVgt2/VJhFgsEx8oTj4LPKCLbbCW9MtJ5 23AgcaHEDQ9a8lEW+NZvPgeoy3fAB/Uz2ihHYXA= X-Google-Smtp-Source: ABdhPJx0VMFg85aEi7wEQ2ZTu4FfVG2aBKQwbwvJISJyn10zzpCBruNkLuX9kdqOu5t0ixzOsCfFEQ== X-Received: by 2002:a17:906:51d4:: with SMTP id v20mr13053416ejk.107.1625775727220; Thu, 08 Jul 2021 13:22:07 -0700 (PDT) Received: from [192.168.178.50] ([79.132.252.54]) by smtp.gmail.com with ESMTPSA id c1sm1825905edt.18.2021.07.08.13.22.06 for (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Thu, 08 Jul 2021 13:22:06 -0700 (PDT) Message-ID: <8242aca652161e867154eba4f9b5a65fa2ee9298.camel@odiso.com> From: alexandre derumier To: Proxmox VE user list Date: Thu, 08 Jul 2021 22:22:06 +0200 In-Reply-To: References: User-Agent: Evolution 3.40.2 MIME-Version: 1.0 X-SPAM-LEVEL: Spam detection results: 0 AWL 0.905 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 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" Content-Transfer-Encoding: 8bit X-Content-Filtered-By: Mailman/MimeDel 2.1.29 Subject: Re: [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: Thu, 08 Jul 2021 20:22:15 -0000 Le jeudi 08 juillet 2021 à 10:40 +0300, Alex K a écrit : > > - 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). Hi, I hade done some prelimary code with dotpro scheduling algorithm, but I never have time to finish it https://github.com/aderumier/pve-ha-balancer I need to finish the streaming/rrd of pressure counters, to have good values for vm/ct real cpu/mem usage on the host side. I'll try to rework on it in september, but I'm a lot busy with sdn ipam currently for vm/ct ips allocation.