Beruflich Dokumente
Kultur Dokumente
html)
Products (products.html)
Services (services.html)
Company (company.html)
Community (community.html)
Resources (resources.html)
Requirements
Two physical Server. Alternatively openQRM itself can be installed within a Virtual Machine
at least 1 GB of Memory
at least 100 GB of Diskspace
VT (Virtualization Technology) enabled in the Systems BIOS for the VMware ESX Host system so it can run HVM Virtual Machines later
Please notice!
A detailed Howto about the above initial starting point is available at 'Install openQRM 5.1 on Debian Wheezy' (http://www.openqrmenterprise.com/community/howtos/install-openqrm-51-on-debian-wheezy.html)
For this howto we have used the same openQRM server as for the howtos about 'Virtualization with KVM and openQRM 5.1 on Debian Wheezy'
(http://www.openqrm-enterprise.com/resources/documentation-howtos/howtos/virtualization-with-kvm-and-openqrm-51-on-debian-wheezy.html),
'Virtualization with Xen and openQRM 5.1 on Debian Wheezy' (http://www.openqrm-enterprise.com/resources/documentationhowtos/howtos/virtualization-with-xen-and-openqrm-51-on-debian-wheezy.html) and 'Automated Amazon EC2 Cloud deployments with openQRM 5.1
on Debian Wheezy' (http://www.openqrm-enterprise.com/resources/documentation-howtos/howtos/automated-amazon-ec2-cloud-deploymentswith-openqrm-51-on-debian-wheezy.html). That means with this howto we are going to add functionality to an existing openQRM setup. This is to
show that openQRM manages all different virtualization and deployment types seamlessly.
Actually this means you can use either use the 'Install openQRM 5.1 on Debian Wheezy' (http://www.openqrmenterprise.com/resources/documentation-howtos/howtos/install-openqrm-51-on-debian-wheezy.html), 'Virtualization with KVM and openQRM 5.1 on
Debian Wheezy' (http://www.openqrm-enterprise.com/resources/documentation-howtos/howtos/virtualization-with-kvm-and-openqrm-51-on-debian-
wheezy.html), 'Virtualization with Xen and openQRM 5.1 on Debian Wheezy' or 'Automated Amazon EC2 Cloud deployments with openQRM 5.1 on
Debian Wheezy' (http://www.openqrm-enterprise.com/resources/documentation-howtos/howtos/automated-amazon-ec2-cloud-deployments-withopenqrm-51-on-debian-wheezy.html) howto as starting point.
As the first step after the openQRM installation and initialization it is recommended to configure a custom domain name for the openQRM
management network. In this Use-Case the openQRM Server has the private Class C IP address 192.168.178.5/255.255.255.0 based on the previous
'Howto install openQRM 5.1 on Debian Wheezy' (URL). Since the openQRM management network is a private one any syntactically correct domain
name can be used e.g. 'my123cloud.net'. The default domain name pre-configured in the DNS plugin is "oqnet.org".
Best practice is to use the 'openqrm' commandline util to setup the domain name for the DNS plugin. Please login to the openQRM Server system
and run the following command as 'root' in a terminal:
Enabling Plugins
In the openQRM Plugin Manager please enable and start the following plugins in the sequence below:
Hint: You can use the filter in the plugin list to find plugins by their type easily!
Please notice!
During the VMWare SDK installation the VMWare installer only searchs for Ubuntu in the release file. To succeed the installation on Debian please
add the paramter directly on the commandline please running as root:
During the SDK installation please accept the licence and the default parameters.
The autodiscovery now searches the openQRM management network for existing ESX Hosts.
During the autodiscovery the event list shows an active event to inform about the action running in the background.
Click on 'Add' to add the ESX Hosts to openQRM data-center repository. In the 'Add' form please provide the admin user credentials to manage the
ESX Host. When finished click on 'Submit'
Please notice!
Please make sure to provide the exact hostname PLUS domainname in this form! The VMWare API is really serious that the correct full FQDN is
used for the Host configuration.
To re-check the exact domainname configuration of the ESX Host please login to the ESX Console
You can find the configured domainname in the ESX console - Configure Management Network - Custom DNS Suffixes
The integration automatically created a server object from the type ESX Host
To store the Virtual Machine Images and configuration VMWare ESX is using 'Datastore'. Serveral different storage types are supported to be attached
to an ESX Host as Datastore e.g. NAS, iSCSI or FC SAN. For this Howto a simple NAS/NFS share is used for the initial Datastore on the ESX Host. To
create a NFS share for the Datestore we are using the 'nfs-storage' plugin. First step is to create a new storage object from the type 'nfs-deployment'.
Go to Datacenter -> Components -> Storagte -> Add new Storage
Provide a name for the storage object, select 'nfs-deployment' as Deployment Type and choose the openQRM server as resource.
Creating the new storage forwards to the storage overview. Please click on 'Manage' of the new created NFS-Storage Ojbect.
Provide a name for the new volume, we choose 'esx_datastore' for this Howto.
Here again the NFS volume overview with the new created volume listed. Now please click on 'Auth' to authenticate the new created NFS share
against the ESX Hosts ip.
Now the NFS volume is correctly authenticated against the ESX Hosts ip.
We are going to attach this NFS share as Datastore to the ESX Host later in this Howto. First we go on with creating a automatic-installation profile with
LinuxCOE.
The LinuxCOE Project provides a useful UI to create automatic-installation ISO images for various Linux distribution e.g. preseed, kickstart and
autoyast. Those ISO images can be then used to fully automatically install a Linux distribution without any manual interaction needed. The integration
of LinuxCOE in openQRM makes those automatic-installation ISO images automatically available on all Virtualization Hosts (mounted by nfs at
/linuxcoe from the openQRM server). This makes it easy to configure a Virtual Machines installation boot image from the central ISO Pool mount
point.
Please notice!
The LinuxCOE plugin in openQRM comes with a fully automatically setup and pre-configuration of LinuxCOE. Since LinuxCOE is an installationframework it is recommended to add further custom configuration such as local package mirrors, new distribution data and config files etc. Please
read more about how to further enhance your LinuxCOE installation at http://linuxcoe.sourceforge.net/#documentation
(http://linuxcoe.sourceforge.net/#documentation).
Here please provide your custom package setup for the automatic-installation.
The summary page of the LinuxCOE wizard allows to preconfigure a root and user account. Click on 'Go for it' to create the automatic-installation
template.
The ISO image is created. No need to download it since it will be used directly by the VMware ESX Host for a VMware ESX Virtual Machine installation
from a central '/linuxcoe-iso' NFS share on the openQRM server.
Go to Plugins -> Deployment -> LinuxCOE -> Template Manager and click on 'Edit'.
Here add the previously created NFS Volume as new Datastore. The path for the NFS share is '/exports/esx_datastore'
Now click again 'Add new NAS Datastore'. We are going to add the automatically shared LinuxCOE ISO Pool to the ESX Hosts as another Datastore.
This datastore is used to provide ISO Images for Operating Systems installations.
To add the LinuxCOE ISO Pool please provide a name for the datastore, the ip address of the openQRM server and as path '/linuxcoe'
Here again the Datastore overview with the 2 new datastores created.
Please give a name for the new server. Easiest is to use the 'generate name' button. Also provide a useful description.
In the Resource-Selection please click on 'new resource'. A resource in openQRM is a logical generic object which is mapped to a physical system or
Virtual Machine of any type.
On the next page find a selection of different resource types to create. Please choose 'VMware ESX (localboot) Virtual Machine'
This forwards to the VMware ESX Host selection. Please select the VMware ESX Host as the Virtualization Host of the VM
On the VMware ESX Virtual Machine Overview please click on 'Add local VM'
In the VM add form provide a name for the new VM. Again the easiest is to use the 'generate name' button. There are lots of different parameters
which can be configured. Anyway you can go with most of the default selection. Please just make sure the first network card of the VM is connected to
the 'Default VM Network'
Further down the VM add form please configure the boot sequence of the VM. Select 'iso' and open the Filepicker by clicking on the 'Browse' button.
This will open a small new window listing all ISO Images found on the ESX Virtualization Host. Navigate to '/linuxcoe' and select the previously created
LinuxCOE automatic-installation iso iamge. Please notice that the name of the iso image may be different in your setup.
Creating the new VM automatically forwards back into the server wizard with the new created resource available. Select the new resource and
'Submit'
An Image for the new ESX VM got automatically created during the VM creation. Please select the VM Image and click on 'Submit'
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'
Starting the logical server object triggers to actually start the resource (the VMware ESX 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 -> VMware ESX -> VMware ESX VMs and select the VMware ESX Host system.
In the VMware ESX VM overview click on the 'console' button of the VM. This opens a VNC console within your web browser
Please notice!
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 VMware ESX VM is now automatically installing a Debian Linux distribution. Good time for you to grab a coffee!
Please notice!
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:
Go to Plugins -> Virtualization -> ESX -> Discovery and click on 'Autodiscover ESX Hosts'
- stop the VM in the ESX VM overview - Plugins -> Virtualization -> ESX -> VMs -> select ESX Host + Stop VM
- in Plugins -> Virtualization -> VMware ESX -> VMware ESX VMs select the VMware ESX Host and udate the VM to boot 'local'
- now start the VM again - Plugins -> Virtualization -> ESX -> VMs -> select ESX Host + Start VM
Here a screenshot of the completed Debian installation after setting the boot-sequence of the VM to 'local'
cd /usr/share/openqrm/plugins/local-server/web/local-vm/
scp openqrm-local-vm-client [ip-address-of-the-VM]:/tmp/
ssh [ip-address-of-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
/tmp/openqrm-local-vm-client
This will automatically setup the 'openqrm-local-vm-client' in the system init and start it.
Full control for KVM, Xen, VMware and Amazon EC2 systems within a
single managment console
Here the Datacenter Dashboard after we have created the VMware ESX Virtual Machine
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 additional 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.
Links
openQRM Community - http://www.openqrm.com/ (http://www.openqrm.com/)
openQRM Project at sourceforge - http://sourceforge.net/projects/openqrm/ (http://sourceforge.net/projects/openqrm/)
openQRM Enterprise - http://www.openqrm-enterprise.com/ (http://www.openqrm-enterprise.com/)
openQRM at Twitter - https://twitter.com/openQRM (https://twitter.com/openQRM)
openQRM at Facebook - https://www.facebook.com/pages/openQRM-Enterprise/324904179687
(https://www.facebook.com/pages/openQRM-Enterprise/324904179687)
LinuxCOE Project - http://linuxcoe.sourceforge.net/ (http://linuxcoe.sourceforge.net/)
Get in touch
openQRM Enterprise GmbH
Godesberger Allee 139
53175 Bonn / Germany
Tel +49 (0)228 5344 9500
E-Mail info@openqrm-enterprise.com
openQRM Editions
Enterprise Edition (/products/enterpriseedition.html)
Community Edition (/products/communityedition.html)
Edition Comparison (/products/editioncomparison.html)
Legal Information (/imprint.html)
Contact openQRM
Name *
E-Mail *
Your Message *
Web www.openqrm-enterprise.com
(http://www.openqrm-enterprise.com)
Send