diff --git a/docs/en-US/citrix-xenserver-installation.xml b/docs/en-US/citrix-xenserver-installation.xml index b8ab5923982..c786b8347d4 100644 --- a/docs/en-US/citrix-xenserver-installation.xml +++ b/docs/en-US/citrix-xenserver-installation.xml @@ -1,5 +1,5 @@ - %BOOK_ENTITIES; ]> @@ -26,123 +26,123 @@ Citrix XenServer Installation for &PRODUCT; If you want to use the Citrix XenServer hypervisor to run guest virtual machines, install XenServer 6.0 or XenServer 6.0.2 on the host(s) in your cloud. For an initial installation, follow the steps below. If you have previously installed XenServer and want to upgrade to another version, see .
- System Requirements for XenServer Hosts - - The host must be certified as compatible with one of the following. See the Citrix Hardware Compatibility Guide: http://hcl.xensource.com + System Requirements for XenServer Hosts - XenServer 5.6 SP2 - XenServer 6.0 - XenServer 6.0.2 + The host must be certified as compatible with one of the following. See the Citrix Hardware Compatibility Guide: http://hcl.xensource.com + + XenServer 5.6 SP2 + XenServer 6.0 + XenServer 6.0.2 + + + You must re-install Citrix XenServer if you are going to re-use a host from a previous install.Must support HVM (Intel-VT or AMD-V enabled) + Be sure all the hotfixes provided by the hypervisor vendor are applied. Track the release of hypervisor patches through your hypervisor vendor’s support channel, and apply patches as soon as possible after they are released. &PRODUCT; will not track or notify you of required hypervisor patches. It is essential that your hosts are completely up to date with the provided hypervisor patches. The hypervisor vendor is likely to refuse to support any system that is not up to date with patches. + All hosts within a cluster must be homogenous. The CPUs must be of the same type, count, and feature flags. + Must support HVM (Intel-VT or AMD-V enabled in BIOS) + 64-bit x86 CPU (more cores results in better performance) + Hardware virtualization support required + 4 GB of memory + 36 GB of local disk + At least 1 NIC + Statically allocated IP Address + When you deploy &PRODUCT;, the hypervisor host must not have any VMs already running - - All hosts must be 64-bit and must support HVM (Intel-VT or AMD-V enabled in BIOS). - All hosts within a cluster must be homogenous. That means the CPUs must be of the same type, count, and feature flags. - You must re-install Citrix XenServer if you are going to re-use a host from a previous install. - 64-bit x86 CPU (more cores results in better performance) - Hardware virtualization support required - 4 GB of memory - 36 GB of local disk - At least 1 NIC - Statically allocated IP Address - Be sure all the hotfixes provided by the hypervisor vendor are applied. Track the release of hypervisor patches through your hypervisor vendor’s support channel, and apply patches as soon as possible after they are released. &PRODUCT; will not track or notify you of required hypervisor patches. It is essential that your hosts are completely up to date with the provided hypervisor patches. The hypervisor vendor is likely to refuse to support any system that is not up to date with patches. For more information, see Highly Recommended Hotfixes for XenServer in the &PRODUCT; Knowledge Base. - - The lack of up-do-date hotfixes can lead to data corruption and lost VMs. + The lack of up-do-date hotfixes can lead to data corruption and lost VMs.
- XenServer Installation Steps - - From https://www.citrix.com/English/ss/downloads/, download the appropriate version of XenServer for your &PRODUCT; version (see ). Install it using the Citrix XenServer Installation Guide. - After installation, perform the following configuration steps, which are described in the next few sections: + XenServer Installation Steps + + From https://www.citrix.com/English/ss/downloads/, download the appropriate version of XenServer for your &PRODUCT; version (see ). Install it using the Citrix XenServer Installation Guide. + After installation, perform the following configuration steps, which are described in the next few sections: - - - - + + + + Required Optional - - - - + + + + - - + + Set up SR if not using NFS, iSCSI, or local disk; see - - + + - - + + - - + + - - + +
- Configure XenServer dom0 Memory - Configure the XenServer dom0 settings to allocate more memory to dom0. This can enable XenServer to handle larger numbers of virtual machines. We recommend 2940 MB of RAM for XenServer dom0. For instructions on how to do this, see http://support.citrix.com/article/CTX126531. The article refers to XenServer 5.6, but the same information applies to XenServer 6.0. + Configure XenServer dom0 Memory + Configure the XenServer dom0 settings to allocate more memory to dom0. This can enable XenServer to handle larger numbers of virtual machines. We recommend 2940 MB of RAM for XenServer dom0. For instructions on how to do this, see http://support.citrix.com/article/CTX126531. The article refers to XenServer 5.6, but the same information applies to XenServer 6.0.
- Username and Password - All XenServers in a cluster must have the same username and password as configured in &PRODUCT;. + Username and Password + All XenServers in a cluster must have the same username and password as configured in &PRODUCT;.
- Time Synchronization - The host must be set to use NTP. All hosts in a pod must have the same time. - - + Time Synchronization + The host must be set to use NTP. All hosts in a pod must have the same time. + + Install NTP. # yum install ntp - - + + Edit the NTP configuration file to point to your NTP server. # vi /etc/ntp.conf Add one or more server lines in this file with the names of the NTP servers you want to use. For example: - -server 0.xenserver.pool.ntp.org + server 0.xenserver.pool.ntp.org server 1.xenserver.pool.ntp.org server 2.xenserver.pool.ntp.org server 3.xenserver.pool.ntp.org - - + + Restart the NTP client. # service ntpd restart - - + + Make sure NTP will start again upon reboot. # chkconfig ntpd on - - + +
- Licensing - Citrix XenServer Free version provides 30 days usage without a license. Following the 30 day trial, XenServer requires a free activation and license. You can choose to install a license now or skip this step. If you skip this step, you will need to install a license when you activate and license the XenServer. -
- Getting and Deploying a License - If you choose to install a license now you will need to use the XenCenter to activate and get a license. - + Licensing + Citrix XenServer Free version provides 30 days usage without a license. Following the 30 day trial, XenServer requires a free activation and license. You can choose to install a license now or skip this step. If you skip this step, you will need to install a license when you activate and license the XenServer. +
+ Getting and Deploying a License + If you choose to install a license now you will need to use the XenCenter to activate and get a license. + In XenCenter, click Tools > License manager. Select your XenServer and select Activate Free XenServer. Request a license. - - You can install the license with XenCenter or using the xe command line tool. -
+ + You can install the license with XenCenter or using the xe command line tool. +
- Install &PRODUCT; XenServer Support Package (CSP) - (Optional) - To enable security groups, elastic load balancing, and elastic IP on XenServer, download and install the &PRODUCT; XenServer Support Package (CSP). After installing XenServer, perform the following additional steps on each XenServer host. - - + Install &PRODUCT; XenServer Support Package (CSP) + (Optional) + To enable security groups, elastic load balancing, and elastic IP on XenServer, download and install the &PRODUCT; XenServer Support Package (CSP). After installing XenServer, perform the following additional steps on each XenServer host. + + Download the CSP software onto the XenServer host from one of the following links: For XenServer 6.0.2: http://download.cloud.com/releases/3.0.1/XS-6.0.2/xenserver-cloud-supp.tgz @@ -150,51 +150,50 @@ server 3.xenserver.pool.ntp.org http://download.cloud.com/releases/2.2.0/xenserver-cloud-supp.tgz For XenServer 6.0: http://download.cloud.com/releases/3.0/xenserver-cloud-supp.tgz - - + + Extract the file: # tar xf xenserver-cloud-supp.tgz - - + + Run the following script: # xe-install-supplemental-pack xenserver-cloud-supp.iso - - + + If the XenServer host is part of a zone that uses basic networking, disable Open vSwitch (OVS): # xe-switch-network-backend bridge Restart the host machine when prompted. - - - The XenServer host is now ready to be added to &PRODUCT;. + + + The XenServer host is now ready to be added to &PRODUCT;.
- Primary Storage Setup for XenServer - &PRODUCT; natively supports NFS, iSCSI and local storage. If you are using one of these storage types, there is no need to create the XenServer Storage Repository ("SR"). - If, however, you would like to use storage connected via some other technology, such as FiberChannel, you must set up the SR yourself. To do so, perform the following steps. If you have your hosts in a XenServer pool, perform the steps on the master node. If you are working with a single XenServer which is not part of a cluster, perform the steps on that XenServer. - - Connect FiberChannel cable to all hosts in the cluster and to the FiberChannel storage host. - + Primary Storage Setup for XenServer + &PRODUCT; natively supports NFS, iSCSI and local storage. If you are using one of these storage types, there is no need to create the XenServer Storage Repository ("SR"). + If, however, you would like to use storage connected via some other technology, such as FiberChannel, you must set up the SR yourself. To do so, perform the following steps. If you have your hosts in a XenServer pool, perform the steps on the master node. If you are working with a single XenServer which is not part of a cluster, perform the steps on that XenServer. + + Connect FiberChannel cable to all hosts in the cluster and to the FiberChannel storage host. + Rescan the SCSI bus. Either use the following command or use XenCenter to perform an HBA rescan. # scsi-rescan - - Repeat step 2 on every host. - + + Repeat step 2 on every host. + Check to be sure you see the new SCSI disk. # ls /dev/disk/by-id/scsi-360a98000503365344e6f6177615a516b -l The output should look like this, although the specific file name will be different (scsi-<scsiID>): - -lrwxrwxrwx 1 root root 9 Mar 16 13:47 + lrwxrwxrwx 1 root root 9 Mar 16 13:47 /dev/disk/by-id/scsi-360a98000503365344e6f6177615a516b -> ../../sdc - - Repeat step 4 on every host. - + + Repeat step 4 on every host. + On the storage server, run this command to get a unique ID for the new SR. # uuidgen The output should look like this, although the specific ID will be different: e6849e96-86c3-4f2c-8fcc-350cc711be3d - - + + Create the FiberChannel SR. In name-label, use the unique ID you just generated. # xe sr-create type=lvmohba shared=true diff --git a/docs/en-US/hypervisor-host-install-overview.xml b/docs/en-US/hypervisor-host-install-overview.xml index 187abea8e4e..716b43ddf91 100644 --- a/docs/en-US/hypervisor-host-install-overview.xml +++ b/docs/en-US/hypervisor-host-install-overview.xml @@ -23,11 +23,11 @@ -->
- Hypervisor Host Installation Overview - This section describes installing a Hypervisor host. This is targeted towards hosts running Linux Kernel Virtual Machine (KVM) + KVM Installation Overview + If you want to use the Linux Kernel Virtual Machine (KVM) hypervisor to run guest virtual machines, install KVM on the host(s) in your cloud. The material in this section doesn't duplicate KVM installation docs. It provides the &PRODUCT;-specific steps that are needed to prepare a KVM host to work with &PRODUCT;. Before continuing, make sure that you have applied the latest updates to your host. It is NOT recommended to run services on this host not controlled by &PRODUCT;. - The procedure for installing the Hypervisor Host is: + The procedure for installing a KVM Hypervisor Host is: Prepare the Operating System Install and configure libvirt diff --git a/docs/en-US/hypervisor-installation.xml b/docs/en-US/hypervisor-installation.xml index 8bfc0c09c9b..cc6a762027a 100644 --- a/docs/en-US/hypervisor-installation.xml +++ b/docs/en-US/hypervisor-installation.xml @@ -26,4 +26,6 @@ Hypervisor Installation + + \ No newline at end of file diff --git a/docs/en-US/hypervisor-kvm-install-flow.xml b/docs/en-US/hypervisor-kvm-install-flow.xml index e2544c19251..fe79e8501d3 100644 --- a/docs/en-US/hypervisor-kvm-install-flow.xml +++ b/docs/en-US/hypervisor-kvm-install-flow.xml @@ -24,6 +24,7 @@
KVM Hypervisor Host Installation + diff --git a/docs/en-US/hypervisor-kvm-requirements.xml b/docs/en-US/hypervisor-kvm-requirements.xml new file mode 100644 index 00000000000..7e7af6afd9f --- /dev/null +++ b/docs/en-US/hypervisor-kvm-requirements.xml @@ -0,0 +1,53 @@ + + +%BOOK_ENTITIES; +]> + + + +
+ System Requirements for KVM Hypervisor Hosts + KVM is included with a variety of Linux-based operating systems. Although you are not required to run these distributions, the following are recommended: + + CentOS / RHEL: 6.3 + Ubuntu: 12.04(.1) + + The main requirement for KVM hypervisors is the libvirt and Qemu version. No matter what + Linux distribution you are using, make sure the following requirements are met: + + libvirt: 0.9.4 or higher + Qemu/KVM: 1.0 or higher + + In addition, the following hardware requirements apply: + + Hosts must be certified as compatible with the selected operating system. For example, see the RHEL Hardware Compatibility Guide at https://hardware.redhat.com/. + Within a single cluster, the hosts must be of the same kernel version. For example, if one host is RHEL6 64 bit, they must all be RHEL6 64 bit. + All hosts within a cluster must be homogenous. The CPUs must be of the same type, count, and feature flags. + Must support HVM (Intel-VT or AMD-V enabled) + 64-bit x86 CPU (more cores results in better performance) + Hardware virtualization support required + 4 GB of memory + 36 GB of local disk + At least 1 NIC + Statically allocated IP Address + Latest hotfixes applied to hypervisor software + When you deploy &PRODUCT;, the hypervisor host must not have any VMs already running + +
\ No newline at end of file diff --git a/docs/en-US/minimum-system-requirements.xml b/docs/en-US/minimum-system-requirements.xml index 422a810f913..7c0f15f9cd9 100644 --- a/docs/en-US/minimum-system-requirements.xml +++ b/docs/en-US/minimum-system-requirements.xml @@ -45,7 +45,7 @@ Host/Hypervisor System Requirements The host is where the cloud services run in the form of guest virtual machines. Each host is one machine that meets the following requirements: - Must be 64-bit and must support HVM (Intel-VT or AMD-V enabled). + Must support HVM (Intel-VT or AMD-V enabled). 64-bit x86 CPU (more cores results in better performance) Hardware virtualization support required 4 GB of memory @@ -54,36 +54,17 @@ Statically allocated IP Address Latest hotfixes applied to hypervisor software When you deploy &PRODUCT;, the hypervisor host must not have any VMs already running + All hosts within a cluster must be homogenous. The CPUs must be of the same type, count, and feature flags. Hosts have additional requirements depending on the hypervisor. See the requirements listed at the top of the Installation section for your chosen hypervisor: Be sure you fulfill the additional hypervisor requirements and installation steps provided in this Guide. Hypervisor hosts must be properly prepared to work with CloudStack. For example, the requirements for XenServer are listed under Citrix XenServer Installation. -
- Citrix XenServer requirements - To be determined -
-
- VMware vSphere requirements - To be determined -
-
- KVM requirements - For running a KVM hypervisor the main requirement is the Linux distribution it is running. Although you are not required to run these distributions, it is recommended. - Recommended distributions: - - CentOS / RHEL: 6.3 - Ubuntu: 12.04(.1) - - The main requirement for KVM hypervisors is the libvirt and Qemu version. If you whish to run on a different distribution, make sure you meet the following requirements: - - libvirt: 0.9.4 or higher - Qemu/KVM: 1.0 or higher - -
-
- Oracle VM (OVM) requirements - To be determined -
+ + + + + +
diff --git a/docs/en-US/ovm-install.xml b/docs/en-US/ovm-install.xml new file mode 100644 index 00000000000..fa4a86b0776 --- /dev/null +++ b/docs/en-US/ovm-install.xml @@ -0,0 +1,29 @@ + + +%BOOK_ENTITIES; +]> + + + +
+ Installing OVM for &PRODUCT; + TODO + +
diff --git a/docs/en-US/ovm-requirements.xml b/docs/en-US/ovm-requirements.xml new file mode 100644 index 00000000000..aadc71f0e2f --- /dev/null +++ b/docs/en-US/ovm-requirements.xml @@ -0,0 +1,28 @@ + + +%BOOK_ENTITIES; +]> + + + +
+ System Requirements for OVM + TODO +
\ No newline at end of file diff --git a/docs/en-US/vmware-install.xml b/docs/en-US/vmware-install.xml new file mode 100644 index 00000000000..211bfe4b316 --- /dev/null +++ b/docs/en-US/vmware-install.xml @@ -0,0 +1,29 @@ + + +%BOOK_ENTITIES; +]> + + + +
+ Installing VMware for &PRODUCT; + TODO + +
\ No newline at end of file diff --git a/docs/en-US/vmware-requirements.xml b/docs/en-US/vmware-requirements.xml new file mode 100644 index 00000000000..8a6479621ce --- /dev/null +++ b/docs/en-US/vmware-requirements.xml @@ -0,0 +1,40 @@ + + +%BOOK_ENTITIES; +]> + + + +
+ System Requirements for VMware + TODO + + Must support HVM (Intel-VT or AMD-V enabled). + 64-bit x86 CPU (more cores results in better performance) + Hardware virtualization support required + 4 GB of memory + 36 GB of local disk + At least 1 NIC + Statically allocated IP Address + Latest hotfixes applied to hypervisor software + When you deploy &PRODUCT;, the hypervisor host must not have any VMs already running + All hosts within a cluster must be homogenous. The CPUs must be of the same type, count, and feature flags. + +
\ No newline at end of file