cloudstack-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From pdion...@apache.org
Subject [25/63] [abbrv] cloudstack-docs-admin git commit: 50% des chaines sont traduites en FR
Date Wed, 08 Feb 2017 01:18:38 GMT
http://git-wip-us.apache.org/repos/asf/cloudstack-docs-admin/blob/a6b15cb9/source/locale/pot/networking/external_firewalls_and_load_balancers.pot
----------------------------------------------------------------------
diff --git a/source/locale/pot/networking/external_firewalls_and_load_balancers.pot b/source/locale/pot/networking/external_firewalls_and_load_balancers.pot
index ebe9d94..046bacf 100644
--- a/source/locale/pot/networking/external_firewalls_and_load_balancers.pot
+++ b/source/locale/pot/networking/external_firewalls_and_load_balancers.pot
@@ -1,14 +1,14 @@
 # SOME DESCRIPTIVE TITLE.
-# Copyright (C) 
+# Copyright (C) 2016, Apache Software Foundation
 # This file is distributed under the same license as the Apache CloudStack Administration Documentation package.
 # FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
 #
 #, fuzzy
 msgid ""
 msgstr ""
-"Project-Id-Version: Apache CloudStack Administration Documentation 4\n"
+"Project-Id-Version: Apache CloudStack Administration Documentation 4.8\n"
 "Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2014-06-30 12:52+0200\n"
+"POT-Creation-Date: 2016-08-22 13:55+0200\n"
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
 "Language-Team: LANGUAGE <LL@li.org>\n"
@@ -17,687 +17,550 @@ msgstr ""
 "Content-Transfer-Encoding: 8bit\n"
 
 #: ../../networking/external_firewalls_and_load_balancers.rst:18
-# 9b2c57c96864404ab39ea18532184a3c
 msgid "External Firewalls and Load Balancers"
 msgstr ""
 
 #: ../../networking/external_firewalls_and_load_balancers.rst:20
-# 406fa3a599d74b6fb0f6a893d839784a
 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 ""
 
 #: ../../networking/external_firewalls_and_load_balancers.rst:27
-# e50bcd9fe60e430d85efc883354624a5
 msgid "About Using a NetScaler Load Balancer"
 msgstr ""
 
 #: ../../networking/external_firewalls_and_load_balancers.rst:29
-# 1cf32061da5449a2a6dc5887c27b0d72
 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 ""
 
 #: ../../networking/external_firewalls_and_load_balancers.rst:35
-# 188f8456b75c41ffadbc92d637327f54
 msgid "In a Basic zone, load balancing service is supported only if Elastic IP or Elastic LB services are enabled."
 msgstr ""
 
 #: ../../networking/external_firewalls_and_load_balancers.rst:38
-# 7189603a0b934b4b8f4de77ccc774586
 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 ""
 
 #: ../../networking/external_firewalls_and_load_balancers.rst:52
-# baddaa181f054bb5b0b41e5dcce1387e
 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 ""
 
 #: ../../networking/external_firewalls_and_load_balancers.rst:56
-# 263c8a9eb9d147ad91ae71970d65bd41
 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 ""
 
 #: ../../networking/external_firewalls_and_load_balancers.rst:61
-# 79187d2fbfa743c39e8c524304235dc2
 msgid "To install and enable an external load balancer for CloudStack management, see External Guest Load Balancer Integration in the Installation Guide."
 msgstr ""
 
 #: ../../networking/external_firewalls_and_load_balancers.rst:65
-# d3c851ee525b49599c01646d4d1e2dd5
 msgid "The Citrix NetScaler comes in three varieties. The following summarizes how these variants are treated in CloudStack."
 msgstr ""
 
 #: ../../networking/external_firewalls_and_load_balancers.rst:68
-# 64aec7c1c44049498dcf6c10b4fa5605
 msgid "**MPX**"
 msgstr ""
 
 #: ../../networking/external_firewalls_and_load_balancers.rst:70
-# b8df1ce8dfa14d8c8ecc441c6f71748f
 msgid "Physical appliance. Capable of deep packet inspection. Can act as application firewall and load balancer"
 msgstr ""
 
 #: ../../networking/external_firewalls_and_load_balancers.rst:73
-# 3a1ec0e897e34118a0fbeb78f64a544a
 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 ""
 
 #: ../../networking/external_firewalls_and_load_balancers.rst:77
-# 68d5e27c550d40cd921b14324d33692a
 msgid "**VPX**"
 msgstr ""
 
 #: ../../networking/external_firewalls_and_load_balancers.rst:79
-# 886b66d79fd049739f35d53684946f35
 msgid "Virtual appliance. Can run as VM on XenServer, ESXi, and Hyper-V hypervisors. Same functionality as MPX"
 msgstr ""
 
 #: ../../networking/external_firewalls_and_load_balancers.rst:82
-# acdf8d15b2b740579349caa99d8ff14f
 msgid "Supported on ESXi and XenServer. Same functional support as for MPX. CloudStack will treat VPX and MPX as the same device type."
 msgstr ""
 
 #: ../../networking/external_firewalls_and_load_balancers.rst:85
-# 632775a416fd40bfb11895ae39b883e9
 msgid "**SDX**"
 msgstr ""
 
 #: ../../networking/external_firewalls_and_load_balancers.rst:87
-# 94896445c73d42c7a8a8b30da3d762a9
 msgid "Physical appliance. Can create multiple fully isolated VPX instances on a single appliance to support multi-tenant usage"
 msgstr ""
 
 #: ../../networking/external_firewalls_and_load_balancers.rst:90
-# 7272ab89523e416fba357a4ceb24b459
 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 ""
 
 #: ../../networking/external_firewalls_and_load_balancers.rst:98
-# e712ff0906b7463083ac7a8f9b19847c
 msgid "Configuring SNMP Community String on a RHEL Server"
 msgstr ""
 
 #: ../../networking/external_firewalls_and_load_balancers.rst:100
-# a0e11ba7efae4e63a0cd9eb015162722
 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 ""
 
 #: ../../networking/external_firewalls_and_load_balancers.rst:106
-# d9a8fc53fc4949bda74cb44fbcb04146
 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 ""
 
 #: ../../networking/external_firewalls_and_load_balancers.rst:110
-# 9f7d96642a9b435ab7687ecf88e6f6de
 msgid "Ensure that you installed SNMP on RedHat. If not, run the following command:"
 msgstr ""
 
 #: ../../networking/external_firewalls_and_load_balancers.rst:117
-# 657a8fba85b14585be4a9165ba95128b
 msgid "Edit the /etc/snmp/snmpd.conf file to allow the SNMP polling from the NetScaler device."
 msgstr ""
 
 #: ../../networking/external_firewalls_and_load_balancers.rst:120
-# 752d34a607b64dbea0348f5551d5cebc
 msgid "Map the community name into a security name (local and mynetwork, depending on where the request is coming from):"
 msgstr ""
 
 #: ../../networking/external_firewalls_and_load_balancers.rst:124
-# 07b1fa6ac91c4aa186c434d633b0384e
 msgid "Use a strong password instead of public when you edit the following table."
 msgstr ""
 
 #: ../../networking/external_firewalls_and_load_balancers.rst:133
-# f8acb0abc31c4fd0ab9300c705ba1f72
 msgid "Setting to 0.0.0.0 allows all IPs to poll the NetScaler server."
 msgstr ""
 
 #: ../../networking/external_firewalls_and_load_balancers.rst:135
-# 327a4b1c1e4d429c83dc1e1628f8376a
 msgid "Map the security names into group names:"
 msgstr ""
 
 #: ../../networking/external_firewalls_and_load_balancers.rst:145
-# 193cbe00950147958924521840ba4405
 msgid "Create a view to allow the groups to have the permission to:"
 msgstr ""
 
 #: ../../networking/external_firewalls_and_load_balancers.rst:151
-# 39191ba80aa24e32898e8a79892fb7cf
 msgid "Grant access with different write permissions to the two groups to the view you created."
 msgstr ""
 
 #: ../../networking/external_firewalls_and_load_balancers.rst:160
-# ca08ac1ab89442c9a42c7d59efa70e6b
 msgid "Unblock SNMP in iptables."
 msgstr ""
 
 #: ../../networking/external_firewalls_and_load_balancers.rst:166
-# f161affb624f4139be0750f3dc19f505
 msgid "Start the SNMP service:"
 msgstr ""
 
 #: ../../networking/external_firewalls_and_load_balancers.rst:172
-# 60eb8801ebf44b97b3b4cc63348013b6
 msgid "Ensure that the SNMP service is started automatically during the system startup:"
 msgstr ""
 
 #: ../../networking/external_firewalls_and_load_balancers.rst:181
-# 8893688efc574dbfba90b00df9f467bd
 msgid "Initial Setup of External Firewalls and Load Balancers"
 msgstr ""
 
 #: ../../networking/external_firewalls_and_load_balancers.rst:183
-# 2149019287d549649f77e49102f3a8e2
 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 ""
 
 #: ../../networking/external_firewalls_and_load_balancers.rst:187
-# 7bec0089c55040c9bcc3b75a4ce9ae0b
 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 ""
 
 #: ../../networking/external_firewalls_and_load_balancers.rst:191
-# 5d690ff5c70b4951a41d9ccf663e1e5d
 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 ""
 
 #: ../../networking/external_firewalls_and_load_balancers.rst:195
-# a8b478c2d3334a0aa56507a774978095
 msgid "A firewall filter counter that measures the number of bytes of outgoing traffic for the account"
 msgstr ""
 
 #: ../../networking/external_firewalls_and_load_balancers.rst:198
-# 438d673ffaa3412c98761796e1c9043c
 msgid "The following objects are created on the load balancer:"
 msgstr ""
 
 #: ../../networking/external_firewalls_and_load_balancers.rst:200
-# 07491865d4a3476293c53ae24c343c78
 msgid "A new VLAN that matches the account's provisioned Zone VLAN"
 msgstr ""
 
 #: ../../networking/external_firewalls_and_load_balancers.rst:202
-# 3691e62805b34e95acd2ff232154ca0d
 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 ""
 
 #: ../../networking/external_firewalls_and_load_balancers.rst:207
-# 1e387fca9feb4a08825eb2dfe3547fb0
 msgid "Ongoing Configuration of External Firewalls and Load Balancers"
 msgstr ""
 
 #: ../../networking/external_firewalls_and_load_balancers.rst:209
-# 133336c3018e4957ba148ad3a8f85ed4
 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 ""
 
 #: ../../networking/external_firewalls_and_load_balancers.rst:218
-# cfcd0d08f25142019221555a1a499683
 msgid "A static NAT rule that maps the public IP address to the private IP address of a VM."
 msgstr ""
 
 #: ../../networking/external_firewalls_and_load_balancers.rst:221
-# 76e196b931384143a2f1b65467f003dd
 msgid "A security policy that allows traffic within the set of protocols and port ranges that are specified."
 msgstr ""
 
 #: ../../networking/external_firewalls_and_load_balancers.rst:224
-# b6b755f7fb5a4d4d9495bfe3b0eac10e
 msgid "A firewall filter counter that measures the number of bytes of incoming traffic to the public IP."
 msgstr ""
 
 #: ../../networking/external_firewalls_and_load_balancers.rst:227
-# 077fa026b5954737b4af75e98a4dd1e8
 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 ""
 
 #: ../../networking/external_firewalls_and_load_balancers.rst:234
-# a882754de1c64a389513a78637f3325d
 msgid "Load Balancer Rules"
 msgstr ""
 
 #: ../../networking/external_firewalls_and_load_balancers.rst:236
-# 9b95ee51dc6e4026905b950584948d63
 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 ""
 
 #: ../../networking/external_firewalls_and_load_balancers.rst:242
-# 7ac5de99c5694e0b89ceb6d4c39e0dfb
 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 ""
 
 #: ../../networking/external_firewalls_and_load_balancers.rst:253
-# b09aa6c58aa84b8f89b3293a64ca17fd
 msgid "Adding a Load Balancer Rule"
 msgstr ""
 
 #: ../../networking/external_firewalls_and_load_balancers.rst:255
-# 1bc40a00c2f341118db65e97bbbcf986
 msgid "Log in to the CloudStack UI as an administrator or end user."
 msgstr ""
 
 #: ../../networking/external_firewalls_and_load_balancers.rst:257
-# 57f7d8a61234427abc813c4208e84192
 msgid "In the left navigation, choose Network."
 msgstr ""
 
 #: ../../networking/external_firewalls_and_load_balancers.rst:259
-# d947318aba7746718816eb5c7e29e9b1
 msgid "Click the name of the network where you want to load balance the traffic."
 msgstr ""
 
 #: ../../networking/external_firewalls_and_load_balancers.rst:262
-# 20fc7dedf2cf482d94d8977ac64c6b0d
 msgid "Click View IP Addresses."
 msgstr ""
 
 #: ../../networking/external_firewalls_and_load_balancers.rst:264
-# aff4544b414847af82ceceb0bd4e3b55
 msgid "Click the IP address for which you want to create the rule, then click the Configuration tab."
 msgstr ""
 
 #: ../../networking/external_firewalls_and_load_balancers.rst:267
-# a84c70dc6b4f4d7c8f5a2d1f82b59355
 msgid "In the Load Balancing node of the diagram, click View All."
 msgstr ""
 
 #: ../../networking/external_firewalls_and_load_balancers.rst:269
-# 698c929938644fa88bcaa781f68ea4e7
 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 ""
 
 #: ../../networking/external_firewalls_and_load_balancers.rst:274
-# 2991ed0062324ee88859d10be3c6d280
 msgid "To do that, select the name of the network, then click Add Load Balancer tab. Continue with #7."
 msgstr ""
 
 #: ../../networking/external_firewalls_and_load_balancers.rst:277
-# f62541afe2764660ba42de5ab1903be0
 msgid "Fill in the following:"
 msgstr ""
 
 #: ../../networking/external_firewalls_and_load_balancers.rst:279
-# 9d106d6a229045acbfc2622c0c395bd9
 msgid "**Name**: A name for the load balancer rule."
 msgstr ""
 
 #: ../../networking/external_firewalls_and_load_balancers.rst:281
-# 75090eb93c0c438fbb12cc3c26d20ef9
 msgid "**Public Port**: The port receiving incoming traffic to be balanced."
 msgstr ""
 
 #: ../../networking/external_firewalls_and_load_balancers.rst:284
-# 61dc53b8703148608a98d96de9b2f3f7
 msgid "**Private Port**: The port that the VMs will use to receive the traffic."
 msgstr ""
 
 #: ../../networking/external_firewalls_and_load_balancers.rst:287
-# 9e98c799101c44728527da77d95553ee
 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 ""
 
 #: ../../networking/external_firewalls_and_load_balancers.rst:292
-# 1fc198ccbf4e4718beba8aaec97b2a38
 msgid "**Stickiness**: (Optional) Click Configure and choose the algorithm for the stickiness policy. See Sticky Session Policies for Load Balancer Rules."
 msgstr ""
 
 #: ../../networking/external_firewalls_and_load_balancers.rst:296
-# 8d672e758cc24f2da82cbdd82c83ea21
 msgid "**AutoScale**: Click Configure and complete the AutoScale configuration as explained in :ref:`conf-autoscale`."
 msgstr ""
 
 #: ../../networking/external_firewalls_and_load_balancers.rst:299
-# 33ab79892f344fde975f3d6c32cd9b12
 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 ""
 
 #: ../../networking/external_firewalls_and_load_balancers.rst:303
-# d643db9463b745c7ac1f19daad8358dd
 msgid "**Ping path (Optional)**: Sequence of destinations to which to send health check queries. Default: / (all)."
 msgstr ""
 
 #: ../../networking/external_firewalls_and_load_balancers.rst:306
-# b33a72d1050241329dd52806584f0b49
 msgid "**Response time (Optional)**: How long to wait for a response from the health check (2 - 60 seconds). Default: 5 seconds."
 msgstr ""
 
 #: ../../networking/external_firewalls_and_load_balancers.rst:309
-# 885f1763ea71493ea93ba841259240b3
 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 ""
 
 #: ../../networking/external_firewalls_and_load_balancers.rst:314
-# 82dd529deb534e00b11b709fad1a829f
 msgid "**Healthy threshold (Optional)**: Number of consecutive health check successes that are required before declaring an instance healthy. Default: 2."
 msgstr ""
 
 #: ../../networking/external_firewalls_and_load_balancers.rst:318
-# 8c946ad8aa9b402ba1d7808681a90216
 msgid "**Unhealthy threshold (Optional)**: Number of consecutive health check failures that are required before declaring an instance unhealthy. Default: 10."
 msgstr ""
 
 #: ../../networking/external_firewalls_and_load_balancers.rst:322
-# 8bd4120f80ff41368605d05b647ee837
 msgid "Click Add VMs, then select two or more VMs that will divide the load of incoming traffic, and click Apply."
 msgstr ""
 
 #: ../../networking/external_firewalls_and_load_balancers.rst:325
-# 9720f8ded014448394288000a5c40217
 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 ""
 
 #: ../../networking/external_firewalls_and_load_balancers.rst:330
-# 3ccedfb3a9324eb1860d1924ac909e3a
 msgid "Sticky Session Policies for Load Balancer Rules"
 msgstr ""
 
 #: ../../networking/external_firewalls_and_load_balancers.rst:332
-# b33d98749eb5488a8a02cad61861c752
 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 ""
 
 #: ../../networking/external_firewalls_and_load_balancers.rst:338
-# 68678f9c4f934ed796779a0d4121e91a
 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 ""
 
 #: ../../networking/external_firewalls_and_load_balancers.rst:352
-# bb05b34273814acfb053cac6ffdfe917
 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 ""
 
 #: ../../networking/external_firewalls_and_load_balancers.rst:360
-# 35aba1c4298e4ecdaaa750f3375b4be2
 msgid "Health Checks for Load Balancer Rules"
 msgstr ""
 
 #: ../../networking/external_firewalls_and_load_balancers.rst:362
-# d9cc398640dc410ea5c44e614e8d82cd
 msgid "(NetScaler load balancer only; requires NetScaler version 10.0)"
 msgstr ""
 
 #: ../../networking/external_firewalls_and_load_balancers.rst:364
-# 13a5a45067f34a0b8387527dfaa9d0ce
 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 ""
 
 #: ../../networking/external_firewalls_and_load_balancers.rst:371
-# 507b3dcc2fbd48a18c5ae46dcb37b341
 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 ""
 
 #: ../../networking/external_firewalls_and_load_balancers.rst:376
-# 35f78e270b3e47749e7a677486944ac1
 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 ""
 
 #: ../../networking/external_firewalls_and_load_balancers.rst:386
-# bdff04e42c3943e38c182443f757f743
 msgid "You can delete or modify existing health check policies."
 msgstr ""
 
 #: ../../networking/external_firewalls_and_load_balancers.rst:388
-# eef49f2114c344a58739dcf8f68aac70
 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 ""
 
 #: ../../networking/external_firewalls_and_load_balancers.rst:393
-# 6f13b2ca1fd74ad2a09363a9de9dfa54
 msgid "For details on how to set a health check policy using the UI, see :ref:`adding-lb-rule`."
 msgstr ""
 
 #: ../../networking/external_firewalls_and_load_balancers.rst:400
-# 6f66a1def18847c0ba2eec5214f58bc4
 msgid "Configuring AutoScale"
 msgstr ""
 
 #: ../../networking/external_firewalls_and_load_balancers.rst:402
-# 1d10105f71d4436ca70e813d83aa587d
 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 ""
 
 #: ../../networking/external_firewalls_and_load_balancers.rst:410
-# f916e1ba803d4d5f93f20a1fc650704f
 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 ""
 
 #: ../../networking/external_firewalls_and_load_balancers.rst:419
-# fa4167d0761945e6b5552ddc195aa1cb
 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 ""
 
 #: ../../networking/external_firewalls_and_load_balancers.rst:424
-# 25cc6eeee03544bead38d29ffde91c33
 msgid "AutoScale is supported on NetScaler Release 10 Build 74.4006.e and beyond."
 msgstr ""
 
 #: ../../networking/external_firewalls_and_load_balancers.rst:428
-# f97b092a261142629f674c1cf40ee949
 msgid "Prerequisites"
 msgstr ""
 
 #: ../../networking/external_firewalls_and_load_balancers.rst:430
-# 0c697f756785488aaa591aa8b9a921cc
 msgid "Before you configure an AutoScale rule, consider the following:"
 msgstr ""
 
 #: ../../networking/external_firewalls_and_load_balancers.rst:432
-# 8229cf3ea2d24a22bc9707f8f142ca5e
 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 ""
 
 #: ../../networking/external_firewalls_and_load_balancers.rst:437
-# a3b170baceb44749ba1bc8c05a2d5b1c
 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 ""
 
 #: ../../networking/external_firewalls_and_load_balancers.rst:441
-# df32d04c33ca462ea54e7d716b2d8ffe
 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 ""
 
 #: ../../networking/external_firewalls_and_load_balancers.rst:446
-# e416b95063a0497fa2b7ca6430c0957c
 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 ""
 
 #: ../../networking/external_firewalls_and_load_balancers.rst:456
-# 0ac0707e74464bd0840f60e335716a25
 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 ""
 
 #: ../../networking/external_firewalls_and_load_balancers.rst:464
-# f8d93cd584a54fd8b2a72143d4107323
 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 ""
 
 #: ../../networking/external_firewalls_and_load_balancers.rst:468
-# f4e671d2a1814ee7936944319291f882
 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 ""
 
 #: ../../networking/external_firewalls_and_load_balancers.rst:473
-# 1def24ca3fcf4a9984043a4339307137
 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 ""
 
 #: ../../networking/external_firewalls_and_load_balancers.rst:480
-# d722fd21fbb64e1f8fe5c04b72d39a29
 msgid "Configuration"
 msgstr ""
 
 #: ../../networking/external_firewalls_and_load_balancers.rst:482
-# aa34165bbbed4360bb6cebfc7b978d91
 msgid "Specify the following:"
 msgstr ""
 
 #: ../../networking/external_firewalls_and_load_balancers.rst:484
-# 306046475ddb4e789bc88bc1633cdc73
 msgid "|autoscaleateconfig.png|"
 msgstr ""
 
 #: ../../networking/external_firewalls_and_load_balancers.rst:486
-# 951132877c0f4870b67560ae8035c8eb
 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 ""
 
 #: ../../networking/external_firewalls_and_load_balancers.rst:494
-# 313bdbb8a05e46239d80664ae76a92cf
 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 ""
 
 #: ../../networking/external_firewalls_and_load_balancers.rst:500
-# cd0d1d8ce17d439eb9c360d182e61bc0
 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 ""
 
 #: ../../networking/external_firewalls_and_load_balancers.rst:508
-# b883f060ac0a4b669952542845307113
 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 ""
 
 #: ../../networking/external_firewalls_and_load_balancers.rst:518
-# 1062b529c80542fe9f49822dc8e1226b
 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 ""
 
 #: ../../networking/external_firewalls_and_load_balancers.rst:523
-# 2f6f81ae0f294d00be1d4501c00d3ef4
 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 ""
 
 #: ../../networking/external_firewalls_and_load_balancers.rst:529
-# 80e14b2eba9f4b31bf0f73a8fb4665ac
 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 ""
 
 #: ../../networking/external_firewalls_and_load_balancers.rst:537
-# c05f5503e8994d1bbe38126fc1652574
 msgid "Specify the following scale-up and scale-down policies:"
 msgstr ""
 
 #: ../../networking/external_firewalls_and_load_balancers.rst:539
-# 8b8ee965cf5f45e4a993ef5a61584ee7
 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 ""
 
 #: ../../networking/external_firewalls_and_load_balancers.rst:544
-# aef0e1b396cc4f4aa88ea919926bc457
 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 ""
 
 #: ../../networking/external_firewalls_and_load_balancers.rst:551
-# e13329c9be684765967ad40f1ed75b4e
 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 ""
 
 #: ../../networking/external_firewalls_and_load_balancers.rst:555
-# 736606eaa3ac4622b52ed0ab0545ba37
 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 ""
 
 #: ../../networking/external_firewalls_and_load_balancers.rst:559
-# e74122a065ed4373a7c1291eb1291e64
 msgid "**Add**: Click Add to add the condition."
 msgstr ""
 
 #: ../../networking/external_firewalls_and_load_balancers.rst:561
-# 7d05f0a9ea384a5790999dfcd7fd3647
 msgid "Additionally, if you want to configure the advanced settings, click Show advanced settings, and specify the following:"
 msgstr ""
 
 #: ../../networking/external_firewalls_and_load_balancers.rst:564
-# 9e8ccf2af53541eea6450c116ba10b0a
 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 ""
 
 #: ../../networking/external_firewalls_and_load_balancers.rst:569
-# 9a0a8077043d427ba02f39207e648c16
 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 ""
 
 #: ../../networking/external_firewalls_and_load_balancers.rst:576
-# d562af8950534ba78cfad860812c91af
 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 ""
 
 #: ../../networking/external_firewalls_and_load_balancers.rst:582
-# b74500ed7cdc4d5e984c9d01a17d6cae
 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 ""
 
 #: ../../networking/external_firewalls_and_load_balancers.rst:589
-# 6e921b5c683943bf8e306cb4cd731b76
 msgid "**Disk Offerings**: A predefined set of disk size for primary data storage."
 msgstr ""
 
 #: ../../networking/external_firewalls_and_load_balancers.rst:592
-# 8eeeb8c4bf1749e6b405081fce9318ca
 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 ""
 
 #: ../../networking/external_firewalls_and_load_balancers.rst:596
-# 63d93ca18c5245e3aa630d743d5b1fff
 msgid "**SNMP Port**: The port number on which the SNMP agent that run on the provisioned VMs is listening. Default port is 161."
 msgstr ""
 
 #: ../../networking/external_firewalls_and_load_balancers.rst:599
-# 8e4ead8319ea470ba2e3a6183acf7ce2
 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 ""
 
 #: ../../networking/external_firewalls_and_load_balancers.rst:604
-# c5ab8b8578de4f5b8e2aa37c414525aa
 msgid "**Apply**: Click Apply to create the AutoScale configuration."
 msgstr ""
 
 #: ../../networking/external_firewalls_and_load_balancers.rst:608
-# 3d6ec42e045a4082a8798bec5791982a
 msgid "Disabling and Enabling an AutoScale Configuration"
 msgstr ""
 
 #: ../../networking/external_firewalls_and_load_balancers.rst:610
-# ec5c758cc62a40e587a4b6c4fddb434f
 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 ""
 
 #: ../../networking/external_firewalls_and_load_balancers.rst:616
-# 0a60f936b205455c98dceed77b11df3c
 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 ""
 
 #: ../../networking/external_firewalls_and_load_balancers.rst:626
-# f4bb71e85bd344b89fdcb3239a0f51f8
 msgid "Updating an AutoScale Configuration"
 msgstr ""
 
 #: ../../networking/external_firewalls_and_load_balancers.rst:628
-# 3bf60f14a73d43869794736b33b5aa5b
 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 ""
 
 #: ../../networking/external_firewalls_and_load_balancers.rst:633
-# f9665a6811b3410ba434ca755c6451f6
 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 ""
 
 #: ../../networking/external_firewalls_and_load_balancers.rst:639
-# debb34a5766f45ca8759a81e6401dc05
 msgid "Runtime Considerations"
 msgstr ""
 
 #: ../../networking/external_firewalls_and_load_balancers.rst:641
-# 57af5a07b00746d1b071d2eb6e80fea1
 msgid "An administrator should not assign a VM to a load balancing rule which is configured for AutoScale."
 msgstr ""
 
 #: ../../networking/external_firewalls_and_load_balancers.rst:644
-# 7df6035fc7ca442bbbb5d7bd0ea0428b
 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 ""
 
 #: ../../networking/external_firewalls_and_load_balancers.rst:651
-# 0eca9ec603bb4fc28eaabd868afa3e27
 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 ""
 

http://git-wip-us.apache.org/repos/asf/cloudstack-docs-admin/blob/a6b15cb9/source/locale/pot/networking/global_server_load_balancing.pot
----------------------------------------------------------------------
diff --git a/source/locale/pot/networking/global_server_load_balancing.pot b/source/locale/pot/networking/global_server_load_balancing.pot
index e9acc45..d5fdae5 100644
--- a/source/locale/pot/networking/global_server_load_balancing.pot
+++ b/source/locale/pot/networking/global_server_load_balancing.pot
@@ -1,14 +1,14 @@
 # SOME DESCRIPTIVE TITLE.
-# Copyright (C) 
+# Copyright (C) 2016, Apache Software Foundation
 # This file is distributed under the same license as the Apache CloudStack Administration Documentation package.
 # FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
 #
 #, fuzzy
 msgid ""
 msgstr ""
-"Project-Id-Version: Apache CloudStack Administration Documentation 4\n"
+"Project-Id-Version: Apache CloudStack Administration Documentation 4.8\n"
 "Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2014-06-30 12:52+0200\n"
+"POT-Creation-Date: 2016-08-22 13:55+0200\n"
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
 "Language-Team: LANGUAGE <LL@li.org>\n"
@@ -17,557 +17,443 @@ msgstr ""
 "Content-Transfer-Encoding: 8bit\n"
 
 #: ../../networking/global_server_load_balancing.rst:18
-# dcd5b9f2eedc4d1682f64e174cd2cef7
 msgid "Global Server Load Balancing Support"
 msgstr ""
 
 #: ../../networking/global_server_load_balancing.rst:20
-# 6cf6d74b4dde4e5fb05f41ae52822a4a
 msgid "CloudStack supports Global Server Load Balancing (GSLB) functionalities to provide business continuity, and enable seamless resource movement within a CloudStack environment. CloudStack achieve this by extending its functionality of integrating with NetScaler Application Delivery Controller (ADC), which also provides various GSLB capabilities, such as disaster recovery and load balancing. The DNS redirection technique is used to achieve GSLB in CloudStack."
 msgstr ""
 
 #: ../../networking/global_server_load_balancing.rst:28
-# 7396fe0f91a94dcf8d73474623b3c975
 msgid "In order to support this functionality, region level services and service provider are introduced. A new service 'GSLB' is introduced as a region level service. The GSLB service provider is introduced that will provider the GSLB service. Currently, NetScaler is the supported GSLB provider in CloudStack. GSLB functionality works in an Active-Active data center environment."
 msgstr ""
 
 #: ../../networking/global_server_load_balancing.rst:37
-# c1b8feb53b76438681b08acf77c25440
 msgid "About Global Server Load Balancing"
 msgstr ""
 
 #: ../../networking/global_server_load_balancing.rst:39
-# e03a6a1a69b640308c22260d5737533b
 msgid "Global Server Load Balancing (GSLB) is an extension of load balancing functionality, which is highly efficient in avoiding downtime. Based on the nature of deployment, GSLB represents a set of technologies that is used for various purposes, such as load sharing, disaster recovery, performance, and legal obligations. With GSLB, workloads can be distributed across multiple data centers situated at geographically separated locations. GSLB can also provide an alternate location for accessing a resource in the event of a failure, or to provide a means of shifting traffic easily to simplify maintenance, or both."
 msgstr ""
 
 #: ../../networking/global_server_load_balancing.rst:51
-# ba32175058a043b081e7045d04a34334
 msgid "Components of GSLB"
 msgstr ""
 
 #: ../../networking/global_server_load_balancing.rst:53
-# 8282609b9ff24cd980a31ea858744fba
 msgid "A typical GSLB environment is comprised of the following components:"
 msgstr ""
 
 #: ../../networking/global_server_load_balancing.rst:55
-# 0c4b0b08a37346789443744bef960c26
 msgid "**GSLB Site**: In CloudStack terminology, GSLB sites are represented by zones that are mapped to data centers, each of which has various network appliances. Each GSLB site is managed by a NetScaler appliance that is local to that site. Each of these appliances treats its own site as the local site and all other sites, managed by other appliances, as remote sites. It is the central entity in a GSLB deployment, and is represented by a name and an IP address."
 msgstr ""
 
 #: ../../networking/global_server_load_balancing.rst:63
-# e6f8317f00944a5faf27bf059374e211
 msgid "**GSLB Services**: A GSLB service is typically represented by a load balancing or content switching virtual server. In a GSLB environment, you can have a local as well as remote GSLB services. A local GSLB service represents a local load balancing or content switching virtual server. A remote GSLB service is the one configured at one of the other sites in the GSLB setup. At each site in the GSLB setup, you can create one local GSLB service and any number of remote GSLB services."
 msgstr ""
 
 #: ../../networking/global_server_load_balancing.rst:72
-# 0d6074d67e874afaafcced32aa2dcad8
 msgid "**GSLB Virtual Servers**: A GSLB virtual server refers to one or more GSLB services and balances traffic between traffic across the VMs in multiple zones by using the CloudStack functionality. It evaluates the configured GSLB methods or algorithms to select a GSLB service to which to send the client requests. One or more virtual servers from different zones are bound to the GSLB virtual server. GSLB virtual server does not have a public IP associated with it, instead it will have a FQDN DNS name."
 msgstr ""
 
 #: ../../networking/global_server_load_balancing.rst:81
-# 25269a15ffaf4c48880b969ed8e8ff0b
 msgid "**Load Balancing or Content Switching Virtual Servers**: According to Citrix NetScaler terminology, a load balancing or content switching virtual server represents one or many servers on the local network. Clients send their requests to the load balancing or content switching virtual server's virtual IP (VIP) address, and the virtual server balances the load across the local servers. After a GSLB virtual server selects a GSLB service representing either a local or a remote load balancing or content switching virtual server, the client sends the request to that virtual server's VIP address."
 msgstr ""
 
 #: ../../networking/global_server_load_balancing.rst:91
-# a4ae12735c574a18995202afba84a585
 msgid "**DNS VIPs**: DNS virtual IP represents a load balancing DNS virtual server on the GSLB service provider. The DNS requests for domains for which the GSLB service provider is authoritative can be sent to a DNS VIP."
 msgstr ""
 
 #: ../../networking/global_server_load_balancing.rst:96
-# 18dae232ea054aad8beb56723f2e9d6d
 msgid "**Authoritative DNS**: ADNS (Authoritative Domain Name Server) is a service that provides actual answer to DNS queries, such as web site IP address. In a GSLB environment, an ADNS service responds only to DNS requests for domains for which the GSLB service provider is authoritative. When an ADNS service is configured, the service provider owns that IP address and advertises it. When you create an ADNS service, the NetScaler responds to DNS queries on the configured ADNS service IP and port."
 msgstr ""
 
 #: ../../networking/global_server_load_balancing.rst:107
-# 9efb5a6ae20d45eab31e7fe7ffc87eab
 msgid "How Does GSLB Works in CloudStack?"
 msgstr ""
 
 #: ../../networking/global_server_load_balancing.rst:109
-# daac6a57d97c4caebd3fa5d2f5f27324
 msgid "Global server load balancing is used to manage the traffic flow to a web site hosted on two separate zones that ideally are in different geographic locations. The following is an illustration of how GLSB functionality is provided in CloudStack: An organization, xyztelco, has set up a public cloud that spans two zones, Zone-1 and Zone-2, across geographically separated data centers that are managed by CloudStack. Tenant-A of the cloud launches a highly available solution by using xyztelco cloud. For that purpose, they launch two instances each in both the zones: VM1 and VM2 in Zone-1 and VM5 and VM6 in Zone-2. Tenant-A acquires a public IP, IP-1 in Zone-1, and configures a load balancer rule to load balance the traffic between VM1 and VM2 instances. CloudStack orchestrates setting up a virtual server on the LB service provider in Zone-1. Virtual server 1 that is set up on the LB service provider in Zone-1 represents a publicly accessible virtual server that client reaches at I
 P-1. The client traffic to virtual server 1 at IP-1 will be load balanced across VM1 and VM2 instances."
 msgstr ""
 
 #: ../../networking/global_server_load_balancing.rst:126
-# ab85065c7a794a62bb64bb4d17ff62c9
 msgid "Tenant-A acquires another public IP, IP-2 in Zone-2 and sets up a load balancer rule to load balance the traffic between VM5 and VM6 instances. Similarly in Zone-2, CloudStack orchestrates setting up a virtual server on the LB service provider. Virtual server 2 that is setup on the LB service provider in Zone-2 represents a publicly accessible virtual server that client reaches at IP-2. The client traffic that reaches virtual server 2 at IP-2 is load balanced across VM5 and VM6 instances. At this point Tenant-A has the service enabled in both the zones, but has no means to set up a disaster recovery plan if one of the zone fails. Additionally, there is no way for Tenant-A to load balance the traffic intelligently to one of the zones based on load, proximity and so on. The cloud administrator of xyztelco provisions a GSLB service provider to both the zones. A GSLB provider is typically an ADC that has the ability to act as an ADNS (Authoritative Domain Name Server) and has the
  mechanism to monitor health of virtual servers both at local and remote sites. The cloud admin enables GSLB as a service to the tenants that use zones 1 and 2."
 msgstr ""
 
 #: ../../networking/global_server_load_balancing.rst:144
-# 16e02bcf2da14fd48ec4af740ccfc445
 msgid "|gslb.png|"
 msgstr ""
 
 #: ../../networking/global_server_load_balancing.rst:146
-# 7f93cb0f9f2e4bc58cfc7f308c019bda
 msgid "Tenant-A wishes to leverage the GSLB service provided by the xyztelco cloud. Tenant-A configures a GSLB rule to load balance traffic across virtual server 1 at Zone-1 and virtual server 2 at Zone-2. The domain name is provided as A.xyztelco.com. CloudStack orchestrates setting up GSLB virtual server 1 on the GSLB service provider at Zone-1. CloudStack binds virtual server 1 of Zone-1 and virtual server 2 of Zone-2 to GLSB virtual server 1. GSLB virtual server 1 is configured to start monitoring the health of virtual server 1 and 2 in Zone-1. CloudStack will also orchestrate setting up GSLB virtual server 2 on GSLB service provider at Zone-2. CloudStack will bind virtual server 1 of Zone-1 and virtual server 2 of Zone-2 to GLSB virtual server 2. GSLB virtual server 2 is configured to start monitoring the health of virtual server 1 and 2. CloudStack will bind the domain A.xyztelco.com to both the GSLB virtual server 1 and 2. At this point, Tenant-A service will be globally reac
 hable at A.xyztelco.com. The private DNS server for the domain xyztelcom.com is configured by the admin out-of-band to resolve the domain A.xyztelco.com to the GSLB providers at both the zones, which are configured as ADNS for the domain A.xyztelco.com. A client when sends a DNS request to resolve A.xyztelcom.com, will eventually get DNS delegation to the address of GSLB providers at zone 1 and 2. A client DNS request will be received by the GSLB provider. The GSLB provider, depending on the domain for which it needs to resolve, will pick up the GSLB virtual server associated with the domain. Depending on the health of the virtual servers being load balanced, DNS request for the domain will be resolved to the public IP associated with the selected virtual server."
 msgstr ""
 
 #: ../../networking/global_server_load_balancing.rst:175
-# dcd79b8e29a442d098cb8090a4527144
 msgid "Configuring GSLB"
 msgstr ""
 
 #: ../../networking/global_server_load_balancing.rst:177
-# af3fb04e787447d9976ebb989e847e3d
 msgid "To configure a GSLB deployment, you must first configure a standard load balancing setup for each zone. This enables you to balance load across the different servers in each zone in the region. Then on the NetScaler side, configure both NetScaler appliances that you plan to add to each zone as authoritative DNS (ADNS) servers. Next, create a GSLB site for each zone, configure GSLB virtual servers for each site, create GLSB services, and bind the GSLB services to the GSLB virtual servers. Finally, bind the domain to the GSLB virtual servers. The GSLB configurations on the two appliances at the two different zones are identical, although each sites load-balancing configuration is specific to that site."
 msgstr ""
 
 #: ../../networking/global_server_load_balancing.rst:189
-# f12e3e8dd3114cc6ab5febf7d770620a
 msgid "Perform the following as a cloud administrator. As per the example given above, the administrator of xyztelco is the one who sets up GSLB:"
 msgstr ""
 
 #: ../../networking/global_server_load_balancing.rst:192
-# 9579cd3756414bb59e03052c3c4807de
 msgid "In the cloud.dns.name global parameter, specify the DNS name of your tenant's cloud that make use of the GSLB service."
 msgstr ""
 
 #: ../../networking/global_server_load_balancing.rst:195
-# e675df400e4c40079a4b8ac2c3a3a007
 msgid "On the NetScaler side, configure GSLB as given in `Configuring Global Server Load Balancing (GSLB) <http://support.citrix.com/proddocs/topic/netscaler-traffic-management-10-map/ns-gslb-config-con.html>`_:"
 msgstr ""
 
 #: ../../networking/global_server_load_balancing.rst:199
-# 8366d0a33b5d4328b32668eee7db43a7
 msgid "Configuring a standard load balancing setup."
 msgstr ""
 
 #: ../../networking/global_server_load_balancing.rst:201
-# 652a6e0d3f25435bad8a3a37ff14f6de
 msgid "Configure Authoritative DNS, as explained in `Configuring an Authoritative DNS Service <http://support.citrix.com/proddocs/topic/netscaler-traffic-management-10-map/ns-gslb-config-adns-svc-tsk.html>`_."
 msgstr ""
 
 #: ../../networking/global_server_load_balancing.rst:205
-# eb1be7170a664c05818eea4cebcd652c
 msgid "Configure a GSLB site with site name formed from the domain name details."
 msgstr ""
 
 #: ../../networking/global_server_load_balancing.rst:208
-# af0e9c7b27f545b9a2532edf6109ddf3
 msgid "Configure a GSLB site with the site name formed from the domain name."
 msgstr ""
 
 #: ../../networking/global_server_load_balancing.rst:211
-# 6c3c9b0f00314c219b51b9ea4a817b37
 msgid "As per the example given above, the site names are A.xyztelco.com and B.xyztelco.com."
 msgstr ""
 
 #: ../../networking/global_server_load_balancing.rst:214
-# 8bc45e9126194d24824f0e0e2d92ca1b
 msgid "For more information, see `Configuring a Basic GSLB Site <http://support.citrix.com/proddocs/topic/netscaler-traffic-management-10-map/ns-gslb-config-basic-site-tsk.html>`_."
 msgstr ""
 
 #: ../../networking/global_server_load_balancing.rst:217
-# 7276993a8c1f4f089886c5bfce5f4f6e
 msgid "Configure a GSLB virtual server."
 msgstr ""
 
 #: ../../networking/global_server_load_balancing.rst:219
-# 8d0c82c139184d3992209af4d2e54a6c
 msgid "For more information, see `Configuring a GSLB Virtual Server <http://support.citrix.com/proddocs/topic/netscaler-traffic-management-10-map/ns-gslb-config-vsvr-tsk.html>`_."
 msgstr ""
 
 #: ../../networking/global_server_load_balancing.rst:222
-# 7db75bd72fa44709ab7adb82ba26f318
 msgid "Configure a GSLB service for each virtual server."
 msgstr ""
 
 #: ../../networking/global_server_load_balancing.rst:224
-# 7dd4d9aa1c394ed6859a00b0331f3e5b
 msgid "For more information, see `Configuring a GSLB Service <http://support.citrix.com/proddocs/topic/netscaler-traffic-management-10-map/ns-gslb-config-svc-tsk.html>`_."
 msgstr ""
 
 #: ../../networking/global_server_load_balancing.rst:227
-# 30745365545f4cbca1a5ff6fa73a495f
 msgid "Bind the GSLB services to the GSLB virtual server."
 msgstr ""
 
 #: ../../networking/global_server_load_balancing.rst:229
-# f5c32c764b0c44cc9b430cd2c74f5a0b
 msgid "For more information, see `Binding GSLB Services to a GSLB Virtual Server <http://support.citrix.com/proddocs/topic/netscaler-traffic-management-10-map/ns-gslb-bind-svc-vsvr-tsk.html>`_."
 msgstr ""
 
 #: ../../networking/global_server_load_balancing.rst:232
-# 74f55b2693404f1d8b46b1960f0987db
 msgid "Bind domain name to GSLB virtual server. Domain name is obtained from the domain details."
 msgstr ""
 
 #: ../../networking/global_server_load_balancing.rst:235
-# 012a1ab7ff7b422995e21b6709b4c6b3
 msgid "For more information, see `Binding a Domain to a GSLB Virtual Server <http://support.citrix.com/proddocs/topic/netscaler-traffic-management-10-map/ns-gslb-bind-dom-vsvr-tsk.html>`_."
 msgstr ""
 
 #: ../../networking/global_server_load_balancing.rst:238
-# efe8d44a7dc84347bdc932507e0cf417
 msgid "In each zone that are participating in GSLB, add GSLB-enabled NetScaler device."
 msgstr ""
 
 #: ../../networking/global_server_load_balancing.rst:241
-# b4176a11b248487686fbfb80d484f72d
 msgid "For more information, see :ref:`enabling-gslb-in-ns`."
 msgstr ""
 
 #: ../../networking/global_server_load_balancing.rst:243
-# 8fc3da50593741b9863599aee89587e8
 msgid "As a domain administrator/ user perform the following:"
 msgstr ""
 
 #: ../../networking/global_server_load_balancing.rst:245
-# 8c1293eb2d3746e8abb219c5c4cb7290
 msgid "Add a GSLB rule on both the sites."
 msgstr ""
 
 #: ../../networking/global_server_load_balancing.rst:247
-# a78f47a38a364e859b24e482f8eab174
 msgid "See \":ref:`adding-gslb-rule`\"."
 msgstr ""
 
 #: ../../networking/global_server_load_balancing.rst:249
-# 17e3b59ea95e4eb39b1290cea67e4801
 msgid "Assign load balancer rules."
 msgstr ""
 
 #: ../../networking/global_server_load_balancing.rst:251
-# d37f5840c4d34fa9aa990a0bb0610af9
 msgid "See \":ref:`assigning-lb-rule-gslb`\"."
 msgstr ""
 
 #: ../../networking/global_server_load_balancing.rst:255
-# 2553447c986746b582a9f8b495396c3b
 msgid "Prerequisites and Guidelines"
 msgstr ""
 
 #: ../../networking/global_server_load_balancing.rst:257
-# 8627b5c519f04c4bb75b82af96f25418
 msgid "The GSLB functionality is supported both Basic and Advanced zones."
 msgstr ""
 
 #: ../../networking/global_server_load_balancing.rst:259
-# c2b5f208b13f4b07b6755c0a53fa1104
 msgid "GSLB is added as a new network service."
 msgstr ""
 
 #: ../../networking/global_server_load_balancing.rst:261
-# 3c6e0da5ecd148d599a35191c7e92678
 msgid "GSLB service provider can be added to a physical network in a zone."
 msgstr ""
 
 #: ../../networking/global_server_load_balancing.rst:263
-# 6c159f1bc2224bb2b35dd03ec51bc6b1
 msgid "The admin is allowed to enable or disable GSLB functionality at region level."
 msgstr ""
 
 #: ../../networking/global_server_load_balancing.rst:266
-# 6367e49f50d0418c92b7b6fc7cc91a39
 msgid "The admin is allowed to configure a zone as GSLB capable or enabled."
 msgstr ""
 
 #: ../../networking/global_server_load_balancing.rst:268
-# a66b5c6d51534ab492d244d518221776
 msgid "A zone shall be considered as GSLB capable only if a GSLB service provider is provisioned in the zone."
 msgstr ""
 
 #: ../../networking/global_server_load_balancing.rst:271
-# 0ea762e8718b465eaacf40a6118c8f7f
 msgid "When users have VMs deployed in multiple availability zones which are GSLB enabled, they can use the GSLB functionality to load balance traffic across the VMs in multiple zones."
 msgstr ""
 
 #: ../../networking/global_server_load_balancing.rst:275
-# ed2130b4027e41e3833699a89ff82708
 msgid "The users can use GSLB to load balance across the VMs across zones in a region only if the admin has enabled GSLB in that region."
 msgstr ""
 
 #: ../../networking/global_server_load_balancing.rst:278
-# 1b374fea614b459eb39cfbe4f20478c9
 msgid "The users can load balance traffic across the availability zones in the same region or different regions."
 msgstr ""
 
 #: ../../networking/global_server_load_balancing.rst:281
-# 62da6f878356420f9becc6fffbe1ae6d
 msgid "The admin can configure DNS name for the entire cloud."
 msgstr ""
 
 #: ../../networking/global_server_load_balancing.rst:283
-# 799fe9490296493e9d86d0ea8cdc9297
 msgid "The users can specify an unique name across the cloud for a globally load balanced service. The provided name is used as the domain name under the DNS name associated with the cloud."
 msgstr ""
 
 #: ../../networking/global_server_load_balancing.rst:287
-# 1d6c20de63954971a720227985a74433
 msgid "The user-provided name along with the admin-provided DNS name is used to produce a globally resolvable FQDN for the globally load balanced service of the user. For example, if the admin has configured xyztelco.com as the DNS name for the cloud, and user specifies 'foo' for the GSLB virtual service, then the FQDN name of the GSLB virtual service is foo.xyztelco.com."
 msgstr ""
 
 #: ../../networking/global_server_load_balancing.rst:294
-# a7817e36fe2c4ea58737d1a5ae3db30b
 msgid "While setting up GSLB, users can select a load balancing method, such as round robin, for using across the zones that are part of GSLB."
 msgstr ""
 
 #: ../../networking/global_server_load_balancing.rst:297
-# 971bcd7f3cf24bbbb424a020cc7c06a4
 msgid "The user shall be able to set weight to zone-level virtual server. Weight shall be considered by the load balancing method for distributing the traffic."
 msgstr ""
 
 #: ../../networking/global_server_load_balancing.rst:301
-# 6f3d31dca71d4b608fa90d1eb73ecee2
 msgid "The GSLB functionality shall support session persistence, where series of client requests for particular domain name is sent to a virtual server on the same zone."
 msgstr ""
 
 #: ../../networking/global_server_load_balancing.rst:305
-# bfaf6196eae343259864ac2443ff5746
 msgid "Statistics is collected from each GSLB virtual server."
 msgstr ""
 
 #: ../../networking/global_server_load_balancing.rst:311
-# d2f3468cd4ac44d58c53e731e50e35dd
 msgid "Enabling GSLB in NetScaler"
 msgstr ""
 
 #: ../../networking/global_server_load_balancing.rst:313
-# d51d618416764b5c843fc13bfd2dfa6d
 msgid "In each zone, add GSLB-enabled NetScaler device for load balancing."
 msgstr ""
 
 #: ../../networking/global_server_load_balancing.rst:315
-# 91d1d3b496c34b179f0b865500b6bf93
 msgid "Log in as administrator to the CloudStack UI."
 msgstr ""
 
 #: ../../networking/global_server_load_balancing.rst:317
-# cc1ae38bffd84c058812510e8495b73f
 msgid "In the left navigation bar, click Infrastructure."
 msgstr ""
 
 #: ../../networking/global_server_load_balancing.rst:319
-# 46ba7c7f81d04aa78f0c04d3d045bc8a
 msgid "In Zones, click View More."
 msgstr ""
 
 #: ../../networking/global_server_load_balancing.rst:321
-# 1feb8d2e09014d9989264c48ece8fc81
 msgid "Choose the zone you want to work with."
 msgstr ""
 
 #: ../../networking/global_server_load_balancing.rst:323
-# 82a50383b1124be48db8d0c5721e9f13
 msgid "Click the Physical Network tab, then click the name of the physical network."
 msgstr ""
 
 #: ../../networking/global_server_load_balancing.rst:326
-# 75224089389e4bee8e89a1caf1dc5880
 msgid "In the Network Service Providers node of the diagram, click Configure."
 msgstr ""
 
 #: ../../networking/global_server_load_balancing.rst:329
-# 410a9b626bf9412a9f482c2df1aac784
 msgid "You might have to scroll down to see this."
 msgstr ""
 
 #: ../../networking/global_server_load_balancing.rst:331
-# 1d32a851fb92436c8e045ccc828641f4
 msgid "Click NetScaler."
 msgstr ""
 
 #: ../../networking/global_server_load_balancing.rst:333
-# af72e8614fc44c60af3004624dba03b1
 msgid "Click Add NetScaler device and provide the following:"
 msgstr ""
 
 #: ../../networking/global_server_load_balancing.rst:335
-# 6290f4f42d054ac28661b16c5366b62f
 msgid "For NetScaler:"
 msgstr ""
 
 #: ../../networking/global_server_load_balancing.rst:337
-# 8e09b55d68a849d089029f2c893e3e97
 msgid "**IP Address**: The IP address of the SDX."
 msgstr ""
 
 #: ../../networking/global_server_load_balancing.rst:339
-# 9b9b4165d2ee4e64b3b0b04390702686
 msgid "**Username/Password**: The authentication credentials to access the device. CloudStack uses these credentials to access the device."
 msgstr ""
 
 #: ../../networking/global_server_load_balancing.rst:343
-# 212ab71ac16a49309da99e2870717faa
 msgid "**Type**: The type of device that is being added. It could be F5 Big Ip Load Balancer, NetScaler VPX, NetScaler MPX, or NetScaler SDX. For a comparison of the NetScaler types, see the CloudStack Administration Guide."
 msgstr ""
 
 #: ../../networking/global_server_load_balancing.rst:348
-# 3d72c6cb5cbb49418002a5e3acf1617c
 msgid "**Public interface**: Interface of device that is configured to be part of the public network."
 msgstr ""
 
 #: ../../networking/global_server_load_balancing.rst:351
-# 5bbed919dc2c45008af4312d028cfbd7
 msgid "**Private interface**: Interface of device that is configured to be part of the private network."
 msgstr ""
 
 #: ../../networking/global_server_load_balancing.rst:354
-# fb82ba2e06e34aaf9ab8e8fa8362b43d
 msgid "**GSLB service**: Select this option."
 msgstr ""
 
 #: ../../networking/global_server_load_balancing.rst:356
-# 8a1e3ad262934da086878740aefca5fc
 msgid "**GSLB service Public IP**: The public IP address of the NAT translator for a GSLB service that is on a private network."
 msgstr ""
 
 #: ../../networking/global_server_load_balancing.rst:359
-# 5ca3fc19dd8e4706872b9e3af0652c2f
 msgid "**GSLB service Private IP**: The private IP of the GSLB service."
 msgstr ""
 
 #: ../../networking/global_server_load_balancing.rst:361
-# 8f1a8fd9ec814e02970f7edf85c8fad1
 msgid "**Number of Retries**. Number of times to attempt a command on the device before considering the operation failed. Default is 2."
 msgstr ""
 
 #: ../../networking/global_server_load_balancing.rst:364
-# 2416b7a9e5fa43fdb27834cb7e46253b
 msgid "**Capacity**: The number of networks the device can handle."
 msgstr ""
 
 #: ../../networking/global_server_load_balancing.rst:366
-# c9166740fb2747a7abd4ae6c0851aabc
 msgid "**Dedicated**: When marked as dedicated, this device will be dedicated to a single account. When Dedicated is checked, the value in the Capacity field has no significance implicitly, its value is 1."
 msgstr ""
 
 #: ../../networking/global_server_load_balancing.rst:371
-# e7f874eb36ba4cd380f7a50d5bff8909
 msgid "Click OK."
 msgstr ""
 
 #: ../../networking/global_server_load_balancing.rst:377
-# d1556618bd5d4d18862c048d52694dd4
 msgid "Adding a GSLB Rule"
 msgstr ""
 
 #: ../../networking/global_server_load_balancing.rst:379
 #: ../../networking/global_server_load_balancing.rst:423
-# c06bbbd0cb824ecc8ef3d7956571f739
-# 2b618c03ffb14afb99d7e63813820288
 msgid "Log in to the CloudStack UI as a domain administrator or user."
 msgstr ""
 
 #: ../../networking/global_server_load_balancing.rst:381
 #: ../../networking/global_server_load_balancing.rst:425
-# 3b04d23a46774662bbca98318323a71e
-# 62eb7d6a5d9b4256bde0fcafb9f42b7f
 msgid "In the left navigation pane, click Region."
 msgstr ""
 
 #: ../../networking/global_server_load_balancing.rst:383
 #: ../../networking/global_server_load_balancing.rst:427
-# 940f5610d0484910bf9e9ba31728be30
-# 581952b854514ed78884cc712ee4ec94
 msgid "Select the region for which you want to create a GSLB rule."
 msgstr ""
 
 #: ../../networking/global_server_load_balancing.rst:385
 #: ../../networking/global_server_load_balancing.rst:429
-# fc1d362cc95a4668b2a24c7c0f488348
-# 8519e9d4ad6d46989865460e20b186b6
 msgid "In the Details tab, click View GSLB."
 msgstr ""
 
 #: ../../networking/global_server_load_balancing.rst:387
-# f59a742f9f1b4f37b6f0bc0b062028d6
 msgid "Click Add GSLB."
 msgstr ""
 
 #: ../../networking/global_server_load_balancing.rst:389
-# ca546577015a45af8ddcdc3d2ad22f3a
 msgid "The Add GSLB page is displayed as follows:"
 msgstr ""
 
 #: ../../networking/global_server_load_balancing.rst:391
-# b0b6437c269342ff9099b6da9a6d5b9f
 msgid "|gslb-add.png|"
 msgstr ""
 
 #: ../../networking/global_server_load_balancing.rst:393
-# 767ce39d9a094fda85465381d3a93bad
 msgid "Specify the following:"
 msgstr ""
 
 #: ../../networking/global_server_load_balancing.rst:395
-# affa9e59440b4f4e9e6428e887d12582
 msgid "**Name**: Name for the GSLB rule."
 msgstr ""
 
 #: ../../networking/global_server_load_balancing.rst:397
-# 82b72cbf0f8949fdab2de931138620c5
 msgid "**Description**: (Optional) A short description of the GSLB rule that can be displayed to users."
 msgstr ""
 
 #: ../../networking/global_server_load_balancing.rst:400
-# 8a6b82bfcd3a469c838315b17f4cd014
 msgid "**GSLB Domain Name**: A preferred domain name for the service."
 msgstr ""
 
 #: ../../networking/global_server_load_balancing.rst:402
-# ff5539d5f09f48bc80c0cf9dc83dcca0
 msgid "**Algorithm**: (Optional) The algorithm to use to load balance the traffic across the zones. The options are Round Robin, Least Connection, and Proximity."
 msgstr ""
 
 #: ../../networking/global_server_load_balancing.rst:406
-# b07f4dffc105427389bb8e089a71f9f0
 msgid "**Service Type**: The transport protocol to use for GSLB. The options are TCP and UDP."
 msgstr ""
 
 #: ../../networking/global_server_load_balancing.rst:409
-# 03ffe3890f5c4ea79836cfa0cc96986f
 msgid "**Domain**: (Optional) The domain for which you want to create the GSLB rule."
 msgstr ""
 
 #: ../../networking/global_server_load_balancing.rst:412
-# 5d0367f6567241968e5d6cac6f8ab34b
 msgid "**Account**: (Optional) The account on which you want to apply the GSLB rule."
 msgstr ""
 
 #: ../../networking/global_server_load_balancing.rst:415
 #: ../../networking/global_server_load_balancing.rst:439
-# 0161504934d746e39b05e6b50e264faf
-# 8c377e12f8494a009d5eed7e06824fe3
 msgid "Click OK to confirm."
 msgstr ""
 
 #: ../../networking/global_server_load_balancing.rst:421
-# f61c6b78ef4940129243771e21d78f4c
 msgid "Assigning Load Balancing Rules to GSLB"
 msgstr ""
 
 #: ../../networking/global_server_load_balancing.rst:431
-# 54cc7b916ceb420584020f5ff230b79c
 msgid "Select the desired GSLB."
 msgstr ""
 
 #: ../../networking/global_server_load_balancing.rst:433
-# 5e2a1bf3adfc41bab4bea1a489f9bda1
 msgid "Click view assigned load balancing."
 msgstr ""
 
 #: ../../networking/global_server_load_balancing.rst:435
-# 269db9ca8770495f9c5bc08491e61bc6
 msgid "Click assign more load balancing."
 msgstr ""
 
 #: ../../networking/global_server_load_balancing.rst:437
-# eceeb5fccdfa4cac904ef8fb945242c9
 msgid "Select the load balancing rule you have created for the zone."
 msgstr ""
 
 #: ../../networking/global_server_load_balancing.rst:443
-# d8792daad4a94b4589452d5b61f75cd9
 msgid "Known Limitation"
 msgstr ""
 
 #: ../../networking/global_server_load_balancing.rst:445
-# 7424fdf000e3479c910e72fbbaaa0169
 msgid "Currently, CloudStack does not support orchestration of services across the zones. The notion of services and service providers in region are to be introduced."
 msgstr ""
 

http://git-wip-us.apache.org/repos/asf/cloudstack-docs-admin/blob/a6b15cb9/source/locale/pot/networking/guest_ip_ranges.pot
----------------------------------------------------------------------
diff --git a/source/locale/pot/networking/guest_ip_ranges.pot b/source/locale/pot/networking/guest_ip_ranges.pot
index 2e32f45..5120a45 100644
--- a/source/locale/pot/networking/guest_ip_ranges.pot
+++ b/source/locale/pot/networking/guest_ip_ranges.pot
@@ -1,14 +1,14 @@
 # SOME DESCRIPTIVE TITLE.
-# Copyright (C) 
+# Copyright (C) 2016, Apache Software Foundation
 # This file is distributed under the same license as the Apache CloudStack Administration Documentation package.
 # FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
 #
 #, fuzzy
 msgid ""
 msgstr ""
-"Project-Id-Version: Apache CloudStack Administration Documentation 4\n"
+"Project-Id-Version: Apache CloudStack Administration Documentation 4.8\n"
 "Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2014-06-30 12:52+0200\n"
+"POT-Creation-Date: 2016-08-22 13:55+0200\n"
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
 "Language-Team: LANGUAGE <LL@li.org>\n"
@@ -17,17 +17,14 @@ msgstr ""
 "Content-Transfer-Encoding: 8bit\n"
 
 #: ../../networking/guest_ip_ranges.rst:18
-# c4f6e8eb1ed7428a8132309d84e4b1bf
 msgid "Guest IP Ranges"
 msgstr ""
 
 #: ../../networking/guest_ip_ranges.rst:20
-# ef6d3891253c4ed58a8a51c2f86b51dc
 msgid "The IP ranges for guest network traffic are set on a per-account basis by the user. This allows the users to configure their network in a fashion that will enable VPN linking between their guest network and their clients."
 msgstr ""
 
 #: ../../networking/guest_ip_ranges.rst:25
-# 943864c06f494d7ca4f4310246ba996a
 msgid "In shared networks in Basic zone and Security Group-enabled Advanced networks, you will have the flexibility to add multiple guest IP ranges from different subnets. You can add or remove one IP range at a time. For more information, see `\"About Multiple IP Ranges\" <#about-multiple-ip-ranges>`_."
 msgstr ""
 

http://git-wip-us.apache.org/repos/asf/cloudstack-docs-admin/blob/a6b15cb9/source/locale/pot/networking/guest_traffic.pot
----------------------------------------------------------------------
diff --git a/source/locale/pot/networking/guest_traffic.pot b/source/locale/pot/networking/guest_traffic.pot
index 4cb5bbb..b930282 100644
--- a/source/locale/pot/networking/guest_traffic.pot
+++ b/source/locale/pot/networking/guest_traffic.pot
@@ -1,14 +1,14 @@
 # SOME DESCRIPTIVE TITLE.
-# Copyright (C) 
+# Copyright (C) 2016, Apache Software Foundation
 # This file is distributed under the same license as the Apache CloudStack Administration Documentation package.
 # FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
 #
 #, fuzzy
 msgid ""
 msgstr ""
-"Project-Id-Version: Apache CloudStack Administration Documentation 4\n"
+"Project-Id-Version: Apache CloudStack Administration Documentation 4.8\n"
 "Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2014-06-30 12:52+0200\n"
+"POT-Creation-Date: 2016-08-22 13:55+0200\n"
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
 "Language-Team: LANGUAGE <LL@li.org>\n"
@@ -17,37 +17,30 @@ msgstr ""
 "Content-Transfer-Encoding: 8bit\n"
 
 #: ../../networking/guest_traffic.rst:18
-# 6a1d02b308ae4f228e4104aa95e39ee3
 msgid "Guest Traffic"
 msgstr ""
 
 #: ../../networking/guest_traffic.rst:20
-# 77e0128afe644aa9a04259e24cb22595
 msgid "A network can carry guest traffic only between VMs within one zone. Virtual machines in different zones cannot communicate with each other using their IP addresses; they must communicate with each other by routing through a public IP address."
 msgstr ""
 
 #: ../../networking/guest_traffic.rst:25
-# 79cb326a48f942949bf3dfe341a3664f
 msgid "See a typical guest traffic setup given below:"
 msgstr ""
 
 #: ../../networking/guest_traffic.rst:27
-# e0ac4742331840b89eef72912ffd2138
 msgid "|guest-traffic-setup.png|"
 msgstr ""
 
 #: ../../networking/guest_traffic.rst:29
-# 685689cd44444e13aefa015c58761ebb
 msgid "Typically, the Management Server automatically creates a virtual router for each network. A virtual router is a special virtual machine that runs on the hosts. Each virtual router in an isolated network has three network interfaces. If multiple public VLAN is used, the router will have multiple public interfaces. Its eth0 interface serves as the gateway for the guest traffic and has the IP address of 10.1.1.1. Its eth1 interface is used by the system to configure the virtual router. Its eth2 interface is assigned a public IP address for public traffic. If multiple public VLAN is used, the router will have multiple public interfaces."
 msgstr ""
 
 #: ../../networking/guest_traffic.rst:40
-# c07d5440a8e64d5b912e6e98e6f9d078
 msgid "The virtual router provides DHCP and will automatically assign an IP address for each guest VM within the IP range assigned for the network. The user can manually reconfigure guest VMs to assume different IP addresses."
 msgstr ""
 
 #: ../../networking/guest_traffic.rst:45
-# 360d9d124254479e85292973d6d8e7f9
 msgid "Source NAT is automatically configured in the virtual router to forward outbound traffic for all guest VMs"
 msgstr ""
 

http://git-wip-us.apache.org/repos/asf/cloudstack-docs-admin/blob/a6b15cb9/source/locale/pot/networking/inter_vlan_routing.pot
----------------------------------------------------------------------
diff --git a/source/locale/pot/networking/inter_vlan_routing.pot b/source/locale/pot/networking/inter_vlan_routing.pot
index d7b6b80..17ca4d9 100644
--- a/source/locale/pot/networking/inter_vlan_routing.pot
+++ b/source/locale/pot/networking/inter_vlan_routing.pot
@@ -1,14 +1,14 @@
 # SOME DESCRIPTIVE TITLE.
-# Copyright (C) 
+# Copyright (C) 2016, Apache Software Foundation
 # This file is distributed under the same license as the Apache CloudStack Administration Documentation package.
 # FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
 #
 #, fuzzy
 msgid ""
 msgstr ""
-"Project-Id-Version: Apache CloudStack Administration Documentation 4\n"
+"Project-Id-Version: Apache CloudStack Administration Documentation 4.8\n"
 "Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2014-06-30 12:52+0200\n"
+"POT-Creation-Date: 2016-08-22 13:55+0200\n"
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
 "Language-Team: LANGUAGE <LL@li.org>\n"
@@ -17,102 +17,82 @@ msgstr ""
 "Content-Transfer-Encoding: 8bit\n"
 
 #: ../../networking/inter_vlan_routing.rst:18
-# 536a6b6a19a04686832c0c8f3202472a
 msgid "About Inter-VLAN Routing (nTier Apps)"
 msgstr ""
 
 #: ../../networking/inter_vlan_routing.rst:20
-# 01903cae08524fb18fb51475e29cccc5
 msgid "Inter-VLAN Routing (nTier Apps) is the capability to route network traffic between VLANs. This feature enables you to build Virtual Private Clouds (VPC), an isolated segment of your cloud, that can hold multi-tier applications. These tiers are deployed on different VLANs that can communicate with each other. You provision VLANs to the tiers your create, and VMs can be deployed on different tiers. The VLANs are connected to a virtual router, which facilitates communication between the VMs. In effect, you can segment VMs by means of VLANs into different networks that can host multi-tier applications, such as Web, Application, or Database. Such segmentation by means of VLANs logically separate application VMs for higher security and lower broadcasts, while remaining physically connected to the same device."
 msgstr ""
 
 #: ../../networking/inter_vlan_routing.rst:33
-# d835d5a69985471085a5688b045c4e38
 msgid "This feature is supported on XenServer, KVM, and VMware hypervisors."
 msgstr ""
 
 #: ../../networking/inter_vlan_routing.rst:35
-# 7aecd1ac66b84f9cb92b03fea7d5edde
 msgid "The major advantages are:"
 msgstr ""
 
 #: ../../networking/inter_vlan_routing.rst:37
-# dca4c4be393c4d7bbcda75f49ffc8efc
 msgid "The administrator can deploy a set of VLANs and allow users to deploy VMs on these VLANs. A guest VLAN is randomly alloted to an account from a pre-specified set of guest VLANs. All the VMs of a certain tier of an account reside on the guest VLAN allotted to that account."
 msgstr ""
 
 #: ../../networking/inter_vlan_routing.rst:43
-# d5d8b41e126e4b38913d0cf7de1ec29d
 msgid "A VLAN allocated for an account cannot be shared between multiple accounts."
 msgstr ""
 
 #: ../../networking/inter_vlan_routing.rst:45
-# 4e04be2a6cef4fa8973d317232221018
 msgid "The administrator can allow users create their own VPC and deploy the application. In this scenario, the VMs that belong to the account are deployed on the VLANs allotted to that account."
 msgstr ""
 
 #: ../../networking/inter_vlan_routing.rst:49
-# 48018251e76046c4a606035de8d1b4d5
 msgid "Both administrators and users can create multiple VPCs. The guest network NIC is plugged to the VPC virtual router when the first VM is deployed in a tier."
 msgstr ""
 
 #: ../../networking/inter_vlan_routing.rst:53
-# cc50778ecfab43c38af3373511f47072
 msgid "The administrator can create the following gateways to send to or receive traffic from the VMs:"
 msgstr ""
 
 #: ../../networking/inter_vlan_routing.rst:56
-# 5d91169a83a5400b8408b6ce4ccb84f5
 msgid "**VPN Gateway**: For more information, see `\"Creating a VPN gateway for the VPC\" <#creating-a-vpn-gateway-for-the-vpc>`_."
 msgstr ""
 
 #: ../../networking/inter_vlan_routing.rst:59
-# 1f0ed1ecf964455ab40301bdf5ab2dc2
 msgid "**Public Gateway**: The public gateway for a VPC is added to the virtual router when the virtual router is created for VPC. The public gateway is not exposed to the end users. You are not allowed to list it, nor allowed to create any static routes."
 msgstr ""
 
 #: ../../networking/inter_vlan_routing.rst:64
-# b843201a793749bb924d48f21be04e09
 msgid "**Private Gateway**: For more information, see \":ref:`adding-priv-gw-vpc`\"."
 msgstr ""
 
 #: ../../networking/inter_vlan_routing.rst:66
-# a4ac63d4b99a4edd968087d0f622647a
 msgid "Both administrators and users can create various possible destinations-gateway combinations. However, only one gateway of each type can be used in a deployment."
 msgstr ""
 
 #: ../../networking/inter_vlan_routing.rst:70
-# 50735b7154a64b7880f5543c4792b1c0
 msgid "For example:"
 msgstr ""
 
 #: ../../networking/inter_vlan_routing.rst:72
-# bdd41dc64438436aac12d9f1c8d5a8bc
 msgid "**VLANs and Public Gateway**: For example, an application is deployed in the cloud, and the Web application VMs communicate with the Internet."
 msgstr ""
 
 #: ../../networking/inter_vlan_routing.rst:76
-# f2c3b70246534d5aabdd3954a25ba1eb
 msgid "**VLANs, VPN Gateway, and Public Gateway**: For example, an application is deployed in the cloud; the Web application VMs communicate with the Internet; and the database VMs communicate with the on-premise devices."
 msgstr ""
 
 #: ../../networking/inter_vlan_routing.rst:81
-# 7fb2fe01c3484b80a30d4c6edb0b5782
 msgid "The administrator can define Network Access Control List (ACL) on the virtual router to filter the traffic among the VLANs or between the Internet and a VLAN. You can define ACL based on CIDR, port range, protocol, type code (if ICMP protocol is selected) and Ingress/Egress type."
 msgstr ""
 
 #: ../../networking/inter_vlan_routing.rst:87
-# 95cd03acfa2948c682ec51eaf24346be
 msgid "The following figure shows the possible deployment scenarios of a Inter-VLAN setup:"
 msgstr ""
 
 #: ../../networking/inter_vlan_routing.rst:90
-# a9f3216208ba417681d8885848d2a414
 msgid "|mutltier.png|"
 msgstr ""
 
 #: ../../networking/inter_vlan_routing.rst:92
-# 785b1c5286424a3680f6ffa4fa40de5a
 msgid "To set up a multi-tier Inter-VLAN deployment, see \":ref:`configuring-vpc`\"."
 msgstr ""
 


Mime
View raw message