blob: c6128904ad078e1510824d402b6f9c6a2495469a [file] [log] [blame]
# 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:
msgid ""
msgstr ""
"Project-Id-Version: Apache CloudStack Administration RTD\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2014-06-30 12:52+0200\n"
"PO-Revision-Date: 2016-12-18 23:36+0100\n"
"Language-Team: French (http://www.transifex.com/ke4qqq/apache-cloudstack-"
"administration-rtd/language/fr/)\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Language: fr\n"
"Plural-Forms: nplurals=2; plural=(n > 1);\n"
"Last-Translator: \n"
"X-Generator: Poedit 1.8.11\n"
# 9b2c57c96864404ab39ea18532184a3c
#: ../../networking/external_firewalls_and_load_balancers.rst:18
msgid "External Firewalls and Load Balancers"
msgstr ""
# 406fa3a599d74b6fb0f6a893d839784a
#: ../../networking/external_firewalls_and_load_balancers.rst:20
msgid ""
"CloudStack is capable of replacing its Virtual Router with an external "
"Juniper SRX device and an optional external NetScaler or F5 load balancer "
"for gateway and load balancing services. In this case, the VMs use the SRX "
"as their gateway."
msgstr ""
# e50bcd9fe60e430d85efc883354624a5
#: ../../networking/external_firewalls_and_load_balancers.rst:27
msgid "About Using a NetScaler Load Balancer"
msgstr ""
# 1cf32061da5449a2a6dc5887c27b0d72
#: ../../networking/external_firewalls_and_load_balancers.rst:29
msgid ""
"Citrix NetScaler is supported as an external network element for load "
"balancing in zones that use isolated networking in advanced zones. Set up "
"an external load balancer when you want to provide load balancing through "
"means other than CloudStack's provided virtual router."
msgstr ""
# 188f8456b75c41ffadbc92d637327f54
#: ../../networking/external_firewalls_and_load_balancers.rst:35
msgid ""
"In a Basic zone, load balancing service is supported only if Elastic IP or "
"Elastic LB services are enabled."
msgstr ""
# 7189603a0b934b4b8f4de77ccc774586
#: ../../networking/external_firewalls_and_load_balancers.rst:38
msgid ""
"When NetScaler load balancer is used to provide EIP or ELB services in a "
"Basic zone, ensure that all guest VM traffic must enter and exit through "
"the NetScaler device. When inbound traffic goes through the NetScaler "
"device, traffic is routed by using the NAT protocol depending on the EIP/"
"ELB configured on the public IP to the private IP. The traffic that is "
"originated from the guest VMs usually goes through the layer 3 router. To "
"ensure that outbound traffic goes through NetScaler device providing EIP/"
"ELB, layer 3 router must have a policy-based routing. A policy-based route "
"must be set up so that all traffic originated from the guest VM's are "
"directed to NetScaler device. This is required to ensure that the outbound "
"traffic from the guest VM's is routed to a public IP by using NAT.For more "
"information on Elastic IP, see `\"About Elastic IP\" <#about-elastic-ip>`_."
msgstr ""
# baddaa181f054bb5b0b41e5dcce1387e
#: ../../networking/external_firewalls_and_load_balancers.rst:52
msgid ""
"The NetScaler can be set up in direct (outside the firewall) mode. It must "
"be added before any load balancing rules are deployed on guest VMs in the "
"zone."
msgstr ""
# 263c8a9eb9d147ad91ae71970d65bd41
#: ../../networking/external_firewalls_and_load_balancers.rst:56
msgid ""
"The functional behavior of the NetScaler with CloudStack is the same as "
"described in the CloudStack documentation for using an F5 external load "
"balancer. The only exception is that the F5 supports routing domains, and "
"NetScaler does not. NetScaler can not yet be used as a firewall."
msgstr ""
# 79187d2fbfa743c39e8c524304235dc2
#: ../../networking/external_firewalls_and_load_balancers.rst:61
msgid ""
"To install and enable an external load balancer for CloudStack management, "
"see External Guest Load Balancer Integration in the Installation Guide."
msgstr ""
# d3c851ee525b49599c01646d4d1e2dd5
#: ../../networking/external_firewalls_and_load_balancers.rst:65
msgid ""
"The Citrix NetScaler comes in three varieties. The following summarizes how "
"these variants are treated in CloudStack."
msgstr ""
# 64aec7c1c44049498dcf6c10b4fa5605
#: ../../networking/external_firewalls_and_load_balancers.rst:68
msgid "**MPX**"
msgstr "**MPX**"
# b8df1ce8dfa14d8c8ecc441c6f71748f
#: ../../networking/external_firewalls_and_load_balancers.rst:70
msgid ""
"Physical appliance. Capable of deep packet inspection. Can act as "
"application firewall and load balancer"
msgstr ""
# 3a1ec0e897e34118a0fbeb78f64a544a
#: ../../networking/external_firewalls_and_load_balancers.rst:73
msgid ""
"In advanced zones, load balancer functionality fully supported without "
"limitation. In basic zones, static NAT, elastic IP (EIP), and elastic load "
"balancing (ELB) are also provided."
msgstr ""
# 68d5e27c550d40cd921b14324d33692a
#: ../../networking/external_firewalls_and_load_balancers.rst:77
msgid "**VPX**"
msgstr "**VPX**"
# 886b66d79fd049739f35d53684946f35
#: ../../networking/external_firewalls_and_load_balancers.rst:79
msgid ""
"Virtual appliance. Can run as VM on XenServer, ESXi, and Hyper-V "
"hypervisors. Same functionality as MPX"
msgstr ""
# acdf8d15b2b740579349caa99d8ff14f
#: ../../networking/external_firewalls_and_load_balancers.rst:82
msgid ""
"Supported on ESXi and XenServer. Same functional support as for MPX. "
"CloudStack will treat VPX and MPX as the same device type."
msgstr ""
# 632775a416fd40bfb11895ae39b883e9
#: ../../networking/external_firewalls_and_load_balancers.rst:85
msgid "**SDX**"
msgstr "**SDX**"
# 94896445c73d42c7a8a8b30da3d762a9
#: ../../networking/external_firewalls_and_load_balancers.rst:87
msgid ""
"Physical appliance. Can create multiple fully isolated VPX instances on a "
"single appliance to support multi-tenant usage"
msgstr ""
# 7272ab89523e416fba357a4ceb24b459
#: ../../networking/external_firewalls_and_load_balancers.rst:90
msgid ""
"CloudStack will dynamically provision, configure, and manage the life cycle "
"of VPX instances on the SDX. Provisioned instances are added into "
"CloudStack automatically - no manual configuration by the administrator is "
"required. Once a VPX instance is added into CloudStack, it is treated the "
"same as a VPX on an ESXi host."
msgstr ""
# e712ff0906b7463083ac7a8f9b19847c
#: ../../networking/external_firewalls_and_load_balancers.rst:98
msgid "Configuring SNMP Community String on a RHEL Server"
msgstr ""
# a0e11ba7efae4e63a0cd9eb015162722
#: ../../networking/external_firewalls_and_load_balancers.rst:100
msgid ""
"The SNMP Community string is similar to a user id or password that provides "
"access to a network device, such as router. This string is sent along with "
"all SNMP requests. If the community string is correct, the device responds "
"with the requested information. If the community string is incorrect, the "
"device discards the request and does not respond."
msgstr ""
# d9a8fc53fc4949bda74cb44fbcb04146
#: ../../networking/external_firewalls_and_load_balancers.rst:106
msgid ""
"The NetScaler device uses SNMP to communicate with the VMs. You must "
"install SNMP and configure SNMP Community string for a secure communication "
"between the NetScaler device and the RHEL machine."
msgstr ""
# 9f7d96642a9b435ab7687ecf88e6f6de
#: ../../networking/external_firewalls_and_load_balancers.rst:110
msgid ""
"Ensure that you installed SNMP on RedHat. If not, run the following command:"
msgstr ""
# 657a8fba85b14585be4a9165ba95128b
#: ../../networking/external_firewalls_and_load_balancers.rst:117
msgid ""
"Edit the /etc/snmp/snmpd.conf file to allow the SNMP polling from the "
"NetScaler device."
msgstr ""
# 752d34a607b64dbea0348f5551d5cebc
#: ../../networking/external_firewalls_and_load_balancers.rst:120
msgid ""
"Map the community name into a security name (local and mynetwork, depending "
"on where the request is coming from):"
msgstr ""
# 07b1fa6ac91c4aa186c434d633b0384e
#: ../../networking/external_firewalls_and_load_balancers.rst:124
msgid ""
"Use a strong password instead of public when you edit the following table."
msgstr ""
# f8acb0abc31c4fd0ab9300c705ba1f72
#: ../../networking/external_firewalls_and_load_balancers.rst:133
msgid "Setting to 0.0.0.0 allows all IPs to poll the NetScaler server."
msgstr ""
# 327a4b1c1e4d429c83dc1e1628f8376a
#: ../../networking/external_firewalls_and_load_balancers.rst:135
msgid "Map the security names into group names:"
msgstr ""
# 193cbe00950147958924521840ba4405
#: ../../networking/external_firewalls_and_load_balancers.rst:145
msgid "Create a view to allow the groups to have the permission to:"
msgstr ""
# 39191ba80aa24e32898e8a79892fb7cf
#: ../../networking/external_firewalls_and_load_balancers.rst:151
msgid ""
"Grant access with different write permissions to the two groups to the view "
"you created."
msgstr ""
# ca08ac1ab89442c9a42c7d59efa70e6b
#: ../../networking/external_firewalls_and_load_balancers.rst:160
msgid "Unblock SNMP in iptables."
msgstr "Débloquer SNMP dans iptables."
# f161affb624f4139be0750f3dc19f505
#: ../../networking/external_firewalls_and_load_balancers.rst:166
msgid "Start the SNMP service:"
msgstr "Démarrer le service SNMP :"
# 60eb8801ebf44b97b3b4cc63348013b6
#: ../../networking/external_firewalls_and_load_balancers.rst:172
msgid ""
"Ensure that the SNMP service is started automatically during the system "
"startup:"
msgstr ""
# 8893688efc574dbfba90b00df9f467bd
#: ../../networking/external_firewalls_and_load_balancers.rst:181
msgid "Initial Setup of External Firewalls and Load Balancers"
msgstr ""
# 2149019287d549649f77e49102f3a8e2
#: ../../networking/external_firewalls_and_load_balancers.rst:183
msgid ""
"When the first VM is created for a new account, CloudStack programs the "
"external firewall and load balancer to work with the VM. The following "
"objects are created on the firewall:"
msgstr ""
# 7bec0089c55040c9bcc3b75a4ce9ae0b
#: ../../networking/external_firewalls_and_load_balancers.rst:187
msgid ""
"A new logical interface to connect to the account's private VLAN. The "
"interface IP is always the first IP of the account's private subnet (e.g. "
"10.1.1.1)."
msgstr ""
# 5d690ff5c70b4951a41d9ccf663e1e5d
#: ../../networking/external_firewalls_and_load_balancers.rst:191
msgid ""
"A source NAT rule that forwards all outgoing traffic from the account's "
"private VLAN to the public Internet, using the account's public IP address "
"as the source address"
msgstr ""
# a8b478c2d3334a0aa56507a774978095
#: ../../networking/external_firewalls_and_load_balancers.rst:195
msgid ""
"A firewall filter counter that measures the number of bytes of outgoing "
"traffic for the account"
msgstr ""
# 438d673ffaa3412c98761796e1c9043c
#: ../../networking/external_firewalls_and_load_balancers.rst:198
msgid "The following objects are created on the load balancer:"
msgstr ""
# 07491865d4a3476293c53ae24c343c78
#: ../../networking/external_firewalls_and_load_balancers.rst:200
msgid "A new VLAN that matches the account's provisioned Zone VLAN"
msgstr ""
# 3691e62805b34e95acd2ff232154ca0d
#: ../../networking/external_firewalls_and_load_balancers.rst:202
msgid ""
"A self IP for the VLAN. This is always the second IP of the account's "
"private subnet (e.g. 10.1.1.2)."
msgstr ""
# 1e387fca9feb4a08825eb2dfe3547fb0
#: ../../networking/external_firewalls_and_load_balancers.rst:207
msgid "Ongoing Configuration of External Firewalls and Load Balancers"
msgstr ""
# 133336c3018e4957ba148ad3a8f85ed4
#: ../../networking/external_firewalls_and_load_balancers.rst:209
msgid ""
"Additional user actions (e.g. setting a port forward) will cause further "
"programming of the firewall and load balancer. A user may request "
"additional public IP addresses and forward traffic received at these IPs to "
"specific VMs. This is accomplished by enabling static NAT for a public IP "
"address, assigning the IP to a VM, and specifying a set of protocols and "
"port ranges to open. When a static NAT rule is created, CloudStack programs "
"the zone's external firewall with the following objects:"
msgstr ""
# cfcd0d08f25142019221555a1a499683
#: ../../networking/external_firewalls_and_load_balancers.rst:218
msgid ""
"A static NAT rule that maps the public IP address to the private IP address "
"of a VM."
msgstr ""
# 76e196b931384143a2f1b65467f003dd
#: ../../networking/external_firewalls_and_load_balancers.rst:221
msgid ""
"A security policy that allows traffic within the set of protocols and port "
"ranges that are specified."
msgstr ""
# b6b755f7fb5a4d4d9495bfe3b0eac10e
#: ../../networking/external_firewalls_and_load_balancers.rst:224
msgid ""
"A firewall filter counter that measures the number of bytes of incoming "
"traffic to the public IP."
msgstr ""
# 077fa026b5954737b4af75e98a4dd1e8
#: ../../networking/external_firewalls_and_load_balancers.rst:227
msgid ""
"The number of incoming and outgoing bytes through source NAT, static NAT, "
"and load balancing rules is measured and saved on each external element. "
"This data is collected on a regular basis and stored in the CloudStack "
"database."
msgstr ""
# a882754de1c64a389513a78637f3325d
#: ../../networking/external_firewalls_and_load_balancers.rst:234
msgid "Load Balancer Rules"
msgstr "Règles de répartition de charge"
# 9b95ee51dc6e4026905b950584948d63
#: ../../networking/external_firewalls_and_load_balancers.rst:236
msgid ""
"A CloudStack user or administrator may create load balancing rules that "
"balance traffic received at a public IP to one or more VMs. A user creates "
"a rule, specifies an algorithm, and assigns the rule to a set of VMs."
msgstr ""
# 7ac5de99c5694e0b89ceb6d4c39e0dfb
#: ../../networking/external_firewalls_and_load_balancers.rst:242
msgid ""
"If you create load balancing rules while using a network service offering "
"that includes an external load balancer device such as NetScaler, and later "
"change the network service offering to one that uses the CloudStack virtual "
"router, you must create a firewall rule on the virtual router for each of "
"your existing load balancing rules so that they continue to function."
msgstr ""
"Si vous créez des règles de répartition de charge lors de votre utilisation "
"d'une offre de service réseau qui inclue un périphérique externe de "
"répartition de charge comme un NetScaler, et plus tard changez l'offre de "
"service réseau pour une qui utilise un routeur virtuel CloudStack, vous "
"devrez créer une règle de pare-feu sur le routeur virtuel pour chacune de "
"vos règles de répartition de charge afin qu'il puisse continuer de "
"fonctionner."
# b09aa6c58aa84b8f89b3293a64ca17fd
#: ../../networking/external_firewalls_and_load_balancers.rst:253
msgid "Adding a Load Balancer Rule"
msgstr "Ajouter une règle de répartition de charge"
# 1bc40a00c2f341118db65e97bbbcf986
#: ../../networking/external_firewalls_and_load_balancers.rst:255
msgid "Log in to the CloudStack UI as an administrator or end user."
msgstr ""
"Se connecter à l'interface de CloudStack comme administrateur ou "
"utilisateur final."
# 57f7d8a61234427abc813c4208e84192
#: ../../networking/external_firewalls_and_load_balancers.rst:257
msgid "In the left navigation, choose Network."
msgstr "Dans la navigation à gauche, choisissez Réseau."
# d947318aba7746718816eb5c7e29e9b1
#: ../../networking/external_firewalls_and_load_balancers.rst:259
msgid ""
"Click the name of the network where you want to load balance the traffic."
msgstr ""
# 20fc7dedf2cf482d94d8977ac64c6b0d
#: ../../networking/external_firewalls_and_load_balancers.rst:262
msgid "Click View IP Addresses."
msgstr "Cliquez sur Voir les adresses IP."
# aff4544b414847af82ceceb0bd4e3b55
#: ../../networking/external_firewalls_and_load_balancers.rst:264
msgid ""
"Click the IP address for which you want to create the rule, then click the "
"Configuration tab."
msgstr ""
# a84c70dc6b4f4d7c8f5a2d1f82b59355
#: ../../networking/external_firewalls_and_load_balancers.rst:267
msgid "In the Load Balancing node of the diagram, click View All."
msgstr ""
"Dans le noeud Répartiteur de charge du diagramme, cliquer sur Tout voir."
# 698c929938644fa88bcaa781f68ea4e7
#: ../../networking/external_firewalls_and_load_balancers.rst:269
msgid ""
"In a Basic zone, you can also create a load balancing rule without "
"acquiring or selecting an IP address. CloudStack internally assign an IP "
"when you create the load balancing rule, which is listed in the IP "
"Addresses page when the rule is created."
msgstr ""
# 2991ed0062324ee88859d10be3c6d280
#: ../../networking/external_firewalls_and_load_balancers.rst:274
msgid ""
"To do that, select the name of the network, then click Add Load Balancer "
"tab. Continue with #7."
msgstr ""
# f62541afe2764660ba42de5ab1903be0
#: ../../networking/external_firewalls_and_load_balancers.rst:277
msgid "Fill in the following:"
msgstr "Remplissez les champs suivants:"
# 9d106d6a229045acbfc2622c0c395bd9
#: ../../networking/external_firewalls_and_load_balancers.rst:279
msgid "**Name**: A name for the load balancer rule."
msgstr ""
# 75090eb93c0c438fbb12cc3c26d20ef9
#: ../../networking/external_firewalls_and_load_balancers.rst:281
msgid "**Public Port**: The port receiving incoming traffic to be balanced."
msgstr ""
# 61dc53b8703148608a98d96de9b2f3f7
#: ../../networking/external_firewalls_and_load_balancers.rst:284
msgid ""
"**Private Port**: The port that the VMs will use to receive the traffic."
msgstr ""
# 9e98c799101c44728527da77d95553ee
#: ../../networking/external_firewalls_and_load_balancers.rst:287
msgid ""
"**Algorithm**: Choose the load balancing algorithm you want CloudStack to "
"use. CloudStack supports a variety of well-known algorithms. If you are not "
"familiar with these choices, you will find plenty of information about them "
"on the Internet."
msgstr ""
# 1fc198ccbf4e4718beba8aaec97b2a38
#: ../../networking/external_firewalls_and_load_balancers.rst:292
msgid ""
"**Stickiness**: (Optional) Click Configure and choose the algorithm for the "
"stickiness policy. See Sticky Session Policies for Load Balancer Rules."
msgstr ""
# 8d672e758cc24f2da82cbdd82c83ea21
#: ../../networking/external_firewalls_and_load_balancers.rst:296
msgid ""
"**AutoScale**: Click Configure and complete the AutoScale configuration as "
"explained in :ref:`conf-autoscale`."
msgstr ""
# 33ab79892f344fde975f3d6c32cd9b12
#: ../../networking/external_firewalls_and_load_balancers.rst:299
msgid ""
"**Health Check**: (Optional; NetScaler load balancers only) Click Configure "
"and fill in the characteristics of the health check policy. See :ref:"
"`health-check`."
msgstr ""
# d643db9463b745c7ac1f19daad8358dd
#: ../../networking/external_firewalls_and_load_balancers.rst:303
msgid ""
"**Ping path (Optional)**: Sequence of destinations to which to send health "
"check queries. Default: / (all)."
msgstr ""
# b33a72d1050241329dd52806584f0b49
#: ../../networking/external_firewalls_and_load_balancers.rst:306
msgid ""
"**Response time (Optional)**: How long to wait for a response from the "
"health check (2 - 60 seconds). Default: 5 seconds."
msgstr ""
# 885f1763ea71493ea93ba841259240b3
#: ../../networking/external_firewalls_and_load_balancers.rst:309
msgid ""
"**Interval time (Optional)**: Amount of time between health checks (1 "
"second - 5 minutes). Default value is set in the global configuration "
"parameter lbrule\\_health check\\_time\\_interval."
msgstr ""
# 82dd529deb534e00b11b709fad1a829f
#: ../../networking/external_firewalls_and_load_balancers.rst:314
msgid ""
"**Healthy threshold (Optional)**: Number of consecutive health check "
"successes that are required before declaring an instance healthy. Default: "
"2."
msgstr ""
# 8c946ad8aa9b402ba1d7808681a90216
#: ../../networking/external_firewalls_and_load_balancers.rst:318
msgid ""
"**Unhealthy threshold (Optional)**: Number of consecutive health check "
"failures that are required before declaring an instance unhealthy. Default: "
"10."
msgstr ""
# 8bd4120f80ff41368605d05b647ee837
#: ../../networking/external_firewalls_and_load_balancers.rst:322
msgid ""
"Click Add VMs, then select two or more VMs that will divide the load of "
"incoming traffic, and click Apply."
msgstr ""
# 9720f8ded014448394288000a5c40217
#: ../../networking/external_firewalls_and_load_balancers.rst:325
msgid ""
"The new load balancer rule appears in the list. You can repeat these steps "
"to add more load balancer rules for this IP address."
msgstr ""
# 3ccedfb3a9324eb1860d1924ac909e3a
#: ../../networking/external_firewalls_and_load_balancers.rst:330
msgid "Sticky Session Policies for Load Balancer Rules"
msgstr ""
# b33d98749eb5488a8a02cad61861c752
#: ../../networking/external_firewalls_and_load_balancers.rst:332
msgid ""
"Sticky sessions are used in Web-based applications to ensure continued "
"availability of information across the multiple requests in a user's "
"session. For example, if a shopper is filling a cart, you need to remember "
"what has been purchased so far. The concept of \"stickiness\" is also "
"referred to as persistence or maintaining state."
msgstr ""
# 68678f9c4f934ed796779a0d4121e91a
#: ../../networking/external_firewalls_and_load_balancers.rst:338
msgid ""
"Any load balancer rule defined in CloudStack can have a stickiness policy. "
"The policy consists of a name, stickiness method, and parameters. The "
"parameters are name-value pairs or flags, which are defined by the load "
"balancer vendor. The stickiness method could be load balancer-generated "
"cookie, application-generated cookie, or source-based. In the source-based "
"method, the source IP address is used to identify the user and locate the "
"user's stored data. In the other methods, cookies are used. The cookie "
"generated by the load balancer or application is included in request and "
"response URLs to create persistence. The cookie name can be specified by "
"the administrator or automatically generated. A variety of options are "
"provided to control the exact behavior of cookies, such as how they are "
"generated and whether they are cached."
msgstr ""
# bb05b34273814acfb053cac6ffdfe917
#: ../../networking/external_firewalls_and_load_balancers.rst:352
msgid ""
"For the most up to date list of available stickiness methods, see the "
"CloudStack UI or call listNetworks and check the SupportedStickinessMethods "
"capability."
msgstr ""
# 35aba1c4298e4ecdaaa750f3375b4be2
#: ../../networking/external_firewalls_and_load_balancers.rst:360
msgid "Health Checks for Load Balancer Rules"
msgstr ""
# d9cc398640dc410ea5c44e614e8d82cd
#: ../../networking/external_firewalls_and_load_balancers.rst:362
msgid "(NetScaler load balancer only; requires NetScaler version 10.0)"
msgstr ""
# 13a5a45067f34a0b8387527dfaa9d0ce
#: ../../networking/external_firewalls_and_load_balancers.rst:364
msgid ""
"Health checks are used in load-balanced applications to ensure that "
"requests are forwarded only to running, available services. When creating a "
"load balancer rule, you can specify a health check policy. This is in "
"addition to specifying the stickiness policy, algorithm, and other load "
"balancer rule options. You can configure one health check policy per load "
"balancer rule."
msgstr ""
# 507b3dcc2fbd48a18c5ae46dcb37b341
#: ../../networking/external_firewalls_and_load_balancers.rst:371
msgid ""
"Any load balancer rule defined on a NetScaler load balancer in CloudStack "
"can have a health check policy. The policy consists of a ping path, "
"thresholds to define \"healthy\" and \"unhealthy\" states, health check "
"frequency, and timeout wait interval."
msgstr ""
# 35f78e270b3e47749e7a677486944ac1
#: ../../networking/external_firewalls_and_load_balancers.rst:376
msgid ""
"When a health check policy is in effect, the load balancer will stop "
"forwarding requests to any resources that are found to be unhealthy. If the "
"resource later becomes available again, the periodic health check will "
"discover it, and the resource will once again be added to the pool of "
"resources that can receive requests from the load balancer. At any given "
"time, the most recent result of the health check is displayed in the UI. "
"For any VM that is attached to a load balancer rule with a health check "
"configured, the state will be shown as UP or DOWN in the UI depending on "
"the result of the most recent health check."
msgstr ""
# bdff04e42c3943e38c182443f757f743
#: ../../networking/external_firewalls_and_load_balancers.rst:386
msgid "You can delete or modify existing health check policies."
msgstr ""
# eef49f2114c344a58739dcf8f68aac70
#: ../../networking/external_firewalls_and_load_balancers.rst:388
msgid ""
"To configure how often the health check is performed by default, use the "
"global configuration setting healthcheck.update.interval (default value is "
"600 seconds). You can override this value for an individual health check "
"policy."
msgstr ""
# 6f13b2ca1fd74ad2a09363a9de9dfa54
#: ../../networking/external_firewalls_and_load_balancers.rst:393
msgid ""
"For details on how to set a health check policy using the UI, see :ref:"
"`adding-lb-rule`."
msgstr ""
# 6f66a1def18847c0ba2eec5214f58bc4
#: ../../networking/external_firewalls_and_load_balancers.rst:400
msgid "Configuring AutoScale"
msgstr ""
# 1d10105f71d4436ca70e813d83aa587d
#: ../../networking/external_firewalls_and_load_balancers.rst:402
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 ""
# f916e1ba803d4d5f93f20a1fc650704f
#: ../../networking/external_firewalls_and_load_balancers.rst:410
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 ""
# fa4167d0761945e6b5552ddc195aa1cb
#: ../../networking/external_firewalls_and_load_balancers.rst:419
msgid ""
"CloudStack uses the NetScaler load balancer to monitor all aspects of a "
"system's health and work in unison with CloudStack to initiate scale-up or "
"scale-down actions."
msgstr ""
# 25cc6eeee03544bead38d29ffde91c33
#: ../../networking/external_firewalls_and_load_balancers.rst:424
msgid ""
"AutoScale is supported on NetScaler Release 10 Build 74.4006.e and beyond."
msgstr ""
# f97b092a261142629f674c1cf40ee949
#: ../../networking/external_firewalls_and_load_balancers.rst:428
msgid "Prerequisites"
msgstr "Prérequis"
# 0c697f756785488aaa591aa8b9a921cc
#: ../../networking/external_firewalls_and_load_balancers.rst:430
msgid "Before you configure an AutoScale rule, consider the following:"
msgstr ""
# 8229cf3ea2d24a22bc9707f8f142ca5e
#: ../../networking/external_firewalls_and_load_balancers.rst:432
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 ""
# a3b170baceb44749ba1bc8c05a2d5b1c
#: ../../networking/external_firewalls_and_load_balancers.rst:437
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 ""
# df32d04c33ca462ea54e7d716b2d8ffe
#: ../../networking/external_firewalls_and_load_balancers.rst:441
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 ""
# e416b95063a0497fa2b7ca6430c0957c
#: ../../networking/external_firewalls_and_load_balancers.rst:446
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 `\"Configuring SNMP Community String on a RHELServer\" "
"<#configuring-snmp-community-string-on-a-rhel-server>`_ to configure SNMP "
"on a RHEL machine."
msgstr ""
# 0ac0707e74464bd0840f60e335716a25
#: ../../networking/external_firewalls_and_load_balancers.rst:456
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 server's cluster. Additionally, ensure that the NetScaler "
"device has access to this IP address to provide AutoScale support."
msgstr ""
# f8d93cd584a54fd8b2a72143d4107323
#: ../../networking/external_firewalls_and_load_balancers.rst:464
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 :ref:`update-autoscale`."
msgstr ""
# f4e671d2a1814ee7936944319291f882
#: ../../networking/external_firewalls_and_load_balancers.rst:468
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 ""
# 1def24ca3fcf4a9984043a4339307137
#: ../../networking/external_firewalls_and_load_balancers.rst:473
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 ""
# d722fd21fbb64e1f8fe5c04b72d39a29
#: ../../networking/external_firewalls_and_load_balancers.rst:480
msgid "Configuration"
msgstr "Configuration"
# aa34165bbbed4360bb6cebfc7b978d91
#: ../../networking/external_firewalls_and_load_balancers.rst:482
msgid "Specify the following:"
msgstr "Spécifier les informations suivantes :"
# 306046475ddb4e789bc88bc1633cdc73
#: ../../networking/external_firewalls_and_load_balancers.rst:484
msgid "|autoscaleateconfig.png|"
msgstr "|autoscaleateconfig.png|"
# 951132877c0f4870b67560ae8035c8eb
#: ../../networking/external_firewalls_and_load_balancers.rst:486
msgid ""
"**Template**: 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 ""
# 313bdbb8a05e46239d80664ae76a92cf
#: ../../networking/external_firewalls_and_load_balancers.rst:494
msgid ""
"**Compute offering**: 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 ""
# cd0d1d8ce17d439eb9c360d182e61bc0
#: ../../networking/external_firewalls_and_load_balancers.rst:500
msgid ""
"**Min Instance**: 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 ""
# b883f060ac0a4b669952542845307113
#: ../../networking/external_firewalls_and_load_balancers.rst:508
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 ""
# 1062b529c80542fe9f49822dc8e1226b
#: ../../networking/external_firewalls_and_load_balancers.rst:518
msgid ""
"**Max Instance**: Maximum number of active VM instances that **should be "
"assigned to**\\ a load balancing rule. This parameter defines the upper "
"limit of active VM instances that can be assigned to a load balancing rule."
msgstr ""
# 2f6f81ae0f294d00be1d4501c00d3ef4
#: ../../networking/external_firewalls_and_load_balancers.rst:523
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 ""
# 80e14b2eba9f4b31bf0f73a8fb4665ac
#: ../../networking/external_firewalls_and_load_balancers.rst:529
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 ""
# c05f5503e8994d1bbe38126fc1652574
#: ../../networking/external_firewalls_and_load_balancers.rst:537
msgid "Specify the following scale-up and scale-down policies:"
msgstr ""
# 8b8ee965cf5f45e4a993ef5a61584ee7
#: ../../networking/external_firewalls_and_load_balancers.rst:539
msgid ""
"**Duration**: 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 ""
# aef0e1b396cc4f4aa88ea919926bc457
#: ../../networking/external_firewalls_and_load_balancers.rst:544
msgid ""
"**Counter**: The performance counters expose the state of the monitored "
"instances. By default, CloudStack 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 "
"CloudStack by using the CloudStack API."
msgstr ""
# e13329c9be684765967ad40f1ed75b4e
#: ../../networking/external_firewalls_and_load_balancers.rst:551
msgid ""
"**Operator**: 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 ""
# 736606eaa3ac4622b52ed0ab0545ba37
#: ../../networking/external_firewalls_and_load_balancers.rst:555
msgid ""
"**Threshold**: 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 ""
# e74122a065ed4373a7c1291eb1291e64
#: ../../networking/external_firewalls_and_load_balancers.rst:559
msgid "**Add**: Click Add to add the condition."
msgstr ""
# 7d05f0a9ea384a5790999dfcd7fd3647
#: ../../networking/external_firewalls_and_load_balancers.rst:561
msgid ""
"Additionally, if you want to configure the advanced settings, click Show "
"advanced settings, and specify the following:"
msgstr ""
# 9e8ccf2af53541eea6450c116ba10b0a
#: ../../networking/external_firewalls_and_load_balancers.rst:564
msgid ""
"**Polling interval**: 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 ""
# 9a0a8077043d427ba02f39207e648c16
#: ../../networking/external_firewalls_and_load_balancers.rst:569
msgid ""
"**Quiet Time**: 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 ""
# d562af8950534ba78cfad860812c91af
#: ../../networking/external_firewalls_and_load_balancers.rst:576
msgid ""
"**Destroy VM Grace Period**: 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 ""
# b74500ed7cdc4d5e984c9d01a17d6cae
#: ../../networking/external_firewalls_and_load_balancers.rst:582
msgid ""
"**Security Groups**: 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 ""
# 6e921b5c683943bf8e306cb4cd731b76
#: ../../networking/external_firewalls_and_load_balancers.rst:589
msgid ""
"**Disk Offerings**: A predefined set of disk size for primary data storage."
msgstr ""
# 8eeeb8c4bf1749e6b405081fce9318ca
#: ../../networking/external_firewalls_and_load_balancers.rst:592
msgid ""
"**SNMP Community**: 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 ""
# 63d93ca18c5245e3aa630d743d5b1fff
#: ../../networking/external_firewalls_and_load_balancers.rst:596
msgid ""
"**SNMP Port**: The port number on which the SNMP agent that run on the "
"provisioned VMs is listening. Default port is 161."
msgstr ""
# 8e4ead8319ea470ba2e3a6183acf7ce2
#: ../../networking/external_firewalls_and_load_balancers.rst:599
msgid ""
"**User**: 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 ""
# c5ab8b8578de4f5b8e2aa37c414525aa
#: ../../networking/external_firewalls_and_load_balancers.rst:604
msgid "**Apply**: Click Apply to create the AutoScale configuration."
msgstr ""
# 3d6ec42e045a4082a8798bec5791982a
#: ../../networking/external_firewalls_and_load_balancers.rst:608
msgid "Disabling and Enabling an AutoScale Configuration"
msgstr ""
# ec5c758cc62a40e587a4b6c4fddb434f
#: ../../networking/external_firewalls_and_load_balancers.rst:610
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 |EnableDisable.png| "
"button."
msgstr ""
# 0a60f936b205455c98dceed77b11df3c
#: ../../networking/external_firewalls_and_load_balancers.rst:616
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 |"
"EnableDisable.png| button."
msgstr ""
# f4bb71e85bd344b89fdcb3239a0f51f8
#: ../../networking/external_firewalls_and_load_balancers.rst:626
msgid "Updating an AutoScale Configuration"
msgstr ""
# 3bf60f14a73d43869794736b33b5aa5b
#: ../../networking/external_firewalls_and_load_balancers.rst:628
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 ""
# f9665a6811b3410ba434ca755c6451f6
#: ../../networking/external_firewalls_and_load_balancers.rst:633
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 ""
# debb34a5766f45ca8759a81e6401dc05
#: ../../networking/external_firewalls_and_load_balancers.rst:639
msgid "Runtime Considerations"
msgstr ""
# 57af5a07b00746d1b071d2eb6e80fea1
#: ../../networking/external_firewalls_and_load_balancers.rst:641
msgid ""
"An administrator should not assign a VM to a load balancing rule which is "
"configured for AutoScale."
msgstr ""
# 7df6035fc7ca442bbbb5d7bd0ea0428b
#: ../../networking/external_firewalls_and_load_balancers.rst:644
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 ""
# 0eca9ec603bb4fc28eaabd868afa3e27
#: ../../networking/external_firewalls_and_load_balancers.rst:651
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 ""