Some ideas for the Roadmap

[/dev/null]

Hi,

I'm now using Proxmox for nearly 2 years (since the beginning of the project). I'm using it daily, at work and at home.

Some features that I would like probably to see in future versions:

1. Integration of backup-restore in the GUI
2. Snapshotting of containers & VMs (GUI integrated)
3. Cloning containers & VMs from the GUI (probably creating templates using the GUI)
4. Define advanced parameters of backups jobs - I'm thinking of parameters such as bwlimit and maxfiles (see http://wiki.openvz.org/Backup_of_a_running_container_with_vzdump#Synopsis)

I know all this could be done using the Shell and custom scripts but I think these features would push Proxmox VE again more at the top compared to other virtualization environments.

 

[jncnath]

+1

I'm in full agreement with your suggested enhancements.

 

[tom]

Hi,

I'm now using Proxmox for nearly 2 years (since the beginning of the project). I'm using it daily, at work and at home.

Some features that I would like probably to see in future versions:

1. Integration of backup-restore in the GUI
2. Snapshotting of containers & VMs (GUI integrated)
3. Cloning containers & VMs from the GUI (probably creating templates using the GUI)
4. Define advanced parameters of backups jobs - I'm thinking of parameters such as bwlimit and maxfiles (see http://wiki.openvz.org/Backup_of_a_running_container_with_vzdump#Synopsis)

I know all this could be done using the Shell and custom scripts but I think these features would push Proxmox VE again more at the top compared to other virtualization environments.

ad 2:
pls explain in detail what you mean with "snapshotting", describe functionality and think of KVM and our storage model, and also OpenVZ

ad 3:
cloning is a quite risky task regarding security and VERY OS dependent - so this means it will not be possible - or do I miss a simple approach?

 

[yatesco]

ad 3:
cloning is a quite risky task regarding security and VERY OS dependent - so this means it will not be possible - or do I miss a simple approach?

Even if snapshotting the entire VM is dangerous it would be convenient to be able to define templates that default values for the 'create' page. For example, I find myself creating lots and lots of Ubuntu 10.4 KVM machines with 8GB of disk, 512 of RAM, the same vmbrX and attached to the install ISO. Once I have booted I then supply a command line parameter to the kickstart file (or would once I can get the thing to work!). I cannot use OpenVZ because of Java issues (or rather my issues getting Java to work with OpenVZ ).

In ESXi I create a VM as normal, start it up, enter the command line parameter and then snapshot it. This is perfectly safe and is actually quite a time saver. To install a new "testing" machine I right click the "testing-template" and select "Deploy". I have another template for each of the other VLANs I have.

Sure - I still need to install the actual OS but it does save time and reduces the opportunity of error.

 

[tom]

Even if snapshotting the entire VM is dangerous it would be convenient to be able to define templates that default values for the 'create' page. For example, I find myself creating lots and lots of Ubuntu 10.4 KVM machines with 8GB of disk, 512 of RAM, the same vmbrX and attached to the install ISO. Once I have booted I then supply a command line parameter to the kickstart file (or would once I can get the thing to work!). I cannot use OpenVZ because of Java issues (or rather my issues getting Java to work with OpenVZ ).

In ESXi I create a VM as normal, start it up, enter the command line parameter and then snapshot it. This is perfectly safe and is actually quite a time saver. To install a new "testing" machine I right click the "testing-template" and select "Deploy". I have another template for each of the other VLANs I have.

Sure - I still need to install the actual OS but it does save time and reduces the opportunity of error.

yes, an OS independent approach will be a better way.

 

[m.ardito]

I think everyone would love easing/automating the vm admin task of replicating the same base vm again and again, me too.

But IMHO every cloning solution has to cope with the fact that each vm is supposed to be unique, i.e. to have unique
- SID (win machines),
- SSH keys,
- hostnames,
- IPs,
- MAC addresses, and so on.

Of course you can restore PVE vm as another VMID and then change everything in order to make the new vm unique but i don't know how other hypervisors (esxi) do that "easily", on each OS.

How do openvz appliances create the 'uniquity' each time they're used to create a new vm? Is there a "run at first boot" script that does that?

On windows systems, it is unclear if a duplicate SID is always a real problem, probably the best way would be use Sysprep probably (see http://blogs.technet.com/b/markrussinovich/archive/2009/11/03/3291024.aspx)

Marco

 

[tom]

I think everyone would love easing/automating the vm admin task of replicating the same base vm again and again, me too.

But IMHO every cloning solution has to cope with the fact that each vm is supposed to be unique, i.e. to have unique
- SID (win machines),
- SSH keys,
- hostnames,
- IPs,
- MAC addresses, and so on.

Of course you can restore PVE vm as another VMID and then change everything in order to make the new vm unique but i don't know how other hypervisors (esxi) do that "easily", on each OS.

How do openvz appliances create the 'uniquity' each time they're used to create a new vm? Is there a "run at first boot" script that does that?

yes, during the first start-up all keys should be created. if you create the appliance with our dab this is done automatically (http://pve.proxmox.com/wiki/Debian_Appliance_Builder). But there are a lot of openvz templates around not doing this, e.g. delivered with wide open mysql servers etc.

On windows systems, it is unclear if a duplicate SID is always a real problem, probably the best way would be use Sysprep probably (see http://blogs.technet.com/b/markrussinovich/archive/2009/11/03/3291024.aspx)
Marco

its unclear even on windows, and generally speaking, how can Proxmox VE knows what applications are installed? I know some others are offering cloning just ignoring most security issues and the users will run into problems soon. I would prefer a solution where you can define the hardware setup and if you "clone" the installation will start.

btw, there are a lot of independent mass deployment solutions around, especially for windows.

 

[/dev/null]

ad 2:
pls explain in detail what you mean with "snapshotting", describe functionality and think of KVM and our storage model, and also OpenVZ

With "snapshotting" I meant the ability to make the typical "snapshots".

At least it would be nice to have a GUI-implementation of the backups. That means if you could manage backups assigned to a particular VM and probably restore,delte backups etc.

"Snapshots" could in the beginning realized by doing simple full-backups.

 

[m.ardito]

Well, if your storage is LVM based (iscsi LUN) and the machine is running, you can already have "full system" snapshot with vm downtime around 1 second: doing a "snapshot" backup, from pve gui or manually with vzdump

Marco

 

[vcp_ai]

May be a simple one, but ...
Can you include a sshconsole or secureshell to the ProxMox Server Machine, may be on the Administration area of the Web Page left Panel, or on a New Tab on Server Administration ?

 

[tom]

yes, this is already on our todo list (but not the highest priority as there are still some security issues to be resolved first.)

 

[vcp_ai]

Another simple one ...

Include a Backup_Now button on Backups setting to allow for inmediate backup...

Regards

 

[krislyttle]

Hello everyone...new to the forum and I'm pleased to be here.

I must admit straight away that I'm not yet a Proxmox user, but I'm planning to fairly soon, all being well.

I would like to know if Proxmox would be interested in creating a client-based hypervisor as part of the roadmap. I'm thinking this would allow for working offline and auto-syncing with the VM(s) on the server once the connection is re-established. Or is this already doable using alternate means or product?

Thanks in advance.

UPDATE: I came across an open-source desktop solution called VERDE from a company called Virtual Bridges that may do what I'll need when the time comes.

Has anyone used this product, particularly in conjunction with Proxmox VE?

 

[BiagioParuolo]

Web Services or Remote Api???

 

[krislyttle]

Web Services or Remote Api???

Quite honestly, I don't know; I'm not in IT. I'm just an electrical engineer exploring ideas on using open-source solutions as much as possible (virtualization being among them) in a home office environment to collaborate with other professionals (wherever they're physically located) over the internet. I'm thinking I'd have at least one personal and one professional VM on my notebook as well as my server. This is all hypothetical, though, so bear that in mind.

Let me know if you need any further information to give you a clearer understanding on what I intend to do; I'd love to get any suggestions.

 

[twocell]

I would like to see something like this (read all 3 articles):

http://www.linux-kvm.com/content/how-you-can-use-qemukvm-base-images-be-more-productive-part-1

implemented in the web based software. Using the copy on write features of cqow2 you can set an image as a "base" or "golden" image. You can then deploy servers based on this image without duplicating the shared data. Licensing and deployment depends on the OS, but there are tools for Windows.


My final roadmap suggestion would be BTRFS support. If you haven't read this article yet:

http://lwn.net/Articles/342892/

BTRFS isn't production ready yet, but it's very close and provides a ton of features that would be very beneficial to Proxmox:

* Extremely fast writable snapshots.
* Online file system check and defrag.
* High performance compression.
* Multiple device support.
* Extents for large files, and pack for small files.

Obviously you don't want to run BTRFS on critical production servers, but I think it's ready to start testing. Personally I think this is going to be the future.

 

[JustaGuy]

* Online file system check and defrag.
* High performance compression.

Integrity checking is a constant concern in the back of my mind.
Twice since using PVE (2-3 years?), I've encountered unusable/corrupted .tar backups and I worry about good ones being overwritten.

manage backups assigned to a particular VM

I found this thread while querying 'maxfiles', currently looking for an easy way to assign non-global, rather per-disk backup history.
Currently the maxfiles value must accomodate the lowest common denominator with regard to storage capacity, ie. the largest machine cannot do maxfiles=foo+1 because the +1 is larger than the target storage, thus all VMs must adhere to that maxfiles value despite their being so much smaller.

a sshconsole or secureshell to the ProxMox Server Machine, may be on the Administration area of the Web Page left Panel, or on a New Tab on Server Administration ?

Has crossed my mind, saw the need more than once.

Backup_Now button

Quite a few simple little buttons like this would certainly contribute to the improvement of the admin's experience, however I can see how these types of features have the ability to nickel & dime the developers' time and distract from features I'd much rather see have the attention they deserve, ie. HA, Firewall, Users- IMO.


I'm reluctant to make any demands, since already the devs have far more than done good by me. But I'll mention quickly that I often think about how to implement a customer portal, and wish I could afford to rent a VPS from the PVE partners just to see how they manage PVE instances.
As always other things take priority & the idea fails to evolve.

It would be nice to see someone with the skills to make the small extraneous features happen, pick it up and do so.
I for one, wish I had time to do among other things- contribute to the wiki, since aside form occasional beta testing that's about the best I can do at this point. The matter of time is a distinct factor.
My own to-do list is a great challenge lately.

 

[pgervais]

Create a RAM drive from Proxmox GUI to allow VM (32 bit windows) to use it for the pagefile. Many companies are stuck using 32 bit Terminal Server (due to corporate apps.) and this would help resolve the 4GB Windows RAM limitation.