Proxmox 2.x planned features

L

l.mierzwa

Member
Jun 2, 2009
147
0
16
Hi,

roadmap for 2.x includes such things as:


  • HA for KVM guests
  • User management (advanced)
  • Resource monitoring
Are this features started in any way? I would like to know few details on how are they going to work as I'm planning to use proxmox.


  • HA for KVM guests - this probably mean that if proxmox machine will die, then all kvm containers which are using remote or replicated storage will be restarted on another one in the same cluster, right?
  • User management (advanced) - this one is very important to me, I got many vm users and I would like to give then control over containers they own, this is probably what You are planning as it seems natural evolution for corporate users, but I would like to know how are You going to store users. The tricky part is how those users will be stored, the best thing for me (and probably whole lot of people) would be to fetch users from LDAP/Active Directory server and set in proxmox configuration which of them are proxmox admins to give them full control.
  • Resource monitoring - are You going to simply extend current monitoring with historical data storage and show some fancy graphs instead of bars, or does it mean some more dramatic changes like implementing collectd or something similar?
Łukasz Mierzwa
 
l.mierzwa said:
Hi,

roadmap for 2.x includes such things as:


  • HA for KVM guests
  • User management (advanced)
  • Resource monitoring
Are this features started in any way? I would like to know few details on how are they going to work as I'm planning to use proxmox.


  • HA for KVM guests - this probably mean that if proxmox machine will die, then all kvm containers which are using remote or replicated storage will be restarted on another one in the same cluster, right?
  • User management (advanced) - this one is very important to me, I got many vm users and I would like to give then control over containers they own, this is probably what You are planning as it seems natural evolution for corporate users, but I would like to know how are You going to store users. The tricky part is how those users will be stored, the best thing for me (and probably whole lot of people) would be to fetch users from LDAP/Active Directory server and set in proxmox configuration which of them are proxmox admins to give them full control.
  • Resource monitoring - are You going to simply extend current monitoring with historical data storage and show some fancy graphs instead of bars, or does it mean some more dramatic changes like implementing collectd or something similar?
Łukasz Mierzwa
Click to expand...

HA is currently under heavy development, second priority is user management - you can expect the first beta releases with HA in Q2/Q3.
 
l.mierzwa said:
Can You share on what to expect from this features? Is it documented in any way at this time?
Click to expand...

it will be based on the latest and greatest Linux HA technologies :-). there is still no fixed feature list but it is a quite cool system and and a major milestone for the project. as soon as we have detailed info we will publish it here.
 
Is there any information available on how the upgrade process from 1.x to 2.x will go? Will it be possible to upgrade without interruption to production systems? I'm getting ready to deploy proxmox in a production environment and am wondering if I should hold off on more critical vm's until 2.x comes out.
 
jhammer said:
Is there any information available on how the upgrade process from 1.x to 2.x will go? Will it be possible to upgrade without interruption to production systems? I'm getting ready to deploy proxmox in a production environment and am wondering if I should hold off on more critical vm's until 2.x comes out.
Click to expand...

the whole cluster communication will change. but its too early to say something detailed about the upgrade process.
 
I would definitely like to see continuity of snapshots across upgrades. This is needed if you want to compare favorably with other VM management environments. At least put in the release notes that snapshots can't be used across upgrades.
 
cstrav said:
I would definitely like to see continuity of snapshots across upgrades. This is needed if you want to compare favorably with other VM management environments. At least put in the release notes that snapshots can't be used across upgrades.
Click to expand...

you talk about backups via snapshots (vzdump using LVM snapshots)?
there should be no issues here.
 
l.mierzwa said:
Are this features started in any way?
Click to expand...

yes, we currently work on those features.

l.mierzwa said:
HA for KVM guests - this probably mean that if proxmox machine will die, then all kvm containers which are using remote or replicated storage will be restarted on another one in the same cluster, right?
Click to expand...

yes.

l.mierzwa said:
User management (advanced) - this one is very important to me, I got many vm users and I would like to give then control over containers they own, this is probably what You are planning as it seems natural evolution for corporate users, but I would like to know how are You going to store users. The tricky part is how those users will be stored, the best thing for me (and probably whole lot of people) would be to fetch users from LDAP/Active Directory server and set in proxmox configuration which of them are proxmox admins to give them full control.
Click to expand...

There will be a file which stores 'users --> access right' mapping. The autentification mechanism will be configurable (per user), for example 'pam', 'ldap', directly stored passwd, certificates, ...

l.mierzwa said:
Resource monitoring - are You going to simply extend current monitoring with historical data storage and show some fancy graphs instead of bars, or does it mean some more dramatic changes like implementing collectd or something similar?
Click to expand...


That is still not decided.
 
Could it be possible to add some form of hooks for events like creating, modifying and deleting containers? After each such event a user defined script would be called (with some set of arguments describing container) so I could integrate proxmox with my current infrastructure, I could for example add entries to dns/dhcp or whatever.
 
l.mierzwa said:
Could it be possible to add some form of hooks for events like creating, modifying and deleting containers? After each such event a user defined script would be called (with some set of arguments describing container) so I could integrate proxmox with my current infrastructure
Click to expand...

If your 'infrastructure' create/delete the containers, it can also call those scripts, no need to add hooks. Or what do I miss?
 
dietmar said:
If your 'infrastructure' create/delete the containers, it can also call those scripts, no need to add hooks. Or what do I miss?
Click to expand...

I create/delete containers from within proxmox, but after I add/modify some container I usually must do some other stuff (like add host to nagios) so it would be easier for me if I could define in proxmox a script that would be run by proxmox after each such action.
 
Any update on the HA feature? (it is Q2 and almost Q3 ;))

We are looking for a panel/solution with HA and if Proxmox is the solution in the near future we are going with proxmox (and donate some money).

And how does the HA will work? with or without a SAN/NAS?
 
Regarding the actual configuration and management of the machines, I would strongly recommend puppet (http://www.puppetlabs.com/). You basically define each host (or classes of host) and say things like "hostA is a web server so it should have apache and this SSL key and the nagios checks are XYZ". After installing hostA you then install a puppet client and then puppet will configure the macine (and associated services like nagios) for you.

It takes a while to get used to, and does require some effort, but it is worth it if you have find yourself doing the same thing over and over again.

I moved about 40 machines in a few hours because most of them had fairly static configuration (i.e. apache web servers or tomcat application servers) and were configured in puppet. It was a dream to do.
 
You must log in or register to reply here.
Top Bottom