Virtualisation with Xen and openQRM on Debian - Revision history

Stvsyf at 04:15, 10 December 2020

2020-12-10T04:15:03Z

Stvsyf: /* Enabling Plugins */

2020-12-10T00:49:15Z

Enabling Plugins

Show changes

Stvsyf: /* Create the Virtualization Host Object */

2020-12-01T02:30:33Z

Create the Virtualization Host Object

Stvsyf: /* Create the Virtualization Host Object */

2020-12-01T02:14:54Z

Create the Virtualization Host Object

Stvsyf: /* Install Debian Wheezy on the second system dedicated for the Xen Host */

2020-12-01T00:26:01Z

Install Debian Wheezy on the second system dedicated for the Xen Host

Stvsyf at 23:48, 30 November 2020

2020-11-30T23:48:37Z

Show changes

Stvsyf: Created page with "h"

2020-11-30T23:34:55Z

Created page with "h"

New page

← Older revision		Revision as of 04:15, 10 December 2020
Line 312:		Line 312:

	You've successfully installed Xen Virtualisation on openQRM!		You've successfully installed Xen Virtualisation on openQRM!
		+	[[Category:Tutorial]]
		+	[[Category:Virtualisation]]
		+	[[Category:Xen]]
		+	[[Category:Debian]]

@@ Line 176: / Line 176: @@
 Go to '''Datacentre -> Server''' and click on '''<nowiki/>'Edit'''' of the Xen Host server object
-[[File:Csm 11-openqrm-xen cacff36955.png|none|thumb|390x390px]]
+[[File:Csm 11-openqrm-xen cacff36955.png|none|thumb|390x390px|Click on '''<nowiki/>'Edit'''']]
 In the server edit section please select '''Network -> Network Manager'''.
@@ Line 188: / Line 188: @@
 Then click on '''submit''' to create the new network bridge.
-[[File:Csm 13-openqrm-xen e3ce850a17.png|none|thumb|390x390px]]
+[[File:Csm 13-openqrm-xen e3ce850a17.png|none|thumb|390x390px|Click on '''submit''']]
 === Create a LinuxCOE automatic-installation template ===
@@ Line 195: / Line 195: @@
 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 installation-framework 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 <nowiki>http://linuxcoe.sourceforge.net/#documentation</nowiki>
+'''NOTE:''' The LinuxCOE plugin in openQRM comes with a fully automatically setup and pre-configuration of LinuxCOE. Since LinuxCOE is an installation-framework 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 <nowiki>http://linuxcoe.sourceforge.net/#documentation</nowiki>
 First step is to create a new automatic-installation profile and ISO image.
-Go to Plugins -> Deployment -> LinuxCOE -> Create Templates and select a Linux distribution and version for the automatic-installation. For this How-To we will use 'Debian Squeeze 64bit'. Please leave the hostname input empty since openQRM will care about this via its dhcpd plugin.
+Go to '''Plugins -> Deployment -> LinuxCOE -> Create Templates''' and '''select a Linux distribution''' and version for the automatic-installation. For this How-To we will use '''<nowiki/>'Debian Squeeze 64bit''''. Please leave the hostname input empty since openQRM will care about this via its '''dhcpd plugin.'''
+[[File:Csm 18-openqrm-xen e76924d84f.png|none|thumb|390x390px|Select a Linux distribution and version for the automatic-installation.]]
-Leave the default settings on the next page of LinuxCOE wizard.
+Leave the '''default settings''' on the next page of LinuxCOE wizard.
+[[File:Csm 19-openqrm-xen 860efac774.png|none|thumb|390x390px|Leave the default settings on the next page]]
-Next please select a Mirror from the list.
+Next '''select a Mirror''' from the list.
+[[File:Csm 20-openqrm-xen b682fe271f.png|none|thumb|390x390px|'''Select a Mirror''']]
-Here please provide your custom package setup for the automatic-installation.
+Here provide your '''custom package setup''' for the automatic-installation.
+[[File:Csm 21-openqrm-xen 2d6b16b8d5.png|none|thumb|390x390px|Provide your '''custom package setup''']]
-On the following page please leave the default settings.
+On the following page leave the '''default settings'''.
+[[File:Csm 22-openqrm-xen 0a8ba5e988.png|none|thumb|390x390px|Leave the default settings.]]
-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 summary page of the LinuxCOE wizard allows you to preconfigure a root and user account. Click on '''<nowiki/>'Go for it'''' to create the automatic-installation template.
+[[File:Csm 23-openqrm-xen d6731b6fb6.png|none|thumb|390x390px|Reconfigure a root and user account]]
 The ISO image is created. No need to download it since it will be used directly by the Xen Host for a Xen Virtual Machine installation from a central '/linuxcoe-iso' NFS share on the openQRM server.

@@ Line 144: / Line 144: @@
 The integration via the 'local-server' plugin created a new resource object for the Xen Host in openQRM.
+[[File:Csm 02-openqrm-xen 7d2db10a81.png|none|thumb|390x390px|New resource object for the Xen Host in openQRM.]]
 It also created a new server object for the integrated Xen Host to allow further management. Go to '''Datacentre -> Server''' and click on 'Edit' of the Xen Host.
+[[File:Csm 03-openqrm-xen c6da10b4a8.png|none|thumb|390x390px|Go to '''Datacentre -> Server''' and click on 'Edit' of the Xen Host]]
 In the following Edit dialog please set 'Xen Host' as the Virtualization type of the second server, then submit to save
+[[File:Csm 04-openqrm-xen 53ca00b1b3.png|none|thumb|390x390px|Set 'Xen Host' as the Virtualization type of the second server]]
 This is the Server list after configuring the Virtualization Host Object
+[[File:Csm 05-openqrm-xen 1238f8008a.png|none|thumb|390x390px|Server list after configuring the Virtualization Host Object]]
 Additionally 2 Xen Storage Objects are automatically created to manage different types of VM volumes
 === Create a LVM Volume Group ===
 The Xen Storage type with the best flexibility regarding volume management is 'Xen LVM Storage'. Each VM gets its own dedicated logical volume as its root image. Alternatively 'Xen Blockfile Storage' can be used. Volumes for this storage type are created on the Hosts filesystem via the qemu-img command. This How-To describes the 'Xen LVM Storage' type.
-Go to Datacenter -> Storage and click on the 'manage' button of the 'xen-lvm' storage object
+Go to '''Datacentre -> Storage''' and click on the 'manage' button of the 'xen-lvm' storage object
-'''Please notice!''' The system automatically checks if the system utilities for the LVM functionalities are available. If not it openQRM triggers to automatically install them via the distribution package manager. This may delay the first time the command is executed on the system.
+'''NOTE:''' The system automatically checks if the system utilities for the LVM functionalities are available. If not it openQRM triggers to automatically install them via the distribution package manager. This may delay the first time the command is executed on the system.
-Now click on 'Add new Volume group'
+Now click on '''<nowiki/>'Add new Volume group''''
+[[File:Csm 07-openqrm-xen 21d8599c9e.png|none|thumb|390x390px|Click on 'Add new Volume group']]
-When you have followed the paritioning setup in the seconds system Debian installation there is now a dedicated /dev/sda3 partition available which can be used to create a LVM Volume group. Please provide a name for the LVM Volume group (here 'xenvg'), select the /dev/sda3 device and submit.
+When you have followed the partitioning setup in the seconds system Debian installation there is now a dedicated /dev/sda3 partition available which can be used to create a LVM Volume group. Please '''provide a name''' for the LVM Volume group (here 'xenvg'), select the '''/dev/sda3''' device and submit.
 '''Please notice''': On the Xen Host for this How-To we are going to use /dev/sdb3! If you have installed on a single disk your choice will be still /dev/sda3.
+[[File:Csm 08-openqrm-xen 7d66db2e22.png|none|thumb|390x390px|Provide info and submit]]
-Confirm to create the new Volume group
+'''Confirm''' to create the new Volume group
+[[File:Csm 09-openqrm-xen 16b71f5fb3.png|none|thumb|390x390px|Confirm to create the new Volume group]]
 The LVM Volume group to store the VM Images is created now
 === Create one or more network bridges ===
 The Xen Virtualization technology is using network bridges to connect the Virtual Machines virtualized network interfaces to real networks.
-Go to Datacenter -> Server and click on 'Edit' of the Xen Host server object
+Go to '''Datacentre -> Server''' and click on '''<nowiki/>'Edit'''' of the Xen Host server object
+[[File:Csm 11-openqrm-xen cacff36955.png|none|thumb|390x390px]]
-In the server edit section please select Network -> Network Manager.
+In the server edit section please select '''Network -> Network Manager'''.
 This will provide a list of all available network interfaces on the system.
-'''Please notice''': The system automatically checks if the system utilities for the bridge and network functionalities are available. If not it openQRM triggers to automatically install them via the distribution package manager. This may delay the first time the command is executed on the system.
+'''NOTE''': The system automatically checks if the system utilities for the bridge and network functionalities are available. If not it openQRM triggers to automatically install them via the distribution package manager. This may delay the first time the command is executed on the system.
-Then click on submit to create the new network bridge.
+Please click on '''<nowiki/>'Add new network bridge'''' to create a new network bridge
-Here a screenshot of the network interface list after creating the new network bridge 'br0'.
+Then click on '''submit''' to create the new network bridge.
 === Create a LinuxCOE automatic-installation template ===

@@ Line 68: / Line 68: @@
 After the installation finished please login to the system and update its packaging system as 'root'
-apt-get update && apt-get upgrade
+<code>apt-get update && apt-get upgrade</code>
 Then install the Xen Hypervisor plus its package dependencies by the following command:
-apt-get install xen-linux-system-amd64
+<code>apt-get install xen-linux-system-amd64</code>
-To set the Xen Hypervisor as the default kernel in Grub please edit "/etc/default/grub" and udpate
+To set the Xen Hypervisor as the default kernel in Grub please edit "/etc/default/grub" and update
-GRUB_DEFAULT=0
+<code>GRUB_DEFAULT=0</code>
 to
-GRUB_DEFAULT=2
+<code>GRUB_DEFAULT=2</code>
 After a regular Debian Installation the Xen Hypervisor is normally the third boot option in /boot/grub/grub.cfg. Counting from 0 the GRUB_DEFAULT should be set to 2). Then run:
-update-grub && reboot
+<code>update-grub && reboot</code>
 to update the Grub boot-loader and to reboot the system into the Xen Hypervisor.
-After reboot login again to the 2. system and ensure that the system has booted the Xen Hypervisor by running:
+After reboot login again to the second system and ensure that the system has booted the Xen Hypervisor by running:
-xm list
+<code>xm list</code>
-The output of this command should be similar to the following:
+The output of this command should be similar to the following:<blockquote><code>root@debian:~# xm list</code>
-root@debian:~# xm list
+<code>Name                                        ID   Mem    VCPUs    State   Time(s)</code>
-Name                                         ID   Mem VCPUs      State   Time(s)
+<code>Domain-0                                     0   3514     2     r-----   20.9</code>
-Domain-0                                     0  3514     2     r-----     20.9
+<code>root@debian:~#</code></blockquote>
 === Enable VNC access to the Virtual Machine console on the Xen Host ===
 To enable VNC access to the Virtual Machine console on the Xen Host please edit '/etc/xen/xend-config.sxp' and adapt the 'vnclisten' parameter. Uncomment and update it to:
-vnclisten="0.0.0.0"
+<code>vnclisten="0.0.0.0"</code>
 Then restart Xen to activate the new VNC configuration.
-/etc/init./xend restart
+<code>/etc/init./xend restart</code>
 === Integrate the Xen System into openQRM via the "local-server" plugin ===
 Copy (scp) the openqrm-local-server integration tool from the openQRM server to the second System dedicated for the Xen Host:
-scp /usr/share/openqrm/plugins/local-server/bin/openqrm-local-server 192.168.178.6:
+<code>scp /usr/share/openqrm/plugins/local-server/bin/openqrm-local-server 192.168.178.6:</code>
 Then login (ssh) to the second System and run the openqrm-local-server tool with the 'integrate' parameter:
-./openqrm-local-server integrate -u openqrm -p openqrm -q 192.168.178.5 -n xen -i eth0 -s http
+<code>./openqrm-local-server integrate -u openqrm -p openqrm -q 192.168.178.5 -n xen -i eth0 -s http</code>
 Here how it looks like on the seconds system terminal console:
-root@debian:~# ./openqrm-local-server
+<code>root@debian:~# ./openqrm-local-server</code>
-Usage : ./openqrm-local-server integrate -u <user> -p <password> -q <ip-address-of-openQRM-server> [ -n <hostname> ] [-i <network-interface>] [-s <http/https>]
+<code>Usage : ./openqrm-local-server integrate -u <user> -p <password> -q <ip-address-of-openQRM-server> [ -n <hostname> ] [-i <network-interface>] [-s <http/https>]</code>
-       ./openqrm-local-server remove -u <user> -p <password> -q <ip-address-of-openQRM-server> [ -n <hostname> ] [-s <http/https>]
+<code>       ./openqrm-local-server remove -u <user> -p <password> -q <ip-address-of-openQRM-server> [ -n <hostname> ] [-s <http/https>]</code>
-root@xen1:~# ./openqrm-local-server integrate -u openqrm -p openqrm -q 192.168.178.5 -n xen -i eth0 -s http
+<code>root@xen1:~# ./openqrm-local-server integrate -u openqrm -p openqrm -q 192.168.178.5 -n xen -i eth0 -s http</code>
-Integrating system to openQRM-server at 192.168.178.5
+<code>Integrating system to openQRM-server at 192.168.178.5</code>
--> could not find dropbear. Trying to automatically install it ...
+<code>-> could not find dropbear. Trying to automatically install it ...</code>
-Reading package lists... Done
+<code>Reading package lists... Done</code>
-Building dependency tree
+<code>Building dependency tree      </code>
-........... (more output and automatic package installation)
+<code>........... (more output and automatic package installation)</code>
-root@debian:~#
+<code>root@debian:~#</code>
 === Create the Virtualization Host Object ===
-'''Please notice''': In this How-To we will name this second, integrated system as 'Xen Host'! In the openQRM UI the Xen Host is named 'xen'
+'''NOTE''': In this How-To we will name this second, integrated system as 'Xen Host'. In the openQRM UI the Xen Host is named 'xen'
 The integration via the 'local-server' plugin created a new resource object for the Xen Host in openQRM.
-It also created a new server object for the integrated Xen Host to allow further management. Go to Datacenter -> Server and click on 'Edit' of the Xen Host.
 In the following Edit dialog please set 'Xen Host' as the Virtualization type of the second server, then submit to save