User Tools
computing:storage:xenserver
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
computing:storage:xenserver [2012/04/15 11:50] gcooper |
— (current) | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | ====== Citrix XenServer ====== | ||
| - | |||
| - | http:// | ||
| - | |||
| - | XenServer is a bare-metal hypervisor, available for free, that is similar to VMware ESXi. | ||
| - | |||
| - | Requires Windows to run the XenCenter management tool. | ||
| - | |||
| - | ===== Official Citrix Resources ===== | ||
| - | |||
| - | Quick Installation Guide: | ||
| - | |||
| - | http:// | ||
| - | |||
| - | Other documentation: | ||
| - | |||
| - | http:// | ||
| - | |||
| - | ===== Updates ===== | ||
| - | |||
| - | * Version upgrades are done with the Rolling Pool Upgrade tool within XenCenter | ||
| - | * Command line updates are more reliable and faster | ||
| - | |||
| - | http:// | ||
| - | |||
| - | < | ||
| - | wget http:// | ||
| - | wget http:// | ||
| - | wget http:// | ||
| - | wget http:// | ||
| - | |||
| - | for x in XS*.zip; do unzip $x; done | ||
| - | |||
| - | for x in *.xsupdate; do xe patch-upload file-name=$x; | ||
| - | </ | ||
| - | |||
| - | Then install the updates one at a time, in order, using the UUID's printed by the last command: | ||
| - | |||
| - | < | ||
| - | xe patch-pool-apply uuid=< | ||
| - | </ | ||
| - | |||
| - | Then reboot the XenServer host: | ||
| - | |||
| - | < | ||
| - | reboot | ||
| - | </ | ||
| - | |||
| - | ==== Multiple XenServers ==== | ||
| - | |||
| - | For a single XenServer, the above commands would suffice when run from the commmand line of the XenServer. | ||
| - | |||
| - | To update multiple XenServers, you would download the updates once, then push them to multiple servers by running additional commands specifying server/ | ||
| - | |||
| - | ===== Remote Access ===== | ||
| - | |||
| - | Remote Access is a weak spot in XenServer since everything is managed by XenCenter (on Windows) and XenCenter doesn' | ||
| - | |||
| - | The easiest way I've found to access the console of a VM running on a XenServer behind NAT is: | ||
| - | |||
| - | - Enable remote SSH access directly to the XenServer | ||
| - | * You can forward a non-standard port at the firewall (22222) to the standard port 22 at the XenServer | ||
| - | - Each VM's VNC console is only available to localhost (the XenServer) | ||
| - | - To access a VM's console, you must tunnel through localhost (the XenServer) | ||
| - | - Use SSH port forwarding to forward a VM's VNC port (5901, 5902, 5903, etc.) to ' | ||
| - | * Each VM runs on a different VNC port | ||
| - | - The IP address of the VM doesn' | ||
| - | |||
| - | You can determine which VNC port is assigned to which VM like this: logged into the XenServer via SSH: | ||
| - | |||
| - | < | ||
| - | ssh -p 22222 -l root -L 5903: | ||
| - | </ | ||
| - | xe vm-list | ||
| - | xe vm-list name-label=" | ||
| - | netstat -lp|grep -w < | ||
| - | </ | ||
| - | |||
| - | Now you can forward the port(s) and access the VNC console of the VM from other terminals on your remote workstation: | ||
| - | |||
| - | < | ||
| - | ssh -p 22222 -l root -L < | ||
| - | |||
| - | vncviewer localhost:< | ||
| - | </ | ||
| - | |||
| - | ===== OpenXenManager ===== | ||
| - | |||
| - | OpenXenManager is a graphical interface to manage XenServer / Xen Cloud Platform (XCP) hosts through the network. OpenXenManager is an open-source multiplatform clone of XenCenter (Citrix). | ||
| - | |||
| - | http:// | ||
| - | |||
| - | ==== Installation ==== | ||
| - | |||
| - | === Ubuntu === | ||
| - | |||
| - | < | ||
| - | sudo apt-get install subversion python-glade2 python-gtk-vnc | ||
| - | cd ~/bin/ | ||
| - | svn co https:// | ||
| - | </ | ||
| - | |||
| - | Launcher command: | ||
| - | |||
| - | < | ||
| - | python ~/ | ||
| - | </ | ||
| - | |||
| - | === Fedora === | ||
| - | |||
| - | < | ||
| - | sudo yum -y install gtk-vnc-python subversion | ||
| - | cd ~/bin/ | ||
| - | svn co https:// | ||
| - | </ | ||
| - | |||
| - | Launcher: | ||
| - | |||
| - | < | ||
| - | python ~/ | ||
| - | </ | ||
| - | |||
| - | ===== Create a new ISO storage repository (New Storage) ===== | ||
| - | |||
| - | ==== CIFS ==== | ||
| - | |||
| - | CIFS -> Centos CIFS ISO library -> \\192.168.0.6\nas_vg_1.nas_vol_1.no_backup\Centos | ||
| - | |||
| - | \\server\share\folder | ||
| - | |||
| - | Set username and password. | ||
| - | |||
| - | ==== NFS ==== | ||
| - | |||
| - | You can't set folders using NFS, only shares, so .iso files must be in the top-level folder with NFS:xe appliance-start uuid=[uuid-vapp] | ||
| - | |||
| - | No_Backup NFS ISO library -> 192.168.0.6:/ | ||
| - | |||
| - | ==== Local Disk ==== | ||
| - | |||
| - | :!: Note that this will probably break and have to be fixed after a version upgrade! | ||
| - | |||
| - | < | ||
| - | mkdir -p / | ||
| - | |||
| - | xe sr-create name-label ="ISO Repository" | ||
| - | </ | ||
| - | |||
| - | You may have to give the new SR a name in XenCenter. | ||
| - | |||
| - | :?: I suspect you would need to recreate the directory and recopy the ISO files to repair after upgrading your XenServer. | ||
| - | |||
| - | ===== Install Guest (New VM) ===== | ||
| - | |||
| - | ==== Centos 5.5 Minimal Netinstall ==== | ||
| - | |||
| - | Start with 5.4 32-bit template and use mostly defaults. | ||
| - | |||
| - | Install from URL: | ||
| - | |||
| - | http:// | ||
| - | |||
| - | http:// | ||
| - | |||
| - | Do NOT start the VM automatically. | ||
| - | |||
| - | Adjust the Description and Storage Name and Storage Description as needed. | ||
| - | |||
| - | Start the VM - be patient because some large files are transferred over the 'net. | ||
| - | |||
| - | ==== Debian 5 (Lenny) Net-Install ==== | ||
| - | |||
| - | URL: | ||
| - | |||
| - | http:// | ||
| - | |||
| - | then: | ||
| - | |||
| - | debian.mirrors.easynews.com | ||
| - | |||
| - | < | ||
| - | apt-get install openssh-server | ||
| - | </ | ||
| - | |||
| - | ==== SME Server 8 Netinstall ==== | ||
| - | |||
| - | URL: | ||
| - | |||
| - | http:// | ||
| - | |||
| - | ===== Install XenServer Tools ===== | ||
| - | |||
| - | In XenCenter, select xs-tools.iso for the DVD drive. | ||
| - | |||
| - | < | ||
| - | mount /dev/xvdd /mnt | ||
| - | cd /mnt/Linux | ||
| - | </ | ||
| - | |||
| - | ==== Ubuntu/ | ||
| - | |||
| - | < | ||
| - | bash install.sh | ||
| - | |||
| - | wget -q http:// | ||
| - | |||
| - | / | ||
| - | </ | ||
| - | |||
| - | ==== SME Server 8 ==== | ||
| - | |||
| - | < | ||
| - | mv / | ||
| - | echo " | ||
| - | / | ||
| - | ln -s / | ||
| - | </ | ||
| - | |||
| - | ===== To get the uuid of the VDI of a specific VM ===== | ||
| - | |||
| - | < | ||
| - | xe vm-disk-list vm= < name of the VM > | ||
| - | </ | ||
| - | |||
| - | ===== Boot Linux to CD-ROM ===== | ||
| - | |||
| - | < | ||
| - | xe vm-list | ||
| - | |||
| - | xe vm-param-set HVM-boot-policy=" | ||
| - | </ | ||
| - | |||
| - | Next, on the " | ||
| - | On the " | ||
| - | |||
| - | Before starting VM, make sure that the ISO that you want is in the VM's DVD-Drive located on the " | ||
| - | |||
| - | Proceed to use SUSE CD-ROM (or DVD) to upgrade, or Linux Rescue media, etc. Once all changes have been made to the VM, you will need to revert back the change to the VM's parameter with the following command: | ||
| - | |||
| - | xe vm-param-set HVM-boot-policy="" | ||
| - | |||
| - | Reboot VM | ||
| - | |||
| - | Final caveat... mouse is unavailable as it is "HVM mode" and no device has been loaded. | ||
| - | |||
| - | ===== Xenserver Backup ===== | ||
| - | |||
| - | See [[XenServer Backup]]. | ||
| - | |||
| - | ===== AoE Storage ===== | ||
| - | |||
| - | See [[computing: | ||
| - | |||
| - | http:// | ||
| - | |||
| - | http:// | ||
| - | |||
| - | ===== High Availability ===== | ||
| - | |||
| - | http:// | ||
| - | |||
| - | * Bonded NICs | ||
| - | * Separate network paths for | ||
| - | * VMs | ||
| - | * Storage | ||
| - | * Management | ||
| - | * 6 NICs per server! | ||
| - | * SAN/[[NAS]] storage | ||
| - | |||
| - | ===== Firewall ===== | ||
| - | |||
| - | XenCenter - Port 443 | ||
| - | |||
| - | http:// | ||
| - | |||
| - | < | ||
| - | iptables -nL -v --line-numbers | ||
| - | </ | ||
| - | |||
| - | ==== NTP ==== | ||
| - | |||
| - | < | ||
| - | iptables -I RH-Firewall-1-INPUT 13 -p udp --dport 123 -j ACCEPT | ||
| - | service iptables save | ||
| - | </ | ||
| - | |||
| - | ==== Sample Firewall ==== | ||
| - | |||
| - | This sample firewall allows NTP and limits access to ports 22, 80 and 443 by the sourde IP. | ||
| - | |||
| - | / | ||
| - | |||
| - | < | ||
| - | # Generated by iptables-save v1.3.5 on Mon Apr 9 00:15:34 2012 | ||
| - | *filter | ||
| - | :INPUT ACCEPT [0:0] | ||
| - | :FORWARD ACCEPT [0:0] | ||
| - | :OUTPUT ACCEPT [135:25337] | ||
| - | : | ||
| - | -A INPUT -j RH-Firewall-1-INPUT | ||
| - | -A FORWARD -j RH-Firewall-1-INPUT | ||
| - | -A RH-Firewall-1-INPUT -i lo -j ACCEPT | ||
| - | -A RH-Firewall-1-INPUT -p icmp -m icmp --icmp-type any -j ACCEPT | ||
| - | -A RH-Firewall-1-INPUT -p esp -j ACCEPT | ||
| - | -A RH-Firewall-1-INPUT -p ah -j ACCEPT | ||
| - | -A RH-Firewall-1-INPUT -d 224.0.0.251 -p udp -m udp --dport 5353 -j ACCEPT | ||
| - | -A RH-Firewall-1-INPUT -p udp -m udp --dport 631 -j ACCEPT | ||
| - | -A RH-Firewall-1-INPUT -p tcp -m tcp --dport 631 -j ACCEPT | ||
| - | -A RH-Firewall-1-INPUT -i xenapi -p udp -m udp --dport 67 -j ACCEPT | ||
| - | -A RH-Firewall-1-INPUT -m state --state RELATED, | ||
| - | -A RH-Firewall-1-INPUT -p udp -m state --state NEW -m udp --dport 694 -j ACCEPT | ||
| - | -A RH-Firewall-1-INPUT -s 209.104.9.32/ | ||
| - | -A RH-Firewall-1-INPUT -s 209.193.64.248/ | ||
| - | -A RH-Firewall-1-INPUT -s 72.200.111.140 -p tcp -m state --state NEW -m tcp --dport 22 -j ACCEPT | ||
| - | -A RH-Firewall-1-INPUT -s 209.193.64.2 -p tcp -m state --state NEW -m tcp --dport 22 -j ACCEPT | ||
| - | -A RH-Firewall-1-INPUT -s 209.104.9.32/ | ||
| - | -A RH-Firewall-1-INPUT -s 209.193.64.248/ | ||
| - | -A RH-Firewall-1-INPUT -s 72.200.111.140 -p tcp -m state --state NEW -m tcp --dport 80 -j ACCEPT | ||
| - | -A RH-Firewall-1-INPUT -s 209.193.64.2 -p tcp -m state --state NEW -m tcp --dport 80 -j ACCEPT | ||
| - | -A RH-Firewall-1-INPUT -p udp -m udp --dport 123 -j ACCEPT | ||
| - | -A RH-Firewall-1-INPUT -s 209.104.9.32/ | ||
| - | -A RH-Firewall-1-INPUT -s 209.193.64.248/ | ||
| - | -A RH-Firewall-1-INPUT -s 72.200.111.140 -p tcp -m state --state NEW -m tcp --dport 443 -j ACCEPT | ||
| - | -A RH-Firewall-1-INPUT -s 209.193.64.2 -p tcp -m state --state NEW -m tcp --dport 443 -j ACCEPT | ||
| - | -A RH-Firewall-1-INPUT -j REJECT --reject-with icmp-host-prohibited | ||
| - | COMMIT | ||
| - | # Completed on Mon Apr 9 00:15:34 2012 | ||
| - | </ | ||
| - | |||
| - | ===== vApp - VM Startup Order ===== | ||
| - | |||
| - | http:// | ||
| - | |||
| - | * vApp Feature introduced in XenServer 6 | ||
| - | * Not currently configurable via the GUI | ||
| - | * By default, vApps won't auto-start on a cold boot | ||
| - | |||
| - | < | ||
| - | xe appliance-list | ||
| - | xe appliance-list < | ||
| - | </ | ||
| - | |||
| - | Add this line to / | ||
| - | |||
| - | < | ||
| - | xe appliance-start uuid=[uuid-vapp] | ||
| - | </ | ||
| - | |||
| - | ===== Resize Virtual Disk ===== | ||
| - | |||
| - | Assumes: | ||
| - | |||
| - | 1. Running LVM in the guest (you can do this without it, but it's difficult). | ||
| - | 2. You're using a filesystem such as Ext3 on the partition you wish to expand which supports online expansion. | ||
| - | 3. You're able to perform a backup just in case something goes wrong. | ||
| - | |||
| - | Steps: | ||
| - | |||
| - | __5-11. Run pvresize / | ||
| - | __ | ||
| - | 1. Shut down the virtual machine from XenCenter. | ||
| - | |||
| - | 2. Resize the VDI from XenCenter to the appropriate size | ||
| - | |||
| - | 3. Start the VM up. | ||
| - | |||
| - | 4. Run "fdisk -l" to locate the virtual disk by looking at the size. | ||
| - | |||
| - | 5. Run "fdisk / | ||
| - | |||
| - | 6. Create a new partition (usually primary) using all available space. The default options will be sufficient. To do this, type " | ||
| - | |||
| - | 7. Reboot the VM again to allow udev to create the appropriate /dev/ node for the partition just created. | ||
| - | |||
| - | 8. Create a new physical volume by running " | ||
| - | |||
| - | 9. Locate the Volume Group containing the partition by running " | ||
| - | |||
| - | 10. Extend your Volume Group with the newly added Physical Volume by running vgextend as shown: | ||
| - | " | ||
| - | |||
| - | 11. Confirm the Volume Group has free storage by running " | ||
| - | |||
| - | 12. Expand the Logical Volume using all available free extents by running: | ||
| - | lvextend -l+100%FREE / | ||
| - | Remember to change VolGroupXX and LogVolYY as appropriate. | ||
| - | |||
| - | 13. Assuming ext3 or ext2 is being used (other filesystems will have their own tools for this purpose), resize the filesystem by running: | ||
| - | resize2fs / | ||
| - | |||
| - | 14. As a precaution, reboot the system again checking the filesystem for errors: | ||
| - | shutdown -r now -F | ||
| - | |||
| - | 15. Observe the output of the " | ||
| - | |||
| - | ===== Guest GUI ===== | ||
| - | |||
| - | ==== X and VNC on XenServer ==== | ||
| - | |||
| - | When you install Redhat on XenServer it does not by default enable a virtual video device. You are only given the text console by default. | ||
| - | |||
| - | Citrix' | ||
| - | |||
| - | Check to make sure that vnc-server and gdm are installed. | ||
| - | |||
| - | < | ||
| - | rpm -q vnc-server gdm | ||
| - | </ | ||
| - | |||
| - | If they are not, install them. | ||
| - | |||
| - | < | ||
| - | yum install vnc-server gdm | ||
| - | </ | ||
| - | |||
| - | Modify ''/ | ||
| - | |||
| - | < | ||
| - | [servers] | ||
| - | 0=VNC | ||
| - | [server-VNC] | ||
| - | name=VNC Server | ||
| - | command=/ | ||
| - | flexible=true | ||
| - | </ | ||
| - | |||
| - | When GDM is running it should be listening on port 5900. Make sure that the iptables firewall allows access to this port from any machine running XenCenter or wanting to connect. | ||
| - | |||
| - | < | ||
| - | iptables -N vnc | ||
| - | iptables -I INPUT -p tcp -m state --state NEW -m tcp --dport 5900 -j vnc | ||
| - | iptables -A vnc -s 134.114.0.0/ | ||
| - | iptables -A vnc -p tcp -m tcp -m state --state NEW --dport 5900 -j REJECT | ||
| - | </ | ||
| - | |||
| - | Now everything is set up, but by default Redhat on XenServer starts up into runlevel 3. This does not by default start GDM. So you can modify the default runlevel in / | ||
computing/storage/xenserver.1334512244.txt.gz · Last modified: 2012/04/15 11:50 by gcooper
Page Tools
Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Share Alike 4.0 International
