cloudstack/docs/zh-TW/autoscale.po

458 lines
19 KiB
Plaintext
Raw Blame History

This file contains ambiguous Unicode characters

This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.

#Licensed to the Apache Software Foundation (ASF) under one
#or more contributor license agreements. See the NOTICE file
#distributed with this work for additional information
#regarding copyright ownership. The ASF licenses this file
#to you under the Apache License, Version 2.0 (the
#"License"); you may not use this file except in compliance
#with the License. You may obtain a copy of the License at
#http://www.apache.org/licenses/LICENSE-2.0
#Unless required by applicable law or agreed to in writing,
#software distributed under the License is distributed on an
#"AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
#KIND, either express or implied. See the License for the
#specific language governing permissions and limitations
#under the License.
#
# Translators:
# Isaac Chiang <isaacchiang@gmail.com>, 2013.
msgid ""
msgstr ""
"Project-Id-Version: Apache CloudStack Docs\n"
"POT-Creation-Date: 2013-04-12T11:19:38\n"
"PO-Revision-Date: 2013-04-08 15:40+0000\n"
"Last-Translator: isaac.chiang <isaacchiang@gmail.com>\n"
"Language-Team: None\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Language: zh_TW\n"
"Plural-Forms: nplurals=1; plural=0;\n"
#. Tag: title
#, no-c-format
msgid "Configuring AutoScale"
msgstr "設定 AutoScale "
#. Tag: para
#, no-c-format
msgid ""
"AutoScaling allows you to scale your back-end services or application VMs up"
" or down seamlessly and automatically according to the conditions you "
"define. With AutoScaling enabled, you can ensure that the number of VMs you "
"are using seamlessly scale up when demand increases, and automatically "
"decreases when demand subsides. Thus it helps you save compute costs by "
"terminating underused VMs automatically and launching new VMs when you need "
"them, without the need for manual intervention."
msgstr "AutoScaling允許您擴充終端服務或無縫及自動地增加或減少VM根據您的設定。啟用AutoScaling您可以確定當需求增加時VM數量會跟著增加反之則自動減少。這能幫您減少運算成本不用手動介入"
#. Tag: para
#, no-c-format
msgid ""
"NetScaler AutoScaling is designed to seamlessly launch or terminate VMs "
"based on user-defined conditions. Conditions for triggering a scaleup or "
"scaledown action can vary from a simple use case like monitoring the CPU "
"usage of a server to a complex use case of monitoring a combination of "
"server's responsiveness and its CPU usage. For example, you can configure "
"AutoScaling to launch an additional VM whenever CPU usage exceeds 80 percent"
" for 15 minutes, or to remove a VM whenever CPU usage is less than 20 "
"percent for 30 minutes."
msgstr "NetScaler AutoScaling設計為無縫執行或根據使用者定義情況終止VM觸發變動的情況會依據像監控CPU使用率等簡單的規則或是監控伺服器的反應及CPU使用率等複雜的規則而有所不同例如您想要想要在CPU使用率在15分鐘超過80%就增加VM或是CPU使用率在30分鐘低於20%就移除VM"
#. Tag: para
#, no-c-format
msgid ""
"&PRODUCT; uses the NetScaler load balancer to monitor all aspects of a "
"system's health and work in unison with &PRODUCT; to initiate scale-up or "
"scale-down actions."
msgstr ""
#. Tag: para
#, no-c-format
msgid "AutoScale is supported on NetScaler Release 10 Build 73.e and beyond."
msgstr ""
#. Tag: title
#, no-c-format
msgid "Prerequisites"
msgstr "事前準備"
#. Tag: para
#, no-c-format
msgid "Before you configure an AutoScale rule, consider the following:"
msgstr "在您設定 AutoScale 規則之前,請先考慮:"
#. Tag: para
#, no-c-format
msgid ""
"Ensure that the necessary template is prepared before configuring AutoScale."
" When a VM is deployed by using a template and when it comes up, the "
"application should be up and running."
msgstr "確保必要的模組已經準備好當VM使用模組部署時應用程式需要出現並執行"
#. Tag: para
#, no-c-format
msgid ""
"If the application is not running, the NetScaler device considers the VM as "
"ineffective and continues provisioning the VMs unconditionally until the "
"resource limit is exhausted."
msgstr "如果應用程式並未執行NetScaler裝置會認為VM是無效的並繼續無條件的配置VM直到資源耗盡"
#. Tag: para
#, no-c-format
msgid ""
"Deploy the templates you prepared. Ensure that the applications come up on "
"the first boot and is ready to take the traffic. Observe the time requires "
"to deploy the template. Consider this time when you specify the quiet time "
"while configuring AutoScale."
msgstr "部署您準備的模組確定應用程式在開機時有出現並可以處理流量。觀察部署模組需要的時間用來考慮設定AutoScale時是否正常"
#. Tag: para
#, no-c-format
msgid ""
"The AutoScale feature supports the SNMP counters that can be used to define "
"conditions for taking scale up or scale down actions. To monitor the SNMP-"
"based counter, ensure that the SNMP agent is installed in the template used "
"for creating the AutoScale VMs, and the SNMP operations work with the "
"configured SNMP community and port by using standard SNMP managers. For "
"example, see <xref linkend=\"configure-snmp-rhel\" /> to configure SNMP on a"
" RHEL machine."
msgstr "AutoScale功能支援SNMP計數器可使用為定義狀況想要監視 SNMP-based 計數器請確保SNMP agent已安裝在模組中及 使用標準SNMP管理器使 SNMP運作單元可以在設定後的SNMP 群組及通訊埠正常運作,例如,詳見<xref linkend=\"configure-snmp-rhel\" />來設定RHEL機器上的SNMP "
#. Tag: para
#, no-c-format
msgid ""
"Ensure that the endpointe.url parameter present in the Global Settings is "
"set to the Management Server API URL. For example, "
"http://10.102.102.22:8080/client/api. In a multi-node Management Server "
"deployment, use the virtual IP address configured in the load balancer for "
"the management servers cluster. Additionally, ensure that the NetScaler "
"device has access to this IP address to provide AutoScale support."
msgstr "確定endpointe.url 欄位有出現在Global Setting並設定為Management Server API URL。例如http://10.102.102.22:8080/client/api。對於多節點管理伺服器使用虛擬IP在管理伺服器叢集的負載平衡器中設定。另外確定NetScaler 裝置可以存取此IP藉此提供AutoScale支援"
#. Tag: para
#, no-c-format
msgid ""
"If you update the endpointe.url, disable the AutoScale functionality of the "
"load balancer rules in the system, then enable them back to reflect the "
"changes. For more information see <xref linkend=\"update-autoscale\" />"
msgstr "如果您更新endpointe.url請停用系統的負載平衡規則的AutoScale功能然後再啟用使變更生效更多資訊詳見<xref linkend=\"update-autoscale\" /> "
#. Tag: para
#, no-c-format
msgid ""
"If the API Key and Secret Key are regenerated for an AutoScale user, ensure "
"that the AutoScale functionality of the load balancers that the user "
"participates in are disabled and then enabled to reflect the configuration "
"changes in the NetScaler."
msgstr "如果API Key 及 Secret Key為AutoScale 使用者重新產生請確定使用者參與的負載平衡器的AutoScale功能有先停用後再啟用以使變更生效"
#. Tag: para
#, no-c-format
msgid ""
"In an advanced Zone, ensure that at least one VM should be present before "
"configuring a load balancer rule with AutoScale. Having one VM in the "
"network ensures that the network is in implemented state for configuring "
"AutoScale."
msgstr "在進階區域中確定在設定AutoScale的負載平衡規則前至少有一個VM顯示此確定網路是在執行狀態"
#. Tag: title
#, no-c-format
msgid "Configuration"
msgstr "系統設定"
#. Tag: para
#, no-c-format
msgid "Specify the following:"
msgstr "具體說明以下:"
#. Tag: para
#, no-c-format
msgid ""
"<emphasis role=\"bold\">Template</emphasis>: A template consists of a base "
"OS image and application. A template is used to provision the new instance "
"of an application on a scaleup action. When a VM is deployed from a "
"template, the VM can start taking the traffic from the load balancer without"
" any admin intervention. For example, if the VM is deployed for a Web "
"service, it should have the Web server running, the database connected, and "
"so on."
msgstr "<emphasis role=\"bold\">Template</emphasis>:模組包含作業系統映像及應用程式。用來提供新 instance 擴增動作當VM部署後VM可以開始由負載平衡器接收流量例如如果VM部署為網頁服務網頁伺服器應會開始執行資料庫開始連結然後繼續下去"
#. Tag: para
#, no-c-format
msgid ""
"<emphasis role=\"bold\">Compute offering</emphasis>: A predefined set of "
"virtual hardware attributes, including CPU speed, number of CPUs, and RAM "
"size, that the user can select when creating a new virtual machine instance."
" Choose one of the compute offerings to be used while provisioning a VM "
"instance as part of scaleup action."
msgstr "<emphasis role=\"bold\">Compute offering</emphasis>一組先定義的虛擬硬體包含CPU速度、CPU數量及記憶體大小讓使用者可以在建立新的虛擬機器時選擇配置VM instance為擴增動作的一部份時選擇一個計算服務"
#. Tag: para
#, no-c-format
msgid ""
"<emphasis role=\"bold\">Min Instance</emphasis>: The minimum number of "
"active VM instances that is assigned to a load balancing rule. The active VM"
" instances are the application instances that are up and serving the "
"traffic, and are being load balanced. This parameter ensures that a load "
"balancing rule has at least the configured number of active VM instances are"
" available to serve the traffic."
msgstr ""
#. Tag: para
#, no-c-format
msgid ""
"If an application, such as SAP, running on a VM instance is down for some "
"reason, the VM is then not counted as part of Min Instance parameter, and "
"the AutoScale feature initiates a scaleup action if the number of active VM "
"instances is below the configured value. Similarly, when an application "
"instance comes up from its earlier down state, this application instance is "
"counted as part of the active instance count and the AutoScale process "
"initiates a scaledown action when the active instance count breaches the Max"
" instance value."
msgstr ""
#. Tag: para
#, no-c-format
msgid ""
"<emphasis role=\"bold\">Max Instance</emphasis>: Maximum number of active VM"
" instances that <emphasis role=\"bold\">should be assigned to </emphasis>a "
"load balancing rule. This parameter defines the upper limit of active VM "
"instances that can be assigned to a load balancing rule."
msgstr ""
#. Tag: para
#, no-c-format
msgid ""
"Specifying a large value for the maximum instance parameter might result in "
"provisioning large number of VM instances, which in turn leads to a single "
"load balancing rule exhausting the VM instances limit specified at the "
"account or domain level."
msgstr ""
#. Tag: para
#, no-c-format
msgid ""
"If an application, such as SAP, running on a VM instance is down for some "
"reason, the VM is not counted as part of Max Instance parameter. So there "
"may be scenarios where the number of VMs provisioned for a scaleup action "
"might be more than the configured Max Instance value. Once the application "
"instances in the VMs are up from an earlier down state, the AutoScale "
"feature starts aligning to the configured Max Instance value."
msgstr ""
#. Tag: para
#, no-c-format
msgid "Specify the following scale-up and scale-down policies:"
msgstr ""
#. Tag: para
#, no-c-format
msgid ""
"<emphasis role=\"bold\">Duration</emphasis>: The duration, in seconds, for "
"which the conditions you specify must be true to trigger a scaleup action. "
"The conditions defined should hold true for the entire duration you specify "
"for an AutoScale action to be invoked."
msgstr ""
#. Tag: para
#, no-c-format
msgid ""
"<emphasis role=\"bold\">Counter</emphasis>: The performance counters expose "
"the state of the monitored instances. By default, &PRODUCT; offers four "
"performance counters: Three SNMP counters and one NetScaler counter. The "
"SNMP counters are Linux User CPU, Linux System CPU, and Linux CPU Idle. The "
"NetScaler counter is ResponseTime. The root administrator can add additional"
" counters into &PRODUCT; by using the &PRODUCT; API."
msgstr ""
#. Tag: para
#, no-c-format
msgid ""
"<emphasis role=\"bold\">Operator</emphasis>: The following five relational "
"operators are supported in AutoScale feature: Greater than, Less than, Less "
"than or equal to, Greater than or equal to, and Equal to."
msgstr ""
#. Tag: para
#, no-c-format
msgid ""
"<emphasis role=\"bold\">Threshold</emphasis>: Threshold value to be used for"
" the counter. Once the counter defined above breaches the threshold value, "
"the AutoScale feature initiates a scaleup or scaledown action."
msgstr ""
#. Tag: para
#, no-c-format
msgid "<emphasis role=\"bold\">Add</emphasis>: Click Add to add the condition."
msgstr ""
#. Tag: para
#, no-c-format
msgid ""
"Additionally, if you want to configure the advanced settings, click Show "
"advanced settings, and specify the following:"
msgstr ""
#. Tag: para
#, no-c-format
msgid ""
"<emphasis role=\"bold\">Polling interval</emphasis>: Frequency in which the "
"conditions, combination of counter, operator and threshold, are to be "
"evaluated before taking a scale up or down action. The default polling "
"interval is 30 seconds."
msgstr ""
#. Tag: para
#, no-c-format
msgid ""
"<emphasis role=\"bold\">Quiet Time</emphasis>: This is the cool down period "
"after an AutoScale action is initiated. The time includes the time taken to "
"complete provisioning a VM instance from its template and the time taken by "
"an application to be ready to serve traffic. This quiet time allows the "
"fleet to come up to a stable state before any action can take place. The "
"default is 300 seconds."
msgstr ""
#. Tag: para
#, no-c-format
msgid ""
"<emphasis role=\"bold\">Destroy VM Grace Period</emphasis>: The duration in "
"seconds, after a scaledown action is initiated, to wait before the VM is "
"destroyed as part of scaledown action. This is to ensure graceful close of "
"any pending sessions or transactions being served by the VM marked for "
"destroy. The default is 120 seconds."
msgstr ""
#. Tag: para
#, no-c-format
msgid ""
"<emphasis role=\"bold\">Security Groups</emphasis>: Security groups provide "
"a way to isolate traffic to the VM instances. A security group is a group of"
" VMs that filter their incoming and outgoing traffic according to a set of "
"rules, called ingress and egress rules. These rules filter network traffic "
"according to the IP address that is attempting to communicate with the VM."
msgstr ""
#. Tag: para
#, no-c-format
msgid ""
"<emphasis role=\"bold\">Disk Offerings</emphasis>: A predefined set of disk "
"size for primary data storage."
msgstr ""
#. Tag: para
#, no-c-format
msgid ""
"<emphasis role=\"bold\">SNMP Community</emphasis>: The SNMP community string"
" to be used by the NetScaler device to query the configured counter value "
"from the provisioned VM instances. Default is public."
msgstr ""
#. Tag: para
#, no-c-format
msgid ""
"<emphasis role=\"bold\">SNMP Port</emphasis>: The port number on which the "
"SNMP agent that run on the provisioned VMs is listening. Default port is "
"161."
msgstr ""
#. Tag: para
#, no-c-format
msgid ""
"<emphasis role=\"bold\">User</emphasis>: This is the user that the NetScaler"
" device use to invoke scaleup and scaledown API calls to the cloud. If no "
"option is specified, the user who configures AutoScaling is applied. Specify"
" another user name to override."
msgstr ""
#. Tag: para
#, no-c-format
msgid ""
"<emphasis role=\"bold\">Apply</emphasis>: Click Apply to create the "
"AutoScale configuration."
msgstr ""
#. Tag: title
#, no-c-format
msgid "Disabling and Enabling an AutoScale Configuration"
msgstr ""
#. Tag: para
#, no-c-format
msgid ""
"If you want to perform any maintenance operation on the AutoScale VM "
"instances, disable the AutoScale configuration. When the AutoScale "
"configuration is disabled, no scaleup or scaledown action is performed. You "
"can use this downtime for the maintenance activities. To disable the "
"AutoScale configuration, click the Disable AutoScale<inlinemediaobject> "
"<imageobject> <imagedata fileref=\"./images/enable-disable-autoscale.png\" "
"/> </imageobject> <textobject> <phrase>EnableDisable.png: button to enable "
"or disable AutoScale.</phrase> </textobject> </inlinemediaobject>button."
msgstr ""
#. Tag: para
#, no-c-format
msgid ""
"The button toggles between enable and disable, depending on whether "
"AutoScale is currently enabled or not. After the maintenance operations are "
"done, you can enable the AutoScale configuration back. To enable, open the "
"AutoScale configuration page again, then click the Enable "
"AutoScale<inlinemediaobject> <imageobject> <imagedata fileref=\"./images"
"/enable-disable-autoscale.png\" /> </imageobject> <textobject> "
"<phrase>EnableDisable.png: button to enable or disable AutoScale.</phrase> "
"</textobject> </inlinemediaobject>button."
msgstr ""
#. Tag: title
#, no-c-format
msgid "Updating an AutoScale Configuration"
msgstr ""
#. Tag: para
#, no-c-format
msgid ""
"You can update the various parameters and add or delete the conditions in a "
"scaleup or scaledown rule. Before you update an AutoScale configuration, "
"ensure that you disable the AutoScale load balancer rule by clicking the "
"Disable AutoScale button."
msgstr ""
#. Tag: para
#, no-c-format
msgid ""
"After you modify the required AutoScale parameters, click Apply. To apply "
"the new AutoScale policies, open the AutoScale configuration page again, "
"then click the Enable AutoScale button."
msgstr ""
#. Tag: title
#, no-c-format
msgid "Runtime Considerations"
msgstr ""
#. Tag: para
#, no-c-format
msgid ""
"An administrator should not assign a VM to a load balancing rule which is "
"configured for AutoScale."
msgstr ""
#. Tag: para
#, no-c-format
msgid ""
"Before a VM provisioning is completed if NetScaler is shutdown or restarted,"
" the provisioned VM cannot be a part of the load balancing rule though the "
"intent was to assign it to a load balancing rule. To workaround, rename the "
"AutoScale provisioned VMs based on the rule name or ID so at any point of "
"time the VMs can be reconciled to its load balancing rule."
msgstr ""
#. Tag: para
#, no-c-format
msgid ""
"Making API calls outside the context of AutoScale, such as destroyVM, on an "
"autoscaled VM leaves the load balancing configuration in an inconsistent "
"state. Though VM is destroyed from the load balancer rule, NetScaler "
"continues to show the VM as a service assigned to a rule."
msgstr ""