Howdy all,
So, somewhere along the way Jamie released Cloudmin 2.7. Big feature in that release is LVM partition support, which was the #1 feature request from existing users, but it also has a number of other features requested by users, including more capabilities and more limits (including Account Plans) for the virtual machine owner accounts.
Changes since 2.6:
- CPU, memory and run-time usage are now collected for all systems, and displayed on the Edit System page. This is also combined for system owners, and the sum total of their usage across all owned machines is displayed on the Edit System Owner page.
- Added locking to all scripts, to prevent concurrent updates to the same systems.
- Protect scripts that update or create systems from being terminated by a browser cancel, which could leave Cloudmin in an in-consistent state.
- CPU and drive temperatures are now collected from systems running Virtualmin Pro 3.69 or later, and can be plotted on the System Statistics page.
- Virtual systems can be reset to their original state using the new Reset From Image page, or the reset-image API command.
- Virtual systems on Xen can now have their root filesystem on an LVM logical volume on the host system. Additional disks can also be added on LVM, and logical volumes can be expanded if needed.
- Virtualmin Pro licence expiry dates are shown on the Edit System and Virtualmin Pro Licences page.
- Virtual system images copied to host systems can now be cached up to some maximum total size, using the 'System image cache' section on the 'Edit Xen Host' page. This prevents un-necessary data transfers between the Cloudmin master and host systems.
- Account plans which define limits on system, disk, RAM and CPU use for system owners can now be created. Each owner's limits, virtual system types, actions and host systems are now inherited from their plan, and plan changes update all owners at once.
- System owners can now create new virtual systems, up to the limits defined in their plans. They can also manage CPU, disk and memory use on virtual systems, if allowed in the plan.
Updates are handled via the built-in package updates module, and so you should have already seen the updates a few days ago (I'm slower than usual on noticing these things...getting ready for OSCON!).
And, hot on the heels of that, Jamie let me know he has a prerelase version 2.8 of Cloudmin with OpenVZ support ready for testers. Please contact me, here or via email (joe@virtualmin.com), if you're a Cloudmin user that's been waiting for OpenVZ support, and we'll get you setup with that version. Note that this is a test release, and probably shouldn't be used on production systems until you know it doesn't do something nasty (it has, of course, been tested in-house, but this is a big feature and a lot of new code that interacts with rather complex systems). At the very least, you should have recent, known-good, backups of everything that this new code would touch (so any OpenVZ virtual machines you plan to import, etc.).
As always file tickets in the ticket tracker if you have any problems with the new release.
