Virtualization With KVM And openQRM 5.1 On Debian Wheezy - Page 4
Creating the new Image automatically forwards back into the server wizard with the new created image available. Select the new image and 'Submit'
Click on 'Submit' to edit the Image parameter
This following step allows to edit further Image parameter e.g. setting a root password
The last step in the server wizard presents the full configuration and allows to further setup network, management, monitoring and deployment configuration. Click on 'Submit' to save the server configuration.
The server overview list the new server, not yet activated. Please select the new created server and click on 'Start'
Confirm starting the server
Started the new server, now marked as 'active'. Starting the logical server object triggers to actually start the resource (the KVM VM) with the configured Image (the LVM volume) and triggers additional automatic configuration tasks via a plugin-hook. This server start- and stop hooks are "asking" each activated plugin if there is "some work to do". For a few examples how hooks are used in openQRM please check the list below:
- The DNS plugin is using those hooks to automatically add (or remove) the server name into the managed bind server
- The Dhcpd plugin add the "hostname option" for the server to its configuration
- The Nagios plugin adds/removes service checks for automatic monitoring
- The Puppet plugin activates configured appliaction recipes to automatically setup and pre-configure services on the VM
Go to Plugins -> Virtualization -> KVM -> KVM VMs and select the openQRM server. In the KVM VM overview click on the 'console' button of the VM. This opens a VNC console within your web browser
You need to deactivate the browsers Pop-up Blocker for the openQRM website!
To start the automatic installation please type 'install' in the VNC console and press ENTER.
The KVM VM is now automatically installing a Debian Linux distribution. Good time for you to grab a coffee!
After the automatic installation via the attached LinuxCOE ISO image the VM reboots to the install screen again. We now have to re-configure the VMs boot-sequence to 'local-boot'. To do this please follow the steps below:
- stop the VM by stopping its server object - Datacenter -> Server -> Select + Stop
- in Plugins -> Virtualization -> KVM -> KVM VMs select the KVM Host and udate the VM to boot 'local'
- now start the VM again by starting its server object - Datacenter -> Server -> Select + Start
Here a screenshot of the completed Debian installation after setting the boot-sequence of the VM to 'local'
Install the 'openqrm-local-vm-client'
Now it is recommended to install the 'openqrm-local-vm-client' on the fresh installed system. For local-installed Virtual Machines (e.g. kvm(local VM), xen(local VM), lxc(local VM), openvz(local VM) which have access to the openQRM network the 'openqrm-local-vm-client' activates the plugin-client-boot-services to allow further management functionality (e.g. application deployment with Puppet, system statistics with Collectd etc). Monitoring and openQRM actions are still running on behalf of the VM Host.
The 'openqrm-local-vm-client' also automatically makes sure that the 'acpi-support/acpid' package is installed to enable the reboot/restart functionalities of KVM via the VM monitor socket. To install the 'openqrm-local-vm-client' on VM please follow the steps below:
Copy the 'openqrm-local-vm-client' utility to the running VM
scp openqrm-local-vm-client [ip-address-of-the-VM]:/tmp/
Then login to the VM
This prompts for the password which was configured in the LinuxCOE automatic-installation template. Please give the password and execute the openqrm-local-vm-client utility
This will automatically setup the 'openqrm-local-vm-client' in the system init and start it.
Create additional KVM VMs by cloning/snapshotting the Volume
Go to Plugins -> Virtualization -> KVM -> KVM Volumes and select the 'openqrm-lvm' storage object. Then choose the 'kvmvg' logical volume group to get a list of all available LVM volumes. In this view you can use the 'clone' or 'snap' action to clone or snapshot existing, installed KVM LVM Volumes. The 'clone' action creates a new logical volume and copies the content of the origin over. Snaptshoting is using the "copy-on-write" mechanism of LVM which is much more efficient. Actually a deployd snapshot of a KVM LVM Volume just stores the changes compared to its origin. That means that creating snapshots e.g. per user allows to 'just' store the data which is different per user.
Here the Datacenter Dashboard after we have created the KVM Virtual Machine
Add more functionalities to your openQRM Setup
To continue and further enhance your openQRM KVM Virtualization Setup there are several things to do:
- Enable the puppet plugin and automatically deploy your appliactions to your server
- Enable the highavailability plugin to automatically gain HA for your server
- Enable the hybrid-cloud plugin to automate your Amazon EC2 and Eucalyptus deployments
- Enable the cloud plugin for a complete Self-Service deployment of your Server and Software stack to end-users
- Enable further Virtualization plugins and integrate remote Virtulization hosts for a fully distributed Cloud environment
- Enable further Storage and Deployment plugins to automatically provision your Virtualization Hosts and other physical systems
... and more.
openQRM Community - http://www.openqrm.com/
openQRM Project at sourceforge - http://sourceforge.net/projects/openqrm/
openQRM Enterprise - http://www.openqrm-enterprise.com/
openQRM at Twitter - https://twitter.com/openQRM
openQRM at Facebook - https://www.facebook.com/pages/openQRM-Enterprise/324904179687
LinuxCOE Project - http://linuxcoe.sourceforge.net/
Another openQRM Howto sponsored by openQRM Enterprise