From: "DERUMIER, Alexandre" <alexandre.derumier@groupe-cyllene.com>
To: "pve-devel@lists.proxmox.com" <pve-devel@lists.proxmox.com>
Cc: "daniela@proxmox.com" <daniela@proxmox.com>,
"contact@gilouweb.com" <contact@gilouweb.com>
Subject: fosdem feedback
Date: Thu, 12 Feb 2026 08:19:45 +0000 [thread overview]
Message-ID: <f70be20c0ac8de7fba1cb4a2e088024c646aa8e4.camel@groupe-cyllene.com> (raw)
Hi everybody,
sorry to be late but I was super busy at work after the Fosdem.
I would like first to thanks the proxmox teams && proxmox users
community for the help for the stand, this year was even more crazy
than last year !
I don't known if they was more people or maybe it was because we were
in the main building, but we don't have stopped all the weeks.
Maybe thanks to Fiona too for the Austrian biscuits ;)
Thanks to Gilou && Francois-Xavier !
Thanks to Pietro for helping too during the lunch time !
So about the stand:
We didn't have enough stickers as usual , maybe more XL t-shirt size
for next year could be great too. (less XS size too, sysadmins are
generally is little big ^_^ )
We had a lot of thank you from proxmox users, so I'm forwarding the
thanks you to all proxmox developpers !
A lot of people already known Proxmox (more than last year),
a lot of people are looking to migrate from vmware too (thanks broadcom
) and also sovereignty was the big topic this year (thanks Trump ;)
Big companies, smaller companies, homelabers, public institutions,...
People had a lot of feature requests too, here the main requests I'm
remembering:
- cross cluster vm replication for Disaster recovery (zfs, ceph for
now. qcow2 snap in the future if possible) --> this one was the more
requested
- better backup scheduling (currently a planned backup is launched on
all nodes at same time pushing too much network load, and it's
difficult to do node by node sequentially without an external
scheduling with script)
- pool quota / tenant quota. (user can't create more than total vm
cpu/ram/disk on the pool)
- auto snapshot schedule
- vm load balancing (people coming from vmware want DRS)
- nodes rolling update for the whole cluster
- basic alerting on ressources (cpu,ram,....)
- user self service portal
- vdi portal
Thanks you again for the help, and see you next year ! (or maybe at
Tuxis proxmox days, or another conference )
Alexandre
(BTW, can you send me the picture we have taken with the whole team ? )
next reply other threads:[~2026-02-12 8:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-12 8:19 DERUMIER, Alexandre [this message]
2026-02-12 12:20 ` François-Xavier Guidet
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=f70be20c0ac8de7fba1cb4a2e088024c646aa8e4.camel@groupe-cyllene.com \
--to=alexandre.derumier@groupe-cyllene.com \
--cc=contact@gilouweb.com \
--cc=daniela@proxmox.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