[Feature Request] Wishlist Collection for PVE 2

[WonkyPie]

Hello,
since I couldn't find any active and up-to-date wishlist for PVE 2, I decided to create one.
So far, two (minor) wishes came up:

• I would like to store the webinterface user and password in my browser, but for some reason, it does not offer to save it. (Tested with Firefox and Chrome) (Or is that intended behaviour?)
• The new VNC console seems to be starting significantly slower than the 1.x console, it says "Status:X509Plain" for several seconds. Usually no big deal, but it can be annoying if you're in a rush.

You are welcome to add more requests/wishes
Greetings,
WonkyPie

 

[m.ardito]

well i did one in the past!

http://pve.proxmox.com/wiki/Wishlist

i think nobody ever noticed it :-D

maybe can we make an "official" one and join ideas/wishes to help pve team sort out?

what users/team think?

Marco

 

[emanuelebruno]

well i did one in the past!
[...]Marco

Hi Marco, nice to meet you? are you italian?
Sincerely,
Emanuele.

 

[m.ardito]

si di torino, tu?

"meet" è probabilmente eagerato... :-D

ma il forum è in inglese

--------------

yes from turin, and you?

"meet" is probably too much, here :-D

but this is an english-based forum

Marco

 

[emanuelebruno]

ciao Marco, io sono di Catania. E' da un pò che sto lavorando sotto proxmox e che bazzico questo forum. Sul mio sito ho cominciato a mettere un pò di materiale e se vuoi darci un'occhiata questo è il link http://emanuelebruno.it/ ; nel frattempo ti do anche qualche link più specifico su alcuni argomenti che sto sviluppando :

- http://emanuelebruno.it/forum/topic.php?id=320#post-534 una raccolta di faq per proxmox
- http://emanuelebruno.it/forum/topic.php?id=319#post-533 qualche punto di partenza per realizzare un firewall o un sistema minimo di protezione
- http://emanuelebruno.it/forum/topic.php?id=324#post-539 qui do qualche accenno per installare elastix su Proxmox (openvz)

Domani ritirerò un paio di microserver dell'hp su cui vorrei installare proxmox in configurazione cluster (vorrei sperimentare il live-migration tra due sedi remote) e mi piacerebbe tanto trovare qualcuno con cui collaborare magari per scrivere qualche guida dettagliata sul mio blog.

A presto.

----
HI Marco, I live in Catania. I'm very new to proxmox (only 2 months) and I like this forum. In my website you can find some arguments about proxmox and if you want feel to take a look to this link http://emanuelebruno.it/ ; in the mean time I have choosen for you three links about proxmox :

- http://emanuelebruno.it/forum/topic.php?id=320#post-534 this is a proxmox f.a.q. collection
- http://emanuelebruno.it/forum/topic.php?id=319#post-533 in this post I try to give some istructions for installing a firewall or configure fail2ban
- http://emanuelebruno.it/forum/topic.php?id=324#post-539 in this post I try to explain how to install elastix on proxmox (openvz)

Tomorrow I'll buy 2 hp microserver and it is my intention to install proxmox in cluster configuration (I want to try the livemigration between two different location with an ADSL connection) and I'd like to meet somebody to share some experience and for writing some detailed guide on my blog.

See you soon (is probably too much, here :-D )

 

[tin]

OK, here's my requests. First one is something that really bugs me, but the rest are just low grade feature requests.

• Ability to save password in browser (as OP requested). Or a "remember me" tickbox. Perhaps this should be a server-side option to prevent password saving in larger enterprises...
• Save the view for the left hand column. I prefer the folder view for some reason, but it defaults back to server view each time I log back in.
• Sort VMs in "server view" by VMID only, allowing VZ and KVM machines to mix. For example, I have a mix of VZ and KVM machines that are higher importance than some others. I've numbered the low importance ones starting at 200, while high importance VMs start at 100. But currently this has low priority VZ machines above high priority KVM machines in server view. This seems to make no sense since people preferring to separate KVM and VZ machines can simply switch to folder view.
• Option to start a restored VM automatically when restore completes. I rarely need to make changes to restored VMs, and if they're measured in GBs, I tend to go off and do something else while it restores. Starting automatically would save me some effort.

I was going to tidy up the wiki wishlist and put these there, but it appears to require separate registration and manual activation - too hard.

 

[svendsen]

I also want to add a few wishes
I think in general I only want diff backups and replicated storage (ceph/sheepdog/gluster). But there are also space for lot of web interface improvements:

- Ability to add existing disk images to VMs
- Ability to resize disks
- Ability to see disk size
- Ability to see ip adress
- VM/CT Startup priority list
- VM/CT Shutdown strategy (like VMware where you can choose that all VMs shall shutdown or suspend when hypervisor is rebooting/shutting down)
- KVM templates (at some point doable by backup/restore today)
- VM cloning (at some point doable by backup/restore today)
- VM snapshots (at some point doable by backup/restore today)

 

[tom]

I also want to add a few wishes
I think in general I only want diff backups and replicated storage (ceph/sheepdog/gluster).

ceph is already in, work in progress (see git).

But there are also space for lot of web interface improvements:

- Ability to add existing disk images to VMs
- Ability to resize disks
- Ability to see disk size
- Ability to see ip adress

all this works already for CT´s. for KVM guests its not that trivial as it depends on the guest, make it impossible in some cases.

- VM/CT Startup priority list
- VM/CT Shutdown strategy (like VMware where you can choose that all VMs shall shutdown or suspend when hypervisor is rebooting/shutting down)

available since 2.1, seems you missed it. http://pve.proxmox.com/wiki/Virtual_Machine_Startup_and_Shutdown_Behavior

 

[dietmar]

I think he meant the 'suspend to disk' feature on shutdown.

 

[svendsen]

ceph is already in, work in progress (see git).

Yes I know, I'm actually testing it - but it can still be on my wishlist, can't it?

all this works already for CT´s. for KVM guests its not that trivial as it depends on the guest, make it impossible in some cases.

Yes, I know it already works for CT's. I cannot see which point is impossible to make? Fx the ip adress is just a matter of a small startup script that executes URI/API to update Proxmox with ip adress and other info

available since 2.1, seems you missed it. http://pve.proxmox.com/wiki/Virtual_Machine_Startup_and_Shutdown_Behavior

You are right, my fault, didn't think

 

[svendsen]

I think he meant the 'suspend to disk' feature on shutdown.

Yeah, well I meant a general shutdown strategy, which is actually now available from 2.1 - but a suspend to disk feature would also be nice!

 

[starnetwork]

My Suggestions:
1. add "Resource Adviser" that check how many machines the server can run and the correct usage
It should be based on CPU usage, available memory, Machine types (KVM / OpenVZ), Disk space, and server I/O
and introduce the bottleneck in terms of resources

2. simple, add restart option to OpenVZ Machines over GUI.

Best Regards,
Star Network.

 

[m.ardito]

wouldn't it be great to have just one single wiki place for wishlists? like http://pve.proxmox.com/wiki/Wishlist
there pepole could then see if any wish has been approved, rejected or maybe already implemented and pointed to the right wiki place...

or at least make a "whishlist" sticky post...

Marco

 

[tom]

we have already a roadmap, showing what is coming next. if someone want to develop enhancements, we have a developer list for this.

and if some wants paid development, just contact office@proxmox.com and our team can discuss this directly.

 

[m.ardito]

we have already a roadmap, showing what is coming next. if someone want to develop enhancements, we have a developer list for this.
and if some wants paid development, just contact office@proxmox.com and our team can discuss this directly.

Tom, i'm sure you know that a wishlist is another thing, it's not "what we are doing/what we will be doing next" that is a roadmap.
a wishlist it's what users (and possibly many of them) would like to see next if it's not already in the roadmap. maybe they have no money to sponsor that, but a wish costs nothing, and may never come true. ideally a wish (in the wishlist) will be rejected, kept there forever or moved to the roadmap by developers.

if someone pays for his wish, and you prioritize that, it's obviously ok, but with an official wishlist it could happen that someone see a good idea there, and says , "hey, good idea, i could sponsor or contribute (money, code, time, efforts) to that!"

otherwise it could be seen as:
<<we develop anything people is paying for, other than that, we develop just what we think it's useful to have, and don't care particularly about nonpaying user's wishes>>

that said, since you developed this wonder, and everybody knows its a really useful, excellent and generous work, you can do whatever you want, but regular users may have good ideas on new features that could be shared with others, and that could start a discussion about that features, i think this. i just think that forum posts here and there are a wrong method for this, a wiki wishlist could be a good place where pve developers could "approve" some good ideas started from the forums before they will put (if ever) it in the roadmap, being sponsored by someone or not.

my 2c,
Marco

 

[martin]

New ideas are welcome. But this must be discussed, filtered. We think this is best done in this discussion forum and/or the mailing lists.

Based on this, it will finally go to the product. We also have a list of possible enhancements in our bugzilla.

So there are plenty of ways to discuss and share ideas, so I doubt that introducing more and more lists does help here (just increase work).