You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cloudstack.apache.org by se...@apache.org on 2014/06/30 11:46:03 UTC
[5/8] Push tx/config and new pot files in preparation for 4.4 RC
http://git-wip-us.apache.org/repos/asf/cloudstack-docs-admin/blob/fffde327/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
new file mode 100644
index 0000000..9ab8fd5
--- /dev/null
+++ b/source/locale/pot/networking/global_server_load_balancing.pot
@@ -0,0 +1,573 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C)
+# This file is distributed under the same license as the Apache CloudStack Administration Documentation package.
+# FIRST AUTHOR <EM...@ADDRESS>, YEAR.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: Apache CloudStack Administration Documentation 4\n"
+"Report-Msgid-Bugs-To: \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 <EM...@ADDRESS>\n"
+"Language-Team: LANGUAGE <LL...@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"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/fffde327/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
new file mode 100644
index 0000000..9fceb15
--- /dev/null
+++ b/source/locale/pot/networking/guest_ip_ranges.pot
@@ -0,0 +1,33 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C)
+# This file is distributed under the same license as the Apache CloudStack Administration Documentation package.
+# FIRST AUTHOR <EM...@ADDRESS>, YEAR.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: Apache CloudStack Administration Documentation 4\n"
+"Report-Msgid-Bugs-To: \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 <EM...@ADDRESS>\n"
+"Language-Team: LANGUAGE <LL...@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"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/fffde327/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
new file mode 100644
index 0000000..40f7679
--- /dev/null
+++ b/source/locale/pot/networking/guest_traffic.pot
@@ -0,0 +1,53 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C)
+# This file is distributed under the same license as the Apache CloudStack Administration Documentation package.
+# FIRST AUTHOR <EM...@ADDRESS>, YEAR.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: Apache CloudStack Administration Documentation 4\n"
+"Report-Msgid-Bugs-To: \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 <EM...@ADDRESS>\n"
+"Language-Team: LANGUAGE <LL...@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"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/fffde327/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
new file mode 100644
index 0000000..2d92364
--- /dev/null
+++ b/source/locale/pot/networking/inter_vlan_routing.pot
@@ -0,0 +1,118 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C)
+# This file is distributed under the same license as the Apache CloudStack Administration Documentation package.
+# FIRST AUTHOR <EM...@ADDRESS>, YEAR.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: Apache CloudStack Administration Documentation 4\n"
+"Report-Msgid-Bugs-To: \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 <EM...@ADDRESS>\n"
+"Language-Team: LANGUAGE <LL...@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"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 ""
+
http://git-wip-us.apache.org/repos/asf/cloudstack-docs-admin/blob/fffde327/source/locale/pot/networking/ip_forwarding_and_firewalling.pot
----------------------------------------------------------------------
diff --git a/source/locale/pot/networking/ip_forwarding_and_firewalling.pot b/source/locale/pot/networking/ip_forwarding_and_firewalling.pot
new file mode 100644
index 0000000..9246e03
--- /dev/null
+++ b/source/locale/pot/networking/ip_forwarding_and_firewalling.pot
@@ -0,0 +1,393 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C)
+# This file is distributed under the same license as the Apache CloudStack Administration Documentation package.
+# FIRST AUTHOR <EM...@ADDRESS>, YEAR.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: Apache CloudStack Administration Documentation 4\n"
+"Report-Msgid-Bugs-To: \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 <EM...@ADDRESS>\n"
+"Language-Team: LANGUAGE <LL...@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#: ../../networking/ip_forwarding_and_firewalling.rst:18
+# 3ec46c2d67cb4acc87705b3f0985e5c8
+msgid "IP Forwarding and Firewalling"
+msgstr ""
+
+#: ../../networking/ip_forwarding_and_firewalling.rst:20
+# 5bb709bf233742ce8f3a83dc5ce7cf26
+msgid "By default, all incoming traffic to the public IP address is rejected. All outgoing traffic from the guests is also blocked by default."
+msgstr ""
+
+#: ../../networking/ip_forwarding_and_firewalling.rst:23
+# 83f985061e4e4301aa5ce50049ea4565
+msgid "To allow outgoing traffic, follow the procedure in :ref:`egress-fw-rules`."
+msgstr ""
+
+#: ../../networking/ip_forwarding_and_firewalling.rst:25
+# 1328a8040ae7487b8f7ed1dcaaf5a596
+msgid "To allow incoming traffic, users may set up firewall rules and/or port forwarding rules. For example, you can use a firewall rule to open a range of ports on the public IP address, such as 33 through 44. Then use port forwarding rules to direct traffic from individual ports within that range to specific ports on user VMs. For example, one port forwarding rule could route incoming traffic on the public IP's port 33 to port 100 on one user VM's private IP."
+msgstr ""
+
+#: ../../networking/ip_forwarding_and_firewalling.rst:35
+# 88ee727310bb4a5789291e8e48578dab
+msgid "Firewall Rules"
+msgstr ""
+
+#: ../../networking/ip_forwarding_and_firewalling.rst:37
+# 073cb21345c44ce2a3f2ce3446d4ad3a
+msgid "By default, all incoming traffic to the public IP address is rejected by the firewall. To allow external traffic, you can open firewall ports by specifying firewall rules. You can optionally specify one or more CIDRs to filter the source IPs. This is useful when you want to allow only incoming requests from certain IP addresses."
+msgstr ""
+
+#: ../../networking/ip_forwarding_and_firewalling.rst:43
+# b43e4fc4f43841c9aebd342bbd60b33d
+msgid "You cannot use firewall rules to open ports for an elastic IP address. When elastic IP is used, outside access is instead controlled through the use of security groups. See `\"Adding a Security Group\" <#adding-a-security-group>`_."
+msgstr ""
+
+#: ../../networking/ip_forwarding_and_firewalling.rst:48
+# 36b1e8acd3ef4b1cb7a7ffd1f60599c5
+msgid "In an advanced zone, you can also create egress firewall rules by using the virtual router. For more information, see \":ref:`egress-fw-rules`\"."
+msgstr ""
+
+#: ../../networking/ip_forwarding_and_firewalling.rst:51
+# 2aeb084c075b4451b0911c2a6baf0f84
+msgid "Firewall rules can be created using the Firewall tab in the Management Server UI. This tab is not displayed by default when CloudStack is installed. To display the Firewall tab, the CloudStack administrator must set the global configuration parameter firewall.rule.ui.enabled to \"true.\""
+msgstr ""
+
+#: ../../networking/ip_forwarding_and_firewalling.rst:57
+# e1408eeb730f4709bbba8852f79807fd
+msgid "To create a firewall rule:"
+msgstr ""
+
+#: ../../networking/ip_forwarding_and_firewalling.rst:59
+#: ../../networking/ip_forwarding_and_firewalling.rst:132
+#: ../../networking/ip_forwarding_and_firewalling.rst:245
+# 098b22043ec643559c039b39aa24d618
+# f62479b013c241a791c42b8843bd140d
+# c384f1b44804485fba23fe018c16683e
+msgid "Log in to the CloudStack UI as an administrator or end user."
+msgstr ""
+
+#: ../../networking/ip_forwarding_and_firewalling.rst:61
+#: ../../networking/ip_forwarding_and_firewalling.rst:134
+# a633160d3ee343639365b9067af58eb1
+# c6c7495d464a4262ace3361c7cce9b5b
+msgid "In the left navigation, choose Network."
+msgstr ""
+
+#: ../../networking/ip_forwarding_and_firewalling.rst:63
+# ff56e69810c34ee4a08280a7ef06cfbb
+msgid "Click the name of the network where you want to work with."
+msgstr ""
+
+#: ../../networking/ip_forwarding_and_firewalling.rst:65
+# d546be88025a4254b8eecf1f0b16bdf0
+msgid "Click View IP Addresses."
+msgstr ""
+
+#: ../../networking/ip_forwarding_and_firewalling.rst:67
+# 0c60a7fde5644f9188c0bf190c166890
+msgid "Click the IP address you want to work with."
+msgstr ""
+
+#: ../../networking/ip_forwarding_and_firewalling.rst:69
+# 0e0775a902554fa68fc54157ed73ed0a
+msgid "Click the Configuration tab and fill in the following values."
+msgstr ""
+
+#: ../../networking/ip_forwarding_and_firewalling.rst:71
+# 8bb21f2deca7442683f782de4a83935f
+msgid "**Source CIDR**: (Optional) To accept only traffic from IP addresses within a particular address block, enter a CIDR or a comma-separated list of CIDRs. Example: 192.168.0.0/22. Leave empty to allow all CIDRs."
+msgstr ""
+
+#: ../../networking/ip_forwarding_and_firewalling.rst:76
+# 4cb05fbe28ae408a8df34014da711575
+msgid "**Protocol**: The communication protocol in use on the opened port(s)."
+msgstr ""
+
+#: ../../networking/ip_forwarding_and_firewalling.rst:79
+# e59d4d2a187f4510a91409fac5cfb51c
+msgid "**Start Port and End Port**: The port(s) you want to open on the firewall. If you are opening a single port, use the same number in both fields"
+msgstr ""
+
+#: ../../networking/ip_forwarding_and_firewalling.rst:83
+# 3274875afce44bbe9d7017bb4e2fc2b2
+msgid "**ICMP Type and ICMP Code**: Used only if Protocol is set to ICMP. Provide the type and code required by the ICMP protocol to fill out the ICMP header. Refer to ICMP documentation for more details if you are not sure what to enter"
+msgstr ""
+
+#: ../../networking/ip_forwarding_and_firewalling.rst:88
+#: ../../networking/ip_forwarding_and_firewalling.rst:163
+#: ../../networking/ip_forwarding_and_firewalling.rst:276
+# 41821a610d844daf8255026b71299059
+# 1d39fcb3a5e34d769f89885db9866836
+# 2319658c89b74a0294ce8f0a253a4d53
+msgid "Click Add."
+msgstr ""
+
+#: ../../networking/ip_forwarding_and_firewalling.rst:94
+# eec2e0a57feb4eca85c58ac1b58b228b
+msgid "Egress Firewall Rules in an Advanced Zone"
+msgstr ""
+
+#: ../../networking/ip_forwarding_and_firewalling.rst:96
+# 3bae6d1e0fb543beaeb466c40aeddfc3
+msgid "The egress traffic originates from a private network to a public network, such as the Internet. By default, the egress traffic is blocked in default network offerings, so no outgoing traffic is allowed from a guest network to the Internet. However, you can control the egress traffic in an Advanced zone by creating egress firewall rules. When an egress firewall rule is applied, the traffic specific to the rule is allowed and the remaining traffic is blocked. When all the firewall rules are removed the default policy, Block, is applied."
+msgstr ""
+
+#: ../../networking/ip_forwarding_and_firewalling.rst:107
+# 80fbdba2a681463894376f620458c160
+msgid "Prerequisites and Guidelines"
+msgstr ""
+
+#: ../../networking/ip_forwarding_and_firewalling.rst:109
+# 998ae537c5664319b836e769ab967fc3
+msgid "Consider the following scenarios to apply egress firewall rules:"
+msgstr ""
+
+#: ../../networking/ip_forwarding_and_firewalling.rst:111
+# 18a68e97f28f4f7898b92513d34e5e26
+msgid "Egress firewall rules are supported on Juniper SRX and virtual router."
+msgstr ""
+
+#: ../../networking/ip_forwarding_and_firewalling.rst:114
+# a4eaae6cb4474e5a8182092404f48116
+msgid "The egress firewall rules are not supported on shared networks."
+msgstr ""
+
+#: ../../networking/ip_forwarding_and_firewalling.rst:116
+# 85bdd2e7a708485bae147bfa93cdcb1b
+msgid "Allow the egress traffic from specified source CIDR. The Source CIDR is part of guest network CIDR."
+msgstr ""
+
+#: ../../networking/ip_forwarding_and_firewalling.rst:119
+# d9af348ce95e47a0bae91a55488b1155
+msgid "Allow the egress traffic with protocol TCP,UDP,ICMP, or ALL."
+msgstr ""
+
+#: ../../networking/ip_forwarding_and_firewalling.rst:121
+# 786d85af2e334cf5a8a25fc59dde7cb5
+msgid "Allow the egress traffic with protocol and destination port range. The port range is specified for TCP, UDP or for ICMP type and code."
+msgstr ""
+
+#: ../../networking/ip_forwarding_and_firewalling.rst:124
+# 8d9e5fa49cb648a6ad0b917f06176014
+msgid "The default policy is Allow for the new network offerings, whereas on upgrade existing network offerings with firewall service providers will have the default egress policy Deny."
+msgstr ""
+
+#: ../../networking/ip_forwarding_and_firewalling.rst:130
+# ee1ee0417255469abce66dbfd40f9611
+msgid "Configuring an Egress Firewall Rule"
+msgstr ""
+
+#: ../../networking/ip_forwarding_and_firewalling.rst:136
+# 4d43b047c25a4605acc888b025d376aa
+msgid "In Select view, choose Guest networks, then click the Guest network you want."
+msgstr ""
+
+#: ../../networking/ip_forwarding_and_firewalling.rst:139
+# 4c11dfc739f94ce0995b7c7bdf566e5d
+msgid "To add an egress rule, click the Egress rules tab and fill out the following fields to specify what type of traffic is allowed to be sent out of VM instances in this guest network:"
+msgstr ""
+
+#: ../../networking/ip_forwarding_and_firewalling.rst:143
+# a476fe8da41b43168b89c7b558afcb48
+msgid "|egress-firewall-rule.png|"
+msgstr ""
+
+#: ../../networking/ip_forwarding_and_firewalling.rst:145
+# d56527f1ac864c5c9d47df9e55c225cf
+msgid "**CIDR**: (Add by CIDR only) To send traffic only to the IP addresses within a particular address block, enter a CIDR or a comma-separated list of CIDRs. The CIDR is the base IP address of the destination. For example, 192.168.0.0/22. To allow all CIDRs, set to 0.0.0.0/0."
+msgstr ""
+
+#: ../../networking/ip_forwarding_and_firewalling.rst:151
+# c1e8fac9fa8046d8a9315511c011542e
+msgid "**Protocol**: The networking protocol that VMs uses to send outgoing traffic. The TCP and UDP protocols are typically used for data exchange and end-user communications. The ICMP protocol is typically used to send error messages or network monitoring data."
+msgstr ""
+
+#: ../../networking/ip_forwarding_and_firewalling.rst:156
+# 6b9d46d4c88d48c98d3fa4fcceb60e29
+msgid "**Start Port, End Port**: (TCP, UDP only) A range of listening ports that are the destination for the outgoing traffic. If you are opening a single port, use the same number in both fields."
+msgstr ""
+
+#: ../../networking/ip_forwarding_and_firewalling.rst:160
+# 17c266c56f194132a6fc948f3142e4bc
+msgid "**ICMP Type, ICMP Code**: (ICMP only) The type of message and error code that are sent."
+msgstr ""
+
+#: ../../networking/ip_forwarding_and_firewalling.rst:167
+# f0100304289f4a67b01e8f6c52976a10
+msgid "Configuring the Default Egress Policy"
+msgstr ""
+
+#: ../../networking/ip_forwarding_and_firewalling.rst:169
+# a802326f92404392beacd9675985c106
+msgid "The default egress policy for Isolated guest network is configured by using Network offering. Use the create network offering option to determine whether the default policy should be block or allow all the traffic to the public network from a guest network. Use this network offering to create the network. If no policy is specified, by default all the traffic is allowed from the guest network that you create by using this network offering."
+msgstr ""
+
+#: ../../networking/ip_forwarding_and_firewalling.rst:177
+# 9b5e480b6757449ab8272d3e7a691110
+msgid "You have two options: Allow and Deny."
+msgstr ""
+
+#: ../../networking/ip_forwarding_and_firewalling.rst:180
+# 9b8d4463d6024d8589cc801658fa7bab
+msgid "Allow"
+msgstr ""
+
+#: ../../networking/ip_forwarding_and_firewalling.rst:182
+# 01d29e0665f84d548d9f41399d9258d8
+msgid "If you select Allow for a network offering, by default egress traffic is allowed. However, when an egress rule is configured for a guest network, rules are applied to block the specified traffic and rest are allowed. If no egress rules are configured for the network, egress traffic is accepted."
+msgstr ""
+
+#: ../../networking/ip_forwarding_and_firewalling.rst:189
+# 63816b9551f04933aa99e27cc3dc34f1
+msgid "Deny"
+msgstr ""
+
+#: ../../networking/ip_forwarding_and_firewalling.rst:191
+# 1952d7735fb746a6834bbdeed4c1eaa9
+msgid "If you select Deny for a network offering, by default egress traffic for the guest network is blocked. However, when an egress rules is configured for a guest network, rules are applied to allow the specified traffic. While implementing a guest network, CloudStack adds the firewall egress rule specific to the default egress policy for the guest network."
+msgstr ""
+
+#: ../../networking/ip_forwarding_and_firewalling.rst:198
+# 238db98415e74782937deddd3970b285
+msgid "This feature is supported only on virtual router and Juniper SRX."
+msgstr ""
+
+#: ../../networking/ip_forwarding_and_firewalling.rst:200
+# e460df960d61405db56e64d21a8c43d7
+msgid "Create a network offering with your desirable default egress policy:"
+msgstr ""
+
+#: ../../networking/ip_forwarding_and_firewalling.rst:202
+# 5271ad0a1d4a4a27aa5597b044b42acf
+msgid "Log in with admin privileges to the CloudStack UI."
+msgstr ""
+
+#: ../../networking/ip_forwarding_and_firewalling.rst:204
+# fd49a59627284ffda66fef7096eaa709
+msgid "In the left navigation bar, click Service Offerings."
+msgstr ""
+
+#: ../../networking/ip_forwarding_and_firewalling.rst:206
+# 7fce8b96f6e64727bb6063766c828bdd
+msgid "In Select Offering, choose Network Offering."
+msgstr ""
+
+#: ../../networking/ip_forwarding_and_firewalling.rst:208
+# ef8895c197ff4343b04aecc73b5a9294
+msgid "Click Add Network Offering."
+msgstr ""
+
+#: ../../networking/ip_forwarding_and_firewalling.rst:210
+# abb73d0d766d4d32a4bbe32137193cad
+msgid "In the dialog, make necessary choices, including firewall provider."
+msgstr ""
+
+#: ../../networking/ip_forwarding_and_firewalling.rst:213
+# 932c30480a1f4e3ea92f06ba4296ae45
+msgid "In the Default egress policy field, specify the behaviour."
+msgstr ""
+
+#: ../../networking/ip_forwarding_and_firewalling.rst:215
+# 41d012a83e774bdeaeac42e5b44d851c
+msgid "Click OK."
+msgstr ""
+
+#: ../../networking/ip_forwarding_and_firewalling.rst:217
+# 5a1192bc5c8a4c3c930879e56c5d58bb
+msgid "Create an isolated network by using this network offering."
+msgstr ""
+
+#: ../../networking/ip_forwarding_and_firewalling.rst:219
+# 3918ff66d4914376a4707b9db470a027
+msgid "Based on your selection, the network will have the egress public traffic blocked or allowed."
+msgstr ""
+
+#: ../../networking/ip_forwarding_and_firewalling.rst:224
+# 29ffedbd547e431f95d82b075df5ea66
+msgid "Port Forwarding"
+msgstr ""
+
+#: ../../networking/ip_forwarding_and_firewalling.rst:226
+# d9efd9df178e4f7c8d81b2ba24a9fdbb
+msgid "A port forward service is a set of port forwarding rules that define a policy. A port forward service is then applied to one or more guest VMs. The guest VM then has its inbound network access managed according to the policy defined by the port forwarding service. You can optionally specify one or more CIDRs to filter the source IPs. This is useful when you want to allow only incoming requests from certain IP addresses to be forwarded."
+msgstr ""
+
+#: ../../networking/ip_forwarding_and_firewalling.rst:234
+# ae4f5d3e4bc24f8584c17c3057688144
+msgid "A guest VM can be in any number of port forward services. Port forward services can be defined but have no members. If a guest VM is part of more than one network, port forwarding rules will function only if they are defined on the default network"
+msgstr ""
+
+#: ../../networking/ip_forwarding_and_firewalling.rst:239
+# 89ce910349884d8ea8a7b4f6aee10613
+msgid "You cannot use port forwarding to open ports for an elastic IP address. When elastic IP is used, outside access is instead controlled through the use of security groups. See Security Groups."
+msgstr ""
+
+#: ../../networking/ip_forwarding_and_firewalling.rst:243
+# 263627f6e1de45999d0e9ab68c8a1a2d
+msgid "To set up port forwarding:"
+msgstr ""
+
+#: ../../networking/ip_forwarding_and_firewalling.rst:247
+# 41c9b9f2473e4b5aa0d8ea3c54e45b1b
+msgid "If you have not already done so, add a public IP address range to a zone in CloudStack. See Adding a Zone and Pod in the Installation Guide."
+msgstr ""
+
+#: ../../networking/ip_forwarding_and_firewalling.rst:251
+# 2c98fbd961df4ef28a276b3ccf1d53c0
+msgid "Add one or more VM instances to CloudStack."
+msgstr ""
+
+#: ../../networking/ip_forwarding_and_firewalling.rst:253
+# 17a544cc6c8a42cbaef47575f1029173
+msgid "In the left navigation bar, click Network."
+msgstr ""
+
+#: ../../networking/ip_forwarding_and_firewalling.rst:255
+# ade84b4f63694fadbe6c835b52ba796f
+msgid "Click the name of the guest network where the VMs are running."
+msgstr ""
+
+#: ../../networking/ip_forwarding_and_firewalling.rst:257
+# 48ab8bf9d7e04ca7a13eaf58eeead278
+msgid "Choose an existing IP address or acquire a new IP address. See `\"Acquiring a New IP Address\" <#acquiring-a-new-ip-address>`_. Click the name of the IP address in the list."
+msgstr ""
+
+#: ../../networking/ip_forwarding_and_firewalling.rst:261
+# da392889cd304ce8973c2b4b8341665b
+msgid "Click the Configuration tab."
+msgstr ""
+
+#: ../../networking/ip_forwarding_and_firewalling.rst:263
+# 4d02af0497b544d89616ff1ddf286767
+msgid "In the Port Forwarding node of the diagram, click View All."
+msgstr ""
+
+#: ../../networking/ip_forwarding_and_firewalling.rst:265
+# ee9101e2c97447d4b23f89177c60e7ab
+msgid "Fill in the following:"
+msgstr ""
+
+#: ../../networking/ip_forwarding_and_firewalling.rst:267
+# e9d9402255ae405781f85b32409d3654
+msgid "**Public Port**: The port to which public traffic will be addressed on the IP address you acquired in the previous step."
+msgstr ""
+
+#: ../../networking/ip_forwarding_and_firewalling.rst:270
+# bf8d351e8ca649ca9931311f402ea7bc
+msgid "**Private Port**: The port on which the instance is listening for forwarded public traffic."
+msgstr ""
+
+#: ../../networking/ip_forwarding_and_firewalling.rst:273
+# 5140efc173fd46e194d6c4827a8a67fc
+msgid "**Protocol**: The communication protocol in use between the two ports"
+msgstr ""
+
http://git-wip-us.apache.org/repos/asf/cloudstack-docs-admin/blob/fffde327/source/locale/pot/networking/ip_load_balancing.pot
----------------------------------------------------------------------
diff --git a/source/locale/pot/networking/ip_load_balancing.pot b/source/locale/pot/networking/ip_load_balancing.pot
new file mode 100644
index 0000000..6577685
--- /dev/null
+++ b/source/locale/pot/networking/ip_load_balancing.pot
@@ -0,0 +1,48 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C)
+# This file is distributed under the same license as the Apache CloudStack Administration Documentation package.
+# FIRST AUTHOR <EM...@ADDRESS>, YEAR.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: Apache CloudStack Administration Documentation 4\n"
+"Report-Msgid-Bugs-To: \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 <EM...@ADDRESS>\n"
+"Language-Team: LANGUAGE <LL...@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#: ../../networking/ip_load_balancing.rst:18
+# 974ac2a4e2dd4641920f5361833b3e12
+msgid "IP Load Balancing"
+msgstr ""
+
+#: ../../networking/ip_load_balancing.rst:20
+# 7eaede5161a04e0cbb6a4b15fc2de3b2
+msgid "The user may choose to associate the same public IP for multiple guests. CloudStack implements a TCP-level load balancer with the following policies."
+msgstr ""
+
+#: ../../networking/ip_load_balancing.rst:24
+# 8c044fa0f1714d63815a08d7a658b08d
+msgid "Round-robin"
+msgstr ""
+
+#: ../../networking/ip_load_balancing.rst:26
+# 6732c79a9ecf4eec91f6ddea4d55833a
+msgid "Least connection"
+msgstr ""
+
+#: ../../networking/ip_load_balancing.rst:28
+# 28c3b6fa228545e382ed84cceaf1666a
+msgid "Source IP"
+msgstr ""
+
+#: ../../networking/ip_load_balancing.rst:30
+# 0eac6f2afde349909f9ee8d0148a99b6
+msgid "This is similar to port forwarding but the destination may be multiple IP addresses."
+msgstr ""
+
http://git-wip-us.apache.org/repos/asf/cloudstack-docs-admin/blob/fffde327/source/locale/pot/networking/ip_reservation_in_guest_networks.pot
----------------------------------------------------------------------
diff --git a/source/locale/pot/networking/ip_reservation_in_guest_networks.pot b/source/locale/pot/networking/ip_reservation_in_guest_networks.pot
new file mode 100644
index 0000000..97b3f79
--- /dev/null
+++ b/source/locale/pot/networking/ip_reservation_in_guest_networks.pot
@@ -0,0 +1,238 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C)
+# This file is distributed under the same license as the Apache CloudStack Administration Documentation package.
+# FIRST AUTHOR <EM...@ADDRESS>, YEAR.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: Apache CloudStack Administration Documentation 4\n"
+"Report-Msgid-Bugs-To: \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 <EM...@ADDRESS>\n"
+"Language-Team: LANGUAGE <LL...@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#: ../../networking/ip_reservation_in_guest_networks.rst:18
+# 25e21d9bd50e4db29764c09ec3255ea1
+msgid "IP Reservation in Isolated Guest Networks"
+msgstr ""
+
+#: ../../networking/ip_reservation_in_guest_networks.rst:20
+# f043acb1e27b49aebecf48876dca90d4
+msgid "In isolated guest networks, a part of the guest IP address space can be reserved for non-CloudStack VMs or physical servers. To do so, you configure a range of Reserved IP addresses by specifying the CIDR when a guest network is in Implemented state. If your customers wish to have non-CloudStack controlled VMs or physical servers on the same network, they can share a part of the IP address space that is primarily provided to the guest network."
+msgstr ""
+
+#: ../../networking/ip_reservation_in_guest_networks.rst:28
+# fe77cb19c33a475f9389f57e62e466e0
+msgid "In an Advanced zone, an IP address range or a CIDR is assigned to a network when the network is defined. The CloudStack virtual router acts as the DHCP server and uses CIDR for assigning IP addresses to the guest VMs. If you decide to reserve CIDR for non-CloudStack purposes, you can specify a part of the IP address range or the CIDR that should only be allocated by the DHCP service of the virtual router to the guest VMs created in CloudStack. The remaining IPs in that network are called Reserved IP Range. When IP reservation is configured, the administrator can add additional VMs or physical servers that are not part of CloudStack to the same network and assign them the Reserved IP addresses. CloudStack guest VMs cannot acquire IPs from the Reserved IP Range."
+msgstr ""
+
+#: ../../networking/ip_reservation_in_guest_networks.rst:43
+# 9428ab05bfce48cb9dce92078998854c
+msgid "IP Reservation Considerations"
+msgstr ""
+
+#: ../../networking/ip_reservation_in_guest_networks.rst:45
+# 5780d0b48e6f44cbb972018a31489ebb
+msgid "Consider the following before you reserve an IP range for non-CloudStack machines:"
+msgstr ""
+
+#: ../../networking/ip_reservation_in_guest_networks.rst:48
+# cc50e370af0c450588c711e282c0ac93
+msgid "IP Reservation is supported only in Isolated networks."
+msgstr ""
+
+#: ../../networking/ip_reservation_in_guest_networks.rst:50
+# 9543f099f9de4fc3a8a815cd3cb04f40
+msgid "IP Reservation can be applied only when the network is in Implemented state."
+msgstr ""
+
+#: ../../networking/ip_reservation_in_guest_networks.rst:53
+# c7bc13975b37474299e4a7a65c56ed75
+msgid "No IP Reservation is done by default."
+msgstr ""
+
+#: ../../networking/ip_reservation_in_guest_networks.rst:55
+# f7a970b25ef94f48bc75a5c8a5fd0a0c
+msgid "Guest VM CIDR you specify must be a subset of the network CIDR."
+msgstr ""
+
+#: ../../networking/ip_reservation_in_guest_networks.rst:57
+# a96a64591c4d498ca7c95b1458def6f3
+msgid "Specify a valid Guest VM CIDR. IP Reservation is applied only if no active IPs exist outside the Guest VM CIDR."
+msgstr ""
+
+#: ../../networking/ip_reservation_in_guest_networks.rst:60
+# 0710411bb18c4764970dffcc49fe5dab
+msgid "You cannot apply IP Reservation if any VM is alloted with an IP address that is outside the Guest VM CIDR."
+msgstr ""
+
+#: ../../networking/ip_reservation_in_guest_networks.rst:63
+# ba005fe1c84e4e5d8d8b2f2cbd904deb
+msgid "To reset an existing IP Reservation, apply IP reservation by specifying the value of network CIDR in the CIDR field."
+msgstr ""
+
+#: ../../networking/ip_reservation_in_guest_networks.rst:66
+# 23bef4e190a54c2298a52b3acb439c57
+msgid "For example, the following table describes three scenarios of guest network creation:"
+msgstr ""
+
+#: ../../networking/ip_reservation_in_guest_networks.rst:70
+# fd80ccd9ee7947c6a41f35a77766ba87
+msgid "Case"
+msgstr ""
+
+#: ../../networking/ip_reservation_in_guest_networks.rst:70
+# 1b0d9124efce41c8bf2ff9c04f471053
+msgid "CIDR"
+msgstr ""
+
+#: ../../networking/ip_reservation_in_guest_networks.rst:70
+# 340cf6747d6449b09015c49437828468
+msgid "Network CIDR"
+msgstr ""
+
+#: ../../networking/ip_reservation_in_guest_networks.rst:70
+# ca9e89e3707343c6a6bb2e2c52dc4acd
+msgid "Reserved IP Range for Non-CloudStack VMs"
+msgstr ""
+
+#: ../../networking/ip_reservation_in_guest_networks.rst:70
+# e1395f7f735643f98e49f71acb302533
+msgid "Description"
+msgstr ""
+
+#: ../../networking/ip_reservation_in_guest_networks.rst:72
+# bfc721eb783042dbbd4049d97eeae50c
+msgid "1"
+msgstr ""
+
+#: ../../networking/ip_reservation_in_guest_networks.rst:72
+#: ../../networking/ip_reservation_in_guest_networks.rst:73
+#: ../../networking/ip_reservation_in_guest_networks.rst:76
+# 07110191079642298d8d53f83f4a6fe7
+# a0e61e48b84a4bb297fead377ce043cf
+# d64231917df74c5189732a5fedd1d141
+msgid "10.1.1.0/24"
+msgstr ""
+
+#: ../../networking/ip_reservation_in_guest_networks.rst:72
+#: ../../networking/ip_reservation_in_guest_networks.rst:72
+#: ../../networking/ip_reservation_in_guest_networks.rst:76
+#: ../../networking/ip_reservation_in_guest_networks.rst:76
+# 865ea8d88306424bab506a500520c22e
+# 184b1eac870b483f910546a5d5b37906
+# 70f4868471d54ac882b8093eb1db9f74
+# 3c040050888741f09b3cee5a8482aca4
+msgid "None"
+msgstr ""
+
+#: ../../networking/ip_reservation_in_guest_networks.rst:72
+# 24e526351c7b4686b16e030bc869d399
+msgid "No IP Reservation."
+msgstr ""
+
+#: ../../networking/ip_reservation_in_guest_networks.rst:73
+# 81f560cf3b4c47bbb2b781add102de88
+msgid "2"
+msgstr ""
+
+#: ../../networking/ip_reservation_in_guest_networks.rst:73
+# 725f92aed0d44be3bb5865f246acc29d
+msgid "10.1.1.0/26"
+msgstr ""
+
+#: ../../networking/ip_reservation_in_guest_networks.rst:73
+# 02e4012c8ce94d95a0c5e4d5088637fd
+msgid "10.1.1.64 to 10.1.1.254"
+msgstr ""
+
+#: ../../networking/ip_reservation_in_guest_networks.rst:73
+# 8fe36bed92d2475bbdd0fa903eb8c54b
+msgid "IP Reservation configured by the UpdateNetwork API with guestvmcidr=10.1.1.0/26 or enter 10.1.1.0/26 in the CIDR field in the UI."
+msgstr ""
+
+#: ../../networking/ip_reservation_in_guest_networks.rst:76
+# e2c363737b654228a0ac0581ba4c55c8
+msgid "3"
+msgstr ""
+
+#: ../../networking/ip_reservation_in_guest_networks.rst:76
+# 139e9ad2489d40738198ebfac4b14c45
+msgid "Removing IP Reservation by the UpdateNetwork API with guestvmcidr=10.1.1.0/24 or enter 10.1.1.0/24 in the CIDR field in the UI."
+msgstr ""
+
+#: ../../networking/ip_reservation_in_guest_networks.rst:83
+# 43bbd9a15792420cb8b1e694ad792cf2
+msgid "Limitations"
+msgstr ""
+
+#: ../../networking/ip_reservation_in_guest_networks.rst:85
+# 1ed6f796d3f04ed0b5c96512bc673c25
+msgid "The IP Reservation is not supported if active IPs that are found outside the Guest VM CIDR."
+msgstr ""
+
+#: ../../networking/ip_reservation_in_guest_networks.rst:88
+# 28ed30440a3543f6b7744261f3f5c2e0
+msgid "Upgrading network offering which causes a change in CIDR (such as upgrading an offering with no external devices to one with external devices) IP Reservation becomes void if any. Reconfigure IP Reservation in the new re-implemeted network."
+msgstr ""
+
+#: ../../networking/ip_reservation_in_guest_networks.rst:95
+# f9aacfd3f1a94c7c8d3ca0910da962a9
+msgid "Best Practices"
+msgstr ""
+
+#: ../../networking/ip_reservation_in_guest_networks.rst:97
+# c5d0950bef8a49ce9b373d64fcf22b86
+msgid "Apply IP Reservation to the guest network as soon as the network state changes to Implemented. If you apply reservation soon after the first guest VM is deployed, lesser conflicts occurs while applying reservation."
+msgstr ""
+
+#: ../../networking/ip_reservation_in_guest_networks.rst:104
+# 636d85b86d5a460788a233fd1cb49014
+msgid "Reserving an IP Range"
+msgstr ""
+
+#: ../../networking/ip_reservation_in_guest_networks.rst:106
+# 34eb58849cb141e9898291a434cc05ba
+msgid "Log in to the CloudStack UI as an administrator or end user."
+msgstr ""
+
+#: ../../networking/ip_reservation_in_guest_networks.rst:108
+# 3dc484e1bd5145259125fe0fcf8ccf8c
+msgid "In the left navigation, choose Network."
+msgstr ""
+
+#: ../../networking/ip_reservation_in_guest_networks.rst:110
+# e4559a4e7ddf4812890314b955dae344
+msgid "Click the name of the network you want to modify."
+msgstr ""
+
+#: ../../networking/ip_reservation_in_guest_networks.rst:112
+# 9119b8d7ea884da4b996f8a191d30e0b
+msgid "In the Details tab, click Edit. |ip-edit-icon.png|"
+msgstr ""
+
+#: ../../networking/ip_reservation_in_guest_networks.rst:114
+# 31eaf6bfc27e465e950da4b920fbad80
+msgid "The CIDR field changes to editable one."
+msgstr ""
+
+#: ../../networking/ip_reservation_in_guest_networks.rst:116
+# f29831c8666d45218af0ae6769e46fff
+msgid "In CIDR, specify the Guest VM CIDR."
+msgstr ""
+
+#: ../../networking/ip_reservation_in_guest_networks.rst:118
+# 41acec1236df4ddbad427f23127244b1
+msgid "Click Apply."
+msgstr ""
+
+#: ../../networking/ip_reservation_in_guest_networks.rst:120
+# 8213a6fd8f414bd2b710a4ee77b167ae
+msgid "Wait for the update to complete. The Network CIDR and the Reserved IP Range are displayed on the Details page."
+msgstr ""
+
http://git-wip-us.apache.org/repos/asf/cloudstack-docs-admin/blob/fffde327/source/locale/pot/networking/isolation_in_advanced_zone_with_vlan.pot
----------------------------------------------------------------------
diff --git a/source/locale/pot/networking/isolation_in_advanced_zone_with_vlan.pot b/source/locale/pot/networking/isolation_in_advanced_zone_with_vlan.pot
new file mode 100644
index 0000000..160f2c4
--- /dev/null
+++ b/source/locale/pot/networking/isolation_in_advanced_zone_with_vlan.pot
@@ -0,0 +1,273 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C)
+# This file is distributed under the same license as the Apache CloudStack Administration Documentation package.
+# FIRST AUTHOR <EM...@ADDRESS>, YEAR.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: Apache CloudStack Administration Documentation 4\n"
+"Report-Msgid-Bugs-To: \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 <EM...@ADDRESS>\n"
+"Language-Team: LANGUAGE <LL...@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#: ../../networking/isolation_in_advanced_zone_with_vlan.rst:18
+# 2ce5e59640934ab387652df180ce1583
+msgid "Isolation in Advanced Zone Using Private VLAN"
+msgstr ""
+
+#: ../../networking/isolation_in_advanced_zone_with_vlan.rst:20
+# 813ada1771994469abac6b243cbc4ed6
+msgid "Isolation of guest traffic in shared networks can be achieved by using Private VLANs (PVLAN). PVLANs provide Layer 2 isolation between ports within the same VLAN. In a PVLAN-enabled shared network, a user VM cannot reach other user VM though they can reach the DHCP server and gateway, this would in turn allow users to control traffic within a network and help them deploy multiple applications without communication between application as well as prevent communication with other users' VMs."
+msgstr ""
+
+#: ../../networking/isolation_in_advanced_zone_with_vlan.rst:29
+# 1f6fb3f08ede4dbcbd7c9017afd047dd
+msgid "Isolate VMs in a shared networks by using Private VLANs."
+msgstr ""
+
+#: ../../networking/isolation_in_advanced_zone_with_vlan.rst:31
+# c578b86e668046b18652e81289fd1811
+msgid "Supported on KVM, XenServer, and VMware hypervisors"
+msgstr ""
+
+#: ../../networking/isolation_in_advanced_zone_with_vlan.rst:33
+# f410d2d58c4b4e91b95fec05d57cf0b8
+msgid "PVLAN-enabled shared network can be a part of multiple networks of a guest VM."
+msgstr ""
+
+#: ../../networking/isolation_in_advanced_zone_with_vlan.rst:38
+# 23d9d81e853644d8a8e311853c02a801
+msgid "About Private VLAN"
+msgstr ""
+
+#: ../../networking/isolation_in_advanced_zone_with_vlan.rst:40
+# a83e1c8b0ee2433b8776507d78fdd2b4
+msgid "In an Ethernet switch, a VLAN is a broadcast domain where hosts can establish direct communication with each another at Layer 2. Private VLAN is designed as an extension of VLAN standard to add further segmentation of the logical broadcast domain. A regular VLAN is a single broadcast domain, whereas a private VLAN partitions a larger VLAN broadcast domain into smaller sub-domains. A sub-domain is represented by a pair of VLANs: a Primary VLAN and a Secondary VLAN. The original VLAN that is being divided into smaller groups is called Primary, which implies that all VLAN pairs in a private VLAN share the same Primary VLAN. All the secondary VLANs exist only inside the Primary. Each Secondary VLAN has a specific VLAN ID associated to it, which differentiates one sub-domain from another."
+msgstr ""
+
+#: ../../networking/isolation_in_advanced_zone_with_vlan.rst:53
+# 4b8abf8fe1534c228333ad081037a150
+msgid "Three types of ports exist in a private VLAN domain, which essentially determine the behaviour of the participating hosts. Each ports will have its own unique set of rules, which regulate a connected host's ability to communicate with other connected host within the same private VLAN domain. Configure each host that is part of a PVLAN pair can be by using one of these three port designation:"
+msgstr ""
+
+#: ../../networking/isolation_in_advanced_zone_with_vlan.rst:60
+# d369217099d04739b0c778e20ac02897
+msgid "**Promiscuous**: A promiscuous port can communicate with all the interfaces, including the community and isolated host ports that belong to the secondary VLANs. In Promiscuous mode, hosts are connected to promiscuous ports and are able to communicate directly with resources on both primary and secondary VLAN. Routers, DHCP servers, and other trusted devices are typically attached to promiscuous ports."
+msgstr ""
+
+#: ../../networking/isolation_in_advanced_zone_with_vlan.rst:68
+# 1e0c762b123d404eaedebd33003ad75b
+msgid "**Isolated VLANs**: The ports within an isolated VLAN cannot communicate with each other at the layer-2 level. The hosts that are connected to Isolated ports can directly communicate only with the Promiscuous resources. If your customer device needs to have access only to a gateway router, attach it to an isolated port."
+msgstr ""
+
+#: ../../networking/isolation_in_advanced_zone_with_vlan.rst:74
+# 15e3128ebacd47afb6aa943d0f2a5df1
+msgid "**Community VLANs**: The ports within a community VLAN can communicate with each other and with the promiscuous ports, but they cannot communicate with the ports in other communities at the layer-2 level. In a Community mode, direct communication is permitted only with the hosts in the same community and those that are connected to the Primary PVLAN in promiscuous mode. If your customer has two devices that need to be isolated from other customers' devices, but to be able to communicate among themselves, deploy them in community ports."
+msgstr ""
+
+#: ../../networking/isolation_in_advanced_zone_with_vlan.rst:84
+# 6a977183f6864375ada79a287e63bab3
+msgid "For further reading:"
+msgstr ""
+
+#: ../../networking/isolation_in_advanced_zone_with_vlan.rst:86
+# ca791914bab54854b0b9c5cfdbb20be8
+msgid "`Understanding Private VLANs <http://www.cisco.com/en/US/docs/switches/lan/catalyst3750/software/release/12.2_25_see/configuration/guide/swpvlan.html#wp1038379>`_"
+msgstr ""
+
+#: ../../networking/isolation_in_advanced_zone_with_vlan.rst:89
+# e676f05feb9a46d6974a4ed7048edad2
+msgid "`Cisco Systems' Private VLANs: Scalable Security in a Multi-Client Environment <http://tools.ietf.org/html/rfc5517>`_"
+msgstr ""
+
+#: ../../networking/isolation_in_advanced_zone_with_vlan.rst:92
+# d5429c82db8a47aa82c6bf7602605f93
+msgid "`Private VLAN (PVLAN) on vNetwork Distributed Switch - Concept Overview (1010691) <http://kb.vmware.com>`_"
+msgstr ""
+
+#: ../../networking/isolation_in_advanced_zone_with_vlan.rst:97
+# ad67b66852ee445b847bec89936c0d02
+msgid "Prerequisites"
+msgstr ""
+
+#: ../../networking/isolation_in_advanced_zone_with_vlan.rst:99
+# 1f2367cd590b456b9590a9b2616c8ad5
+msgid "Use a PVLAN supported switch."
+msgstr ""
+
+#: ../../networking/isolation_in_advanced_zone_with_vlan.rst:101
+# f2c1161babac465c93d8ff531d97174d
+msgid "See `Private VLAN Catalyst Switch Support Matrix <http://www.cisco.com/en/US/products/hw/switches/ps708/products_tech_note09186a0080094830.shtml>`_ for more information."
+msgstr ""
+
+#: ../../networking/isolation_in_advanced_zone_with_vlan.rst:105
+# d6805374b5244b3da5f5a39bbb521739
+msgid "All the layer 2 switches, which are PVLAN-aware, are connected to each other, and one of them is connected to a router. All the ports connected to the host would be configured in trunk mode. Open Management VLAN, Primary VLAN (public) and Secondary Isolated VLAN ports. Configure the switch port connected to the router in PVLAN promiscuous trunk mode, which would translate an isolated VLAN to primary VLAN for the PVLAN-unaware router."
+msgstr ""
+
+#: ../../networking/isolation_in_advanced_zone_with_vlan.rst:113
+# 3afd52bf2fa3442b8f0721d8bca53715
+msgid "Note that only Cisco Catalyst 4500 has the PVLAN promiscuous trunk mode to connect both normal VLAN and PVLAN to a PVLAN-unaware switch. For the other Catalyst PVLAN support switch, connect the switch to upper switch by using cables, one each for a PVLAN pair."
+msgstr ""
+
+#: ../../networking/isolation_in_advanced_zone_with_vlan.rst:118
+# 5ce2b463414844099564cd171152b994
+msgid "Configure private VLAN on your physical switches out-of-band."
+msgstr ""
+
+#: ../../networking/isolation_in_advanced_zone_with_vlan.rst:120
+# 2cd1aebdb79742a3ab786e439ef69d89
+msgid "Before you use PVLAN on XenServer and KVM, enable Open vSwitch (OVS)."
+msgstr ""
+
+#: ../../networking/isolation_in_advanced_zone_with_vlan.rst:123
+# 23029ff5d87847c3b9a551d1755aae1a
+msgid "OVS on XenServer and KVM does not support PVLAN natively. Therefore, CloudStack managed to simulate PVLAN on OVS for XenServer and KVM by modifying the flow table."
+msgstr ""
+
+#: ../../networking/isolation_in_advanced_zone_with_vlan.rst:129
+# 1ab529fe7a53485da31a8085c5fc8181
+msgid "Creating a PVLAN-Enabled Guest Network"
+msgstr ""
+
+#: ../../networking/isolation_in_advanced_zone_with_vlan.rst:131
+# 73811e0470e04b63a31d32549a8c882b
+msgid "Log in to the CloudStack UI as administrator."
+msgstr ""
+
+#: ../../networking/isolation_in_advanced_zone_with_vlan.rst:133
+# f987d4525be34ae986962e374a48197f
+msgid "In the left navigation, choose Infrastructure."
+msgstr ""
+
+#: ../../networking/isolation_in_advanced_zone_with_vlan.rst:135
+# 81a7cad61d0c43e3989e9742e6efb902
+msgid "On Zones, click View More."
+msgstr ""
+
+#: ../../networking/isolation_in_advanced_zone_with_vlan.rst:137
+# 62eb1c2209d34440987b38dc999dad75
+msgid "Click the zone to which you want to add a guest network."
+msgstr ""
+
+#: ../../networking/isolation_in_advanced_zone_with_vlan.rst:139
+# aeaece1bb557450383b2b0c0930b8d39
+msgid "Click the Physical Network tab."
+msgstr ""
+
+#: ../../networking/isolation_in_advanced_zone_with_vlan.rst:141
+# bdccf5bb73ce4a58b074c7db9f09db19
+msgid "Click the physical network you want to work with."
+msgstr ""
+
+#: ../../networking/isolation_in_advanced_zone_with_vlan.rst:143
+# d325d3d79e0e41fd9ce93131ae2ea76a
+msgid "On the Guest node of the diagram, click Configure."
+msgstr ""
+
+#: ../../networking/isolation_in_advanced_zone_with_vlan.rst:145
+# 3254ff32eecc4e9b9ac57fc4f2219acd
+msgid "Click the Network tab."
+msgstr ""
+
+#: ../../networking/isolation_in_advanced_zone_with_vlan.rst:147
+# fdd056f25bee447e98028c9301071fd7
+msgid "Click Add guest network."
+msgstr ""
+
+#: ../../networking/isolation_in_advanced_zone_with_vlan.rst:149
+# f58f17bd25284897abbe7df71fc2c3fb
+msgid "The Add guest network window is displayed."
+msgstr ""
+
+#: ../../networking/isolation_in_advanced_zone_with_vlan.rst:151
+# 5e421fb492504766a709b728f4fc51e5
+msgid "Specify the following:"
+msgstr ""
+
+#: ../../networking/isolation_in_advanced_zone_with_vlan.rst:153
+# 606686347ca84fbc9a83c5f46c31d8ea
+msgid "**Name**: The name of the network. This will be visible to the user."
+msgstr ""
+
+#: ../../networking/isolation_in_advanced_zone_with_vlan.rst:156
+# 73bbe5e4075e43f39b388b8b267c5401
+msgid "**Description**: The short description of the network that can be displayed to users."
+msgstr ""
+
+#: ../../networking/isolation_in_advanced_zone_with_vlan.rst:159
+# 17a0fe7f48cc4af3bbe7b8e52b6f6d1b
+msgid "**VLAN ID**: The unique ID of the VLAN."
+msgstr ""
+
+#: ../../networking/isolation_in_advanced_zone_with_vlan.rst:161
+# 1656d47de54d42a788bc34e0a0c5f2e4
+msgid "**Secondary Isolated VLAN ID**: The unique ID of the Secondary Isolated VLAN."
+msgstr ""
+
+#: ../../networking/isolation_in_advanced_zone_with_vlan.rst:164
+# 22e09670bce14054b1c11ce5ff049ba5
+msgid "For the description on Secondary Isolated VLAN, see `About Private VLAN\" <#about-private-vlan>`_."
+msgstr ""
+
+#: ../../networking/isolation_in_advanced_zone_with_vlan.rst:167
+# 38765c8ae24048dba72826d07d096afe
+msgid "**Scope**: The available scopes are Domain, Account, Project, and All."
+msgstr ""
+
+#: ../../networking/isolation_in_advanced_zone_with_vlan.rst:170
+# 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/isolation_in_advanced_zone_with_vlan.rst:176
+# 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/isolation_in_advanced_zone_with_vlan.rst:180
+# 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/isolation_in_advanced_zone_with_vlan.rst:184
+# 3aa0f96be4f84d1bae1f1744b108dff8
+msgid "**All**: The guest network is available for all the domains, account, projects within the selected zone."
+msgstr ""
+
+#: ../../networking/isolation_in_advanced_zone_with_vlan.rst:187
+# 339b47c6f0f94ca4a221c0f592e92d5b
+msgid "**Network Offering**: If the administrator has configured multiple network offerings, select the one you want to use for this network."
+msgstr ""
+
+#: ../../networking/isolation_in_advanced_zone_with_vlan.rst:191
+# ae2111debd664f179fe8eb3b251587ff
+msgid "**Gateway**: The gateway that the guests should use."
+msgstr ""
+
+#: ../../networking/isolation_in_advanced_zone_with_vlan.rst:193
+# df6c332c5f7e427d867dcef1784c0731
+msgid "**Netmask**: The netmask in use on the subnet the guests will use."
+msgstr ""
+
+#: ../../networking/isolation_in_advanced_zone_with_vlan.rst:195
+# 5331fd382d74450c957ad9e5fa46a095
+msgid "**IP Range**: A range of IP addresses that are accessible from the Internet and are assigned to the guest VMs."
+msgstr ""
+
+#: ../../networking/isolation_in_advanced_zone_with_vlan.rst:198
+# 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/isolation_in_advanced_zone_with_vlan.rst:202
+# 0f106d1db97249348138b9cf76182524
+msgid "Click OK to confirm."
+msgstr ""
+