This HowTo is brought to you by openQRM Enterprise [http://www.openqrm-enterprise.com/] Document Version : 25.05.2010 openQRM Enterprise GmbH Berrenrather Straße 188c 50937 Köln / Germany Telefon : +49 (0) 221 995589-10 Fax : +49 (0) 221 995589-20 Mail : [email protected] This HowTo guides you step-by-step through an openQRM Cloud setup on CentOS 5.5 for deploying physical Windows Systems. Hardware required for this HowTo are 2 physical systems. The technical details of this openQRM Cloud setup are described in the openQRM Enterprise Documentation at http://www.openqrm-enterprise.com/news/details/article/in-depth-documentationof-openqrm-available.html [http://www.openqrm-enterprise.com/news/details/article/in-depth-documentation-of-openqrm-available.html] section “Configuring a Basic Setup”. 1 of 95 When installing the system with CentOS 5.5 in the partitioning layout screen select “Advanced storage configuration” partitioning. Create 3 Partitions : 1. primary ext3 mounted at / (the rootfs) 2. primary swap 3. primary “lvm” (for the server-image store) Important is to use a custom partition schema and create a dedicated partition for later storing the server-images (in this HowTo it will be /dev/hda3). In the package-selection screen choose “Gnome Desktop Environment”. No need to install any extra software packages for now. Please notice : In the SELinux screen please disable SELinux ! In the Firewall screen please disable the firewall ! When the installation finished reboot and login. Here a screenshot of the CentOS Desktop directly after the installation : Below a console output of lsb_release showing the exact CentOS version. Please notice that all console commands in this HowTo are being executed as “root”. [root@cloud ~]# lsb_release -a LSB Version: :core-3.1-ia32:core-3.1-noarch:graphics-3.1-ia32:graphics-3.1-noarch Distributor ID: CentOS Description: CentOS release 5.5 (Final) Release: 5.5 Codename: Final [root@cloud ~]# 2 of 95 Now edit /etc/sysconfig/network-scripts/ifcfg-eth0 and setup static, private ip-address. (In this example it is 192.168.88.6. Please adapt the ip-configuration to your network-environment) [root@cloud network-scripts]# cat /etc/sysconfig/network-scripts/ifcfg-eth0 DEVICE=eth0 BOOTPROTO=none HWADDR=00:02:b3:a0:d3:12 ONBOOT=yes DHCP_HOSTNAME=cloud IPADDR=192.168.88.6 NETMASK=255.255.255.0 GATEWAY=192.168.88.1 TYPE=Ethernet [root@cloud network-scripts]# Then apply the new network configuration by restarting the network. [root@cloud network-scripts]# /etc/init.d/network restart Shutting down interface eth0: Shutting down loopback interface: Bringing up loopback interface: Bringing up interface eth0: [root@cloud network-scripts]# [ [ [ [ OK OK OK OK ] ] ] ] Now setup the static ip-address (in this HowTo “192.168.88.6”) and hostname in /etc/hosts. Please make sure that the hostname (in this Howto “cloud”) does not appear in the line starting with 127.0.0.1. [root@cloud ~]# cat /etc/hosts # Do not remove the following line, or various programs # that require network functionality will fail. 127.0.0.1 localhost.localdomain localhost 192.168.88.6 cloud ::1 localhost6.localdomain6 localhost6 [root@cloud ~]# Now prepare the dedicated partition to be used with lvm, then create a logical volume group “vol”. [root@cloud ~]# pvcreate /dev/hda3 Physical volume "/dev/hda3" successfully created [root@cloud ~]# vgcreate vol /dev/hda3 Volume group "vol" successfully created [root@cloud ~]# vgs VG #PV #LV #SN Attr VSize VFree vol 1 0 0 wz--n- 186.22G 186.22G [root@cloud ~]# 3 of 95 20.allow' `etc/targets.gz [root@cloud ietd]# cd iscsitarget-1.conf.1/kernel/iscsi_trgt.org ~]# > /etc/ietd.1.c Applying Patch compat-2.4.4.1.4.20.1/iscsitarget-1.allow' -> `/etc/iet/initiators.1/kernel/iscsi_trgt.3.conf.tar.8' `doc/manpages/ietd.patch patching file kernel/conn.initiators' `kernel/iscsi_trgt.6.gz from http://iscsitarget.5' -> `/usr/share/man/man5/ietd.vmware' -> `/usr/share/doc/iscsitarget/README.18-194.. <snip> 2002-06-10 20:41:12 (245 KB/s) .initiators' -> `/usr/share/doc/iscsitarget/README.conf ~]# Start the iSCSI-Target : [root@cloud ~]# /etc/init.conf' -> `/etc/iet/ietd.1..gz/ .20.`iscsitarget-1.conf.4.6.8' -> `/usr/share/man/man8/ietd.tar.1]# make install `usr/ietd' -> `/usr/sbin/ietd' `usr/ietadm' -> `/usr/sbin/ietadm' `etc/initd/initd.8' `doc/manpages/ietd.20.conf ~]# ln -s /etc/ietd.net/projects/iscsitarget/files/iscsitarget/1.ko make[1]: Leaving directory `/usr/src/kernels/2..20.el5-i686' Install : [root@cloud iscsitarget-1. stage 2.patch .allow' `doc/manpages/ietadm.3.4.20.18-194.net/] : [root@cloud ~]# mkdir ietd [root@cloud ~]# cd ietd/ [root@cloud ietd]# wget http://sourceforge.ko' -> `/lib/modules/2.4..gz' saved [137487/137487] [root@cloud ietd]# tar -xzf iscsitarget-1.1.1]# Adapt compatibility for the ietd.Since CentOS does not provide a standard rpm package for the “ietd” (Enterprise iSCSI Target) this needs to be build from the sources..6. MODPOST CC /root/ietd/iscsitarget-1.ko' Running depmod [root@cloud iscsitarget-1.1 Compile : [root@cloud iscsitarget-1.conf /etc/iet/ietd.20.4.32.d/iscsi-target start Starting iSCSI Target: [root@cloud ~]# [ OK ] 4 of 95 . <snip> Complete! [root@cloud ~]# Create ietd dir and download and unpack latest iscsi-target-[version].4.tar. <snip> CC [M] /root/ietd/iscsitarget-1.4..1]# make Applying Patch compat-2.20.redhat' -> `/etc/init.20.o LD [M] /root/ietd/iscsitarget-1.vmware' `README.8' -> `/usr/share/man/man8/ietadm.tar..31.sourceforge.1/kernel/iscsi_trgt.5' install: creating directory `/usr/share/doc/iscsitarget' `ChangeLog' -> `/usr/share/doc/iscsitarget/ChangeLog' `COPYING' -> `/usr/share/doc/iscsitarget/COPYING' `RELEASE_NOTES' -> `/usr/share/doc/iscsitarget/RELEASE_NOTES' `README' -> `/usr/share/doc/iscsitarget/README' `README.4.sourceforge.6.20.d/iscsi-target' install: creating directory `/etc/iet' `etc/ietd.conf configfile location : [root@cloud [root@cloud [root@cloud [root@cloud ~]# mv /etc/iet/ietd.o Building modules.o LD [M] /root/ietd/iscsitarget-1.20.mod.20.allow' -> `/etc/iet/targets..el5/extra/iscsi/iscsi_trgt.1.net/ [http://iscsitarget.conf /etc/iet/ietd..1/kernel/seq_list. [root@cloud ~]# yum -y install kernel-devel openssl-devel gcc rpm-build Loaded plugins: fastestmirror Loading mirror speeds from cached hostfile .conf' `etc/initiators.4.4. Your MySQL connection id is 2 Server version: 5... 100521 14:44:53 [Warning] option 'max_join_size': unsigned value 18446744073709551615 100521 14:44:53 [Warning] option 'max_join_size': unsigned value 18446744073709551615 OK To start mysqld at boot time you have to copy support-files/mysql.server to the right place for your system PLEASE REMEMBER TO SET A PASSWORD FOR THE MySQL root USER ! To do so. 100521 14:44:53 [Warning] option 'max_join_size': unsigned value 18446744073709551615 100521 14:44:53 [Warning] option 'max_join_size': unsigned value 18446744073709551615 OK Filling help tables.77 Source distribution Type 'help. You can start the MySQL daemon with: cd /usr ..com [ OK ] Starting MySQL: [ OK ] [root@cloud ~]# adjusted to 4294967295 adjusted to 4294967295 adjusted to 4294967295 adjusted to 4294967295 Now check that you can connect to it : [root@cloud ~]# mysql Welcome to the MySQL monitor. mysql> quit Bye [root@cloud ~]# Add mysqld to init via chkconfig : [root@cloud [root@cloud [root@cloud mysqld [root@cloud bin]# chkconfig --add mysqld bin]# chkconfig mysqld on bin]# chkconfig --list mysqld 0:off 1:off 2:on bin]# 3:on 4:on 5:on 6:off 5 of 95 ..pl cd mysql-test . start the server. then issue the following commands: /usr/bin/mysqladmin -u root password 'new-password' /usr/bin/mysqladmin -u root -h cloud password 'new-password' Alternatively you can run: /usr/bin/mysql_secure_installation which will also give you the option of removing the test databases and anonymous user created by default. perl mysql-test-run. [root@cloud ~]# yum -y install mysql-server Loaded plugins: fastestmirror Loading mirror speeds from cached hostfile . Type '\c' to clear the buffer.' or '\h' for help.com Support MySQL by buying support/licenses at http://shop.. or \g. This is strongly recommended for production servers..mysql.mysql. /usr/bin/mysqld_safe & You can test the MySQL daemon with mysql-test-run.. <snip> Complete! [root@cloud ~]# After install start the mysqld service : [root@cloud ~]# /etc/init.0. See the manual for more instructions.pl Please report any problems with the /usr/bin/mysqlbug script! The latest information about MySQL is available on the web at http://www. Commands end with .d/mysqld start Initializing MySQL database: Installing MySQL system tables.For the openQRM Server Database backend please install the “mysql-server” package. 6/source/openqrm-thirdparty-cache. tar. <snip> [root@cloud src]# All compilation results are cached by the openQRM build-system.svn. patch found make installed found gcc installed found portmap installed found rsync installed found zlib-devel installed found wget installed found tar installed found bzip2 installed found unzip installed found patch installed openqrm-plugin-aoe-storage requires: openqrm-plugin-aws requires: openqrm-plugin-citrix requires: openqrm-plugin-cloud requires: openqrm-plugin-collectd requires: openqrm-plugin-dhcpd requires: openqrm-plugin-dns requires: openqrm-plugin-equallogic-storage requires: openqrm-plugin-highavailability requires: openqrm-plugin-image-shelf requires: openqrm-plugin-iscsi-storage requires: openqrm-plugin-kvm requires: openqrm-plugin-kvm-storage requires: openqrm-plugin-linux-vserver requires: openqrm-plugin-linuxcoe requires: openqrm-plugin-local-server requires: openqrm-plugin-local-storage requires: openqrm-plugin-lvm-storage requires: openqrm-plugin-nagios2 requires: openqrm-plugin-nagios3 requires: openqrm-plugin-netapp-storage requires: openqrm-plugin-nfs-storage requires: openqrm-plugin-puppet requires: openqrm-plugin-sanboot-storage requires: openqrm-plugin-solx86 requires: 6 of 95 ..We build openQRM from the sources which are available in the openQRM Projects subversion repository. unzip.sourceforge.. The second (and every further “make” run) will just takes a few seconds. zlib-devel.. gcc..6/source/openqrm-thirdparty-cache. [root@cloud ~]# cd openqrm/trunk/src/ [root@cloud src]# And run “make”.tgz/download] and unzip it in your home directory. [root@cloud src]# make . Please notice that this step requires a working internet connection... [root@cloud ~]# svn co https://openqrm. This build-cache then will avoid any downloads. The only requirement for that is to have “subversion (client)” and “make” available so please install both components. wget. portmap. To ensure all components are build correctly simply run “make” again. If no internet is available on this system you can download http://sourceforge. bzip2.spec A openqrm/branches A openqrm/tags Checked out revision 1996. <snip> A openqrm/trunk/src/rpm/README A openqrm/trunk/src/rpm/openqrm-entire...tgz/download [http://sourceforge. [root@cloud ~]# yum -y install subversion Loaded plugins: fastestmirror Loading mirror speeds from cached hostfile . [root@cloud ~]# Change to the src/ dir.. Here how the console output looks like for the second “make” run : [root@cloud src]# make Checking requirements for the compilation phase openqrm-server requires: make. <snip> Complete! [root@cloud ~]# Now checkout the openQRM sources from the svn repository.net/projects/openqrm/files/openQRM-4.net/projects/openqrm/files/openQRM-4. rsync.net/svnroot/openqrm openqrm . kpxe.ubuntu. taking the ready built component from the cache Adding /sbin/portmap to default initrd-template Adding /sbin/rpc.ubuntu.statd to default initrd-template Adding /bin/bash to default initrd-template Adding /usr/bin/rsync to default initrd-template Adding /usr/bin/wget to default initrd-template Adding /sbin/modprobe to default initrd-template Adding /sbin/depmod to default initrd-template Adding /sbin/insmod to default initrd-template Adding /sbin/lsmod to default initrd-template Adding /sbin/mke2fs to default initrd-template Adding /sbin/sfdisk to default initrd-template Adding /sbin/udevd to default initrd-template Adding /lib/udev/vol_id to default initrd-template -> found component gpxe (undionly.6.debian. <snip> Creating the openqrm-client boot-service package [root@cloud src]# 7 of 95 .tgz) already downloaded -> found component openqrm-client.6.i386 (openqrm-initrd-template..1.4.i386.ubuntu.i386.4.1-setup.tgz) already downloaded -> found component openqrm-client.4.centos.tgz) already download -> found component openqrm-initrd-template.6.centos.1.x86_64.14.tgz) already downloaded -> found component adodb (adodb498. then mkdir -p .exe) already downloaded -> found component sshterm-component (openqrm-plugin-sshterm-components-1.1.9./thirdparty ].x86_64 (openqrm-client.windows (openQRM-Client-4..x86_64 (openqrm-initrd-template.tgz) already download -> found component openqrm-initrd-template.4.6.x86_64 (openqrm-client.x86_64 (openqrm-client.1.x86_64.i386 (openqrm-client.bz2) already downloaded -> Found busybox-1.6.exe) already downloaded -> found component sshterm-component (openqrm-plugin-sshterm-components-1. fi -> found component gpxe (undionly.1.x86_64.x86_64. taking the ready built component from the cache -> found component pciutils (pciutils-3.tgz) already downloaded -> found component openqrm-client.tar.tgz) already downloaded -> found component openqrm-initrd-template.debian.i386.x86_64 (openqrm-initrd-template.tgz) already downloaded -> found component openqrm-initrd-template.2/_install/bin/busybox already in the build-cache -> Skipping compilation.i386..gz) already downloaded -> Found pciutils-3.2.1.6.4.kpxe.ubuntu.i386 (openqrm-client.openqrm-plugin-sshterm requires: openqrm-plugin-tftpd requires: openqrm-plugin-tmpfs-storage requires: openqrm-plugin-vbox requires: openqrm-plugin-vmware-esx requires: openqrm-plugin-vmware-server requires: openqrm-plugin-vmware-server2 requires: openqrm-plugin-windows requires: openqrm-plugin-xen requires: openqrm-plugin-xen-storage requires: openqrm-plugin-zabbix requires: openqrm-plugin-zfs-storage requires: Checking for required components to compile openQRM finished successfully if [ -d .tgz) already downloaded -> found component openqrm-initrd-template.tgz) already downloaded -> found component jquery (jquery-1.1.tar.1.0.debian.ubuntu.centos.1.6.tgz) already downloaded -> found component kvm-nic-bios (kvm-nic-bios-1.x86_64.tgz) already download [root@cloud src]# Then run “make install”.tgz) already downloaded Creating the default initrd-template -> found component busybox (busybox-1. cp -aR ./buildtmp/.6.debian.tgz) already downloaded -> found component openqrm-client.zip) already downloaded -> found component openqrm-client.6./thirdparty/* .i386.0.centos.6.2..tgz) already downloaded -> found component openqrm-client.9.4.centos.0.4.i386.centos.centos.6.0.1.1.1.52/dropbear already in the build-cache -> Skipping compilation.tar.14.debian.9.tgz) already downloaded -> found component kvm-nic-bios (kvm-nic-bios-1.x86_64. [root@cloud src]# make install include/ include/openqrm-plugin-local-storage-functions bin/ .windows (openQRM-Client-4.4.debian.4.ubuntu.6.tgz) already downloaded -> found component openqrm-client.52.ubuntu.x86_64 (openqrm-initrd-template.9.4.6.i386 (openqrm-initrd-template.3.1.1.ubuntu.4.tgz) already downloaded -> found component openqrm-client.tgz) already downloaded -> found component js-interface (interface_1.4.debian. taking the ready built component from the cache -> found component dropbear (dropbear-0.4/pcimodules already in the build-cache -> Skipping compilation.i386 (openqrm-initrd-template../buildtmp.1.tgz) already downloaded -> found component openqrm-initrd-template.centos.debian.4.6.2.i386 (openqrm-client.gz) already downloaded -> Found dropbear-0.1.1-setup. conf Checking /usr/share/openqrm/etc/openqrm-server.. Loaded plugins: fastestmirror .... Starting the openQRM-server ver.And finally initialize and start openQRM by “sudo make start”. We are now ready to configure the openQRM Server via the Web-UI. 4. php-soap.d/openqrm-httpd.168..6/openqrm/ -> User: openqrm -> Password: openqrm [root@cloud src]# “make start” triggers a check for the openQRM runtime-dependencies which will install all additional required packages automatically.88.. openssl -> found httpd installed NOTICE: Trying to automatically install php .. screen. 8 of 95 . php.. Running initialization.0 Creating custom apache config. Initialization complete.conf for OP[ OK ]B_PROTOCOL=https.88..6.. Please configure your openQRM Server at: http://192. php-mysql. syslinux.. [root@cloud src]# make start Checking the requirements for RedHat based systems .. Will output 1024 bit rsa secret key to '/usr/share/openqrm/etc/dropbear/dropbear_rsa_host_key' Generating key. this may take a while.0.168. mysql. Looking for syslinux/pxelinux... using 192.. <snip> Checking for required components finished successfully Starting httpd: httpd: Could not reliably determine the server's fully qualified domain name.ssh/authorized_keys. At first start the openQRM Server is initialized. Public key portion is: ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAAAgmOa49UMeOPqid06cR96yfRD/SQ98J1REpLKyyJ518iFFQyGKb9j2quZD+8FfKYt6rgFgS6 kGw95qJf6lqYc/rIH5ezcl4bVCn0Zo9pQkTyF496+iAp6AbPOX9KfBivu+5KWc7sfxOiDWGErPhzTGSkvjxwDAu2PkXAvTjUHMhhXxLk= root@cloud Fingerprint: md5 de:cc:34:cb:2b:e5:b1:3d:50:dd:cc:f0:b5:ca:e9:e5 Adding public key to /root/..6 for Server [ OK ] First startup detected..found: /usr/lib/syslinux/pxelinux. procmail./etc/httpd/conf.Reloading httpd: Adding password for user openqrm Initializing dropbear.. openqrm-server requires: httpd. Login to your openQRM Server at http://-ip-address-/openqrm [http://-ip-address-/openqrm] . User and password is “openqrm”. 9 of 95 . Please make sure to change this default credentials after the configuration phase. First select the first interface (eth0) as the openQRM management network-device. 10 of 95 .The step-by-step Web-based configuration guides you through the setup phase. Then select “myslq” as the Database to use as the openQRM backend. 11 of 95 . And then configure the Database connection credentials. 12 of 95 . 13 of 95 .openQRM is now fully configured and will forward to the Datacenter Dashboard. The openQRM Datacenter Dashboard 14 of 95 . Via the Plugin-manager please enable and start the following plug-ins in the same sequence as listed below : dhcpd tftpd sanboot-storage windows cloud 15 of 95 . Select the openQRM Server “resource” 16 of 95 .After that please go to Base → Components → Create → Storage and create a new Storage from the type “Sanboot-Storage (iSCSI)”. Here just give the Storage Server a name and save. 17 of 95 . Here how the Storage List looks now. 18 of 95 . Click on the “Mgmt” button of the new created “sanboot” Storage Server. 19 of 95 . Please select the “vol” volume group. 20 of 95 . Here how the Volume List looks now.conf Target windowsxp:windowsxp Lun 0 Path=/dev/mapper/vol-windowsxp.Now create a new volume with the name “windowsxp” and the size slightly bigger than the local harddisk of the system which is used to create the windows “image”. In this HowTo a 40GB local disk is used to install and transfer a Windows installation to a Lun on an iSCSI-Target.Type=fileio [root@cloud ~]# Convert 21 of 95 .04G [root@cloud ~]# cat /etc/ietd. The volume we create is 41000MB so a little bit bigger than the actual physical disk. On the console it now looks like : [root@cloud ~]# lvs LV VG Attr LSize Origin Snap% Move Log Copy% windowsxp vol -wi-ao 40. → http://etherboot. Windows 7) can be directly installed on to the iSCSI-Target.org/wiki/sanboot/iscsi_install] 22 of 95 .g.org/wiki/sanboot /winxp [http://etherboot.Install Windows on the local disk of the second system For this HowTo we used Windows XP Professional and exactly followed the GPXE-Instructions at http://etherboot.org/wiki/sanboot/winxp] We recommend to do a fresh install and full format of the local harddisk during the install procedure ! Please notice : The method “install local + transfer to iSCSI Lun” is used because Windows XP does not support to be installed directly on the iSCSI-Target.org /wiki/sanboot/iscsi_install [http://etherboot. Newer versions of Windows (e. org /wiki/sanboot/winnt_iscsi [http://etherboot.x boot-buildxxx-arch/lang. 23 of 95 .After Windows is installed please add the “iSCSI Boot” support. Here we pick the i386/X86 EN one.exe according to your Windows installation.org/wiki/sanboot/winnt_iscsi] On the webpage download the “Initiator 2. Open a web browser and point it to http://etherboot. Download this file to your Desktop. 24 of 95 . 25 of 95 .Please execute it and follow the installation instructions. 26 of 95 27 of 95 28 of 95 29 of 95 . Now please download the Windows SAN Boot Configuration Driver from http://etherboot.org/wiki/sanboot/winnt_sanbootconf] 30 of 95 .org/wiki/sanboot/winnt_sanbootconf [http://etherboot. 31 of 95 . Please double-click and extract it to your Desktop.This file is a ZIP-File containing the SAN Boot driver. Double-click on the extracted directory. 32 of 95 . Double-click the sanbootconf directory. 33 of 95 . Now run the sanbootconf Installer and follow the instructions. 34 of 95 . 35 of 95 .Accept the GNU General Public License. 36 of 95 . 37 of 95 .Installation completed. 168.251 .0 GB.168. bash-3.unixsherpa. Save the changed bios settings and the system will now boot into openQRM as new “idle” resource from the type “Physical System”.11 seconds. (fingerprint md5 ff:5f:e7:60:ae:14:74:4a:39:15:8c:a6:62:98:73:0b) bash-3. 6322. This means the full disk content was transferred to the remote logical volume On the openQRM Server you can use “kill -USR1 [pid-of-dd-process]” to trigger dd to report how many bytes are transferred.Transfer disk content using nc To transfer the disk content of the local install Windows System to the iSCSI Lun on the “Sanboot” Storage Server we are using a simply client-server raw data transfer via the combination of “nc” and “dd”.88.unixsherpa.3 MB/s [root@cloud ~]# Run “sync” to ensure all bits are flushed to the logical volume : [root@cloud ~]# sync [root@cloud ~]# 38 of 95 . start a nc listener on the Windows logical volume [root@cloud ~]# ls /dev/mapper/vol-windowsxp /dev/mapper/vol-windowsxp [root@cloud ~]# nc -l 12345 | dd of=/dev/mapper/vol-windowsxp # this command won't return but listen on port 12345 to submit data # which it reads bitwise from the network port to /dev/mapper/vol-windowsxp 2.com/2009/08/10/remote-mirroring-using-nc-and-dd/ [http://solutions..2# 3. Wait until this command returns. Commands can be run using the full path in the commandline. Please find more details at http://solutions.2# bash-3.88. dd to remote nc listener Use the combination of dd + nc to transfer the disk content to the remote logical volume. When it finished it will look like : ..2# Please notice that this shell does not have a PATH environment var set.2# /sbin/fdisk -l /dev/sda Disk /dev/sda: 40. 78165360+0 records in 78165360+0 records out 40020664320 bytes (40 GB) copied. Here how to identify the local disk with the windows installation bash-3. 63 sectors/track.168.6 12345 Please notice that this can take a while depending on the disk size and network speed.2# dd if=/dev/sda | nc 192./openqrm login -i 192.2# cat /proc/partitions major minor #blocks name 8 0 39082680 sda 8 1 39070048 sda1 bash-3.168. 4865 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Device Boot Start End Blocks Id System /dev/sda1 * 1 4864 39070048+ 7 HPFS/NTFS bash-3. When the system is in the “idle” state please follow the steps below to transfer the disk-content from the physical windows system to the iSCSI Lun : 1. 6.. Host '192.251 Login to resource 192. 40020664320 bytes 255 heads.88. login via the “openqrm login” command Here the syntax of the “openqrm login” comand : /usr/share/openqrm/bin/openqrm login -i [ip-address-of-the-idle-resource-withe-the-windows-installed-on-local-disk] [root@cloud ~]# cd /usr/share/openqrm/bin/ [root@cloud bin]# .com/2009/08/10/remotemirroring-using-nc-and-dd/] After the Windows installation reboot the system and configure the boot-sequence in its BIOS to start from network (pxe-boot).88.251' key accepted unconditionally. 39 of 95 . remove the disk and reboot it through network. When the system fully rebooted to “idle” state again create logical “image” in openQRM. Please notice : Make sure to have the BIOS boot-sequence set to network-boot only.Poweroff the “idle” resource (the one with the windows installation on the local disk). Go to Base → Components → Create → Image and select the “Sanboot” Storage Server. 40 of 95 . 41 of 95 .Give a name for the “image” and select the “windowsxp” volume as the root-device. Here how the “image” list will look like now. 42 of 95 .Save the image. Please go to Base → Appliance → Create and select the “idle” resource. 43 of 95 .Now create an “appliance”. Save the appliance. 44 of 95 . select the “default” kernel and the “windowsxp” image.Name the “appliance” windowsxp. Start “appliance” 45 of 95 Please find a video of the full boot-up sequence of the Windows system booting from the remote iSCSI Storage Server at Youtube - http://www.youtube.com/watch?v=IwnyUgS--w4 [http://www.youtube.com/watch?v=IwnyUgS--w4] The Windows “image” is deployed and working fine now. Still we need to further pre-configure it to enable management through openQRM. First step it to create a Windows User “root” on the deployed Windows “image”. 46 of 95 47 of 95 Next step is to Install openQRM-Client on the Windows “image” Please open a Web-Browser and login to the openQRM Server. 48 of 95 . Go to Plugins → Deployment → Windows → About 49 of 95 . 50 of 95 .and download the Windows openQRM-Client Installer. Run the openQRM-Client Installer and follow the instructions. 51 of 95 . 52 of 95 . 53 of 95 . 54 of 95 . 55 of 95 . 56 of 95 . 57 of 95 . 58 of 95 . 59 of 95 . 60 of 95 . 61 of 95 . 62 of 95 . 63 of 95 . 64 of 95 . 65 of 95 . 66 of 95 . 67 of 95 . 68 of 95 . 69 of 95 . 70 of 95 . 71 of 95 . 72 of 95 . msc” and add the permission to “remote shutdown” to user “root”.Now please run “gpedit. 73 of 95 . 74 of 95 . Please notice : If the Windows Firewall is active you need to also open TCP port 22 ! 75 of 95 . openQRM can now manage this Windows “image”. 76 of 95 .After installation of the openQRM-Client on the deployed Windows “image” the “resource” get active in openQRM. After that please go to Plugins → Cloud → Configuration → Main Config and configure the following items : cloud_admin_email → your valid email address (may be a local address depending on your postfix setup) auto_provision → true external_portal_url → (optional) external Cloud Portal URL request_physical_systems → yes auto_give_ccus → 100 show_disk_resize → (optional) true show_private_image → true cloud_selector → true cloud_currency → (optional) set to US or Euro cloud_1000_ccus → How much 1000 CCUs are worh in US/Euro For all other configuration items you can continue with the defaults. Here a screenshot of the Main Cloud Configuration page : 77 of 95 . Save your configuration. 78 of 95 .Next step is to configure the Cloud Products via the “Cloud-Selector”. 79 of 95 .Go to Plugins → Cloud → Configuration → Products → Kernel and create a new “Windows” kernel product. It will look like this. 80 of 95 . Now create a “Memory” product with the exact size of the memory available on the 2. Please adjust the memory size according to your physical system. In this HowTo we used a system with 3008MB physical memory. physical system (the system the windows “image” ig going to be deployed to). 81 of 95 . 82 of 95 .It will look like this. Now create a “Physical System” virtualization product. 83 of 95 . 84 of 95 .It will look like this. 85 of 95 .The next step is to tell the Cloud which “images” to show to the CloudUsers. Go to Plugins → Cloud → Configuration → Private Images and select “All” in the checkboxes for the windowsxp “image”. 86 of 95 .Following step is to create one or more CloudUser. Go to Plugins → Cloud → User and add a new Clouduser with a valid email address. The CloudUser List now looks like the screenshot below. As the Cloud-Administrator you can simply login as a specific CloudUser by clicking on the CloudUser name. 87 of 95 . This is the openQRM Cloud-Portal after login : 88 of 95 . Tab “Visual Cloud Designer” 89 of 95 .Click on the 2. 90 of 95 .The Visual Cloud Designer shows all components available in the Cloud. You can now start constructing your Cloud-Appliance by drag-and-drop. 91 of 95 . Then check the costs for this Appliance (hourly. daily and monthly). 92 of 95 . And with a single click request this custom system from the openQRM Cloud. 93 of 95 . On the console this looks like : [root@cloud ~]# lvs LV VG Attr LSize Origin Snap% Move Log Copy% 2.53G windowsxp 0. In the Storage Manager the Cloud-Volume is marked with the “s” (snapshot) attribute.For Cloud deployment openQRM automatically creates a LVM snapshot of the origin Windows “image”.04G [root@cloud ~]# Convert License thoughts : Please notice that you are responsible to take care of Windows License management when you are deploying multiply snapshots of the Windows OS ! 94 of 95 .cloud_1_1_ vol swi-ao 19. That means that the (remote) hard-disk of the Windows “image” is actually a LVM snapshot.06 windowsxp vol owi-ao 40. com/news/details /article/in-depth-documentation-of-openqrm-available.com] This HowTo is brought to you by openQRM Enterprise [http://www. There is also an active community maintaining the forums and mailing-lists of the openQRM Project.openqrm-enterprise. Matthias Rechenburg [email protected] [http://www.com] Copyright 2010.openqrm-enterprise.html] .openqrm-enterprise.com [http://www.openqrm-enterprise. flexible and robust openQRM managed Datacenter Environment is the detailed technical documentation available at http://www.Using Sanboot-storage with AOE deployment Separating Storage and openQRM on dedicated Systems openQRM Server HA Setup Adding Virtualization Host from different types Adding more Physical Systems Adding more Storage Systems Enabling automatic Monitoring IP- and Network-Management Cloud-Billing Cloud Integration / SOAP WebService … and more The best source of informations how to scale your basic openQRM Setup to a distributed.com [mailto:[email protected] 95 of 95 . For professional services and support please contact openQRM Enterprise .com/news/details/article/in-depthdocumentation-of-openqrm-available.com/] openQRM Enterprise GmbH Berrenrather Straße 188c 50937 Köln / Germany Telefon : +49 (0) 221 995589-10 Fax : +49 (0) 221 995589-20 Mail : [email protected]. http://www.
Report "Openqrm Cloud Howto Deploying Physical Windows Systems on Centos 5.5"