source/adminguide/locale/zh_CN/LC_MESSAGES/hosts.mo (25 lines of code) (raw):
�� � $ ,
,
* -
X
e $ � * � - � � $ � ! �
� � � $ � � B � T � V 4 A ] { � � 5 � * � ( ` = D � G � � + � � � % � 6 � 0 � 2 � O 7 8 & p � � < ) y f � � m � F " ^ o � � � q { � 2 &" < Y" G �" 1 �" . # 0 ?# p$ 5 t$ - �$ , �$ < % B% c% * w% � �% N 9& 1 �& 0 �& � �& � u( - .) h \) � �) # g* �* �* �* �* " �* d + n+ D �+ C �+ 4 , D, z J, D �, -
- � 8-
. $1 E1 } H2 - �2 D �2 � 93 � �3 & �4 �4 � �5 � q6 � 7 � �7 > v9 I �9 � �9 � �; t '< P �< K �< 9= : X> K �> �> ? �> . <? 3 k? � �? T@ �A �A � B % �B �B . �B �B C C -C IC i gC �C �C �C C D � FD * �D F � 1H � �I Z uJ ? �J K #K -K 1 LK � ~K V M � nN c 1O x �Q R
R .R � KR $ T � ET + CU & oU + �U % �U �U �U �U V � V �V �V � �V � �W w qX �X
Y � Y - Z � CZ �Z �Z
[ )[ E[ a[ w[ 0 �[ + �[ �[ F \ @ K\ G �\ � �\ [] � j^ #_ 6 0` & g` " �` � �` / Ia & ya � �a 1 6c . hc � �d d Ie �e 0 �e ` �e � Qf P �f ! &g � Hg * �h B i H Ji * �i * �i � �i �j $ �j 1 �j 1 0k = bk �k �k �k r �k K al 0 �l 0 �l R m � bn o I o � io �o p 'p 4p Pp dp W zp �p E �p E .q $ tq �q o �q 3 r Dr � `r 7 s Fu � _u | v ( �v 4 �v | �v � cw + !x � Mx r y v �y w �y k tz / �{ B | F S| � �} i &~ C �~ S �~ � ( C '� = k� 3 �� - ݀ 2 � & >� � e� ]
� h� ' u� ~ �� � =� 0 W� �� ��
�� �� �� M ք $� 7� >� . K� � z� � � � � 3 �� u �� K 7� @ �� Ċ ъ ۊ 6 � t +� �� � �� � X� q Q�
Ð ΐ ؐ (Supported for XenServer, KVM, and VMware) (XenServer) For more information, see `Highly Recommended Hotfixes for XenServer in the CloudStack Knowledge Base <http://docs.cloudstack.org/Knowledge_Base/Possible_VM_corruption_if_XenServer_Hotfix_is_not_Applied/Highly_Recommended_Hotfixes_for_XenServer_5.6_SP2>`_. **Guest Type**: Select Isolated. **Specify VLAN**: Select the option. **To place a server in Maintenance Mode:** **To take a server out of Maintenance Mode:** 500-599 600-799 800-899 900-999 A node cannot be removed from a cluster until it has been placed in maintenance mode. This will ensure that all of the VMs on it have been migrated to other Hosts. To remove a Host from the cloud: Adding Hosts Adding Non Contiguous VLAN Ranges Additional hosts can be added at any time to provide more capacity for guest VMs. For requirements and instructions, see `“Adding a Host” <http://docs.cloudstack.apache.org/projects/cloudstack-installation/en/latest/configuration.html#adding-a-host>`_. All VMs are required to support the virtio drivers. These drivers are installed in all Linux kernel versions 2.6.25 and greater. The administrator must set CONFIG\_VIRTIO\_BALLOON=y in the virtio configuration. All VMs should have a balloon driver installed in them. The hypervisor communicates with the balloon driver to free up and make the memory available to a VM. Assigning VLANs to Isolated Networks Balloon Driver CPU and memory (RAM) over-provisioning factors can be set for each cluster to change the number of VMs that can run on each host in the cluster. This helps optimize the use of resources. By increasing the over-provisioning ratio, more resource capacity will be used. If the ratio is set to 1, no over-provisioning is done. Capacity = 2 GB Over-provisioning factor = 2 Capacity after over-provisioning = 4 GB Change the password on all hosts in the cluster. Now the password for the host and the password known to CloudStack will not match. Operations on the cluster will fail until the two passwords match. Changing Host Password Click Apply. Click Edit |edit-icon.png|. Click Enter Maintenance Mode. Click Exit Maintenance Mode. Click Physical Network. Click the Compute tab. Click the Enable/Disable button. |enable-disable.png| Click the pod or cluster name in the list. CloudStack accounts. CloudStack accounts. Account-specific VLAN chosen by CloudStack admin to assign to that account. CloudStack accounts. Account-specific VLAN is chosen from this pool. CloudStack accounts. Can be scoped by project, domain, or all accounts. CloudStack automatically creates and destroys interfaces bridged to VLANs on the hosts. In general the administrator does not need to manage this process. CloudStack manages VLANs differently based on hypervisor type. For XenServer or KVM, the VLANs are created on only the hosts where they will be used and then they are destroyed when all guests that require them have been terminated or moved to another host. CloudStack provides you the ability to control VLAN assignment to Isolated networks. As a Root admin, you can assign a VLAN ID when a network is created, just the way it's done for Shared networks. CloudStack provides you with the flexibility to add non contiguous VLAN ranges to your network. The administrator can either update an existing VLAN range or add multiple non contiguous VLAN ranges while creating a zone. You can also use the UpdatephysicalNetwork API to extend the VLAN range. Create a network offering by specifying the following: Disabling and Enabling Zones, Pods, and Clusters Ensure that the VLAN range does not already exist. Fill in your desired over-provisioning multipliers in the fields CPU overcommit ratio and RAM overcommit ratio. The value which is intially shown in these fields is the default value inherited from the global configuration settings. First use vCenter to exit the vCenter maintenance mode. For KVM, stop the cloud-agent service. For XenServer, you can take a server offline temporarily by using the Maintenance Mode feature in XenCenter. When you place a server into Maintenance Mode, all running VMs are automatically migrated from it to another host in the same pool. If the server is the pool master, a new master will also be selected for the pool. While a server is Maintenance Mode, you cannot create or start any VMs on it. For more information, see the CloudStack Installation Guide. For vSphere the VLANs are provisioned on all hosts in the cluster even if there is no guest running on a particular Host that requires the VLAN. This allows the administrator to perform live migration and other functions in vCenter without having to create the VLAN on the destination Host. Additionally, the VLANs are not removed from the Hosts when they are no longer needed. Get the list of host IDs for the host in the cluster where you are changing the password. You will need to access the database to determine these host IDs. For each hostname "h" (or vSphere cluster) that you are changing the password for, execute: Hosts can be removed from the cloud as needed. The procedure to remove a host depends on the hypervisor type. Hypervisor capabilities Identify all hosts in the cluster. If you are disabling or enabling a pod or cluster, click the name of the zone that contains the pod or cluster. If you are disabling or enabling a zone, find the name of the zone in the list, and click the Enable/Disable button. |enable-disable.png| In XenServer, due to a constraint of this hypervisor, you can not use an over-provisioning factor greater than 4. In Zones, click View More. In any given cloud, the optimum number of VMs for each host is affected by such things as the hypervisor, storage, and hardware configuration. These may be different for each cluster in the same cloud. A single global over-provisioning setting can not provide the best utilization for all the different clusters in the cloud. It has to be set for the lowest common denominator. The per-cluster setting provides a finer granularity for better utilization of resources, no matter where the CloudStack placement algorithm decides to place a VM. In the Guest node of the diagram, click Configure. In the Pods or Clusters node of the diagram, click View All. In the Resources pane, select the server, then do one of the following: In the left navigation bar, click Infrastructure. In the left navigation, choose Infrastructure. It is safer not to deploy additional new VMs while the capacity recalculation is underway, in case the new values for available capacity are not high enough to accommodate the new VMs. Just wait for the new used/available values to become available, to be sure there is room for all the new VMs you want. KVM Limitations on Over-Provisioning in XenServer and KVM Log in as administrator to the CloudStack UI. Log in to the CloudStack UI as administrator Log in to the CloudStack UI as an administrator or end user. Maintaining Hypervisors on Hosts Management traffic. Memory ballooning is supported by default. Now use vCenter to perform whatever actions are necessary to maintain the host. During this time, the host cannot be the target of new VM allocations. On Zones, click View More, then click the zone to which you want to work with. On the Server menu, click Enter Maintenance Mode. On the Server menu, click Exit Maintenance Mode. Only VMs deployed after the change are affected by the new setting. If you want VMs deployed before the change to adopt the new over-provisioning ratio, you must stop and restart the VMs. When this is done, CloudStack recalculates or scales the used and reserved capacities based on the new over-provisioning ratios, to ensure that CloudStack is correctly tracking the amount of free capacity. Only the Root admin can assign VLANs because the regular users or domain admin are not aware of the physical network topology. They cannot even view what VLAN is assigned to a network. Over-Provisioning and Service Offering Limits Over-provisioning ratios are dynamically substituted in CloudStack's capacity calculations. For example: Place the host into CloudStack's "scheduled maintenance" mode. This does not invoke the vCenter maintenance mode, but only causes VMs to be migrated off the host Place the node in maintenance mode. Re-Installing Hosts Removing Hosts Removing XenServer and KVM Hosts Removing vSphere Hosts Requirements for Over-Provisioning Reserved for administrative purposes. CloudStack software can access this, hypervisors, system VMs. Reserved for future use Right-click, then click Enter Maintenance Mode on the shortcut menu. Right-click, then click Exit Maintenance Mode on the shortcut menu. Scheduled Maintenance and Maintenance Mode for Hosts Scope See `“Scheduled Maintenance and Maintenance Mode for Hosts” <#scheduled-maintenance-and-maintenance-mode-for-hosts>`_. Select the cluster you want to work with, and click the Edit button. Service Offering Limits and Over-Provisioning Service offering limits (e.g. 1 GHz, 1 core) are strictly enforced for core count. For example, a guest with a service offering of one core will have only one core available to it regardless of other activity on the Host. Service offering limits for gigahertz are enforced only in the presence of contention for CPU resources. For example, suppose that a guest was created with a service offering of 1 GHz on a Host that has 2 GHz cores, and that guest is the only guest running on the Host. The guest will have the full 2 GHz available to it. When multiple guests are attempting to use the CPU a weighting factor is used to schedule CPU resources. The weight is based on the clock speed in the service offering. Guests receive a CPU allocation that is proportionate to the GHz in the service offering. For example, a guest created from a 2 GHz service offering will receive twice the CPU allocation as a guest created from a 1 GHz service offering. CloudStack does not perform memory over-provisioning. Setting Over-Provisioning Ratios Several prerequisites are required in order for over-provisioning to function properly. The feature is dependent on the OS type, hypervisor capabilities, and certain scripts. It is the administrator's responsibility to ensure that these requirements are met. Specify all the VLANs you want to use, VLANs not specified will be removed if you are adding new ranges to the existing list. Specify the VLAN when you create the network. Specify the start and end of the VLAN range in comma-separated list. The DMC (Dynamic Memory Control) capability of the hypervisor should be enabled. Only XenServer Advanced and above versions have this feature. The KVM hypervisor can not manage memory allocation to VMs dynamically. CloudStack sets the minimum and maximum amount of memory that a VM can use. The hypervisor adjusts the memory within the set limits based on the memory contention. The VLAN Ranges field now is editable. The administrator can also set global default over-provisioning ratios in the cpu.overprovisioning.factor and mem.overprovisioning.factor global configuration variables. The default value of these variables is 1: over-provisioning is turned off by default. The administrator can specify a memory over-provisioning ratio, and can specify both CPU and memory over-provisioning ratios on a per-cluster basis. The balloon driver can be found as a part of the VMware tools. All the VMs that are deployed in a over-provisioned cluster should have the VMware tools installed. The balloon driver can be found as a part of xen pv or PVHVM drivers. The xen pvhvm drivers are included in upstream linux kernels 2.6.36+. The former behaviour also is supported — VLAN is randomly allocated to a network from the VNET range of the physical network when the network turns to Implemented state. The VLAN is released back to the VNET pool when the network shuts down as a part of the Network Garbage Collection. The VLAN can be re-used either by the same network when it is implemented again, or by any other network. On each subsequent implementation of a network, a new VLAN can be assigned. The hypervisor must be capable of using the memory ballooning. The lack of up-do-date hotfixes can lead to data corruption and lost VMs. The overprovisioning settings can be used along with dedicated resources (assigning a specific cluster to an account) to effectively offer different levels of service to different accounts. For example, an account paying for a more expensive level of service could be assigned to a dedicated cluster with an over-provisioning ratio of 1, and a lower-paying account to a cluster with a ratio of 2. The password for a XenServer Node, KVM Node, or vSphere Node may be changed in the database. Note that all Nodes in a Cluster must have the same password. The server's status in the Resources pane shows when all running VMs have been successfully migrated off the server. Then use CloudStack's administrator UI to cancel the CloudStack maintenance mode Then you may power down the Host, re-use its IP address, re-install it, etc There are two ways the root admin can set CPU and RAM over-provisioning ratios. First, the global configuration settings cpu.overprovisioning.factor and mem.overprovisioning.factor will be applied when a new cluster is created. Later, the ratios can be modified for an existing cluster. This makes the host ready for CloudStack to reactivate it. This should return a single ID. Record the set of such IDs for these hosts. To change a Node's password: To change the over-provisioning ratios for an existing cluster: To disable and enable a zone, pod, or cluster: To enable you to assign VLANs to Isolated networks, To enter maintenance mode on a vCenter host, both vCenter and CloudStack must be used in concert. CloudStack and vCenter have separate maintenance modes that work closely together. To remove this type of host, first place it in maintenance mode, as described in `“Scheduled Maintenance and Maintenance Mode for Hosts” <#scheduled-maintenance-and-maintenance-mode-for-hosts>`_. Then use CloudStack to remove the host. CloudStack will not direct commands to a host that has been removed using CloudStack. However, the host may still exist in the vCenter cluster. Traffic type Under Clusters, click View All. Update the passwords for the host in the database. In this example, we change the passwords for hosts with IDs 5, 10, and 12 to "password". Use the UI option to remove the node. Used = 3 GB Free = 1 GB Using this network offering, create a network. VLAN Allocation Example VLAN IDs VLAN Provisioning VLAN carrying guest traffic VLAN carrying public traffic. VLANs are required for public and guest traffic. The following is an example of a VLAN allocation scheme: VLANs carrying guest traffic. VMware VMware, KVM Wait for the "Ready for Maintenance" indicator to appear in the UI. When VLAN is specified, a CIDR and gateway are assigned to this network and the state is changed to Setup. In this state, the network will not be garbage collected. When a new host is added to a cluster, CloudStack will assume the host has the capability to perform the CPU and RAM over-provisioning which is configured for that cluster. It is up to the administrator to be sure the host is actually suitable for the level of over-provisioning which has been set. When running hypervisor software on hosts, be sure all the hotfixes provided by the hypervisor vendor are applied. Track the release of hypervisor patches through your hypervisor vendor’s support channel, and apply patches as soon as possible after they are released. CloudStack will not track or notify you of required hypervisor patches. It is essential that your hosts are completely up to date with the provided hypervisor patches. The hypervisor vendor is likely to refuse to support any system that is not up to date with patches. When the CloudStack maintenance mode is requested, the host first moves into the Prepare for Maintenance state. In this state it cannot be the target of new guest VM starts. Then all VMs will be migrated off the server. Live migration will be used to move VMs off the host. This allows the guests to be migrated to other hosts with no disruption to the guests. After this migration is completed, the host will enter the Ready for Maintenance mode. When the host comes back online, the VMs that were migrated off of it may be migrated back to it manually and new VMs can be added. When the maintenance tasks are complete, take the host out of maintenance mode as follows: With this configuration, suppose you deploy 3 VMs of 1 GB each: Working with Hosts XenServer XenServer and Maintenance Mode You can create a VPC tier or an Isolated network. You can enable or disable a zone, pod, or cluster without permanently removing it from the cloud. This is useful for maintenance or when there are problems that make a portion of the cloud infrastructure unreliable. No new allocations will be made to a disabled zone, pod, or cluster until its state is returned to Enabled. When a zone, pod, or cluster is first added to the cloud, it is Disabled by default. You can place a host into maintenance mode. When maintenance mode is activated, the host becomes unavailable to receive new guest VMs, and the guest VMs already running on the host are seamlessly migrated to another host not in maintenance mode. This migration uses live migration technology and does not interrupt the execution of the guest. You can re-install a host after placing it in maintenance mode and then removing it. If a host is down and cannot be placed in maintenance mode, it should still be removed before the re-install. You can use the same VLANs on different physical networks provided that each physical network has its own underlying layer-2 infrastructure, such as switches. For example, you can specify VLAN range 500 to 1000 while deploying physical networks A and B in an Advanced zone setup. This capability allows you to set up an additional layer-2 physical infrastructure on a different physical NIC and use the same set of VLANs if you run out of VLANs. Another advantage is that you can use the same set of IPs for different customers, each one with their own routers and the guest networks on different physical NICs. You cannot change a VLAN once it's assigned to the network. The VLAN remains with the network for its entire life cycle. greater than 1000 less than 500 vCenter and Maintenance Mode Project-Id-Version: Apache CloudStack Administration RTD
Report-Msgid-Bugs-To:
POT-Creation-Date: 2014-06-30 12:52+0200
PO-Revision-Date: 2014-06-30 12:04+0000
Last-Translator: FULL NAME <EMAIL@ADDRESS>
Language-Team: Chinese (China) (http://www.transifex.com/projects/p/apache-cloudstack-administration-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;
（支持XenServer、KVM和VMware） （XenServer）更多信息，请参考`CloudStack知识库中高度推荐的XenServer修补程序 <http://docs.cloudstack.org/Knowledge_Base/Possible_VM_corruption_if_XenServer_Hotfix_is_not_Applied/Highly_Recommended_Hotfixes_for_XenServer_5.6_SP2>`_. **来宾网络类型**：选择隔离的。 **指定VLAN**：选择一个选项。 **使一台服务器进入维护模式：** **使服务器退出维护模式：** 500-599 600-799 800-899 900-999 cluster中的主机只有进入维护模式才能被移除。这么做是为了确保其上所有的VMs被迁移至其他主机。要从云中移除一个主机： 添加主机 添加不连续的VLAN范围 添加主机能为来宾VMs提供更多的性能。更多需求与说明请参阅 `“添加主机” <http://docs.cloudstack.apache.org/projects/cloudstack-installation/en/latest/configuration.html#adding-a-host>`_。 所有VMs都需要支持virtio驱动。Linux kernel versions 2.6.25和更高版本中已经安装了这些驱动。管理员必须在virtio的配置文件中配置CONFIG\_VIRTIO\_BALLOON=y。 所有VMs中都安装了balloon驱动。Hypervisor靠balloon驱动与VM通讯以释放内存和让内存变得可用。 给隔离的网络指定VLAN。 Balloon驱动 CPU和内存（RAM）超配直接影响每个群集中主机上可以运行的VMs数量。这样可以帮助优化资源的使用。依靠增加超配比率，能使使资源更充分的被利用。如果比率设为1，那么表示没有使用超配。 容量=2GB 超配系数=2 超配后容量=4GB 更改群集中所有主机的密码。此刻主机上的密码与CloudStack已知的密码不一致。两个密码不一致的话会导致群集上的操作失败。 更改主机密码 点击应用 点击编辑|edit-icon.png|。 点击进入维护模式。 点击退出维护模式。 点击物理网络。 点击计算这个标签。 点击启用/禁用按钮。|enable-disable.png| 点击列表中的pod或者cluster名称。 CloudStack账户。 CloudStack 账户。CloudStack管理员为账户指定特定的VLAN。 CloudStack 账户。 从这个池中选择账户特定的VLAN。 CloudStack 账户。可作为项目、域或所有账户的作用域。 CloudStack能在主机上自动创建和销毁桥接至VLAN的网络接口。一般来说，管理员不需要介入此处理过程。 CloudStack根据hypervisor类型的不同，管理VLANs的方式也不同。对于XenServer或者KVM来说，只在使用VLANs的主机上创建VLANs，并且当所有使用VLANs的来宾虚机被销毁或者移动至其他主机的时候，这些VLANs就会被销毁。 CloudStack能够让你控制VLAN分配至隔离网络。作为一个Root管理员，当一个网络被创建后，你能为其分配一个VLAN ID，这个网络只能是共享网络。 CloudStack能让你灵活的给你的网络添加不连续的VLAN范围。在创建一个zone的时候，管理员要么更新一个已存在的VLAN范围，要么添加多个不连续的VLAN范围。你同样可以使用UpdatephysicalNetwork API来扩展VLAN范围。 使用下列指定的步骤创建一个网络方案： 禁用和启用Zones，Pods和Clusters 确保VLAN范围没有被使用。 在CPU overcommit ratio和RAM overcommit ratio区域里填入你希望的超配系数。这里的初始值是从全局配置设置里继承而来的。 首先通过vCenter退出vCenter维护模式。 对于KVM，停止cloud-agent服务。 对于XenServer，你能够通过使用XenCenter中的维护模式功能将一台服务器临时的离线。当你使一台服务器进入维护模式，所有运行的VMs都会自动的迁移到同一个池中的其他主机上。如果此服务器是池master主机，那么此池会选举一个新的master主机。当一台服务器在维护模式下时，你不能在上面创建或启动任何VMs。 更多信息，请参考CloudStack安装指导。 vSphere上的VLANs是在群集中的所有主机上配置的，不管主机上有没有使用VLAN的来宾虚机在运行。这样允许管理员在vCenter中不需在目标主机上创建VLAN就可以执行在线迁移和其他功能。此外，当主机不再需要的时候VLANs也不会被移除。 获取群集中你更改了密码的主机ID列表。你必须访问数据库来获取这些ID。为每个你要更改密码的主机名（或者vSphere群集） "h"，执行： 主机在需要的时候可以被移除。这个过程取决于主机所使用的hypervisor类型。 Hypervisor功能 让群集中所有的主机状态保持一致。 如果你要禁用或启用一个pod或者cluster，点击包含该pod或cluster的zone名称。 如果你要禁用或启用一个zone，请在列表里找到zone的名称，然后点击启用/禁用按钮。|enable-disable.png| 在XenServer中，由于这个hypervisor的限制，超配系数不能超过4。 点击区域中的查看更多。 在任何已有的云中，hypervisor、存储和硬件配置影响每个主机上VMs最佳数量。同一个云中的每个群集的这些配置可能都不同。单一的全局超配设置不能为云中所有的群集提供最佳效果。它只能作为一个基线。无论CloudStack使用哪种算法来放置一个VM，每个群集都提供了细颗粒度的设置以提供更好的资源效果。 在图中的来宾节点上，点击配置 在示意图中的Pods或者Clusters节点，点击查看所有。 在资源面板，选择服务器，然后按下列步骤进行操作： 在左侧导航栏中，点击基础架构 在左边的导航，选择基础架构。 如果新的可用容量不足以满足新的VMs需求，那么当重新计算容量的过程中不去部署新的VMs是比较安全的。等新的已用/可用容量完全可用时，确认这空间对于你想创建的VMs足够用。 KVM XenServer和KVM中超配的局限性 使用管理员登录到CloudStack管理界面。 使用管理员权限的账号登录到CloudStack 使用管理员或者终端用户账号登录CloudStack UI。 在主机上维护Hypervisors 管理流量。 默认支持内存ballooning。 现在使用vCenter通过必要的步骤将主机进入维护模式。在此期间，主机不会运行新的VM。 在Zones上，点击查看更多，然后点击你要进行操作的zone。 在服务器菜单，点击进入维护模式。 在服务器菜单，点击提出维护模式。 只有在变更之后部署VMs，设置才会生效。如果想让变更之前部署的VMs也能继承新的超配比率，你必须重启VMs。当此操作完成之后，CloudStack会重新计算或者调整已使用的资源，并且基于新的超配比率预留出容量，以保证CloudStack正确的掌握了剩余容量的情况。 只有Root管理员能够分配VLANs，因为常规的用户和域管理员并不清楚物理网络拓扑。他们也不能查看哪个VLAN被分配给网络。 超配和服务方案限制 超配比率是由CloudStack的容量计算器动态调整的。比如： 在CloudStack中，将主机进入"维护计划"模式。这个操作不会调用vCenter的维护模式，但是会将VMs迁离该主机。 将主机进入维护模式。 重新安装主机 移除主机 移除XenServer和KVM主机 移除vSphere主机 存储超配的要求 出于管理目的而预留的。CloudStack，hypervisors和系统虚机能访问它。 保留为将来使用 右击，然后在弹出的快捷菜单中点击进入维护模式。 右击，然后在弹出的快捷菜单中点击退出维护模式。 主机的维护计划与维护模式 范围 请参考`“主机的维护计划与维护模式” <#scheduled-maintenance-and-maintenance-mode-for-hosts>`_. 选择你要操作的群集，点击编辑按钮。 服务方案限制和超配 服务方案限制（比如1GHz，1 core）是受到core数严格限制的。比如，一个使用1 core服务方案的用户只能用 1core，无论这个主机多空闲。 GHz的服务方案限制只存在于CPU资源的争用中。比如，假设用户在一个有2GHz core的主机上创建了一个1 GHz的服务方案，并且该用户是这个主机上唯一一个用户。那么该用户有2 GHz可用性能。当多个用户尝试使用CPU，则由权重系数来调度CPU资源。这个权重基于服务方案中的时钟速度。用户分配到的CPU GHz与服务方案中一致。比如，用户从一个2GHz服务方案中创建的VM分配到的CPU是从1 GHz方案中分配到的2倍。CloudStack不能提供内存的超配。 设置存储超配系数 为了让超配能够正常工作需要几个前提条件。此特性取决于OS类型，hypervisor功能和特定的脚本。管理员负责确认这些条件都符合。 指定所有你想使用的VLANs，如果你添加新的范围到已有列表里，那么没有指定的VLANs将被移除。 当你创建网络的时候指定VLAN。 指定VLAN范围的起始和结束用逗号隔开。 Hypervisor必须启用了DMC（动态内存控制）功能。只有XenServer高级版以及更高版本拥有这个功能。 KVM hypervisor不能动态的管理分配给VMs的内存。CloudStack设置VM能够使用的内存最小和最大量。Hypervisor基于存储器争用技术在设定范围内调整内存。 现在VLAN范围区域是可编辑的了。 管理员也可以在cpu.overprovisioning.factor和mem.overprovisioning.factor这两个全局配置变量中设置全局默认超配比率。默认的值是1：默认情况下超配是关闭的。 管理员可以在每个群集中指定一个内存超配比率，也可以同时指定CPU和内存超配比率。 Balloon驱动是VMware tools的一部分。在一台超配群集中部署的所有的VMs都应该安装VMware tools。 Balloon驱动是Xen pv或者PVHVM驱动的一部分。Linux kernels 2.6.36和以上版本中包含了Xen pvhvm驱动。 同样被支持—当网络转换为运行状态是，VLAN是随机地通过物理网络的VNET范围分配给网络。当网络作为网络垃圾回收过程的一部分而关闭时，VLAN会被回收到VNET池。当网络再次启用的时候VLAN还能被其重用，或者其他网络使用。在每个新启用的网络中，都有一个新的VLAN被分配。 Hypervisor必须能够使用内存ballooning。 缺乏最新补丁更新可能会导致数据和虚拟机丢失。 超配设置和专用资源（对一个账号分配一个特定的群集）一起使用时能对不同用户有效的提供的不同服务级别。比如，一个账号购买了比较高级别的服务，那么分配给他一个超配比率为1的专用群集，购买低级别服务的账号分配一个比率为2的群集。 数据库中的XenServer主机，KVM主机或者vShpere主机密码可能会被变更。注意群集中的所有节点密码必须一致。 当所有运行当中的VMs成功的迁离该主机后，在资源面板中会显示服务器的状态。 然后通过CloudStack的管理员UI来取消CloudStack维护模式 然后你可以关掉主机，重用它的IP地址，重新安装系统，等等。 管理员有两种方法来设置CPU和RAM超配系数。第一，当新的群集被创建完成的时候全局配置中的cpu.overprovisioning.factor和mem.overprovisioning.factor将生效。第二，对于已存在的群集可以直接修改系数。 这么做是为了主机能够准备好以便CloudStack恢复它。 这条命令将会返回一个ID。记录这些主机的ID。 用户名和密码要更改一台主机的密码： 在已存在的群集中更改超配系数： 要禁用和启用一个zone，pod或者cluster： 要把VLANs分配给隔离的网络， 要使vCenter主机进入维护模式，vCenter和CloudStack上都必须进行此操作。CloudStack和vCenter有各自的维护模式，他们需要紧密合作。 要移除此类型的主机，首先按照 `“主机的维护计划与维护模式” <#scheduled-maintenance-and-maintenance-mode-for-hosts>`_中的描述将其进入维护模式。然后使用CloudStack来移除主机。使用CloudStack移除主机时，CloudStack不会直接操作主机。但是，主机可能仍然存留在vCenter群集中。 流量类型 在群集页面，点击查看所有。 在数据库中为这些主机更新密码。在这个例子中，我们将主机ID为5,10和12的密码更改为"password"。 使用UI选项来移除主机。 已使用=3GB 空闲=1GB 使用这个网络方案，创建一个网络。 VLAN分配示例 VLAN IDs VLAN供应 承载来宾流量 承载公共流量。 公共和来宾流量要求使用VLAN，下面是一个VLAN分配的示例： 承载来宾流量 VMware VMware、KVM 等"准备好维护"指示灯出现在UI中。 当VLAN被指定后，CIDR和网关就被分配给这个网络了，并且它的状态也变成Setup了。在这个状态下，网络不会被回收。 当一个新主机被添加到群集中，CloudStack假设配置了超配的群集中的主机能够提供CPU和RAM的超配能力。这个要靠管理员来决定主机是否真的能够提供设置的超配级别。 当主机上运行了hypervisor软件，请确保安装了供应商提供的所有修补程序。请通过供应商跟踪虚拟化平台的补丁发布情况，一旦发布，请尽快打上补丁。CloudStack不会跟踪或通知您所需要的虚拟化平台补丁。您的主机及时打上最新虚拟化平台补丁是非常重要的。虚拟化平台厂商很可能会拒绝支持未打最新补丁的系统。 当CloudStack维护模式启用后，主机首先会进入准备维护状态。在这个阶段它不能运行新的来宾VMs。然后所有的VMs将会被迁离该主机。主机使用在线迁移来迁移VMs。这种方式能够使来宾VMs在迁移到其他主机的过程中不会中断用户的操作。 当主机恢复正常，被迁移走的VMs可能需要手工迁移回来并且也能在主机上添加新的VMs了。 当维护任务完成之后，按以下操作将主机退出维护模式： 按照这个配置，假设你部署了3个VMs，每个VM 1GB： 使用主机 XenServer XenServer和维护模式 你可以创建一个VPC层或者一个隔离网络。 你可以启用或禁用一个zone，pod或者cluster而不用永久的从云中移除他们。这对于维护或者当云中一部分架构的可靠性有问题的时候很有用。禁用状态下的zone，pod或cluster不会接受新的分配，除非其状态变为启用。当一个zone，pod或cluster是初次添加到云中的，默认的情况下它是禁用的。 你可以使一台主机进入维护模式。当激活维护模式时，这台主机将不会接纳新的来宾VMs，同时上面的VMs会无缝地迁移到其他非维护模式的主机上。这个迁移使用在线迁移技术并且不会中断用户的操作。 你可以在将主机进入维护模式并移除它之后重新安装系统。如果主机是宕机状态而不能进入维护模式，在重装它之前仍然能被移除。 你能够使用由不同的拥有二层网络结构的物理网络提供同样的VLANs，比如交换机。比如，在对高级zone中部署物理网络A和B的时候，你可以指定VLAN范围为500-1000。如果你的VLANs用尽了，这个功能允许你在不同的物理网卡上设置追加一个二层物理网络并且使用同样的VLANs设置。另一个优点是你可以在不同的物理网卡上为不同的客户使用同样的IPs设置，每个都有自己的路由器和来宾网络。 一旦VLAN被分配给一个网络的话，你就不能更改它。VLAN将伴随着网络的整个生命周期。 大于1000 小于500 vCenter与维护模式