apache/cloudstack
1
0
Fork 0
mirror of https://github.com/apache/cloudstack.git synced 2025-11-02 11:52:28 +01:00
Code Issues Packages Projects Releases Wiki Activity

CLOUDSTACK-816. DOC. Fix position of health check configuration step in adding a load balancer rule. Fix to document for health checks for load balanced instances.

Browse Source
This commit is contained in:
Jessica 2013-08-08 21:52:34 -07:00
parent 84d3be21ea
commit 30a08e5f96
1 changed files with 16 additions and 16 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

32
docs/en-US/add-load-balancer-rule.xml
View File

@ -74,24 +74,24 @@
<para><emphasis role="bold">AutoScale</emphasis>: Click Configure and complete the
AutoScale configuration as explained in <xref linkend="autoscale"/>.</para>
</listitem>
<listitem><para><emphasis role="bold">Health Check</emphasis>: (Optional; NetScaler load balancers only) Click
Configure and fill in the characteristics of the health check policy. See <xref
linkend="health-checks-for-lb-rules"/>.</para>
<itemizedlist>
<listitem><para><emphasis role="bold">Ping path (Optional)</emphasis>: Sequence of destinations to which to send health check queries.
Default: / (all).</para></listitem>
<listitem><para><emphasis role="bold">Response time (Optional)</emphasis>: How long to wait for a response from the health check (2 - 60 seconds).
Default: 5 seconds.</para></listitem>
<listitem><para><emphasis role="bold">Interval time (Optional)</emphasis>: Amount of time between health checks (1 second - 5 minutes).
Default value is set in the global configuration parameter lbrule_health check_time_interval.</para></listitem>
<listitem><para><emphasis role="bold">Healthy threshold (Optional)</emphasis>: Number of consecutive health check successes
that are required before declaring an instance healthy.
Default: 2.</para></listitem>
<listitem><para><emphasis role="bold">Unhealthy threshold (Optional)</emphasis>: Number of consecutive health check failures that are required before declaring an instance unhealthy.
Default: 10.</para></listitem>
</itemizedlist></listitem>
</itemizedlist>
</listitem>
<listitem><para><emphasis role="bold">Health Check</emphasis>: (Optional; NetScaler load balancers only) Click
Configure and fill in the characteristics of the health check policy. See <xref
linkend="health-checks-for-lb-rules"/>.</para>
<itemizedlist>
<listitem><para><emphasis role="bold">Ping path (Optional)</emphasis>: Sequence of destinations to which to send health check queries.
Default: / (all).</para></listitem>
<listitem><para><emphasis role="bold">Response time (Optional)</emphasis>: How long to wait for a response from the health check (2 - 60 seconds).
Default: 5 seconds.</para></listitem>
<listitem><para><emphasis role="bold">Interval time (Optional)</emphasis>: Amount of time between health checks (1 second - 5 minutes).
Default value is set in the global configuration parameter lbrule_health check_time_interval.</para></listitem>
<listitem><para><emphasis role="bold">Healthy threshold (Optional)</emphasis>: Number of consecutive health check successes
that are required before declaring an instance healthy.
Default: 2.</para></listitem>
<listitem><para><emphasis role="bold">Unhealthy threshold (Optional)</emphasis>: Number of consecutive health check failures that are required before declaring an instance unhealthy.
Default: 10.</para></listitem>
</itemizedlist></listitem>
<listitem>
<para>Click Add VMs, then select two or more VMs that will divide the load of incoming
traffic, and click Apply.</para>