Updated Branches: refs/heads/master fddbcd004 -> a2dcc8335
CLOUDSTACK-1001 Project: http://git-wip-us.apache.org/repos/asf/cloudstack-docs/repo Commit: http://git-wip-us.apache.org/repos/asf/cloudstack-docs/commit/a2dcc833 Tree: http://git-wip-us.apache.org/repos/asf/cloudstack-docs/tree/a2dcc833 Diff: http://git-wip-us.apache.org/repos/asf/cloudstack-docs/diff/a2dcc833 Branch: refs/heads/master Commit: a2dcc8335a95f4f9ebaa7e955ea67f0080266efe Parents: fddbcd0 Author: radhikap <radhika.puthiyet...@citrix.com> Authored: Fri Jan 17 14:07:10 2014 +0530 Committer: radhikap <radhika.puthiyet...@citrix.com> Committed: Fri Jan 17 14:07:10 2014 +0530 ---------------------------------------------------------------------- en-US/about-hosts.xml | 15 ++-- en-US/about-primary-storage.xml | 25 +++--- en-US/about-secondary-storage.xml | 2 +- en-US/hyperv-checklist.xml | 92 +++++++++++++------- en-US/hyperv-host-add.xml | 8 +- en-US/hyperv-install-network.xml | 5 ++ en-US/hyperv-install-steps.xml | 79 +++++++++++++++++ en-US/hyperv-install-storage.xml | 19 ++-- en-US/hyperv-requirements.xml | 14 --- en-US/hyperv-topology-req.xml | 25 ++++++ en-US/hypervisor-support-for-primarystorage.xml | 15 ++++ en-US/management-server-install-systemvm.xml | 4 + en-US/primary-storage-add.xml | 4 +- 13 files changed, 232 insertions(+), 75 deletions(-) ---------------------------------------------------------------------- http://git-wip-us.apache.org/repos/asf/cloudstack-docs/blob/a2dcc833/en-US/about-hosts.xml ---------------------------------------------------------------------- diff --git a/en-US/about-hosts.xml b/en-US/about-hosts.xml index 87b6bab..4264cc8 100644 --- a/en-US/about-hosts.xml +++ b/en-US/about-hosts.xml @@ -24,23 +24,26 @@ <section id="about-hosts"> <title>About Hosts</title> - <para>A host is a single computer. Hosts provide the computing resources that run the guest virtual machines. Each host has hypervisor software installed on it to manage the guest VMs. For example, a Linux KVM-enabled server, a Citrix XenServer server, and an ESXi server are hosts.</para> - <para>The host is the smallest organizational unit within a &PRODUCT; deployment. Hosts are contained within clusters, clusters are contained within pods, and pods are contained within zones.</para> + <para>A host is a single computer. Hosts provide the computing resources that run guest virtual + machines. Each host has hypervisor software installed on it to manage the guest VMs. For + example, a host can be a Citrix XenServer server, a Linux KVM-enabled server, an ESXi server, or + a Windows Hyper-V server.</para> + <para>The host is the smallest organizational unit within a &PRODUCT; deployment. Hosts are contained within clusters, clusters are contained within pods, pods are contained within zones, and + zones can be contained within regions.</para> <para>Hosts in a &PRODUCT; deployment:</para> <itemizedlist> - <listitem><para>Provide the CPU, memory, storage, and networking resources needed to host the virtual - machines</para></listitem> + <listitem><para>Provide the CPU, memory, storage, and networking resources needed to host the virtual machines</para></listitem> <listitem><para>Interconnect using a high bandwidth TCP/IP network and connect to the Internet</para></listitem> <listitem><para>May reside in multiple data centers across different geographic locations</para></listitem> <listitem><para>May have different capacities (different CPU speeds, different amounts of RAM, etc.), although the hosts within a cluster must all be homogeneous</para></listitem> </itemizedlist> <para>Additional hosts can be added at any time to provide more capacity for guest VMs.</para> - <para>&PRODUCT; automatically detects the amount of CPU and memory resources provided by the Hosts.</para> + <para>&PRODUCT; automatically detects the amount of CPU and memory resources provided by the hosts.</para> <para>Hosts are not visible to the end user. An end user cannot determine which host their guest has been assigned to.</para> <para>For a host to function in &PRODUCT;, you must do the following:</para> <itemizedlist> <listitem><para>Install hypervisor software on the host</para></listitem> <listitem><para>Assign an IP address to the host</para></listitem> - <listitem><para>Ensure the host is connected to the &PRODUCT; Management Server</para></listitem> + <listitem><para>Ensure the host is connected to the &PRODUCT; Management Server.</para></listitem> </itemizedlist> </section> http://git-wip-us.apache.org/repos/asf/cloudstack-docs/blob/a2dcc833/en-US/about-primary-storage.xml ---------------------------------------------------------------------- diff --git a/en-US/about-primary-storage.xml b/en-US/about-primary-storage.xml index 21f030d..ca319c6 100644 --- a/en-US/about-primary-storage.xml +++ b/en-US/about-primary-storage.xml @@ -24,25 +24,24 @@ <section id="about-primary-storage"> <title>About Primary Storage</title> - <para>Primary storage is associated with a cluster and/or a zone. It stores the disk volumes for all of the VMs running on hosts in that cluster. You can add multiple primary storage servers to a cluster or a zone (at least one is required at the cluster level). Primary storage is typically located close to the hosts for increased performance. &PRODUCT; manages the allocation of guest virtual disks to particular primary storage devices.</para> - <para>Primary storage uses the concept of a storage tag. A storage tag is a label that is used to identify the primary storage. Each primary storage can be associated with zero, one, or more storage tags. When a VM is spun up or a data disk attached to a VM for the first time, these tags, if supplied, are used to determine which primary storage can support the VM or data disk (ex. say you need to guarantee a certain number of IOPS to a particular volume).</para> - <para>Primary storage can be either static or dynamic. Static primary storage is what CloudStack - has traditionally supported. In this model, the administrator must present CloudStack with a - certain amount of preallocated storage (ex. a volume from a SAN) and CloudStack can place many - of its volumes on this storage. In the newer, dynamic model, the administrator can present - CloudStack with a storage system itself (ex. a SAN). CloudStack, working in concert with a - plug-in developed for that storage system, can dynamically create volumes on the storage system. - A valuable use for this ability is Quality of Service (QoS). If a volume created in CloudStack - can be backed by a dedicated volume on a SAN (i.e. a one-to-one mapping between a SAN volume and - a CloudStack volume) and the SAN provides QoS, then CloudStack can provide QoS.</para> + <para>Primary storage is associated with a cluster or (in KVM and VMware) a zone, and it stores + the disk volumes for all the VMs running on hosts.</para> + <para>You can add multiple primary storage servers to a cluster or zone. At least one is + required. It is typically located close to the hosts for increased performance. + &PRODUCT; manages the allocation of guest virtual disks to particular primary storage devices.</para> + <para>It is useful to set up zone-wide primary storage when you want to avoid extra data copy + operations. With cluster-based primary storage, data in the primary storage is directly + available only to VMs within that cluster. If a VM in a different cluster needs some of the + data, it must be copied from one cluster to another, using the zone's secondary storage as an + intermediate step. This operation can be unnecessarily time-consuming.</para> <para>For Hyper-V, SMB/CIFS storage is supported. Note that Zone-wide Primary Storage is not supported in Hyper-V.</para> <para>&PRODUCT; is designed to work with all standards-compliant iSCSI and NFS servers that are supported by the underlying hypervisor, including, for example:</para> <itemizedlist> - <listitem><para>SolidFire for iSCSI</para></listitem> <listitem><para>Dell EqualLogic⢠for iSCSI</para></listitem> <listitem><para>Network Appliances filers for NFS and iSCSI</para></listitem> <listitem><para>Scale Computing for NFS</para></listitem> </itemizedlist> - <para>If you intend to use only local disk for your installation, you can skip to Add Secondary Storage.</para> + <para>If you intend to use only local disk for your installation, you can skip adding separate + primary storage.</para> </section> http://git-wip-us.apache.org/repos/asf/cloudstack-docs/blob/a2dcc833/en-US/about-secondary-storage.xml ---------------------------------------------------------------------- diff --git a/en-US/about-secondary-storage.xml b/en-US/about-secondary-storage.xml index 31b67bc..7383825 100644 --- a/en-US/about-secondary-storage.xml +++ b/en-US/about-secondary-storage.xml @@ -44,7 +44,7 @@ object storage in addition to the zone-based NFS Secondary Staging Store. It is not necessary to copy templates and snapshots from one zone to another, as would be required when using zone NFS alone. Everything is available everywhere.</para> - <para>For Hyper-V, SMB/CIFS storage is supported.</para> + <para>For Hyper-V hosts, SMB/CIFS storage is supported.</para> <para>&PRODUCT; provides plugins that enable both OpenStack Object Storage (Swift, <ulink url="http://swift.openstack.org";>swift.openstack.org</ulink>) and Amazon Simple Storage Service (S3) object storage. When using one of these storage plugins, you configure Swift or S3 http://git-wip-us.apache.org/repos/asf/cloudstack-docs/blob/a2dcc833/en-US/hyperv-checklist.xml ---------------------------------------------------------------------- diff --git a/en-US/hyperv-checklist.xml b/en-US/hyperv-checklist.xml index 78545cd..5e7f8fc 100644 --- a/en-US/hyperv-checklist.xml +++ b/en-US/hyperv-checklist.xml @@ -40,44 +40,32 @@ <row> <entry><para>Server Roles</para></entry> <entry><para>Hyper-V</para></entry> - <entry><para>After the Windows Server 2012 R2 installation, ensure that Hyper-V is selected from Server - Roles. For more information, see <ulink + <entry><para>After the Windows Server 2012 R2 installation, ensure that Hyper-V is + selected from Server Roles. For more information, see <ulink url="http://technet.microsoft.com/en-us/library/jj134187.aspx#BKMK_Step2";>Installing Hyper-V</ulink>.</para></entry> </row> <row> - <entry><para>Server Roles</para></entry> - <entry><para>File and Storage Services</para></entry> - <entry><para>After the Windows Server 2012 R2 installation, ensure that File and Storage Services is - selected from Server Roles to create an SMB file share. For more information, see - <ulink url="http://technet.microsoft.com/en-us/library/jj134187.aspx#BKMK_Step3"; - >Creating an SMB File Share Using Server Manager</ulink>.</para></entry> - </row> - <row> <entry><para>Share Location</para></entry> <entry><para>New folders in the /Share directory</para></entry> - <entry><para>The location of the file share for the Hyper-V deployment will be the new folder created in - the \Shares on the selected volume. You can create sub-folders for both &PRODUCT; - Primary and Secondary storage within the share location.</para> - <para>When you select the profile for the file shares, ensure that you select SMB Share - -Applications. This creates the file shares with settings appropriate for - Hyper-V.</para></entry> - </row> - <row> - <entry><para>Preferred DNS Server</para></entry> - <entry><para>The IP address of the Active Directory domain.</para></entry> - <entry><para>While adding an Hyper-V host to the domain, use the domain IP as the DNS - server.</para></entry> + <entry><para>Ensure that folders are created for Primary and Secondary storage. The SMB + share and the hosts should be part of the same domain.</para> + <para>If you are using Windows SMB shre, the location of the file share for the Hyper-V + deployment will be the new folder created in the \Shares on the selected volume. You + can create sub-folders for both &PRODUCT; Primary and Secondary storage within the + share location. When you select the profile for the file shares, ensure that you + select SMB Share -Applications. This creates the file shares with settings appropriate + for Hyper-V.</para></entry> </row> <row> <entry><para>Domain and Hosts</para></entry> <entry><para/></entry> - <entry><para>Hosts should be part of the Active Directory domain.</para></entry> + <entry><para>Hosts should be part of the same Active Directory domain.</para></entry> </row> <row> <entry><para>Hyper-V Users</para></entry> <entry><para>Full control</para></entry> - <entry><para>Full control on the SMB File share.</para></entry> + <entry><para>Full control on the SMB file share.</para></entry> </row> <row> <entry><para>Virtual Switch</para></entry> @@ -96,16 +84,60 @@ configuring &PRODUCT; physical network labels.</para></entry> </row> <row> - <entry><para>Hyper-V Admin User</para></entry> + <entry><para>Hyper-V Domain Users</para></entry> <entry><para/></entry> - <entry><para>Add the Hyper-V administrator to the Hyper-V Administrators - group.</para></entry> + <entry> + <itemizedlist> + <listitem> + <para>Add the Hyper-V domain users to the Hyper-V Administrators group.</para> + </listitem> + <listitem> + <para>A domain user should have full control on the SMB share that is exported for + primary and secondary storage. </para> + </listitem> + <listitem> + <para>This domain user should be part of the Hyper-V Administrators and Local + Administrators group on the Hyper-V hosts that are to be managed by + &PRODUCT;.</para> + </listitem> + <listitem> + <para>The Hyper-V Agent service runs with the credentials of this domain user + account.</para> + </listitem> + <listitem> + <para>Specify the credential of the domain user while adding a host to &PRODUCT; so + that it can manage it.</para> + </listitem> + <listitem> + <para>Specify the credential of the domain user while adding a shared SMB primary or + secondary storage.</para> + </listitem> + </itemizedlist> + </entry> + </row> + <row> + <entry><para>Migration</para></entry> + <entry><para>Migration</para></entry> + <entry><para>Enable Migration.</para> + </entry> </row> <row> + <entry><para>Migration</para></entry> <entry><para>Delegation</para></entry> - <entry><para/></entry> - <entry><para>Enable Delegation to the Microsoft Virtual System Migration - service.</para></entry> + <entry><para>If you want to use Live Migration, enable Delegation. Enable the following services of other + hosts participating in Live Migration: CIFS and Microsoft Virtual System Migration + Service.</para> + </entry> + </row> + <row> + <entry><para>Migration</para></entry> + <entry><para>Kerberos</para></entry> + <entry><para>Enable Kerberos for Live Migration.</para></entry> + </row> + <row> + <entry><para>Network Access Permission for Dial-in</para></entry> + <entry><para>Allow access</para></entry> + <entry><para>Allow access for Dial-in connections.</para></entry> </row> </tbody> </tgroup> http://git-wip-us.apache.org/repos/asf/cloudstack-docs/blob/a2dcc833/en-US/hyperv-host-add.xml ---------------------------------------------------------------------- diff --git a/en-US/hyperv-host-add.xml b/en-US/hyperv-host-add.xml index 144c829..738515e 100644 --- a/en-US/hyperv-host-add.xml +++ b/en-US/hyperv-host-add.xml @@ -27,11 +27,11 @@ <listitem> <para>Before adding a host to the &PRODUCT; configuration, ensure that you install Hyper-V on the host.</para> - <para/> <warning> <para>Be sure you have performed the additional &PRODUCT;-specific configuration steps described in the Hyper-V installation section.</para> </warning> + <para/> </listitem> <listitem> <para>If you have not already done so, install Hyper-V on the host. You will need to know @@ -66,15 +66,15 @@ </para> </listitem> <listitem> - <para><emphasis role="bold">Username</emphasis>: Usually root. Specify domain name in the - path. For example, domain 1/ admin.</para> + <para><emphasis role="bold">Username</emphasis>: Username of the domain user you created. + Specify domain name in the path. For example, domain 1\ admin.</para> </listitem> <listitem> <para><emphasis role="bold">Password</emphasis>: This is the password for the user named above.</para> </listitem> <listitem> - <para><emphasis role="bold">Host Tags</emphasis> (Optional). Any labels that you use to + <para><emphasis role="bold">Host Tags</emphasis> (Optional): Any labels that you use to categorize hosts for ease of maintenance. For example, you can set to the cloud's HA tag (set in the ha.tag global configuration parameter) if you want this host to be used only for VMs with the "high availability" feature enabled. For more information, see http://git-wip-us.apache.org/repos/asf/cloudstack-docs/blob/a2dcc833/en-US/hyperv-install-network.xml ---------------------------------------------------------------------- diff --git a/en-US/hyperv-install-network.xml b/en-US/hyperv-install-network.xml index 5387b5d..1ea2b40 100644 --- a/en-US/hyperv-install-network.xml +++ b/en-US/hyperv-install-network.xml @@ -26,4 +26,9 @@ <para>You should have a plan for how the hosts will be cabled and which physical NICs will carry what types of traffic. By default, &PRODUCT; will use the device that is used for the default route.</para> + <para>If you are using Hyper-V 2012 R2, manually create an external virtual switch before adding + the host to &PRODUCT;. If the Hyper-V host is added to the Hyper-V manager, select the host, + then click Virtual Switch Manager, then New Virtual Switch. In the External Network, select the + desired NIC adapter and click Apply. </para> + <para>If you are using Windows 2012 R2, virtual switch is created automatically.</para> </section> http://git-wip-us.apache.org/repos/asf/cloudstack-docs/blob/a2dcc833/en-US/hyperv-install-steps.xml ---------------------------------------------------------------------- diff --git a/en-US/hyperv-install-steps.xml b/en-US/hyperv-install-steps.xml new file mode 100644 index 0000000..a981862 --- /dev/null +++ b/en-US/hyperv-install-steps.xml @@ -0,0 +1,79 @@ +<?xml version='1.0' encoding='utf-8' ?> +<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd"; [ +<!ENTITY % BOOK_ENTITIES SYSTEM "cloudstack.ent"> +%BOOK_ENTITIES; +]> + +<!-- Licensed to the Apache Software Foundation (ASF) under one + or more contributor license agreements. See the NOTICE file + distributed with this work for additional information + regarding copyright ownership. The ASF licenses this file + to you under the Apache License, Version 2.0 (the + "License"); you may not use this file except in compliance + with the License. You may obtain a copy of the License at + + http://www.apache.org/licenses/LICENSE-2.0 + + Unless required by applicable law or agreed to in writing, + software distributed under the License is distributed on an + "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY + KIND, either express or implied. See the License for the + specific language governing permissions and limitations + under the License. +--> +<section id="hyperv-install-steps"> + <title>Hyper-V Installation Steps</title> + <orderedlist> + <listitem> + <para>Download the operating system from <ulink + url="http://technet.microsoft.com/en-us/windowsserver/hh534429";>Windows Server 2012 + R2</ulink> .</para> + </listitem> + <listitem> + <para>Install it on the host as given in <ulink + url="http://technet.microsoft.com/library/hh831620";>Install and Deploy Windows Server 2012 + R2</ulink>.</para> + </listitem> + <listitem> + <para>Post installation, ensure that you enable Hyper-V role in the server.</para> + </listitem> + <listitem> + <para>If no Active Directory domain exists in your deployment, create one and add users to the + domain.</para> + </listitem> + <listitem> + <para>In the Active Directory domain, ensure that all the Hyper-v hosts are added so that all + the hosts are part of the domain.</para> + </listitem> + <listitem> + <para>Add the domain user to the following groups on the Hyper-V host: Hyper-V Administrators + and Local Administrators.</para> + </listitem> + <listitem> + <para>After installation, perform the following configuration tasks, which are described in + the next few sections.</para> + </listitem> + </orderedlist> + <informaltable> + <tgroup cols="2" align="left" colsep="1" rowsep="1"> + <colspec colwidth="1.0*" colname="1" colnum="1"/> + <colspec colwidth="3.76*" colname="2" colnum="2"/> + <thead> + <row> + <entry><para>Required</para></entry> + <entry><para>Optional</para></entry> + </row> + </thead> + <tbody> + <row> + <entry><para><xref linkend="hyperv-agent-install"/></para></entry> + <entry><para><xref linkend="hyperv-install-storage"/></para></entry> + </row> + <row> + <entry><para><xref linkend="hyperv-install-network"/></para></entry> + <entry><para/></entry> + </row> + </tbody> + </tgroup> + </informaltable> +</section> http://git-wip-us.apache.org/repos/asf/cloudstack-docs/blob/a2dcc833/en-US/hyperv-install-storage.xml ---------------------------------------------------------------------- diff --git a/en-US/hyperv-install-storage.xml b/en-US/hyperv-install-storage.xml index 391a126..d49f285 100644 --- a/en-US/hyperv-install-storage.xml +++ b/en-US/hyperv-install-storage.xml @@ -24,15 +24,24 @@ <section id="hyperv-install-storage"> <title>Storage Preparation for Hyper-V (Optional)</title> <para>&PRODUCT; allows administrators to set up shared Primary Storage and Secondary Storage that - uses CIFS.</para> + uses SMB.</para> <orderedlist> <listitem> - <para>Create a CIFS storage and expose it over smb3.</para> + <para>Create a SMB storage and expose it over SMB Version 3.</para> + <para>For more information, see <ulink + url="http://technet.microsoft.com/en-us/library/jj134187.aspx";>Deploying Hyper-V over + SMB</ulink>.</para> + <para>You can also create and export SMB share using Windows. After the Windows Server 2012 R2 + installation, select File and Storage Services from Server Roles to create an SMB file + share. For more information, see <ulink + url="http://technet.microsoft.com/en-us/library/jj134187.aspx#BKMK_Step3";>Creating an SMB + File Share Using Server Manager</ulink>.</para> </listitem> <listitem> - <para>Add the storage to an Active Directory domain.</para> - <para>The CIFS storage and host need not be in the same domain. However, the storage should be - accessible from the Management Server with the domain user privileges. </para> + <para>Add the SMB share to the Active Directory domain.</para> + <para>The SMB share and the hosts managed by &PRODUCT; need to be in the same domain. However, + the storage should be accessible from the Management Server with the domain user privileges. + </para> </listitem> <listitem> <para>While adding storage to &PRODUCT;, ensure that the correct domain, and credentials are http://git-wip-us.apache.org/repos/asf/cloudstack-docs/blob/a2dcc833/en-US/hyperv-requirements.xml ---------------------------------------------------------------------- diff --git a/en-US/hyperv-requirements.xml b/en-US/hyperv-requirements.xml index 504f2cf..312708d 100644 --- a/en-US/hyperv-requirements.xml +++ b/en-US/hyperv-requirements.xml @@ -66,18 +66,4 @@ </listitem> </itemizedlist> </section> - <section id="other-prereq"> - <title>Miscellaneous Prerequisites</title> - <itemizedlist> - <listitem> - <para>Domain-joined hosts. This is needed for Live Migration.</para> - </listitem> - <listitem> - <para>Permissions are given as given in <xref linkend="hyperv-checklist"/>.</para> - </listitem> - <listitem> - <para>Pure Hyper-V zones</para> - </listitem> - </itemizedlist> - </section> </section> http://git-wip-us.apache.org/repos/asf/cloudstack-docs/blob/a2dcc833/en-US/hyperv-topology-req.xml ---------------------------------------------------------------------- diff --git a/en-US/hyperv-topology-req.xml b/en-US/hyperv-topology-req.xml new file mode 100644 index 0000000..d97dc6e --- /dev/null +++ b/en-US/hyperv-topology-req.xml @@ -0,0 +1,25 @@ +<?xml version='1.0' encoding='utf-8' ?> +<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd"; [ +<!ENTITY % BOOK_ENTITIES SYSTEM "cloudstack.ent"> +%BOOK_ENTITIES; +]> +<!-- Licensed to the Apache Software Foundation (ASF) under one + or more contributor license agreements. See the NOTICE file + distributed with this work for additional information + regarding copyright ownership. The ASF licenses this file + to you under the Apache License, Version 2.0 (the + "License"); you may not use this file except in compliance + with the License. You may obtain a copy of the License at + http://www.apache.org/licenses/LICENSE-2.0 + Unless required by applicable law or agreed to in writing, + software distributed under the License is distributed on an + "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY + KIND, either express or implied. See the License for the + specific language governing permissions and limitations + under the License. +--> +<section id="hyperv-topology-req"> + <title>Hyper-V Topology Requirements</title> + <para>&PRODUCT; Management Server communicates with Hyper-V Agent by using HTTPS. For secure + communication between the Management Server and the Hyper-V host, open port 8250.</para> +</section> http://git-wip-us.apache.org/repos/asf/cloudstack-docs/blob/a2dcc833/en-US/hypervisor-support-for-primarystorage.xml ---------------------------------------------------------------------- diff --git a/en-US/hypervisor-support-for-primarystorage.xml b/en-US/hypervisor-support-for-primarystorage.xml index fdef1f2..8f42749 100644 --- a/en-US/hypervisor-support-for-primarystorage.xml +++ b/en-US/hypervisor-support-for-primarystorage.xml @@ -37,6 +37,7 @@ <entry><para>VMware vSphere</para></entry> <entry><para>Citrix XenServer</para></entry> <entry><para>KVM</para></entry> + <entry><para>Hyper-V</para></entry> </row> </thead> <tbody> @@ -46,36 +47,50 @@ <entry><para>VMDK</para></entry> <entry><para>VHD</para></entry> <entry><para>QCOW2</para></entry> + <entry><para>VHD</para> + <para>Snapshorts are not supported.</para></entry> </row> <row> <entry><para><emphasis role="bold">iSCSI support</emphasis></para></entry> <entry><para>VMFS</para></entry> <entry><para>Clustered LVM</para></entry> <entry><para>Yes, via Shared Mountpoint</para></entry> + <entry><para>No</para></entry> </row> <row> <entry><para><emphasis role="bold">Fiber Channel support</emphasis></para></entry> <entry><para>VMFS</para></entry> <entry><para>Yes, via Existing SR</para></entry> <entry><para>Yes, via Shared Mountpoint</para></entry> + <entry><para>No</para></entry> </row> <row> <entry><para><emphasis role="bold">NFS support</emphasis></para></entry> <entry><para>Y</para></entry> <entry><para>Y</para></entry> <entry><para>Y</para></entry> + <entry><para>No</para></entry> </row> <row> <entry><para><emphasis role="bold">Local storage support</emphasis></para></entry> <entry><para>Y</para></entry> <entry><para>Y</para></entry> <entry><para>Y</para></entry> + <entry><para>Y</para></entry> </row> <row> <entry><para><emphasis role="bold">Storage over-provisioning</emphasis></para></entry> <entry><para>NFS and iSCSI</para></entry> <entry><para>NFS</para></entry> <entry><para>NFS</para></entry> + <entry><para>No</para></entry> + </row> + <row> + <entry><para><emphasis role="bold">SMB/CIFS</emphasis></para></entry> + <entry><para>No</para></entry> + <entry><para>No</para></entry> + <entry><para>No</para></entry> + <entry><para>Yes</para></entry> </row> </tbody> </tgroup> http://git-wip-us.apache.org/repos/asf/cloudstack-docs/blob/a2dcc833/en-US/management-server-install-systemvm.xml ---------------------------------------------------------------------- diff --git a/en-US/management-server-install-systemvm.xml b/en-US/management-server-install-systemvm.xml index 0d930ad..32098b8 100644 --- a/en-US/management-server-install-systemvm.xml +++ b/en-US/management-server-install-systemvm.xml @@ -42,6 +42,10 @@ up to 30 minutes each time it runs.</para> <itemizedlist> <listitem> + <para>For Hyper-V</para> + <programlisting># /usr/share/cloudstack-common/scripts/storage/secondary/cloud-install-sys-tmplt -m /mnt/secondary -u http://download.cloud.com/templates/4.3/systemvm64template-2013-12-23-hyperv.vhd.bz2 -h hyperv -s <optional-management-server-secret-key> -F</programlisting> + </listitem> + <listitem> <para>For XenServer:</para> <programlisting># /usr/lib64/cloud/common/scripts/storage/secondary/cloud-install-sys-tmplt -m /mnt/secondary -u http://download.cloud.com/templates/acton/acton-systemvm-02062012.vhd.bz2 -h xenserver -s <optional-management-server-secret-key> -F</programlisting> </listitem> http://git-wip-us.apache.org/repos/asf/cloudstack-docs/blob/a2dcc833/en-US/primary-storage-add.xml ---------------------------------------------------------------------- diff --git a/en-US/primary-storage-add.xml b/en-US/primary-storage-add.xml index 207debd..48ace2d 100644 --- a/en-US/primary-storage-add.xml +++ b/en-US/primary-storage-add.xml @@ -28,7 +28,7 @@ <para>Hardware requirements:</para> <itemizedlist> <listitem> - <para>Any standards-compliant iSCSI or NFS server that is supported by the underlying + <para>Any standards-compliant iSCSI, SMB, or NFS server that is supported by the underlying hypervisor.</para> </listitem> <listitem> @@ -106,7 +106,7 @@ <listitem> <para><emphasis role="bold">Protocol.</emphasis> For XenServer, choose either NFS, iSCSI, or PreSetup. For KVM, choose NFS or SharedMountPoint. For vSphere choose either - VMFS (iSCSI or FiberChannel) or NFS.</para> + VMFS (iSCSI or FiberChannel) or NFS. For Hyper-V, choose SMB.</para> </listitem> <listitem> <para><emphasis role="bold">Server (for NFS, iSCSI, or PreSetup).</emphasis> The IP
