From mboxrd@z Thu Jan 1 00:00:00 1970
Return-Path: <t.lamprecht@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 1D9AF7102D
for <pve-devel@lists.proxmox.com>; Thu, 23 Jun 2022 12:59:46 +0200 (CEST)
Received: from firstgate.proxmox.com (localhost [127.0.0.1])
by firstgate.proxmox.com (Proxmox) with ESMTP id 1502F2520B
for <pve-devel@lists.proxmox.com>; Thu, 23 Jun 2022 12:59:46 +0200 (CEST)
Received: from proxmox-new.maurer-it.com (proxmox-new.maurer-it.com
[94.136.29.106])
(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 firstgate.proxmox.com (Proxmox) with ESMTPS id 953F625270
for <pve-devel@lists.proxmox.com>; Thu, 23 Jun 2022 12:59:44 +0200 (CEST)
Received: from proxmox-new.maurer-it.com (localhost.localdomain [127.0.0.1])
by proxmox-new.maurer-it.com (Proxmox) with ESMTP id 6343143C1A;
Thu, 23 Jun 2022 12:59:44 +0200 (CEST)
Message-ID: <3ab98c32-e9d6-f37f-8e8c-858a1e6d0c86@proxmox.com>
Date: Thu, 23 Jun 2022 12:59:42 +0200
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101
Thunderbird/102.0
Content-Language: en-GB
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
"DERUMIER, Alexandre" <Alexandre.DERUMIER@groupe-cyllene.com>
References: <e5da5f421d7b9ec06ede9bfa6228c3e80010328b.camel@groupe-cyllene.com>
From: Thomas Lamprecht <t.lamprecht@proxmox.com>
In-Reply-To: <e5da5f421d7b9ec06ede9bfa6228c3e80010328b.camel@groupe-cyllene.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-SPAM-LEVEL: Spam detection results: 0
AWL 0.004 Adjusted score from AWL reputation of From: address
BAYES_00 -1.9 Bayes spam probability is 0 to 1%
KAM_DMARC_STATUS 0.01 Test Rule for DKIM or SPF Failure with Strict Alignment
NICE_REPLY_A -0.001 Looks like a legit reply (A)
SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record
SPF_PASS -0.001 SPF: sender matches SPF record
T_SCC_BODY_TEXT_LINE -0.01 -
Subject: Re: [pve-devel] proxmox French days conference feedback
X-BeenThere: pve-devel@lists.proxmox.com
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Proxmox VE development discussion <pve-devel.lists.proxmox.com>
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/>
List-Post: <mailto:pve-devel@lists.proxmox.com>
List-Help: <mailto:pve-devel-request@lists.proxmox.com?subject=help>
List-Subscribe: <https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel>,
<mailto:pve-devel-request@lists.proxmox.com?subject=subscribe>
X-List-Received-Date: Thu, 23 Jun 2022 10:59:46 -0000
Hi,
Am 23/06/2022 um 10:43 schrieb DERUMIER, Alexandre:
> So the conference was a success.
> Overall experience with proxmox VE/PBS is really good.
> Nobody had serious problem with PVE/PBS.
>=20
> Some are coming from openstack (too big, too complex to manage)
> Some others are coming from vmware.
> Some others are using proxmox since 0.9 =F0=9F=98=89
> Some return of experience with ceph too. (with some problems).
>=20
>=20
Thanks for the feedback and talking about Proxmox projects!
> Maybe for the most requested missing features:
>=20
> - cross cluster management + replication/disaster recovery. (They have=
> a lot of dual room / dual site. But 3 sites to keep quorum is not
> always possible)
That's in the pipeline, cross cluster migration is not that far off and F=
abian
should be soon able to pick that up (he works on some infrastructure proj=
ects
currently to make air-gapped offline updates possible in a relatively eas=
y and
integrated way), that's one of the biggest pre-requisites left.
>=20
> - a drs feature like vmware for vm balancing=C2=A0
> (I'm still working on it, I'll try to have a working after this summer.=
> I still need vm pressure stats pending patches apply first =F0=9F=98=89=
I'd really like to more actively work on this from our part too, I though=
t about
7.3 feature planning a bit yesterday and wrote a few (rough) edge points=
for
tackling this, using the alogrithm and rough direction you already worked=
on in
your proof of concepts (thx!):
- [ ] Static (and later Dynamic) Resource Scheduling (S/DRS)
- [ ] Coordinate with Alexandre as he's working partly on that too, b=
ut we
may want to use a bit of a different design and/or feature set =
(at
least initially) and integration timeline
- [ ] checkout TOPSIS more closely and implement relevant parts in ru=
st to
expose via perlmod, that's then fast and much easier to reason
correctness in static, and safety focused language like rust.
- [ ] Make basic static resource capacity like CPU (# of socket, core=
and
hyper threads) and memory available for other cluster nodes (fo=
r
example, via kv_broadcast after (re)start of pve-cluster)
- [ ] Add infrastructure to use that static (!) information for balan=
cing
out the cluster.
- [ ] spit out a list of actions that would result in a balanced
cluster: migrate guest A to node X, migrate guest B to node=
Y
- [ ] use that for creating a simulation and regression testing s=
ystem
in the spirit of the ha-managers simulation and regression =
test
system, but as independent test & executable
- [ ] integrate in HA, due to static-ness and safe-and-slow integrati=
on it
should be first only be done on recovery, for better balancing =
out.
- [ ] add API create support for creating a CT/VM to the best fitting=
node,
i.e., the lowest used one
- [ ] make balancing algo available for non-ha too, allow a cluster w=
ide
manual re-balance (e.g., with action-proposal shown to user for=
confirmation)
- [ ] Extend with dynamic information like IO/memory/CPU pressure
- [ ] Finally: Allow to opt-in in periodic auto-balancing for HA mana=
ged
IMO the semi-static resource availability and usage would be nice in gene=
ral as
first step, that could then also allow one to relatively easily pre-error=
/warn out
on VM start if there won't be enough memory available (maybe overridable =
for odd
zram/KSM cases, or when one just doesn't want to care about that and like=
s OOMs ;)
>=20
> - Pool quota (restrict the total mem/cpu/disk allocated to all vms in a=
> pool). as they have some clusters shared between differents
> departements / students/ ...
>=20
It'd need a bit new infrastructure, but it wouldn't be /that/ hard to imp=
lement.
>=20
> A big thanks to Daniela for the T-shirts and other goodies !
>=20
> Also, another recurrent question:
>=20
> "Why proxmox team is not more present on differents events/conference=20
> like fosdem, ... ?"
>=20
Some colleagues frequent fosdem, but in the last two and a half years doi=
ng
or attending presence conferences was a bit difficult.
> Yes, we would like to drink some beers with you guys =F0=9F=98=89
Would be nice! :-)