cloudstack-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From seb...@apache.org
Subject [7/8] Push tx/config and new pot files in preparation for 4.4 RC
Date Mon, 30 Jun 2014 09:46:05 GMT
http://git-wip-us.apache.org/repos/asf/cloudstack-docs-admin/blob/fffde327/source/locale/pot/networking.pot
----------------------------------------------------------------------
diff --git a/source/locale/pot/networking.pot b/source/locale/pot/networking.pot
index 0d4b3f5..45235bf 100644
--- a/source/locale/pot/networking.pot
+++ b/source/locale/pot/networking.pot
@@ -8,7 +8,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: Apache CloudStack Administration Documentation 4\n"
 "Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2014-05-27 10:34+0200\n"
+"POT-Creation-Date: 2014-06-30 11:44+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"
@@ -207,9 +207,7 @@ msgid "Host based (KVM/Xen)"
 msgstr ""
 
 #: ../../networking.rst:139
-#: ../../networking/remote_access_vpn.rst:18
 # 2c2f1239e908471a929feb91a02e08dd
-# 037fa60a2e2f4601bf22e714a97fe0fd
 msgid "Remote Access VPN"
 msgstr ""
 
@@ -352,44 +350,18 @@ msgstr ""
 #: ../../networking.rst:153
 #: ../../networking.rst:174
 #: ../../networking.rst:292
-#: ../../networking/remote_access_vpn.rst:118
-#: ../../networking/remote_access_vpn.rst:452
-#: ../../networking/remote_access_vpn.rst:515
-#: ../../networking/remote_access_vpn.rst:647
-#: ../../networking/static_nat.rst:18
-#: ../../networking/virtual_private_cloud_config.rst:348
-#: ../../networking/virtual_private_cloud_config.rst:515
-#: ../../networking/virtual_private_cloud_config.rst:750
-#: ../../networking/virtual_private_cloud_config.rst:808
-#: ../../networking/virtual_private_cloud_config.rst:869
-#: ../../networking/virtual_private_cloud_config.rst:1035
-#: ../../networking/virtual_private_cloud_config.rst:1303
 # eea6bbfe102d498e8fed5cb73cc69b0d
 # c02a1aa3d43f4cde9668b0c049f5ca68
 # fdd23b4cdd3f4aa4a540bf84253e6a5b
-# 74d00e17afdf47d8a79f5c8f0a90a214
-# 404668f335f04d41947db0129e79e65f
-# bee509b27e7c4c9985f5bd7c9169ecaf
-# 7f14717fbb6e471c9e00e2f7622cfa7b
-# 89295dfc645a421eac4401834f1b5564
-# 503c7c6831eb4f5ca96c64c2b8328442
-# b565e6a4cff8412f9d1c9032ea24e848
-# 749694902cf440fea4b8315f93dddf91
-# 0b5fb5da84014d7680951915cb26b0a8
-# f8fa3d05ec454df1abf7f6a5079c965b
-# 43f4ab42a09a499783f95aba183bd8a7
-# 88e9603df37e4eacb36619474a076744
 msgid "Static NAT"
 msgstr ""
 
 #: ../../networking.rst:155
 #: ../../networking.rst:176
 #: ../../networking.rst:295
-#: ../../networking/ip_forwarding_and_firewalling.rst:224
 # b4c037f8d0f1486a8b571d432c94dfc2
 # 218d3d03262e42b2aff11ea6d99f0a49
 # 3ec6fc2e436743f7bf4b9704948e4af3
-# 29ffedbd547e431f95d82b075df5ea66
 msgid "Port Forwarding"
 msgstr ""
 
@@ -450,9 +422,7 @@ msgid "The CloudStack administrator can create any number of custom network offe
 msgstr ""
 
 #: ../../networking.rst:204
-#: ../../networking/external_firewalls_and_load_balancers.rst:242
 # f84d6b9ac9d44d159518d14cc74cef39
-# 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 ""
 
@@ -477,43 +447,27 @@ msgid "To create a network offering:"
 msgstr ""
 
 #: ../../networking.rst:227
-#: ../../networking/ip_forwarding_and_firewalling.rst:202
 # ad144ea208224f0ba8bfd3d268ebaa1a
-# 5271ad0a1d4a4a27aa5597b044b42acf
 msgid "Log in with admin privileges to the CloudStack UI."
 msgstr ""
 
 #: ../../networking.rst:229
-#: ../../networking/ip_forwarding_and_firewalling.rst:204
 # 7183c1c87f1e4a549609755e3b609e22
-# fd49a59627284ffda66fef7096eaa709
 msgid "In the left navigation bar, click Service Offerings."
 msgstr ""
 
 #: ../../networking.rst:231
-#: ../../networking/ip_forwarding_and_firewalling.rst:206
 # 22b7bae2bee145399e00d289bccc7917
-# 7fce8b96f6e64727bb6063766c828bdd
 msgid "In Select Offering, choose Network Offering."
 msgstr ""
 
 #: ../../networking.rst:233
-#: ../../networking/ip_forwarding_and_firewalling.rst:208
-#: ../../networking/virtual_private_cloud_config.rst:961
-#: ../../networking/virtual_private_cloud_config.rst:1167
 # ef1169d122904044a6c0246757cbbb46
-# ef8895c197ff4343b04aecc73b5a9294
-# 08107e25d3ae4ed5a4e72a9ef68249af
-# f88397d4525c49d4b10ca8f6d24c5999
 msgid "Click Add Network Offering."
 msgstr ""
 
 #: ../../networking.rst:235
-#: ../../networking/virtual_private_cloud_config.rst:963
-#: ../../networking/virtual_private_cloud_config.rst:1169
 # 3479c8e9a5ef4f458aa9a86725ea9a15
-# 0b77090696474c0a9cab45f79b1c7986
-# e1cffd47fe2e4f3089c2620a68b839a1
 msgid "In the dialog, make the following choices:"
 msgstr ""
 
@@ -573,9 +527,7 @@ msgid "Supported Services"
 msgstr ""
 
 #: ../../networking.rst:281
-#: ../../networking/ip_reservation_in_guest_networks.rst:70
 # d4aa55848ef645639458f908896ac697
-# e1395f7f735643f98e49f71acb302533
 msgid "Description"
 msgstr ""
 
@@ -702,9 +654,7 @@ msgid "For more information, see `“Configuring Network Access Control List”
 msgstr ""
 
 #: ../../networking.rst:304
-#: ../../networking/security_groups.rst:18
 # 72b47ce7c25a4820af0c52549a594235
-# b67087ae536e4b77ac5668f8f3f73ba8
 msgid "Security Groups"
 msgstr ""
 
@@ -809,7428 +759,7 @@ msgid "To block the egress traffic for a guest network, select Deny. In this cas
 msgstr ""
 
 #: ../../networking.rst:407
-#: ../../networking/ip_forwarding_and_firewalling.rst:88
-#: ../../networking/ip_forwarding_and_firewalling.rst:163
-#: ../../networking/ip_forwarding_and_firewalling.rst:276
-#: ../../networking/public_ips_and_vlans_for_accounts.rst:117
-#: ../../networking/remote_access_vpn.rst:153
-#: ../../networking/security_groups.rst:210
-#: ../../networking/virtual_private_cloud_config.rst:642
 # fcfc7b9313f94bbda5ac1afbd8168f7c
-# 41821a610d844daf8255026b71299059
-# 1d39fcb3a5e34d769f89885db9866836
-# 2319658c89b74a0294ce8f0a253a4d53
-# cbf3d4473399404684b33c48a92e0148
-# f388fc2f4f0749f5bbb9e062d57f1137
-# 39febf06883a4d248d1ac5ad19510065
-# a267ec664f35442db0c8d33d273ec07a
 msgid "Click Add."
 msgstr ""
 
-#: ../../networking/acquiring_an_ip_address.rst:18
-# aec0c098f53f452cb8665fc7b69cd182
-msgid "Acquiring a New IP Address"
-msgstr ""
-
-#: ../../networking/acquiring_an_ip_address.rst:20
-#: ../../networking/external_firewalls_and_load_balancers.rst:255
-#: ../../networking/ip_forwarding_and_firewalling.rst:59
-#: ../../networking/ip_forwarding_and_firewalling.rst:132
-#: ../../networking/ip_forwarding_and_firewalling.rst:245
-#: ../../networking/ip_reservation_in_guest_networks.rst:106
-#: ../../networking/multiple_guest_networks.rst:47
-#: ../../networking/multiple_guest_networks.rst:97
-#: ../../networking/multiple_guest_networks.rst:135
-#: ../../networking/multiple_guest_networks.rst:153
-#: ../../networking/multiple_guest_networks.rst:173
-#: ../../networking/multiple_subnets_in_shared_network.rst:52
-#: ../../networking/portable_ips.rst:58
-#: ../../networking/portable_ips.rst:90
-#: ../../networking/releasing_an_ip_address.rst:24
-#: ../../networking/remote_access_vpn.rst:59
-#: ../../networking/remote_access_vpn.rst:301
-#: ../../networking/remote_access_vpn.rst:411
-#: ../../networking/remote_access_vpn.rst:431
-#: ../../networking/remote_access_vpn.rst:493
-#: ../../networking/remote_access_vpn.rst:624
-#: ../../networking/security_groups.rst:62
-#: ../../networking/security_groups.rst:124
-#: ../../networking/static_nat.rst:36
-#: ../../networking/virtual_private_cloud_config.rst:179
-#: ../../networking/virtual_private_cloud_config.rst:223
-#: ../../networking/virtual_private_cloud_config.rst:331
-#: ../../networking/virtual_private_cloud_config.rst:380
-#: ../../networking/virtual_private_cloud_config.rst:492
-#: ../../networking/virtual_private_cloud_config.rst:662
-#: ../../networking/virtual_private_cloud_config.rst:729
-#: ../../networking/virtual_private_cloud_config.rst:788
-#: ../../networking/virtual_private_cloud_config.rst:848
-#: ../../networking/virtual_private_cloud_config.rst:1014
-#: ../../networking/virtual_private_cloud_config.rst:1227
-#: ../../networking/virtual_private_cloud_config.rst:1282
-#: ../../networking/virtual_private_cloud_config.rst:1360
-#: ../../networking/virtual_private_cloud_config.rst:1388
-# 6113064b39bc4682869acf44286131ad
-# 1bc40a00c2f341118db65e97bbbcf986
-# 098b22043ec643559c039b39aa24d618
-# f62479b013c241a791c42b8843bd140d
-# c384f1b44804485fba23fe018c16683e
-# 34eb58849cb141e9898291a434cc05ba
-# fc94885acfb44c089b5b955040cda635
-# e90f66fa32fb4ac0bdd48def8833e52d
-# 443695bf438a4240b9c354d9c66f2292
-# dc150422f8d8498e81ccfa11cc7daf5f
-# f4162f2a3af54aee90b80a9efec6523f
-# 402388a40d1c4432adf97dcb94bc7e0a
-# b085a9f5f2ce4744b86603f26196b283
-# a28f4db3b1734d3c9f0aa6cada34dab5
-# 99e24197740148e683aa3ffad5870800
-# 85153916f2a94aeb80faa2c9f22cfcea
-# e7cff502f3494c00b665a1b732e05fb1
-# 7fd5ac75573d435b8c164435b6b50404
-# ab1f2323529a48e8a071e9baa44284e3
-# 6dfbddbad973426b8d6704da05fb2166
-# ce7c03a477b84c029914728fac5f85d5
-# a026f1875e7f4cec8447b013bf2d7a78
-# 27e30ee65cbe485bb8e7370a38b75281
-# e6dabe6070464d23926137799673505a
-# 27c90db3b2d846b58c9abf075735077b
-# 23214314bc4c40d3bc784cf8b99c1273
-# 06da644a106746d9b22320df5442e7eb
-# 8292048a7bd74adeae7e3b6677cc7dc8
-# fb4e97f30b554d92af68a1e9d1886576
-# ceaea70c95b1422597606b789f77fae7
-# c80fe5feb23443ab8e81a05534c38d15
-# 612a8d98561a4b08824d22d8ab9cd815
-# 3d9f5b1f4cf7497ebaa39f40d2b7d3fb
-# 7af40adf2d7f49ee82115cf17558f076
-# 54efcc991da44e5b87cab339063f09cc
-# 98308f9c7c7e4548b3e6ef0828178c9d
-# b16c2e02fd8e42a1aacb687d60b4fb46
-# 1d2a5b77246843818d6d6cc8fd7482ae
-msgid "Log in to the CloudStack UI as an administrator or end user."
-msgstr ""
-
-#: ../../networking/acquiring_an_ip_address.rst:22
-#: ../../networking/external_firewalls_and_load_balancers.rst:257
-#: ../../networking/ip_forwarding_and_firewalling.rst:61
-#: ../../networking/ip_forwarding_and_firewalling.rst:134
-#: ../../networking/ip_reservation_in_guest_networks.rst:108
-#: ../../networking/multiple_guest_networks.rst:49
-#: ../../networking/multiple_guest_networks.rst:179
-#: ../../networking/portable_ips.rst:92
-#: ../../networking/releasing_an_ip_address.rst:26
-#: ../../networking/remote_access_vpn.rst:303
-#: ../../networking/remote_access_vpn.rst:413
-#: ../../networking/remote_access_vpn.rst:433
-#: ../../networking/remote_access_vpn.rst:495
-#: ../../networking/remote_access_vpn.rst:626
-#: ../../networking/security_groups.rst:64
-#: ../../networking/static_nat.rst:38
-#: ../../networking/virtual_private_cloud_config.rst:181
-#: ../../networking/virtual_private_cloud_config.rst:225
-#: ../../networking/virtual_private_cloud_config.rst:333
-#: ../../networking/virtual_private_cloud_config.rst:382
-#: ../../networking/virtual_private_cloud_config.rst:494
-#: ../../networking/virtual_private_cloud_config.rst:664
-#: ../../networking/virtual_private_cloud_config.rst:731
-#: ../../networking/virtual_private_cloud_config.rst:790
-#: ../../networking/virtual_private_cloud_config.rst:850
-#: ../../networking/virtual_private_cloud_config.rst:1016
-#: ../../networking/virtual_private_cloud_config.rst:1229
-#: ../../networking/virtual_private_cloud_config.rst:1284
-#: ../../networking/virtual_private_cloud_config.rst:1362
-#: ../../networking/virtual_private_cloud_config.rst:1390
-# ccc7a493b9b940c2b706c15e852b3e93
-# 57f7d8a61234427abc813c4208e84192
-# a633160d3ee343639365b9067af58eb1
-# c6c7495d464a4262ace3361c7cce9b5b
-# 3dc484e1bd5145259125fe0fcf8ccf8c
-# e9d2f3becfba421592c540e757fe27e8
-# 1e2cad5b28aa4f56bfee80c03c969d5c
-# b933b6d78fe94153a35b24d2ccfd8e06
-# da80f79b21a846878018930987c87ffd
-# 6a26e636eb224d1eb75c9782de7c830d
-# affc98b5cd4b401086e5e00f9e69ac90
-# 23c81aa674f64826830390c49839730c
-# 98dc2f6f69d341b0b1867f35102e20ff
-# d4efd83e728b439eaa8408bd783d0c11
-# 344ee6a79a674e88a4a61b24b0a01b42
-# 726614a43cbf4c448770c40822676059
-# 25aa9d2390434c03a89b6b16c9b69fe9
-# 6e8e81dbb9f447c3aaabac12cbbebc79
-# 7daeed72e5de4f68b5d3fec3deae5a12
-# ad50664f103d4bc3b95d04f0c6891395
-# b462daef366f4f119997d229bdcd4fde
-# cbb8c618e79f4f5bb024ac637c94f155
-# d418a0fbecc7474d89b0c7122cb9f046
-# c1602cd2089a4465bb64a310c84582ae
-# 692a153c672746fa937e636f18024241
-# f2241fbd031643a498b64bc52bc9a3ed
-# 35b9e68484d140e1813335d0a33c68d1
-# bb61fadd006d4624a91bb45665efac73
-# 0cdbc29c89c540c08fa87bd601f4976c
-# 2706338d19fe43d589acd0c274b932c0
-msgid "In the left navigation, choose Network."
-msgstr ""
-
-#: ../../networking/acquiring_an_ip_address.rst:24
-#: ../../networking/ip_forwarding_and_firewalling.rst:63
-#: ../../networking/portable_ips.rst:94
-#: ../../networking/releasing_an_ip_address.rst:28
-#: ../../networking/static_nat.rst:40
-# 9a6973f9449e4414a4643a6da352263e
-# ff56e69810c34ee4a08280a7ef06cfbb
-# 2f46ac57574a4ff3833cd3af46386463
-# 24863c020eb04ba9808fc2e0f24e0760
-# 71505d3318714907a3abd5319833b78e
-msgid "Click the name of the network where you want to work with."
-msgstr ""
-
-#: ../../networking/acquiring_an_ip_address.rst:26
-#: ../../networking/external_firewalls_and_load_balancers.rst:262
-#: ../../networking/ip_forwarding_and_firewalling.rst:65
-#: ../../networking/portable_ips.rst:96
-#: ../../networking/releasing_an_ip_address.rst:30
-#: ../../networking/remote_access_vpn.rst:82
-#: ../../networking/static_nat.rst:42
-# beaa083fcce64bb48e44a47c9b4ab745
-# 20fc7dedf2cf482d94d8977ac64c6b0d
-# d546be88025a4254b8eecf1f0b16bdf0
-# a7dc83315ae746af830094d45cfe7c11
-# 1e70144ba5394954a2c92850335b7555
-# a23f38b6e2c8464bb754dcb7965bd45e
-# 0898722d18384a89a217a7a8e7cb6fbf
-msgid "Click View IP Addresses."
-msgstr ""
-
-#: ../../networking/acquiring_an_ip_address.rst:28
-#: ../../networking/portable_ips.rst:98
-# 76867ce630364509a651c09137cab94e
-# 64b8eac8ac21402293c2fff5d435a7eb
-msgid "Click Acquire New IP."
-msgstr ""
-
-#: ../../networking/acquiring_an_ip_address.rst:30
-#: ../../networking/portable_ips.rst:100
-# 35698ea68aa24ff79ce9dc09c1d12caf
-# 4a739787a6194df09e032797d1fe0911
-msgid "The Acquire New IP window is displayed."
-msgstr ""
-
-#: ../../networking/acquiring_an_ip_address.rst:32
-#: ../../networking/portable_ips.rst:102
-# 4819ef07622d41fd818aef83d9752ac2
-# c8424da0e97a443f9d01fab04339184f
-msgid "Specify whether you want cross-zone IP or not."
-msgstr ""
-
-#: ../../networking/acquiring_an_ip_address.rst:34
-# 342295d34e8e4252b2850d040aca7909
-msgid "If you want Portable IP click Yes in the confirmation dialog. If you want a normal Public IP click No."
-msgstr ""
-
-#: ../../networking/acquiring_an_ip_address.rst:37
-# 9a4837aaa4c940b78c8aa311245b748a
-msgid "For more information on Portable IP, see `\"Portable IPs\" <#portable-ips>`_."
-msgstr ""
-
-#: ../../networking/acquiring_an_ip_address.rst:40
-#: ../../networking/portable_ips.rst:106
-# 2ee8ad57fe20463893a86f3fe6eb669f
-# 97dbf547785f4b1aaea165efca4b50a9
-msgid "Within a few moments, the new IP address should appear with the state Allocated. You can now use the IP address in port forwarding or static NAT rules."
-msgstr ""
-
-#: ../../networking/advanced_zone_config.rst:19
-# bcc6293e20c4470c938be75c5f17196e
-msgid "Advanced Zone Physical Network Configuration"
-msgstr ""
-
-#: ../../networking/advanced_zone_config.rst:21
-# 65ad7a2b34f848cd9f21c2d2d51f06f6
-msgid "Within a zone that uses advanced networking, you need to tell the Management Server how the physical network is set up to carry different kinds of traffic in isolation."
-msgstr ""
-
-#: ../../networking/advanced_zone_config.rst:27
-# 360066243e5b4ffc894a816b7e903923
-msgid "Configure Guest Traffic in an Advanced Zone"
-msgstr ""
-
-#: ../../networking/advanced_zone_config.rst:29
-# ed393c6319d54e98ba44a7577315044b
-msgid "These steps assume you have already logged in to the CloudStack UI. To configure the base guest network:"
-msgstr ""
-
-#: ../../networking/advanced_zone_config.rst:32
-# e3081f9e98e446d6855a2e72cba9849d
-msgid "In the left navigation, choose Infrastructure. On Zones, click View More, then click the zone to which you want to add a network."
-msgstr ""
-
-#: ../../networking/advanced_zone_config.rst:35
-#: ../../networking/advanced_zone_config.rst:87
-#: ../../networking/isolation_in_advanced_zone_with_vlan.rst:145
-# 7e76a728cc8a43778d79ff577c30b3f2
-# 22748233c6cf4d06b5ba94259fe1e6e9
-# 3254ff32eecc4e9b9ac57fc4f2219acd
-msgid "Click the Network tab."
-msgstr ""
-
-#: ../../networking/advanced_zone_config.rst:37
-#: ../../networking/advanced_zone_config.rst:89
-#: ../../networking/isolation_in_advanced_zone_with_vlan.rst:147
-# 1c9241340a4d47a58af0ae3e10893ea1
-# 2c90664c2e9647c59a36e2a8f25d1a87
-# fdd056f25bee447e98028c9301071fd7
-msgid "Click Add guest network."
-msgstr ""
-
-#: ../../networking/advanced_zone_config.rst:39
-# cbb8ccbe13b34ed88593d4cf688451a1
-msgid "The Add guest network window is displayed:"
-msgstr ""
-
-#: ../../networking/advanced_zone_config.rst:41
-# ef5079e0fa7f4e5c8bac3410c02fa00f
-msgid "|addguestnetwork.png|"
-msgstr ""
-
-#: ../../networking/advanced_zone_config.rst:43
-#: ../../networking/remote_access_vpn.rst:311
-#: ../../networking/virtual_private_cloud_config.rst:189
-# ec8bb470f4924bd0af5b256494fbf0f5
-# 0810d2cb133043b4858badbc2e4ac704
-# 7bd4344fc68d4e6c8939286640c64ff6
-msgid "Provide the following information:"
-msgstr ""
-
-#: ../../networking/advanced_zone_config.rst:45
-# fa32f98dfeb04b68b79b01e6ef0e1fcf
-msgid "**Name**: The name of the network. This will be user-visible"
-msgstr ""
-
-#: ../../networking/advanced_zone_config.rst:47
-# f38e902b2f2c4fe78960c5d37c4a3609
-msgid "**Display Text**: The description of the network. This will be user-visible"
-msgstr ""
-
-#: ../../networking/advanced_zone_config.rst:50
-# c1e74ac05b5a4eacb568d9201d733f74
-msgid "**Zone**: The zone in which you are configuring the guest network."
-msgstr ""
-
-#: ../../networking/advanced_zone_config.rst:52
-# 1bb07d209bd44e82b5f43507bb058db9
-msgid "**Network offering**: If the administrator has configured multiple network offerings, select the one you want to use for this network"
-msgstr ""
-
-#: ../../networking/advanced_zone_config.rst:55
-# a33441c2621f415eb45dbc077a63e7bb
-msgid "**Guest Gateway**: The gateway that the guests should use"
-msgstr ""
-
-#: ../../networking/advanced_zone_config.rst:57
-# 7f50db013a5941939cff931a256abb58
-msgid "**Guest Netmask**: The netmask in use on the subnet the guests will use"
-msgstr ""
-
-#: ../../networking/advanced_zone_config.rst:60
-#: ../../networking/global_server_load_balancing.rst:371
-#: ../../networking/ip_forwarding_and_firewalling.rst:215
-#: ../../networking/multiple_subnets_in_shared_network.rst:95
-#: ../../networking/persistent_networks.rst:94
-#: ../../networking/portable_ips.rst:84
-#: ../../networking/public_ips_and_vlans_for_accounts.rst:115
-#: ../../networking/remote_access_vpn.rst:402
-#: ../../networking/remote_access_vpn.rst:425
-#: ../../networking/security_groups.rst:72
-#: ../../networking/virtual_private_cloud_config.rst:211
-#: ../../networking/virtual_private_cloud_config.rst:281
-#: ../../networking/virtual_private_cloud_config.rst:455
-#: ../../networking/virtual_private_cloud_config.rst:479
-# 186fd6f7a8de48fea845645978a6b332
-# e7f874eb36ba4cd380f7a50d5bff8909
-# 41d012a83e774bdeaeac42e5b44d851c
-# c54dd19ac3fc4b1abe5c8e2ba6021969
-# fd7fed942171405cb30c3ea00f4111cb
-# 8615e1020e2747f0ba31cd4cb186a010
-# e54b45158ec1469392091a64574cbb55
-# 4d12f59b777c48e98fb18ab2bace355d
-# a65f0ba427b04b6da2bdc39a05acba02
-# 237fc184482448589b8a2eb7c3c70e76
-# f0a8bdb0febf4b97879a69db489ba8b8
-# a37c6acaf1254a6f818d9f64ae0960aa
-# 677238e0e48a40898578fd007249ecaa
-# 650c882688974599ba5c3660d14f2838
-msgid "Click OK."
-msgstr ""
-
-#: ../../networking/advanced_zone_config.rst:64
-# 6c2ac4e12f5f4a8c8788df54295b6e31
-msgid "Configure Public Traffic in an Advanced Zone"
-msgstr ""
-
-#: ../../networking/advanced_zone_config.rst:66
-# 7e91e673073d49e69f1ec92976a0d118
-msgid "In a zone that uses advanced networking, you need to configure at least one range of IP addresses for Internet traffic."
-msgstr ""
-
-#: ../../networking/advanced_zone_config.rst:71
-# c4aa53c641a347da9da814dfc32940a5
-msgid "Configuring a Shared Guest Network"
-msgstr ""
-
-#: ../../networking/advanced_zone_config.rst:73
-#: ../../networking/isolation_in_advanced_zone_with_vlan.rst:131
-#: ../../networking/public_ips_and_vlans_for_accounts.rst:54
-# d5ac14718de945a5ae1eda9e0574d9cf
-# 73811e0470e04b63a31d32549a8c882b
-# 5409cfc1bd6f4b41bdd23eee4d6b9396
-msgid "Log in to the CloudStack UI as administrator."
-msgstr ""
-
-#: ../../networking/advanced_zone_config.rst:75
-#: ../../networking/isolation_in_advanced_zone_with_vlan.rst:133
-#: ../../networking/multiple_subnets_in_shared_network.rst:54
-# 9a3fd0f929374352a6cf52cc9790dfb1
-# f987d4525be34ae986962e374a48197f
-# c062e6ebc0b74be185c8e192c237a3d8
-msgid "In the left navigation, choose Infrastructure."
-msgstr ""
-
-#: ../../networking/advanced_zone_config.rst:77
-#: ../../networking/isolation_in_advanced_zone_with_vlan.rst:135
-# dbfd04e800154df197a15cb258be6d3f
-# 81a7cad61d0c43e3989e9742e6efb902
-msgid "On Zones, click View More."
-msgstr ""
-
-#: ../../networking/advanced_zone_config.rst:79
-#: ../../networking/isolation_in_advanced_zone_with_vlan.rst:137
-# 7f633e5cc4504dfdaa399fcb8ab6c22e
-# 62eb1c2209d34440987b38dc999dad75
-msgid "Click the zone to which you want to add a guest network."
-msgstr ""
-
-#: ../../networking/advanced_zone_config.rst:81
-#: ../../networking/isolation_in_advanced_zone_with_vlan.rst:139
-#: ../../networking/public_ips_and_vlans_for_accounts.rst:62
-#: ../../networking/public_ips_and_vlans_for_accounts.rst:132
-# 173dd051e7a1433d90061cca03962fc4
-# aeaece1bb557450383b2b0c0930b8d39
-# 04eaa49757a64adf830002153cf8db20
-# cea8888967a844ccbb283c973f4b9482
-msgid "Click the Physical Network tab."
-msgstr ""
-
-#: ../../networking/advanced_zone_config.rst:83
-#: ../../networking/isolation_in_advanced_zone_with_vlan.rst:141
-# e48da344ca7241429e6404ab7b137b39
-# bdccf5bb73ce4a58b074c7db9f09db19
-msgid "Click the physical network you want to work with."
-msgstr ""
-
-#: ../../networking/advanced_zone_config.rst:85
-#: ../../networking/isolation_in_advanced_zone_with_vlan.rst:143
-# 0e03928f490a4bf5acd9028fed3fd8d8
-# d325d3d79e0e41fd9ce93131ae2ea76a
-msgid "On the Guest node of the diagram, click Configure."
-msgstr ""
-
-#: ../../networking/advanced_zone_config.rst:91
-#: ../../networking/isolation_in_advanced_zone_with_vlan.rst:149
-# 9272a3e9c02b4d3fb7e88cd90f63e56f
-# f58f17bd25284897abbe7df71fc2c3fb
-msgid "The Add guest network window is displayed."
-msgstr ""
-
-#: ../../networking/advanced_zone_config.rst:93
-#: ../../networking/external_firewalls_and_load_balancers.rst:482
-#: ../../networking/global_server_load_balancing.rst:393
-#: ../../networking/isolation_in_advanced_zone_with_vlan.rst:151
-#: ../../networking/multiple_subnets_in_shared_network.rst:75
-#: ../../networking/portable_ips.rst:70
-#: ../../networking/public_ips_and_vlans_for_accounts.rst:79
-#: ../../networking/public_ips_and_vlans_for_accounts.rst:89
-#: ../../networking/public_ips_and_vlans_for_accounts.rst:107
-#: ../../networking/public_ips_and_vlans_for_accounts.rst:142
-#: ../../networking/virtual_private_cloud_config.rst:248
-#: ../../networking/virtual_private_cloud_config.rst:539
-#: ../../networking/virtual_private_cloud_config.rst:1062
-#: ../../networking/virtual_private_cloud_config.rst:1330
-# 271290c4c54643a9a8cc203840b4bb3b
-# aa34165bbbed4360bb6cebfc7b978d91
-# 767ce39d9a094fda85465381d3a93bad
-# 5e421fb492504766a709b728f4fc51e5
-# 8d5c0e4efe1742f7988a60fe55223d66
-# 9c9681bfaca543f09522720f86b05c3b
-# b99e236f412f4946af47669c8d62396e
-# eedc80b2aa5c4c8696da4d4b51a28179
-# 39b98908344542aeb2e40bdbf9550571
-# f6dc925b4c634b9fa0523254d12380bb
-# b372cab6baf04844a5ff7a1611d1d5b6
-# 4bc6b0a5224f4b8383ff3c5322dc34c6
-# 95ebee159c7a49d6a38872dfbba22963
-# 1490eec9177146d0bb7ef70ee1896fb9
-msgid "Specify the following:"
-msgstr ""
-
-#: ../../networking/advanced_zone_config.rst:95
-#: ../../networking/isolation_in_advanced_zone_with_vlan.rst:153
-# a69cf77fdc48441b9a0e41233bf3d4db
-# 606686347ca84fbc9a83c5f46c31d8ea
-msgid "**Name**: The name of the network. This will be visible to the user."
-msgstr ""
-
-#: ../../networking/advanced_zone_config.rst:97
-#: ../../networking/isolation_in_advanced_zone_with_vlan.rst:156
-# 924d5df6b0f643c3ad34cdfa02548391
-# 73bbe5e4075e43f39b388b8b267c5401
-msgid "**Description**: The short description of the network that can be displayed to users."
-msgstr ""
-
-#: ../../networking/advanced_zone_config.rst:100
-#: ../../networking/isolation_in_advanced_zone_with_vlan.rst:159
-# 8c68c64196cb4b548290e4a3e9851553
-# 17a0fe7f48cc4af3bbe7b8e52b6f6d1b
-msgid "**VLAN ID**: The unique ID of the VLAN."
-msgstr ""
-
-#: ../../networking/advanced_zone_config.rst:102
-# 0711300a6023445c91c8a4d7926a8e04
-msgid "**Isolated VLAN ID**: The unique ID of the Secondary Isolated VLAN."
-msgstr ""
-
-#: ../../networking/advanced_zone_config.rst:105
-#: ../../networking/isolation_in_advanced_zone_with_vlan.rst:167
-# dbbc4b85106a407f9bb4532a5c1a40a2
-# 38765c8ae24048dba72826d07d096afe
-msgid "**Scope**: The available scopes are Domain, Account, Project, and All."
-msgstr ""
-
-#: ../../networking/advanced_zone_config.rst:108
-#: ../../networking/isolation_in_advanced_zone_with_vlan.rst:170
-# 46fd996ba0b241efa0f21c9f22c7c77d
-# 90706772c0084832b86742ce99f99d6e
-msgid "**Domain**: Selecting Domain limits the scope of this guest network to the domain you specify. The network will not be available for other domains. If you select Subdomain Access, the guest network is available to all the sub domains within the selected domain."
-msgstr ""
-
-#: ../../networking/advanced_zone_config.rst:114
-#: ../../networking/isolation_in_advanced_zone_with_vlan.rst:176
-# 79bd2bf86f74472db3b4cba26ef143dd
-# 7e174e9b956f4f2784d5196f1a30439f
-msgid "**Account**: The account for which the guest network is being created for. You must specify the domain the account belongs to."
-msgstr ""
-
-#: ../../networking/advanced_zone_config.rst:118
-#: ../../networking/isolation_in_advanced_zone_with_vlan.rst:180
-# f3de2d8830134ab195b04b7e4b74b215
-# d8216708afb2490c97e3cca13b2752dd
-msgid "**Project**: The project for which the guest network is being created for. You must specify the domain the project belongs to."
-msgstr ""
-
-#: ../../networking/advanced_zone_config.rst:122
-#: ../../networking/isolation_in_advanced_zone_with_vlan.rst:184
-# e03c5c4ff8d646cdb1a4029a794765e5
-# 3aa0f96be4f84d1bae1f1744b108dff8
-msgid "**All**: The guest network is available for all the domains, account, projects within the selected zone."
-msgstr ""
-
-#: ../../networking/advanced_zone_config.rst:125
-#: ../../networking/isolation_in_advanced_zone_with_vlan.rst:187
-# 74217dea4b9c4d8faa89e1ea6b2c754e
-# 339b47c6f0f94ca4a221c0f592e92d5b
-msgid "**Network Offering**: If the administrator has configured multiple network offerings, select the one you want to use for this network."
-msgstr ""
-
-#: ../../networking/advanced_zone_config.rst:129
-#: ../../networking/isolation_in_advanced_zone_with_vlan.rst:191
-# 587275eb7b1249e590763c8b0fb81d41
-# ae2111debd664f179fe8eb3b251587ff
-msgid "**Gateway**: The gateway that the guests should use."
-msgstr ""
-
-#: ../../networking/advanced_zone_config.rst:131
-#: ../../networking/isolation_in_advanced_zone_with_vlan.rst:193
-# 8123de4fbb1d4a1cba01cb099365b448
-# df6c332c5f7e427d867dcef1784c0731
-msgid "**Netmask**: The netmask in use on the subnet the guests will use."
-msgstr ""
-
-#: ../../networking/advanced_zone_config.rst:133
-#: ../../networking/isolation_in_advanced_zone_with_vlan.rst:195
-# 129d7c2b8ec442cb802ec894eb871959
-# 5331fd382d74450c957ad9e5fa46a095
-msgid "**IP Range**: A range of IP addresses that are accessible from the Internet and are assigned to the guest VMs."
-msgstr ""
-
-#: ../../networking/advanced_zone_config.rst:136
-# 8ea844eb28e94825bdefeba5cc1e143c
-msgid "If one NIC is used, these IPs should be in the same CIDR in the case of IPv6."
-msgstr ""
-
-#: ../../networking/advanced_zone_config.rst:139
-# 1a2dacdd2a984c978ad1455bdb6c04b8
-msgid "**IPv6 CIDR**: The network prefix that defines the guest network subnet. This is the CIDR that describes the IPv6 addresses in use in the guest networks in this zone. To allot IP addresses from within a particular address block, enter a CIDR."
-msgstr ""
-
-#: ../../networking/advanced_zone_config.rst:144
-#: ../../networking/isolation_in_advanced_zone_with_vlan.rst:198
-# d17e32d82ae849139dda243c9ddc9676
-# 6be7da6ede894331ad2082717f19c89d
-msgid "**Network Domain**: A custom DNS suffix at the level of a network. If you want to assign a special domain name to the guest VM network, specify a DNS suffix."
-msgstr ""
-
-#: ../../networking/advanced_zone_config.rst:148
-#: ../../networking/global_server_load_balancing.rst:415
-#: ../../networking/global_server_load_balancing.rst:439
-#: ../../networking/isolation_in_advanced_zone_with_vlan.rst:202
-#: ../../networking/remote_access_vpn.rst:555
-# e200da9c829a41109b13173bce7f11ca
-# 0161504934d746e39b05e6b50e264faf
-# 8c377e12f8494a009d5eed7e06824fe3
-# 0f106d1db97249348138b9cf76182524
-# dd03407d4f064ec99ea68bb066d2289e
-msgid "Click OK to confirm."
-msgstr ""
-
-#: ../../networking/basic_zone_config.rst:19
-# bf16fca54893437db5aad5aa3f2e6e2c
-msgid "Basic Zone Physical Network Configuration"
-msgstr ""
-
-#: ../../networking/basic_zone_config.rst:21
-# 153ba46cfcf14ac28f2db2730d2e43af
-msgid "In a basic network, configuring the physical network is fairly straightforward. You only need to configure one guest network to carry traffic that is generated by guest VMs. When you first add a zone to CloudStack, you set up the guest network through the Add Zone screens."
-msgstr ""
-
-#: ../../networking/dns_and_dhcp.rst:18
-# 727de7b64d0e4c34bddda54359ed846d
-msgid "DNS and DHCP"
-msgstr ""
-
-#: ../../networking/dns_and_dhcp.rst:20
-# f58ccb2c24bb47c0872a16c74d47f121
-msgid "The Virtual Router provides DNS and DHCP services to the guests. It proxies DNS requests to the DNS server configured on the Availability Zone."
-msgstr ""
-
-#: ../../networking/elastic_ips.rst:18
-# 68f25b7a2e514065b563d7ccdd72f355
-msgid "About Elastic IPs"
-msgstr ""
-
-#: ../../networking/elastic_ips.rst:20
-# bf34049aef4a4cddb2aa0169d49b5281
-msgid "Elastic IP (EIP) addresses are the IP addresses that are associated with an account, and act as static IP addresses. The account owner has the complete control over the Elastic IP addresses that belong to the account. As an account owner, you can allocate an Elastic IP to a VM of your choice from the EIP pool of your account. Later if required you can reassign the IP address to a different VM. This feature is extremely helpful during VM failure. Instead of replacing the VM which is down, the IP address can be reassigned to a new VM in your account."
-msgstr ""
-
-#: ../../networking/elastic_ips.rst:29
-# 8b249afbc2664b01a564524559d5c5fd
-msgid "Similar to the public IP address, Elastic IP addresses are mapped to their associated private IP addresses by using StaticNAT. The EIP service is equipped with StaticNAT (1:1) service in an EIP-enabled basic zone. The default network offering, DefaultSharedNetscalerEIPandELBNetworkOffering, provides your network with EIP and ELB network services if a NetScaler device is deployed in your zone. Consider the following illustration for more details."
-msgstr ""
-
-#: ../../networking/elastic_ips.rst:37
-# deef19d6b1414dbb967743f1b7cef2df
-msgid "|eip-ns-basiczone.png|"
-msgstr ""
-
-#: ../../networking/elastic_ips.rst:39
-# a1f02d4922ed4bbb8941ccc048f0b0b4
-msgid "In the illustration, a NetScaler appliance is the default entry or exit point for the CloudStack instances, and firewall is the default entry or exit point for the rest of the data center. Netscaler provides LB services and staticNAT service to the guest networks. The guest traffic in the pods and the Management Server are on different subnets / VLANs. The policy-based routing in the data center core switch sends the public traffic through the NetScaler, whereas the rest of the data center goes through the firewall."
-msgstr ""
-
-#: ../../networking/elastic_ips.rst:48
-# 28c78bf967714b33884e97cfa4ca307b
-msgid "The EIP work flow is as follows:"
-msgstr ""
-
-#: ../../networking/elastic_ips.rst:50
-# 773cd4ac9b6d4973832aafd2d0cf2f9e
-msgid "When a user VM is deployed, a public IP is automatically acquired from the pool of public IPs configured in the zone. This IP is owned by the VM's account."
-msgstr ""
-
-#: ../../networking/elastic_ips.rst:54
-# 23a70289953d415c81e8dd6ebc86423c
-msgid "Each VM will have its own private IP. When the user VM starts, Static NAT is provisioned on the NetScaler device by using the Inbound Network Address Translation (INAT) and Reverse NAT (RNAT) rules between the public IP and the private IP."
-msgstr ""
-
-#: ../../networking/elastic_ips.rst:60
-# bfa50768ea9b496599aa1804e3437f25
-msgid "Inbound NAT (INAT) is a type of NAT supported by NetScaler, in which the destination IP address is replaced in the packets from the public network, such as the Internet, with the private IP address of a VM in the private network. Reverse NAT (RNAT) is a type of NAT supported by NetScaler, in which the source IP address is replaced in the packets generated by a VM in the private network with the public IP address."
-msgstr ""
-
-#: ../../networking/elastic_ips.rst:67
-# cef50f723bd34b298098fab0ed2c2328
-msgid "This default public IP will be released in two cases:"
-msgstr ""
-
-#: ../../networking/elastic_ips.rst:69
-# 954fad75b2bd41d1b16f50f819a7e300
-msgid "When the VM is stopped. When the VM starts, it again receives a new public IP, not necessarily the same one allocated initially, from the pool of Public IPs."
-msgstr ""
-
-#: ../../networking/elastic_ips.rst:73
-# a5713ccdbc7f41dea9e1fb5bd2a81337
-msgid "The user acquires a public IP (Elastic IP). This public IP is associated with the account, but will not be mapped to any private IP. However, the user can enable Static NAT to associate this IP to the private IP of a VM in the account. The Static NAT rule for the public IP can be disabled at any time. When Static NAT is disabled, a new public IP is allocated from the pool, which is not necessarily be the same one allocated initially."
-msgstr ""
-
-#: ../../networking/elastic_ips.rst:81
-# a8f5524c22bd4ddf82fd8d2d6240b94f
-msgid "For the deployments where public IPs are limited resources, you have the flexibility to choose not to allocate a public IP by default. You can use the Associate Public IP option to turn on or off the automatic public IP assignment in the EIP-enabled Basic zones. If you turn off the automatic public IP assignment while creating a network offering, only a private IP is assigned to a VM when the VM is deployed with that network offering. Later, the user can acquire an IP for the VM and enable static NAT."
-msgstr ""
-
-#: ../../networking/elastic_ips.rst:90
-# 89cea0807df84e08bd3c61dbf7579d80
-msgid "For more information on the Associate Public IP option, see `\"Creating a New Network Offering\" <networking.html#creating-a-new-network-offering>`_."
-msgstr ""
-
-#: ../../networking/elastic_ips.rst:94
-# e8e0a7038ebb4ea181ba58c3f4cdc0ed
-msgid "The Associate Public IP feature is designed only for use with user VMs. The System VMs continue to get both public IP and private by default, irrespective of the network offering configuration."
-msgstr ""
-
-#: ../../networking/elastic_ips.rst:98
-# 116e2d3d7abc4e4b89e08770c938b985
-msgid "New deployments which use the default shared network offering with EIP and ELB services to create a shared network in the Basic zone will continue allocating public IPs to each user VM."
-msgstr ""
-
-#: ../../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:253
-# b09aa6c58aa84b8f89b3293a64ca17fd
-msgid "Adding a Load Balancer Rule"
-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:264
-#: ../../networking/virtual_private_cloud_config.rst:1055
-#: ../../networking/virtual_private_cloud_config.rst:1323
-# aff4544b414847af82ceceb0bd4e3b55
-# faa2aca06f244ec79e1495f403d60fba
-# f6b4d72a1ace463aaeae65e85f5351fe
-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
-#: ../../networking/virtual_private_cloud_config.rst:1058
-# a84c70dc6b4f4d7c8f5a2d1f82b59355
-# 05fb941cda1540a6ae76a68c80d28164
-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
-#: ../../networking/ip_forwarding_and_firewalling.rst:265
-# f62541afe2764660ba42de5ab1903be0
-# ee9101e2c97447d4b23f89177c60e7ab
-msgid "Fill in the following:"
-msgstr ""
-
-#: ../../networking/external_firewalls_and_load_balancers.rst:279
-#: ../../networking/virtual_private_cloud_config.rst:1064
-#: ../../networking/virtual_private_cloud_config.rst:1249
-# 9d106d6a229045acbfc2622c0c395bd9
-# 48072a5bd67b4fc2b091903b2930ef20
-# 23e879002b734874bb3fb8648d82ec9f
-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
-#: ../../networking/virtual_private_cloud_config.rst:1069
-# 61dc53b8703148608a98d96de9b2f3f7
-# 95e57b758d354580b0723b1cf69b1ad9
-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
-#: ../../networking/isolation_in_advanced_zone_with_vlan.rst:97
-#: ../../networking/multiple_guest_networks.rst:88
-# f97b092a261142629f674c1cf40ee949
-# ad67b66852ee445b847bec89936c0d02
-# 7d8b8d41cfa04ea0b337a64b1206ae92
-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: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 ""
-
-#: ../../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 a

<TRUNCATED>

Mime
View raw message