source/installguide/locale/zh_CN/LC_MESSAGES/configuration.mo (25 lines of code) (raw):
�� � � � � i � P � X L
! { Z! � �# � �$ S �% V �& j N' p �' i *( � �( � �) 3 K* 7 * + �* � �+ : m, H �, z �, 6 l- p �- � / � �0 � b1 � �2 H �4 � �4 � m6 G 8 ( N8 Z w8 �8 �8 ) 9 7 :9 Q r9 { �9 w @: � �: x 9; z �; a -< E �< � �< � i= � 3> , �> k ? ! x? a �? c �? � `@ %A )B +C a 3D � �D V YE C �F a �F } VG � �G { bH l �H � KI � *J i �J Z dK s �K [ 3L H �L = �L = M � TM � �M � yN O iO � �P � WQ ~ �Q a uR � �R # �S �S � �S 8 VT h �T I �T B BU � �U V .V " KV ! nV W �W �W X %X :X NX a dX a �X 3 (Y E \Y C �Y > �Y C %Z D iZ �Z �Z �Z # �Z [
-[ ;[ \[ t[ �[ �[
�[ 3 �[ � �[ x\ �\ 6 �] � �^ � a_ a �_ - D` ra � �a � .b B �b � *d � �d 7 �e * �e , �e 7 !f Yf C yf / �f , �f g -g 6 =g tg �g > �g �g 5 �g � 0h
�h i i i -i 1 ?i S qi g �i -j < Dj �j �j 1 �j 0 �j = k F Zk �m �m � �m P �n �n ( o K 2o k ~o ^ �o � Ip D �p � @q G �q D !r . fr �r ) �r 5 �r s $s a 0s � �t 1 ;v I mv C �v �v - y � @y l �y ^ 7z * �z � �z � �{ G| M| . k| � �| = J} 4 �} K �} 9 � � C� q Ԁ � F� � D� � ܂ c s� 4 ׃ ( � � 5� � | 5� 2 �� g � � M� z � � }� < � r P� I Ê �
� { �� :� ' R� � z� K ,� j x� 0 � � � 6 ɐ y � � z� � � � �� V� % t� / �� , ʖ � �� � �� � �� + ?� � k� � � � �� , � { 6� = �� � � 4 �� ; ޠ � � 2 ҡ i � 1 o� * �� . ̢ � �� � � � � } �� �
� �� B �� o �� j� " �� * �� , ٦ � � v � � Z� v 8� � �� � R� - �� 2 '� � Z� � � " �� � L �� d B� e �� }
� � �� � @� 0 -� ^� ; b� ) �� + ȱ . �� 1 #� - U� * �� �� E �� S � Q Y� c �� 1 � P A� �� � �� T _� �� P ӵ 5 $� K Z� l �� v � " �� Z �� E � E N� �� � �� 9 G� ( �� + �� 1 ֺ ` � i� y� I �� l ֻ C� ' a� & �� �� } �� { ?� � �� ' ?� ) g� n �� $ � � %� � �� � �� � /� � �� ) �� �� � �� � �� � q� 0 G� � x� � R� � F� y )� � �� � +� q � ^ �� ` �� A P� e �� h �� m a� � �� � � �� 2 N� ' �� � �� E v� B �� A �� T A� � �� ^ m� ] �� � *� � �� J l� I �� � � . �� � �� �� �� - �� �� � � m � � o� ; � � Z� ] 2� � �� � 7� � � � �� V U� b �� � � & �� > �� � &� F �� C � = a� �� �� �� H �� F � f� / n� 4 �� 2 �� 7 � 8 >� . w� 1 �� 1 �� �
� � �� � -� �� �� �� �� � #� *� /� >� D� \� x� �� 0 �� & �� � � $� E� Y� p�
�� ! �� �� g �� 9� J� \� s� �� �� �� �� �� �� �� F � # d� � �� U Y� �� � �� P �� H �� � � � �� �� L �� ] �� X U� S �� � � � �� ' �� + �� � �� � �� 9 ^ E � f � > E { � { � | ^ F ^ � A ~ F ~ � F D " � : � ! � , 7 M E � l � J 8
N �
b �
k 5 R � H � ~ = � � � � - = S k 8 � P � > I � � � p � S 6 ? Q � � � U G L \ � \ � ` N _ � O � _ � � O � M � l $ M � A � : ! 8 \ o � g � m & 6 � ] � � s k! f �! � F" " # C# k `# " �# a �# = Q$ 1 �$ } �$ ?% Q% " n% � �% E $& j& # }& �& �& �& r �& r N' ? �' D ( A F( L �( ? �( D ) Z) j) ) $ �) �) �) ' �) * !* =* ' P* x* ' �* U �* + � + < �+ W 0- ` �- G �- , 1. ^/ G q/ � �/ � J0 � A1 t �1 ) t2 �2 ( �2 3 �2 ! 3 6 93 p3 # �3 �3 �3 6 �3 ] 4 r4 E �4 �4 0 �4 � 5 �5 �5 �5 �5 Z 6 ! i6 T �6 o �6 P7 ? l7 �7 �7 $ �7 8 $ 8 � D8 : $: � 4: N �: E; X; . o; c �; \ < � _< 3 �< � 2= > �= < �= . 6> e> ) �> 6 �> �> �> � �> �? 3 �@ E A 2 MA q �A $ �B q C � �C X D 6 hD � �D � rE F F 0 F � NF 6 �F 5 G 0 FG 5 wH i �H h I � �I � SJ � �J B �K * �K ! %L � GL $M j 4M / �M x �M � HO Q Q u oQ 6 �Q l R a �R � �R q pS � �S � vT � U U �U l V 0 xV � �V � ;W R .X �X �Y � �Z " [ + 2[ * ^[ * �[ � �[ i\ � z] 5 <^ � r_
7` D Ea � �b �c i �d 6 �d � 6e 0 �e : �e y *f * �f W �f * 'g i Rg * �g � �g � lh � �h � }i x j �j H �j � �j nk �k �k - �k � �k c �l � m ^ �m � 9n � �n 1 uo . �o � �o � �p Oq kq ? �q E �q J r i Qr � �r `s $ wt �t 0 �t $ �t �t ! u $ 7u 5 \u 5 �u �u - �u 1 v D 5v ~ zv ; �v H 5w ' ~w � �w Z Px �x E �x - y 9 2y [ ly o �y 8z : Wz @ �{ C �{ - | � E| F �| ( 9} . b} 7 �} N �} ~ (~ ? ;~ N {~ $ �~ �~ p , W � ` � V� o� � �� e� a �� � � s �� r � 5 w� � �� _ a� � �� V ]� Y �� � � \ Ň � "� k �� f *� R �� � � b Ҋ H 5� g ~� E � ] ,� S �� b ލ � A� � � T �� , � � � K �� H �� ` @� H �� � � H �� } � m h� � ֕ 3 X� C �� i Ж ' :� i b� ! ̗ � � � � � T �� � K� 3 Й � � � ̚ � S� � �� � Ϝ � �� _ � H �� � ɞ v� @ �� � ؟ - |� : �� 7 � � $� @� / S� , �� �� / �� 4 � 2 � 7 O� 8 �� . �� . � 1 � � P� d գ ` :� �� �� Ѥ � �� � � � -� 3� K� g� �� 0 �� & Υ �� �� � 2� F� ]� q� ! ~� �� ^ �� � 0� B� Y� o� �� �� �� ȧ ϧ � F � # R� (Introduced in version 3.0.1) Assign a network traffic label to each traffic type on each physical network. These labels must match the labels you have already defined on the hypervisor host. To assign each label, click the Edit button under the traffic type icon within each physical network. A popup dialog appears where you can type the label, then click OK. (NetScaler only) Configure the IP range for public traffic. The IPs in this range will be used for the static NAT capability which you enabled by selecting the network offering for NetScaler with EIP and ELB. Enter the following details, then click Add. If desired, you can repeat this step to add more IP ranges. When done, click Next. (NetScaler only) If you chose the network offering for NetScaler, you have an additional screen to fill out. Provide the requested details to set up the NetScaler, then click Next. (Optional) OpenStack Object Storage (Swift) (see http://swift.openstack.org) (VMware only) If you have enabled Nexus dvSwitch in the environment, you must specify the corresponding Ethernet port profile names as network traffic label for each traffic type on the physical network. For more information on Nexus dvSwitch, see Configuring a vSphere Cluster with Nexus 1000v Virtual Switch in the Installation Guide. If you have enabled VMware dvSwitch in the environment, you must specify the corresponding Switch name as network traffic label for each traffic type on the physical network. For more information, see Configuring a VMware Datacenter with VMware Distributed Virtual Switch in the Installation Guide. **Advanced.** For more sophisticated network topologies. This network model provides the most flexibility in defining guest networks and providing custom network offerings such as firewall, VPN, or load balancer support. **Basic.** For AWS-style networking. Provides a single network where each VM instance is assigned an IP directly from the network. Guest isolation can be provided through layer-3 means such as security groups (IP address source filtering). **CPU overcommit ratio**: Enter the CPU overcommit ratio for the cluster. The value you enter determines the CPU consumption of each VM in the selected cluster. By increasing the over-provisioning ratio, more resource capacity will be used. If no value is specified, the value is defaulted to 1, which implies no over-provisioning is done. **Capacity.** Number of guest networks/accounts that will share this NetScaler device. **Cluster Name**: Enter the name of the cluster you created in vCenter. For example, "cloud.cluster.2.2.1" **Cluster name.** Enter a name for the cluster. This can be text of your choosing and is not used by CloudStack. **Cluster.** (Visible only if you choose Cluster in the Scope field.) The cluster for the storage device. **DNS 1 and 2.** These are DNS servers for use by guest VMs in the zone. These DNS servers will be accessed via the public network you will add later. The public IP addresses for the zone must have a route to the DNS server named here. **Dedicated.** When marked as dedicated, this device will be dedicated to a single account. When Dedicated is checked, the value in the Capacity field has no significance – implicitly, its value is 1. **Gateway.** The gateway for the hosts in that pod. **Gateway.** The gateway in use for these IP addresses. **Guest CIDR.** This is the CIDR that describes the IP addresses in use in the guest virtual networks in this zone. For example, 10.1.1.0/24. As a matter of good practice you should set different CIDRs for different zones. This will make it easier to set up VPNs between networks in different zones. **Guest Traffic vSwitch Type**: This option is displayed only if you enable the Override Guest Traffic option. Select a desirable switch. **Guest gateway.** The gateway that the guests should use. **Guest netmask.** The netmask in use on the subnet the guests will use. **Guest start IP/End IP.** Enter the first and last IP addresses that define a range that CloudStack can assign to guests. **Host Name.** The DNS name or IP address of the host. **Host Tags.** (Optional) Any labels that you use to categorize hosts for ease of maintenance. For example, you can set this 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 HA-Enabled Virtual Machines as well as HA for Hosts. **Host Tags.** (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 HA-Enabled Virtual Machines as well as HA for Hosts, both in the Administration Guide. **Hypervisor.** (Introduced in version 3.0.1) Choose the hypervisor for the first cluster in the zone. You can add clusters with different hypervisors later, after you finish adding the zone. **Hypervisor.** (Version 3.0.0 only; in 3.0.1, this field is read only) Choose the type of hypervisor software that all hosts in this cluster will run. If you choose VMware, additional fields appear so you can give information about a vSphere cluster. For vSphere servers, we recommend creating the cluster of hosts in vCenter and then adding the entire cluster to CloudStack. See Add Cluster: vSphere . **Hypervisor.** (Version 3.0.0 only; in 3.0.1, this field is read only) Choose the type of hypervisor software that all hosts in this cluster will run. If you choose VMware, additional fields appear so you can give information about a vSphere cluster. For vSphere servers, we recommend creating the cluster of hosts in vCenter and then adding the entire cluster to CloudStack. See Add Cluster: vSphere. **IP address.** The NSIP (NetScaler IP) address of the NetScaler device. **Internal DNS 1 and Internal DNS 2.** These are DNS servers for use by system VMs in the zone (these are VMs used by CloudStack itself, such as virtual routers, console proxies, and Secondary Storage VMs.) These DNS servers will be accessed via the management traffic network interface of the System VMs. The private IP address you provide for the pods must have a route to the internal DNS server named here. **Internal DNS 1 and Internal DNS 2.** These are DNS servers for use by system VMs in the zone(these are VMs used by CloudStack itself, such as virtual routers, console proxies,and Secondary Storage VMs.) These DNS servers will be accessed via the management traffic network interface of the System VMs. The private IP address you provide for the pods must have a route to the internal DNS server named here. **Lun # (for iSCSI).** In iSCSI this is the LUN number. For example, 3. **Lun.** The LUN number. For example, 3. **NFS Server.** The IP address of the server or fully qualified domain name of the server. **Name.** A name for the zone. **Name.** The name of the pod. **Name.** The name of the storage device. **Netmask.** The netmask associated with this IP range. **Netmask.** The network prefix that defines the pod's subnet. Use CIDR notation. **Network Domain.** (Optional) If you want to assign a special domain name to the guest VM network, specify the DNS suffix. **Network Offering.** Your choice here determines what network services will be available on the network for guest VMs. **Number of retries.** Number of times to attempt a command on the device before considering the operation failed. Default is 2. **Override Guest Traffic**: Enable this option to override the zone-wide guest traffic for the cluster you are creating. **Override Public Traffic**: Enable this option to override the zone-wide public traffic for the cluster you are creating. **Password.** This is the password for the user named above (from your XenServer or KVM install). **Path (for NFS).** In NFS this is the exported path from the server. **Path (for SharedMountPoint).** With KVM this is the path on each host that is where this primary storage is mounted. For example, "/mnt/primary". **Path (for VMFS).** In vSphere this is a combination of the datacenter name and the datastore name. The format is "/" datacenter name "/" datastore name. For example, "/cloud.dc.VM/cluster1datastore". **Path.** A combination of the datacenter name and the datastore name. The format is "/" datacenter name "/" datastore name. For example, "/cloud.dc.VM/cluster1datastore". **Path.** The exported path from the server. **Path.** The path on each host that is where this primary storage is mounted. For example, "/mnt/primary". **Pod Name.** A name for the pod. **Pod.** (Visible only if you choose Cluster in the Scope field.) The pod for the storage device. **Private interface.** Interface of NetScaler that is configured to be part of the private network. **Protocol.** For XenServer, choose either NFS, iSCSI, or PreSetup. For KVM, choose NFS or SharedMountPoint. For vSphere choose either VMFS (iSCSI or FiberChannel) or NFS. For Hyper-V, choose SMB. **Protocol.** For XenServer, choose either NFS, iSCSI, or PreSetup. For KVM, choose NFS, SharedMountPoint, CLVM, and RBD. For vSphere choose either VMFS (iSCSI or FiberChannel) or NFS. The remaining fields in the screen vary depending on what you choose here. **Protocol.** For XenServer, choose either NFS, iSCSI, or PreSetup. For KVM, choose NFS, SharedMountPoint,CLVM, or RBD. For vSphere choose either VMFS (iSCSI or FiberChannel) or NFS. The remaining fields in the screen vary depending on what you choose here. **Public Traffic vSwitch Type**: This option is displayed only if you enable the Override Public Traffic option. Select a desirable switch. If the vmware.use.dvswitch global parameter is true, the default option will be VMware vNetwork Distributed Virtual Switch. **Public interface.** Interface of NetScaler that is configured to be part of the public network. **Public.** A public zone is available to all users. A zone that is not public will be assigned to a particular domain. Only users in that domain will be allowed to create guest VMs in this zone. **RAM overcommit ratio**: Enter the RAM overcommit ratio for the cluster. The value you enter determines the memory consumption of each VM in the selected cluster. By increasing the over-provisioning ratio, more resource capacity will be used. If no value is specified, the value is defaulted to 1, which implies no over-provisioning is done. **Reserved system gateway.** The gateway for the hosts in that pod. **Reserved system netmask.** The network prefix that defines the pod's subnet. Use CIDR notation. **SMB Domain**: Applicable only if you select SMB/CIFS provider. The Active Directory domain that the SMB share is a part of. **SMB Domain**\ (for SMB/CIFS): Applicable only if you select SMB/CIFS provider. The Active Directory domain that the SMB share is a part of. **SMB Password** (for SMB/CIFS): Applicable only if you select SMB/CIFS provider. The password associated with the account. **SMB Password**: Applicable only if you select SMB/CIFS provider. The password associated with the account. **SMB Username** (for SMB/CIFS): Applicable only if you select SMB/CIFS provider. The username of the account which has the necessary permissions to the SMB shares. The user must be part of the Hyper-V administrator group. **SMB Username**: Applicable only if you select SMB/CIFS provider. The username of the account which has the necessary permissions to the SMB shares. The user must be part of the Hyper-V administrator group. **SR Name-Label (for PreSetup).** Enter the name-label of the SR that has been set up outside CloudStack. **SR Name-Label.** Enter the name-label of the SR that has been set up outside CloudStack. **Scope.** Indicate whether the storage is available to all hosts in the zone or only to hosts in a single cluster. **Server (for NFS, iSCSI, or PreSetup).** The IP address or DNS name of the storage device. **Server (for VMFS).** The IP address or DNS name of the vCenter server. **Server.** The IP address or DNS name of the storage device. **Server.** The IP address or DNS name of the vCenter server. **Start IP/End IP.** A range of IP addresses that are assumed to be accessible from the Internet and will be allocated for access to guest VMs. **Start IP/End IP.** A range of IP addresses that are assumed to be accessible from the Internet and will be allocated for access to guest networks. **Start/End Reserved System IP.** The IP range in the management network that CloudStack uses to manage various system VMs, such as Secondary Storage VMs, Console Proxy VMs, and DHCP. For more information, see System Reserved IP Addresses. **Start/End Reserved System IP.** The IP range in the management network that CloudStack uses to manage various system VMs, such as Secondary Storage VMs, Console Proxy VMs, and DHCP. For more information, see `“System Reserved IP Addresses” <http://docs.cloudstack.apache.org/en/latest/concepts.html?highlight=about%20pods#id4>`_. **Tags (optional).** The comma-separated list of tags for this storage device. It should be an equivalent set or superset of the tags on your disk offerings. **Tags (optional).** The comma-separated list of tags for this storage device. It should be an equivalent set or superset of the tags on your disk offerings.. **Target IQN (for iSCSI).** In iSCSI this is the IQN of the target. For example, iqn.1986-03.com.sun:02:01ec9bb549-1271378984. **Target IQN.** The IQN of the target. For example, iqn.1986-03.com.sun:02:01ec9bb549-1271378984. **Type.** NetScaler device type that is being added. It could be NetScaler VPX, NetScaler MPX, or NetScaler SDX. For a comparison of the types, see About Using a NetScaler Load Balancer. **Username.** The username is root. **Username.** Usually root. **Username/Password.** The authentication credentials to access the device. CloudStack uses these credentials to access the device. **VLAN.** The VLAN that will be used for public traffic. **vCenter Datacenter**: Enter the vCenter datacenter that the cluster is in. For example, "cloud.dc.VM". **vCenter Host**: Enter the hostname or IP address of the vCenter server. **vCenter Password**: Enter the password for the user named above. **vCenter Username**: Enter the username that CloudStack should use to connect to vCenter. This user must have all the administrative privileges. 100GB minimum capacity :ref:`adding-a-host-vsphere` :ref:`adding-a-host-xenserver-kvm` A CIDR that describes the network that the management CIDRs reside on. This variable must be set for deployments that use vSphere. It is recommended to be set for other deployments as well. Example: 192.168.3.0/24. A secondary storage device must be located in the same zone as the guest VMs it serves. About Configuration Parameters Add Cluster: KVM or XenServer Add Cluster: vSphere Add Primary Storage Add Secondary Storage Add a region with ID 1, the name of region 1, and the endpoint <region.1.IP.address>:8080/client. Add a region with ID 2, the name of region 2, and the endpoint <region.2.IP.address>:8080/client. Add a zone to the region. See :ref:`adding-a-zone`. Add more clusters to the pod (optional). See :ref:`adding-a-cluster`. Add more hosts to the cluster (optional). See :ref:`adding-a-host`. Add more pods to the zone (optional). See :ref:`adding-a-pod`. Add primary storage to the cluster. See :ref:`add-primary-storage`. Add secondary storage to the zone. See :ref:`add-secondary-storage`. Adding Primary Storage Adding Regions (optional) Adding Secondary Storage Adding Third and Subsequent Regions Adding a Cluster Adding a Host Adding a Host (XenServer or KVM) Adding a Host (vSphere) Adding a Pod Adding a Region Adding a XenServer or KVM Host Adding a Zone Adding an NFS Secondary Staging Store for Each Zone Adding primary storage that is based on the SolidFire plug-in enables CloudStack to provide hard quality-of-service (QoS) guarantees. Advanced Zone Configuration After everything is configured, CloudStack will perform its initialization. This can take 30 minutes or more, depending on the speed of your network. When the initialization has completed successfully, the administrator's Dashboard should be displayed in the CloudStack UI. After the Management Server is installed and running, you can add the compute resources for it to manage. For an overview of how a CloudStack cloud infrastructure is organized, see `“Cloud Infrastructure Overview” <http://docs.cloudstack.apache.org/en/latest/concepts.html#cloud-infrastructure-overview>`_. After you select Advanced in the Add Zone wizard and click Next, you will be asked to enter the following details. Then click Next. After you select Basic in the Add Zone wizard and click Next, you will be asked to enter the following details. Then click Next. Any standards-compliant iSCSI, SMB, or NFS server that is supported by the underlying hypervisor. Assign a network traffic label to each traffic type on the physical network. These labels must match the labels you have already defined on the hypervisor host. To assign each label, click the Edit button under the traffic type icon. A popup dialog appears where you can type the label, then click OK. Basic Zone Configuration Be sure you have performed the additional CloudStack-specific configuration steps described in the hypervisor installation section for your particular hypervisor. Before adding a host to the CloudStack configuration, you must first install your chosen hypervisor on the host. CloudStack can manage hosts running VMs under a variety of hypervisors. Before you can configure the host, you need to install the hypervisor software on the host. You will need to know which version of the hypervisor software version is supported by CloudStack and what additional configuration is required to ensure the host will work with CloudStack. To find these installation details, see: Before you can fill out this screen, you need to prepare the secondary storage by setting up NFS shares and installing the latest CloudStack System VM template. See Adding Secondary Storage : By the end of the installation procedure, the Management Server should have been started. Be sure that the Management Server installation was successful and complete. Bypass internal DNS, and use the external DNS1 and DNS2 Choose one of the following network types: Choose the hypervisor type for this cluster. Choose the pod in which you want to create the cluster. Choose the zone you just added. Choose which traffic types will be carried by the physical network. Citrix XenServer Installation and Configuration Citrix XenServer Installation for CloudStack Click Add Cluster. Click Add Host. Click Add Instance and follow the steps in the wizard. Click Add Pod. Click Add Primary Storage. Click Add Region. In the dialog, fill in the following fields: Click Add Secondary Storage. Click Add Zone. The zone creation wizard will appear. Click Launch VM. Your VM will be created and started. It might take some time to download the template and complete the VM startup. You can watch the VM’s progress in the Instances screen. Click Launch. Click Next. Click OK. Click View Clusters. Click View Hosts. Click the Add NFS Secondary Staging Store button. Click the Compute and Storage tab. In the Pods node of the diagram, click View All. Click the Compute tab, and click View All on Pods. Choose the pod to which you want to add the cluster. Click the Compute tab. Click the Compute tab. In the Clusters node, click View All. Click the Remove Region button. Click the Settings tab. Click the cluster where you want to add the host. Click the name of the region you want to delete. Click the name of the resource where you want to set a limit. CloudStack provides a variety of settings you can use to set limits, configure features, and enable or disable features in the cloud. Once your Management Server is running, you might need to set some of these configuration parameters, depending on what optional features you are setting up. You can set default values at the global level, which will be in effect throughout the cloud unless you override them at a lower level. You can make local settings, which will override the global configuration parameter values, at the level of an account, zone, cluster, or primary storage. Configuration Parameters Configuration requirements: Configure the IP range for public Internet traffic. Enter the following details, then click Add. If desired, you can repeat this step to add more public Internet IP ranges. When done, click Next. Configure the network for guest traffic. Provide the following, then click Next: Configuring a Storage Plug-in Configuring your CloudStack Installation Congratulations! You have successfully completed a CloudStack Installation. Copy the account, user, and domain tables from any existing region's database to the new region's database. Copy the account, user, and domain tables from the region 1 database to the region 2 database. Copy the script from the Management Server in /usr/share/cloudstack-common/scripts/vm/hypervisor/xenserver/cloud-setup-bonding.sh to the master host and ensure it is executable. Create NFS Secondary Staging Store. This box must always be checked. Create the cluster of hosts in vCenter. Follow the vCenter instructions to do this. You will create a cluster that looks something like this in vCenter. Default data transfer rate in megabits per second allowed in a network. Default domain name for VMs inside a virtual networks with a router. DefaultSharedNetscalerEIPandELBNetworkOffering DefaultSharedNetworkOffering DefaultSharedNetworkOfferingWithSGService Define regions (optional). See :ref:`adding-regions`. Deleting a Region Description Determines the vCenter session timeout value by using this parameter. The default value is 20 minutes. Increase the timeout value to avoid timeout errors in VMware deployments because certain VMware operations take more than 20 minutes. Determines whether CloudStack will use storage that is local to the Host for data disks, templates, and snapshots. By default CloudStack will not use this storage. You should change this to true if you want to use local storage and you understand the reliability and feature drawbacks to choosing local storage. Do not put more than 8 hosts in a vSphere cluster Each Secondary Storage server must be available to all hosts in the zone. Each cluster must contain only hosts with the identical hypervisor. Each region has its own CloudStack instance. Therefore, the first step of creating a new region is to install the Management Server software, on one or more nodes, in the geographic area where you want to set up the new region. Use the steps in the Installation guide. When you come to the step where you set up the database, use the additional command-line flag ``-r <region_id>`` to set a region ID for the new region. The default region is automatically assigned a region ID of 1, so your first additional region might be region 2. Enable or diable dynamically scaling of a VM. Endpoint. The URL where you can log in to the Management Server in the new region. This has the format <region.2.IP.address>:8080/client. Ensure that nothing is stored on the server. Adding the server to CloudStack will destroy any existing data. Enter a name for the cluster. This can be text of your choosing and is not used by CloudStack. Enter the following details in the dialog. Even if the UI allows you to uncheck this box, do not do so. This checkbox and the three fields below it must be filled in. Even when Swift or S3 is used as the secondary storage provider, an NFS staging storage in each zone is still required. Every zone must have at least one NFS store provisioned; multiple NFS servers are allowed per zone. To provision an NFS Staging Store for a zone: Field Fill in the following fields: Fill out the dialog box fields, then click OK: Find the name of the particular resource that you want to work with. For example, if you are in Infrastructure, click View All on the Zones, Clusters, or Primary Storage area. First, run this command to copy the contents of the database: For KVM, do not put more than 16 hosts in a cluster. For XenServer nodes, this is a true/false variable that instructs CloudStack to enable iSCSI multipath on the XenServer Hosts when they are added. This defaults to false. Set it to true if you would like CloudStack to enable multipath.If this is true for a NFS-based deployment multipath will still be enabled on the XenServer host. However, this does not impact NFS operation and is harmless. For XenServer, do not put more than 8 hosts in a cluster. For all additional hosts to be added to the cluster, run the following command. This will cause the host to join the master in a XenServer pool. For hardware requirements, see the installation section for your hypervisor in the CloudStack Installation Guide. For more information about using VMs, including instructions for how to allow incoming network traffic to the VM, start, stop, and delete VMs, and move a VM from one host to another, see Working With Virtual Machines in the Administrator’s Guide. For vSphere servers, we recommend creating the cluster of hosts in vCenter and then adding the entire cluster to CloudStack. Follow these requirements: For vSphere servers, we recommend creating the cluster of hosts in vCenter and then adding the entire cluster to CloudStack. See Add Cluster: vSphere. Global Settings. This displays a list of the parameters with brief descriptions and current values. Go to the Instances tab, and filter by My Instances. Granular Global Configuration Parameters Grouping your cloud resources into geographic regions is an optional step when provisioning the cloud. For an overview of regions, see `“About Regions” <http://docs.cloudstack.apache.org/en/latest/concepts.html#about-regions>`_. Hardware requirements: Heterogeneous Secondary Storage is not supported in Regions. You can use only a single NFS, S3, or Swift account per region. Host Name. The DNS name or IP address of the host. Host Tags (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 HA-Enabled Virtual Machines as well as HA for Hosts. Host management for vSphere is done through a combination of vCenter and the CloudStack admin UI. CloudStack requires that all hosts be in a CloudStack cluster, but the cluster may consist of a single host. As an administrator you must decide if you would like to use clusters of one host or of multiple hosts. Clusters of multiple hosts allow for features like live migration. Clusters also require shared storage such as NFS or iSCSI. Hypervisor Capabilities. This displays a list of hypervisor versions with the maximum number of guests supported for each. ID. A unique identifying number. Use the same number you set in the database during Management Server installation in the new region; for example, 2. If false, users will not be able to create public templates. If network bonding is in use, the administrator must cable the new host identically to other hosts in the cluster. If one NIC is used, these IPs should be in the same CIDR as the pod CIDR. If shared mountpoint storage is in use, the administrator should ensure that the new host has all the same mountpoints (with storage mounted) as the other hosts in the cluster. If the vmware.use.dvswitch global parameter is true, the default option will be VMware vNetwork Distributed Virtual Switch. If true and if an account has one or more dedicated guest VLAN ranges, VLANs are allocated from the system pool after all the VLANs dedicated to the account have been consumed. If true and if an account has one or more dedicated public IP ranges, IPs are acquired from the system pool after all the IPs dedicated to the account have been consumed. If you are using OpenVswitch bridges edit the file agent.properties on the KVM host and set the parameter network.bridge.type to openvswitch before adding the host to CloudStack If you are using an Hyper-V host, ensure that you have created a SMB share. If you decide to grow your deployment, you can add more hosts, primary storage, zones, pods, and clusters. If you do not need security groups, choose this. If you do not provision shared primary storage, you must set the global configuration parameter system.vm.local.storage.required to true, or else you will not be able to start VMs. If you do not take action to define regions, then all the zones in your cloud will be automatically grouped into a single default region. This region is assigned the region ID of 1. You can change the name or URL of the default region by displaying the region in the CloudStack UI and clicking the Edit button. If you have enabled Nexus dvSwitch in the environment, the following parameters for dvSwitch configuration are displayed: If you have installed a Citrix NetScaler appliance as part of your zone network, and you will be using its Elastic IP and Elastic Load Balancing features, choose this. With the EIP and ELB features, a basic zone with security groups enabled can offer 1:1 static NAT and load balancing. If you have not already done so, install the hypervisor software on the host. You will need to know which version of the hypervisor software version is supported by CloudStack and what additional configuration is required to ensure the host will work with CloudStack. To find these installation details, see the appropriate section for your hypervisor in the CloudStack Installation Guide. If you want to enable security groups for guest traffic isolation, choose this. (See Using Security Groups to Control Traffic to VMs.) In Hypervisor, choose VMware. In Secondary Storage, click View All. In Select View, choose Secondary Staging Store. In Select View, choose one of the following: In a new cluster, CloudStack adds the first host for you. You can always add more hosts later. For an overview of what a host is, see About Hosts. In a new cluster, CloudStack adds the first host for you. You can always add more hosts later. For an overview of what a host is, see `“About Hosts” <http://docs.cloudstack.apache.org/en/latest/concepts.html?highlight=about%20pods#about-hosts>`_. In a new cluster, CloudStack adds the first primary storage server for you. You can always add more servers later. For an overview of what primary storage is, see About Primary Storage. In a new cluster, CloudStack adds the first primary storage server for you. You can always add more servers later. For an overview of what primary storage is, see `“About Primary Storage” <http://docs.cloudstack.apache.org/en/latest/concepts.html?highlight=about%20pods#about-primary-storage>`_. In a new pod, CloudStack adds the first cluster for you. You can always add more clusters later. For an overview of what a cluster is, see About Clusters. In a new pod, CloudStack adds the first cluster for you. You can always add more clusters later. For an overview of what a cluster is, see `“About Clusters” <http://docs.cloudstack.apache.org/en/latest/concepts.html?highlight=about%20pods#about-clusters>`_. In a new zone, CloudStack adds the first pod for you. You can always add more pods later. For an overview of what a pod is, see `“About Pods” <http://docs.cloudstack.apache.org/en/latest/concepts.html?highlight=about%20pods#about-pods>`_. In a new zone, CloudStack adds the first secondary storage server for you. For an overview of what secondary storage is, see `“About Secondary Storage” <http://docs.cloudstack.apache.org/en/latest/concepts.html?highlight=about%20pods#about-secondary-storage>`_. In data disk offering, if desired, add another data disk. This is a second volume that will be available to but not mounted in the guest. For example, in Linux on XenServer you will see /dev/xvdb in the guest after rebooting the VM. A reboot is not required if you have a PV-enabled OS kernel in use. In default network, choose the primary network for the guest. In a trial installation, you would have only one option here. In the Actions column, click the Edit icon to modify a value. In the Actions column, click the Edit icon to modify a value. If you are viewing Hypervisor Capabilities, you must click the name of the hypervisor first to display the editing screen. In the Clusters node of the diagram, click View All. In the Primary Storage node of the diagram, click View All. In the following commands, it is assumed that you have set the root password on the database, which is a CloudStack recommended best practice. Substitute your own MySQL root password. In the left navigation bar, click Global Settings. In the left navigation bar, click Infrastructure or Accounts, depending on where you want to set a value. In the left navigation bar, click Infrastructure. In the left navigation bar, click Regions. In the left navigation, choose Infrastructure. In the left navigation, choose Infrastructure. In Zones, click View More, then click the zone in which you want to add the cluster. In the left navigation, choose Infrastructure. In Zones, click View More, then click the zone in which you want to add the host. In the left navigation, choose Infrastructure. In Zones, click View More, then click the zone in which you want to add the primary storage. In the left navigation, choose Infrastructure. In Zones, click View More, then click the zone to which you want to add a pod. In the template selection, choose the template to use in the VM. If this is a fresh installation, likely only the provided CentOS template is available. Initialize and Test Initialize and test the new cloud. See :ref:`initialize-and-test`. Install CloudStack in each additional region. Set the region ID for each region during the database setup step. KVM Host Additional Requirements KVM Installation and Configuration KVM vSphere Installation and Configuration Log in to <region.1.IP.address>:8080/client. Log in to CloudStack in the first region as root administrator (that is, log in to <region.1.IP.address>:8080/client), and add a region with ID 3, the name of region 3, and the endpoint <region.3.IP.address>:8080/client. Log in to CloudStack in the first region as root administrator (that is, log in to <region.1.IP.address>:8080/client). Log in to CloudStack in the second region as root administrator (that is, log in to <region.2.IP.address>:8080/client), and add a region with ID 3, the name of region 3, and the endpoint <region.3.IP.address>:8080/client. Log in to CloudStack in the third region as root administrator (that is, log in to <region.3.IP.address>:8080/client). Log in to each of the other regions, navigate to the one you want to delete, and click Remove Region. For example, to remove the third region in a 3-region cloud: Log in to the CloudStack UI (see `“Log In to the UI” <http://docs.cloudstack.apache.org/projects/cloudstack-administration/en/latest/ui.html#log-in-to-the-ui>`_). Log in to the CloudStack UI as administrator. Log in to the CloudStack UI as root administrator. Log in to the CloudStack UI as the root administrator. See `“Log In to the UI” <http://docs.cloudstack.apache.org/projects/cloudstack-administration/en/latest/ui.html#log-in-to-the-ui>`_. Log in to the CloudStack UI. See `“Log In to the UI” <http://docs.cloudstack.apache.org/projects/cloudstack-administration/en/latest/ui.html#log-in-to-the-ui>`_. Log in to the UI as administrator. Log in to the UI. MVIP%3D[Management Virtual IP Address] (can be suffixed with :[port number]) Make sure the hypervisor host does not have any VMs already running before you add it to CloudStack. Make sure the hypervisor hosts do not have any VMs already running before you add them to CloudStack. Make sure the new host has the same network configuration (guest, private, and public network) as other hosts in the cluster. Make sure you prepared the system VM template during Management Server installation. See `“Prepare the System VM Template” <installation.html#prepare-the-system-vm-template>`_. Maximum number of items per page that can be returned by a CloudStack API command. The limit applies at the cloud level and can vary from cloud to cloud. You can override this with a lower value on a particular API call by using the page and pagesize API command parameters. For more information, see the Developer's Guide. Default: 500. Minimum required capacity depends on your needs. NFS NFS server. The name of the zone's Secondary Staging Store. NFS storage appliance or Linux NFS server Name of the default router template on KVM. Name of the default router template on VMware. Name of the default router template on Xenserver. Name. Give the new region a descriptive name. Name. Give the storage a descriptive name. Network Offering Nexus dvSwitch IP Address: The IP address of the Nexus VSM appliance. Nexus dvSwitch Password: The password associated with the username specified above. Nexus dvSwitch Username: The username required to access the Nexus VSM appliance. Now add the hypervisor host to CloudStack. The technique to use varies depending on the hypervisor. Now add the new region to region 1 in CloudStack. Now perform the same procedure in reverse. Log in to region 2, and add region 1. On Zones, click View More. Once the Management Server is running, add your new region to all existing regions by repeatedly using the Add Region button in the UI. For example, if you were adding region 3: Optionally give your VM a name and a group. Use any descriptive text you would like. Overview of Provisioning Steps Password. This is the password for the user from your XenServer or KVM install). Path. The path to the zone's Secondary Staging Store. Primary storage cannot be added until a host has been added to the cluster. Provide the following information in the dialog. The fields below make reference to the values from vCenter. Provide the following information in the dialog. The information required varies depending on your choice in Protocol. Provide the following information. Provider. Choose S3, Swift, NFS, or CIFS then fill in the related fields which appear. The fields will vary depending on the storage provider; for more information, consult the provider's documentation (such as the S3 or Swift website). NFS can be used for zone-based storage, and the others for region-wide storage. For Hyper-V, select SMB/CIFS. Remove project accounts. Run these commands on the region 2 database: Remove project accounts. Run these commands on the region 3 database: Repeat for additional hosts. Repeat the procedure in reverse to add all existing regions to the new region. For example, for the third region, add the other two existing regions: Repeat these steps for <region.2.IP.address>:8080/client. Requirements for XenServer and KVM Hosts Restart the Management Servers in region 2. Restart the Management Servers in the new region. Routes that are blacklisted cannot be used for creating static routes for a VPC Private Gateway. Run the script: SMB/CIFS (Hyper-V) SVIP%3D[Storage Virtual IP Address] (can be suffixed with :[port number]) Select a service offering. Be sure that the hardware you have allows starting the selected service offering. Set the default zone as null: Setting Global Configuration Parameters Setting Local Configuration Parameters SharedMountPoint Specify a range of VLAN IDs to carry guest traffic for each physical network (see VLAN Allocation Example ), then click Next. Specify whether or not to reserve CPU when not over-provisioning; In case of CPU over-provisioning, CPU is always reserved. Specify whether or not to reserve memory when not over-provisioning; In case of memory over-provisioning memory is always reserved. System Requirements for Primary Storage System Requirements for Secondary Storage The CloudStack Installation Guide provides instructions on how to install each supported hypervisor and configure it for use with CloudStack. See the appropriate section in the Installation Guide for information about which version of your chosen hypervisor is supported, as well as crucial additional steps to configure the hypervisor hosts for use with CloudStack. The First Region: The Default Region The SolidFire storage plug-in for CloudStack is part of the standard CloudStack install. There is no additional work required to add this component. The createStoragePool API has been augmented to support plugable storage providers. The following is a list of parameters to use when adding storage to CloudStack that is based on the SolidFire plug-in: The documentation for each CloudStack feature should direct you to the names of the applicable parameters. The following table shows a few of the more useful parameters. The following global configuration parameters have been made more granular. The parameters are listed under three different scopes: account, cluster, and zone. The label you want to use throughout the cloud to designate certain hosts as dedicated HA hosts. These hosts will be used only for HA-enabled VMs that are restarting due to the failure of another host. For example, you could set this to ha\_host. Specify the ha.tag value asa host tag when you add a new host to the cloud. The percentage, as a value between 0 and 1, of CPU utilization above which allocators will disable that cluster from further usage. Keep the corresponding notification threshold lower than this value to be notified beforehand. The percentage, as a value between 0 and 1, of allocated storage utilization above which alerts are sent that the storage is below the threshold. The percentage, as a value between 0 and 1, of allocated storage utilization above which allocators will disable that pool because the available allocated storage is below the threshold. The percentage, as a value between 0 and 1, of cpu utilization above which alerts are sent that the available CPU is below the threshold. The percentage, as a value between 0 and 1, of memory utilization above which alerts are sent that the available memory is below the threshold. The percentage, as a value between 0 and 1, of memory utilization above which allocators will disable that cluster from further usage. Keep the corresponding notification threshold lower than this value to be notified beforehand. The percentage, as a value between 0 and 1, of storage utilization above which alerts are sent that the available storage is below the threshold. The percentage, as a value between 0 and 1, of storage utilization above which allocators will disable the pool because the available storage capacity is below the threshold. The range of IPs to be allocated to remotely access the VPN clients. The first IP in the range is used by the VPN server. The rest of the steps differ depending on whether you chose Basic or Advanced. Continue with the steps that apply to you: The storage server should be a machine with a large number of disks. The disks should ideally be managed by a hardware RAID controller. The tag sets on primary storage across clusters in a Zone must be identical. For example, if cluster A provides primary storage that has tags T1 and T2, all other clusters in the Zone must also provide primary storage that has tags T1 and T2. The traffic types are management, public, guest, and storage traffic. For more information about the types, roll over the icons to display their tool tips, or see Basic Zone Network Traffic Types. This screen starts out with some traffic types already assigned. To add more, drag and drop traffic types onto the network. You can also change the network name if desired. The url parameter is somewhat unique in that its value can contain additional key/value pairs. Then run this command to put the data onto the new region's database. For example, for region 3: Then run this command to put the data onto the region 2 database: There may be a slight delay while the host is provisioned. It should automatically display in the UI. There might be a slight delay while the cluster is provisioned. It will automatically display in the UI. These steps assume you have already installed the hypervisor on the hosts and logged in to the CloudStack UI. These traffic labels will be defined only for the hypervisor selected for the first cluster. For all other hypervisors, the labels can be configured after the zone is created. This is the IP address of the Management Server. If you are using multiple Management Servers you should enter a load balanced IP address that is reachable via the private network. This is used to protect your internal network from rogue attempts to download arbitrary files using the template download feature. This is a comma-separated list of CIDRs. If a requested URL matches any of these CIDRs the Secondary Storage VM will use the private network interface to fetch the URL. Other URLs will go through the public interface. We suggest you set this to 1 or 2 hardened internal machines where you keep your templates. For example, set it to 192.168.1.66/32. This section tells how to add regions, zones, pods, clusters, hosts, storage, and networks to your cloud. If you are unfamiliar with these entities, please begin by looking through `*Cloud Infrastructure Concepts* <http://docs.cloudstack.apache.org/en/latest/concepts.html#cloud-infrastructure-concepts>`_. To add a vSphere cluster to CloudStack: To add the third region, and subsequent additional regions, the steps are similar to those for adding the second region. However, you must repeat certain steps additional times for each additional region: To configure the first cluster, enter the following, then click Next: To configure the first host, enter the following, then click Next: To configure the first pod, enter the following, then click Next: To configure the first primary storage server, enter the following, then click Next: To prepare for the zone-based Secondary Staging Store, you should have created and mounted an NFS share during Management Server installation. See `“Prepare NFS Shares” <installation.html#prepare-nfs-shares>`_. To provision the cloud infrastructure, or to scale it up at any time, follow these procedures: To use the VM, click the View Console button. |ConsoleButton.png: button to launch a console| Use the following steps to set global configuration parameters. These values will be the defaults in effect throughout your CloudStack deployment. Use the following steps to set local configuration parameters for an account, zone, cluster, or primary storage. These values will override the global configuration settings. Use the search box to narrow down the list to those you are interested in. Use these steps to add a second region in addition to the default region. Used for CPU over-provisioning calculation; the available CPU will be the mathematical product of actualCpuCapacity and cpu.overprovisioning.factor. Used for memory over-provisioning calculation. Used for storage over-provisioning calculation; available storage will be the mathematical product of actualStorageSize and storage.overprovisioning.factor. Username. Usually root. VMFS VMware vSphere Installation and Configuration Value Verify that the system is ready. In the left navigation bar, select Templates. Click on the CentOS 5.5 (64bit) no Gui (KVM) template. Check to be sure that the status is "Download Complete." Do not proceed to the next step until this status is displayed. We strongly recommend the use of multiple NICs. If multiple NICs are used, they may be in a different subnet. When copying and pasting a command, be sure the command has pasted as a single line before executing. Some document viewers may introduce unwanted line breaks in copied text. When setting up primary storage, follow these restrictions: When using preallocated storage for primary storage, be sure there is nothing on the storage (ex. you have an empty SAN volume or an empty NFS share). Adding the storage to CloudStack will destroy any existing data. When you add a hypervisor host to CloudStack, the host must not have any VMs already running. When you add a new zone, you will be prompted to configure the zone’s physical network and add the first pod, cluster, host, primary storage, and secondary storage. When you create a new zone, the first primary storage is added as part of that procedure. You can add primary storage servers at any time, such as when adding a new cluster or adding more servers to an existing cluster. When you create a new zone, the first secondary storage is added as part of that procedure. You can add secondary storage servers at any time to add more servers to an existing zone. When you created a new zone, CloudStack adds the first pod for you. You can add more pods at any time using the procedure in this section. When you deploy CloudStack, the hypervisor host must not have any VMs already running. When you have finished these steps, you will have a deployment with the following basic structure: With all hosts added to the XenServer pool, run the cloud-setup-bond script. This script will complete the configuration and setup of the bonds on the new hosts in the cluster. XenServer Host Additional Requirements XenServer and KVM hosts can be added to a cluster at any time. You need to tell CloudStack about the hosts that it will manage. Hosts exist inside clusters, so before you begin adding hosts to the cloud, you must add at least one cluster. Zone. The zone where the NFS Secondary Staging Store is to be located. `“Advanced Zone Configuration” <#advanced-zone-configuration>`_ `“Basic Zone Configuration” <#basic-zone-configuration>`_ account allow.public.user.templates blacklisted.routes capacityBytes=[whole number of bytes from the SAN to give to CloudStack] capacityIops=[whole number of IOPS from the SAN to give to CloudStack] cluster cluster.cpu.allocated.capacity.disablethreshold cluster.cpu.allocated.capacity.notificationthreshold cluster.memory.allocated.capacity.disablethreshold cluster.memory.allocated.capacity.notificationthreshold cluster.storage.allocated.capacity.notificationthreshold cluster.storage.capacity.notificationthreshold clusterAdminPassword%3D[cluster admin's password] clusterAdminUsername%3D[cluster admin's username] clusterDefaultBurstIopsPercentOfMaxIops%3D[Burst IOPS is determined by (Min IOPS \* clusterDefaultBurstIopsPercentOfMaxIops parameter) (can be a decimal value)] clusterDefaultMaxIops%3D[Max IOPS (whole number) to set for a volume; used if Max IOPS is not specified by administrator or user] clusterDefaultMinIops%3D[Min IOPS (whole number) to set for a volume; used if Min IOPS is not specified by administrator or user] command=createStoragePool cpu.overprovisioning.factor default.page.size enable.dynamic.scale.vm guest.domain.suffix ha.tag host hypervisor=Any iSCSI management.network.cidr mem.overprovisioning.factor name=[name for primary storage] network.throttling.rate pool.storage.allocated.capacity.disablethreshold pool.storage.capacity.disablethreshold preSetup provider=SolidFire remote.access.vpn.client.iprange router.template.kvm router.template.vmware router.template.xen scope=zone secstorage.allowed.internal.sites storage.overprovisioning.factor url=[key/value pairs detailed below (values are URL encoded; for example, '=' is represented as '%3D')] use.external.dns use.local.storage use.system.guest.vlans use.system.public.ips vmware.reserve.cpu vmware.reserve.mem vmware.vcenter.session.timeout xen.setup.multipath zone zoneId=[your zone id] |addcluster.png: add a cluster| |provisioning-overview.png: Conceptual overview of a basic deployment| |vsphereclient.png: vSphere client| Project-Id-Version: Apache CloudStack Installation RTD
Report-Msgid-Bugs-To:
POT-Creation-Date: 2014-06-30 11:42+0200
PO-Revision-Date: 2014-06-30 10:23+0000
Last-Translator: FULL NAME <EMAIL@ADDRESS>
Language-Team: Chinese (China) (http://www.transifex.com/projects/p/apache-cloudstack-installation-rtd/language/zh_CN/)
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
Language: zh_CN
Plural-Forms: nplurals=1; plural=0;
(在3.0.1版本中介绍过)为每一种不同的物理网络分配不同的网络流量标签。这些标签必须和你在hypervisor主机中定义的标签一致。更改标签名，可以在每一个物理网络里点击相应的流量标签的编辑按钮，一个对话框会跳出来，输入合适的标签之后，点击下一步。 (只针对NetScaler) 设置公网的IP范围。此IP范围用作启用了EIP和ELB技术的网络方案的NAT映射。输入这些细节信息，点击增加。如果有必要，你可以重复输入多个公网IP范围。当这一切完成之后，点击下一步继续。 (只针对NetScaler) 如果你选择的网络方案是针对NetScaler的，则还要一个额外的选项需要填写。在填写了关于NetScaler的细节信息之后，点击下一步继续。 （可选）OpenStack Object Storage (Swift) (参见 http://swift.openstack.org) (只针对VMWARE)如果你的环境中有Nexus分布式虚拟交换机(dvSwitch),则必须为每一种物理网络上的流量类型的标签指定为相应的局域网端口配置名称(Ethernet port profile names).关于Nexus dvSwitch更多信息，可以查看安装指南的相关章节。如果你的环境中有VMware的分布式虚拟交换机（dvSwitch），,则必须为每一种物理网络上的流量类型的标签指定为相应的虚拟交换机名称(Switch name)。关于这方面的更多信息，参看安装指南当中的关于VMware Datacenter的相关章节。 **高级** 为更复杂的网络拓扑而设计。这种网络模型可以实现更灵活的客户虚拟机网络配置，并且可以提供防火墙，VPN，负载均衡这些高级功能。 **基本.** 类似AWS风格的网络。单一网段，每个VM都得到此网段的一个IP。客户虚拟机之间主要以安全组形式在网络第三层之间实现隔离。（IP地址源过滤） **CPU超配比率**: 输入此群集的CPU超配比率。这个比率值决定了群集内每台虚拟机的CPU耗用比率。增加这个数据，则能使用更多的资源。如果不设置此值的话，默认值为1，这就表示没有使用超配。 **容量**，共享NetScaler设备的最大客户网络或帐号的数量。 **群集名称**:输入你在VCENTER中创建的群集名称。比如："cloud.cluster.2.2.1" **群集名称.** 你要为此群集提供一个CLOUDSTACK之前没有使用的名称。 **集群.** (只有在范围域内选择集群时可见)针对存储设备的集群 **DNS 1 和 2.** 这些DNS是提供给区域里的客户虚拟机使用的。这些DNS服务器IP访问是通过随后添加的公网进行的。此区域的公网IP地址必须能够路由到这些DNS服务器。 **专用** 当标示为专用之后，则这个设备只为一个帐号使用。当选择专用之后，容量的数值不再可任意设置---明显的，它的数量只能为1. **网关.** 机柜提供点的网关。 **网关** 为这些IP地址定义网关。 **客户虚拟机CIDR.** 这个CIDR指的是在这个区域内的虚拟客户机的网络，比如10.1.1.0/24。最好能为不同的区域配置不同的CIDR，因为这样可以更方便的在不同的区域中建立相关的VPN。 **Guest Traffic vSwitch Type**:只有当the Override Guest Traffic选项启用后才会出现。为此选择一种合适的虚拟交换机类型。 **来宾网关.** 客户来宾虚拟机使用的网关。 **来宾子网掩码.** 客户来宾虚拟机使用的子网掩码。 **客户来宾开始/结束IP.** 输入CLOUDSTACK用来分配给客户来宾使用的起止IP地址。 **宿主机名称.** 宿主机的IP地址或DNS解析名称。 **主机标签(可选).** 此标签用于将主机分类，以便更好的后期维护。比如，如果你只想此宿主机用于具有HA（high availability）高可用性能的虚拟机，那么，你可以将此宿主机设置为云里相关的HA标签。(参看全局设置参数里的ha.tag)，关于HA的更多信息，请参看HA虚拟机和HA宿主机的相关章节。 **主机标签.** (可选)此标签用于将主机分类，以便更好的后期维护。比如，如果你只想此宿主机用于具有HA（high availability）高可用性能的虚拟机，那么，你可以将此宿主机设置为云里相关的HA标签。(参看全局设置参数里的ha.tag)，关于HA的更多信息，请参看HA虚拟机和HA宿主机的相关章节。 **Hypervisor.**(在version 3.0.1介绍过) 需要为区域内的第一个集群选择一种hypervisor。当你完成添加区域的配置之后，也可以为另外的集群配置不同的hypervisor。 **Hypervisor.** (只针对Version 3.0.0;在3.0.1中，这一栏是只读的)选择一种在这个群集中运行的hypervisor。如果你选择宾是VMWARE，则需要提供关于VSPHERE群集的信息。对于VSHPERE服务器，我们建议先在VCENTER里将群集设备好，然后作为群集整体加入CLOUDSTACK。参看Add Cluster: vSphere。 **Hypervisor.** (只针对Version 3.0.0;在3.0.1中，这一栏是只读的)选择一种在这个群集中运行的hypervisor。如果你选择宾是VMWARE，则需要提供关于VSPHERE群集的信息。对于VSHPERE服务器，我们建议先在VCENTER里将群集设备好，然后作为群集整体加入CLOUDSTACK。参看Add Cluster: vSphere。 **IP地址.** 针对NetScaler的NSIP（NetScaler的IP地址）。 **内部 DNS 1 和内部 DNS 2.** 区域内的系统虚拟机会用到这些DNS服务器(系统虚拟机是CLOUDSTACK本身会用到的虚拟机如虚拟路由器-VR，控制台代理虚拟机-CPVM，二级存储虚拟机-SSVM)，这些系统虚拟机通过管理网络访问这个DNS服务器。为机柜提供点配置的私有IP地址必须能路由到这些内部DNS服务器。 **内网 DNS 1 和内网 DNS 2.** 区域内的系统虚拟机会用到这些DNS服务器(系统虚拟机是CLOUDSTACK本身会用到的虚拟机如虚拟路由器-VR，控制台代理虚拟机-CPVM，二级存储虚拟机-SSVM)，这些系统虚拟机通过管理网络访问这个DNS服务器。为机柜提供点配置的私有IP地址必须能路由到这些内部DNS服务器。 **Lun # (for iSCSI).** 在iSCSI中，这是LUN的号码，例如： 3. **Lun.** LUN编号。比如：3。 **NFS服务器** NFS服务器的IP地址或相应域名。 **名称.** 为这个区域命名 **名称** 机柜提供点名称 **名称** 存储设备的名称 **子网掩码** 定义这些IP地址的子网掩码。 **网络** 定义这个提供点的子网络前缀。用CIDR格式。 **网络域** （可选） 如果你想为客户虚机网络定义一个域名，在此处输入后缀名。 **网络方案。** 你需要客户虚拟机可用的网络方案及服务 **重试次数** 认为操作失败前的最大重试次数，默认为2次。 **重用客户机流量**:如果选中此项，则会在全区域范围内重用客户机流量。 **重用公共网络流量**:启用这个选项，则可以在区域的范围内重用公共网络流量。 **密码。** 上面用户名的密码（主要针对XenServer 和 KVM的安装） **路径(对NFS).** 对NFS协议，这是从服务器上导出的路径 **路径(对SharedMountPoint).** 对KVM而言，这是每一个主机上挂载的主存储的路径。例如："/mnt/primary". **路径（对VMFS）.** 在vSphere中，这是数据中心名称以及数据存储名称的结合。格式如下："/" 数据中心名称 "/" 数据存储名称"。例如："/cloud.dc.VM/cluster1datastore". **路径** 这是一个datacenter name 和 datastore name集成在一起的名字。格式如"/" datacenter name "/" datastore name. 示例： "/cloud.dc.VM/cluster1datastore". **路径.** 服务器输出的存储路径。 **路径.**每一个主机的主存储的挂载路径。格式如 "/mnt/primary"。 **机柜提供点名称** 为此机柜提供点命名。 **Pod.** (只有在范围域内选择集群时可见)针对存储设备的Pod。 **内网接口** NetScaler接口配置为内网的一部分。 **协议.** 对XenServer主机而言，可以选择NFS，iSCSI或者PreSetup。对KVM而言，可以选择NFS或者ShareMountPoint。对vSphere而言，可以选择NFS或VMFS（iSCSI或FiberChannel，对Hyper-V而言，选择SMB。 **协议** 对于XenServer，选择NFS, iSCSI, 或 PreSetup.对于KVM，选择NFS, SharedMountPoint,CLVM, 或RBD.对于VSPHERE，选择VMFS（iSCSI 或FiberChannel）或NFS。本栏的其它选择依你选项不同而不同。 **协议** 对于XenServer，选择NFS, iSCSI, 或 PreSetup.对于KVM，选择NFS, SharedMountPoint,CLVM, 或RBD.对于VSPHERE，选择VMFS（iSCSI 或FiberChannel）或NFS。本栏的其它选择依你选项不同而不同。 **公共流量vSwitch类型**: 这个选项只有在你启用了Override Public Traffic之后才会显示出来，你可以选择一种合适的虚拟交换机。如果vmware.use.dvswitch这个全局参数设置为true，则默认选项为VMware vNetwork Distributed Virtual Switch. **公网接口.** NetScaler接口配置为公网的一部分。 **公有区域.** 一个公有区域可以被所有用户使用。而非公有区域会有一个指定的域名，只有指定域名中的用户才可以在那个区域里创建客户虚拟机。 **RAM超配比率**:输入RAM的超配比率。这个比率值决定了群集内每台虚拟机的MEM耗用比率。增加这个数据，则能使用更多的资源。如果不设置此值的话，默认值为1，这就表示没有使用超配。 **保留系统的网关** 这个机柜提供点内宿主机的网关。 **保留系统的子网掩码.** 定义此机柜提供点的子网前缀，用CIDR标示。 **SMB Domain**:仅当选择了SMB/CIFS时可用。是SMB共享目录活动哉的一部分。 **SMB Domain**\ (for SMB/CIFS)，仅在选择了 SMB/CIFS时可用。SMB共享的活动目录域 **SMB 密码** (for SMB/CIFS)，仅在选择了 SMB/CIFS时可用。此密码与账户关联。 **SMB Password**:仅当选择了SMB/CIFS时可用。此密码与账户关联。 **SMB 用户名** (for SMB/CIFS)，仅在选择了 SMB/CIFS时可用。此账户针对SMB拥有必要的权限。用户必须是Hyper-V管理组的成员。 **SMB Username**:仅当选择了SMB/CIFS时可用。此账户针对SMB拥有必要的权限。用户必须是Hyper-V管理组的成员。 **SR标签名(针对PreSetup).** 输入被设为外部CloudStack SR的标签名 **SR 名称标签** 输入在CLOUDSTACK外部设置好的SR的名称标签。 **范围.** 表明存储是对区域中的所有主机可用或者是仅对单一集群中的主机可用。 **服务器（针对NFS，iSCSI或PreSetup）** 存储设备的IP地址和DNS **服务器（针对VMFS）.** vCenter 服务器的IP地址和DNS **服务器** 存储设备的IP地址或DNS解析名称。 **服务器** vCenter服务器的IP地址或DNS名称。 **开始IP/结束IP.** 定义公网IP范围，这些IP用来访问公网或是从公网访问客户虚拟机。 **开始IP/结束IP.** 为客户机的网络配置一个可供互联网访问进出的IP地址范围。 **开始/结束系统保留的IP.** 这些IP地址是CLOUDSTACK给各种管理用的系统虚拟机使用的。如SSVM，CPVM,DHCP（VR）等。如需更多详情，请参看系统保留IP这一章节 **开始/结束系统保留的IP.** 这些IP地址是CLOUDSTACK给各种管理用的系统虚拟机使用的。如SSVM，CPVM,DHCP（VR）等。如需更多详情，请参看：`“系统保留IP地址” <http://docs.cloudstack.apache.org/en/latest/concepts.html?highlight=about%20pods#id4>`_. **标签.** (可选项)以逗号分隔的一系列存储设备的标签。它应该是磁盘方案中标签的等价集合或者父集。 **标签(可选).** 对此类存储设备以逗号分隔的标签列表。相当于在你磁盘提供者的标签集合或超集。 **目标IQN(for iSCSI).** 在iSCSI中，这是目标的IQN。例如，iqn.1986-03.com.sun:02:01ec9bb549-1271378984. **Target IQN.** ISCSI target的IQN编号，格式如：iqn.1986-03.com.sun:02:01ec9bb549-1271378984。 **类型.** 需要添加的NetScaler设备的类型。它必须是NetScaler VPX, NetScaler MPX, or NetScaler SDX当中的一种。至于这三种类型的比较，可以参看NetScaler负载均衡这一章节内容。 **用户名.** 用户名为root。 **用户名.** 通常为root **用户名/密码.** 访问此设备的认证许可。CLOUDSTACK使用这些认证信息访问此设备。 **VLAN** 公网流量的VLAN号。 **vCenter Datacenter**:输入此群集拥有的vCenter Datacenter名称，比如："cloud.dc.VM". **vCenter主机**: VCENTER的主机的IP地址或主机名。 **vCenter密码**: 输入上面用户的密码。 **vCenter用户名**:输入CLOUDSTACK连接到VCENTER所用的用户名。这个用户名必须要有所有的管理权限。 最少100GB容量 :ref:`adding-a-host-vsphere` :ref:`adding-a-host-xenserver-kvm` CIDR描述了管理存在的CIDR。在使用vSphere部署时，此项必须设置。推荐其他部署时也同样设置。例如：192.168.3.0/24 二级存储必须与他服务的客户虚拟机在同一个区域。 关于配置参数 添加群集：KVM 或者 XenServer 添加群集：vSphere 添加主存储 添加二级存储 在增加地域的选择里，输入地域1的ID,名称，端口（1,region 1,<region.1.IP.address>:8080/client） 在增加地域的选择里，输入地域2的ID,名称，端口（2,region 2,<region.2.IP.address>:8080/client） 在地域内增加一个区域，参阅 :ref:`adding-a-zone`。 在提供点内增群集(可选)。参阅 :ref:`adding-a-cluster`。 在群集内增加主机(可选)。参阅 :ref:`adding-a-host`。 在区域内增一个机柜提供点(可选)。参阅 :ref:`adding-a-pod`。 为群集增加主存储。参阅 :ref:`add-primary-storage`。 为区域增加辅助存储。参阅 :ref:`add-secondary-storage`。 添加主存储 增加地域(可选) 添加二级存储 增加第三个或是更多的地域 添加群集 添加一个宿主机 添加一个宿主机(XenServer 或KVM) 添加一个宿主机(vSphere) 添加一个机柜提供点 增加一个地域 添加一个新的XenServer或KVM主机 增加一个区域 为每一个区域添加二级暂存区 基于SolidFire插件添加的主存储能够使CloudStack提供较好的QoS保证。 添加高级区域 在所有配置完成后，CloudStack会执行初始化。根据网络速度的不同，可能会需要30分钟或更多的时间。当初始化完成后，管理员控制面板会出现在CloudStack的界面中。 当管理节点服务器安装结束并正常运行之后，你可以开始将计算资源池纳入其管理范围。关于CloudStack云计算系统是如何组织构架的，请参阅：`“Cloud Infrastructure Overview” <http://docs.cloudstack.apache.org/en/latest/concepts.html#cloud-infrastructure-overview>`_. 当你选择高级区域以后，你需要提供以下信息，然后点击下一步。 当你选择了基本区域之后，你需要输入以下细节信息，才能进入下一步。 以下的hypervisor都支持标准化的iSCSI, SMB, 或 NFS服务器。 为物理网络上承载的每一种CLOUDSTACK网络流量类型赋予一个标签。这些标签必须与你已在宿主机上设置的（网桥）标签名一致。如果要编辑标签，点击流量类型上的编辑按钮，在弹出的对话框中输入相应名称，然后再点击OK即可。 基本区域配置 确保你已按CLOUDSTACK的要求，安装并设置好了hypervisor。 当你在添加一个新的宿主机之后，你必须先在宿主机上安装一种hypervisor。CLOUDSTACK是可以管理多种hypervisor的。 当你在配置宿主机之后，你需要在宿主机上安装hypervisor软件。你也需要事先了解CLOUDSTACK所能支持的hypervisor种类及版本，以及是否需要额外的配置信息。关于这些配置的详细信息，参看： 当你在填写这些信息时，你需要准备好二级存储的NFS共享，并且安装好CLOUDSTACK最新的系统虚拟机模板。更多信息，可以查看Adding Secondary Storage : 在安装过程结束后, 管理服务器应该是运行状态. 请确保管理服务器安装完成并正确运行. 忽略内部DNS，使用外部DNS1和DNS2 选择一种网络类型： 选择这个群集的hypervisor类型。 选择你想在哪个机柜提供点增加群集。 选择你刚才添加的区域。 选择在物理网络里需要承载的流量类型。 Citrix XenServer安装及配置 为CloudStack安装Citrix XenServer 点击增加群集。 点击添加主机 点击添加实例，并完成向导指示的步骤。 点击增加提供点。（此处提供点对应于翻译此翻译文档的机柜提供点） 点击 添加主存储 点击增加地域，在弹出的对话框里，输入以下字段： 点击添加二级存储。 点击添加区域，向导界面就会出现。 点击启动虚拟机，你的虚拟机将会被创建并被启动。可能会需要一点时间来下载模板并完成启动。你可以在实例页观察虚拟的过程。 点击启动 点击下一步 点击确定。 点击查看群集。 点击查看主机。（此处主机即可此翻译文档中宿主机的同一概念。） 点击添加二级暂存区按钮 点击计算和存储标签。在图中的机柜提供点里，点击查看全部。 点击计算标签。在机柜提供点栏里点击查看全部。选择你想添加群集的机柜提供点。 点击计算这个标签。 点击计算标签。在群集节点里，点击查看全部。 点击删除区域按钮。 点击设定标签 在相应的群集里添加主机。 选择你想删除的区域。 点击你想限定的资源名称。 CloudStack提供了各类设置，可以用来限制某性配置功能，打开或关闭云中的某些功能。一旦你的管理服务器运行后，你可能需要设置一些参数，依赖于你打开了哪些参数。也可以在全局设置中使用默认值，他们都会在云中全部起作用，除非在低级别配置时配置有错误。你也可以设置局部参数，在账户，区域，集群，主存储级别时，允许覆盖全局配置参数 配置参数 配置需求： 配置公网IP地址范围，输入以下细节，然后点击添加。如果需要，你可以重复此过程以便添加更多的公网IP地址。当这一切完成之后，点击下一步。 为客户来宾配置网络，提供好如下信息，然后点击下一步。 配置存储插件 配置CloudStack安装 恭喜！你已经完了CloudStack的安装。 将帐号，用户，域信息数据表从已存在的地域的数据库拷贝到新的地域里。 将帐号，用户，域信息数据表从地域1的数据库拷贝到地域2数据库中。 将管理服务器中/usr/share/cloudstack-common/scripts/vm/hypervisor/xenserver/cloud-setup-bonding.sh拷贝到master主机中并确认该脚本可执行。 创建NFS二级暂存区，必须要勾选此项。 在VCENTER里新建一个群集。请参看VCENTER的相关操作指地完成这一。在VCENTER里建立群集的大致过程如下： 在网络中允许的默认每秒传输数据容量，单位MB 在具有路由的虚拟网络中的虚拟机的默认域名 DefaultSharedNetscalerEIPandELBNetworkOffering DefaultSharedNetworkOffering DefaultSharedNetworkOfferingWithSGService 定义地域(可选)，参阅 :ref:`adding-regions`。 删除一个地域 描述 通过使用这个参数来决定虚拟中心连接的失效时间。默认值是20分钟。增大此值，以避免在VMware部署中的错误，因为VMware的操作可能会需要超过20分钟的时间。 用来决定CloudStack是否使用主机本地的存储存放数据盘，模板，快照。CloudStack默认不使用本地存储。如果你想使用本地存储时可设置为是，并且你也知道选择本地存储的可信赖以及随时读取的功能。 在一个VSPHOERE群集里不要超过8个主机。 每一个二级存储服务器必须对区域的所有主机可用。 每一个群集必须包含相同的 hypervisor。 每一个地域都有专属的CloudStack实例。因此，当你要部署一个新的地域时，首先要做的就是在一个或多个节点上安装管理节点服务器。在按照安装指南安装此节点的数据库时，需要在命令行上加上参数 ``-r <region_id>`` 。默认的地域的region ID为1，故而第一个新增地域的region ID应该为2. 打开或关闭动态规模虚拟机 端点--可以登录到新地域中管理服务器的URL。端点的格式为<region.2.IP.address>:8080/client。 确保二级存储服务器上没有存储任何数据。添加服务器到CloudStack时，会损坏服务器上原有已存的数据 为群集输入一个名称。这个名称必须为CLOUDSTACK里没有使用的名字。 在随后的对话栏里，输入以下细节信息。 即使UI允许你不勾选此项，也不要这样做。此项以及下面的三项内容是必须要填写的。即使二级存储提供商使用了Swift或S3，在每个区域中NFS暂存区仍是需要的。 每一个区域至少有一个NFS存储区。每个区域允许存在多个NFS服务器。按以下步骤为区域添加一个二级暂存区 值域 填写以下内容： 填写对话框中的内容，然后点击确定 找到你想使用的特定资源的名称。例如，如果你在基础架构中，在区域，集群，主存储上点击查看全部， 首先，运行这个命令拷贝数据库的内容： 对于KVM，每一个群集不要超过16个主机。 对于XenServer节点，此 是/否 变量指示CloudStack允许XenServer主机的iSCSI的多路径。默认值为否。如果希望CloudStack允许多路径，请置为是。如果值为是，基于NFS部署的XenServer主机允许多路径。当然这不会影响NFS的操作并且没有任何危害。 对于 XenServer，群集内不要超过8个主机。 对于要加入群集的其它主机，运行下面的命令就会将主机加入XenServer计算池内。 硬件方面的需求，请参看CLOUDSTACK安装指南中关于你具体安装的hypervisor的要求。 关于使用虚拟机的更多信息，包括如何允许进入虚拟机的网络流量，开始，停止，删除虚拟机以及从一个主机上迁移虚拟，参看管理员手册中的使用虚拟部分。 对于VSPHERRE服务器，我们推荐的方案是先在VCENTER里建好群集，然后将整个群集加入到CLOUDSTACK群集中。这个群集需要以下条件： 对于vSphere主机，我们推荐先在VCENTER里建好群集，然后将整个群集加入CLOUDSTACK。关于如何在VCENTER里添加群集，可以参看VSPHERE的相关内容章节。 全局设置。这会显示参数值，并附有简单的说明。 点击实例标签，筛选我的实例。 全局配置参数的精细设置 在部署云的过程中将云资源按地域组织起来是是一个可选的步骤。关于地域的描述，可以参阅 `“关于地域” <http://docs.cloudstack.apache.org/en/latest/concepts.html#about-regions>`_. 硬件要求： 地域中不支持多类二级存储共存。每一个地域只能使用NFS，S3或Swift其中的一种。 主机名---此主机的IP地址或DNS名称。 主机标签(可选)。此标签用于将主机分类，以便更好的后期维护。比如，如果你只想此宿主机用于具有HA（high availability）高可用性能的虚拟机，那么，你可以将此宿主机设置为云里相关的HA标签。(参看全局设置参数里的ha.tag)，关于HA的更多信息，请参看HA虚拟机和HA宿主机的相关章节。 对于VSPHERE的主机管理是结合VCENTER和CLOUDSTACK WEB UUI管理界面一起完成的。CLOUDSTACK需要所有的主机都在同一个群集里，但群集可能只是由一个主机构成。作为一个管理员，你必须决定到底是使用一个主机一个群集还是多个主机一个群集。多个主机一个群集，可以实现CLOUDSTACK的一些高级功能，如热迁移等。当然，此群集需要有NFS或ISCSI等这个共享存储支持。 虚拟化能力。这会显示虚拟化版本以及所支持的最大用户数。 ID--唯一标识号，这个ID与安装管理服务器过程中，设置数据库时的数字相同；例如ID为2。 如果值为否，用户将不能创建公共模板。 如果使用了网卡绑定，管理员必须和群集中其它主机一样连接网线到这个新的主机 如果一个网卡已在使用，则这些IP地址的CIDR必须和机柜提供点的CIDR一致。 如果使用了共享挂载存储，则管理员要确保群集里所有新机方和其它主机一样有相同的存储挂载点。 如果全局参数vmware.use.dvswitch为true，则默认的选项为VMware vNetwork Distributed Virtual Switch。 如果值为是，并且如果账户有一个或多个专用的客户VLAN范围，在账户专用的VLAN用完后，可从系统池中获取VLAN。 如果值为是，并且如果账户有一个或多个专用的公用ip范围，在账户专用的IP用完以后，可以从系统池中获取ip. 如果在CLOUDSTACK中使用了OpenVswitch网桥，则在操作前，需要将KVM计算主机上的agent.properties文件的network.bridge.type参数设置为openvswitch。 如果你正在使用Hyper-V主机，确保你已经创建了一个SMB共享目录。 如果决定扩展你的部署，可以增加更多的主机，主存储，区域，资源池以及集群。 如果你需要安全组，选择这个选项。 当你没有共享的主存储时，则必须将全局参数的system.vm.local.storage.required设置为true,否则，将不能启动虚拟机。 如果你没有执行任何操作来定义地域, 那么云环境中所有的资源域都会组织到一个默认的地域里. 这个地域的ID是1。当然，你可以通过CloudStack的WEB UI来编辑此默认地域的名称和URL网址。 如果你启用了Nexus dvSwitch，下面关于dvSwitch的数据也需要设置： 如果，你在CLOUDSTACK内安装了Citrix NetScaler应用，并且你需要Elastic IP和Elastic Load Balancing这些功能的话，选择这个选项。EIP 和ELB技术在安全组启用的情况下，可以提供1：1的NAT映射和负载均衡功能。 如果你还没有这么作，就需要在主机上安装hypervisor软件。你需要知道CLOUDSTACK支持哪些hypervisor，以及主机上还需要哪个特别的配置。可以参看CLOUDSTACK安装指南的相关章节，找到具体的安装信息。 如果你希望通过安全组来隔离客户虚拟机流量，选择这个选项。(参看通过安全组隔离虚拟机这一章节。) 在Hypervisor里，选择VMware。 在二级存储中，点击 查看全部。 在选择视图中，选择二级暂存区 在选择视图中，选择以下一个： 在一个新的群集里，CLOUDSTACK会添加第一个宿主机。当然，之后你可以添加更多的宿主机。关于宿主机的概念，可以参看About Hosts的章节。 在一个新的群集，CLOUDSTACK会添加好第一个宿主机，随后，你也可以自行添加更多的宿主机。关于什么是宿主机，参阅 `“关于主机” <http://docs.cloudstack.apache.org/en/latest/concepts.html?highlight=about%20pods#about-hosts>`_. 在一个新的群集里，CLOUDSTACK会添加第一个主存储。当然，你也可以在随后添加更多的主存储。关于主存储的细节，可以参看相关章节：Primary Storage 在一个新的群集，CLOUDSTACK会添加好第一台主存储服务器，随后，你也可以自行添加更多的存储服务器。关于什么是主存储服务器，参阅 `“关于主存储” <http://docs.cloudstack.apache.org/en/latest/concepts.html?highlight=about%20pods#about-primary-storage>`_. 在一个新的机柜提供点里，CLOUDSTACK会为你加第一个群集。当然，你也可以以后再添加其它的群集。如果想多了解群集，你可以参看群集的相关章节。 在一个新的机柜提供点，CLOUDSTACK会添加第一个群集。当然，随后你可以添加更多的群集。关于什么是群集，参阅 `“关于群集” <http://docs.cloudstack.apache.org/en/latest/concepts.html?highlight=about%20pods#about-clusters>`_. 在一个新的区域，CLOUSTACK总是会为你添加第一个机柜提供点。当然，在区域设置完成之后，你可以添加理多的机柜提供点。关于机柜提供点的详细，参看此URL：`“About Pods” <http://docs.cloudstack.apache.org/en/latest/concepts.html?highlight=about%20pods#about-pods>`_. 在一个新的区域里，CLOUDSTACK会添加第一个二级存储。关于什么是二级存储，请参阅 `“关于辅助存储” <http://docs.cloudstack.apache.org/en/latest/concepts.html?highlight=about%20pods#about-secondary-storage>`_。 在数据盘方案中，如果可以，添加另一块数据盘。此盘可用，但并未在客户机中挂。例如，基于XenServer的Linux，重启虚拟机后会在/dev/xvdb中看见客户机。如果操作系统内核中使能了PV，重启并不是必要的一步。 在默认网络中，为客户机选择主网络。在试用安装中，这里可能只有一个选项。 在动作栏，点击编辑按钮可修改一个值。 在动作栏，点击编辑按钮可修改一个值。如果查看虚拟化能力，必须先点击虚拟化名称以显示编辑页。 在对话栏的群集里，点击查看全部。 在结构图的主存储节点上，点击 查看全部。 接下来的操作，你需要确保已设置好MYSQL数据库的root用户密码，这也是CloudStack推荐的操作。 在左侧导航栏中，点击全局设置 在左侧导航栏中，点击基础架构或账户，取决于你想设定的内容。 在左侧导航栏中，点击基础架构 在左边的导航栏中，点击区域（为文档翻译中地域的概念，英文为region，下同） 在左边的导航，选择基础架构。 在左右的导航栏里，点击基础架构。在区域里，点击查看全部。然后点击你想增加群集所在的区域。 在左边的导航栏里，点击区域基础架构。在区域里，点击查看全部。然后在相应的区域里添加主机。 在左侧导航栏中，点击基础架构，在区域中，点击 查看更多，然后点击你所需要添加主存储的区域名称。 在左侧的导航栏里，选择基础架构。在区域栏目里，选择查看全部。然后，点击相应的区域以添加新的机柜提供点。 在模板选择中，选择在虚拟机中使用的模板。如果是初次安装，可能仅提供了CentOS的模板。 初始化及测试 初始化并测试云计算环境。参阅 :ref:`initialize-and-test`。 在每个额外的地域中安装CloudStack管理节点，并在安装数据库时为其设置不同的地域ID（region ID）。 KVM主机的额外要求 KVM的安装和配置 KVM vSphere安装及配置 登陆：<region.1.IP.address>:8080/client。 以系统管理员身份登陆第一个地域的CloudStack(登陆URL：<region.1.IP.address>:8080/client)，在增加地域时，输入地域ID ,名称，端点<region.3.IP.address>:8080/client。 以系统管理员身份登陆CloudStack的第一个地域(登陆<region.1.IP.address>:8080/client) 以系统管理员身份登陆第二个地域的CloudStack（登陆URL：<region.2.IP.address>:8080/client），在增加地域时，输入地域的ID,名称，端点<region.3.IP.address>:8080/client。 以系统管理员身份登陆CLOUDSTACK（登陆URL：<region.3.IP.address>:8080/client）。 登陆到CLOUDSTACK的WEB UI，点击区域导航栏，选择你想删除的地域，然后，删除。例如，如果你想删除地域3： 登陆CloudStack用户界面。(参阅 `“Log In to the UI” <http://docs.cloudstack.apache.org/projects/cloudstack-administration/en/latest/ui.html#log-in-to-the-ui>`_)。 作为管理员登录到CloudStack用户界面。 以根管理员身份登录CloudStack界面。 以系统管理员身份登陆CloudStack WEB用户界面，参阅 `“登录用户界面” <http://docs.cloudstack.apache.org/projects/cloudstack-administration/en/latest/ui.html#log-in-to-the-ui>`_. 登陆到CloudStack用户界面。参阅 `“登录用户界面” <http://docs.cloudstack.apache.org/projects/cloudstack-administration/en/latest/ui.html#log-in-to-the-ui>`_. 以管理员登录界面。 登陆到UI界面。 MVIP%3D【管理虚拟IP地址】，后面可以使用端口号 确保 hypervisor在加入CLOUDSTACK前没有运行任何虚拟机。 确保在你想加入CLOUDSTACK群集前，VSPHERE没有任何虚拟机。 确保新主机和群集内其它主机有一个的网络设置（客户机，内网，外网网络）。 确保你在安装管理节点时，准备了系统虚拟机模板，参见 `“准备系统虚拟机模板” <installation.html#prepare-the-system-vm-template>`_. 通过CloudStack API命令返回每页中显示条目的最大值。在云级别中适用此限制，不同的云之间会有所不同。通过使用page和pagesize参数调用特定的API，将其修改为较小的值。要了解更多，请参阅开发指南。默认值：500 最小容量取决于你的需求。 NFS NFS服务器。二级暂存区的区域名称。 二级存储器或Linux NFS服务器 kvm的默认路由模板名称 VMware的默认路由模板名称 XenServer的默认路由模板名称 名称--为新的地域提供一个描述性名称。 名称--需要给二级存储一个描述性名称。 网络方案 Nexus dvSwitch IP地址: Nexus VSM的IP地址 Nexus dvSwitch 密码:上面用户名的密码。 Nexus dvSwitch 用户名：具体有 Nexus VSM 权限的用户名。 现在，可以添加hypervisor主机到CLOUDSTACK了。具体的添加技巧和过程取决于使选用的hypervisor类型。 现在，开始在 CloudStack内加入一个新的地域。 现在，执行一次相同的操作，在地域2中加入默认地域1. 在区域页面，点击查看全部。 一旦新地域的CloudStack管理服务器处于运行状态，在CloudStack WEB UI中使用添加地域按钮增加新的地域。以下以新增地域3作为示例： 可以给你的虚拟机一个名字或组名，允许使用你喜欢的描述性文字。 安装步骤概述 密码---这通常是指XenServer或KVM安装时设置好的密码。 路径。二级暂存区所在区域的路径 在主机成功加入群集之后才能添加主存储。 提供界面要求的如下信息。这些信息的值可以参考VCENTER中对应的值。 提供弹出对话框中所需要的信息。依据你所选协议的不同，所需的信息会有所不同。 提供主机的如下信息。 提供者。选择S3，Swift，NFS或者CIFS。此时会出现需要填写的相关内容。根据提供者的不同，需要的内容会有所不同。要了解更多，可参考提供者文档（如S3或Swift网站）。NFS可用于区域存储，其他的可用于地域存储。对 Hyper-V，选择 SMB/CIFS。 删除项目帐户. 在地域2的数据库中运行如下命令: 在地域3上运行这些命令，以便删除项目管理帐号： 在其它宿主机上复杂此操作过程。 在新的地域里，也同样增加所有的已存在的域域，例如，如果新地域是第三个CLOUDSTACK地域，刚需要其WEB UI里增加前两个地域信息： 在地域2里重复这些步骤：<region.2.IP.address>:8080/client。 XenServer和KVM宿主机的相关要求 重新启动地域2中的管理节点服务。 在新地域里重启CLOUDSTACK管理节点的服务。 黑名单中的路由不能用于虚拟机的私有网关来创建静态路由 运行脚本： SMB/CIFS (Hyper-V) SVIP%3D【管理虚拟IP地址】，后面可以使用端口号 选择服务方案。确保已有的硬件允许你开始选择服务方案。 设置默认区域为空白(NULL)： 设定全局配置参数 设定全局参数 SharedMountPoint 定义每个物理网络上的客户流量的VLAN ID范围(参看 VLAN 分配示例 )，然后点击下一步。 当未过载使用时说明是否预留cpu。防止cpu过载，cpu总是有预留的。 当未过载使用时说明是否预留内存。防止内存过载，内存总是有预留的。 主存储的系统需求 二级存储的系统需求 CLOUDSTACK安装指南提供了如何安装配置各种hypervisor的步骤。你可以参考相关章节找到你所使用的hypervisor的安装指南，以及为了加入CLOUDSTACK而需要的额外的配置步骤。 第一个地域：默认地域 SolidFire存储插件是CloudStack标准安装的一部分，不需要另做其他准备工作。 创建存储池的API已经被扩展到支持插件式存储供应商。下面给出了当向基于SolidFire插件的CloudStack添加存储时可使用的参数列表。 每一个CloudStack的功能文档，都会引导你到应用参数名，下表给出了一些更有用的参数。 以下全局配置参数更加精细。以下列出的参数有三个不同的范围，账户，集群和区域。 这个标签标示一个在全云中使用的特定主机，作为专用高可用性主机。被标示的主机仅用作使能的高可用性虚拟机，他们在其他主机失败时启动。例如，在向云中添加一个新主机时可以标明主机的标签为ha.tag，将其设为高可用性主机。 百分比，其值从0到1，cpu的使用率超过设定值后，分配器将关闭进一步的使用。设定相应通知限值要低于此值，以便能够被提前通知到。 百分比，其值从0到1，分配存储的利用率超过设定值，系统将会发送警告 百分比，其值从0到1，已分配存储的使用率超过设定值后，分配器将关闭存储池，因为可用于分配的存储要小于限值。 百分比，其值从0到1，cpu的使用率超过设定值，系统将会发送警告 百分比，其值从0到1，内存的使用率超过设定值，系统将会发送警告 百分比，其值从0到1，内存的使用率超过设定值后，分配器将关闭进一步的使用。设定相应通知限值要低于此值，以便能够被提前通知到。 百分比，其值从0到1，可用存储的比率超过设定值，系统将会发送警告 百分比，其值从0到1，已分配存储的使用率超过设定值后，分配器将关闭存储池，因为可用于分配的存储要小于限值。 应当给远程访问vpn的客户分配一个ip范围。范围中的第一个ip被vpn 服务器所使用。 根据选择的基本或高级区域的不同步骤会存在差异。选择适合你的步骤继续： 存储服务器应该配置大容量硬盘，且硬盘配置硬件RAID控制器。 在区域的群集中当，主存储的标签都必须是唯一的。比如，如果你在A群集当中提供的主存储的标签为T1和T2，那么，你在同一个区域的另一个群集提供的主存储标签也必须为T1和T2。 流量类型分为管理流量，公网流量，来宾客户流量，和存储流量。关于这些流量的更多信息，可以点击相关图标得到一些帮助。这个屏幕显示的是已分配好的流量类型。如果要继续增加，可以拖动相关流量类型到网络里，当然，也可以将网络更改成你认为合适的名字。 url参数有时是唯一的，他的值可以包含额外的键值对。 然后，运行这个命令将数据库的内容放到新的地域数据库当中去（如地域3）： 然后，运行这条命令将数据放入地域2的MYSQL数据库： 在主机添加好之后，可能会有稍稍的延迟才会有WEB UI界面中显示出来。 当群集建好之后，会有稍稍的迟延之后，才会有UI里显示出来。 这些步骤确保你已在宿主机上安装好hypervisor，并且已登陆CLOUDSTACK的WEB UI。 这些流量类型标签只是定义了区域内的第一个集群的hypervisor。对于其它hypervisor，则这个标签可以在区域创建完成之后配置。 这是管理服务器的IP地址。如果你部署了多台管理服务器，你应该在这里输入一个内网可以访问到的负载均衡IP地址。 这用来保护内部网络避免通过使用模板下载功能暴力尝试下载文件。可以用逗号分隔多个CIDR。如果需要网址来匹配CIDR，二级存储虚拟机会使用私有网络来获取网址。其他网址则会通过公共接口。建议将其设成1或2个内部用来保存模板的地址，如：192.168.1.66/32 这一章节的内容将会告诉你如何增加地域，区域，提供点，集群，主机，存储和网络。如果你不熟悉这些概念，可以参阅: `*云基础设施的概念* <http://docs.cloudstack.apache.org/en/latest/concepts.html#cloud-infrastructure-concepts>`_. 在CLOUDSTACK中添加一个VSHPERE群集： 增加第三个或是更多地域的操作与增加第二个地域的操作类似，但是，你必须重复这几个特定的操作步骤： 配置第一个群集，输入以下这些信息，然后点击下一步。 配置第一个宿主机，输入以下信息，然后点击下一步： 开始配置第一个机柜提供点，输入以下这些信息，然后点击下一步继续。 配置第一个主存储，输入以下信息，然后点击下一步： 为了准备区域的二级存储，你应当在管理节点安装时创建并挂载了NFS共享目录。参见 `“准备NFS共享目录” <installation.html#prepare-nfs-shares>`_. 准备云基础架构，或是进行扩展时，请遵从如下步骤： 为了使用虚拟机，点击通讯视图按钮以启动一个通讯窗口. |ConsoleButton.png: button to launch a console| 通过以下几步来设定全局配置参数。在整个CloudStack的部署过程，默认值会起作用。 使用以下几步来设置本地配置参数，包括账号，区域，集群或主存储。这些值会覆盖全局配置值。 使用搜索框来缩小你所赶兴趣的内容。 通过下面的步骤来添加除默认地域外的第二个地域. 用来进行cpu过度提供计算。可利用的cpu是实际cpu容量与cpu过度提供因子的乘积。 用来进行内存过度提供计算。 用来进行存储过载计算，可利用的存储是实际存储容量与存储过载因子的乘积。 用户名--通常为root用户。 VMFS VMware vSphere 安装和配置 值 确保系统已经准备完成。在左侧导航栏中，选择 模板 ，点击CentOS 5.5 (64bit) no Gui (KVM) template，查看其状态是否为 下载完成。在状态没有变成下载完成前，不要继续操作。 我们强烈推荐使用多网卡，因为多网卡就可以配置不同的子网。 当复制和粘贴命令时，请确保没有多余的换行符，因为一些文档查看器可能会在复制时加上换行符。 当添加主存储时，存在以下这些限制： 如果提前准备好了主存储，请确认主存储目录里没有任何数据（比如空的SAN卷或NFS共享目录）。将主存储加入CLOUDSTACK时，会清除主存储里的一切数据。 当你往CLOUDSTACK里新增一个hypervisor宿主机时，此宿主机上一定不能有虚拟机在运行（全新的宿主机）。 当你要增加一个新的区域时，你会被提示需要同时配置物理网络以前第一个机柜提供点，集群，宿主机，主存储，二级存储。 当你添加一个新的区域时，主存储作为操作过程的一个步骤已建好。以后，你也可以随时添加主存储。当在添加新的群集或是添加新的主机时都可以添加主存储。 当你创建一个新的区域时，第一个二级存储作为创建的一部分 。为了添加更多的服务器，你可以随时添加二级存储服务器到已创建的区域中。 当你添加一个区域时，CLOUDSTACK会添加第一个机柜提供点。用本章节的办法，你可以随时添加更多的机柜提供点。 当你开始部署CLOUDSTACK时，hypervisor宿主机必须不能有已在运行的虚拟机。 当你完成这些步骤以后, 你将部署如下的一个基本结构: 当所有主机都加入XenServer计算池后，运行cloud-setup-bond脚本。这个脚本将会完成配置工作，并且在群集的新主机里设置相关的绑定。 XenServe宿主机的额外要求 XenServer和KVM可以在任何时间被加入CLOUDSTACK群集。 你需要告诉CLOUDSTACK它所能管理的宿主机。宿主机存在于群集内，所以，在为云里添加主机之后，必须先至少存在一个群集。 区域，即二级暂存区所在的区域。 `“配置高级区域” <#advanced-zone-configuration>`_ `“配置基本区域” <#basic-zone-configuration>`_ 账户 allow.public.user.templates blacklisted.routes capacityBytes=【来自SAN的全部字节数】 capacityIops=【来自SAN的全部IOPS号】 集群 cluster.cpu.allocated.capacity.disablethreshold cluster.cpu.allocated.capacity.notificationthreshold cluster.memory.allocated.capacity.disablethreshold cluster.memory.allocated.capacity.notificationthreshold cluster.storage.allocated.capacity.notificationthreshold cluster.storage.capacity.notificationthreshold clusterAdminPassword%3D[集群管理员密码] clusterAdminUsername%3D[集群管理员用户名] clusterDefaultBurstIopsPercentOfMaxIops%3D【最小的IOPS \* clusterDefaultBurstIopsPercentOfMaxIops 参数，可以是十进值】 clusterDefaultMaxIops%3D【卷的最大IOPS号，在管理员或用户没有给出此号时使用】 clusterDefaultMinIops%3D[卷的最小IOPS号，在管理员或用户没有给出此号时使用] command=createStoragePool cpu.overprovisioning.factor default.page.size enable.dynamic.scale.vm guest.domain.suffix ha.tag host hypervisor=任意 iSCSI management.network.cidr mem.overprovisioning.factor name=【主存储的名称】 network.throttling.rate pool.storage.allocated.capacity.disablethreshold pool.storage.capacity.disablethreshold preSetup provider=SolidFire remote.access.vpn.client.iprange router.template.kvm router.template.vmware router.template.xen scope=区域 secstorage.allowed.internal.sites storage.overprovisioning.factor url=【键值对下面有详细说明（值由url编码，例如，'='编码后为‘%3D’】 use.external.dns use.local.storage use.system.guest.vlans use.system.public.ips vmware.reserve.cpu vmware.reserve.mem vmware.vcenter.session.timeout xen.setup.multipath 区域 zoneId=【你的区域ID】 |addcluster.png: add a cluster| |provisioning-overview.png: Conceptual overview of a basic deployment| |vsphereclient.png: vSphere client|