This is the first in a series of posts outlining the feature, methods and ideas surrounding the tool: Ubuntu-VM-Builder.

Ubuntu-VM-Builder

Caution, security warning:
These are default settings for a new virtual machine, you will want to change them immediately or better idea would be to set them during build, for more information keep reading after the break.
Default fullname: Ubuntu
Default username: ubuntu
Default password: ubuntu

Here is some quick information on what Ubuntu-VM-builder is:

ubuntu-vm-builder provides a method to quickly create a clean testing environment, a way to automate the virtual machine installation process, and for software developers, the ability to integrate the creation of a virtual machine into the build process of an application. If using a local mirror the virtual machine creation process can take less than two minutes from start to finish. (source)

Step 1. To install Ubuntu-VM-Builder on your linux workstation, requires 8.04 or greater

sudo apt-get install ubuntu-vm-builder

ubuntu-vm-builder Depends on:
Depends: debootstrap
Depends: kpartx
Depends: parted
Depends: qemu

These will automatically be installed by apt-get during the installation, no other installation is required.

Step 2. To build a virtual machine, first move into the directory where you will want the vm folder to be created
mkdir ~/virtual-machines
cd ~/virtual-machines

Step 3. Run Ubuntu-vm-builder, with the required flags and options
sudo ubuntu-vm-builder kvm hardy

For more flags, options and some examples keep reading.
Read more »

Potential future job posting:

Virtual Network Administrator

Responsibilities: A virtual network administrator oversees virtual computer networks to ensure that they function smoothly. A virtual network consists of a grouping of virtual machines that communicate with each other on a physical computer known as a virtual machine host server, on which computer files, programs, and other information are stored. A network may be as small as two or three virtual machines or as large as hundreds when paravirtualization is used.

Education: A virtual network administrator should have a strong background in math, sciences, and computer science, as well as experience working with virtual machines. Although a college degree in computer science, systems science, math, or engineering is not required to become a virtual network administrator, advancement is difficult without one. Administrators should be familiar with a variety of enterprise virtualization software packages, including Microsoft, VMware, and Sun. Because computer technology changes rapidly, administrators must constantly upgrade their knowledge base.

Working Conditions: Virtual network administrators, like other computer professionals, work in an office environment. Most put in forty hours or more of work per week. Much of the job is performed as part of an enterprise team, along with physical network administrators, and virtual machine managers. Configuring a virtual network can require long hours of work over a short period of time. Maintaining the virtual network can alternate between routine tasks and the more interesting but hectic work of troubleshooting and fixing virtual network problems. If a virtual network crashes, the administrator must work as quickly as possible, regardless of the hour, to solve the problem and restore the network to operation.

Similar Job description: Network Administrator Job Description

How about this strange idea, Remote Office Live CD?

Now initially it sounds strange, having a remote office server, running with a live CD, but it does have some really unique potential.

You run a small to medium sized business, where 80% of your workforce works, or could work from home. They all require access to the company database, using ancient software which doesn’t support VPN or other complex networking technology. So, how do you deploy out a database server to 50 plus employees who may only have 1 physical computer at home? Simple, a live CD. Build a live cd, with virtualization, and a virtual database server on the first CD, and then use a second cd, flash card or external hard drive for the database. Or, have the virtual machine updated itself using VPN on boot.

If your database, for example merchandise catalog is only updated bi-weekly, then just send out a second CD or new flash drive every other week. The live CD means that no matter how much crap is on the computer at the house, it won’t affect the “company business”, due to no local access.

If you need to update anything on the operating system, send out a new first CD. Due to the nature of a livecd, there is very little risk of a long term virus lasting any longer then the power cycle of the computer.

From an IT standpoint this would make home office support so easy. All users would be guanteed the same desktop experience every time they turn their computer on. No more problems of the kids homework taking over that system you sent them home with for “company business.”

The same idea would work well for sending out demo software to clients, something Microsoft is testing now with their Virtualization products. They offer a collection of VHDs, for testing, which “could”, possible be loaded onto a virtual machine off a boot cd. This isn’t an optimal setup, but it would possibly work:

PC -> Linux Boot LiveCD -> Linux Distro -> VMware -> VHD converted to VMware -> Vista

This allows you to build a Vista boot CD.

Sources:
OpenVZ Virtualization Software Available with CentOS On ‘Live CD’ To Simplify Trial Usage
Virtualization For Everyone in Ten Minutes or Less and XenExpress
Xenfire 2.0
Run IT on a Virtual Hard Disk