We are happy to announce that UForge 3.4 release is ready! This release includes a major new service - Migration. We've also moved to RBAC and made some huge improvements to supporting Windows.
The new Migration service (launched in Beta) allows you to deep scan a live system (whether the system is virtual, cloud or physical) and import this scan as a model (i.e. server template) into UForge. This is a game-changer in the way customers create server templates in UForge. Live systems are simply teleported into UForge and transformed into a model, allowing you to re-generate images to any other target platform (traditional migration) as well as having access to the model of the live system - i.e. all the package information, licensing etc. This allows you to retrieve information on a live system for auditing purposes, or lets you tweak and change the model (updates) prior to migrating the system. Debian and RPM-based systems are supported, with Windows coming in the near future. For more information read this article, for a demo, see this video.
Role-Based Access Control
Up until now resource access has been enforced on a user per user basis. UForge resource access management has now been overhauled. Administrators can now create roles that manage entitlements that describe access to various UForge resources. These roles can then be assigned to one or more users. UForge RBAC is handled by Apache Syncope which has been embedded into the UForge platform. This module includes identity and access management, opening the door for UForge to integrate seamlessly with IAM use cases.
Ever since the arrival of UForge 3.0, users have been able to create templates using Windows as a guest OS (not available with UForge online). With this upcoming release it will now be possible to have more control of your Windows templates, including:
- adding boot scripts to configure the instance on first (or every) boot.
- silent installation of 3rd party software by automatically executing the installation with parameters.
- include Windows activation keys in the template.
UForge calculates package versions and dependencies during an image generation based on a date. This allows the user to roll-forward or roll-back operating system packages in an OS profile. The negative impact on using the mechanism is that the user couldn't specify a particular package version to be part of the generation; depending on the build date of the package, an earlier or more up to date version of the package would be chosen instead. UForge now provides a mechanism to select a particular package version, known as making a package “sticky”. This increases the flexibility the user has in choosing package versions as well as protecting against destructive upgrades. This article provides more information on package dependencies.
User Usage & Statistics
The new UForge 3.4 has been updated to allow you to get usage statistics per user. We've also put in place the necessary mechanisms to integrate a third party billing system with UForge, allowing you to bill end users based on their user of UForge Factory. In addition, you can set quotas for the number of templates, generations, and migrations a user can carry out.