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/03/31 20:07:00 UTC
[1/7] setup i18n with transifex and sphinx-intl
Repository: cloudstack-docs-install
Updated Branches:
refs/heads/master b1f7a0f01 -> bd81bcc4a
http://git-wip-us.apache.org/repos/asf/cloudstack-docs-install/blob/bd81bcc4/source/locale/pot/optional_installation.pot
----------------------------------------------------------------------
diff --git a/source/locale/pot/optional_installation.pot b/source/locale/pot/optional_installation.pot
new file mode 100644
index 0000000..3ded385
--- /dev/null
+++ b/source/locale/pot/optional_installation.pot
@@ -0,0 +1,1252 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2014, Apache Software Foundation
+# This file is distributed under the same license as the Apache CloudStack Installation Documentation package.
+# FIRST AUTHOR <EM...@ADDRESS>, YEAR.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: Apache CloudStack Installation Documentation 4\n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2014-03-31 14:02-0400\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"
+
+#: ../../optional_installation.rst:17
+# 62835cebd46447fc8a75e16ba7eba401
+msgid "Additional Installation Options"
+msgstr ""
+
+#: ../../optional_installation.rst:19
+# db3fdcfe721d4988b9e54bc7222b20ae
+msgid "The next few sections describe CloudStack features above and beyond the basic deployment options."
+msgstr ""
+
+#: ../../optional_installation.rst:23
+# 2ca513276af64c04a0ea19f1709100ec
+msgid "Installing the Usage Server (Optional)"
+msgstr ""
+
+#: ../../optional_installation.rst:25
+# 08d682ff68c44985bfe7220e1de58937
+msgid "You can optionally install the Usage Server once the Management Server is configured properly. The Usage Server takes data from the events in the system and enables usage-based billing for accounts."
+msgstr ""
+
+#: ../../optional_installation.rst:29
+# a8a635bc3d18492cbdd96c1be333feda
+msgid "When multiple Management Servers are present, the Usage Server may be installed on any number of them. The Usage Servers will coordinate usage processing. A site that is concerned about availability should install Usage Servers on at least two Management Servers."
+msgstr ""
+
+#: ../../optional_installation.rst:35
+# 04a298cf529c44d198b58ff422208441
+msgid "Requirements for Installing the Usage Server"
+msgstr ""
+
+#: ../../optional_installation.rst:39
+# 509d6aa6c0e04ec18e5805a0ce8323fe
+msgid "The Management Server must be running when the Usage Server is installed."
+msgstr ""
+
+#: ../../optional_installation.rst:44
+# 2e23f212128f457ba9abf05c854d807b
+msgid "The Usage Server must be installed on the same server as a Management Server."
+msgstr ""
+
+#: ../../optional_installation.rst:48
+# bda1ce86593d4a38a4644a56e6218ce1
+msgid "Steps to Install the Usage Server"
+msgstr ""
+
+#: ../../optional_installation.rst:52
+# 1c636a3ac72345eda8528a6443e7bb7d
+msgid "Run ./install.sh (NOT VALID, NEED CORRECTION)"
+msgstr ""
+
+#: ../../optional_installation.rst:58
+# 9fb3b577d8154be39e47dcb155e8e615
+msgid "You should see a few messages as the installer prepares, followed by a list of choices."
+msgstr ""
+
+#: ../../optional_installation.rst:63
+# 6af250d789ec47509d34ac3978a4d6fc
+msgid "Choose \"S\" to install the Usage Server."
+msgstr ""
+
+#: ../../optional_installation.rst:71
+# ff0a5c4f21a54bdaacd08a49ef778b62
+msgid "Once installed, start the Usage Server with the following command."
+msgstr ""
+
+#: ../../optional_installation.rst:77
+# aceedf97a46343e89608668dcd949ddd
+msgid "The Administration Guide discusses further configuration of the Usage Server."
+msgstr ""
+
+#: ../../optional_installation.rst:81
+# 816936d415214ab983de8f3bb64a8e6a
+msgid "SSL (Optional)"
+msgstr ""
+
+#: ../../optional_installation.rst:83
+# ab49fd64e3474b68ac3f29143b8c5759
+msgid "CloudStack provides HTTP access in its default installation. There are a number of technologies and sites which choose to implement SSL. As a result, we have left CloudStack to expose HTTP under the assumption that a site will implement its typical practice."
+msgstr ""
+
+#: ../../optional_installation.rst:88
+# fd380c7c8d0649569079e5667153039a
+msgid "CloudStack uses Tomcat as its servlet container. For sites that would like CloudStack to terminate the SSL session, Tomcat’s SSL access may be enabled. Tomcat SSL configuration is described at http://tomcat.apache.org/tomcat-6.0-doc/ssl-howto.html."
+msgstr ""
+
+#: ../../optional_installation.rst:94
+# 2062d2fe64dc4e1bb85bc00d5c08727b
+msgid "Database Replication (Optional)"
+msgstr ""
+
+#: ../../optional_installation.rst:96
+# ab5f2c1a690c419e8d7ea82b4da28b12
+msgid "CloudStack supports database replication from one MySQL node to another. This is achieved using standard MySQL replication. You may want to do this as insurance against MySQL server or storage loss. MySQL replication is implemented using a master/slave model. The master is the node that the Management Servers are configured to use. The slave is a standby node that receives all write operations from the master and applies them to a local, redundant copy of the database. The following steps are a guide to implementing MySQL replication."
+msgstr ""
+
+#: ../../optional_installation.rst:107
+# b3a643bd88d244cd86fdeb8b1823325d
+msgid "Creating a replica is not a backup solution. You should develop a backup procedure for the MySQL data that is distinct from replication."
+msgstr ""
+
+#: ../../optional_installation.rst:111
+# 416f84b83a514c66bcdb90045773f0e0
+msgid "Ensure that this is a fresh install with no data in the master."
+msgstr ""
+
+#: ../../optional_installation.rst:115
+# fc938cd71e774b3b94e05d3e1968f03d
+msgid "Edit my.cnf on the master and add the following in the [mysqld] section below datadir."
+msgstr ""
+
+#: ../../optional_installation.rst:123
+# 105293596d6943a0ae0420f073d771f2
+msgid "The server\\_id must be unique with respect to other servers. The recommended way to achieve this is to give the master an ID of 1 and each slave a sequential number greater than 1, so that the servers are numbered 1, 2, 3, etc."
+msgstr ""
+
+#: ../../optional_installation.rst:130
+# 8a4b5dbe67c447ad9a8e9de760b638d3
+msgid "Restart the MySQL service. On RHEL/CentOS systems, use:"
+msgstr ""
+
+#: ../../optional_installation.rst:136
+# 5c3b7820d00c459ca57265787ec2fd5b
+msgid "On Debian/Ubuntu systems, use:"
+msgstr ""
+
+#: ../../optional_installation.rst:144
+# 4a230f88482a4a95931f2b58a0180585
+msgid "Create a replication account on the master and give it privileges. We will use the \"cloud-repl\" user with the password \"password\". This assumes that master and slave run on the 172.16.1.0/24 network."
+msgstr ""
+
+#: ../../optional_installation.rst:158
+# 8ff34461bbc9443da5c98650a97b141c
+msgid "Leave the current MySQL session running."
+msgstr ""
+
+#: ../../optional_installation.rst:162
+# 3e479f5ab88240a09303449bc895d6a1
+msgid "In a new shell start a second MySQL session."
+msgstr ""
+
+#: ../../optional_installation.rst:166
+# f4fa3623e02e497ca52b062716eb0a22
+msgid "Retrieve the current position of the database."
+msgstr ""
+
+#: ../../optional_installation.rst:180
+# 5521bd2939434fe19ad5ab048c4a917a
+msgid "Note the file and the position that are returned by your instance."
+msgstr ""
+
+#: ../../optional_installation.rst:184
+# 946b0ff096104aad8bbf3e535f59104a
+msgid "Exit from this session."
+msgstr ""
+
+#: ../../optional_installation.rst:188
+# bb7311f9bd634aec8c894b2b2d30d925
+msgid "Complete the master setup. Returning to your first session on the master, release the locks and exit MySQL."
+msgstr ""
+
+#: ../../optional_installation.rst:197
+# 4e9f4473e0b54f0e908fc082912971c5
+msgid "Install and configure the slave. On the slave server, run the following commands."
+msgstr ""
+
+#: ../../optional_installation.rst:207
+# 279f25d33b8147b0915b1b46b3aaa763
+msgid "Edit my.cnf and add the following lines in the [mysqld] section below datadir."
+msgstr ""
+
+#: ../../optional_installation.rst:218
+# ea002a738bb6421397288c9348d5afd7
+msgid "Restart MySQL. Use \"mysqld\" on RHEL/CentOS systems:"
+msgstr ""
+
+#: ../../optional_installation.rst:224
+# a1dd560330d34f029b9ae00431c7c33d
+msgid "On Ubuntu/Debian systems use \"mysql.\""
+msgstr ""
+
+#: ../../optional_installation.rst:232
+# f7f34afbe306462bb75bb4aae77bd393
+msgid "Instruct the slave to connect to and replicate from the master. Replace the IP address, password, log file, and position with the values you have used in the previous steps."
+msgstr ""
+
+#: ../../optional_installation.rst:247
+# a16d103e5fb048caa90dae277c78f150
+msgid "Then start replication on the slave."
+msgstr ""
+
+#: ../../optional_installation.rst:255
+# 77cfc7cfb6a64956b576027056206990
+msgid "Optionally, open port 3306 on the slave as was done on the master earlier."
+msgstr ""
+
+#: ../../optional_installation.rst:258
+# fd7930028c5444219c5f87c752883256
+msgid "This is not required for replication to work. But if you choose not to do this, you will need to do it when failover to the replica occurs."
+msgstr ""
+
+#: ../../optional_installation.rst:263
+# 5e6ad86df98c473db76a1d12f33dd6af
+msgid "Failover"
+msgstr ""
+
+#: ../../optional_installation.rst:265
+# 433eaa9a6ad942e3a9ebf55eda27dddf
+msgid "This will provide for a replicated database that can be used to implement manual failover for the Management Servers. CloudStack failover from one MySQL instance to another is performed by the administrator. In the event of a database failure you should:"
+msgstr ""
+
+#: ../../optional_installation.rst:272
+# d8a77566fc0a4911ab6349269da1bc66
+msgid "Stop the Management Servers (via service cloudstack-management stop)."
+msgstr ""
+
+#: ../../optional_installation.rst:276
+# ff1d228817b54a23b7e2197d5e7cd9b5
+msgid "Change the replica's configuration to be a master and restart it."
+msgstr ""
+
+#: ../../optional_installation.rst:280
+# a36b6275f2354327b0e21394b9a883e0
+msgid "Ensure that the replica's port 3306 is open to the Management Servers."
+msgstr ""
+
+#: ../../optional_installation.rst:285
+# 28145773ff534f1196dfcdc009a27d8d
+msgid "Make a change so that the Management Server uses the new database. The simplest process here is to put the IP address of the new database server into each Management Server's /etc/cloudstack/management/db.properties."
+msgstr ""
+
+#: ../../optional_installation.rst:292
+# 04d5359687c546b193f7694e48690c88
+msgid "Restart the Management Servers:"
+msgstr ""
+
+#: ../../optional_installation.rst:300
+# 908b240989be4e57a7a44645c1f1c200
+msgid "Amazon Web Services Interface"
+msgstr ""
+
+#: ../../optional_installation.rst:303
+# 13fa92afff834f76acf1807913a4ddd9
+msgid "Amazon Web Services Compatible Interface"
+msgstr ""
+
+#: ../../optional_installation.rst:305
+# 0e21bb994755441ba351a442ded0d861
+msgid "CloudStack can translate Amazon Web Services (AWS) API calls to native CloudStack API calls so that users can continue using existing AWS-compatible tools. This translation service runs as a separate web application in the same tomcat server as the management server of CloudStack, listening on a different port. The Amazon Web Services (AWS) compatible interface provides the EC2 SOAP and Query APIs as well as the S3 REST API."
+msgstr ""
+
+#: ../../optional_installation.rst:315
+# fd3570aa6bce4003bd691ddab7131659
+msgid "This service was previously enabled by separate software called CloudBridge. It is now fully integrated with the CloudStack management server."
+msgstr ""
+
+#: ../../optional_installation.rst:319
+# 2584c2fa19ea41e0bc7ecf98656e1baf
+msgid "The compatible interface for the EC2 Query API and the S3 API are Work In Progress. The S3 compatible API offers a way to store data on the management server file system, it is not an implementation of the S3 backend."
+msgstr ""
+
+#: ../../optional_installation.rst:321
+# 4ecbe620a7054b75b388d7d946f8fcbf
+msgid "Limitations"
+msgstr ""
+
+#: ../../optional_installation.rst:325
+# d9b4eceaa5e14986b233f56dab81f2fe
+msgid "Supported only in zones that use basic networking."
+msgstr ""
+
+#: ../../optional_installation.rst:329
+# 7c00f154c2b84f3dacdfa1142686bb4b
+msgid "Available in fresh installations of CloudStack. Not available through upgrade of previous versions."
+msgstr ""
+
+#: ../../optional_installation.rst:334
+# 2c768e3715c347d4b658fd66b9cccabe
+msgid "Features such as Elastic IP (EIP) and Elastic Load Balancing (ELB) are only available in an infrastructure with a Citrix NetScaler device. Users accessing a Zone with a NetScaler device will need to use a NetScaler-enabled network offering (DefaultSharedNetscalerEIP and ELBNetworkOffering)."
+msgstr ""
+
+#: ../../optional_installation.rst:341
+# c79b074d0cd143bfbad1ccbe38da3870
+msgid "Supported API Version"
+msgstr ""
+
+#: ../../optional_installation.rst:345
+# 5d4ee9f9359e4edea1f3f26f95787aae
+msgid "The EC2 interface complies with Amazon's WDSL version dated November 15, 2010, available at `http://ec2.amazonaws.com/doc/2010-11-15/ <http://ec2.amazonaws.com/doc/2010-11-15/>`_."
+msgstr ""
+
+#: ../../optional_installation.rst:351
+# 275a7a85c52446bbba7fa468a12b13e8
+msgid "The interface is compatible with the EC2 command-line tools *EC2 tools v. 1.3.6230*, which can be downloaded at `http://s3.amazonaws.com/ec2-downloads/ec2-api-tools-1.3-62308.zip <http://s3.amazonaws.com/ec2-downloads/ec2-api-tools-1.3-62308.zip>`_."
+msgstr ""
+
+#: ../../optional_installation.rst:357
+# ee2fb0ee43ce44dfbc17dbc415357f4b
+msgid "Work is underway to support a more recent version of the EC2 API"
+msgstr ""
+
+#: ../../optional_installation.rst:360
+# a5066ccca5d947dab401b48fa1c827ac
+msgid "Enabling the EC2 and S3 Compatible Interface"
+msgstr ""
+
+#: ../../optional_installation.rst:362
+# 0a40a8c0aeae4d28847aaffebd2e0b77
+msgid "The software that provides AWS API compatibility is installed along with CloudStack. You must enable the services and perform some setup steps prior to using it."
+msgstr ""
+
+#: ../../optional_installation.rst:368
+# 2d1dfb320f094662a2abab3ee3ed7564
+msgid "Set the global configuration parameters for each service to true. See `*Setting Global Configuration Parameters* <configuration.html#setting-global-configuration-parameters>`_."
+msgstr ""
+
+#: ../../optional_installation.rst:373
+# 3c573004daaf447a9ea3781fd1a8dc67
+msgid "Create a set of CloudStack service offerings with names that match the Amazon service offerings. You can do this through the CloudStack UI as described in the Administration Guide."
+msgstr ""
+
+#: ../../optional_installation.rst:379
+# 94091fd248aa4742b4ade27bbfdc651c
+msgid "Be sure you have included the Amazon default service offering, m1.small. As well as any EC2 instance types that you will use."
+msgstr ""
+
+#: ../../optional_installation.rst:383
+# 042b0e1d5a114ee0b6f9a853b4d4ae39
+msgid "If you did not already do so when you set the configuration parameter in step 1, restart the Management Server."
+msgstr ""
+
+#: ../../optional_installation.rst:390
+# 7b9489e9131b43df850dfeb6d2503cb6
+msgid "The following sections provides details to perform these steps"
+msgstr ""
+
+#: ../../optional_installation.rst:393
+# 108cd093069f4ed98bc18c79149d6156
+msgid "Enabling the Services"
+msgstr ""
+
+#: ../../optional_installation.rst:395
+# 39010121ec2f4c72b2903b5672336aaa
+msgid "To enable the EC2 and S3 compatible services you need to set the configuration variables *enable.ec2.api* and *enable.s3.api* to true. You do not have to enable both at the same time. Enable the ones you need. This can be done via the CloudStack GUI by going in *Global Settings* or via the API."
+msgstr ""
+
+#: ../../optional_installation.rst:401
+# da34d29b15bb4336a4fce15fe496fabd
+msgid "The snapshot below shows you how to use the GUI to enable these services"
+msgstr ""
+
+#: ../../optional_installation.rst:403
+# ca106e08170a43b0955d6377943ecb95
+msgid "|Use the GUI to set the configuration variable to true|"
+msgstr ""
+
+#: ../../optional_installation.rst:405
+# aeb3f192704a4d2a8e37954b1965aa54
+msgid "Using the CloudStack API, the easiest is to use the so-called integration port on which you can make unauthenticated calls. In Global Settings set the port to 8096 and subsequently call the *updateConfiguration* method. The following urls shows you how:"
+msgstr ""
+
+#: ../../optional_installation.rst:415
+# b3b35c42560d4bd38c04fbb26767e459
+msgid "Once you have enabled the services, restart the server."
+msgstr ""
+
+#: ../../optional_installation.rst:418
+# 03be0ef180d04f31ae30950f0955519f
+msgid "Creating EC2 Compatible Service Offerings"
+msgstr ""
+
+#: ../../optional_installation.rst:420
+# 2e71b04ddca44f11b8df8d0516c2a461
+msgid "You will also need to define compute service offerings with names compatible with the `Amazon EC2 instance types <http://aws.amazon.com/ec2/instance-types/>`_ API names (e.g m1.small,m1.large). This can be done via the CloudStack GUI. Go under *Service Offerings* select *Compute offering* and either create a new compute offering or modify an existing one, ensuring that the name matches an EC2 instance type API name. The snapshot below shows you how:"
+msgstr ""
+
+#: ../../optional_installation.rst:428
+# 51951028996a46f18420abe8eb5e467a
+msgid "|Use the GUI to set the name of a compute service offering to an EC2 instance type API name.|"
+msgstr ""
+
+#: ../../optional_installation.rst:432
+# 4598bfc20670422d956c715404a0dfaf
+msgid "Modifying the AWS API Port"
+msgstr ""
+
+#: ../../optional_installation.rst:436
+# c994c76df7fe428aa36240f1299b6572
+msgid "(Optional) The AWS API listens for requests on port 7080. If you prefer AWS API to listen on another port, you can change it as follows:"
+msgstr ""
+
+#: ../../optional_installation.rst:440
+# 0dcbe38e7a8f4d399bfa1e949aea147c
+msgid "Edit the files ``/etc/cloudstack/management/server.xml``, ``/etc/cloudstack/management/server-nonssl.xml``, and ``/etc/cloudstack/management/server-ssl.xml``."
+msgstr ""
+
+#: ../../optional_installation.rst:446
+# 45096710b3864e3dba393626022c56cd
+msgid "In each file, find the tag <Service name=\"Catalina7080\">. Under this tag, locate <Connector executor=\"tomcatThreadPool-internal\" port= ....<."
+msgstr ""
+
+#: ../../optional_installation.rst:450
+# 09955dd23725489ca5b44829047f83a6
+msgid "Change the port to whatever port you want to use, then save the files."
+msgstr ""
+
+#: ../../optional_installation.rst:454
+# 7850ae5c003647e3800993f09d3515e4
+msgid "Restart the Management Server."
+msgstr ""
+
+#: ../../optional_installation.rst:456
+# afa95ed12f774196a3900c58bec43a55
+msgid "If you re-install CloudStack, you will have to re-enable the services and if need be update the port."
+msgstr ""
+
+#: ../../optional_installation.rst:460
+# 90d8f2c211154a228b46bc50294a88f9
+msgid "AWS API User Setup"
+msgstr ""
+
+#: ../../optional_installation.rst:462
+# 6e5a5893f4e74d09b595f97252a0204b
+msgid "In general, users need not be aware that they are using a translation service provided by CloudStack. They only need to send AWS API calls to CloudStack's endpoint, and it will translate the calls to the native CloudStack API. Users of the Amazon EC2 compatible interface will be able to keep their existing EC2 tools and scripts and use them with their CloudStack deployment, by specifying the endpoint of the management server and using the proper user credentials. In order to do this, each user must perform the following configuration steps:"
+msgstr ""
+
+#: ../../optional_installation.rst:473
+# f7141ce2f88f4e81af3fb3225b181f35
+msgid "Generate user credentials."
+msgstr ""
+
+#: ../../optional_installation.rst:477
+# 78c96ff5025e4e1d919e7d09cbd791ae
+msgid "Register with the service."
+msgstr ""
+
+#: ../../optional_installation.rst:481
+# 65dfa81b512744bb8a2441e263329a52
+msgid "For convenience, set up environment variables for the EC2 SOAP command-line tools."
+msgstr ""
+
+#: ../../optional_installation.rst:486
+# 3b4d14b5a5f14ab08a7688e8833a9ec9
+msgid "AWS API Command-Line Tools Setup"
+msgstr ""
+
+#: ../../optional_installation.rst:488
+# dfde155c78ce4200baca48fa3a5f037b
+msgid "To use the EC2 command-line tools, the user must perform these steps:"
+msgstr ""
+
+#: ../../optional_installation.rst:492
+# 800693fcd6894e6aaa4745be9254bee6
+msgid "Be sure you have the right version of EC2 Tools. The supported version is available at `http://s3.amazonaws.com/ec2-downloads/ec2-api-tools-1.3-62308.zip <http://s3.amazonaws.com/ec2-downloads/ec2-api-tools-1.3-62308.zip>`_."
+msgstr ""
+
+#: ../../optional_installation.rst:498
+# df0880de8a5b4705b8dbb43fa76f2a98
+msgid "Set up the EC2 environment variables. This can be done every time you use the service or you can set them up in the proper shell profile. Replace the endpoint (i.e EC2\\_URL) with the proper address of your CloudStack management server and port. In a bash shell do the following."
+msgstr ""
+
+#: ../../optional_installation.rst:512
+# 1a4c91090a9d49718753e24f4e7e15dc
+msgid "Using Timeouts to Ensure AWS API Command Completion"
+msgstr ""
+
+#: ../../optional_installation.rst:514
+# 64619241fff543b9b001ef888c668c66
+msgid "The Amazon EC2 command-line tools have a default connection timeout. When used with CloudStack, a longer timeout might be needed for some commands. If you find that commands are not completing due to timeouts, you can specify a custom timeouts. You can add the following optional command-line parameters to any CloudStack-supported EC2 command:"
+msgstr ""
+
+#: ../../optional_installation.rst:520
+# e3ad2ffe38a3410bab7772a043223629
+msgid "Specifies a connection timeout (in seconds)"
+msgstr ""
+
+#: ../../optional_installation.rst:526
+# e756e801ae374a35bd58b0658429e502
+msgid "Specifies a request timeout (in seconds)"
+msgstr ""
+
+#: ../../optional_installation.rst:532
+# 69ff406095bb492a86be6ba348e2c4f4
+msgid "Example:"
+msgstr ""
+
+#: ../../optional_installation.rst:540
+# e145a9770bf849aaa75f7903c47fcb78
+msgid "The timeouts optional arguments are not specific to CloudStack."
+msgstr ""
+
+#: ../../optional_installation.rst:543
+# 895bcef30e684d5d8c9faa6e9c951af5
+msgid "Supported AWS API Calls"
+msgstr ""
+
+#: ../../optional_installation.rst:545
+# ad0a5e3e13ca4fe7b3df211e2caa7134
+msgid "The following Amazon EC2 commands are supported by CloudStack when the AWS API compatible interface is enabled. For a few commands, there are differences between the CloudStack and Amazon EC2 versions, and these differences are noted. The underlying SOAP call for each command is also given, for those who have built tools using those calls."
+msgstr ""
+
+#: ../../optional_installation.rst:551
+# 7b3c005fe35946dc84a3ea2fc0b6d0d1
+msgid "Table 1. Elastic IP API mapping"
+msgstr ""
+
+#: ../../optional_installation.rst:555
+#: ../../optional_installation.rst:574
+#: ../../optional_installation.rst:585
+#: ../../optional_installation.rst:602
+#: ../../optional_installation.rst:617
+#: ../../optional_installation.rst:638
+#: ../../optional_installation.rst:649
+#: ../../optional_installation.rst:666
+#: ../../optional_installation.rst:677
+#: ../../optional_installation.rst:696
+#: ../../optional_installation.rst:711
+# ab0814b37bab4bebba50ddcf37b3679d
+# 2759704657024f75868e25e8e9fcee4c
+# cbb8c8a42d3d4176bc116f22282dfcd8
+# 460991b7ba4745a0a6389c709ef34405
+# 43eacabecf4340c5978f9bef44afe3e9
+# 6e66ea93f49e4a8088b1240a3c9a5c0d
+# 7eafa5a23d4440129b24fe9c4ccfb831
+# ccac39d7bf1f44209f2df8f4017c1161
+# 71e1a212c3ef4513825770b509b37a15
+# 0f50d90449a448e3aa024777cf190d28
+# a6dafae1ffe245b384f3038eaff5e807
+msgid "EC2 command"
+msgstr ""
+
+#: ../../optional_installation.rst:555
+#: ../../optional_installation.rst:574
+#: ../../optional_installation.rst:585
+#: ../../optional_installation.rst:602
+#: ../../optional_installation.rst:617
+#: ../../optional_installation.rst:638
+#: ../../optional_installation.rst:649
+#: ../../optional_installation.rst:666
+#: ../../optional_installation.rst:677
+#: ../../optional_installation.rst:696
+#: ../../optional_installation.rst:711
+# 78a200ef3d484cf6b7a4c41ad9a8a7ca
+# adc512dff0ae4a40b5a46f0d5b9e39db
+# 2123f81311254f4388c7b7c2551a8078
+# 69d4baa8db464d6fa661b97796f03189
+# f3c078dd4101426694075f0ade30e05d
+# b3163c01285841ea9f888da3cb4239d1
+# d9518541d8044d4e8d6407f71745d28a
+# 5cb191d5b71d46298e4dfd4280bd64b8
+# 495c2421bf98440f8ee0d86344a4fce9
+# 82d977b2cb7943c99d25eb372572fe14
+# b58f0b7b468c47e28ae59c65bd9fa6e7
+msgid "SOAP call"
+msgstr ""
+
+#: ../../optional_installation.rst:555
+#: ../../optional_installation.rst:574
+#: ../../optional_installation.rst:585
+#: ../../optional_installation.rst:602
+#: ../../optional_installation.rst:617
+#: ../../optional_installation.rst:638
+#: ../../optional_installation.rst:649
+#: ../../optional_installation.rst:666
+#: ../../optional_installation.rst:677
+#: ../../optional_installation.rst:696
+#: ../../optional_installation.rst:711
+# ac59537fd8224b4e90196b1d78f23fbc
+# 2ca349b7c7fa446bb5581e7bb8614046
+# ff08a9523404400d83f3c843f0dff971
+# aa37961561ff47aeb4f11b98844c8232
+# df204989b28c46e088905c6861b0be06
+# ae89cb9f31e844d1993649cd64d8254b
+# f53a17d0817a4b558c29eb20c6edc6f9
+# 0c490fff40804f7c8106dad8d03330ce
+# 751e2e6c2d4444b8834f479f1fa43e48
+# dc275e4e74604d87a7bf1d181432f189
+# c917215672fb480ab9377a5aa7ad8f60
+msgid "CloudStack API call"
+msgstr ""
+
+#: ../../optional_installation.rst:557
+# 99e6554c2d594a2d82e50de0499caecd
+msgid "ec2-allocate-address"
+msgstr ""
+
+#: ../../optional_installation.rst:557
+# 0c7211c2d6fa4a3d9d97bda018a2c29b
+msgid "AllocateAddress"
+msgstr ""
+
+#: ../../optional_installation.rst:557
+# b56058adc8e2482bb99b566f5001a655
+msgid "associateIpAddress"
+msgstr ""
+
+#: ../../optional_installation.rst:559
+# 5eb619cc847c4222beea83e790f94c39
+msgid "ec2-associate-address"
+msgstr ""
+
+#: ../../optional_installation.rst:559
+# 8266e0a21a91482588230dd452ec8e70
+msgid "AssociateAddress"
+msgstr ""
+
+#: ../../optional_installation.rst:559
+# bb53eb62239140e1b5e624d08e000b88
+msgid "enableStaticNat"
+msgstr ""
+
+#: ../../optional_installation.rst:561
+# 658fda2a155145a7af43e8b6e0148816
+msgid "ec2-describe-addresses"
+msgstr ""
+
+#: ../../optional_installation.rst:561
+# 5d052cbb95104736ad915a3ca985c666
+msgid "DescribeAddresses"
+msgstr ""
+
+#: ../../optional_installation.rst:561
+# e345bfbcdd094eb8aa8e36a0fbd5d89b
+msgid "listPublicIpAddresses"
+msgstr ""
+
+#: ../../optional_installation.rst:563
+# 87ccbc154760470fa812d074fc093dce
+msgid "ec2-diassociate-address"
+msgstr ""
+
+#: ../../optional_installation.rst:563
+# 0480b2af2f824f7ebd3b345eb5ae6a4f
+msgid "DisassociateAddress"
+msgstr ""
+
+#: ../../optional_installation.rst:563
+# f49b439a4a67450b89eb7fdffb3e1c84
+msgid "disableStaticNat"
+msgstr ""
+
+#: ../../optional_installation.rst:565
+# 9c2f4489a860437282a0c188eeebe3ff
+msgid "ec2-release-address"
+msgstr ""
+
+#: ../../optional_installation.rst:565
+# 35f1e9817f1d4e3a805ca8aaee8fb229
+msgid "ReleaseAddress"
+msgstr ""
+
+#: ../../optional_installation.rst:565
+# a67d0ab0f1a64ec2b8c21b006e1a2f90
+msgid "disassociateIpAddress"
+msgstr ""
+
+#: ../../optional_installation.rst:570
+# 4a72020f31b34940841e0e3c1b4ef643
+msgid "Table 2. Availability Zone API mapping"
+msgstr ""
+
+#: ../../optional_installation.rst:576
+# 0d1a534afa9f4184bb6d7e6ba6d13a79
+msgid "ec2-describe-availability-zones"
+msgstr ""
+
+#: ../../optional_installation.rst:576
+# e2cb2767a40c473a8e6fb813769f7301
+msgid "DescribeAvailabilityZones"
+msgstr ""
+
+#: ../../optional_installation.rst:576
+# 9a382a47bfb74bb593a10a5ff6e25ffd
+msgid "listZones"
+msgstr ""
+
+#: ../../optional_installation.rst:581
+# f62baa92321346e39d05147ba7d3b6d3
+msgid "Table 3. Images API mapping"
+msgstr ""
+
+#: ../../optional_installation.rst:587
+# b6442db2335c4be787e2c6ab6f9993bc
+msgid "ec2-create-image"
+msgstr ""
+
+#: ../../optional_installation.rst:587
+# 384e6c0b65cd4ab7b8012368b424aad0
+msgid "CreateImage"
+msgstr ""
+
+#: ../../optional_installation.rst:587
+# e0c1789e1bc240c486b275ef6bd04ae7
+msgid "createTemplate"
+msgstr ""
+
+#: ../../optional_installation.rst:589
+# 7ea01be830ec4dd9bda90926a00fe600
+msgid "ec2-deregister"
+msgstr ""
+
+#: ../../optional_installation.rst:589
+# bd63ca4e7dc74205bdbd3ad62f01bfe7
+msgid "DeregisterImage"
+msgstr ""
+
+#: ../../optional_installation.rst:589
+# 34ac4b0eb9614903a3619e099a4ccc72
+msgid "DeleteTemplate"
+msgstr ""
+
+#: ../../optional_installation.rst:591
+# f53fef47b43b48ff8f863c654d9b4cdb
+msgid "ec2-describe-images"
+msgstr ""
+
+#: ../../optional_installation.rst:591
+# 47a1032852c24ad4853006959197af20
+msgid "DescribeImages"
+msgstr ""
+
+#: ../../optional_installation.rst:591
+# 0c6b2e8dfa4a462387c76e9832df6e65
+msgid "listTemplates"
+msgstr ""
+
+#: ../../optional_installation.rst:593
+# e09a7882cbc7406194f428d913c31b1a
+msgid "ec2-register"
+msgstr ""
+
+#: ../../optional_installation.rst:593
+# 186fd0feef5d42e39b45127aca5b509d
+msgid "RegisterImage"
+msgstr ""
+
+#: ../../optional_installation.rst:593
+# fcbeab7a8003431e960bee86a6417310
+msgid "registerTemplate"
+msgstr ""
+
+#: ../../optional_installation.rst:598
+# 5bcd512bca8a4e869de4bce42769dc47
+msgid "Table 4. Image Attributes API mapping"
+msgstr ""
+
+#: ../../optional_installation.rst:604
+# 6ef54cf16ba9473fae7f6913ae97b4c9
+msgid "ec2-describe-image-attribute"
+msgstr ""
+
+#: ../../optional_installation.rst:604
+# 4edda821f05c40998556bd1d673fd236
+msgid "DescribeImageAttribute"
+msgstr ""
+
+#: ../../optional_installation.rst:604
+# 4d02a782bb21400a98b3abf5389bfe7d
+msgid "listTemplatePermissions"
+msgstr ""
+
+#: ../../optional_installation.rst:606
+# 6e0940c541194f02a717cd834a129c1a
+msgid "ec2-modify-image-attribute"
+msgstr ""
+
+#: ../../optional_installation.rst:606
+# b0f1f5a1969c4d7489507d856af91c76
+msgid "ModifyImageAttribute"
+msgstr ""
+
+#: ../../optional_installation.rst:606
+#: ../../optional_installation.rst:608
+# 7ddb77996c354b60aa2fe4c82bdd54a0
+# c4da2db179494b67990b93b1ab06aff8
+msgid "updateTemplatePermissions"
+msgstr ""
+
+#: ../../optional_installation.rst:608
+# 9d783054b68d44279cb0809bbb1dab15
+msgid "ec2-reset-image-attribute"
+msgstr ""
+
+#: ../../optional_installation.rst:608
+# f6295dd7096d4ef39d13097670a6e669
+msgid "ResetImageAttribute"
+msgstr ""
+
+#: ../../optional_installation.rst:613
+# da0cf1a9af8b48b59ee0ba6dc31c8d76
+msgid "Table 5. Instances API mapping"
+msgstr ""
+
+#: ../../optional_installation.rst:619
+# 79355e5383ef4aa1a1e89ed488612fda
+msgid "ec2-describe-instances"
+msgstr ""
+
+#: ../../optional_installation.rst:619
+# 27d17d486d5e4743985ce9a4379de40a
+msgid "DescribeInstances"
+msgstr ""
+
+#: ../../optional_installation.rst:619
+#: ../../optional_installation.rst:640
+# 24ca1c436bb345dba12764523b51ec63
+# f5001ce1fafd42fa84dd1de9d24d5b83
+msgid "listVirtualMachines"
+msgstr ""
+
+#: ../../optional_installation.rst:621
+# 00c378633eab48a18c0ec9d21435cdf5
+msgid "ec2-run-instances"
+msgstr ""
+
+#: ../../optional_installation.rst:621
+# d09a59362a054bbfa236be1bd6d20def
+msgid "RunInstances"
+msgstr ""
+
+#: ../../optional_installation.rst:621
+# 087a670aa9874c86b8a3f60817b1f89a
+msgid "deployVirtualMachine"
+msgstr ""
+
+#: ../../optional_installation.rst:623
+# ecd305073eee4cf8a1dc6b574d81df30
+msgid "ec2-reboot-instances"
+msgstr ""
+
+#: ../../optional_installation.rst:623
+# aae4dc0cebdc49efae8d600783b9f12e
+msgid "RebootInstances"
+msgstr ""
+
+#: ../../optional_installation.rst:623
+# 1e8fb9e0ece345dca69feed52349021d
+msgid "rebootVirtualMachine"
+msgstr ""
+
+#: ../../optional_installation.rst:625
+# b0022e5bbdf44ec0a6341d106ec7d94c
+msgid "ec2-start-instances"
+msgstr ""
+
+#: ../../optional_installation.rst:625
+# 46031a76499b4c0e9c5a39e77782c4d9
+msgid "StartInstances"
+msgstr ""
+
+#: ../../optional_installation.rst:625
+# bf1504e3a0674d0b85095e836bd6962a
+msgid "startVirtualMachine"
+msgstr ""
+
+#: ../../optional_installation.rst:627
+# 5f2f3ec553f54c659f3c357b003a8d28
+msgid "ec2-stop-instances"
+msgstr ""
+
+#: ../../optional_installation.rst:627
+# 193cfd3fb58e4dbfa8bd1c233e11a8bf
+msgid "StopInstances"
+msgstr ""
+
+#: ../../optional_installation.rst:627
+# 41ba2031043045a5b0e664038a836a53
+msgid "stopVirtualMachine"
+msgstr ""
+
+#: ../../optional_installation.rst:629
+# 47f5f9f8ea2d494bbd858e7f046cb88b
+msgid "ec2-terminate-instances"
+msgstr ""
+
+#: ../../optional_installation.rst:629
+# 03fa4cc038b54af2b2b0b30a424154b3
+msgid "TerminateInstances"
+msgstr ""
+
+#: ../../optional_installation.rst:629
+# 8f834a4620474486b8d069bc80d4fa97
+msgid "destroyVirtualMachine"
+msgstr ""
+
+#: ../../optional_installation.rst:634
+# ce25e10dee3e4d588935eebac1f5f695
+msgid "Table 6. Instance Attributes Mapping"
+msgstr ""
+
+#: ../../optional_installation.rst:640
+# 7e9fa7a259f843448321f098e781d68d
+msgid "ec2-describe-instance-attribute"
+msgstr ""
+
+#: ../../optional_installation.rst:640
+# b354b9c4037c4be8b16792f11e0a685b
+msgid "DescribeInstanceAttribute"
+msgstr ""
+
+#: ../../optional_installation.rst:645
+# 8b396a202c604bfaa257d8bdc83d963e
+msgid "Table 7. Keys Pairs Mapping"
+msgstr ""
+
+#: ../../optional_installation.rst:651
+# c218341b87854777b1f69ed42f06c6cb
+msgid "ec2-add-keypair"
+msgstr ""
+
+#: ../../optional_installation.rst:651
+# f399f5b2e56f4c22979b33af8110b7b3
+msgid "CreateKeyPair"
+msgstr ""
+
+#: ../../optional_installation.rst:651
+# 7900c842debc41f7b23c4103bfac2fb1
+msgid "createSSHKeyPair"
+msgstr ""
+
+#: ../../optional_installation.rst:653
+# 9cfc2a2925b9456582e8c466e50e36c1
+msgid "ec2-delete-keypair"
+msgstr ""
+
+#: ../../optional_installation.rst:653
+# 8070f7e64f5e490088c7baea20ddc8f4
+msgid "DeleteKeyPair"
+msgstr ""
+
+#: ../../optional_installation.rst:653
+# 25a3f734f8ea47bdacfce912212f0f83
+msgid "deleteSSHKeyPair"
+msgstr ""
+
+#: ../../optional_installation.rst:655
+# 3069cec0128844058911d7ce8909dadf
+msgid "ec2-describe-keypairs"
+msgstr ""
+
+#: ../../optional_installation.rst:655
+# d393c055180b403f892e58e0af9c439c
+msgid "DescribeKeyPairs"
+msgstr ""
+
+#: ../../optional_installation.rst:655
+# b42372e5e42d49988975b69725725faa
+msgid "listSSHKeyPairs"
+msgstr ""
+
+#: ../../optional_installation.rst:657
+# 81bb596e06264af9a48db273ebf0ea8f
+msgid "ec2-import-keypair"
+msgstr ""
+
+#: ../../optional_installation.rst:657
+# fd199e97ef4b40ffbb5f65766607a3c9
+msgid "ImportKeyPair"
+msgstr ""
+
+#: ../../optional_installation.rst:657
+# d6c18bf7d0a64a23a9cd2c725b68bb38
+msgid "registerSSHKeyPair"
+msgstr ""
+
+#: ../../optional_installation.rst:662
+# 5e2d7ff2ad7f414483eaa4f5ed93c53f
+msgid "Table 8. Passwords API Mapping"
+msgstr ""
+
+#: ../../optional_installation.rst:668
+# b051d0105d244d179fc17a308cc1ffeb
+msgid "ec2-get-password"
+msgstr ""
+
+#: ../../optional_installation.rst:668
+# 71a1a1ebb372455099a50f4c1d5e654f
+msgid "GetPasswordData"
+msgstr ""
+
+#: ../../optional_installation.rst:668
+# 5ce16abd4d06403db13d08926e1158e4
+msgid "getVMPassword"
+msgstr ""
+
+#: ../../optional_installation.rst:673
+# 219acf23be7641ddad72e7121ee69796
+msgid "Table 9. Security Groups API Mapping"
+msgstr ""
+
+#: ../../optional_installation.rst:679
+# d59f5068cbbd4ec6896e917c8845cc41
+msgid "ec2-authorize"
+msgstr ""
+
+#: ../../optional_installation.rst:679
+# 1d770748c025465e988a75755f8bd10c
+msgid "AuthorizeSecurityGroupIngress"
+msgstr ""
+
+#: ../../optional_installation.rst:679
+# c9d82294d3bf469aaf5baf38b5ec4d6a
+msgid "authorizeSecurityGroupIngress"
+msgstr ""
+
+#: ../../optional_installation.rst:681
+# e375163e62cc49a19dcece0639d74d1e
+msgid "ec2-add-group"
+msgstr ""
+
+#: ../../optional_installation.rst:681
+# 2b7e0861da1b4181a9397d09cc3670bc
+msgid "CreateSecurityGroup"
+msgstr ""
+
+#: ../../optional_installation.rst:681
+# a6ea159ac67c4adfb718cf441a57703e
+msgid "createSecurityGroup"
+msgstr ""
+
+#: ../../optional_installation.rst:683
+# f5d06234f2704480935e3d6308552b5f
+msgid "ec2-delete-group"
+msgstr ""
+
+#: ../../optional_installation.rst:683
+# 2ba2b0c32f4d4656983301a3b4dbb33f
+msgid "DeleteSecurityGroup"
+msgstr ""
+
+#: ../../optional_installation.rst:683
+# 096876dd93ee45e59918615970873f00
+msgid "deleteSecurityGroup"
+msgstr ""
+
+#: ../../optional_installation.rst:685
+# 7e5a122e72fd494aa65d7b81ba68e23e
+msgid "ec2-describe-group"
+msgstr ""
+
+#: ../../optional_installation.rst:685
+# a5f4bca8d13045869578b21ac13cf577
+msgid "DescribeSecurityGroups"
+msgstr ""
+
+#: ../../optional_installation.rst:685
+# 83310e0ff6f947cf912c59c4825bc6e1
+msgid "listSecurityGroups"
+msgstr ""
+
+#: ../../optional_installation.rst:687
+# 10a505985f0a488d957a3c94952437fd
+msgid "ec2-revoke"
+msgstr ""
+
+#: ../../optional_installation.rst:687
+# 20a97fcd061d495b9fd9530c1b731484
+msgid "RevokeSecurityGroupIngress"
+msgstr ""
+
+#: ../../optional_installation.rst:687
+# a4b72631334b41ad9970ec13fb407ff2
+msgid "revokeSecurityGroupIngress"
+msgstr ""
+
+#: ../../optional_installation.rst:692
+# 6bc48720611a4083b4d7edf62a707dad
+msgid "Table 10. Snapshots API Mapping"
+msgstr ""
+
+#: ../../optional_installation.rst:698
+# d546aaa137334207a7a38816408b9a97
+msgid "ec2-create-snapshot"
+msgstr ""
+
+#: ../../optional_installation.rst:698
+# 2a15c0cc74a24cce8f6a47c5ebe88b30
+msgid "CreateSnapshot"
+msgstr ""
+
+#: ../../optional_installation.rst:698
+# 5156b81572154dc08aabd2c7eff470cc
+msgid "createSnapshot"
+msgstr ""
+
+#: ../../optional_installation.rst:700
+# df85667beada434ea7c65b1e9aba6527
+msgid "ec2-delete-snapshot"
+msgstr ""
+
+#: ../../optional_installation.rst:700
+# 6d5662797d8049dbb372300b509eadf1
+msgid "DeleteSnapshot"
+msgstr ""
+
+#: ../../optional_installation.rst:700
+# 2e00aedaa9474c12b4478f36c38522a7
+msgid "deleteSnapshot"
+msgstr ""
+
+#: ../../optional_installation.rst:702
+# 133870454b7a46a4975b338e8707e99a
+msgid "ec2-describe-snapshots"
+msgstr ""
+
+#: ../../optional_installation.rst:702
+# 91e9a8133a5145eabf6c7b20249daef4
+msgid "DescribeSnapshots"
+msgstr ""
+
+#: ../../optional_installation.rst:702
+# 774d14bab36946ef9a461f31cc3ca2c5
+msgid "listSnapshots"
+msgstr ""
+
+#: ../../optional_installation.rst:707
+# 1488a3ce4b014e2f8463c68d71e51a3f
+msgid "Table 11. Volumes API Mapping"
+msgstr ""
+
+#: ../../optional_installation.rst:713
+# 574127e918dc493bbaf9f00fe59b51e1
+msgid "ec2-attach-volume"
+msgstr ""
+
+#: ../../optional_installation.rst:713
+# 6d12ce27f3a3464f9e39618bcb2d6b17
+msgid "AttachVolume"
+msgstr ""
+
+#: ../../optional_installation.rst:713
+# eca0d38a1e85441c9bd95d3ae220c995
+msgid "attachVolume"
+msgstr ""
+
+#: ../../optional_installation.rst:715
+# 46017b1d538746a590d57482750f6869
+msgid "ec2-create-volume"
+msgstr ""
+
+#: ../../optional_installation.rst:715
+# 275a90cc400a467799bfc076ad4e91d9
+msgid "CreateVolume"
+msgstr ""
+
+#: ../../optional_installation.rst:715
+# 3a9965009180409e8c94474d984b7fca
+msgid "createVolume"
+msgstr ""
+
+#: ../../optional_installation.rst:717
+# d87fd97018ce47c1befddf53071bca74
+msgid "ec2-delete-volume"
+msgstr ""
+
+#: ../../optional_installation.rst:717
+# e00e5d79af884664aae162eb23d97daa
+msgid "DeleteVolume"
+msgstr ""
+
+#: ../../optional_installation.rst:717
+# 0ea441d0a5a444c8a822f70933d79fad
+msgid "deleteVolume"
+msgstr ""
+
+#: ../../optional_installation.rst:719
+# 9eec17b895294c358e0e6d068e3c67f7
+msgid "ec2-describe-volume"
+msgstr ""
+
+#: ../../optional_installation.rst:719
+# a21c198723b14699801f195d9c447f13
+msgid "DescribeVolume"
+msgstr ""
+
+#: ../../optional_installation.rst:719
+# 3ac919eb5ebc40cc8d69ec270a2d98b9
+msgid "listVolumes"
+msgstr ""
+
+#: ../../optional_installation.rst:721
+# b11e784574f64ed09d472fb0a1b8f878
+msgid "ec2-detach-volume"
+msgstr ""
+
+#: ../../optional_installation.rst:721
+# fd89621510db420cabe46f1e087869f6
+msgid "DetachVolume"
+msgstr ""
+
+#: ../../optional_installation.rst:721
+# ce97fae64f4544e98b34790f6c802962
+msgid "detachVolume"
+msgstr ""
+
+#: ../../optional_installation.rst:727
+# 43b90aa15e304481be19f8f11994e7e5
+msgid "Examples"
+msgstr ""
+
+#: ../../optional_installation.rst:729
+# 1c5767a4fecb43c5b54f99f5be3a1d87
+msgid "There are many tools available to interface with a AWS compatible API. In this section we provide a few examples that users of CloudStack can build upon."
+msgstr ""
+
+#: ../../optional_installation.rst:734
+# ad24d991529b4e8889c9179531422ed2
+msgid "Boto Examples"
+msgstr ""
+
+#: ../../optional_installation.rst:736
+# 22da38cb9aa64efe84e9b9696a02fa9d
+msgid "Boto is one of them. It is a Python package available at https://github.com/boto/boto. In this section we provide two examples of Python scripts that use Boto and have been tested with the CloudStack AWS API Interface."
+msgstr ""
+
+#: ../../optional_installation.rst:741
+# e405217390dc4f6fadf3a611a3682e82
+msgid "First is an EC2 example. Replace the Access and Secret Keys with your own and update the endpoint."
+msgstr ""
+
+#: ../../optional_installation.rst:744
+# 8ae07fcf316a4ff7b85e8cd2f69099a1
+msgid "Example 1. An EC2 Boto example"
+msgstr ""
+
+#: ../../optional_installation.rst:783
+# 280894a2c7214f7385efe46698611dbb
+msgid "Second is an S3 example. The S3 interface in CloudStack is obsolete. If you need an S3 interface you should look at systems like RiakCS, Ceph or GlusterFS. This example is here for completeness and can be adapted to other S3 endpoint."
+msgstr ""
+
+#: ../../optional_installation.rst:785
+# e2b2412c5c9546e489607ec6759b33dd
+msgid "Example 2. An S3 Boto Example"
+msgstr ""
+
http://git-wip-us.apache.org/repos/asf/cloudstack-docs-install/blob/bd81bcc4/source/locale/pot/qig.pot
----------------------------------------------------------------------
diff --git a/source/locale/pot/qig.pot b/source/locale/pot/qig.pot
new file mode 100644
index 0000000..59c1c00
--- /dev/null
+++ b/source/locale/pot/qig.pot
@@ -0,0 +1,682 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2014, Apache Software Foundation
+# This file is distributed under the same license as the Apache CloudStack Installation Documentation package.
+# FIRST AUTHOR <EM...@ADDRESS>, YEAR.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: Apache CloudStack Installation Documentation 4\n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2014-03-31 14:02-0400\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"
+
+#: ../../qig.rst:2
+# 35e1fe047cc845ec9cb1bf425e7fc7e3
+msgid "Quick Installation Guide for CentOS"
+msgstr ""
+
+#: ../../qig.rst:6
+# 13fd6d1d11de41d6832a347676bea1a1
+msgid "Overview"
+msgstr ""
+
+#: ../../qig.rst:9
+# 3e45fb1727574a908f313db6c4e826c2
+msgid "What exactly are we building?"
+msgstr ""
+
+#: ../../qig.rst:11
+# 97084d2754134b85ba4376391b983895
+msgid "Infrastructure-as-a-Service (IaaS) clouds can be a complex thing to build, and by definition they have a plethora of options, which often lead to confusion for even experienced admins who are newcomers to building cloud platforms. The goal for this runbook is to provide a straightforward set of instructions to get you up and running with CloudStack with a minimum amount of trouble."
+msgstr ""
+
+#: ../../qig.rst:18
+# e910a84892ff4ab18b24d9f012210b54
+msgid "High level overview of the process"
+msgstr ""
+
+#: ../../qig.rst:20
+# 51759713fe8a463a931bb68bfe5988f4
+msgid "This runbook will focus on building a CloudStack cloud using KVM with CentOS 6.4 with NFS storage on a flat layer-2 network utilizing layer-3 network isolation (aka Security Groups), and doing it all on a single piece of hardware."
+msgstr ""
+
+#: ../../qig.rst:23
+# 3f504f52a12f45a69e00649499ee1c48
+msgid "KVM, or Kernel-based Virtual Machine is a virtualization technology for the Linux kernel. KVM supports native virtualization atop processors with hardware virtualization extensions."
+msgstr ""
+
+#: ../../qig.rst:26
+# 52a1da07ea634d99a588b52b490fe029
+msgid "Security Groups act as distributed firewalls that control access to a group of virtual machines."
+msgstr ""
+
+#: ../../qig.rst:30
+#: ../../qig.rst:367
+# 933834c0d8504b24b0847d8b20a8b773
+# 5fe6ffbe83414152bc5371356ba85caa
+msgid "Prerequisites"
+msgstr ""
+
+#: ../../qig.rst:32
+# aaeb5e052cc5479b9715063a0c52cbd7
+msgid "To complete this runbook you'll need the following items:"
+msgstr ""
+
+#: ../../qig.rst:34
+# 111e363cb216467580fb2e67adffab12
+msgid "At least one computer which supports hardware virtualization."
+msgstr ""
+
+#: ../../qig.rst:35
+# 940dcf9f700447b2911787c759e0fda9
+msgid "The `CentOS 6.4 x86_64 minimal install CD <http://mirrors.kernel.org/centos/6.4/isos/x86_64/CentOS-6.4-x86_64-minimal.iso>`_"
+msgstr ""
+
+#: ../../qig.rst:36
+# ab275f0fbbf84fd287e0d151ebe2ad0f
+msgid "A /24 network with the gateway being at xxx.xxx.xxx.1, no DHCP should be on this network and none of the computers running CloudStack will have a dynamic address. Again this is done for the sake of simplicity."
+msgstr ""
+
+#: ../../qig.rst:39
+# 285d826bba724e4798020e2e5b5e14b4
+msgid "Environment"
+msgstr ""
+
+#: ../../qig.rst:41
+# 912ea3a31cdf4633a553f917ac36564b
+msgid "Before you begin , you need to prepare the environment before you install CloudStack. We will go over the steps to prepare now."
+msgstr ""
+
+#: ../../qig.rst:45
+# fbcdb706775c41f6b8cb192ceaf7efdd
+msgid "Operating System"
+msgstr ""
+
+#: ../../qig.rst:47
+# 19cc8786321b4ff586be0f93ddde1d43
+msgid "Using the CentOS 6.4 x86_64 minimal install ISO, you'll need to install CentOS on your hardware. The defaults will generally be acceptable for this installation."
+msgstr ""
+
+#: ../../qig.rst:50
+# ec66f0260d7f441582177488f136dc5a
+msgid "Once this installation is complete, you'll want to connect to your freshly installed machine via SSH as the root user. Note that you should not allow root logins in a production environment, so be sure to turn off remote logins once you have finished the installation and configuration."
+msgstr ""
+
+#: ../../qig.rst:57
+# 2cf9d6390b3b4d1b89f4c5995fe8a67e
+msgid "Configuring the network"
+msgstr ""
+
+#: ../../qig.rst:59
+# 150faa9055944d9bbd123036744f185f
+msgid "By default the network will not come up on your hardware and you will need to configure it to work in your environment. Since we specified that there will be no DHCP server in this environment we will be manually configuring your network interface. We will assume, for the purposes of this exercise, that eth0 is the only network interface that will be connected and used."
+msgstr ""
+
+#: ../../qig.rst:64
+# 70d1a82edc1b4576aa842e59835c7b4a
+msgid "Connecting via the console you should login as root. Check the file /etc/sysconfig/network-scripts/ifcfg-eth0, it will look like this by default:"
+msgstr ""
+
+#: ../../qig.rst:74
+# a8f443d9c12f46beae544e5fc64b926c
+msgid "Unfortunately, this configuration will not permit you to connect to the network, and is also unsuitable for our purposes with CloudStack. We want to configure that file so that it specifies the IP address, netmask, etc., as shown in the following example:"
+msgstr ""
+
+#: ../../qig.rst:78
+# b949efbf268a4a40a50392d4b10aa99b
+msgid "You should not use the Hardware Address (aka the MAC address) from our example for your configuration. It is network interface specific, so you should keep the address already provided in the HWADDR directive."
+msgstr ""
+
+#: ../../qig.rst:94
+# 6f10b42e84f44c048eea36f0f5929cf8
+msgid "IP Addressing Throughout this document we are assuming that you will have a /24 network for your CloudStack implementation. This can be any RFC 1918 network. However, we are assuming that you will match the machine address that we are using. Thus we may use 172.16.10.2 and because you might be using the 192.168.55.0/24 network you would use 192.168.55.2"
+msgstr ""
+
+#: ../../qig.rst:97
+# bd025ea01c354438985e1b7354460eca
+msgid "Now that we have the configuration files properly set up, we need to run a few commands to start up the network:"
+msgstr ""
+
+#: ../../qig.rst:108
+# ece8bcbdd26a499888b015e0c398a5f8
+msgid "Hostname"
+msgstr ""
+
+#: ../../qig.rst:110
+# e9a0e2949a9a4ba18a6b3b9b82343e70
+msgid "CloudStack requires that the hostname be properly set. If you used the default options in the installation, then your hostname is currently set to localhost.localdomain. To test this we will run:"
+msgstr ""
+
+#: ../../qig.rst:117
+# a222d511c5534fdbadc2d0cc3eb11659
+msgid "At this point it will likely return:"
+msgstr ""
+
+#: ../../qig.rst:123
+# d1f4e65c31ba496ebb5debe5420b4654
+msgid "To rectify this situation - we'll set the hostname by editing the /etc/hosts file so that it follows a similar format to this example:"
+msgstr ""
+
+#: ../../qig.rst:132
+# 50dd670f31394db08fffc5c81cd9eebe
+msgid "After you've modified that file, go ahead and restart the network using:"
+msgstr ""
+
+#: ../../qig.rst:138
+# b761577409834fab96e4ab9cec66d1f3
+msgid "Now recheck with the hostname --fqdn command and ensure that it returns a FQDN response"
+msgstr ""
+
+#: ../../qig.rst:143
+# b8ef5abf6cda4d47827398dfe9e7b078
+msgid "SELinux"
+msgstr ""
+
+#: ../../qig.rst:145
+# 222d16fa0fe040bc848ee97bdefdf32a
+msgid "At the moment, for CloudStack to work properly SELinux must be set to permissive. We want to both configure this for future boots and modify it in the current running system."
+msgstr ""
+
+#: ../../qig.rst:148
+# accdcff2faf84f67a75afdf3f7803df0
+msgid "To configure SELinux to be permissive in the running system we need to run the following command:"
+msgstr ""
+
+#: ../../qig.rst:154
+# 705fd51d1b2d4dc7b66823bbb89721a7
+msgid "To ensure that it remains in that state we need to configure the file /etc/selinux/config to reflect the permissive state, as shown in this example:"
+msgstr ""
+
+#: ../../qig.rst:173
+# 2499a5b702c84346869908b6401a7fe9
+msgid "NTP"
+msgstr ""
+
+#: ../../qig.rst:175
+# 5b46c1b4ccb1446ebad10da4a83212ad
+msgid "NTP configuration is a necessity for keeping all of the clocks in your cloud servers in sync. However, NTP is not installed by default. So we'll install and and configure NTP at this stage. Installation is accomplished as follows:"
+msgstr ""
+
+#: ../../qig.rst:182
+# 781db9fed4274636a5f465d65ae96cdd
+msgid "The actual default configuration is fine for our purposes, so we merely need to enable it and set it to start on boot as follows:"
+msgstr ""
+
+#: ../../qig.rst:193
+# a294af76e3c44e9ebd2175352f4df7fe
+msgid "Configuring the CloudStack Package Repository"
+msgstr ""
+
+#: ../../qig.rst:195
+# f31fe230f7e5445aa4c82ee3de4437a4
+msgid "We need to configure the machine to use a CloudStack package repository."
+msgstr ""
+
+#: ../../qig.rst:197
+# cd8c29304b6e4a52bbc897c9b67179ae
+msgid "The Apache CloudStack official releases are source code. As such there are no 'official' binaries available. The full installation guide describes how to take the source release and generate RPMs and and yum repository. This guide attempts to keep things as simple as possible, and thus we are using one of the community-provided yum repositories."
+msgstr ""
+
+#: ../../qig.rst:199
+# e2256262d9354b479703bcb76f59ce3d
+msgid "To add the CloudStack repository, create /etc/yum.repos.d/cloudstack.repo and insert the following information."
+msgstr ""
+
+#: ../../qig.rst:210
+# 66953d7bf28b44b5bd9b9b0d6f8842b5
+msgid "NFS"
+msgstr ""
+
+#: ../../qig.rst:212
+# a1a2e7eb7b184e1f93370ed838c28bb7
+msgid "Our configuration is going to use NFS for both primary and secondary storage. We are going to go ahead and setup two NFS shares for those purposes. We'll start out by installing nfs-utils."
+msgstr ""
+
+#: ../../qig.rst:219
+# 7ec076aa37eb4c08ba78355e113e34ec
+msgid "We now need to configure NFS to serve up two different shares. This is handled comparatively easily in the /etc/exports file. You should ensure that it has the following content:"
+msgstr ""
+
+#: ../../qig.rst:227
+# 5162dcde2db840b88e95999c228067f3
+msgid "You will note that we specified two directories that don't exist (yet) on the system. We'll go ahead and create those directories and set permissions appropriately on them with the following commands:"
+msgstr ""
+
+#: ../../qig.rst:235
+# 03d619dc4fc14523b11009f6ae99c210
+msgid "CentOS 6.x releases use NFSv4 by default. NFSv4 requires that domain setting matches on all clients. In our case, the domain is cloud.priv, so ensure that the domain setting in /etc/idmapd.conf is uncommented and set as follows: Domain = cloud.priv"
+msgstr ""
+
+#: ../../qig.rst:239
+# 79823f78fc3449d2bdb08b29fdbc0c4e
+msgid "Now you'll need uncomment the configuration values in the file /etc/sysconfig/nfs"
+msgstr ""
+
+#: ../../qig.rst:250
+# 93af69ba8271458f998954d475299208
+msgid "Now we need to configure the firewall to permit incoming NFS connections. Edit the file /etc/sysconfig/iptables"
+msgstr ""
+
+#: ../../qig.rst:266
+# a74fdf52538345818c2f91d9c3a91c4f
+msgid "Now you can restart the iptables service with the following command:"
+msgstr ""
+
+#: ../../qig.rst:272
+# b9b53885032a4cdd91bdf793191c64bc
+msgid "We now need to configure the nfs service to start on boot and actually start it on the host by executing the following commands:"
+msgstr ""
+
+#: ../../qig.rst:283
+# 9d9957f9b1494c8a879c3ed7060f2a56
+msgid "Management Server Installation"
+msgstr ""
+
+#: ../../qig.rst:285
+# ccddb1a218184fe1804636347c2e1ea4
+msgid "We're going to install the CloudStack management server and surrounding tools."
+msgstr ""
+
+#: ../../qig.rst:288
+# 6b8c70ea2ce24b1e877242cd4a3c0c5b
+msgid "Database Installation and Configuration"
+msgstr ""
+
+#: ../../qig.rst:290
+# 89e46187899144059e8c6d9885e80523
+msgid "We'll start with installing MySQL and configuring some options to ensure it runs well with CloudStack."
+msgstr ""
+
+#: ../../qig.rst:292
+# 31d2de49a29f461b849def0a134a9376
+msgid "Install by running the following command:"
+msgstr ""
+
+#: ../../qig.rst:298
+# ed69068b6d824d11bbbfb621bcfede98
+msgid "With MySQL now installed we need to make a few configuration changes to /etc/my.cnf. Specifically we need to add the following options to the [mysqld] section:"
+msgstr ""
+
+#: ../../qig.rst:309
+# 1dc8c451832547a6b1e244186cc5f44d
+msgid "Now that MySQL is properly configured we can start it and configure it to start on boot as follows:"
+msgstr ""
+
+#: ../../qig.rst:317
+#: ../../qig.rst:383
+# 2828c68eb95b488ab76e26c9f13daac3
+# ffd327842b864f27ba9d3a470b64741c
+msgid "Installation"
+msgstr ""
+
+#: ../../qig.rst:319
+# c72e0c93973d4148b55d981606867b18
+msgid "We are now going to install the management server. We do that by executing the following command:"
+msgstr ""
+
+#: ../../qig.rst:325
+# 614e39ce470c41d8b0608e86e95cf9b3
+msgid "With the application itself installed we can now setup the database, we'll do that with the following command and options:"
+msgstr ""
+
+#: ../../qig.rst:331
+# 53ea489ea49644bf92ec9aaa9700708f
+msgid "When this process is finished, you should see a message like \"CloudStack has successfully initialized the database.\""
+msgstr ""
+
+#: ../../qig.rst:333
+# 95f99a12e8bd4aa493624e57d12571ad
+msgid "Now that the database has been created, we can take the final step in setting up the management server by issuing the following command:"
+msgstr ""
+
+#: ../../qig.rst:341
+# ea6b184f33a94091b0bed2ab097f8104
+msgid "System Template Setup"
+msgstr ""
+
+#: ../../qig.rst:343
+# 9acb4839221b4d7d8ccd58902f606742
+msgid "CloudStack uses a number of system VMs to provide functionality for accessing the console of virtual machines, providing various networking services, and managing various aspects of storage. This step will acquire those system images ready for deployment when we bootstrap your cloud."
+msgstr ""
+
+#: ../../qig.rst:347
+# 23d5ace61a844520b9920490c9839ef1
+msgid "Now we need to download the system VM template and deploy that to the share we just mounted. The management server includes a script to properly manipulate the system VMs images."
+msgstr ""
+
+#: ../../qig.rst:356
+# 7a0469d4fa064b36b21e822e809c0417
+msgid "That concludes our setup of the management server. We still need to configure CloudStack, but we will do that after we get our hypervisor set up."
+msgstr ""
+
+#: ../../qig.rst:360
+# 6cb86fea04e340f1a3c317bd06393ffe
+msgid "KVM Setup and Installation"
+msgstr ""
+
+#: ../../qig.rst:362
+# 694238d19b1d47dc8dbb9f9d716e5a03
+msgid "KVM is the hypervisor we'll be using - we will recover the initial setup which has already been done on the hypervisor host and cover installation of the agent software, you can use the same steps to add additional KVM nodes to your CloudStack environment."
+msgstr ""
+
+#: ../../qig.rst:369
+# 7f7906b3ab8f4e90b0a96c5e08fb16b3
+msgid "We explicitly are using the management server as a compute node as well, which means that we have already performed many of the prerequisite steps when setting up the management server, but we will list them here for clarity. Those steps are:"
+msgstr ""
+
+#: ../../qig.rst:373
+# 88d4443c0c6e4d5cb94fb08f4407f561
+msgid ":ref:`conf-network`"
+msgstr ""
+
+#: ../../qig.rst:374
+# 1565cc75629d45f8aef81bdd8927ea71
+msgid ":ref:`conf-hostname`"
+msgstr ""
+
+#: ../../qig.rst:375
+# 5a9d474e2f2840f2b04c16d476f57ab1
+msgid ":ref:`conf-selinux`"
+msgstr ""
+
+#: ../../qig.rst:376
+# 9571423a403c43b9b01e9227094bb987
+msgid ":ref:`conf-ntp`"
+msgstr ""
+
+#: ../../qig.rst:377
+# 514286365b1d431e847609fac32ccb25
+msgid ":ref:`qigconf-pkg-repo`"
+msgstr ""
+
+#: ../../qig.rst:379
+# 6bc0f6aca97a46fba40883c02ea151e5
+msgid "You shouldn't need to do that for the management server, of course, but any additional hosts will need for you to complete the above steps."
+msgstr ""
+
+#: ../../qig.rst:385
+# b17d04cfdc30493f8d8aa1fe31853929
+msgid "Installation of the KVM agent is trivial with just a single command, but afterwards we'll need to configure a few things."
+msgstr ""
+
+#: ../../qig.rst:392
+# e1e1376460914ea5b03cc1ad8d9b6f4d
+msgid "KVM Configuration"
+msgstr ""
+
+#: ../../qig.rst:394
+# 84ac88e7a6334a08a5b1ec8acc5362fb
+msgid "We have two different parts of KVM to configure, libvirt, and QEMU."
+msgstr ""
+
+#: ../../qig.rst:397
+# b3b7762be0a64f4fb7be24536565be97
+msgid "QEMU Configuration"
+msgstr ""
+
+#: ../../qig.rst:399
+# 96fb088976d44b8dad0fbda31afa54a3
+msgid "KVM configuration is relatively simple at only a single item. We need to edit the QEMU VNC configuration. This is done by editing /etc/libvirt/qemu.conf and ensuring the following line is present and uncommented."
+msgstr ""
+
+#: ../../qig.rst:404
+# 071986cd18744d5286dffaeeeb829fcf
+msgid "vnc_listen=0.0.0.0"
+msgstr ""
+
+#: ../../qig.rst:407
+# f799c4c8e1f24eb4828ab3df46c76927
+msgid "Libvirt Configuration"
+msgstr ""
+
+#: ../../qig.rst:409
+# f82cda8366244ba0ab6f46ef74fa3af4
+msgid "CloudStack uses libvirt for managing virtual machines. Therefore it is vital that libvirt is configured correctly. Libvirt is a dependency of cloud-agent and should already be installed."
+msgstr ""
+
+#: ../../qig.rst:411
+# d97f5408e0f44e9890a0378c9bd7dc84
+msgid "In order to have live migration working libvirt has to listen for unsecured TCP connections. We also need to turn off libvirts attempt to use Multicast DNS advertising. Both of these settings are in /etc/libvirt/libvirtd.conf"
+msgstr ""
+
+#: ../../qig.rst:413
+# 8ef93482e0f2443fa83292f7dd2951e5
+msgid "Set the following paramaters:"
+msgstr ""
+
+#: ../../qig.rst:423
+# a0f3e475e15446b98a6715892a799c5d
+msgid "Turning on \"listen_tcp\" in libvirtd.conf is not enough, we have to change the parameters as well we also need to modify /etc/sysconfig/libvirtd:"
+msgstr ""
+
+#: ../../qig.rst:425
+# bcfbfa1f04c4406aada6924aa6027411
+msgid "Uncomment the following line:"
+msgstr ""
+
+#: ../../qig.rst:431
+# 4180d2037c424f7dac00eaecc738bf36
+msgid "Restart libvirt"
+msgstr ""
+
+#: ../../qig.rst:438
+# 64aec4c2321145bc8cb43d87e13ea603
+msgid "KVM configuration complete"
+msgstr ""
+
+#: ../../qig.rst:439
+# 50fd1bf888a64c828d91e6653c0399b1
+msgid "That concludes our installation and configuration of KVM, and we'll now move to using the CloudStack UI for the actual configuration of our cloud."
+msgstr ""
+
+#: ../../qig.rst:443
+# fdf690af3a3f4d94827e349e8c9f227d
+msgid "Configuration"
+msgstr ""
+
+#: ../../qig.rst:445
+# f9efc4e5ffb747c2b2438ae4e5a12c06
+msgid "As we noted before we will be using security groups to provide isolation and by default that implies that we'll be using a flat layer-2 network. It also means that the simplicity of our setup means that we can use the quick installer."
+msgstr ""
+
+#: ../../qig.rst:449
+# 141607a559884ba897e6b3bda8c66d13
+msgid "UI Access"
+msgstr ""
+
+#: ../../qig.rst:451
+# 7c194cdde2f24cf9b0d5b89ac0fa69cf
+msgid "To get access to CloudStack's web interface, merely point your browser to http://172.16.10.2:8080/client The default username is 'admin', and the default password is 'password'. You should see a splash screen that allows you to choose several options for setting up CloudStack. You should choose the Continue with Basic Setup option."
+msgstr ""
+
+#: ../../qig.rst:455
+# f787e14ca1274bf9a979657d7827ed83
+msgid "You should now see a prompt requiring you to change the password for the admin user. Please do so."
+msgstr ""
+
+#: ../../qig.rst:458
+# 0f367054953d45df94b9dc282fcbdec8
+msgid "Setting up a Zone"
+msgstr ""
+
+#: ../../qig.rst:460
+# 5a392849a21f4426865c8b8d121baf52
+msgid "A zone is the largest organization entity in CloudStack - and we'll be creating one, this should be the screen that you see in front of you now. And for us there are 5 pieces of information that we need."
+msgstr ""
+
+#: ../../qig.rst:463
+# 0b2efdf3d1d349638f8fad1d2ce871bb
+msgid "Name - we will set this to the ever-descriptive 'Zone1' for our cloud."
+msgstr ""
+
+#: ../../qig.rst:464
+# e7665d93b6fa417990104bc3921ae545
+msgid "Public DNS 1 - we will set this to '8.8.8.8' for our cloud."
+msgstr ""
+
+#: ../../qig.rst:465
+# 6330777b8a6349789efb90092a35d85d
+msgid "Public DNS 2 - we will set this to '8.8.4.4' for our cloud."
+msgstr ""
+
+#: ../../qig.rst:466
+# 798c3b9e0efa451e9346164b921e3c49
+msgid "Internal DNS1 - we will also set this to '8.8.8.8' for our cloud."
+msgstr ""
+
+#: ../../qig.rst:467
+# 6b22a1c2ada74878a302ab60aee56f69
+msgid "Internal DNS2 - we will also set this to '8.8.4.4' for our cloud."
+msgstr ""
+
+#: ../../qig.rst:470
+# 9b18506e853543ad8b7ec950a00256b3
+msgid "CloudStack distinguishes between internal and public DNS. Internal DNS is assumed to be capable of resolving internal-only hostnames, such as your NFS server’s DNS name. Public DNS is provided to the guest VMs to resolve public IP addresses. You can enter the same DNS server for both types, but if you do so, you must make sure that both internal and public IP addresses can route to the DNS server. In our specific case we will not use any names for resources internally, and we have indeed them set to look to the same external resource so as to not add a namerserver setup to our list of requirements."
+msgstr ""
+
+#: ../../qig.rst:478
+# 6abb7ced848c4d789ccfe5808162738b
+msgid "Pod Configuration"
+msgstr ""
+
+#: ../../qig.rst:480
+# a0be2d6be3b24aeca0648c6c67188f86
+msgid "Now that we've added a Zone, the next step that comes up is a prompt for information regading a pod. Which is looking for several items."
+msgstr ""
+
+#: ../../qig.rst:483
+# 61e16957539b42feafc9a1090cfc8239
+msgid "Name - We'll use Pod1 for our cloud."
+msgstr ""
+
+#: ../../qig.rst:484
+# 3516c658373648e6aef3e62fc367bb08
+msgid "Gateway - We'll use 172.16.10.1 as our gateway"
+msgstr ""
+
+#: ../../qig.rst:485
+# 1cc7b2c550c245bebaa39bdbe9aa45dc
+msgid "Netmask - We'll use 255.255.255.0"
+msgstr ""
+
+#: ../../qig.rst:486
+# aec0c6dd26da432aa6e09f095bb69f98
+msgid "Start/end reserved system IPs - we will use 172.16.10.10-172.16.10.20"
+msgstr ""
+
+#: ../../qig.rst:487
+# c0347e177c1840319abe84a3355e5ca6
+msgid "Guest gateway - We'll use 172.16.10.1"
+msgstr ""
+
+#: ../../qig.rst:488
+# a2c495db56254916b4cc32d1d4473de9
+msgid "Guest netmask - We'll use 255.255.255.0"
+msgstr ""
+
+#: ../../qig.rst:489
+# dba3ac553808478c8ed12106982fbc26
+msgid "Guest start/end IP - We'll use 172.16.10.30-172.16.10.200"
+msgstr ""
+
+#: ../../qig.rst:492
+# 2f7eba54fac04422a40615b154d8a168
+msgid "Cluster"
+msgstr ""
+
+#: ../../qig.rst:494
+# 52c8411631024954acd09ee782f3c5bd
+msgid "Now that we've added a Zone, we need only add a few more items for configuring the cluster."
+msgstr ""
+
+#: ../../qig.rst:496
+# 5f0719aeef1e4566869cf817f6d44bb1
+msgid "Name - We'll use Cluster1"
+msgstr ""
+
+#: ../../qig.rst:497
+# 291858f202db4698a7d5dbfe53aee727
+msgid "Hypervisor - Choose KVM"
+msgstr ""
+
+#: ../../qig.rst:499
+# 1b28f08904864d2fa2dccd5124fadbfb
+msgid "You should be prompted to add the first host to your cluster at this point. Only a few bits of information are needed."
+msgstr ""
+
+#: ../../qig.rst:501
+# 4351e5655a0847ac8ad693dcc8a98e4a
+msgid "Hostname - we'll use the IP address 172.16.10.2 since we didn't set up a DNS server."
+msgstr ""
+
+#: ../../qig.rst:502
+# b6d07aca91e6415cb85fe4539395421a
+msgid "Username - we'll use 'root'"
+msgstr ""
+
+#: ../../qig.rst:503
+# ac3d973254774190b86239a48d6160c8
+msgid "Password - enter the operating system password for the root user"
+msgstr ""
+
+#: ../../qig.rst:506
+# 57352ed645a840d196826dd1ec54a9e4
+msgid "Primary Storage"
+msgstr ""
+
+#: ../../qig.rst:508
+# b21d11da55b945e98d24f3d6edcb44a1
+msgid "With your cluster now setup - you should be prompted for primary storage information. Choose NFS as the storage type and then enter the following values in the fields:"
+msgstr ""
+
+#: ../../qig.rst:511
+# 3cf4f004da814edb9a1bb060c2a2fab2
+msgid "Name - We'll use 'Primary1'"
+msgstr ""
+
+#: ../../qig.rst:512
+# 3d02b6b358d84793ac50c36e649837d8
+msgid "Server - We'll be using the IP address 172.16.10.2"
+msgstr ""
+
+#: ../../qig.rst:513
+# bc63c7c67c34425b87fc91665bd5ab23
+msgid "Path - Well define /primary as the path we are using"
+msgstr ""
+
+#: ../../qig.rst:516
+# e93426f6cbeb4da583fbe5412fcdda37
+msgid "Secondary Storage"
+msgstr ""
+
+#: ../../qig.rst:518
+# eab19f6315b6418992fdeb8091ecc68e
+msgid "If this is a new zone, you'll be prompted for secondary storage information - populate it as follows:"
+msgstr ""
+
+#: ../../qig.rst:520
+# 06a20b9446cc421f8cd379321ed4dd27
+msgid "NFS server - We'll use the IP address 172.16.10.2"
+msgstr ""
+
+#: ../../qig.rst:521
+# b7cb653afafc44cd8f4b96afe0319397
+msgid "Path - We'll use /secondary"
+msgstr ""
+
+#: ../../qig.rst:523
+# 77df86839f944159bc608fdc4cf35b09
+msgid "Now, click Launch and your cloud should begin setup - it may take several minutes depending on your internet connection speed for setup to finalize."
+msgstr ""
+
+#: ../../qig.rst:526
+# 0e8144e3139949fcac955092fb0158da
+msgid "That's it, you are done with installation of your Apache CloudStack cloud."
+msgstr ""
+
http://git-wip-us.apache.org/repos/asf/cloudstack-docs-install/blob/bd81bcc4/source/locale/pot/storage_setup.pot
----------------------------------------------------------------------
diff --git a/source/locale/pot/storage_setup.pot b/source/locale/pot/storage_setup.pot
new file mode 100644
index 0000000..0c266db
--- /dev/null
+++ b/source/locale/pot/storage_setup.pot
@@ -0,0 +1,290 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2014, Apache Software Foundation
+# This file is distributed under the same license as the Apache CloudStack Installation Documentation package.
+# FIRST AUTHOR <EM...@ADDRESS>, YEAR.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: Apache CloudStack Installation Documentation 4\n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2014-03-31 14:02-0400\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"
+
+#: ../../storage_setup.rst:17
+# 17ed172682494e8b8c6d355a2278c9b3
+msgid "Storage Setup"
+msgstr ""
+
+#: ../../storage_setup.rst:19
+# 7d11e73cd30d433e96f11528bd9d6d04
+msgid "CloudStack is designed to work with a wide variety of commodity and enterprise-grade storage. Local disk may be used as well, if supported by the selected hypervisor. Storage type support for guest virtual disks differs based on hypervisor selection."
+msgstr ""
+
+#: ../../storage_setup.rst:25
+# c94de072e4354efcb9cf1c431fe5208d
+msgid "Storage Type"
+msgstr ""
+
+#: ../../storage_setup.rst:25
+# d18f327bf7d04fc68ceb3854a9b4704b
+msgid "XenServer"
+msgstr ""
+
+#: ../../storage_setup.rst:25
+# c929129e73bf4453b140b3acdacb111a
+msgid "vSphere"
+msgstr ""
+
+#: ../../storage_setup.rst:25
+# 7ca508a9e2274e719a2bd4b2dd03640f
+msgid "KVM"
+msgstr ""
+
+#: ../../storage_setup.rst:27
+# 0af2d843775a4a41bd3d207107ffc98a
+msgid "NFS"
+msgstr ""
+
+#: ../../storage_setup.rst:27
+#: ../../storage_setup.rst:27
+#: ../../storage_setup.rst:27
+#: ../../storage_setup.rst:28
+#: ../../storage_setup.rst:29
+#: ../../storage_setup.rst:30
+#: ../../storage_setup.rst:30
+#: ../../storage_setup.rst:30
+# ced51427419342aea2e093f10775389b
+# 53b3cd6b296848728a0e587896a4eb32
+# ae5c43cc24d9444f9d1152ebb1abb314
+# 9cdb9a75580a4a7dba9a1b9fdeba75d5
+# 2c5c287c8b7d4b2f9ae3173a920de77c
+# b57bf035e0c34133a73e0dc3fda6f83b
+# 084b45afcd30436bbcffd9292b44f4b6
+# ac5dd98097c04a3397054ad3a31b536b
+msgid "Supported"
+msgstr ""
+
+#: ../../storage_setup.rst:28
+# cc4863d6cec14abfba5dc5d5fe71ed06
+msgid "iSCSI"
+msgstr ""
+
+#: ../../storage_setup.rst:28
+# 5568566360ed4a2e96bc0a044df1b8f1
+msgid "Supported via VMFS"
+msgstr ""
+
+#: ../../storage_setup.rst:28
+#: ../../storage_setup.rst:29
+# bf03680db5214b19891d087151d77fa3
+# 08cef555b3384544aad1128bf25c09ad
+msgid "Supported via Clustered Filesystems"
+msgstr ""
+
+#: ../../storage_setup.rst:29
+# 33ecfded4b8c43899f8803502a085e4c
+msgid "Fiber Channel"
+msgstr ""
+
+#: ../../storage_setup.rst:29
+# 1e3cd745a284407c804d4f55eeee95d9
+msgid "Supported via Pre-existing SR"
+msgstr ""
+
+#: ../../storage_setup.rst:30
+# 6857cb84dd1b4a38a399fbd8ec080bdd
+msgid "Local Disk"
+msgstr ""
+
+#: ../../storage_setup.rst:33
+# 4f4a07fc994c4474a14bbecd4f7224a8
+msgid "The use of the Cluster Logical Volume Manager (CLVM) for KVM is not officially supported with CloudStack."
+msgstr ""
+
+#: ../../storage_setup.rst:37
+# 6abccb87e5704c76b734285f8be45d7d
+msgid "Small-Scale Setup"
+msgstr ""
+
+#: ../../storage_setup.rst:39
+# a610ffa8e7e24f5d9bec8cc888502cc5
+msgid "In a small-scale setup, a single NFS server can function as both primary and secondary storage. The NFS server just needs to export two separate shares, one for primary storage and the other for secondary storage."
+msgstr ""
+
+#: ../../storage_setup.rst:44
+# b4922519f597410baabdc69df7b3fd0e
+msgid "Secondary Storage"
+msgstr ""
+
+#: ../../storage_setup.rst:46
+# b04077262c0946c480eb115f445ea351
+msgid "CloudStack is designed to work with any scalable secondary storage system. The only requirement is the secondary storage system supports the NFS protocol."
+msgstr ""
+
+#: ../../storage_setup.rst:52
+# aff4c9a619ff40ac9c9c4cfa2bcc0504
+msgid "The storage server should be a machine with a large number of disks. The disks should ideally be managed by a hardware RAID controller. Modern hardware RAID controllers support hot plug functionality independent of the operating system so you can replace faulty disks without impacting the running operating system."
+msgstr ""
+
+#: ../../storage_setup.rst:55
+# e2239020a8b9478297eaee7c11ffd241
+msgid "Example Configurations"
+msgstr ""
+
+#: ../../storage_setup.rst:57
+# 1b77f54232d54c078c077002cf64acf2
+msgid "In this section we go through a few examples of how to set up storage to work properly on a few types of NFS and iSCSI storage systems."
+msgstr ""
+
+#: ../../storage_setup.rst:61
+# 8940c60255074f908a8187d3614589d7
+msgid "Linux NFS on Local Disks and DAS"
+msgstr ""
+
+#: ../../storage_setup.rst:63
+# 1fe1a2cd8a7f4566bd81e8ac11f19db8
+msgid "This section describes how to configure an NFS export on a standard Linux installation. The exact commands might vary depending on the operating system version."
+msgstr ""
+
+#: ../../storage_setup.rst:69
+# daeb1989c05e48eb96cb80b1e8b73a09
+msgid "Install the RHEL/CentOS distribution on the storage server."
+msgstr ""
+
+#: ../../storage_setup.rst:73
+# 44b17d02ddc142d781f934b785cbb1ee
+msgid "If the root volume is more than 2 TB in size, create a smaller boot volume to install RHEL/CentOS. A root volume of 20 GB should be sufficient."
+msgstr ""
+
+#: ../../storage_setup.rst:79
+# 52c6dedf503c47a99d4af6eff668bdb8
+msgid "After the system is installed, create a directory called /export. This can each be a directory in the root partition itself or a mount point for a large disk volume."
+msgstr ""
+
+#: ../../storage_setup.rst:85
+# dbfd8c03524d4ec09efbbcebcf8863a3
+msgid "If you have more than 16TB of storage on one host, create multiple EXT3 file systems and multiple NFS exports. Individual EXT3 file systems cannot exceed 16TB."
+msgstr ""
+
+#: ../../storage_setup.rst:91
+# c5ff7347ad694b26b233f2b5f45b2cb5
+msgid "After /export directory is created, run the following command to configure it as an NFS export."
+msgstr ""
+
+#: ../../storage_setup.rst:98
+# b339dbfaa84a49a784847b51dd27e6db
+msgid "Adjust the above command to suit your deployment needs."
+msgstr ""
+
+#: ../../storage_setup.rst:102
+# 62a467b96dfc4f6e854333d2fe6a2bae
+msgid "**Limiting NFS export.** It is highly recommended that you limit the NFS export to a particular subnet by specifying a subnet mask (e.g.,”192.168.1.0/24”). By allowing access from only within the expected cluster, you avoid having non-pool member mount the storage. The limit you place must include the management network(s) and the storage network(s). If the two are the same network then one CIDR is sufficient. If you have a separate storage network you must provide separate CIDR’s for both or one CIDR that is broad enough to span both."
+msgstr ""
+
+#: ../../storage_setup.rst:112
+#: ../../storage_setup.rst:262
+# 3618428007654967ae072b4aa3ed68fb
+# c5d1dffb89aa49bc8dc26e946f64e684
+msgid "The following is an example with separate CIDRs:"
+msgstr ""
+
+#: ../../storage_setup.rst:120
+#: ../../storage_setup.rst:270
+# 8590afad5a18497993742cea0d7dfbad
+# cc3b910ed64b4912801008923b3c92dd
+msgid "**Removing the async flag.** The async flag improves performance by allowing the NFS server to respond before writes are committed to the disk. Remove the async flag in your mission critical production deployment."
+msgstr ""
+
+#: ../../storage_setup.rst:127
+# 9a0d1e88bf6e43c6beef093a1f233e8c
+msgid "Run the following command to enable NFS service."
+msgstr ""
+
+#: ../../storage_setup.rst:135
+# df13b77bc82a4697b88cc500431fd84d
+msgid "Edit the /etc/sysconfig/nfs file and uncomment the following lines."
+msgstr ""
+
+#: ../../storage_setup.rst:148
+# fdb587673e0441fd8ef48de89def8254
+msgid "Edit the /etc/sysconfig/iptables file and add the following lines at the beginning of the INPUT chain."
+msgstr ""
+
+#: ../../storage_setup.rst:167
+# 4f3ce2e01fdd4a83b694e70c552f8104
+msgid "Reboot the server."
+msgstr ""
+
+#: ../../storage_setup.rst:169
+# ada9a86cba574f01ad3171c4c90671f5
+msgid "An NFS share called /export is now set up."
+msgstr ""
+
+#: ../../storage_setup.rst:173
+# 44c015d5149744cca4dd73176a9c5783
+msgid "When copying and pasting a command, be sure the command has pasted as a single line before executing. Some document viewers may introduce unwanted line breaks in copied text."
+msgstr ""
+
+#: ../../storage_setup.rst:176
+# 69f633d4ddd9442a92426e8f1d756297
+msgid "Linux NFS on iSCSI"
+msgstr ""
+
+#: ../../storage_setup.rst:178
+# cbd4435d24874baea99e74986f508bf2
+msgid "Use the following steps to set up a Linux NFS server export on an iSCSI volume. These steps apply to RHEL/CentOS 5 distributions."
+msgstr ""
+
+#: ../../storage_setup.rst:183
+# 8fdaa46ad64d478c8172d82f7edc77c4
+msgid "Install iscsiadm."
+msgstr ""
+
+#: ../../storage_setup.rst:194
+# 13addec801544136b34266f347c49d6b
+msgid "Discover the iSCSI target."
+msgstr ""
+
+#: ../../storage_setup.rst:200
+#: ../../storage_setup.rst:214
+# 368ce1fcd0b14cf0a973886773545912
+# 72bdbfe556b34079a5a8ff0f3914b781
+msgid "For example:"
+msgstr ""
+
+#: ../../storage_setup.rst:208
+# 250c23d639d2494cab3bc94bf1183908
+msgid "Log in."
+msgstr ""
+
+#: ../../storage_setup.rst:222
+# af5e134497744c98809d3d6432c727d7
+msgid "Discover the SCSI disk. For example:"
+msgstr ""
+
+#: ../../storage_setup.rst:231
+# fb3b8a7fbc7c4e86b9ac32063fdd0990
+msgid "Format the disk as ext3 and mount the volume."
+msgstr ""
+
+#: ../../storage_setup.rst:241
+# f982c97c58274c4798788d392aadfa3d
+msgid "Add the disk to /etc/fstab to make sure it gets mounted on boot."
+msgstr ""
+
+#: ../../storage_setup.rst:247
+# b710b6ab4d8c4fcab9d1d93517a57613
+msgid "Now you can set up /export as an NFS share."
+msgstr ""
+
+#: ../../storage_setup.rst:251
+# c22af6ab5c9747c39af34f6c7b173f31
+msgid "**Limiting NFS export.** In order to avoid data loss, it is highly recommended that you limit the NFS export to a particular subnet by specifying a subnet mask (e.g.,”192.168.1.0/24”). By allowing access from only within the expected cluster, you avoid having non-pool member mount the storage and inadvertently delete all its data. The limit you place must include the management network(s) and the storage network(s). If the two are the same network then one CIDR is sufficient. If you have a separate storage network you must provide separate CIDRs for both or one CIDR that is broad enough to span both."
+msgstr ""
+
[3/7] setup i18n with transifex and sphinx-intl
Posted by se...@apache.org.
http://git-wip-us.apache.org/repos/asf/cloudstack-docs-install/blob/bd81bcc4/source/locale/pot/managing_networks.pot
----------------------------------------------------------------------
diff --git a/source/locale/pot/managing_networks.pot b/source/locale/pot/managing_networks.pot
new file mode 100644
index 0000000..d8ac813
--- /dev/null
+++ b/source/locale/pot/managing_networks.pot
@@ -0,0 +1,6769 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2014, Apache Software Foundation
+# This file is distributed under the same license as the Apache CloudStack Installation Documentation package.
+# FIRST AUTHOR <EM...@ADDRESS>, YEAR.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: Apache CloudStack Installation Documentation 4\n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2014-03-31 14:02-0400\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"
+
+#: ../../managing_networks.rst:17
+# fc6be4b2a5ef4daab75e0149886b57ab
+msgid "Managing Networks and Traffic"
+msgstr ""
+
+#: ../../managing_networks.rst:19
+# e6e873bbde6b490a93904226a79e35e7
+msgid "In a CloudStack, guest VMs can communicate with each other using shared infrastructure with the security and user perception that the guests have a private LAN. The CloudStack virtual router is the main component providing networking features for guest traffic."
+msgstr ""
+
+#: ../../managing_networks.rst:25
+# 158d9384502741139d4db7ad5d35f129
+msgid "Guest Traffic"
+msgstr ""
+
+#: ../../managing_networks.rst:27
+# 79038a2139e34806a98fb5dd5d6b1380
+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 ""
+
+#: ../../managing_networks.rst:32
+# 23f28e25661d4e449f0498521ff811f4
+msgid "See a typical guest traffic setup given below:"
+msgstr ""
+
+#: ../../managing_networks.rst:34
+# 3e47df0ab4fe4f7994d946a031909210
+msgid "|guest-traffic-setup.png: Depicts a guest traffic setup|"
+msgstr ""
+
+#: ../../managing_networks.rst:36
+# 4ddddc3fc73a4867a25fc49b035a99b7
+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 ""
+
+#: ../../managing_networks.rst:47
+# 32df6f633baa46de8a08df89b547bf68
+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 ""
+
+#: ../../managing_networks.rst:52
+# 037184db1823493ab1584e55b5275584
+msgid "Source NAT is automatically configured in the virtual router to forward outbound traffic for all guest VMs"
+msgstr ""
+
+#: ../../managing_networks.rst:56
+# d2daf1fae25745c0a829cd52009d5ac3
+msgid "Networking in a Pod"
+msgstr ""
+
+#: ../../managing_networks.rst:58
+# 3574c26b40ab456e8286506f92bca83c
+msgid "The figure below illustrates network setup within a single pod. The hosts are connected to a pod-level switch. At a minimum, the hosts should have one physical uplink to each switch. Bonded NICs are supported as well. The pod-level switch is a pair of redundant gigabit switches with 10 G uplinks."
+msgstr ""
+
+#: ../../managing_networks.rst:64
+# 35d1da6e0db343f2ae916ce0be527d56
+msgid "|networksinglepod.png: diagram showing logical view of network in a pod|"
+msgstr ""
+
+#: ../../managing_networks.rst:66
+# b7c71c1045954931b9d89bd5843e0306
+msgid "Servers are connected as follows:"
+msgstr ""
+
+#: ../../managing_networks.rst:70
+# 09e404c4512e44e59345fa1f14899f3d
+msgid "Storage devices are connected to only the network that carries management traffic."
+msgstr ""
+
+#: ../../managing_networks.rst:75
+# a3a5ebaa022e413da0ffc6bdae7b6465
+msgid "Hosts are connected to networks for both management traffic and public traffic."
+msgstr ""
+
+#: ../../managing_networks.rst:80
+# bd0d953a458e41eea4bf15edbfb12b2a
+msgid "Hosts are also connected to one or more networks carrying guest traffic."
+msgstr ""
+
+#: ../../managing_networks.rst:83
+# 28c5e92ff62f49bba80dace0b3ae2fb0
+msgid "We recommend the use of multiple physical Ethernet cards to implement each network interface as well as redundant switch fabric in order to maximize throughput and improve reliability."
+msgstr ""
+
+#: ../../managing_networks.rst:88
+# d85d232eadb24f49a48d499c5adf81e7
+msgid "Networking in a Zone"
+msgstr ""
+
+#: ../../managing_networks.rst:90
+# 45168de567df49238a394803bce5aacc
+msgid "The following figure illustrates the network setup within a single zone."
+msgstr ""
+
+#: ../../managing_networks.rst:92
+# 29289f73fcf54224bc331c5454378f15
+msgid "|networksetupzone.png: Depicts network setup in a single zone|"
+msgstr ""
+
+#: ../../managing_networks.rst:94
+# df4e8223cc9c4409adf7cc8c71e7a98e
+msgid "A firewall for management traffic operates in the NAT mode. The network typically is assigned IP addresses in the 192.168.0.0/16 Class B private address space. Each pod is assigned IP addresses in the 192.168.\\*.0/24 Class C private address space."
+msgstr ""
+
+#: ../../managing_networks.rst:99
+# 9886368af88c424183304a4eb31ab641
+msgid "Each zone has its own set of public IP addresses. Public IP addresses from different zones do not overlap."
+msgstr ""
+
+#: ../../managing_networks.rst:103
+# e924366efd4241009758e8896b3e6669
+msgid "Basic Zone Physical Network Configuration"
+msgstr ""
+
+#: ../../managing_networks.rst:105
+# 99801fc2693a463386163a5ba924265b
+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 ""
+
+#: ../../managing_networks.rst:111
+# 4794c328db1440609a15296cef16b874
+msgid "Advanced Zone Physical Network Configuration"
+msgstr ""
+
+#: ../../managing_networks.rst:113
+# 627040abff364b5ea8314a3426b65674
+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 ""
+
+#: ../../managing_networks.rst:118
+# 7d82c9b8761a46dda119e356cf26d478
+msgid "Configure Guest Traffic in an Advanced Zone"
+msgstr ""
+
+#: ../../managing_networks.rst:120
+# 1744b57706544187ae3a8c396a505bf1
+msgid "These steps assume you have already logged in to the CloudStack UI. To configure the base guest network:"
+msgstr ""
+
+#: ../../managing_networks.rst:125
+# 5aecf3d836d747a884b554bca3fbb83d
+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 ""
+
+#: ../../managing_networks.rst:130
+#: ../../managing_networks.rst:214
+#: ../../managing_networks.rst:1585
+# 0cbb909f14cb492385ca0848aa144676
+# ae580367a0aa4a1186f4e67538afff94
+# af249bda556241b28af1cd321cc15602
+msgid "Click the Network tab."
+msgstr ""
+
+#: ../../managing_networks.rst:134
+#: ../../managing_networks.rst:218
+#: ../../managing_networks.rst:1589
+# 7c7e182828424070b9c41369469b65f0
+# 2e538d60fc224c08a46491e983daca7e
+# 44ba62fc316b4753a5d2655c5c666a98
+msgid "Click Add guest network."
+msgstr ""
+
+#: ../../managing_networks.rst:136
+# 15e6873aadaf411c83caf85f0a01dd5e
+msgid "The Add guest network window is displayed:"
+msgstr ""
+
+#: ../../managing_networks.rst:138
+# 0d02390e218c427e9a53bf85ca53de51
+msgid "|addguestnetwork.png: Add guest network setup in a single zone|"
+msgstr ""
+
+#: ../../managing_networks.rst:142
+#: ../../managing_networks.rst:4111
+#: ../../managing_networks.rst:4979
+# 0800e2f4123c4dd9a3cf88e6df107406
+# 9e8f926d35dd4062a29482a8ac99cbde
+# 30dd4c879c8f431d96a1941eb88e5443
+msgid "Provide the following information:"
+msgstr ""
+
+#: ../../managing_networks.rst:146
+# 7604500c996c439089ccdde1d7c025b4
+msgid "**Name**. The name of the network. This will be user-visible"
+msgstr ""
+
+#: ../../managing_networks.rst:150
+# 360746c957d54a70bd23064f9714bf87
+msgid "**Display Text**: The description of the network. This will be user-visible"
+msgstr ""
+
+#: ../../managing_networks.rst:155
+# 4c0edf7e62fb438f9f48989672721586
+msgid "**Zone**: The zone in which you are configuring the guest network."
+msgstr ""
+
+#: ../../managing_networks.rst:159
+# d0157a715ff0417e968114b1c345ed05
+msgid "**Network offering**: If the administrator has configured multiple network offerings, select the one you want to use for this network"
+msgstr ""
+
+#: ../../managing_networks.rst:164
+# 8821fdb0e3e34d4eb2d879f89ef8265f
+msgid "**Guest Gateway**: The gateway that the guests should use"
+msgstr ""
+
+#: ../../managing_networks.rst:168
+# 4dc47880e5f541529ad13f5cf0ca522f
+msgid "**Guest Netmask**: The netmask in use on the subnet the guests will use"
+msgstr ""
+
+#: ../../managing_networks.rst:173
+#: ../../managing_networks.rst:870
+#: ../../managing_networks.rst:1242
+#: ../../managing_networks.rst:1419
+#: ../../managing_networks.rst:1742
+#: ../../managing_networks.rst:3064
+#: ../../managing_networks.rst:3578
+#: ../../managing_networks.rst:4209
+#: ../../managing_networks.rst:4245
+#: ../../managing_networks.rst:5015
+#: ../../managing_networks.rst:5106
+#: ../../managing_networks.rst:5352
+#: ../../managing_networks.rst:5394
+#: ../../managing_networks.rst:6843
+# 84368ab7e8384ed2ae5ecece5835bf18
+# 40ef14b296d343928f7b1af29927beba
+# fd54e59b59e34039ba86fdf384b32bb4
+# d595b9b3106b4a93b86dc8def713e6cf
+# 946c5d37563d43f98c6f39734828f252
+# 8969b38d8d954135bd6fd49ba48540a2
+# 96826bee1eba4ea1bbc5592ab0c19d71
+# b886d197d674421586d115da68f6e823
+# 8a1b58cd366c4d22a2a0ef021bf5439a
+# 8873118788c94bcc91cdcb0412e1f3a9
+# 067481ecae7e42a691ed616190af998f
+# 26e33f314996484ab84cff370047c483
+# 7d0cd95d267b472fb4b0dda772ffc2bc
+# 6ada6497acc04627b1750ff39f3e3b89
+msgid "Click OK."
+msgstr ""
+
+#: ../../managing_networks.rst:176
+# 92ed55846f3943a0899c3de25a023050
+msgid "Configure Public Traffic in an Advanced Zone"
+msgstr ""
+
+#: ../../managing_networks.rst:178
+# 915dafcef9e741c2a3aa241af4f416bf
+msgid "In a zone that uses advanced networking, you need to configure at least one range of IP addresses for Internet traffic."
+msgstr ""
+
+#: ../../managing_networks.rst:182
+# 38eed1230b0548409982c02a9e02c83e
+msgid "Configuring a Shared Guest Network"
+msgstr ""
+
+#: ../../managing_networks.rst:186
+#: ../../managing_networks.rst:760
+#: ../../managing_networks.rst:1557
+# 029160365cb44beeabf86951b8cabbac
+# 5709f6a0aa4d4e87afbf1cd833e9b2f3
+# 390b3883b39c4ad585199248f00069c2
+msgid "Log in to the CloudStack UI as administrator."
+msgstr ""
+
+#: ../../managing_networks.rst:190
+#: ../../managing_networks.rst:1354
+#: ../../managing_networks.rst:1561
+# 6b9a0641eccf4c888cb21525be4ed4c4
+# 25eb0f7c27f44e2983c3f49702a6d79b
+# 10241f1af1c84aa7a72d15d48b14b3e9
+msgid "In the left navigation, choose Infrastructure."
+msgstr ""
+
+#: ../../managing_networks.rst:194
+#: ../../managing_networks.rst:1565
+# 72ac0f8a684a418aa1a522b990724f3c
+# fcdd5db0bcf7487fb69abb38b182c87c
+msgid "On Zones, click View More."
+msgstr ""
+
+#: ../../managing_networks.rst:198
+#: ../../managing_networks.rst:1569
+# 15ee52a81be94e849e9aebbffd80f86e
+# 572f3b0de37d4cde8ee922ca57357102
+msgid "Click the zone to which you want to add a guest network."
+msgstr ""
+
+#: ../../managing_networks.rst:202
+#: ../../managing_networks.rst:776
+#: ../../managing_networks.rst:898
+#: ../../managing_networks.rst:1573
+# c8621ca1f0014cab8a2df11d16b6e23b
+# b0ac7488089d4de49ab63d4714a358d1
+# 67983bfccffe4126b74f01d74445a757
+# c54cc238e91a40e88ebec6ac9a67c3b9
+msgid "Click the Physical Network tab."
+msgstr ""
+
+#: ../../managing_networks.rst:206
+#: ../../managing_networks.rst:1577
+# 819adbe3002443ac81418804a6524958
+# 4f1ac1f461d24c96aac89732394faeb4
+msgid "Click the physical network you want to work with."
+msgstr ""
+
+#: ../../managing_networks.rst:210
+#: ../../managing_networks.rst:1581
+# bf5520949d574c33956b419b623300af
+# a5e3c030c17040fd843946f7acd71beb
+msgid "On the Guest node of the diagram, click Configure."
+msgstr ""
+
+#: ../../managing_networks.rst:220
+#: ../../managing_networks.rst:1591
+# 3a1c06a1806443829aced440705c6ebb
+# 035fafb19b594767b275df96c08bffd8
+msgid "The Add guest network window is displayed."
+msgstr ""
+
+#: ../../managing_networks.rst:224
+#: ../../managing_networks.rst:806
+#: ../../managing_networks.rst:822
+#: ../../managing_networks.rst:856
+#: ../../managing_networks.rst:916
+#: ../../managing_networks.rst:1218
+#: ../../managing_networks.rst:1391
+#: ../../managing_networks.rst:1595
+#: ../../managing_networks.rst:3095
+#: ../../managing_networks.rst:5061
+#: ../../managing_networks.rst:5485
+#: ../../managing_networks.rst:6237
+#: ../../managing_networks.rst:6629
+# 2f740f3f23ab48a29ae3adbaf94c9a76
+# 342b53e57638424dbd3fc25b5de444cc
+# 81cc7e7f5132410a85166b44099c4efd
+# 433cd273bd454f109daafe4144bedce4
+# fbc94c5a87b34f69a0b7ccd2ec2961b8
+# 49a60cbb39104498a256acb82fa540bc
+# d93b5e9a682247d09575b8fed78e8419
+# 17f3af10510b469ab4fa599fdeca5e84
+# 147594fd9398446a9bffe7aa89aa42ae
+# 9d0d76a77389406aa54c77270247fb68
+# 0d313bd3accd40bba047ccbf1b35d224
+# 3daf7170c2984410906999b0b0fa4f3c
+# 2240e232e86f4b3ca8ab2960be6c573b
+msgid "Specify the following:"
+msgstr ""
+
+#: ../../managing_networks.rst:228
+#: ../../managing_networks.rst:1599
+# 14a5b53bcd874033a8eaa789e7c562d1
+# 2f405f166fd04a0bacf050bb1f4f4250
+msgid "**Name**: The name of the network. This will be visible to the user."
+msgstr ""
+
+#: ../../managing_networks.rst:233
+#: ../../managing_networks.rst:1604
+# 0f8d2c8170fd4b98bf717c87aef34378
+# 7585c82a0ece4f368233e94f9d3dfa64
+msgid "**Description**: The short description of the network that can be displayed to users."
+msgstr ""
+
+#: ../../managing_networks.rst:238
+#: ../../managing_networks.rst:1609
+# 99429451759a40f7ba18b278914e39f0
+# 88da596b302847b090b03d4973e86bfd
+msgid "**VLAN ID**: The unique ID of the VLAN."
+msgstr ""
+
+#: ../../managing_networks.rst:242
+# 00c2912dbf2443aa9b3241c8c5676742
+msgid "**Isolated VLAN ID**: The unique ID of the Secondary Isolated VLAN."
+msgstr ""
+
+#: ../../managing_networks.rst:247
+#: ../../managing_networks.rst:1621
+# 6d2136a01445425e94f1ff5205af5c28
+# f35050303cac4011bb97763f32382baf
+msgid "**Scope**: The available scopes are Domain, Account, Project, and All."
+msgstr ""
+
+#: ../../managing_networks.rst:252
+#: ../../managing_networks.rst:1626
+# fe3608c2f3b3416aa62072104aa0fa8e
+# 21c43e42d8d34b4c97f8065f32bdae9e
+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 ""
+
+#: ../../managing_networks.rst:260
+#: ../../managing_networks.rst:1634
+# 5703f6a9a2db4216aca3b448df168a2a
+# a98df446d79849acbcf910ae486f9f24
+msgid "**Account**: The account for which the guest network is being created for. You must specify the domain the account belongs to."
+msgstr ""
+
+#: ../../managing_networks.rst:266
+#: ../../managing_networks.rst:1640
+# a1006b86f9414bee862542a9fe33ea89
+# 7431a628570b4f8f941f22c0dbca0d10
+msgid "**Project**: The project for which the guest network is being created for. You must specify the domain the project belongs to."
+msgstr ""
+
+#: ../../managing_networks.rst:272
+#: ../../managing_networks.rst:1646
+# 8b76a654149140adb4fb77dc2eaa7f03
+# 86babff897704393a7a47fac16fdb6da
+msgid "**All**: The guest network is available for all the domains, account, projects within the selected zone."
+msgstr ""
+
+#: ../../managing_networks.rst:277
+#: ../../managing_networks.rst:1651
+# abea434f07f34363afcd9c5acb702a37
+# 1367c8fe48974b6b8fcef96e9154b1f5
+msgid "**Network Offering**: If the administrator has configured multiple network offerings, select the one you want to use for this network."
+msgstr ""
+
+#: ../../managing_networks.rst:283
+#: ../../managing_networks.rst:1657
+# 699e9d5856cb463885a05f687b080247
+# 433ee2c2a4084f46956487e77324431b
+msgid "**Gateway**: The gateway that the guests should use."
+msgstr ""
+
+#: ../../managing_networks.rst:287
+#: ../../managing_networks.rst:1661
+# ce51526eaf0744f69498878264436b85
+# 45bbdda7a102498a9f476b2cdb175fd2
+msgid "**Netmask**: The netmask in use on the subnet the guests will use."
+msgstr ""
+
+#: ../../managing_networks.rst:291
+#: ../../managing_networks.rst:1665
+# 6dbeaf06a3e14f82aa81cb65f66d29f5
+# 4eec9a4a29fa4d52a6b4337a8a50155c
+msgid "**IP Range**: A range of IP addresses that are accessible from the Internet and are assigned to the guest VMs."
+msgstr ""
+
+#: ../../managing_networks.rst:294
+# 6136c512a7fd43cf949e71c315564e8e
+msgid "If one NIC is used, these IPs should be in the same CIDR in the case of IPv6."
+msgstr ""
+
+#: ../../managing_networks.rst:299
+# 2049d251d6d24864be2401aae7d15eda
+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 ""
+
+#: ../../managing_networks.rst:306
+#: ../../managing_networks.rst:1670
+# 2eb61bdd6e2e4d0fb52eb0f2ab77e5c3
+# eb07ff88c573443cbf65bd9790a02d7e
+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 ""
+
+#: ../../managing_networks.rst:312
+#: ../../managing_networks.rst:1676
+#: ../../managing_networks.rst:3133
+#: ../../managing_networks.rst:3172
+#: ../../managing_networks.rst:4450
+# 01a5c1ddc4284bf7bb918c2924b99144
+# 29e37ee9c31a42b3b19bbd29b62699db
+# 5b8546575cc143e6aa6df3a739ec2dd4
+# c9c0a1842e2243cbbfbdd7bda9f8c173
+# 62ad85eee39c492e951ac8ef8cc0f1de
+msgid "Click OK to confirm."
+msgstr ""
+
+#: ../../managing_networks.rst:315
+# 0ba3f54aff874d7eb78409feb3e574cb
+msgid "Using Multiple Guest Networks"
+msgstr ""
+
+#: ../../managing_networks.rst:317
+# 9ee699c8fe6347568730b54b7737afe5
+msgid "In zones that use advanced networking, additional networks for guest traffic may be added at any time after the initial installation. You can also customize the domain name associated with the network by specifying a DNS suffix for each network."
+msgstr ""
+
+#: ../../managing_networks.rst:322
+# cb2cfc8f5dd14b6a8d4c568329b1bc9e
+msgid "A VM's networks are defined at VM creation time. A VM cannot add or remove networks after it has been created, although the user can go into the guest and remove the IP address from the NIC on a particular network."
+msgstr ""
+
+#: ../../managing_networks.rst:327
+# 044af5c71d054ac780d922e821f138a2
+msgid "Each VM has just one default network. The virtual router's DHCP reply will set the guest's default gateway as that for the default network. Multiple non-default networks may be added to a guest in addition to the single, required default network. The administrator can control which networks are available as the default network."
+msgstr ""
+
+#: ../../managing_networks.rst:333
+# 0adbfc444f2b4c1db5edbdd5b7d6bbea
+msgid "Additional networks can either be available to all accounts or be assigned to a specific account. Networks that are available to all accounts are zone-wide. Any user with access to the zone can create a VM with access to that network. These zone-wide networks provide little or no isolation between guests.Networks that are assigned to a specific account provide strong isolation."
+msgstr ""
+
+#: ../../managing_networks.rst:341
+# b7306772cd68452da7fcba1da1f76cb7
+msgid "Adding an Additional Guest Network"
+msgstr ""
+
+#: ../../managing_networks.rst:345
+#: ../../managing_networks.rst:412
+#: ../../managing_networks.rst:477
+#: ../../managing_networks.rst:508
+#: ../../managing_networks.rst:543
+#: ../../managing_networks.rst:686
+#: ../../managing_networks.rst:1196
+#: ../../managing_networks.rst:1249
+#: ../../managing_networks.rst:1350
+#: ../../managing_networks.rst:1722
+#: ../../managing_networks.rst:1799
+#: ../../managing_networks.rst:2157
+#: ../../managing_networks.rst:3200
+#: ../../managing_networks.rst:3243
+#: ../../managing_networks.rst:3286
+#: ../../managing_networks.rst:3362
+#: ../../managing_networks.rst:3464
+#: ../../managing_networks.rst:3611
+#: ../../managing_networks.rst:3743
+#: ../../managing_networks.rst:4095
+#: ../../managing_networks.rst:4219
+#: ../../managing_networks.rst:4252
+#: ../../managing_networks.rst:4349
+#: ../../managing_networks.rst:4542
+#: ../../managing_networks.rst:4963
+#: ../../managing_networks.rst:5028
+#: ../../managing_networks.rst:5156
+#: ../../managing_networks.rst:5238
+#: ../../managing_networks.rst:5406
+#: ../../managing_networks.rst:5643
+#: ../../managing_networks.rst:5735
+#: ../../managing_networks.rst:5823
+#: ../../managing_networks.rst:5913
+#: ../../managing_networks.rst:6155
+#: ../../managing_networks.rst:6463
+#: ../../managing_networks.rst:6547
+#: ../../managing_networks.rst:6672
+#: ../../managing_networks.rst:6711
+# bbfccf4187ee4d4fbf07e7f4bb88a635
+# 55b4e0f4a10d435781dc67f60c289bcc
+# 448e46420df84abe9fd5e0a98622bd8a
+# 7045e9260e2b41ac88aea79006e38ad5
+# c94a526c0dc04ebba1a701bb33b34bd3
+# 5878e84a00674d17980caa25c5845868
+# 21870457e3e743f78d2afa2427544010
+# c407b2aceffd487888c468b506ec84f2
+# be7946dbd37144e8a9a120d588d4ed8d
+# 57c820671f3e472e80e9758a6875049d
+# 7effce72473246f583a2c6706cf7ae8b
+# 10a47885bc344872bb68acaa38950c56
+# 0e16e2897c2541bdb9a9fe44c7c8c314
+# 69c641cc9e5745699a855b095a3f4234
+# 682913d951a64d7a9672b6c2d8ce61ec
+# b507fdb77c914103931f4382f7e94b6f
+# 69bf185d9530474e9d1e3ac4caccde82
+# 3a12fbb150d4405283cf759bdc0f579c
+# ce1e6561910a4f9b92872de6c4f0fe75
+# 8e6a2cd4f9da4a7da14bd4ff19517c5c
+# 0c0a9fa95a2c4c23affeb329bc18b9cd
+# ba5dc11cd6054bb0842bd0c996926273
+# 0383bb7ab57f403bb4dfdfd3cbe56bad
+# 0ce64e2cda5f451f939117bb581125bb
+# 2e7c7ca911564fd0b55e438fbf85b707
+# 724f938759144bca86466d021cded7cb
+# 3eb23b8ca60f439097e03d61faefe36b
+# a1e4d7e27f0a4bfd89398d6c8e268485
+# 4fdda4830b1d407b8baa1d170ccbd0f5
+# c1fe8cc9534f44f1825f02b028eda7ff
+# 1c6cfb5f62e947c8a05df1bdbca53570
+# 797717e559d24b03951f25f843042245
+# e1e46b9e3b67432eba081e3fa0b0b179
+# 7b6bd9d6ebe042aa817672a63cbdfa37
+# c7d9f6a38d724a9aa8a5caa76ed2d848
+# e6c130b9b73f4034b0e9d9c8a3aaa8dd
+# bdc2624551194b9eadb9cdfdf7403a02
+# c7ca24ebec074700a533736638fefcc0
+msgid "Log in to the CloudStack UI as an administrator or end user."
+msgstr ""
+
+#: ../../managing_networks.rst:349
+#: ../../managing_networks.rst:553
+#: ../../managing_networks.rst:690
+#: ../../managing_networks.rst:1253
+#: ../../managing_networks.rst:2161
+#: ../../managing_networks.rst:3204
+#: ../../managing_networks.rst:3247
+#: ../../managing_networks.rst:3290
+#: ../../managing_networks.rst:3366
+#: ../../managing_networks.rst:3468
+#: ../../managing_networks.rst:4099
+#: ../../managing_networks.rst:4223
+#: ../../managing_networks.rst:4256
+#: ../../managing_networks.rst:4353
+#: ../../managing_networks.rst:4546
+#: ../../managing_networks.rst:4967
+#: ../../managing_networks.rst:5032
+#: ../../managing_networks.rst:5160
+#: ../../managing_networks.rst:5242
+#: ../../managing_networks.rst:5410
+#: ../../managing_networks.rst:5647
+#: ../../managing_networks.rst:5739
+#: ../../managing_networks.rst:5827
+#: ../../managing_networks.rst:5917
+#: ../../managing_networks.rst:6159
+#: ../../managing_networks.rst:6467
+#: ../../managing_networks.rst:6551
+#: ../../managing_networks.rst:6676
+#: ../../managing_networks.rst:6715
+# 542d2aed321d47bdabd1fca487ffd35e
+# e9aad32ba9934dfabf895d86886307b4
+# a64380da9ffa4f209568917d3e2f7ae6
+# f6467d352c5441f3aac59ff1a7e5751e
+# 489eb5a18ecf487089f92e974e4004b2
+# b77e8c3076474667a41f9c643cfb8921
+# 53f468b814a14dc7bc2846e0bb679713
+# b20083aec91a49e38ba1bd1bbd5ca432
+# cc62da2d87294fe59e75b03eab0b30de
+# 89a49e650a154374ac569bb05b88d91f
+# 230865dbd3c4443cb426bb570ee13485
+# 774f364202474a70b77a8561495b3245
+# 0ad7189c21294ef0b43aba32a8bafb7d
+# 726205f734c447d48af0ecd790bd238a
+# fdade5ad8a554d8897cc4e6c27dbc34e
+# 749f818fe9a349f9bb8cb7538cde74f8
+# b444a52f1dd14725bbd9f33966b9b508
+# bdcf2c42e7064f82ade52bd341621f2e
+# b1f4a91afafd4f6e84df0723ead48206
+# 541424f9e38a42d983bb27f87dcd3225
+# b5e9e12abba44624b3b74fc09e0f77fc
+# f392c162ed3241f09fc16f75065cd789
+# 2cd0df6af7ef4a7f9bad72059870b57b
+# e7d42493086e4c04a6545951d4c1ce5b
+# 3f34c206961e4a239714abc14d945f2c
+# d874094ea72f43988a5a4da919c3aae1
+# 0107854a76984dd18cc4256511f643fb
+# 399088fe7776424c8455730cb62a2f94
+# 9eaf23c1feb144f1b0cd1227b0b9ddd1
+msgid "In the left navigation, choose Network."
+msgstr ""
+
+#: ../../managing_networks.rst:353
+# ffe816f2fabe4d698bc426a2756acbe6
+msgid "Click Add guest network. Provide the following information:"
+msgstr ""
+
+#: ../../managing_networks.rst:357
+# e493749a1b58441b9f26c0ff3b13b9a7
+msgid "**Name**: The name of the network. This will be user-visible."
+msgstr ""
+
+#: ../../managing_networks.rst:361
+# e6573973726c48d1a6ddd47d98dfc7d4
+msgid "**Display Text**: The description of the network. This will be user-visible."
+msgstr ""
+
+#: ../../managing_networks.rst:366
+# 12ce0885bb7f4c36890123d1bdbd6b6d
+msgid "**Zone**. The name of the zone this network applies to. Each zone is a broadcast domain, and therefore each zone has a different IP range for the guest network. The administrator must configure the IP range for each zone."
+msgstr ""
+
+#: ../../managing_networks.rst:373
+# 6a5f82ef524445d184e3c139994c446f
+msgid "**Network offering**: If the administrator has configured multiple network offerings, select the one you want to use for this network."
+msgstr ""
+
+#: ../../managing_networks.rst:379
+# d63cb3347919412cb5652d167f3198a0
+msgid "**Guest Gateway**: The gateway that the guests should use."
+msgstr ""
+
+#: ../../managing_networks.rst:383
+# 1da6215b19f84083aeac888d2ef3bff1
+msgid "**Guest Netmask**: The netmask in use on the subnet the guests will use."
+msgstr ""
+
+#: ../../managing_networks.rst:388
+#: ../../managing_networks.rst:3947
+# 4a768d89236c43fd9f2c33eab727c4e8
+# a127adae4308423cb1caf2db8966bdc4
+msgid "Click Create."
+msgstr ""
+
+#: ../../managing_networks.rst:391
+# 21b37eb5b7fe40bd99e0910a9f2bb75a
+msgid "Reconfiguring Networks in VMs"
+msgstr ""
+
+#: ../../managing_networks.rst:393
+# 476864eb3c9c4bccb394ef84b6e0c94b
+msgid "CloudStack provides you the ability to move VMs between networks and reconfigure a VM's network. You can remove a VM from a network and add to a new network. You can also change the default network of a virtual machine. With this functionality, hybrid or traditional server loads can be accommodated with ease."
+msgstr ""
+
+#: ../../managing_networks.rst:399
+# 9e97bafcd742424d921d811f3230a213
+msgid "This feature is supported on XenServer, VMware, and KVM hypervisors."
+msgstr ""
+
+#: ../../managing_networks.rst:402
+#: ../../managing_networks.rst:1517
+# f34aa270088a4613b0a44df4357afc8f
+# 8bd7a92ac32d4a2a929c8af17d3fb170
+msgid "Prerequisites"
+msgstr ""
+
+#: ../../managing_networks.rst:404
+# 145ab5ecce044608b4b9656676c6cfc7
+msgid "Ensure that vm-tools are running on guest VMs for adding or removing networks to work on VMware hypervisor."
+msgstr ""
+
+#: ../../managing_networks.rst:408
+# 5a51c1312ebb4557a8603954294917c7
+msgid "Adding a Network"
+msgstr ""
+
+#: ../../managing_networks.rst:416
+#: ../../managing_networks.rst:481
+#: ../../managing_networks.rst:512
+# ecf6574c795f4768b731ef450b7ae607
+# 3b1c880a36ab4788a672d34d01ef6a4c
+# 49f1a64bc600489b90f669ff77ba9059
+msgid "In the left navigation, click Instances."
+msgstr ""
+
+#: ../../managing_networks.rst:420
+#: ../../managing_networks.rst:485
+#: ../../managing_networks.rst:516
+# 338fcbaeb8724ead9106c34112c862d9
+# bca3b4caf62d4663b33417eb7edaf223
+# f31277b33b9e4e2f9793e5a8ca4d7bb5
+msgid "Choose the VM that you want to work with."
+msgstr ""
+
+#: ../../managing_networks.rst:424
+#: ../../managing_networks.rst:489
+#: ../../managing_networks.rst:520
+# 156d65dc581c4df498395e309bc7cbde
+# e5d8801dfa004ca1b93351677c983d89
+# 469dea7ab2094639b3d9a2299529fc07
+msgid "Click the NICs tab."
+msgstr ""
+
+#: ../../managing_networks.rst:428
+# 1bd7e90630f144b2b08248a827e64b0b
+msgid "Click Add network to VM."
+msgstr ""
+
+#: ../../managing_networks.rst:430
+# 049059a7b43d4efc989e4fcd813e6e1c
+msgid "The Add network to VM dialog is displayed."
+msgstr ""
+
+#: ../../managing_networks.rst:434
+# 5c99fc8205ef493dbab49c0599061a45
+msgid "In the drop-down list, select the network that you would like to add this VM to."
+msgstr ""
+
+#: ../../managing_networks.rst:437
+# 901988536d184641ac9d5ecaaee03ee2
+msgid "A new NIC is added for this network. You can view the following details in the NICs page:"
+msgstr ""
+
+#: ../../managing_networks.rst:442
+# 8d071d6df54845d6a56e7d96321dd7e8
+msgid "ID"
+msgstr ""
+
+#: ../../managing_networks.rst:446
+# ba92b68db3fc48ae810bd43616abc87a
+msgid "Network Name"
+msgstr ""
+
+#: ../../managing_networks.rst:450
+# eefe16e33001458591bb721f9e964a32
+msgid "Type"
+msgstr ""
+
+#: ../../managing_networks.rst:454
+#: ../../managing_networks.rst:4332
+#: ../../managing_networks.rst:4458
+# ce7e7d2354fc48ccb97e1c2917007397
+# 35a3d8a7cc444f7289fff5b3f02731e3
+# 906d6bce91f745de9cc8eb362260b17b
+msgid "IP Address"
+msgstr ""
+
+#: ../../managing_networks.rst:458
+#: ../../managing_networks.rst:4462
+# 07c404d90b444084935108a2905f8147
+# aa4cc5b288b14a26b34b3cd819e6be4e
+msgid "Gateway"
+msgstr ""
+
+#: ../../managing_networks.rst:462
+# da3675e2aed24eb681d8601910102496
+msgid "Netmask"
+msgstr ""
+
+#: ../../managing_networks.rst:466
+# 48374307b68a4eff88c1778ea7bd9380
+msgid "Is default"
+msgstr ""
+
+#: ../../managing_networks.rst:470
+# 2777d60a7bf14a35bd37af5f0ac55458
+msgid "CIDR (for IPv6)"
+msgstr ""
+
+#: ../../managing_networks.rst:473
+# 84f9d9b60c4e4ce4a509cad5b0900a5b
+msgid "Removing a Network"
+msgstr ""
+
+#: ../../managing_networks.rst:493
+# 707d137eb0aa4adaa497aff9a413ad06
+msgid "Locate the NIC you want to remove."
+msgstr ""
+
+#: ../../managing_networks.rst:497
+# c2a07f20886b47be83f065291dfee6fb
+msgid "Click Remove NIC button. |remove-nic.png: button to remove a NIC|"
+msgstr ""
+
+#: ../../managing_networks.rst:501
+#: ../../managing_networks.rst:533
+# b23abd4aac6242bdbc3f97acc2666a90
+# 8f8b04c7921a441ba8480683014b9864
+msgid "Click Yes to confirm."
+msgstr ""
+
+#: ../../managing_networks.rst:504
+# 4f9e35dc3f614384a7505c4161fffaac
+msgid "Selecting the Default Network"
+msgstr ""
+
+#: ../../managing_networks.rst:524
+# 40b332e2efca44c092058585a0004200
+msgid "Locate the NIC you want to work with."
+msgstr ""
+
+#: ../../managing_networks.rst:528
+# 3d3dc6ede8e440efab9778ab27669811
+msgid "Click the Set default NIC button. |set-default-nic.png: button to set a NIC as default one.|"
+msgstr ""
+
+#: ../../managing_networks.rst:536
+# f0c74bc7df3d400bac208e03ca7e454d
+msgid "Changing the Network Offering on a Guest Network"
+msgstr ""
+
+#: ../../managing_networks.rst:538
+# bd0f96f469b24f7cb9efc0e11835fc56
+msgid "A user or administrator can change the network offering that is associated with an existing guest network."
+msgstr ""
+
+#: ../../managing_networks.rst:547
+# 746637ea703149eab979289dea055956
+msgid "If you are changing from a network offering that uses the CloudStack virtual router to one that uses external devices as network service providers, you must first stop all the VMs on the network."
+msgstr ""
+
+#: ../../managing_networks.rst:557
+#: ../../managing_networks.rst:694
+# b06f831436614c7799e92f02062dd02e
+# b2aef771f9cb4102849882e08921deda
+msgid "Click the name of the network you want to modify."
+msgstr ""
+
+#: ../../managing_networks.rst:561
+# 8fe0c8047dd941648bdb27d5c4d46d64
+msgid "In the Details tab, click Edit. |EditButton.png: button to edit a network|"
+msgstr ""
+
+#: ../../managing_networks.rst:566
+# 38ce91cfac534d3d8ce2d2be8ac4d9db
+msgid "In Network Offering, choose the new network offering, then click Apply."
+msgstr ""
+
+#: ../../managing_networks.rst:569
+# 0c9082cd84904f30a842d0296519899f
+msgid "A prompt is displayed asking whether you want to keep the existing CIDR. This is to let you know that if you change the network offering, the CIDR will be affected."
+msgstr ""
+
+#: ../../managing_networks.rst:573
+# 395368811c93495691bd4e308ae0bbc4
+msgid "If you upgrade between virtual router as a provider and an external network device as provider, acknowledge the change of CIDR to continue, so choose Yes."
+msgstr ""
+
+#: ../../managing_networks.rst:579
+# ee09bef0f4f84d41a949984dce97934e
+msgid "Wait for the update to complete. Don’t try to restart VMs until the network change is complete."
+msgstr ""
+
+#: ../../managing_networks.rst:584
+# 7c315c696ed54f5197595376cdd7d0c0
+msgid "If you stopped any VMs, restart them."
+msgstr ""
+
+#: ../../managing_networks.rst:587
+# 92b286db05494a3f9d6591a9f2ccfc6a
+msgid "IP Reservation in Isolated Guest Networks"
+msgstr ""
+
+#: ../../managing_networks.rst:589
+# 67ed578463354e849af5ed40418159aa
+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 ""
+
+#: ../../managing_networks.rst:597
+# d38381f1dad148afb7aeed5ee6e6db41
+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 ""
+
+#: ../../managing_networks.rst:611
+# 3031b1a715ff422bad8de1f97adc2db7
+msgid "IP Reservation Considerations"
+msgstr ""
+
+#: ../../managing_networks.rst:613
+# c57c48d3a65e474c89a99952e65a6a40
+msgid "Consider the following before you reserve an IP range for non-CloudStack machines:"
+msgstr ""
+
+#: ../../managing_networks.rst:618
+# 05c140f272754cfb9d21597b9c778fc5
+msgid "IP Reservation is supported only in Isolated networks."
+msgstr ""
+
+#: ../../managing_networks.rst:622
+# f5211c450a014b0a8d335434d84aa391
+msgid "IP Reservation can be applied only when the network is in Implemented state."
+msgstr ""
+
+#: ../../managing_networks.rst:627
+# 6add1277df044450bce332b364de119b
+msgid "No IP Reservation is done by default."
+msgstr ""
+
+#: ../../managing_networks.rst:631
+# 0847da9c049c4c0da2a6eac963931b02
+msgid "Guest VM CIDR you specify must be a subset of the network CIDR."
+msgstr ""
+
+#: ../../managing_networks.rst:635
+# 36a9bbd09feb416ca7f9ccca3c54eefb
+msgid "Specify a valid Guest VM CIDR. IP Reservation is applied only if no active IPs exist outside the Guest VM CIDR."
+msgstr ""
+
+#: ../../managing_networks.rst:638
+# 191010bd30424f3aa12cf309a48dcfc4
+msgid "You cannot apply IP Reservation if any VM is alloted with an IP address that is outside the Guest VM CIDR."
+msgstr ""
+
+#: ../../managing_networks.rst:643
+# e4b8dc3735d4441ebf832418538d5833
+msgid "To reset an existing IP Reservation, apply IP reservation by specifying the value of network CIDR in the CIDR field."
+msgstr ""
+
+#: ../../managing_networks.rst:646
+# 8281e4ae0c6a4374b25bfef4f7e74405
+msgid "For example, the following table describes three scenarios of guest network creation:"
+msgstr ""
+
+#: ../../managing_networks.rst:650
+# 9f714ae7b5f346bc87da5182136d41e5
+msgid "Case"
+msgstr ""
+
+#: ../../managing_networks.rst:650
+#: ../../managing_networks.rst:3846
+#: ../../managing_networks.rst:4293
+#: ../../managing_networks.rst:4393
+#: ../../managing_networks.rst:4587
+#: ../../managing_networks.rst:5144
+#: ../../managing_networks.rst:5193
+#: ../../managing_networks.rst:5451
+#: ../../managing_networks.rst:5776
+#: ../../managing_networks.rst:5863
+#: ../../managing_networks.rst:5954
+#: ../../managing_networks.rst:6196
+#: ../../managing_networks.rst:6588
+# 43eb64da7dd14977948b1fd136c81c4f
+# ba69ebf50fa04e628494a63c71ee09be
+# 6e509570aefc4ed58372df0bae71f59e
+# e02ce26c53d447cab48c5987becb6178
+# 372de59b30db4b00a1a4a4503aecb29d
+# 0efc90dc789a42219e0e1821921c3a3b
+# 2f722e4bc54941bf9ac18e34ec89ea21
+# 0f4f84fccf1c4879a9ec6691a4abb447
+# 04c82a1485db4a52a0c4fae3e4018e41
+# 8788d910542844b09ae66506304063dc
+# e65e4e6cdcba4f138e43047ff9d3bed6
+# 23d809b6aa20458dacb898b0e8b4d1da
+# cd520efc8baa4344b57bd33b0fa5254d
+msgid "CIDR"
+msgstr ""
+
+#: ../../managing_networks.rst:650
+# 63125858003344c0b965da2ac922cf02
+msgid "Network CIDR"
+msgstr ""
+
+#: ../../managing_networks.rst:650
+# c3c99ba5184c4c9194605bb04a547f39
+msgid "Reserved IP Range for Non-CloudStack VMs"
+msgstr ""
+
+#: ../../managing_networks.rst:650
+# 0e5c1cae0f4d4f06851e27a50273b95c
+msgid "Description"
+msgstr ""
+
+#: ../../managing_networks.rst:652
+#: ../../managing_networks.rst:5146
+# 2e71a7acd08543168d74d2c0d03e0c39
+# d06565ec0d634d848669aa19d123d59a
+msgid "1"
+msgstr ""
+
+#: ../../managing_networks.rst:652
+#: ../../managing_networks.rst:653
+#: ../../managing_networks.rst:654
+# bd4f28e5c83943d8882e2012659415bf
+# 249137a9387145d0ac514e9000be76cd
+# d7c4b09246fb4bfeb5649c2cf6e23d30
+msgid "10.1.1.0/24"
+msgstr ""
+
+#: ../../managing_networks.rst:652
+#: ../../managing_networks.rst:652
+#: ../../managing_networks.rst:654
+#: ../../managing_networks.rst:654
+# 2f9cc88264fb4285bfa3149ea04b26a5
+# d74122c1ce754a1999acc721dfe12491
+# 3e1cad272521413bb73ebf025861f357
+# c9bd04abf9984e3d82a008b15823df6f
+msgid "None"
+msgstr ""
+
+#: ../../managing_networks.rst:652
+# 672d94082a534891849650884d4c25d0
+msgid "No IP Reservation."
+msgstr ""
+
+#: ../../managing_networks.rst:653
+#: ../../managing_networks.rst:5147
+# 7f31ca61138545d19f53bfea0156930f
+# f11cfcf719bc4813a691abc48eef0c50
+msgid "2"
+msgstr ""
+
+#: ../../managing_networks.rst:653
+# 8e804381dca64c3ab199583ca238a7e8
+msgid "10.1.1.0/26"
+msgstr ""
+
+#: ../../managing_networks.rst:653
+# 042cf084bef6418fa9d8ee1a00593e8a
+msgid "10.1.1.64 to 10.1.1.254"
+msgstr ""
+
+#: ../../managing_networks.rst:653
+# 2094d73c4b004d18b9b1c3be4ac72e10
+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 ""
+
+#: ../../managing_networks.rst:654
+# 769561dd7e454a58b571d069407bc84f
+msgid "3"
+msgstr ""
+
+#: ../../managing_networks.rst:654
+# 99819f9f881049da88cf236d227fbcce
+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 ""
+
+#: ../../managing_networks.rst:659
+# af64fa9a0d594bf6aba58e557fb64ef2
+msgid "Limitations"
+msgstr ""
+
+#: ../../managing_networks.rst:663
+# b133ecb14f0743c5aad172cbec921f69
+msgid "The IP Reservation is not supported if active IPs that are found outside the Guest VM CIDR."
+msgstr ""
+
+#: ../../managing_networks.rst:668
+# 9c8183bbe2aa4950a96b3f707269281c
+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 ""
+
+#: ../../managing_networks.rst:674
+# a6037f7354694b7fa3df7eab35ce68a3
+msgid "Best Practices"
+msgstr ""
+
+#: ../../managing_networks.rst:676
+# 1402bdfed0e642a5bc411cad728d629f
+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 ""
+
+#: ../../managing_networks.rst:682
+# 9d8b936d8d924b3e9610e79cea49d7ed
+msgid "Reserving an IP Range"
+msgstr ""
+
+#: ../../managing_networks.rst:698
+# 43313d5d032c4bc1ae00497086042bf1
+msgid "In the Details tab, click Edit. |edit-icon.png: button to edit a network|"
+msgstr ""
+
+#: ../../managing_networks.rst:701
+# 4b6443793ca64ed7b71e9dacebc772c6
+msgid "The CIDR field changes to editable one."
+msgstr ""
+
+#: ../../managing_networks.rst:705
+# 170900f4419c40d3ae77ba9cee3b6fff
+msgid "In CIDR, specify the Guest VM CIDR."
+msgstr ""
+
+#: ../../managing_networks.rst:709
+# 1fccea99506b441bba9fd6fbc76dd995
+msgid "Click Apply."
+msgstr ""
+
+#: ../../managing_networks.rst:711
+# c0734e33a8844d90aac6295573540aee
+msgid "Wait for the update to complete. The Network CIDR and the Reserved IP Range are displayed on the Details page."
+msgstr ""
+
+#: ../../managing_networks.rst:715
+# aad0613e9913469fb756198fc0170632
+msgid "Reserving Public IP Addresses and VLANs for Accounts"
+msgstr ""
+
+#: ../../managing_networks.rst:717
+# 6e44df38576d4f5e99903f26a9db1253
+msgid "CloudStack provides you the ability to reserve a set of public IP addresses and VLANs exclusively for an account. During zone creation, you can continue defining a set of VLANs and multiple public IP ranges. This feature extends the functionality to enable you to dedicate a fixed set of VLANs and guest IP addresses for a tenant."
+msgstr ""
+
+#: ../../managing_networks.rst:723
+# 8da4bb7270e845baa41435d7a8dc2897
+msgid "Note that if an account has consumed all the VLANs and IPs dedicated to it, the account can acquire two more resources from the system. CloudStack provides the root admin with two configuration parameter to modify this default behavior—use.system.public.ips and use.system.guest.vlans. These global parameters enable the root admin to disallow an account from acquiring public IPs and guest VLANs from the system, if the account has dedicated resources and these dedicated resources have all been consumed. Both these configurations are configurable at the account level."
+msgstr ""
+
+#: ../../managing_networks.rst:733
+# 37e6f49f8b53452a8036407ad381ea12
+msgid "This feature provides you the following capabilities:"
+msgstr ""
+
+#: ../../managing_networks.rst:737
+# 671086ca87b14ae28c39b69fd8046953
+msgid "Reserve a VLAN range and public IP address range from an Advanced zone and assign it to an account"
+msgstr ""
+
+#: ../../managing_networks.rst:742
+# 404fcaa9d1b848d2ab247cce5350c281
+msgid "Disassociate a VLAN and public IP address range from an account"
+msgstr ""
+
+#: ../../managing_networks.rst:746
+# bd85bcf3d9394066af54e1e703ae3cf7
+msgid "View the number of public IP addresses allocated to an account"
+msgstr ""
+
+#: ../../managing_networks.rst:750
+# 01799c3a9b364c51b97d539c849d3394
+msgid "Check whether the required range is available and is conforms to account limits."
+msgstr ""
+
+#: ../../managing_networks.rst:753
+# 7716c7ee6e9a4c68bacaaafbba51a78c
+msgid "The maximum IPs per account limit cannot be superseded."
+msgstr ""
+
+#: ../../managing_networks.rst:756
+# 8f2fa2619671428980abde283469e00d
+msgid "Dedicating IP Address Ranges to an Account"
+msgstr ""
+
+#: ../../managing_networks.rst:764
+#: ../../managing_networks.rst:886
+#: ../../managing_networks.rst:2974
+# d7a82a1208db4208961df5b2bda98eb3
+# 3ac411dc4da74e0689c3e931f08d5c59
+# c74ad6e9cbee4ff685cef4af6c1a1c8a
+msgid "In the left navigation bar, click Infrastructure."
+msgstr ""
+
+#: ../../managing_networks.rst:768
+#: ../../managing_networks.rst:890
+# ad2d0d358fab46f69cc0e2834d1025b5
+# 06d4cbfaa106459eb58d6d9bb34a92a1
+msgid "In Zones, click View All."
+msgstr ""
+
+#: ../../managing_networks.rst:772
+#: ../../managing_networks.rst:894
+#: ../../managing_networks.rst:2982
+# 04e17439a9d04d8c92bace413127ce77
+# e40c006773b9414cbe8dd42bb69472d4
+# 03828d4d48bf4770bdc2328f34b55100
+msgid "Choose the zone you want to work with."
+msgstr ""
+
+#: ../../managing_networks.rst:780
+# b2f55880ae154ea5a38880eeeb515690
+msgid "In the Public node of the diagram, click Configure."
+msgstr ""
+
+#: ../../managing_networks.rst:784
+# 790579c6465f4bf88b03caf31b04e907
+msgid "Click the IP Ranges tab."
+msgstr ""
+
+#: ../../managing_networks.rst:786
+# 9136b3e4ca934c23806bbc7ca0ff01e5
+msgid "You can either assign an existing IP range to an account, or create a new IP range and assign to an account."
+msgstr ""
+
+#: ../../managing_networks.rst:791
+# be977158780a4bfca4232fc7d2573dd7
+msgid "To assign an existing IP range to an account, perform the following:"
+msgstr ""
+
+#: ../../managing_networks.rst:795
+# c85643e60bae4ce7a7341f72ed356343
+msgid "Locate the IP range you want to work with."
+msgstr ""
+
+#: ../../managing_networks.rst:799
+# 8c760073c6e140c98957ae64117cd375
+msgid "Click Add Account |addAccount-icon.png: button to assign an IP range to an account.| button."
+msgstr ""
+
+#: ../../managing_networks.rst:802
+# 5907d0ab73b04589b7fba68c857ad361
+msgid "The Add Account dialog is displayed."
+msgstr ""
+
+#: ../../managing_networks.rst:810
+# d84f7b0e62b043939a4656f457f829e7
+msgid "**Account**: The account to which you want to assign the IP address range."
+msgstr ""
+
+#: ../../managing_networks.rst:815
+# 54ea232ef7544939989c85cf78823ab4
+msgid "**Domain**: The domain associated with the account."
+msgstr ""
+
+#: ../../managing_networks.rst:817
+# cac430d036924f38a9290dde3665c841
+msgid "To create a new IP range and assign an account, perform the following:"
+msgstr ""
+
+#: ../../managing_networks.rst:826
+# d50191ed42ad44ee95f6167032a30c65
+msgid "**Gateway**"
+msgstr ""
+
+#: ../../managing_networks.rst:830
+# 13d287dfefa145e3bf443ca11ed78fa2
+msgid "**Netmask**"
+msgstr ""
+
+#: ../../managing_networks.rst:834
+# 2e49c1a58f4a4bfa87d30c1c449df1e3
+msgid "**VLAN**"
+msgstr ""
+
+#: ../../managing_networks.rst:838
+# 8ebc180647e6488db6d7419f0c96d969
+msgid "**Start IP**"
+msgstr ""
+
+#: ../../managing_networks.rst:842
+# 39bbcd6bce9c4acdb1dde4c134d36aee
+msgid "**End IP**"
+msgstr ""
+
+#: ../../managing_networks.rst:846
+# c9ff42e89acd482b839c78ede4bf72a2
+msgid "**Account**: Perform the following:"
+msgstr ""
+
+#: ../../managing_networks.rst:850
+# 4e8c15e78f4040da8818c60242a385f7
+msgid "Click Account."
+msgstr ""
+
+#: ../../managing_networks.rst:852
+# 4d16eeb78e534a4aba7b7c05c335d94a
+msgid "The Add Account page is displayed."
+msgstr ""
+
+#: ../../managing_networks.rst:860
+# 4fcbdb024f3c4d0e916309194ccf9796
+msgid "****Account****: The account to which you want to assign an IP address range."
+msgstr ""
+
+#: ../../managing_networks.rst:865
+#: ../../managing_networks.rst:930
+# 5dd4ec70717a455cb3eae0f191b2c338
+# e1b99db893e94523a9c9c6c2dca5e50a
+msgid "****Domain****: The domain associated with the account."
+msgstr ""
+
+#: ../../managing_networks.rst:874
+#: ../../managing_networks.rst:1919
+#: ../../managing_networks.rst:3411
+#: ../../managing_networks.rst:3511
+#: ../../managing_networks.rst:3667
+#: ../../managing_networks.rst:3899
+#: ../../managing_networks.rst:5623
+# 222bcd68057f4097804636cc658bae40
+# 583b09f47740445cae14b167a426c0d5
+# d8184c325cbe4e2989e1772dd91acd0b
+# b8bdf6dd077f48bab5be9a342447e9d8
+# 221e41362cdb48c1b692cef19b0a8218
+# f241bee872c34bcfa7d43b4601e1cb48
+# 95df29e50c984e798847dc985a455395
+msgid "Click Add."
+msgstr ""
+
+#: ../../managing_networks.rst:877
+# 6f5ed4ecaf104ec089964163e1e6884f
+msgid "Dedicating VLAN Ranges to an Account"
+msgstr ""
+
+#: ../../managing_networks.rst:881
+# 1d96f022bb0641f591f869dcdef945de
+msgid "After the CloudStack Management Server is installed, log in to the CloudStack UI as administrator."
+msgstr ""
+
+#: ../../managing_networks.rst:902
+#: ../../managing_networks.rst:1367
+# b7387ff7ac314fabb59c5c8adb95d64c
+# 09557ffae33041df84505184339ead4d
+msgid "In the Guest node of the diagram, click Configure."
+msgstr ""
+
+#: ../../managing_networks.rst:906
+# fcf27305c8cf42bcaea54b6e0d583e74
+msgid "Select the Dedicated VLAN Ranges tab."
+msgstr ""
+
+#: ../../managing_networks.rst:910
+# 67395673dcac45fd95c09509e40ab195
+msgid "Click Dedicate VLAN Range."
+msgstr ""
+
+#: ../../managing_networks.rst:912
+# ab0efa84cce7484aa1483aa86e7458e3
+msgid "The Dedicate VLAN Range dialog is displayed."
+msgstr ""
+
+#: ../../managing_networks.rst:920
+# 79112ed3b43d4ac9b8ffd92e5be692f1
+msgid "****VLAN Range****: The VLAN range that you want to assign to an account."
+msgstr ""
+
+#: ../../managing_networks.rst:925
+# a99491d184b347ae9692f3140f8507e1
+msgid "****Account****: The account to which you want to assign the selected VLAN range."
+msgstr ""
+
+#: ../../managing_networks.rst:933
+# fcc09f716f8d4237b77cc161171a4261
+msgid "Configuring Multiple IP Addresses on a Single NIC"
+msgstr ""
+
+#: ../../managing_networks.rst:935
+# a94a3710f1234c97836f59a5a07db667
+msgid "CloudStack provides you the ability to associate multiple private IP addresses per guest VM NIC. In addition to the primary IP, you can assign additional IPs to the guest VM NIC. This feature is supported on all the network configurations—Basic, Advanced, and VPC. Security Groups, Static NAT and Port forwarding services are supported on these additional IPs."
+msgstr ""
+
+#: ../../managing_networks.rst:942
+# 494be8c0259840fb84fb26e96d13a908
+msgid "As always, you can specify an IP from the guest subnet; if not specified, an IP is automatically picked up from the guest VM subnet. You can view the IPs associated with for each guest VM NICs on the UI. You can apply NAT on these additional guest IPs by using network configuration option in the CloudStack UI. You must specify the NIC to which the IP should be associated."
+msgstr ""
+
+#: ../../managing_networks.rst:949
+# 925a5eb75fe04c35bfd19b1ac2f44b7e
+msgid "This feature is supported on XenServer, KVM, and VMware hypervisors. Note that Basic zone security groups are not supported on VMware."
+msgstr ""
+
+#: ../../managing_networks.rst:953
+# 5ac573ae5f4345aeb143a5fcc101524d
+msgid "Use Cases"
+msgstr ""
+
+#: ../../managing_networks.rst:955
+# 872874841bbe414a88684eb2a0045657
+msgid "Some of the use cases are described below:"
+msgstr ""
+
+#: ../../managing_networks.rst:959
+# d5c27060797b4aee9174ebb56ffef918
+msgid "Network devices, such as firewalls and load balancers, generally work best when they have access to multiple IP addresses on the network interface."
+msgstr ""
+
+#: ../../managing_networks.rst:965
+# 24ce123387844169a49487bc30845b7a
+msgid "Moving private IP addresses between interfaces or instances. Applications that are bound to specific IP addresses can be moved between instances."
+msgstr ""
+
+#: ../../managing_networks.rst:971
+# 0c37cb7a4c434f399e9d45b1c2e472e9
+msgid "Hosting multiple SSL Websites on a single instance. You can install multiple SSL certificates on a single instance, each associated with a distinct IP address."
+msgstr ""
+
+#: ../../managing_networks.rst:976
+#: ../../managing_networks.rst:6315
+# d4f7b4962530468a906a498acca4bae2
+# 3da7bf4ad1544749bab36764d2d447ef
+msgid "Guidelines"
+msgstr ""
+
+#: ../../managing_networks.rst:978
+# d6caf12c9309436d9de8f99f9c7543c3
+msgid "To prevent IP conflict, configure different subnets when multiple networks are connected to the same VM."
+msgstr ""
+
+#: ../../managing_networks.rst:982
+# 16aeec8d7d974a11ab5270669432a394
+msgid "Assigning Additional IPs to a VM"
+msgstr ""
+
+#: ../../managing_networks.rst:986
+# 034b4e6e920d4b1b819935e74e2b858c
+msgid "Log in to the CloudStack UI."
+msgstr ""
+
+#: ../../managing_networks.rst:990
+# 6a36c11f314b4a73ae436cedecc70f5e
+msgid "In the left navigation bar, click Instances."
+msgstr ""
+
+#: ../../managing_networks.rst:994
+# a8208d3a66ae4646bb1c56d1ecb10311
+msgid "Click the name of the instance you want to work with."
+msgstr ""
+
+#: ../../managing_networks.rst:998
+# 3614c5b73e634141848b9ffd09823e34
+msgid "In the Details tab, click NICs."
+msgstr ""
+
+#: ../../managing_networks.rst:1002
+# 9ddaf912d7f64aa791244c3f89f4f87e
+msgid "Click View Secondary IPs."
+msgstr ""
+
+#: ../../managing_networks.rst:1006
+# 41a35e39fad3445a94b912212054ec76
+msgid "Click Acquire New Secondary IP, and click Yes in the confirmation dialog."
+msgstr ""
+
+#: ../../managing_networks.rst:1009
+# 966f02979ce94ebfad48594d314843e6
+msgid "You need to configure the IP on the guest VM NIC manually. CloudStack will not automatically configure the acquired IP address on the VM. Ensure that the IP address configuration persist on VM reboot."
+msgstr ""
+
+#: ../../managing_networks.rst:1013
+# 6f93e046959a4ebd9133806cbf00c179
+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 StaticNAT rules."
+msgstr ""
+
+#: ../../managing_networks.rst:1018
+# 584ea105deaf4c149e1f4a22e7c76f9c
+msgid "Port Forwarding and StaticNAT Services Changes"
+msgstr ""
+
+#: ../../managing_networks.rst:1020
+# 66fa989a4cf444159810d5b86fe29d71
+msgid "Because multiple IPs can be associated per NIC, you are allowed to select a desired IP for the Port Forwarding and StaticNAT services. The default is the primary IP. To enable this functionality, an extra optional parameter 'vmguestip' is added to the Port forwarding and StaticNAT APIs (enableStaticNat, createIpForwardingRule) to indicate on what IP address NAT need to be configured. If vmguestip is passed, NAT is configured on the specified private IP of the VM. if not passed, NAT is configured on the primary IP of the VM."
+msgstr ""
+
+#: ../../managing_networks.rst:1030
+# d56668f88c1b4778956f3e78eb0af4f3
+msgid "About Multiple IP Ranges"
+msgstr ""
+
+#: ../../managing_networks.rst:1032
+# a425fadff6f24df8a703773e76e1da84
+msgid "The feature can only be implemented on IPv4 addresses."
+msgstr ""
+
+#: ../../managing_networks.rst:1034
+# 085d7bcb306c4df9b4bcb062fa965779
+msgid "CloudStack provides you with the flexibility to add guest IP ranges from different subnets in Basic zones and security groups-enabled Advanced zones. For security groups-enabled Advanced zones, it implies multiple subnets can be added to the same VLAN. With the addition of this feature, you will be able to add IP address ranges from the same subnet or from a different one when IP address are exhausted. This would in turn allows you to employ higher number of subnets and thus reduce the address management overhead. To support this feature, the capability of ``createVlanIpRange`` API is extended to add IP ranges also from a different subnet."
+msgstr ""
+
+#: ../../managing_networks.rst:1045
+# a916ea5fa2a3442cac9346d464c33b3c
+msgid "Ensure that you manually configure the gateway of the new subnet before adding the IP range. Note that CloudStack supports only one gateway for a subnet; overlapping subnets are not currently supported."
+msgstr ""
+
+#: ../../managing_networks.rst:1049
+# 0cb128b2b4964c4c94d50a7d4f4c113d
+msgid "Use the ``deleteVlanRange`` API to delete IP ranges. This operation fails if an IP from the remove range is in use. If the remove range contains the IP address on which the DHCP server is running, CloudStack acquires a new IP from the same subnet. If no IP is available in the subnet, the remove operation fails."
+msgstr ""
+
+#: ../../managing_networks.rst:1055
+# 5c50556940324ae1a2c2f33b4e3be74c
+msgid "This feature is supported on KVM, xenServer, and VMware hypervisors."
+msgstr ""
+
+#: ../../managing_networks.rst:1058
+# 86f5b04f9bf84ff4a0162e548a43ed45
+msgid "About Elastic IP"
+msgstr ""
+
+#: ../../managing_networks.rst:1060
+# 1abc932ae33e4097ad9d5a7c01466858
+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 ""
+
+#: ../../managing_networks.rst:1069
+# 6f92b16714d4455c9c0d07422b7a5278
+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 ""
+
+#: ../../managing_networks.rst:1077
+# 1917b806df094374b24b204ab96801f8
+msgid "|eip-ns-basiczone.png: Elastic IP in a NetScaler-enabled Basic Zone.|"
+msgstr ""
+
+#: ../../managing_networks.rst:1079
+# 3b1d323c9feb4e9ba7ca76be6aaad6b2
+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 ""
+
+#: ../../managing_networks.rst:1088
+# d73486cd06ff42a3b7ae00d650f94b85
+msgid "The EIP work flow is as follows:"
+msgstr ""
+
+#: ../../managing_networks.rst:1092
+# c76961037d5e4684aae701d14e8628ef
+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 ""
+
+#: ../../managing_networks.rst:1098
+# 113a0b56fa5c4d588763310f3344c045
+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 ""
+
+#: ../../managing_networks.rst:1103
+# 26464e6616334eba867bfbedcd8b9b32
+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 ""
+
+#: ../../managing_networks.rst:1107
+# c24df2c0e244417bac058ee69288159e
+msgid "This default public IP will be released in two cases:"
+msgstr ""
+
+#: ../../managing_networks.rst:1111
+# e69a190aa6ff4094a1376bbd1a48c806
+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 ""
+
+#: ../../managing_networks.rst:1117
+# ae09bc75005442799a101c13ee164cfe
+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 ""
+
+#: ../../managing_networks.rst:1125
+# 85b2631843ed40888b2ca7fe400962fd
+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 ""
+
+#: ../../managing_networks.rst:1134
+# 94a57e6c08fb4beeb2cc92ada6ed0e19
+msgid "For more information on the Associate Public IP option, see the Administration Guide."
+msgstr ""
+
+#: ../../managing_networks.rst:1137
+# 51ff3fc654054203b273f9c148ae18b5
+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 ""
+
+#: ../../managing_networks.rst:1139
+# 83364c7e0dd94f759842ac386a8cac79
+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 ""
+
+#: ../../managing_networks.rst:1144
+# 342239c2715c475b88c10804e3612a51
+msgid "Portable IPs"
+msgstr ""
+
+#: ../../managing_networks.rst:1147
+# dd5fc98d73bc4d75beeb09ce0439d181
+msgid "About Portable IP"
+msgstr ""
+
+#: ../../managing_networks.rst:1149
+# 89820f26aa2645078ccb72b82efc9dfe
+msgid "Portable IPs in CloudStack are region-level pool of IPs, which are elastic in nature, that can be transferred across geographically separated zones. As an administrator, you can provision a pool of portable public IPs at region level and are available for user consumption. The users can acquire portable IPs if admin has provisioned portable IPs at the region level they are part of. These IPs can be use for any service within an advanced zone. You can also use portable IPs for EIP services in basic zones."
+msgstr ""
+
+#: ../../managing_networks.rst:1158
+# bd4cf0b29f8b41b3b03e37f656c52501
+msgid "The salient features of Portable IP are as follows:"
+msgstr ""
+
+#: ../../managing_networks.rst:1162
+# 855ab24aced14fa18033b90699abf066
+msgid "IP is statically allocated"
+msgstr ""
+
+#: ../../managing_networks.rst:1166
+# 7e45d53e50814ec584c37135e430715f
+msgid "IP need not be associated with a network"
+msgstr ""
+
+#: ../../managing_networks.rst:1170
+# f4869a8c48e8434ea57e20c6cc65cf55
+msgid "IP association is transferable across networks"
+msgstr ""
+
+#: ../../managing_networks.rst:1174
+# 2f9e4bbd9a5c4a61957b15982551f2e9
+msgid "IP is transferable across both Basic and Advanced zones"
+msgstr ""
+
+#: ../../managing_networks.rst:1178
+# ea6d679d393d4bcfa494249d365ba374
+msgid "IP is transferable across VPC, non-VPC isolated and shared networks"
+msgstr ""
+
+#: ../../managing_networks.rst:1182
+# afa26b14dffe40119ee655d8132db452
+msgid "Portable IP transfer is available only for static NAT."
+msgstr ""
+
+#: ../../managing_networks.rst:1187
+# 671509538e074821aee5d282b4fd3822
+msgid "Before transferring to another network, ensure that no network rules (Firewall, Static NAT, Port Forwarding, and so on) exist on that portable IP."
+msgstr ""
+
+#: ../../managing_networks.rst:1192
+# a10fe6016ca4432d9466323adc5feafa
+msgid "Configuring Portable IPs"
+msgstr ""
+
+#: ../../managing_networks.rst:1200
+# 323070f73d46451b97228b1b4aadaa54
+msgid "In the left navigation, click Regions."
+msgstr ""
+
+#: ../../managing_networks.rst:1204
+# 428125e4de8d4140af2bbdfcd4ecc332
+msgid "Choose the Regions that you want to work with."
+msgstr ""
+
+#: ../../managing_networks.rst:1208
+# eed1d708ff224966a3d021ab2bc33aa6
+msgid "Click View Portable IP."
+msgstr ""
+
+#: ../../managing_networks.rst:1212
+# abc03c1eb418441fb10a7cf6beb37fea
+msgid "Click Portable IP Range."
+msgstr ""
+
+#: ../../managing_networks.rst:1214
+# 595f33e914024c0a86540527bc370258
+msgid "The Add Portable IP Range window is displayed."
+msgstr ""
+
+#: ../../managing_networks.rst:1222
+# ca11f239cc8449a6817014a3adcd61a0
+msgid "**Start IP/ End IP**: A range of IP addresses that are accessible from the Internet and will be allocated to guest VMs. Enter the first and last IP addresses that define a range that CloudStack can assign to guest VMs."
+msgstr ""
+
+#: ../../managing_networks.rst:1229
+# 6c64c167231b40a68bfe26799c8054c3
+msgid "**Gateway**: The gateway in use for the Portable IP addresses you are configuring."
+msgstr ""
+
+#: ../../managing_networks.rst:1234
+# 83455a09e71a4eccb3755e02bd14515c
+msgid "**Netmask**: The netmask associated with the Portable IP range."
+msgstr ""
+
+#: ../../managing_networks.rst:1238
+# 7b8fbceeaf074302abbd838f0e2849bf
+msgid "**VLAN**: The VLAN that will be used for public traffic."
+msgstr ""
+
+#: ../../managing_networks.rst:1245
+# d850eac9d4014f0dab3417fab28601f7
+msgid "Acquiring a Portable IP"
+msgstr ""
+
+#: ../../managing_networks.rst:1257
+#: ../../managing_networks.rst:3208
+#: ../../managing_networks.rst:3251
+#: ../../managing_networks.rst:3294
+#: ../../managing_networks.rst:3370
+# 3262a0725955438a99e78981176d092f
+# 701bcf108f834cdc9c4ea748e804dab0
+# 2859adde9cb44f6e970e1a0651717bed
+# e93c68f572f04989afefcb87f1716ec4
+# 5efad310be724f029a2e40ffd479c432
+msgid "Click the name of the network where you want to work with."
+msgstr ""
+
+#: ../../managing_networks.rst:1261
+#: ../../managing_networks.rst:2170
+#: ../../managing_networks.rst:3212
+#: ../../managing_networks.rst:3255
+#: ../../managing_networks.rst:3298
+#: ../../managing_networks.rst:3374
+#: ../../managing_networks.rst:3784
+# 305ab6c53fda46d8adf4a49df4f72b73
+# 3186a0f1dbbd4b36afd65ce287083ef4
+# 77cf6faa7c404c33bddce8721952e2e2
+# 6fbd7a5b4b7e4fe684956b795c3516f8
+# 6662b46aca0349ffb4f7db65473cf5a4
+# e6ede01e32f44d8d9eb51185ac8cca93
+# c003065bf88441dc838fb6ff067c1d46
+msgid "Click View IP Addresses."
+msgstr ""
+
+#: ../../managing_networks.rst:1265
+#: ../../managing_networks.rst:3216
+# 3cb9985604264815812c496744d99e7a
+# b3b02650cb5849d29899feb56b041267
+msgid "Click Acquire New IP."
+msgstr ""
+
+#: ../../managing_networks.rst:1267
+#: ../../managing_networks.rst:3218
+# 0fd88d76e0454a0aafadff6be75ab526
+# 25404011fc7044529f48e7fb157f04ed
+msgid "The Acquire New IP window is displayed."
+msgstr ""
+
+#: ../../managing_networks.rst:1271
+#: ../../managing_networks.rst:3222
+# ead81d2ea1984be4874b71915d73fe10
+# 6fe5747d6b7547a8918070f73c52cc78
+msgid "Specify whether you want cross-zone IP or not."
+msgstr ""
+
+#: ../../managing_networks.rst:1275
+# d4620b5751e246e48d4c00aca1d4a8f3
+msgid "Click Yes in the confirmation dialog."
+msgstr ""
+
+#: ../../managing_networks.rst:1277
+#: ../../managing_networks.rst:3230
+# 99771ddd9716455ba6a961284174f20b
+# 1ff8f2a384d445a8ba816f2443f9a096
+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 ""
+
+#: ../../managing_networks.rst:1282
+# e9a2afafc0df48bcba35924913d45e73
+msgid "Transferring Portable IP"
+msgstr ""
+
+#: ../../managing_networks.rst:1284
+# 65ca926473184157a1cfd41612675661
+msgid "An IP can be transferred from one network to another only if Static NAT is enabled. However, when a portable IP is associated with a network, you can use it for any service in the network."
+msgstr ""
+
+#: ../../managing_networks.rst:1288
+# 8afb23c700a44791bb6a9fa4690d1649
+msgid "To transfer a portable IP across the networks, execute the following API:"
+msgstr ""
+
+#: ../../managing_networks.rst:1295
+# 55a1869308ee4aed849674dc2535b805
+msgid "Replace the UUID with appropriate UUID. For example, if you want to transfer a portable IP to network X and VM Y in a network, execute the following:"
+msgstr ""
+
+#: ../../managing_networks.rst:1304
+# 3afd351582954a49b746d509abba4eac
+msgid "Multiple Subnets in Shared Network"
+msgstr ""
+
+#: ../../managing_networks.rst:1306
+# 9a2eae7b8f84440f90cd0402d4ed0d76
+msgid "CloudStack provides you with the flexibility to add guest IP ranges from different subnets in Basic zones and security groups-enabled Advanced zones. For security groups-enabled Advanced zones, it implies multiple subnets can be added to the same VLAN. With the addition of this feature, you will be able to add IP address ranges from the same subnet or from a different one when IP address are exhausted. This would in turn allows you to employ higher number of subnets and thus reduce the address management overhead. You can delete the IP ranges you have added."
+msgstr ""
+
+#: ../../managing_networks.rst:1317
+#: ../../managing_networks.rst:2885
+#: ../../managing_networks.rst:3426
+# 344b838f0b0841728cb18a682c1962e2
+# ca130580b3e848d59bbd0823702a71ad
+# 9d4bbe7d6b854394bcbb260e68f1226a
+msgid "Prerequisites and Guidelines"
+msgstr ""
+
+#: ../../managing_networks.rst:1321
+# 231696a9da0c47e5be1d4fec098a8b7f
+msgid "This feature can only be implemented:"
+msgstr ""
+
+#: ../../managing_networks.rst:1325
+# e11af27c4f9b4a68aa2b824c8d51ef26
+msgid "on IPv4 addresses"
+msgstr ""
+
+#: ../../managing_networks.rst:1329
+# 89a310c9cc9a4cc0b046da60d4db626f
+msgid "if virtual router is the DHCP provider"
+msgstr ""
+
+#: ../../managing_networks.rst:1333
+# 2f901469d8a547669181457a79ea3825
+msgid "on KVM, xenServer, and VMware hypervisors"
+msgstr ""
+
+#: ../../managing_networks.rst:1337
+# 07ac9be1fbd949109da3f8269a75cd31
+msgid "Manually configure the gateway of the new subnet before adding the IP range."
+msgstr ""
+
+#: ../../managing_networks.rst:1342
+# fd0dee06ed544e709ea404a01e2141a4
+msgid "CloudStack supports only one gateway for a subnet; overlapping subnets are not currently supported"
+msgstr ""
+
+#: ../../managing_networks.rst:1346
+# cfe0f1c81e094655b1cf2158397f8beb
+msgid "Adding Multiple Subnets to a Shared Network"
+msgstr ""
+
+#: ../../managing_networks.rst:1358
+# 2239434247834913b8b23dab3f7f896d
+msgid "On Zones, click View More, then click the zone to which you want to work with.."
+msgstr ""
+
+#: ../../managing_networks.rst:1363
+# 52b4f5c3dc6c4c96a91c21e53b5f6ba7
+msgid "Click Physical Network."
+msgstr ""
+
+#: ../../managing_networks.rst:1371
+# d545de9168774122b8d39fe9b88db0f9
+msgid "Click Networks."
+msgstr ""
+
+#: ../../managing_networks.rst:1375
+# 201b95be96f741419b7a53c915e3da38
+msgid "Select the networks you want to work with."
+msgstr ""
+
+#: ../../managing_networks.rst:1379
+# b1dafa11c6dd48aaba7215933fc61640
+msgid "Click View IP Ranges."
+msgstr ""
+
+#: ../../managing_networks.rst:1383
+# 962df84772504a178c0760d6862328be
+msgid "Click Add IP Range."
+msgstr ""
+
+#: ../../managing_networks.rst:1385
+# a8c9f66de4e84e56882ecb276ca04e41
+msgid "The Add IP Range dialog is displayed, as follows:"
+msgstr ""
+
+#: ../../managing_networks.rst:1387
+# ae7f538d814144019a90e1b0ac6f4a3d
+msgid "|add-ip-range.png: adding an IP range to a network.|"
+msgstr ""
+
+#: ../../managing_networks.rst:1393
+#: ../../managing_networks.rst:5063
+# 0884d274eba74f889ae1c3abffff98dd
+# 03a1c57fd13d4fdb9f6c63ec4afcc907
+msgid "All the fields are mandatory."
+msgstr ""
+
+#: ../../managing_networks.rst:1397
+#: ../../managing_networks.rst:5081
+# 8da5ac3902824555b54847009a765ed7
+# fe107d12592248a982087f39da19a41a
+msgid "**Gateway**: The gateway for the tier you create. Ensure that the gateway is within the Super CIDR range that you specified while creating the VPC, and is not overlapped with the CIDR of any existing tier within the VPC."
+msgstr ""
+
+#: ../../managing_networks.rst:1404
+#: ../../managing_networks.rst:5098
+# d23bd452fc4d46579356f5ede9152d95
+# af646832ee3f44ebaa1213c5db09bb4a
+msgid "**Netmask**: The netmask for the tier you create."
+msgstr ""
+
+#: ../../managing_networks.rst:1406
+#: ../../managing_networks.rst:5100
+# 86f10e90777a4711964d8a8df3a0e45c
+# 04b52f8b675747ee8a9c73e86c123710
+msgid "For example, if the VPC CIDR is 10.0.0.0/16 and the network tier CIDR is 10.0.1.0/24, the gateway of the tier is 10.0.1.1, and the netmask of the tier is 255.255.255.0."
+msgstr ""
+
+#: ../../managing_networks.rst:1412
+# 3bdc377e66c842a4a3f09450a0832e67
+msgid "**Start IP/ End IP**: A range of IP addresses that are accessible from the Internet and will be allocated to guest VMs. Enter the first and last IP addresses that define a range that CloudStack can assign to guest VMs ."
+msgstr ""
+
+#: ../../managing_networks.rst:1422
+# b6a0de7ae6b643a3b425583d43f6163e
+msgid "Isolation in Advanced Zone Using Private VLAN"
+msgstr ""
+
+#: ../../managing_networks.rst:1424
+# 4f75858c33ec4279a864c4b208e29b2b
+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 ""
+
+#: ../../managing_networks.rst:1435
+# 2b100ae9fa4e4eaea15ed0c9c965697f
+msgid "Isolate VMs in a shared networks by using Private VLANs."
+msgstr ""
+
+#: ../../managing_networks.rst:1439
+# 72cb21f4bdaa4f6c88f7f1253969f497
+msgid "Supported on KVM, XenServer, and VMware hypervisors"
+msgstr ""
+
+#: ../../managing_networks.rst:1443
+# 64e4f6f904e145cc94c88300b2f6f1ec
+msgid "PVLAN-enabled shared network can be a part of multiple networks of a guest VM."
+msgstr ""
+
+#: ../../managing_networks.rst:1447
+# 39b527fd98914ef4ae1f7cd5d5a083c3
+msgid "About Private VLAN"
+msgstr ""
+
+#: ../../managing_networks.rst:1449
+# ffcf29c6500a4e3a897fefd357efafa1
+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 ""
+
+#: ../../managing_networks.rst:1462
+# dadf77ad95da46d29d655fa1b5c88836
+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 ""
+
+#: ../../managing_networks.rst:1471
+# 338ab35c29694e549d0f63e57cf3ecfc
+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 ""
+
+#: ../../managing_networks.rst:1481
+# 1eb75b61178b4a8da29196b19e0755f1
+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 ""
+
+#: ../../managing_networks.rst:1489
+# 3c344baffb3649a3a99b4762947818ae
+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 ""
+
+#: ../../managing_networks.rst:1499
+# a10ac6622d024e57899b845f7e847140
+msgid "For further reading:"
+msgstr ""
+
+#: ../../managing_networks.rst:1503
+# 5efde3c2b6894bd387b0f388d8bdeae3
+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 ""
+
+#: ../../managing_networks.rst:1508
+# 02596ab9a4bd47daaed6a4272e786d9a
+msgid "`Cisco Systems' Private VLANs: Scalable Security in a Multi-Client Environment <http://tools.ietf.org/html/rfc5517>`__"
+msgstr ""
+
+#: ../../managing_networks.rst:1513
+# 886e828c09384218b5bd4f8cd224d968
+msgid "`Private VLAN (PVLAN) on vNetwork Distributed Switch - Concept Overview (1010691) <http://kb.vmware.com>`__"
+msgstr ""
+
+#: ../../managing_networks.rst:1521
+# 6cb7c445963a491caff15981fe0b4ce4
+msgid "Use a PVLAN supported switch."
+msgstr ""
+
+#: ../../managing_networks.rst:1523
+# f7f97cd16eb24ff588d513c2d34ff289
+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 ""
+
+#: ../../managing_networks.rst:1529
+# 09e5467647fd4eb6af74a6c1cb65b159
+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 ""
+
+#: ../../managing_networks.rst:1537
+# 3eb08525c8114e1fade9c52b44c14c59
+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 ""
+
+#: ../../managing_networks.rst:1544
+# e9c74dd366ef45f1be1d0793986d7f73
+msgid "Configure private VLAN on your physical switches out-of-band."
+msgstr ""
+
+#: ../../managing_networks.rst:1548
+# 2ecc130e165749aba238d52a9a7f2486
+msgid "Before you use PVLAN on XenServer and KVM, enable Open vSwitch (OVS)."
+msgstr ""
+
+#: ../../managing_networks.rst:1550
+# 030698129200435e9f708d7cb120c98b
+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 ""
+
+#: ../../managing_networks.rst:1553
+# f6a73d4d4c73444dbf0a403921b5aa74
+msgid "Creating a PVLAN-Enabled Guest Network"
+msgstr ""
+
+#: ../../managing_networks.rst:1613
+# 740911b6b7d14c93bb243f861cbde303
+msgid "**Secondary Isolated VLAN ID**: The unique ID of the Secondary Isolated VLAN."
+msgstr ""
+
+#: ../../managing_networks.rst:1616
+# 33d01a6c72b3484991970c439ebe1b80
+msgid "For the description on Secondary Isolated VLAN, see `Section 15.14.1, “About Private VLAN” <#about-pvlan>`__."
+msgstr ""
+
+#: ../../managing_networks.rst:1679
+# 2c24eb1bc100495989166e76788319c0
+msgid "Security Groups"
+msgstr ""
+
+#: ../../managing_networks.rst:1682
+# d331348078ea4de8a8dc8471c9cc3cce
+msgid "About Security Groups"
+msgstr ""
+
+#: ../../managing_networks.rst:1684
+# f34bf064d0114b288f2f55f17a25f84a
+msgid "Security groups provide a way to isolate traffic to VMs. 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. Security groups are particularly useful in zones that use basic networking, because there is a single guest network for all guest VMs. In advanced zones, security groups are supported only on the KVM hypervisor."
+msgstr ""
+
+#: ../../managing_networks.rst:1693
+# 5e82a09d657a4767acec9f22d782de51
+msgid "In a zone that uses advanced networking, you can instead define multiple guest networks to isolate traffic to VMs."
+msgstr ""
+
+#: ../../managing_networks.rst:1695
+# 79f27644dfcf4cf788bba960a7f3b5bf
+msgid "Each CloudStack account comes with a default security group that denies all inbound traffic and allows all outbound traffic. The default security group can be modified so that all new VMs inherit some other desired set of rules."
+msgstr ""
+
+#: ../../managing_networks.rst:1700
+# baa28941d5194fae811bbd88c61df125
+msgid "Any CloudStack user can set up any number of additional security groups. When a new VM is launched, it is assigned to the default security group unless another user-defined security group is specified. A VM can be a member of any number of security groups. Once a VM is assigned to a security group, it remains in that group for its entire lifetime; you can not move a running VM from one security group to another."
+msgstr ""
+
+#: ../../managing_networks.rst:1707
+# de98d0c1571a4cc18032b6472947663b
+msgid "You can modify a security group by deleting or adding any number of ingress and egress rules. When you do, the new rules apply to all VMs in the group, whether running or stopped."
+msgstr ""
+
+#: ../../managing_networks.rst:1711
+# 6e7dbedd8ee140e1ad567e65c7ff552d
+msgid "If no ingress rules are specified, then no traffic will be allowed in, except for responses to any traffic that has been allowed out through an egress rule."
+msgstr ""
+
+#: ../../managing_networks.rst:1716
+# 50b80901d7c24d66a23e838b0f4293d3
+msgid "Adding a Security Group"
+msgstr ""
+
+#: ../../managing_networks.rst:1718
+# f870c727a4ba4b5fafdca88cc7a4b660
+msgid "A user or administrator can define a new security group."
+msgstr ""
+
+#: ../../managing_networks.rst:1726
+#: ../../managing_networks.rst:1803
+# 2bd568db435b4894a6594bdabb71b71f
+# ec651383a1084a9bb247059b0cb38cc8
+msgid "In the left navigation, choose Network"
+msgstr ""
+
+#: ../../managing_networks.rst:1730
+# 20641ac9b26d48a8a2af8025a38b3550
+msgid "In Select view, choose Security Groups."
+msgstr ""
+
+#: ../../managing_networks.rst:1734
+# 3b8b48dea99749bf821c45bf85f5edce
+msgid "Click Add Security Group."
+msgstr ""
+
+#: ../../managing_networks.rst:1738
+# da5c74165969469d9c2395eaaa3f94e6
+msgid "Provide a name and description."
+msgstr ""
+
+#: ../../managing_networks.rst:1744
+# cebb13c23de64a278615d79e7d92b3bc
+msgid "The new security group appears in the Security Groups Details tab."
+msgstr ""
+
+#: ../../managing_networks.rst:1748
+# b0f1a7c4f9d74d0cbf905c6ce03546b8
+msgid "To make the security group useful, continue to Adding Ingress and Egress Rules to a Security Group."
+msgstr ""
+
+#: ../../managing_networks.rst:1752
+# 0c59765ee0c64629952434a87beb9d81
+msgid "Security Groups in Advanced Zones (KVM Only)"
+msgstr ""
+
+#: ../../managing_networks.rst:1754
+# 33c22ff2d84d4c149fb2a3ba75f8689f
+msgid "CloudStack provides the ability to use security groups to provide isolation between guests on a single shared, zone-wide network in an advanced zone where KVM is the hypervisor. Using security groups in advanced zones rather than multiple VLANs allows a greater range of options for setting up guest isolation in a cloud."
+msgstr ""
+
+#: ../../managing_networks.rst:1760
+# 0d98099524ba4909b604a7399ffc1bd8
+msgid "Limitations: The following are not supported for this feature:"
+msgstr ""
+
+#: ../../managing_networks.rst:1764
+# cfee500d52ad40699096b1a8e4e389c1
+msgid "Two IP ranges with the same VLAN and different gateway or netmask in security group-enabled shared network."
+msgstr ""
+
+#: ../../managing_networks.rst:1769
+# 6246185f1f154f93875963e698243930
+msgid "Two IP ranges with the same VLAN and different gateway or netmask in account-specific shared networks."
+msgstr ""
+
+#: ../../managing_networks.rst:1774
+# 1d7c154fd0c34eaf9711d6ec05f84dee
+msgid "Multiple VLAN ranges in security group-enabled shared network."
+msgstr ""
+
+#: ../../managing_networks.rst:1778
+# d31b3ceda7e84ff09119957ddcbbdf2b
+msgid "Multiple VLAN ranges in account-specific shared networks."
+msgstr ""
+
+#: ../../managing_networks.rst:1780
+# 6eeb1f2182894bc383d39cb1f701fb27
+msgid "Security groups must be enabled in the zone in order for this feature to be used."
+msgstr ""
+
+#: ../../managing_networks.rst:1784
+# d9c879f6880c426dbe5cc14699e86c87
+msgid "Enabling Security Groups"
+msgstr ""
+
+#: ../../managing_networks.rst:1786
+# 6038307bd32f4032b2cf2283627e5084
+msgid "In order for security groups to function in a zone, the security groups feature must first be enabled for the zone. The administrator can do this when creating a new zone, by selecting a network offering that includes security groups. The procedure is described in Basic Zone Configuration in the Advanced Installation Guide. The administrator can not enable security groups for an existing zone, only when creating a new zone."
+msgstr ""
+
+#: ../../managing_networks.rst:1795
+# 9239428930ac475c8787a1fa5c7b5852
+msgid "Adding Ingress and Egress Rules to a Security Group"
+msgstr ""
+
+#: ../../managing_networks.rst:1807
+# 1dabe90dfbf742b1ad863dda6a7370cf
+msgid "In Select view, choose Security Groups, then click the security group you want ."
+msgstr ""
+
+#: ../../managing_networks.rst:1812
+# 14c6cdb0f76f4e5bafb8a8247c89a3f5
+msgid "To add an ingress rule, click the Ingress Rules tab and fill out the following fields to specify what network traffic is allowed into VM instances in this security group. If no ingress rules are specified, then no traffic will be allowed in, except for responses to any traffic that has been allowed out through an egress rule."
+msgstr ""
+
+#: ../../managing_networks.rst:1820
+# dbc6db6a8f164564b90b36fb8600f6c4
+msgid "**Add by CIDR/Account**. Indicate whether the source of the traffic will be defined by IP address (CIDR) or an existing security group in a CloudStack account (Account). Choose Account if you want to allow incoming traffic from all VMs in another security group"
+msgstr ""
+
+#: ../../managing_networks.rst:1828
+# c7404bcf0635456b924a7d4461860444
+msgid "**Protocol**. The networking protocol that sources will use to send traffic to the security group. TCP and UDP are typically used for data exchange and end-user communications. ICMP is typically used to send error messages or network monitoring data."
+msgstr ""
+
+#: ../../managing_networks.rst:1835
+# 553fb9fc05c647d38e4c15f2ccbb5123
+msgid "**Start Port, End Port**. (TCP, UDP only) A range of listening ports that are the destination for the incoming traffic. If you are opening a single port, use the same number in both fields."
+msgstr ""
+
+#: ../../managing_networks.rst:1841
+# f1ac0dd3df2a46ad8b321cc49981a565
+msgid "**ICMP Type, ICMP Code**. (ICMP only) The type of message and error code that will be accepted."
+msgstr ""
+
+#: ../../managing_networks.rst:1846
+# 4b14903d5adb4c9a8301a393218c0fe9
+msgid "**CIDR**. (Add by CIDR only) To accept only traffic from 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 incoming traffic. For example, 192.168.0.0/22. To allow all CIDRs, set to 0.0.0.0/0."
+msgstr ""
+
+#: ../../managing_networks.rst:1854
+# c1561e01a67747a699e6e8f0b8d265a1
+msgid "**Account, Security Group**. (Add by Account only) To accept only traffic from an
<TRUNCATED>
[5/7] setup i18n with transifex and sphinx-intl
Posted by se...@apache.org.
http://git-wip-us.apache.org/repos/asf/cloudstack-docs-install/blob/bd81bcc4/source/locale/pot/hypervisor_installation.pot
----------------------------------------------------------------------
diff --git a/source/locale/pot/hypervisor_installation.pot b/source/locale/pot/hypervisor_installation.pot
new file mode 100644
index 0000000..180fcff
--- /dev/null
+++ b/source/locale/pot/hypervisor_installation.pot
@@ -0,0 +1,4221 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2014, Apache Software Foundation
+# This file is distributed under the same license as the Apache CloudStack Installation Documentation package.
+# FIRST AUTHOR <EM...@ADDRESS>, YEAR.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: Apache CloudStack Installation Documentation 4\n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2014-03-31 14:02-0400\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"
+
+#: ../../hypervisor_installation.rst:17
+# a5b708b1c7f34ebeb40e555178227b10
+msgid "Hypervisor Installation"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:20
+# c97e1fa112814a849f7cd08e8f9d3c1e
+msgid "KVM Hypervisor Host Installation"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:23
+# 106ceeb500c947a88931ac644e73431d
+msgid "System Requirements for KVM Hypervisor Hosts"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:25
+# afa4fe6e1df94ebeb7668c1cabb0ff0c
+msgid "KVM is included with a variety of Linux-based operating systems. Although you are not required to run these distributions, the following are recommended:"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:31
+#: ../../hypervisor_installation.rst:3327
+# 34c3bdfde3da4f2d9c34601a86f0afcf
+# a161e18b507540c096810a8ec29ef317
+msgid "CentOS / RHEL: 6.3"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:35
+#: ../../hypervisor_installation.rst:3331
+# 4ffd025eb47e4537b6eb5007d2b80629
+# 57d072c73c204d6e81f858aa46f60667
+msgid "Ubuntu: 12.04(.1)"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:37
+# 7decad4017784f2f96f7030e58f6f239
+msgid "The main requirement for KVM hypervisors is the libvirt and Qemu version. No matter what Linux distribution you are using, make sure the following requirements are met:"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:43
+# aee585bafb434d2dbe9d2579ab1dcad5
+msgid "libvirt: 0.9.4 or higher"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:47
+#: ../../hypervisor_installation.rst:3343
+# 008a79408bb34d52bf92873b8905dad3
+# 6364b35d5cdd483f87928821946c3f34
+msgid "Qemu/KVM: 1.0 or higher"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:49
+#: ../../hypervisor_installation.rst:3345
+# 4bc408d879ad447baa475bfd0808aa65
+# 3dbbe376cdd24657968196a32f21fda6
+msgid "The default bridge in CloudStack is the Linux native bridge implementation (bridge module). CloudStack includes an option to work with OpenVswitch, the requirements are listed below"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:55
+# 34be33c099374c35aa8784190733b87c
+msgid "libvirt: 0.9.11 or higher"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:59
+#: ../../hypervisor_installation.rst:3355
+# 7d3d628565264bc69adb04e77462b5b0
+# 4b4d3c51f3b746ed96a5bd61749758f4
+msgid "openvswitch: 1.7.1 or higher"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:61
+#: ../../hypervisor_installation.rst:3357
+# 6b26016e861b4aaaba05f3bd8c98f682
+# 1e2e540227304e14b7a8406969608a5e
+msgid "In addition, the following hardware requirements apply:"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:65
+#: ../../hypervisor_installation.rst:3361
+# 322d406c43f64403bf5e8acfad80318d
+# 49490f42aa554579a0169795b8fec7cf
+msgid "Within a single cluster, the hosts must be of the same distribution version."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:70
+#: ../../hypervisor_installation.rst:3366
+# 86c9ea55ffec4f399b8e7918b7bb43d0
+# e392215de57d4843958e657b3d6d64c7
+msgid "All hosts within a cluster must be homogenous. The CPUs must be of the same type, count, and feature flags."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:75
+#: ../../hypervisor_installation.rst:1027
+#: ../../hypervisor_installation.rst:3371
+# e6544c9e2bed4d36a8b7bf5e2b040667
+# 405d986c35fd4e35bba0d7ea5664327b
+# b176112062f840bf8e4293cb2b6dd440
+msgid "Must support HVM (Intel-VT or AMD-V enabled)"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:79
+#: ../../hypervisor_installation.rst:1051
+#: ../../hypervisor_installation.rst:2263
+#: ../../hypervisor_installation.rst:3375
+# fe8c3dec4f5e48af82d6a1cf4d35c0fa
+# 222e2e6b7d72437fa9d1e291b1abae33
+# b6a567096cf14ce7a86b7cab8cd8a120
+# d2f00762290a412aada0abbdddc35042
+msgid "64-bit x86 CPU (more cores results in better performance)"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:83
+#: ../../hypervisor_installation.rst:1059
+#: ../../hypervisor_installation.rst:2271
+#: ../../hypervisor_installation.rst:3379
+# 8a4b47d3dc3a44c584fbd97dcf25a5a0
+# 14006a14fa284ce6ba19f360f889a0bc
+# 6d7b9af582894902a3e1095cfa7f02fe
+# 130dbc2bf67d4a5687f09f35f760a482
+msgid "4 GB of memory"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:87
+#: ../../hypervisor_installation.rst:1067
+#: ../../hypervisor_installation.rst:2279
+#: ../../hypervisor_installation.rst:3383
+# e8bd701c4ef947078dfed764bd5fc6d9
+# 656d673c698d4b118d21cc9362a8e5dd
+# 947d8b3ed1974720a911fdb6b44d4d36
+# a4a079db675c46938452f27bc17e3e68
+msgid "At least 1 NIC"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:91
+#: ../../hypervisor_installation.rst:1075
+#: ../../hypervisor_installation.rst:3387
+# 3444db1dcb1f47258e2772864b74a072
+# 0d176e6f680c42f88456e42ff3bbc75c
+# eaf19bdaaac2446a9eba73346cfb272c
+msgid "When you deploy CloudStack, the hypervisor host must not have any VMs already running"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:95
+# b090156a97514e25ae92874eabc12ebe
+msgid "KVM Installation Overview"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:97
+# 3c994a4c8bb44c3db12d9d1a91d88511
+msgid "If you want to use the Linux Kernel Virtual Machine (KVM) hypervisor to run guest virtual machines, install KVM on the host(s) in your cloud. The material in this section doesn't duplicate KVM installation docs. It provides the CloudStack-specific steps that are needed to prepare a KVM host to work with CloudStack."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:105
+#: ../../hypervisor_installation.rst:3400
+# 0ae1e0787a0a4b35bb60e6ce2270b93c
+# fbbc0d73551e4738b0780bf7ae39b794
+msgid "Before continuing, make sure that you have applied the latest updates to your host."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:109
+#: ../../hypervisor_installation.rst:3402
+# 3f404325440b43e8929f971c948bddd2
+# cdf930cc6f4f48cfbfa886bcea0c6c5c
+msgid "It is NOT recommended to run services on this host not controlled by CloudStack."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:111
+# b4d910e8d72742e2992a140e0bbb07f9
+msgid "The procedure for installing a KVM Hypervisor Host is:"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:115
+#: ../../hypervisor_installation.rst:130
+#: ../../hypervisor_installation.rst:3408
+#: ../../hypervisor_installation.rst:3423
+# f72c15c1878f4826b773a10ca9d09132
+# a5027d0749d5434b8990a4ce07b63190
+# cd85e26dfec64b0e85060beb3e51e135
+# 3f58fd5515bf4d7c95f3972fecc77a0f
+msgid "Prepare the Operating System"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:119
+#: ../../hypervisor_installation.rst:3412
+# 2a8a33c0f29c40b2823be72c0a3ebbb4
+# c6bed6d3e6b248daa4040d12455fe55a
+msgid "Install and configure libvirt"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:123
+#: ../../hypervisor_installation.rst:3416
+# 1642991c8fbd4e90ac67a46c59e515a5
+# a94fc5d5847b4a85b0f6d0ee714b7b1f
+msgid "Configure Security Policies (AppArmor and SELinux)"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:127
+#: ../../hypervisor_installation.rst:185
+#: ../../hypervisor_installation.rst:3420
+#: ../../hypervisor_installation.rst:3477
+# 1ed5a01ec0704f2eb18b408abd6cae9c
+# 52a64dac3f794d7d9402c6f757812a16
+# 0bf1c9bf0fa048cdb0bffdde08d78760
+# 0902ea5204d74d8faa9db44b32e93779
+msgid "Install and configure the Agent"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:132
+#: ../../hypervisor_installation.rst:3425
+# 54165d82f02949c887291da9ef9385f7
+# 887757221dec4140950e28424103418d
+msgid "The OS of the Host must be prepared to host the CloudStack Agent and run KVM instances."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:137
+#: ../../hypervisor_installation.rst:3430
+# 3b1313122c04424eb3c0f4dea9099319
+# 209d2e9fe5a54af0a434c6fe42d67c94
+msgid "Log in to your OS as root."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:141
+#: ../../hypervisor_installation.rst:3434
+# faa86bd264934b1b8bab5914670677e8
+# ec55ce15def44bbea72ff6f68842becc
+msgid "Check for a fully qualified hostname."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:147
+#: ../../hypervisor_installation.rst:3440
+# 6e562892fc814c038043db4120089438
+# f775086cc87b40dab6aac8299ca88571
+msgid "This should return a fully qualified hostname such as \"kvm1.lab.example.org\". If it does not, edit /etc/hosts so that it does."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:153
+#: ../../hypervisor_installation.rst:3446
+# e009ff0ecafd4666a742d5af03d2309e
+# f85f5a8126094c72a1740ac354fc6e2f
+msgid "Make sure that the machine can reach the Internet."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:161
+#: ../../hypervisor_installation.rst:3454
+# 56ca23a905364937bac5cf61701e8a09
+# de0710f8ee154254b3d424dc19901a33
+msgid "Turn on NTP for time synchronization."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:165
+#: ../../hypervisor_installation.rst:3457
+# 0d18ab8873cc4b938d65ea7d9503d2f3
+# 2281cb7bd1ab44d0a18d9a382ae614d7
+msgid "NTP is required to synchronize the clocks of the servers in your cloud. Unsynchronized clocks can cause unexpected problems."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:170
+#: ../../hypervisor_installation.rst:3462
+# 65aa5ea952b94cb3bcd5151c59496e4d
+# fb7ee24bb05540f9859ba3b87f03487c
+msgid "Install NTP"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:182
+#: ../../hypervisor_installation.rst:3474
+# e93ea97e77314f19b564fc3d5e981897
+# c859b30acde9440ca4835511741c38ac
+msgid "Repeat all of these steps on every hypervisor host."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:187
+# ea49f1e757d443beb13b7434fc7a6337
+msgid "To manage KVM instances on the host CloudStack uses a Agent. This Agent communicates with the Management server and controls all the instances on the host."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:191
+#: ../../hypervisor_installation.rst:3483
+# 34eb5632982c49a7ad56d679b8897bad
+# 84ca527264e445eb9b6965300ff5a67a
+msgid "First we start by installing the agent:"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:193
+#: ../../hypervisor_installation.rst:361
+#: ../../hypervisor_installation.rst:402
+#: ../../hypervisor_installation.rst:3485
+#: ../../hypervisor_installation.rst:3608
+#: ../../hypervisor_installation.rst:3649
+# d894051a1aa4420482cd5ecf26baf9b9
+# e209192de68d4bdb9b3cb14f77c59b1a
+# 0e50e758e1bd45628f4eee81cae74b1d
+# eb677ec246e749239198c0ef7edd5ff4
+# e2c94bf547f64410916a38d7e7fdd670
+# e86cca2d481a47539eef5083baa6edda
+msgid "In RHEL or CentOS:"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:199
+#: ../../hypervisor_installation.rst:367
+#: ../../hypervisor_installation.rst:3491
+#: ../../hypervisor_installation.rst:3614
+# 3b6758b2ccb445b5be94a8dfc7ebd0a2
+# ade0da3eeb2941c49b1186cd22d03202
+# 0f363f2af00f4b159318dab564862baa
+# a14254a637a742dfa6d89b25b9b24656
+msgid "In Ubuntu:"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:205
+#: ../../hypervisor_installation.rst:943
+#: ../../hypervisor_installation.rst:3525
+#: ../../hypervisor_installation.rst:4024
+# d096d4acc81e4e60834b9a24af414019
+# 8bd1adc0e2a34211956f1b708f3c9724
+# 1e3a5fd3b85f4bce9244ebdcc0b999ed
+# 78185f32c03c498db18b23abd0426910
+msgid "The host is now ready to be added to a cluster. This is covered in a later section, see :ref:`adding-a-host`. It is recommended that you continue to read the documentation before adding the host!"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:211
+# af1b91fcf7484085b389fb8d502edcd6
+msgid "Configure CPU model for KVM guest (Optional)"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:213
+# 7fdc1820edee46fca04097cd36443ade
+msgid "In additional,the CloudStack Agent allows host administrator to control the guest CPU model which is exposed to KVM instances. By default, the CPU model of KVM instance is likely QEMU Virtual CPU version x.x.x with least CPU features exposed. There are a couple of reasons to specify the CPU model:"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:221
+# 55671888c52e4644b97eb76e5b37321a
+msgid "To maximise performance of instances by exposing new host CPU features to the KVM instances;"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:226
+# 0076cb899b89481ba3c5032e2156b23a
+msgid "To ensure a consistent default CPU across all machines,removing reliance of variable QEMU defaults;"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:229
+# 06f0cd9e4f7148f2bf5661eb3a4bbb30
+msgid "For the most part it will be sufficient for the host administrator to specify the guest CPU config in the per-host configuration file (/etc/cloudstack/agent/agent.properties). This will be achieved by introducing two new configuration parameters:"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:239
+# 1a1c88bead1d4b90b16007da2a8049af
+msgid "There are three choices to fulfill the cpu model changes:"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:243
+# 171cebf0991b4c7d82b4254c0b0a6fe7
+msgid "**custom:** you can explicitly specify one of the supported named model in /usr/share/libvirt/cpu\\_map.xml"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:248
+# ef3286604260487387d6ef81752d3ff4
+msgid "**host-model:** libvirt will identify the CPU model in /usr/share/libvirt/cpu\\_map.xml which most closely matches the host, and then request additional CPU flags to complete the match. This should give close to maximum functionality/performance, which maintaining good reliability/compatibility if the guest is migrated to another host with slightly different host CPUs."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:257
+# 80a634dd2c22483fb09655f8c07ff193
+msgid "**host-passthrough:** libvirt will tell KVM to passthrough the host CPU with no modifications. The difference to host-model, instead of just matching feature flags, every last detail of the host CPU is matched. This gives absolutely best performance, and can be important to some apps which check low level CPU details, but it comes at a cost with respect to migration: the guest can only be migrated to an exactly matching host CPU."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:265
+# f58590a9696548528006493b8c7ae197
+msgid "Here are some examples:"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:269
+# 42ef165ce6ad4a9e9fa71eb044611a1b
+msgid "custom"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:278
+# 91ceb895db0b4234a51b32614603068e
+msgid "host-model"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:286
+# 9eed04f7453b40529c43301d1de02fb8
+msgid "host-passthrough"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:292
+# dfb22be926364168a84d5cb0b7e44b35
+msgid "host-passthrough may lead to migration failure,if you have this problem,you should use host-model or custom"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:295
+#: ../../hypervisor_installation.rst:3531
+# a5e533a4e79649c2ac3ce750357ee34a
+# 4d3de60d913b41398d75fad799393017
+msgid "Install and Configure libvirt"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:297
+#: ../../hypervisor_installation.rst:3533
+# bf3b3baffb30458eae7af5d56a51a573
+# fd165c09e19c4204af9a194d9e0209fb
+msgid "CloudStack uses libvirt for managing virtual machines. Therefore it is vital that libvirt is configured correctly. Libvirt is a dependency of cloudstack-agent and should already be installed."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:303
+#: ../../hypervisor_installation.rst:3539
+# ff42e0ea9cf64b509d310c0071086352
+# 5b89b062abbe4cc89b7fd10ece8eb9e8
+msgid "In order to have live migration working libvirt has to listen for unsecured TCP connections. We also need to turn off libvirts attempt to use Multicast DNS advertising. Both of these settings are in ``/etc/libvirt/libvirtd.conf``"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:308
+#: ../../hypervisor_installation.rst:3544
+# 9d2c6d97644043c98a8afdfca63ce7ba
+# 62f76e0671a940e38a4ad3785ad3829e
+msgid "Set the following parameters:"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:332
+#: ../../hypervisor_installation.rst:3568
+# 7bf432c121e6497e815bce7ac5f768c2
+# 5c250e445c544d819ef81c56946c9817
+msgid "Turning on \"listen\\_tcp\" in libvirtd.conf is not enough, we have to change the parameters as well:"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:335
+#: ../../hypervisor_installation.rst:3571
+# dff877a089444785a919c9a4ddc1505b
+# 09f64fb99e4f4746998fccfb45d8ffbe
+msgid "On RHEL or CentOS modify ``/etc/sysconfig/libvirtd``:"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:337
+#: ../../hypervisor_installation.rst:3573
+# dc8b92c2767f4d3aa010cafa32e0ffc0
+# 5137041fbceb450dafdafdd8050d781b
+msgid "Uncomment the following line:"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:343
+#: ../../hypervisor_installation.rst:3579
+# f8fa69e0aaf0441ebbd5376315dde649
+# 2c026065c68143c7abdc5ca2fc2436ea
+msgid "On Ubuntu: modify ``/etc/default/libvirt-bin``"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:345
+#: ../../hypervisor_installation.rst:3581
+# b1e0a030287c4eb99b535ef0a0e008cd
+# e7c84f512f6b40c5ae74177fcbef4e7b
+msgid "Add \"-l\" to the following line"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:351
+#: ../../hypervisor_installation.rst:3587
+# fb23df2bb85243918f17fce3511a292f
+# 3f9045ba6c8042cd95dbf7cfaf068566
+msgid "so it looks like:"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:359
+#: ../../hypervisor_installation.rst:3606
+# e9f3700ad8c545ec9162775958e52903
+# 12a8cf99f91a4bfebfef63061401b984
+msgid "Restart libvirt"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:374
+#: ../../hypervisor_installation.rst:3621
+# 8a64baac6d7643dda067b886a5c80ae3
+# 396a781a4a1d4985aa57fc33ab909171
+msgid "Configure the Security Policies"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:376
+#: ../../hypervisor_installation.rst:3623
+# 071b22fa7fe84b5184dcaee305d367f9
+# ba196eddcd1a4db0b3bc5debca46897c
+msgid "CloudStack does various things which can be blocked by security mechanisms like AppArmor and SELinux. These have to be disabled to ensure the Agent has all the required permissions."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:382
+#: ../../hypervisor_installation.rst:3629
+# 66c0547791744ea9a1bf3f4b86157e56
+# a13c1564e14a40a98d164cdc3bfad868
+msgid "Configure SELinux (RHEL and CentOS)"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:386
+#: ../../hypervisor_installation.rst:3633
+# ad5bbcda3fb94378926b1b5e5c49fef5
+# 3bc6b9a75a864efca77472f3a7083402
+msgid "Check to see whether SELinux is installed on your machine. If not, you can skip this section."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:389
+#: ../../hypervisor_installation.rst:3636
+# 186d81a15e7149da89ee20ce59cc48dc
+# 51df5058cd4f43938789667b0444df12
+msgid "In RHEL or CentOS, SELinux is installed and enabled by default. You can verify this with:"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:398
+#: ../../hypervisor_installation.rst:3645
+# 5c9517056a764377bd38722748343a49
+# 47aa2dbec53247e09633898939b840d7
+msgid "Set the SELINUX variable in ``/etc/selinux/config`` to \"permissive\". This ensures that the permissive setting will be maintained after a system reboot."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:408
+#: ../../hypervisor_installation.rst:3655
+# 93857dbce0f54cb68f9fda82a8cd692c
+# 34854b97c968469aa89f9b69611024e4
+msgid "Change the following line"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:414
+#: ../../hypervisor_installation.rst:3661
+# 0e1313c89e3b415ebee6bbc8671f120a
+# fb6153f02ea1423088ece2501fda504f
+msgid "to this"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:422
+#: ../../hypervisor_installation.rst:3669
+# 29a646ccf1ad4545bac2923aabe1b97c
+# 80ca6532afc24061b27c23b6118bdf65
+msgid "Then set SELinux to permissive starting immediately, without requiring a system reboot."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:431
+#: ../../hypervisor_installation.rst:3678
+# 5ce95d10c98449d7b6f2c0ac20da948c
+# c3cf4cecfad547a8a307e334e4503f59
+msgid "Configure Apparmor (Ubuntu)"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:435
+#: ../../hypervisor_installation.rst:3682
+# 87b92b4c575e4c95813f1e9af3b04d77
+# 07b7d10f1b3e49d8952e5b635b7eca2a
+msgid "Check to see whether AppArmor is installed on your machine. If not, you can skip this section."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:438
+#: ../../hypervisor_installation.rst:3685
+# 50e7a0a081684c489805ccda2c5717d6
+# 491c0892c7ef48b18767fafac079a62b
+msgid "In Ubuntu AppArmor is installed and enabled by default. You can verify this with:"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:447
+#: ../../hypervisor_installation.rst:3694
+# 8e560cd81d0544eb8f9bb401145dea8e
+# 26d2ddef7e5f4c29a57ab9455120b3f3
+msgid "Disable the AppArmor profiles for libvirt"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:466
+#: ../../hypervisor_installation.rst:3713
+# 930e8f602c664befbf6c46bcea1cbe7e
+# 5a5ec5e627f84217a2de1c1a9692d83d
+msgid "Configure the network bridges"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:468
+#: ../../hypervisor_installation.rst:680
+#: ../../hypervisor_installation.rst:3715
+# bccb9ebfa523410e95ffbeec12d8b4df
+# c27b62ef62564bce8bbcdebbbc78a2e6
+# eaf1d1b6a92b4d26923b5a26f2d8f6e3
+msgid "This is a very important section, please make sure you read this thoroughly."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:470
+#: ../../hypervisor_installation.rst:3718
+# 37ea1b1181cf4de494d126cdc40a801d
+# 0c2793bb0202408da6ef10e2b99b6eaa
+msgid "This section details how to configure bridges using the native implementation in Linux. Please refer to the next section if you intend to use OpenVswitch"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:472
+#: ../../hypervisor_installation.rst:682
+#: ../../hypervisor_installation.rst:3720
+# 2bf55b978c5a475ebcd65da90eb6386a
+# 994c7b0b85ac4fd4957bf9212cb5afbd
+# 40d0ecab11134b1f984bf6d89271cbd4
+msgid "In order to forward traffic to your instances you will need at least two bridges: *public* and *private*."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:475
+#: ../../hypervisor_installation.rst:685
+#: ../../hypervisor_installation.rst:3723
+# 68eec8c1d0fd4c34a086b108e1ba4a0b
+# 9785a42437c44a48932befa909c24f05
+# b2947b2e839f4cf9a79ddafa66b1b8e0
+msgid "By default these bridges are called *cloudbr0* and *cloudbr1*, but you do have to make sure they are available on each hypervisor."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:478
+#: ../../hypervisor_installation.rst:688
+#: ../../hypervisor_installation.rst:3726
+# fd73cf9a6c174db1a1d0a7a7b0febf8f
+# c6b6935f5a0241319a435306ff08f613
+# d7f8015ac99a49b7a8f2bdd03074f25e
+msgid "The most important factor is that you keep the configuration consistent on all your hypervisors."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:482
+#: ../../hypervisor_installation.rst:705
+#: ../../hypervisor_installation.rst:3730
+# aecc917b1cfc4ae0829bf38e71b146a1
+# dcd1dd91023f487bac62a498068bc7d3
+# 61678fddd1354bc299cc7a3f18060a1b
+msgid "Network example"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:484
+#: ../../hypervisor_installation.rst:707
+#: ../../hypervisor_installation.rst:3732
+# fcb6675f3cbf47bd84f39d85c831b62c
+# 6446967b0b204707837f42e08d7b998a
+# 116a752e270144b9ae56210887f4ad80
+msgid "There are many ways to configure your network. In the Basic networking mode you should have two (V)LAN's, one for your private network and one for the public network."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:488
+#: ../../hypervisor_installation.rst:711
+#: ../../hypervisor_installation.rst:3736
+# 15d921dedb524980b41aafbd170bec51
+# 7956438fead040698f6cced9c78a2b6c
+# 8eefa91987504ceb9f915423bd9cd7ee
+msgid "We assume that the hypervisor has one NIC (eth0) with three tagged VLAN's:"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:493
+#: ../../hypervisor_installation.rst:716
+#: ../../hypervisor_installation.rst:3741
+# 0877467f5181444597ffc59798a984c2
+# e05717e09bf44963b799a357f63d06c0
+# 9c3b52a0f37349628d7e9863b22f7586
+msgid "VLAN 100 for management of the hypervisor"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:497
+#: ../../hypervisor_installation.rst:720
+#: ../../hypervisor_installation.rst:3745
+# d0358c8e6e704280a94d8154520cc512
+# 9d4164a76748495290ea59d97dfde5f0
+# 7db7cbd5fdbd485cab9d24025b7d7812
+msgid "VLAN 200 for public network of the instances (cloudbr0)"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:501
+#: ../../hypervisor_installation.rst:724
+#: ../../hypervisor_installation.rst:3749
+# 1f92bbd42f4848b7824c11163deccdce
+# 386e672345ad4798b937956aa78f982d
+# bca715eb0552403c97ecabf386e7ba9c
+msgid "VLAN 300 for private network of the instances (cloudbr1)"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:503
+#: ../../hypervisor_installation.rst:726
+#: ../../hypervisor_installation.rst:3751
+# aa94795c65f344c89c206c32fe15d941
+# 48a286c49f7441b19ed5ef3435348d59
+# dc43104aac9543c78fafa5f30dffaa8b
+msgid "On VLAN 100 we give the Hypervisor the IP-Address 192.168.42.11/24 with the gateway 192.168.42.1"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:506
+#: ../../hypervisor_installation.rst:729
+#: ../../hypervisor_installation.rst:3754
+# 6d48a58cd57f46238b8aaf12909c69d1
+# b8bb257a296c4bed98f1dad806ad5ba1
+# 900d19465df34526bfc636edfdb5534c
+msgid "The Hypervisor and Management server don't have to be in the same subnet!"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:509
+#: ../../hypervisor_installation.rst:732
+#: ../../hypervisor_installation.rst:3757
+# c32119ed14d44cb8bc32676656b99910
+# d879c320747d4850b1c5bacdd29a1669
+# 83f2160f524f43cf869a63489a608275
+msgid "Configuring the network bridges"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:511
+#: ../../hypervisor_installation.rst:3759
+# a80e5f8891a44a56affd76a4611c1785
+# c623ed65e9ba45b89f407ce4339a56e1
+msgid "It depends on the distribution you are using how to configure these, below you'll find examples for RHEL/CentOS and Ubuntu."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:514
+#: ../../hypervisor_installation.rst:3762
+# 1bb4087b2e5548119e9075fa05467ff9
+# 1992bd1a538a4e87aff11f08a30811ca
+msgid "The goal is to have two bridges called 'cloudbr0' and 'cloudbr1' after this section. This should be used as a guideline only. The exact configuration will depend on your network layout."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:517
+#: ../../hypervisor_installation.rst:759
+#: ../../hypervisor_installation.rst:3765
+# adab06c881724079959a8ae96aa924d0
+# 4978f5c0d9024cceb5523422d9f6e3c3
+# b5304e1cd17b43d49387c9e1f0dc4600
+msgid "Configure in RHEL or CentOS"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:519
+#: ../../hypervisor_installation.rst:3767
+# 95d2aaf4ea374d68ab231cf69aa771db
+# 6ee3e4cd4ddd42eda7adf6a56c2de197
+msgid "The required packages were installed when libvirt was installed, we can proceed to configuring the network."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:522
+#: ../../hypervisor_installation.rst:764
+#: ../../hypervisor_installation.rst:3770
+# 029a729a30a646bb882fa28fc6f4faf5
+# 13fa6771f34e4579bc8dba5e243a4011
+# d8e2cd1aa3de4613894102d0d8dfc562
+msgid "First we configure eth0"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:528
+#: ../../hypervisor_installation.rst:770
+#: ../../hypervisor_installation.rst:3776
+# dfdfd4f9776841959c87e33436d420ff
+# a055bef8a0304bf0827ea85c3116ff08
+# 175ef63f2d0e4d568e5df9298b56ef1f
+msgid "Make sure it looks similar to:"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:539
+#: ../../hypervisor_installation.rst:3787
+# aa158cdf890f4a73aa02cee971b29325
+# 937d87800fba4c0c93874a7e1764bf85
+msgid "We now have to configure the three VLAN interfaces:"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:588
+#: ../../hypervisor_installation.rst:3836
+# 476469f3cb3a44b0b7782a599edaaf84
+# 9fcd4bb8ee1f4977b938630771b1dab2
+msgid "Now we have the VLAN interfaces configured we can add the bridges on top of them."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:595
+#: ../../hypervisor_installation.rst:3843
+# d77a52bf367046fdbce73058d169f265
+# d2eac1f518d24368b764df3e08aacb22
+msgid "Now we just configure it is a plain bridge without an IP-Address"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:608
+#: ../../hypervisor_installation.rst:3856
+# 0188228d5cff43fc939e85ab6c002118
+# 39f78adfcd624290b0564d41b3447db2
+msgid "We do the same for cloudbr1"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:625
+#: ../../hypervisor_installation.rst:672
+#: ../../hypervisor_installation.rst:840
+#: ../../hypervisor_installation.rst:3873
+#: ../../hypervisor_installation.rst:3920
+# 218608446e8e45528b00bea4c57ebab9
+# f929fa3761b04167bda58c3a6f67cbfa
+# cdec6d4dfc5f4e95a212712a3bc64a61
+# dde4ad6a203a4cd58b6fe12d2f745b30
+# 2210405cea3845758c377fea3f5a3a2e
+msgid "With this configuration you should be able to restart the network, although a reboot is recommended to see if everything works properly."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:628
+#: ../../hypervisor_installation.rst:675
+#: ../../hypervisor_installation.rst:843
+#: ../../hypervisor_installation.rst:3876
+#: ../../hypervisor_installation.rst:3923
+# 9ced5c3d4eeb4f27b12cd0cb9f044a90
+# b88351fb9a7b43b09d7230cb38ae4c58
+# 1f463bc97d1147db85bec0e461319336
+# de08a3e8c75f461ea791f59685988cb5
+# a0974a28a6fa4008ae279ad0685d47f5
+msgid "Make sure you have an alternative way like IPMI or ILO to reach the machine in case you made a configuration error and the network stops functioning!"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:631
+#: ../../hypervisor_installation.rst:3879
+# 17acbbca1f3345849046fa6c4ebed4fc
+# 8cdc0e43e63641789dc4bd075c3d0bc3
+msgid "Configure in Ubuntu"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:633
+#: ../../hypervisor_installation.rst:3881
+# 41f30048a88c4bb993a0d890f181b28d
+# 93e837e2bf274c668eee8f0a619c4a5d
+msgid "All the required packages were installed when you installed libvirt, so we only have to configure the network."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:640
+#: ../../hypervisor_installation.rst:3888
+# 01fb8740e0b9423d8b655864775af54e
+# 262554e455a648fabdf442b6e301f259
+msgid "Modify the interfaces file to look like this:"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:678
+# e332c16e171f47169b256805eafe7615
+msgid "Configure the network using OpenVswitch"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:692
+# aa202fe73fee4c45827aa38313f60aec
+msgid "Preparing"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:694
+# eca14b3123854338ba1f14a14829b739
+msgid "To make sure that the native bridge module will not interfere with openvswitch the bridge module should be added to the blacklist. See the modprobe documentation for your distribution on where to find the blacklist. Make sure the module is not loaded either by rebooting or executing rmmod bridge before executing next steps."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:700
+# bf7a4c48ba2a4e4fa616e9e4415abcc7
+msgid "The network configurations below depend on the ifup-ovs and ifdown-ovs scripts which are part of the openvswitch installation. They should be installed in /etc/sysconfig/network-scripts/"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:734
+# 4d690db0a1544fd29d71656ec0ffcefd
+msgid "It depends on the distribution you are using how to configure these, below you'll find examples for RHEL/CentOS."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:737
+# ee8734ea127c4e8f8b66e5c4dea71bbf
+msgid "The goal is to have three bridges called 'mgmt0', 'cloudbr0' and 'cloudbr1' after this section. This should be used as a guideline only. The exact configuration will depend on your network layout."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:740
+# a74c6627f02043d5be917f12e7d0b263
+msgid "Configure OpenVswitch"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:742
+# e34d3c3a549a4b5e90ffd8f8afa33b07
+msgid "The network interfaces using OpenVswitch are created using the ovs-vsctl command. This command will configure the interfaces and persist them to the OpenVswitch database."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:746
+# fc0396cdb2c247b4ba0851d2b478d8c9
+msgid "First we create a main bridge connected to the eth0 interface. Next we create three fake bridges, each connected to a specific vlan tag."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:761
+# 02df0e7f19b4486bbaada2d6b794b9ad
+msgid "The required packages were installed when openvswitch and libvirt were installed, we can proceed to configuring the network."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:781
+# afab5f01a1714f0cb60ff9eed2db599d
+msgid "We have to configure the base bridge with the trunk."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:796
+# e104896bad1742b5b84682172fbd9b32
+msgid "We now have to configure the three VLAN bridges:"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:846
+#: ../../hypervisor_installation.rst:3926
+# 3564d9d50ea44f139e404791fd72f0af
+# 02fce31af22c4ed5abbd727f13ad05f0
+msgid "Configuring the firewall"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:848
+#: ../../hypervisor_installation.rst:3928
+# 2db1d0f133da4a66a7b2907acedd42a9
+# 5b0f650e2d114047a0415b7ea57f3251
+msgid "The hypervisor needs to be able to communicate with other hypervisors and the management server needs to be able to reach the hypervisor."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:851
+#: ../../hypervisor_installation.rst:3931
+# 935242b052ff490e9ad7270b8ddce890
+# 8c950a2e6b57475fa7752ffa9ed1e5bd
+msgid "In order to do so we have to open the following TCP ports (if you are using a firewall):"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:856
+#: ../../hypervisor_installation.rst:3936
+# cb69e4cdb8684774badfb4574559faa0
+# ae914c26a05444f9837e3ea892d275e2
+msgid "22 (SSH)"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:860
+#: ../../hypervisor_installation.rst:3940
+# 3807a267ba4b47248846cb82be68d71e
+# 8d4a188d4a5c42408f9a9da6c952d345
+msgid "1798"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:864
+#: ../../hypervisor_installation.rst:3944
+# 87b8b1e5c9924af5b368bcbb7d2e8148
+# 130a835b7e534e1aad8b66a350c80a9c
+msgid "16509 (libvirt)"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:868
+#: ../../hypervisor_installation.rst:3948
+# eb66ea04a90b4b46bd6c5529c74201b7
+# 332c2e7a9cdc40909b84e4bb4a550a92
+msgid "5900 - 6100 (VNC consoles)"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:872
+#: ../../hypervisor_installation.rst:3952
+# a65af6b9acbf47a08b1f7222b105fd4f
+# 709185e3e76045d6a3a6d0df2f61efb3
+msgid "49152 - 49216 (libvirt live migration)"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:874
+#: ../../hypervisor_installation.rst:3954
+# aa084591023a46ccb4cea81e8cc0baea
+# bc3288c0a792458c9d188c275d27a458
+msgid "It depends on the firewall you are using how to open these ports. Below you'll find examples how to open these ports in RHEL/CentOS and Ubuntu."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:878
+#: ../../hypervisor_installation.rst:3958
+# 7129650cbfc6416d8d015c4a64781ac8
+# 65d598aa7b414f5393a37799d4c2c1a2
+msgid "Open ports in RHEL/CentOS"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:880
+#: ../../hypervisor_installation.rst:3960
+# bb6efe14098442169446a2cfaf0ddfa0
+# e5bb8f2688ff41b98cf556f60758aa87
+msgid "RHEL and CentOS use iptables for firewalling the system, you can open extra ports by executing the following iptable commands:"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:903
+#: ../../hypervisor_installation.rst:3983
+# d68286a4499a42d0af59d58cf3307ce8
+# cabb0609f32c4af983aec749c9a3bde6
+msgid "These iptable settings are not persistent accross reboots, we have to save them first."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:911
+#: ../../hypervisor_installation.rst:3991
+# 307b4260b7a74cd392d59bb3418c7eb8
+# a54b92341f454cf3aee68b8a07bd8108
+msgid "Open ports in Ubuntu"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:913
+#: ../../hypervisor_installation.rst:3993
+# 8f7697ea5cda4eeeae5602b276f55313
+# ca6e09ab840f496fa590a392c3c0fcb1
+msgid "The default firewall under Ubuntu is UFW (Uncomplicated FireWall), which is a Python wrapper around iptables."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:916
+#: ../../hypervisor_installation.rst:3996
+# 036e661454dd43b6bcf5724a4cfc8e21
+# 63b5466496e643e5adac39e7c08d34f7
+msgid "To open the required ports, execute the following commands:"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:938
+#: ../../hypervisor_installation.rst:4019
+# d199e9f02aa34c2e998aba25484840c8
+# f7ee2acc10334a4bb43bb2cb66688c77
+msgid "By default UFW is not enabled on Ubuntu. Executing these commands with the firewall disabled does not enable the firewall."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:941
+#: ../../hypervisor_installation.rst:4022
+# f6fb4b8f7864465a8e8b2c9c726ec59c
+# 16dd0d2c501d4beea5ff4ef875698cd4
+msgid "Add the host to CloudStack"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:949
+# 870fb106f927434690fac18321ce0e59
+msgid "Hypervisor Support for Primary Storage"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:951
+# 11b373255a32403a97695fb159fd09d9
+msgid "The following table shows storage options and parameters for different hypervisors."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:955
+# 71d9dffcec0844acb2949eb60cea1944
+msgid "Primary Storage Type"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:955
+# 0b37e00477ab432691d060c0c73f3257
+msgid "vSphere"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:955
+# 7129c9b88c17431f9d16cb9947a677a7
+msgid "XenServer"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:955
+# 71094f1d15124724a6a0e6213b1d6daf
+msgid "KVM"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:955
+#: ../../hypervisor_installation.rst:1963
+# 09568b1f16e7426cab559aa9770bb87e
+# cfd57be6b2324793bc6c05ad29e6f751
+msgid "Hyper-V"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:957
+# 7046ca99b00143a18a1ac6585ea583d5
+msgid "****Format for Disks, Templates, and Snapshots****"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:957
+# 5ab36f207b4146588dd7917af86aa5b7
+msgid "VMDK"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:957
+#: ../../hypervisor_installation.rst:957
+# 1d7d1640e1344432b8b4c9f64e6e3de5
+# e52e9c78a0de4ad8960d9ed8d6604e7d
+msgid "VHD"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:957
+# 73411b9629ba423fa63a082dc31e04af
+msgid "QCOW2"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:958
+# e66d4e3fef6549cd950eb5a969eaec5a
+msgid "**iSCSI support**"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:958
+#: ../../hypervisor_installation.rst:959
+# 6791f19ffe8c492383fd9e09030fe664
+# 9f409f8d387c4d46becc2b3ee6499050
+msgid "VMFS"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:958
+# 6a8d18eb6310463b8b26ce7341385c5d
+msgid "CLVM"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:958
+#: ../../hypervisor_installation.rst:959
+# 155ee7758b3b41aabd23851828723f07
+# 9b26e9f40b634c0d9829308022399474
+msgid "Yes, via Shared Mountpoint"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:958
+#: ../../hypervisor_installation.rst:959
+#: ../../hypervisor_installation.rst:960
+#: ../../hypervisor_installation.rst:962
+#: ../../hypervisor_installation.rst:963
+#: ../../hypervisor_installation.rst:963
+#: ../../hypervisor_installation.rst:963
+# ebeb1e87b3f440c0a9fa499698356297
+# 0b052a6c7d9a489ba64df2bf64913d0d
+# 3111e9e35d434428bd654afbef6e4661
+# 90ea1419362d4e61bdbbde02d29a56a9
+# 67db36f9276b461a9f2dc0a6c75a84f3
+# 48b9e13cfdf048599e7c03490006ccb4
+# 16b7d2f7dac94f76a225e10445cf619f
+msgid "No"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:959
+# 7d8573527e8a4bfba998b4d3ddf99bb7
+msgid "**Fiber Channel support**"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:959
+# 451dcefc9c6c470491dfea9998e24809
+msgid "Yes, via Existing SR"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:960
+# d36f043836cb43d9b60ee86d2ad41f62
+msgid "**NFS support**"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:960
+#: ../../hypervisor_installation.rst:960
+#: ../../hypervisor_installation.rst:960
+#: ../../hypervisor_installation.rst:961
+#: ../../hypervisor_installation.rst:961
+#: ../../hypervisor_installation.rst:961
+#: ../../hypervisor_installation.rst:961
+#: ../../hypervisor_installation.rst:963
+# 50ad2c0fcf9644c9a4a7c65f8ddcb5fa
+# b7dc2cbb224a4aa886eb6e569412cc82
+# 80a2fd8cf583437ebb542a1d060a0042
+# d06590ec3fc948149d7dd2172c4f6b06
+# be7e08adfd054b1ba87844c789deb247
+# f29c49b5074b4c57a993f973a89e4c78
+# 54d3e136689647ed8412737ac2ba6b93
+# 140e1d436e5343bf99920962e3cb2fc0
+msgid "Yes"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:961
+# ac8413ce909b4b7395fadd007b26c9ff
+msgid "**Local storage support**"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:962
+# 24ab7203b4c943739c6926678f0d0803
+msgid "**Storage over-provisioning**"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:962
+# e2e7fabe2be14351b704696cea18fa20
+msgid "NFS and iSCSI"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:962
+#: ../../hypervisor_installation.rst:962
+# 39253a1a6513430b8e09aaf5098c74ef
+# 42778c796f7740bf85e16e509c1496f4
+msgid "NFS"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:963
+# b9588ec4a2be4b1696503c5e85cc3a84
+msgid "**SMB/CIFS**"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:966
+# 7644794bf16d47c18ed02b558352bea1
+msgid "XenServer uses a clustered LVM system to store VM images on iSCSI and Fiber Channel volumes and does not support over-provisioning in the hypervisor. The storage server itself, however, can support thin-provisioning. As a result the CloudStack can still support storage over-provisioning by running on thin-provisioned storage volumes."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:972
+# d20bddfa830e48d99978bd5eab502169
+msgid "KVM supports \"Shared Mountpoint\" storage. A shared mountpoint is a file system path local to each server in a given cluster. The path must be the same across all Hosts in the cluster, for example /mnt/primary1. This shared mountpoint is assumed to be a clustered filesystem such as OCFS2. In this case the CloudStack does not attempt to mount or unmount the storage as is done with NFS. The CloudStack requires that the administrator insure that the storage is available"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:980
+# 8cc2529993044886a2edc38f568aa43d
+msgid "With NFS storage, CloudStack manages the overprovisioning. In this case the global configuration parameter storage.overprovisioning.factor controls the degree of overprovisioning. This is independent of hypervisor type."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:985
+# b1c2b65035cd42b5b242d8245827be53
+msgid "Local storage is an option for primary storage for vSphere, XenServer, and KVM. When the local disk option is enabled, a local disk storage pool is automatically created on each host. To use local storage for the System Virtual Machines (such as the Virtual Router), set system.vm.use.local.storage to true in global configuration."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:991
+# 2874ceeecfc747368a0daa2f4b670a8d
+msgid "CloudStack supports multiple primary storage pools in a Cluster. For example, you could provision 2 NFS servers in primary storage. Or you could provision 1 iSCSI LUN initially and then add a second iSCSI LUN when the first approaches capacity."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:997
+# bb8410c437ae4dfc83006d467deab5ee
+msgid "Citrix XenServer Installation for CloudStack"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:999
+# f039a87fd91f4cf5af82b5a0d0e14279
+msgid "If you want to use the Citrix XenServer hypervisor to run guest virtual machines, install XenServer 6.0 or XenServer 6.0.2 on the host(s) in your cloud. For an initial installation, follow the steps below. If you have previously installed XenServer and want to upgrade to another version, see :ref:`upgrading-xenserver-version`."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1006
+# 1393db47eb314f93ac51b5df28608757
+msgid "System Requirements for XenServer Hosts"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1010
+# cee59e8c9fbe4466b998c22c775285aa
+msgid "The host must be certified as compatible with one of the following. See the Citrix Hardware Compatibility Guide: `http://hcl.xensource.com <http://hcl.xensource.com>`_"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1014
+# f3b55d603c69440cac3ff406039da6fa
+msgid "XenServer 5.6 SP2"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1015
+# be0e05f590c548658fc054e3b7c183c4
+msgid "XenServer 6.0"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1016
+# 859b34a50d8a47b98924d9bc9e66bf34
+msgid "XenServer 6.0.2"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1017
+# f62ad598aa04405db735768bcd28f3cb
+msgid "XenServer 6.1.0"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1018
+# 1ef19600bf954890ba8ab95144a9dbe9
+msgid "XenServer 6.2.0"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1022
+# 7f67c993b17a4b25a8b436331132a38b
+msgid "You must re-install Citrix XenServer if you are going to re-use a host from a previous install."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1031
+# 79b4544cf3614dd7a7be4fb67c18c3cc
+msgid "Be sure all the hotfixes provided by the hypervisor vendor are applied. Track the release of hypervisor patches through your hypervisor vendor’s support channel, and apply patches as soon as possible after they are released. CloudStack will not track or notify you of required hypervisor patches. It is essential that your hosts are completely up to date with the provided hypervisor patches. The hypervisor vendor is likely to refuse to support any system that is not up to date with patches."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1042
+# 00bde44b482f4ea297f009d4d8544f68
+msgid "All hosts within a cluster must be homogeneous. The CPUs must be of the same type, count, and feature flags."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1047
+# 1cc62dcb812144349e992ef157bc7f1e
+msgid "Must support HVM (Intel-VT or AMD-V enabled in BIOS)"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1055
+#: ../../hypervisor_installation.rst:2267
+# 7f48c8f440f3456a9675ec430f73fa14
+# 91c80a6655bf4e15999366adc5579b63
+msgid "Hardware virtualization support required"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1063
+#: ../../hypervisor_installation.rst:2275
+# edf681afdf084f4d95b31b905feef83e
+# b0c94baa01744e5d9a09a5a1a9be638f
+msgid "36 GB of local disk"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1071
+#: ../../hypervisor_installation.rst:2283
+# 2627aa6551664c18b24d53f01d85fdc9
+# 7d643f0e7d854677adf01b1b91684194
+msgid "Statically allocated IP Address"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1078
+# 86b1054dd7df47728888bb09e899e58e
+msgid "The lack of up-do-date hotfixes can lead to data corruption and lost VMs."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1081
+# ffb7f7e0b7d54edd842322b6dbd130bc
+msgid "XenServer Installation Steps"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1085
+# d29bd0f1992445e7bfe899ec7fdcd3bc
+msgid "From `https://www.citrix.com/English/ss/downloads/ <https://www.citrix.com/English/ss/downloads/>`_, download the appropriate version of XenServer for your CloudStack version (see `\"System Requirements for XenServer Hosts\" <#system-requirements-for-xenserver-hosts>`_). Install it using the Citrix XenServer Installation Guide."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1091
+# e4ff84caeefa4cdb9ff96d78ed4795bc
+msgid "Older Versions of XenServer:"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1093
+# dfbef4c3b3e74946805482a145c437ea
+msgid "Note that you can download the most recent release of XenServer without having a Citrix account. If you wish to download older versions, you will need to create an account and look through the download archives."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1099
+# a1f3be6636a2457095084a99017c2bef
+msgid "Configure XenServer dom0 Memory"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1101
+# 3d95fa3b3a0e4b1eb92dd506d58da069
+msgid "Configure the XenServer dom0 settings to allocate more memory to dom0. This can enable XenServer to handle larger numbers of virtual machines. We recommend 2940 MB of RAM for XenServer dom0. For instructions on how to do this, see `http://support.citrix.com/article/CTX126531 <http://support.citrix.com/article/CTX126531>`_. The article refers to XenServer 5.6, but the same information applies to XenServer 6.0."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1110
+# 9e46ff13cb284bb9bdfbe4141e984bc3
+msgid "Username and Password"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1112
+# 47b11d036dff42a990eebaab43d6265b
+msgid "All XenServers in a cluster must have the same username and password as configured in CloudStack."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1116
+# 04e9a76db62743b99541eca7808c3339
+msgid "Time Synchronization"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1118
+# 9fa198ee495f4b84b0bba7fd628e2e92
+msgid "The host must be set to use NTP. All hosts in a pod must have the same time."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1123
+# 4726eec6f10347b99a5e8076a1285988
+msgid "Install NTP."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1131
+# 5682aee95db547028f5e82cd70b046d7
+msgid "Edit the NTP configuration file to point to your NTP server."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1137
+# 1ce6772b97fb4129b0a526a33bfd18fa
+msgid "Add one or more server lines in this file with the names of the NTP servers you want to use. For example:"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1149
+# 69791d782a3541ca94d6c4751ec78f1f
+msgid "Restart the NTP client."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1157
+# 3b608298222445408c6e4d00c8b36707
+msgid "Make sure NTP will start again upon reboot."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1165
+# 0fcd0d55ec7049b69a3427a227e67180
+msgid "Install CloudStack XenServer Support Package (CSP)"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1167
+# ae16a3a52b0343d8b17bdbe5440015f1
+msgid "(Optional)"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1169
+# 030bdd1824914aac90fb1170106765ba
+msgid "To enable security groups, elastic load balancing, and elastic IP on XenServer, download and install the CloudStack XenServer Support Package (CSP). After installing XenServer, perform the following additional steps on each XenServer host."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1176
+# 41fcedb714c14a428ca6a9efe5a1d42f
+msgid "Download the CSP software onto the XenServer host from one of the following links:"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1179
+# f29bec21956d4917be7874f1b6a4177e
+msgid "For XenServer 6.0.2:"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1181
+# 54880e3acb4945b4ae3d3fb251252130
+msgid "`http://download.cloud.com/releases/3.0.1/XS-6.0.2/xenserver-cloud-supp.tgz <http://download.cloud.com/releases/3.0.1/XS-6.0.2/xenserver-cloud-supp.tgz>`_"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1183
+# 4405c659cea34cb2895c0f43693473f1
+msgid "For XenServer 5.6 SP2:"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1185
+# b1533b01dec04d8ea37cb07d541d8013
+msgid "`http://download.cloud.com/releases/2.2.0/xenserver-cloud-supp.tgz <http://download.cloud.com/releases/2.2.0/xenserver-cloud-supp.tgz>`_"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1187
+# 994df5c8945149b7b8663a2e603fc847
+msgid "For XenServer 6.0:"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1189
+# bc80c4fa363248c292882b511d90808a
+msgid "`http://download.cloud.com/releases/3.0/xenserver-cloud-supp.tgz <http://download.cloud.com/releases/3.0/xenserver-cloud-supp.tgz>`_"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1193
+# 09db532336c943caa7e4713f7f57deaa
+msgid "Extract the file:"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1201
+#: ../../hypervisor_installation.rst:1825
+# 08830377e2e845879acf2acd9cb55ecf
+# aa4d385951184c16a90f45c0c3c5137a
+msgid "Run the following script:"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1209
+# 72924509d484445a81886c53211f2d14
+msgid "If the XenServer host is part of a zone that uses basic networking, disable Open vSwitch (OVS):"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1216
+# adb679b9cadf4ab587ebaa643690988a
+msgid "Restart the host machine when prompted."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1218
+# bd826e8c78c04cf2ac613043dd1aa8ef
+msgid "The XenServer host is now ready to be added to CloudStack."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1221
+# 4d2cc4a9829c43c79dffee9dffb52d68
+msgid "Primary Storage Setup for XenServer"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1223
+# b0cc4d49e6d34d9db259e314792c0177
+msgid "CloudStack natively supports NFS, iSCSI and local storage. If you are using one of these storage types, there is no need to create the XenServer Storage Repository (\"SR\")."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1227
+# a62837dbc9e1484d9a2ec93a3f386570
+msgid "If, however, you would like to use storage connected via some other technology, such as FiberChannel, you must set up the SR yourself. To do so, perform the following steps. If you have your hosts in a XenServer pool, perform the steps on the master node. If you are working with a single XenServer which is not part of a cluster, perform the steps on that XenServer."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1236
+# 81eef0c2ce0249b3a2530d8dd37184b8
+msgid "Connect FiberChannel cable to all hosts in the cluster and to the FiberChannel storage host."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1241
+# b7ae02e3677b4008a1be03a37f030f35
+msgid "Rescan the SCSI bus. Either use the following command or use XenCenter to perform an HBA rescan."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1250
+# 0476baafcfbc4751a7b674d69113d59f
+msgid "Repeat step 2 on every host."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1254
+# 02f48106fb6144b7b2382f5073d07199
+msgid "Check to be sure you see the new SCSI disk."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1260
+# 37c8fa1fc8f84752a31863e7c7d8120d
+msgid "The output should look like this, although the specific file name will be different (scsi-<scsiID>):"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1270
+# d30a16069dcf439f859e28c39d871bdb
+msgid "Repeat step 4 on every host."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1274
+# d057bb9cd0164ff2af5b7b284a2f70bc
+msgid "On the storage server, run this command to get a unique ID for the new SR."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1281
+# 78a081f2a72e4bea8db0fd3c3d5789df
+msgid "The output should look like this, although the specific ID will be different:"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1290
+# faf5a8ab93ff4086828b6dc2491f0fd4
+msgid "Create the FiberChannel SR. In name-label, use the unique ID you just generated."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1299
+# c1a12adfd4e246b9ad5592e39b85708c
+msgid "This command returns a unique ID for the SR, like the following example (your ID will be different):"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1308
+# f32c1d33fc9f40779169b42513227c6b
+msgid "To create a human-readable description for the SR, use the following command. In uuid, use the SR ID returned by the previous command. In name-description, set whatever friendly text you prefer."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1316
+# b754f3a8e4df433090a93bb35257fecd
+msgid "Make note of the values you will need when you add this storage to CloudStack later (see `\"Add Primary Storage\" <configuration.html#add-primary-storage>`_). In the Add Primary Storage dialog, in Protocol, you will choose PreSetup. In SR Name-Label, you will enter the name-label you set earlier (in this example, e6849e96-86c3-4f2c-8fcc-350cc711be3d)."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1324
+# bb2c0a059376456fb6bca7407c545e10
+msgid "(Optional) If you want to enable multipath I/O on a FiberChannel SAN, refer to the documentation provided by the SAN vendor."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1328
+# f948cd8634034bd188d213da27d061f1
+msgid "iSCSI Multipath Setup for XenServer (Optional)"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1330
+# 2f15691307f84faaade1ec0f85382c0a
+msgid "When setting up the storage repository on a Citrix XenServer, you can enable multipath I/O, which uses redundant physical components to provide greater reliability in the connection between the server and the SAN. To enable multipathing, use a SAN solution that is supported for Citrix servers and follow the procedures in Citrix documentation. The following links provide a starting point:"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1339
+# c3e151c53ba543aa9a5c48cd1282a74b
+msgid "`http://support.citrix.com/article/CTX118791 <http://support.citrix.com/article/CTX118791>`_"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1343
+# 341d6153e8204ea697144d7f714fd80d
+msgid "`http://support.citrix.com/article/CTX125403 <http://support.citrix.com/article/CTX125403>`_"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1345
+# d88b03c3c9134875a81d6f6fcda13a65
+msgid "You can also ask your SAN vendor for advice about setting up your Citrix repository for multipathing."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1348
+# 01ad0cb79f9448c48d411af178ff801e
+msgid "Make note of the values you will need when you add this storage to the CloudStack later (see `\"Add Primary Storage\" <configuration.html#add-primary-storage>`_). In the Add Primary Storage dialog, in Protocol, you will choose PreSetup. In SR Name-Label, you will enter the same name used to create the SR."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1353
+# d447c7f93a09485c9104d3e0c6f30ed4
+msgid "If you encounter difficulty, address the support team for the SAN provided by your vendor. If they are not able to solve your issue, see Contacting Support."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1358
+# 3462935ca70247d4ad640ed9fc026627
+msgid "Physical Networking Setup for XenServer"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1360
+# 96146639e1894252a9993fb4085347e3
+msgid "Once XenServer has been installed, you may need to do some additional network configuration. At this point in the installation, you should have a plan for what NICs the host will have and what traffic each NIC will carry. The NICs should be cabled as necessary to implement your plan."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1366
+# f28bb641121f436ca9f8198d73026c0c
+msgid "If you plan on using NIC bonding, the NICs on all hosts in the cluster must be cabled exactly the same. For example, if eth0 is in the private bond on one host in a cluster, then eth0 must be in the private bond on all hosts in the cluster."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1371
+# b85094b7061646f493d481b41f4f5d9b
+msgid "The IP address assigned for the management network interface must be static. It can be set on the host itself or obtained via static DHCP."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1374
+# f4eaab06e1894ba28c9a3ee1c8fd19e2
+msgid "CloudStack configures network traffic of various types to use different NICs or bonds on the XenServer host. You can control this process and provide input to the Management Server through the use of XenServer network name labels. The name labels are placed on physical interfaces or bonds and configured in CloudStack. In some simple cases the name labels are not required."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1381
+# de56a32c98eb4628a39e7d67f51d4762
+msgid "When configuring networks in a XenServer environment, network traffic labels must be properly configured to ensure that the virtual interfaces are created by CloudStack are bound to the correct physical device. The name-label of the XenServer network must match the XenServer traffic label specified while creating the CloudStack network. This is set by running the following command:"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1393
+# 615cf9185dd24899b715f67bf68619ce
+msgid "Configuring Public Network with a Dedicated NIC for XenServer (Optional)"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1395
+# 3c82b6119dda4300b8573ec15d8e2700
+msgid "CloudStack supports the use of a second NIC (or bonded pair of NICs, described in :ref:`nic-bonding-for-xenserver`) for the public network. If bonding is not used, the public network can be on any NIC and can be on different NICs on the hosts in a cluster. For example, the public network can be on eth0 on node A and eth1 on node B. However, the XenServer name-label for the public network must be identical across all hosts. The following examples set the network label to \"cloud-public\". After the management server is installed and running you must configure it with the name of the chosen network label (e.g. \"cloud-public\"); this is discussed in `\"Management Server Installation\" <installation.html#management-server-installation>`_."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1406
+# 110691d610d44e6abc3b85a434281c45
+msgid "If you are using two NICs bonded together to create a public network, see :ref:`nic-bonding-for-xenserver`."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1409
+# 5eeb0c63f90641ba8ae5b6652fb43ac5
+msgid "If you are using a single dedicated NIC to provide public network access, follow this procedure on each new host that is added to CloudStack before adding the host."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1415
+# 06ff995c8cd147ecbee8398ae114eb8f
+msgid "Run xe network-list and find the public network. This is usually attached to the NIC that is public. Once you find the network make note of its UUID. Call this <UUID-Public>."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1421
+# bd31c6c93f934071bb6a514d4b1b50ca
+msgid "Run the following command."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1428
+# d2be307f51684ed299d0d6b382616d08
+msgid "Configuring Multiple Guest Networks for XenServer (Optional)"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1430
+# 52d7d8db9ce2409e83475cdad3955a33
+msgid "CloudStack supports the use of multiple guest networks with the XenServer hypervisor. Each network is assigned a name-label in XenServer. For example, you might have two networks with the labels \"cloud-guest\" and \"cloud-guest2\". After the management server is installed and running, you must add the networks and use these labels so that CloudStack is aware of the networks."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1437
+# 8a5be9e0828c4730b3dcb0b852e2220f
+msgid "Follow this procedure on each new host before adding the host to CloudStack:"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1442
+# 3634bb596dba4e22b7ea59c50eb2f1ef
+msgid "Run xe network-list and find one of the guest networks. Once you find the network make note of its UUID. Call this <UUID-Guest>."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1447
+# 786c3d9e0de241399b68a3ab7c3069cc
+msgid "Run the following command, substituting your own name-label and uuid values."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1456
+# 562afb7e19cf4d4381e2ec0f140e5e61
+msgid "Repeat these steps for each additional guest network, using a different name-label and uuid each time."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1460
+# 41b48003990c4afdb4b6b8a96f1513cd
+msgid "Separate Storage Network for XenServer (Optional)"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1462
+# d1c730db57c24a7da597f35913fe72f0
+msgid "You can optionally set up a separate storage network. This should be done first on the host, before implementing the bonding steps below. This can be done using one or two available NICs. With two NICs bonding may be done as above. It is the administrator's responsibility to set up a separate storage network."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1468
+# 5077124054fc4ba3b593435b5bd5b709
+msgid "Give the storage network a different name-label than what will be given for other networks."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1471
+# 2c93ae198ee746f7b38008dc9aaa2b63
+msgid "For the separate storage network to work correctly, it must be the only interface that can ping the primary storage device's IP address. For example, if eth0 is the management network NIC, ping -I eth0 <primary storage device IP> must fail. In all deployments, secondary storage devices must be pingable from the management network NIC or bond. If a secondary storage device has been placed on the storage network, it must also be pingable via the storage network NIC or bond on the hosts as well."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1480
+# 5dc74fbf37884dd1a441515d7ccb3739
+msgid "You can set up two separate storage networks as well. For example, if you intend to implement iSCSI multipath, dedicate two non-bonded NICs to multipath. Each of the two networks needs a unique name-label."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1484
+# 21486bfc4a50447a974137680f2e8750
+msgid "If no bonding is done, the administrator must set up and name-label the separate storage network on all hosts (masters and slaves)."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1487
+# e74b734827c148e4abf67add41daf5fa
+msgid "Here is an example to set up eth5 to access a storage network on 172.16.0.0/24."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1500
+# 4c8478c9b0404061b4f0eb4cf916b145
+msgid "NIC Bonding for XenServer (Optional)"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1502
+# dc0584c53b15404da1bd19bd6ee782bf
+msgid "XenServer supports Source Level Balancing (SLB) NIC bonding. Two NICs can be bonded together to carry public, private, and guest traffic, or some combination of these. Separate storage networks are also possible. Here are some example supported configurations:"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1509
+# 585023d3f7b24463a959419863701154
+msgid "2 NICs on private, 2 NICs on public, 2 NICs on storage"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1513
+# 85ce9960f5f64e7e81103c42a25c7992
+msgid "2 NICs on private, 1 NIC on public, storage uses management network"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1517
+# 766a18c82a444b0f9940f362c82e2922
+msgid "2 NICs on private, 2 NICs on public, storage uses management network"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1521
+# a559ff80b0a94e9799389702be54cf19
+msgid "1 NIC for private, public, and storage"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1523
+# b92a690f72754add8ee271cf1ba240f1
+msgid "All NIC bonding is optional."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1525
+# 26835cc7c2844c809af0dc5a4cfc4742
+msgid "XenServer expects all nodes in a cluster will have the same network cabling and same bonds implemented. In an installation the master will be the first host that was added to the cluster and the slave hosts will be all subsequent hosts added to the cluster. The bonds present on the master set the expectation for hosts added to the cluster later. The procedure to set up bonds on the master and slaves are different, and are described below. There are several important implications of this:"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1535
+# 422eb3cde8234e3a8e6269cdb3548d5a
+msgid "You must set bonds on the first host added to a cluster. Then you must use xe commands as below to establish the same bonds in the second and subsequent hosts added to a cluster."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1541
+# c3572859ed994bf79cccdac0dc036ada
+msgid "Slave hosts in a cluster must be cabled exactly the same as the master. For example, if eth0 is in the private bond on the master, it must be in the management network for added slave hosts."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1546
+# 50715edffb014ce094ecfdcfc1429bc7
+msgid "Management Network Bonding"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1548
+# 355923780aac48ae87b6a24963efcbab
+msgid "The administrator must bond the management network NICs prior to adding the host to CloudStack."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1552
+# 241a3f2bb47549c1b613bc5468c732d1
+msgid "Creating a Private Bond on the First Host in the Cluster"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1554
+# b0b878648bc34dd3b949b2492db4ebe7
+msgid "Use the following steps to create a bond in XenServer. These steps should be run on only the first host in a cluster. This example creates the cloud-private network with two physical NICs (eth0 and eth1) bonded into it."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1561
+#: ../../hypervisor_installation.rst:1607
+# c818433917984f208742d7624945c715
+# c273eb3061e74432b57d9077c627c6ea
+msgid "Find the physical NICs that you want to bond together."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1568
+# 913da62e00594d7d9256568a0966482a
+msgid "These command shows the eth0 and eth1 NICs and their UUIDs. Substitute the ethX devices of your choice. Call the UUID's returned by the above command slave1-UUID and slave2-UUID."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1574
+# 5f7804ba516044498b79880642b90e2c
+msgid "Create a new network for the bond. For example, a new network with name \"cloud-private\"."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1577
+# d2ccc4ae2a144c8b9d8337cc227fb222
+msgid "**This label is important. CloudStack looks for a network by a name you configure. You must use the same name-label for all hosts in the cloud for the management network.**"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1587
+# f3b50a468a3e4e83813f2acba6062bd8
+msgid "Now you have a bonded pair that can be recognized by CloudStack as the management network."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1591
+# cf64cccd2bb745bcaaddd7b531fbc539
+msgid "Public Network Bonding"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1593
+# f999c0e7062f47cf9e78cd29a0554039
+msgid "Bonding can be implemented on a separate, public network. The administrator is responsible for creating a bond for the public network if that network will be bonded and will be separate from the management network."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1599
+# 0242521ca5b94ecfa005cd45513c5d1f
+msgid "Creating a Public Bond on the First Host in the Cluster"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1601
+# 3582283d68284b5fb85af54cb569eaca
+msgid "These steps should be run on only the first host in a cluster. This example creates the cloud-public network with two physical NICs (eth2 and eth3) bonded into it."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1614
+# 525068448771408183ac84f1a5d006be
+msgid "These command shows the eth2 and eth3 NICs and their UUIDs. Substitute the ethX devices of your choice. Call the UUID's returned by the above command slave1-UUID and slave2-UUID."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1620
+# b9e69c9100564b88b43f6779621e12c4
+msgid "Create a new network for the bond. For example, a new network with name \"cloud-public\"."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1623
+# d4f75d2fc44545eaa191a59720d7ac1c
+msgid "**This label is important. CloudStack looks for a network by a name you configure. You must use the same name-label for all hosts in the cloud for the public network.**"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1633
+# f11b8de48bbf4fc6895b7bb33f52a308
+msgid "Now you have a bonded pair that can be recognized by CloudStack as the public network."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1637
+# 08c0b83d57f64624a7fa7bb0b057d887
+msgid "Adding More Hosts to the Cluster"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1639
+# 7b998653c91d417d9920cdf8a2b62752
+msgid "With the bonds (if any) established on the master, you should add additional, slave hosts. Run the following command for all additional hosts to be added to the cluster. This will cause the host to join the master in a single XenServer pool."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1650
+# 46fa7303d5604b5aa8d3a61679d51e47
+msgid "Complete the Bonding Setup Across the Cluster"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1652
+# 53dea66729854ace9b2af4bdfc78c1ca
+msgid "With all hosts added to the pool, run the cloud-setup-bond script. This script will complete the configuration and set up of the bonds across all hosts in the cluster."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1658
+# cd69e7cc948c43ffa11698a2390cf986
+msgid "Copy the script from the Management Server in /usr/share/cloudstack-common/scripts/vm/hypervisor/xenserver/cloud-setup-bonding.sh to the master host and ensure it is executable."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1664
+# 3b7ac5520f0e464aa6c2c0dcb9f61233
+msgid "Run the script:"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1670
+# 878fb7127a004f419b95241af6bee8ae
+msgid "Now the bonds are set up and configured properly across the cluster."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1675
+# 6b4c5561ec7e4237b7dc17126c581b6a
+msgid "Upgrading XenServer Versions"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1677
+# cfc09c589fb540b0b0a1bec122afd5ff
+msgid "This section tells how to upgrade XenServer software on CloudStack hosts. The actual upgrade is described in XenServer documentation, but there are some additional steps you must perform before and after the upgrade."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1682
+# 2376fd5b927644c8b4b846ad245f3688
+msgid "Be sure the hardware is certified compatible with the new version of XenServer."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1684
+# 942358ec8cfb439aa09b3a2faf54e73c
+msgid "To upgrade XenServer:"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1688
+# e1b8b830b03645a7ab9cc4e5d534e1d1
+msgid "Upgrade the database. On the Management Server node:"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1692
+# 8b47371c505b4b43a8e836e8d1747528
+msgid "Back up the database:"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1701
+# 99f965b30fe24ab8bfff83358a44964e
+msgid "You might need to change the OS type settings for VMs running on the upgraded hosts."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1706
+# ffcbd17272014822acea38cfefd3e547
+msgid "If you upgraded from XenServer 5.6 GA to XenServer 5.6 SP2, change any VMs that have the OS type CentOS 5.5 (32-bit), Oracle Enterprise Linux 5.5 (32-bit), or Red Hat Enterprise Linux 5.5 (32-bit) to Other Linux (32-bit). Change any VMs that have the 64-bit versions of these same OS types to Other Linux (64-bit)."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1715
+# 733596d54def49918fe6659885ae3c7b
+msgid "If you upgraded from XenServer 5.6 SP2 to XenServer 6.0.2, change any VMs that have the OS type CentOS 5.6 (32-bit), CentOS 5.7 (32-bit), Oracle Enterprise Linux 5.6 (32-bit), Oracle Enterprise Linux 5.7 (32-bit), Red Hat Enterprise Linux 5.6 (32-bit) , or Red Hat Enterprise Linux 5.7 (32-bit) to Other Linux (32-bit). Change any VMs that have the 64-bit versions of these same OS types to Other Linux (64-bit)."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1725
+# 14f2e711450e4ff58dd3149c1fdab21d
+msgid "If you upgraded from XenServer 5.6 to XenServer 6.0.2, do all of the above."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1730
+# f2619c1d24c74437a167e2d44d5253c7
+msgid "Restart the Management Server and Usage Server. You only need to do this once for all clusters."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1740
+# fc348fb3fda64c95883a94a886676f1d
+msgid "Disconnect the XenServer cluster from CloudStack."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1744
+#: ../../hypervisor_installation.rst:1874
+#: ../../hypervisor_installation.rst:3252
+#: ../../hypervisor_installation.rst:3301
+# 7f794481fc044e789630a36cdbfdf41f
+# f65c913be82f4fe09eb132c2c6dc033a
+# ca114347489c453a8cbd54f9520a6500
+# 21a397aa7b7d4f23ad83b33343dc8cd7
+msgid "Log in to the CloudStack UI as root."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1748
+# 7153d29a4b934e7bb7b4150b35a8b3e5
+msgid "Navigate to the XenServer cluster, and click Actions – Unmanage."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1752
+#: ../../hypervisor_installation.rst:3263
+# b860ab2de3c14f0da775023c03a393ed
+# 08c7c9f1bbca4dac9ca9abb2d901954f
+msgid "Watch the cluster status until it shows Unmanaged."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1756
+# f527402053e54831b67ae8daef6083c5
+msgid "Log in to one of the hosts in the cluster, and run this command to clean up the VLAN:"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1765
+# b42f28a2c2fb4455a41e6372a470f6a9
+msgid "Still logged in to the host, run the upgrade preparation script:"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1771
+# f6179b84964541bb846a719b3663189e
+msgid "Troubleshooting: If you see the error \"can't eject CD,\" log in to the VM and umount the CD, then run the script again."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1776
+# d7a81f24da0d4fd0b589ebfcfcd71784
+msgid "Upgrade the XenServer software on all hosts in the cluster. Upgrade the master first."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1781
+# 11d3dd98878f4fe08f96c16e5df8c6ac
+msgid "Live migrate all VMs on this host to other hosts. See the instructions for live migration in the Administrator's Guide."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1784
+# 1bdb8f184a494eb4969abf3ba696ed19
+msgid "Troubleshooting: You might see the following error when you migrate a VM:"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1793
+# 6ad7bdb81aca465a9b5938d726550c76
+msgid "To solve this issue, run the following:"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1801
+# 9676fe491f5740eaba74cd4060ed35f4
+msgid "Reboot the host."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1805
+# 383661aa66db407a8dd6f313e2acc4f4
+msgid "Upgrade to the newer version of XenServer. Use the steps in XenServer documentation."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1810
+# ef1bce7a4ef44573a6106976c04c4c45
+msgid "After the upgrade is complete, copy the following files from the management server to this host, in the directory locations shown below:"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1815
+# 64ccf69ad9eb4dfeb17c080ada99de6f
+msgid "Copy this Management Server file"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1815
+# 32e9ec87a68946b5b2705187b2201880
+msgid "To this location on the XenServer host"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1817
+# d008b2ce2b484b0aa482d6df64c2b74e
+msgid "/usr/share/cloudstack-common/scripts/vm/hypervisor/xenserver/xenserver60/NFSSR.py"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1817
+# e6b5a2e9d2684509ba864a23c275056f
+msgid "/opt/xensource/sm/NFSSR.py"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1818
+# d5f8132be2874a02b0853331d25286ed
+msgid "/usr/share/cloudstack-common/scripts/vm/hypervisor/xenserver/setupxenserver.sh"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1818
+# 2393c9fde5964bcdb21f54931c5cd007
+msgid "/opt/xensource/bin/setupxenserver.sh"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1819
+# 7a478317154146aa933ae7193c133e0a
+msgid "/usr/share/cloudstack-common/scripts/vm/hypervisor/xenserver/make\\_migratable.sh"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1819
+# 36d9f18cee164a5c9551ab66b058f0e5
+msgid "/opt/xensource/bin/make\\_migratable.sh"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1820
+# 5e031eb5f37f4b42a7a0357a9e963dde
+msgid "/usr/share/cloudstack-common/scripts/vm/hypervisor/xenserver/cloud-clean-vlan.sh"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1820
+# 12cd3626b3954c23be38e95e7059b7dc
+msgid "/opt/xensource/bin/cloud-clean-vlan.sh"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1831
+# 0b7bb106fe444196ae32f10b125d51bb
+msgid "Troubleshooting: If you see the following error message, you can safely ignore it."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1840
+# 84fc84c6930a40b88488984ff6c9112c
+msgid "Plug in the storage repositories (physical block devices) to the XenServer host:"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1847
+# d796a15c920847c7a8251c995526c02d
+msgid "If you add a host to this XenServer pool, you need to migrate all VMs on this host to other hosts, and eject this host from XenServer pool."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1851
+# f9bd9295e2b84bf2879c1ecbc602c44a
+msgid "Repeat these steps to upgrade every host in the cluster to the same version of XenServer."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1856
+# 8e37aa52a47547be82d24895b65f09f4
+msgid "Run the following command on one host in the XenServer cluster to clean up the host tags:"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1864
+# 8cf9d53037984028bce163054acb29f2
+msgid "When copying and pasting a command, be sure the command has pasted as a single line before executing. Some document viewers may introduce unwanted line breaks in copied text."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1870
+# 3e06a5a1b257415a9ede2507a47d0877
+msgid "Reconnect the XenServer cluster to CloudStack."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1878
+# 950820df270d40ebb2b49296c30a9a53
+msgid "Navigate to the XenServer cluster, and click Actions – Manage."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1882
+# 662b5d4d23744762922ae112f5e61b84
+msgid "Watch the status to see that all the hosts come up."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1886
+# 1b7befb539434c7db47239456ba7213e
+msgid "After all hosts are up, run the following on one host in the cluster:"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1893
+# d3a523f2e69a478bb90498d681b0178b
+msgid "Installing Hyper-V for CloudStack"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1895
+# b93fc39d5763433cb59938b5f75dd607
+msgid "If you want to use Hyper-V hypervisor to run guest virtual machines, install Hyper-V on the hosts in your cloud. The instructions in this section doesn't duplicate Hyper-V Installation documentation. It provides the CloudStack-specific steps that are needed to prepare a Hyper-V host to work with CloudStack."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1902
+# 2038da390b6848a0b3cc3fedef1a9d2c
+msgid "System Requirements for Hyper-V Hypervisor Hosts"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1905
+# fc724f9178b64868879b74a411d95ef5
+msgid "Supported Operating Systems for Hyper-V Hosts"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1909
+# 1a5519a64e134b1a91a658145276f6ed
+msgid "Windows Server 2012 R2 Standard"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1913
+# ee081eb7e4004f578c7da357ca3b65e2
+msgid "Windows Server 2012 R2 Datacenter"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1917
+# cd21b1eeb72340979622e7783f646d92
+msgid "Hyper-V 2012 R2"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1920
+# 0d65d540ddce44ad8a88d9484e834d25
+msgid "Minimum System Requirements for Hyper-V Hosts"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1924
+# ff261434dbf442899d95fec9961fdf73
+msgid "1.4 GHz 64-bit processor with hardware-assisted virtualization."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1928
+# 8213417edf9244ab8b88ea0831f4c865
+msgid "800 MB of RAM"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1932
+# bf16d06d9e7244b6bbb96e7b56e71357
+msgid "32 GB of disk space"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1936
+# 82c14f0ba5cc44b689942c4b99564fff
+msgid "Gigabit (10/100/1000baseT) Ethernet adapter"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1939
+# 51556185e39644d8a4bf6f8f7afa2861
+msgid "Supported Storage"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1943
+# 5beb17ae25a34423bc3a3e369212ec3f
+msgid "Primary Storage: Server Message Block (SMB) Version 3, Local"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1947
+# 55d3704fad27499b92347d61e7deb72a
+msgid "Secondary Storage: SMB"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1950
+# 703eb2b0e6fc40bcbda49bace0d0fb75
+msgid "Preparation Checklist for Hyper-V"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1952
+#: ../../hypervisor_installation.rst:2388
+# 419613931af84db383a87503c76f013c
+# 487f37bf5b724be48da1842d6f4f189e
+msgid "For a smoother installation, gather the following information before you start:"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1955
+# 2c101932aa3e4ca28fdcb6f78b2628f0
+msgid "Hyper-V Requirements"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1957
+#: ../../hypervisor_installation.rst:2715
+# a2108b6906c5463a9d62d10304f6f7c0
+# 7df31f594d084182a124fa1a5963c2e2
+msgid "Value"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1959
+#: ../../hypervisor_installation.rst:2900
+# 8c30f2b9669c4b839800c9fde5954476
+# e536631fc460428f82d0797650809db6
+msgid "Description"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1961
+# 9e31d44efe0d40bc8987a7f1b9a7560a
+msgid "Server Roles"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1965
+# 4de7af81dfc04ce89ecb35699251c666
+msgid "After the Windows Server 2012 R2 installation, ensure that Hyper-V is selected from Server Roles. For more information, see `Installing Hyper-V <http://technet.microsoft.com/en-us/library/jj134187.aspx#BKMK_Step2>`_."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1968
+# 644571f95331448f97fe445ae9ee8de9
+msgid "Share Location"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1970
+# 636f796bb2ad45c5a5de2c9166505359
+msgid "New folders in the /Share directory"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1972
+# 2b338e212cc74f149db217553b6b692f
+msgid "Ensure that folders are created for Primary and Secondary storage. The SMB share and the hosts should be part of the same domain."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1975
+# 7a6f754da1ec458ca9eae5c017e0ab52
+msgid "If you are using Windows SMB share, the location of the file share for the Hyper-V deployment will be the new folder created in the \\\\Shares on the selected volume. You can create sub-folders for both CloudStack Primary and Secondary storage within the share location. When you select the profile for the file shares, ensure that you select SMB Share -Applications. This creates the file shares with settings appropriate for Hyper-V."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1983
+# cfec42b2cfec42d7b8ffbd8e69cb8561
+msgid "Domain and Hosts"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1985
+# 40eb688b68184a569a98d100afc12873
+msgid "Hosts should be part of the same Active Directory domain."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1987
+# 6f43f5b3150444fd8d107a12fcebadb0
+msgid "Hyper-V Users"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1989
+# 571279354d664c0c9db4d00e780060ab
+msgid "Full control"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1991
+# d4526dd1a8b24a46b8a12c3188d43a1a
+msgid "Full control on the SMB file share."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1993
+# 3619e03fbf014ba3a55f9a8cbbeeb5b0
+msgid "Virtual Switch"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1995
+#: ../../hypervisor_installation.rst:2166
+# f63f68f216ba4cabb3a183f2539b2134
+# b7c90a0b793c4c48847a27c21d2b64ac
+msgid "If you are using Hyper-V 2012 R2, manually create an external virtual switch before adding the host to CloudStack. If the Hyper-V host is added to the Hyper-V manager, select the host, then click Virtual Switch Manager, then New Virtual Switch. In the External Network, select the desired NIC adapter and click Apply."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:2001
+#: ../../hypervisor_installation.rst:2172
+# 6d95d36bac3c4cc899af98614236b0d5
+# 4a0f7c13f957472b93f453ba6e2c6f23
+msgid "If you are using Windows 2012 R2, virtual switch is created automatically."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:2004
+# eedd8450f79a4f919ecbd025523beb7a
+msgid "Virtual Switch Name"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:2006
+# 705abed5f4e34a2abcdd893c5a585841
+msgid "Take a note of the name of the virtual switch. You need
<TRUNCATED>
[2/7] setup i18n with transifex and sphinx-intl
Posted by se...@apache.org.
http://git-wip-us.apache.org/repos/asf/cloudstack-docs-install/blob/bd81bcc4/source/locale/pot/network_setup.pot
----------------------------------------------------------------------
diff --git a/source/locale/pot/network_setup.pot b/source/locale/pot/network_setup.pot
new file mode 100644
index 0000000..dc38e27
--- /dev/null
+++ b/source/locale/pot/network_setup.pot
@@ -0,0 +1,1713 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2014, Apache Software Foundation
+# This file is distributed under the same license as the Apache CloudStack Installation Documentation package.
+# FIRST AUTHOR <EM...@ADDRESS>, YEAR.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: Apache CloudStack Installation Documentation 4\n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2014-03-31 14:02-0400\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"
+
+#: ../../network_setup.rst:17
+# 03bdaa3878ef48059529f90ef9afb586
+msgid "Network Setup"
+msgstr ""
+
+#: ../../network_setup.rst:19
+# f4ec374e4e894abe8d702f2342d0bf4a
+msgid "Achieving the correct networking setup is crucial to a successful CloudStack installation. This section contains information to help you make decisions and follow the right procedures to get your network set up correctly."
+msgstr ""
+
+#: ../../network_setup.rst:25
+# 015eb0cd841a4918a67710452e3fee84
+msgid "Basic and Advanced Networking"
+msgstr ""
+
+#: ../../network_setup.rst:27
+# 6f2f6d18096647618908c57de6343037
+msgid "CloudStack provides two styles of networking:."
+msgstr ""
+
+#: ../../network_setup.rst:30
+# 35f7f2c07a8343079a1e81ff1c6ea6cf
+msgid "**Basic**"
+msgstr ""
+
+#: ../../network_setup.rst:30
+# a29436ad2c1f47b686ead42ae7d648ab
+msgid "For AWS-style networking. Provides a single network where guest isolation can be provided through layer-3 means such as security groups (IP address source filtering)."
+msgstr ""
+
+#: ../../network_setup.rst:33
+# 1848d2187f1d4bdfa5667bb76fb79db9
+msgid "**Advanced**"
+msgstr ""
+
+#: ../../network_setup.rst:33
+# 21c108e78bde4a0eb0c8a56ece172adc
+msgid "For more sophisticated network topologies. This network model provides the most flexibility in defining guest networks, but requires more configuration steps than basic networking."
+msgstr ""
+
+#: ../../network_setup.rst:35
+# 5aebd31d3fd64c0aa3b97cd99e3db483
+msgid "Each zone has either basic or advanced networking. Once the choice of networking model for a zone has been made and configured in CloudStack, it can not be changed. A zone is either basic or advanced for its entire lifetime."
+msgstr ""
+
+#: ../../network_setup.rst:40
+# 3ef30fb83d1442d3b8e3acdb90503b3d
+msgid "The following table compares the networking features in the two networking models."
+msgstr ""
+
+#: ../../network_setup.rst:43
+# 82dd7efdfe484d37a2b0a7fd8264c82e
+msgid "Networking Feature"
+msgstr ""
+
+#: ../../network_setup.rst:43
+# e18218ba6b47423097b7f4c8f8096332
+msgid "Basic Network"
+msgstr ""
+
+#: ../../network_setup.rst:43
+# 084adb2cdafd42f49daf25997f52a71d
+msgid "Advanced Network"
+msgstr ""
+
+#: ../../network_setup.rst:45
+# cf6ebe6c183a41f0bdfe57e76b15955c
+msgid "Number of networks"
+msgstr ""
+
+#: ../../network_setup.rst:45
+# 5be9fdf69dc4401487accea91b520ab8
+msgid "Single network"
+msgstr ""
+
+#: ../../network_setup.rst:45
+# 8c7ecfe558e441a5af8459f218a9a451
+msgid "Multiple networks"
+msgstr ""
+
+#: ../../network_setup.rst:46
+# 370dc85892f443b592de2836c8ae875b
+msgid "Firewall type"
+msgstr ""
+
+#: ../../network_setup.rst:46
+#: ../../network_setup.rst:47
+#: ../../network_setup.rst:50
+#: ../../network_setup.rst:51
+# 91d834f45e5840faa8fa4ceb0105fe1b
+# a62f2cbfe24244abbed9697adbc0f7a1
+# b0eee01adf51415b94c325da3205c369
+# f2f4450fc0364615951cd4989bf2d1a1
+msgid "Physical"
+msgstr ""
+
+#: ../../network_setup.rst:46
+#: ../../network_setup.rst:47
+#: ../../network_setup.rst:50
+#: ../../network_setup.rst:51
+#: ../../network_setup.rst:52
+# 92939ada64cb46cea5e667a7483f3a88
+# 9f6310c04ac842c3975c06fa53bf0102
+# 9fe7692b62a24b6b8907c0218b9d12d0
+# 79fcdf99583c41f28f8288cc103f77d4
+# 9d5d473d8fa24ad1b7ff625e14a9ae84
+msgid "Physical and Virtual"
+msgstr ""
+
+#: ../../network_setup.rst:47
+# 5c7e1573e3aa41a98c8d858da115f01c
+msgid "Load balancer"
+msgstr ""
+
+#: ../../network_setup.rst:48
+# 8ed09eee40544757a067440d0af1f5de
+msgid "Isolation type"
+msgstr ""
+
+#: ../../network_setup.rst:48
+# a9ae797c6090433c9dfc9dbfbd29136d
+msgid "Layer 3"
+msgstr ""
+
+#: ../../network_setup.rst:48
+# 753feaff369c45eca38c679a8fe85d9e
+msgid "Layer 2 and Layer 3"
+msgstr ""
+
+#: ../../network_setup.rst:49
+# 6b87885206514a9e83815a27632766ce
+msgid "VPN support"
+msgstr ""
+
+#: ../../network_setup.rst:49
+#: ../../network_setup.rst:52
+#: ../../network_setup.rst:1127
+# d6a4a24cb596422abacfaf405ec4b307
+# 4e3440aeb3f44f8eae7ef35922a832d2
+# 9185a3db64f64736be27796c8abf94bb
+msgid "No"
+msgstr ""
+
+#: ../../network_setup.rst:49
+#: ../../network_setup.rst:53
+#: ../../network_setup.rst:53
+#: ../../network_setup.rst:55
+#: ../../network_setup.rst:55
+#: ../../network_setup.rst:1125
+#: ../../network_setup.rst:1126
+# 45279d7662df4901bad27b21a555b5b4
+# fa869b0c06a44936ae38664ae5b964c6
+# 94424e3b45de45d79f6b66c6f6531299
+# d5286f0917b64bfc9d2685effec949d6
+# 2dc0494184c4403486609b2d85a2c2ad
+# 80eed865b0ed418cbbe7a399e424f1d9
+# 798288df500b4f51b0be8d43a93d1b9e
+msgid "Yes"
+msgstr ""
+
+#: ../../network_setup.rst:50
+# 503ff9c4faad47fd977040f624d3b3cc
+msgid "Port forwarding"
+msgstr ""
+
+#: ../../network_setup.rst:51
+# a56a3231d1e848f695c709ce5baf45d7
+msgid "1:1 NAT"
+msgstr ""
+
+#: ../../network_setup.rst:52
+# f475f6ce633a4476bec28f8a840daa54
+msgid "Source NAT"
+msgstr ""
+
+#: ../../network_setup.rst:53
+# 026973fe60f04800bc46d099c14bdcf0
+msgid "Userdata"
+msgstr ""
+
+#: ../../network_setup.rst:54
+# 30fb573590f141bbae7ba33d4bf8bb97
+msgid "Network usage monitoring"
+msgstr ""
+
+#: ../../network_setup.rst:54
+# 6630eb888e5143d0be0a70e13e21f168
+msgid "sFlow / netFlow at physical router"
+msgstr ""
+
+#: ../../network_setup.rst:54
+# 7559d1ff62bc42f481a7cc8cb6adc938
+msgid "Hypervisor and Virtual Router"
+msgstr ""
+
+#: ../../network_setup.rst:55
+# 9385d68ce2d34875ab06b26c0319aa1a
+msgid "DNS and DHCP"
+msgstr ""
+
+#: ../../network_setup.rst:58
+# a6aba497281a48e9bff8afbd6c9a6272
+msgid "The two types of networking may be in use in the same cloud. However, a given zone must use either Basic Networking or Advanced Networking."
+msgstr ""
+
+#: ../../network_setup.rst:61
+# a27239c3e05f4f60b8ba16abded352fb
+msgid "Different types of network traffic can be segmented on the same physical network. Guest traffic can also be segmented by account. To isolate traffic, you can use separate VLANs. If you are using separate VLANs on a single physical network, make sure the VLAN tags are in separate numerical ranges."
+msgstr ""
+
+#: ../../network_setup.rst:68
+# 777d758fb09445768a2891b8e273603e
+msgid "VLAN Allocation Example"
+msgstr ""
+
+#: ../../network_setup.rst:70
+# 5fbe4896bc00421bbcb359e3d9bd72a2
+msgid "VLANs are required for public and guest traffic. The following is an example of a VLAN allocation scheme:"
+msgstr ""
+
+#: ../../network_setup.rst:74
+# b75e116966e5475c95d5e6db53fee3c0
+msgid "VLAN IDs"
+msgstr ""
+
+#: ../../network_setup.rst:74
+# eea4d9795b974a429773c0748d7442fe
+msgid "Traffic type"
+msgstr ""
+
+#: ../../network_setup.rst:74
+# 0b3853d3d14f4975ab7eed7af588cb09
+msgid "Scope"
+msgstr ""
+
+#: ../../network_setup.rst:76
+# 7ba30eb0289343dc929b0d6b71762ee0
+msgid "less than 500"
+msgstr ""
+
+#: ../../network_setup.rst:76
+# 46b3630dea2846779971de386d0061ef
+msgid "Management traffic. Reserved for administrative purposes."
+msgstr ""
+
+#: ../../network_setup.rst:76
+# f380aab2e1604e67ba9a286e7ad72d00
+msgid "CloudStack software can access this, hypervisors, system VMs."
+msgstr ""
+
+#: ../../network_setup.rst:77
+# add0f7eea0be422eb0d0e8583df4bd39
+msgid "500-599"
+msgstr ""
+
+#: ../../network_setup.rst:77
+# ee3c46bad38a4397abb1cb41cd5f1b39
+msgid "VLAN carrying public traffic."
+msgstr ""
+
+#: ../../network_setup.rst:77
+# 14652e15f43c4300922ff51854bd32d8
+msgid "CloudStack accounts."
+msgstr ""
+
+#: ../../network_setup.rst:78
+# 287abb8446da47df89505536698a5120
+msgid "600-799"
+msgstr ""
+
+#: ../../network_setup.rst:78
+#: ../../network_setup.rst:79
+# d0c66df38d50463096073291feaaf25c
+# fb9b57f83c934957a34139318ecf37f4
+msgid "VLANs carrying guest traffic."
+msgstr ""
+
+#: ../../network_setup.rst:78
+# f72135d431d7457d8373598683d96518
+msgid "CloudStack accounts. Account-specific VLAN is chosen from this pool."
+msgstr ""
+
+#: ../../network_setup.rst:79
+# 6b41efe52d3c419c895885d6fa1ba83e
+msgid "800-899"
+msgstr ""
+
+#: ../../network_setup.rst:79
+# beb773be4f6648b797670b16b4ed9606
+msgid "CloudStack accounts. Account-specific VLAN chosen by CloudStack admin to assign to that account."
+msgstr ""
+
+#: ../../network_setup.rst:80
+# d12d342f2b0549bfa7961cd5ab17ea96
+msgid "900-999"
+msgstr ""
+
+#: ../../network_setup.rst:80
+# 7b233d48fc4049078ffd74b260cfff7b
+msgid "VLAN carrying guest traffic"
+msgstr ""
+
+#: ../../network_setup.rst:80
+# df20993116bf4e4bb14571d7e0d53ad8
+msgid "CloudStack accounts. Can be scoped by project, domain, or all accounts."
+msgstr ""
+
+#: ../../network_setup.rst:81
+# 56b7a0d9885340ab91774f0502e03f66
+msgid "greater than 1000"
+msgstr ""
+
+#: ../../network_setup.rst:81
+# 2bc3f620008541f6ad9dd7516851d998
+msgid "Reserved for future use"
+msgstr ""
+
+#: ../../network_setup.rst:85
+# 20400094cee746b498658eab12a3d120
+msgid "Example Hardware Configuration"
+msgstr ""
+
+#: ../../network_setup.rst:87
+# c9d1fc5eac444e8cbc5aff1173d67b34
+msgid "This section contains an example configuration of specific switch models for zone-level layer-3 switching. It assumes VLAN management protocols, such as VTP or GVRP, have been disabled. The example scripts must be changed appropriately if you choose to use VTP or GVRP."
+msgstr ""
+
+#: ../../network_setup.rst:93
+#: ../../network_setup.rst:199
+# 0b6e3cfcbfd640119616c5cce9fb62ab
+# 7a678f85c8504344a03afa484cd26fb2
+msgid "Dell 62xx"
+msgstr ""
+
+#: ../../network_setup.rst:95
+# 82eed4d95bd04ff9bc2d3a25a1de9935
+msgid "The following steps show how a Dell 62xx is configured for zone-level layer-3 switching. These steps assume VLAN 201 is used to route untagged private IPs for pod 1, and pod 1’s layer-2 switch is connected to Ethernet port 1/g1."
+msgstr ""
+
+#: ../../network_setup.rst:100
+# b3cae48b13c046ba84d46aad2cfbabf0
+msgid "The Dell 62xx Series switch supports up to 1024 VLANs."
+msgstr ""
+
+#: ../../network_setup.rst:104
+#: ../../network_setup.rst:206
+# 8fb1a4ee9be946e292eb97ff3efa29d5
+# 0a2e26f115fe46ecb016c54f1be9a3dd
+msgid "Configure all the VLANs in the database."
+msgstr ""
+
+#: ../../network_setup.rst:114
+# c3cb04692c8842d5b5ad3d4340d44e8c
+msgid "Configure Ethernet port 1/g1."
+msgstr ""
+
+#: ../../network_setup.rst:125
+# 9abb8673cd194d77975f070e0d3303b2
+msgid "The statements configure Ethernet port 1/g1 as follows:"
+msgstr ""
+
+#: ../../network_setup.rst:129
+# 2d4ac0c0a70d49bebec9399363054a0b
+msgid "VLAN 201 is the native untagged VLAN for port 1/g1."
+msgstr ""
+
+#: ../../network_setup.rst:133
+# 241024fc15ac4185896d6f60765c6aeb
+msgid "All VLANs (300-999) are passed to all the pod-level layer-2 switches."
+msgstr ""
+
+#: ../../network_setup.rst:136
+#: ../../network_setup.rst:238
+# 6427ae55796f4cfd8e8a1854f33466d5
+# f9fa0d3dda7543f29c9246eb93ffec01
+msgid "Cisco 3750"
+msgstr ""
+
+#: ../../network_setup.rst:138
+# a6ecac33d6c14952b66e8017ad4a8323
+msgid "The following steps show how a Cisco 3750 is configured for zone-level layer-3 switching. These steps assume VLAN 201 is used to route untagged private IPs for pod 1, and pod 1’s layer-2 switch is connected to GigabitEthernet1/0/1."
+msgstr ""
+
+#: ../../network_setup.rst:145
+#: ../../network_setup.rst:245
+# 830457a045fc47c7b8ed9c5740e464c1
+# 176933aea5a346508236287640ea54a2
+msgid "Setting VTP mode to transparent allows us to utilize VLAN IDs above 1000. Since we only use VLANs up to 999, vtp transparent mode is not strictly required."
+msgstr ""
+
+#: ../../network_setup.rst:157
+# 8ea20a3779954323949736d659d4f422
+msgid "Configure GigabitEthernet1/0/1."
+msgstr ""
+
+#: ../../network_setup.rst:167
+# f1aef677767145a4bb66257ed779b828
+msgid "The statements configure GigabitEthernet1/0/1 as follows:"
+msgstr ""
+
+#: ../../network_setup.rst:171
+# d3f6c0584e724399a82d3a1b9d5b4fea
+msgid "VLAN 201 is the native untagged VLAN for port GigabitEthernet1/0/1."
+msgstr ""
+
+#: ../../network_setup.rst:175
+# d1736402c78e4079828531c40e3f9b95
+msgid "Cisco passes all VLANs by default. As a result, all VLANs (300-999) are passed to all the pod-level layer-2 switches."
+msgstr ""
+
+#: ../../network_setup.rst:179
+# 6ff660c4050c4f06b06f5181a688d274
+msgid "Layer-2 Switch"
+msgstr ""
+
+#: ../../network_setup.rst:181
+# c5578ac90f9a4ae1a8d9436be6005438
+msgid "The layer-2 switch is the access switching layer inside the pod."
+msgstr ""
+
+#: ../../network_setup.rst:185
+# 650d24b9adf54d9b8477c3ab4aef08fe
+msgid "It should trunk all VLANs into every computing host."
+msgstr ""
+
+#: ../../network_setup.rst:189
+# f50e67a3c6d94595bd2f3bd73b9a9366
+msgid "It should switch traffic for the management network containing computing and storage hosts. The layer-3 switch will serve as the gateway for the management network."
+msgstr ""
+
+#: ../../network_setup.rst:193
+# a4f9ace615c141c79c483fa9bfd39792
+msgid "The following sections contain example configurations for specific switch models for pod-level layer-2 switching. It assumes VLAN management protocols such as VTP or GVRP have been disabled. The scripts must be changed appropriately if you choose to use VTP or GVRP."
+msgstr ""
+
+#: ../../network_setup.rst:201
+# a3cf81c4e1fe43cca9903696d4591c81
+msgid "The following steps show how a Dell 62xx is configured for pod-level layer-2 switching."
+msgstr ""
+
+#: ../../network_setup.rst:216
+# d179aa8e95874b16b13d60695bc96388
+msgid "VLAN 201 is used to route untagged private IP addresses for pod 1, and pod 1 is connected to this layer-2 switch."
+msgstr ""
+
+#: ../../network_setup.rst:226
+# f63ff83a01964f68acc76185a5b05b75
+msgid "The statements configure all Ethernet ports to function as follows:"
+msgstr ""
+
+#: ../../network_setup.rst:230
+# 106d02a562d7477f8586172778d1707a
+msgid "All ports are configured the same way."
+msgstr ""
+
+#: ../../network_setup.rst:234
+# bafa7d17558c45c8bf7203a59521eca6
+msgid "All VLANs (300-999) are passed through all the ports of the layer-2 switch."
+msgstr ""
+
+#: ../../network_setup.rst:240
+# 2b72d3ec80aa4c09b6ef046bbd9d257b
+msgid "The following steps show how a Cisco 3750 is configured for pod-level layer-2 switching."
+msgstr ""
+
+#: ../../network_setup.rst:257
+# 15b3cb139c7742d0b17abfefb99f6bdf
+msgid "Configure all ports to dot1q and set 201 as the native VLAN."
+msgstr ""
+
+#: ../../network_setup.rst:267
+# 7336e080ecdd47a88123305127be89dc
+msgid "By default, Cisco passes all VLANs. Cisco switches complain of the native VLAN IDs are different when 2 ports are connected together. That’s why you must specify VLAN 201 as the native VLAN on the layer-2 switch."
+msgstr ""
+
+#: ../../network_setup.rst:273
+# 644dff1fd3644bed880bc56ed29bf62d
+msgid "Hardware Firewall"
+msgstr ""
+
+#: ../../network_setup.rst:275
+# 0f75cc6211f64303b63d1cac56ef4958
+msgid "All deployments should have a firewall protecting the management server; see Generic Firewall Provisions. Optionally, some deployments may also have a Juniper SRX firewall that will be the default gateway for the guest networks; see `“External Guest Firewall Integration for Juniper SRX (Optional)” <#external-guest-firewall-integration-for-juniper-srx-optional>`_."
+msgstr ""
+
+#: ../../network_setup.rst:281
+# dc2fee2bdd664bfdb56d7ee5206cc652
+msgid "Generic Firewall Provisions"
+msgstr ""
+
+#: ../../network_setup.rst:283
+# 614a9bc12b2c4cebad4ce3d0f21252bb
+msgid "The hardware firewall is required to serve two purposes:"
+msgstr ""
+
+#: ../../network_setup.rst:287
+# ebb0dcc176da45889b7d28aad2fccf39
+msgid "Protect the Management Servers. NAT and port forwarding should be configured to direct traffic from the public Internet to the Management Servers."
+msgstr ""
+
+#: ../../network_setup.rst:293
+# 09ae162b447841558abf654626b1c3dc
+msgid "Route management network traffic between multiple zones. Site-to-site VPN should be configured between multiple zones."
+msgstr ""
+
+#: ../../network_setup.rst:296
+# 0163b29a2a3449008b867ce0ac0565ee
+msgid "To achieve the above purposes you must set up fixed configurations for the firewall. Firewall rules and policies need not change as users are provisioned into the cloud. Any brand of hardware firewall that supports NAT and site-to-site VPN can be used."
+msgstr ""
+
+#: ../../network_setup.rst:302
+# 34e975339bad453b927ada8e1902b434
+msgid "External Guest Firewall Integration for Juniper SRX (Optional)"
+msgstr ""
+
+#: ../../network_setup.rst:306
+# 7ef39ebd341e403e991420097b284ba6
+msgid "Available only for guests using advanced networking."
+msgstr ""
+
+#: ../../network_setup.rst:308
+# 26f515df63cf4892b65cc70dcdae99de
+msgid "CloudStack provides for direct management of the Juniper SRX series of firewalls. This enables CloudStack to establish static NAT mappings from public IPs to guest VMs, and to use the Juniper device in place of the virtual router for firewall services. You can have one or more Juniper SRX per zone. This feature is optional. If Juniper integration is not provisioned, CloudStack will use the virtual router for these services."
+msgstr ""
+
+#: ../../network_setup.rst:315
+# 9f37f746be004ad9869e93465078a2f6
+msgid "The Juniper SRX can optionally be used in conjunction with an external load balancer. External Network elements can be deployed in a side-by-side or inline configuration."
+msgstr ""
+
+#: ../../network_setup.rst:319
+# 61a621ee3682474f8b6d9d96900381b3
+msgid "|parallel-mode.png: adding a firewall and load balancer in parallel mode.|"
+msgstr ""
+
+#: ../../network_setup.rst:322
+# d222305ce6bf40cd85c856ce92765746
+msgid "CloudStack requires the Juniper SRX firewall to be configured as follows:"
+msgstr ""
+
+#: ../../network_setup.rst:326
+# 33279c748bd24fb286cf8bb230113f5d
+msgid "Supported SRX software version is 10.3 or higher."
+msgstr ""
+
+#: ../../network_setup.rst:330
+# 4234dbbbbd71413fa29b5563600d1f53
+msgid "Install your SRX appliance according to the vendor's instructions."
+msgstr ""
+
+#: ../../network_setup.rst:334
+# 8fa0cb4c8d564cea896a72550e873ef2
+msgid "Connect one interface to the management network and one interface to the public network. Alternatively, you can connect the same interface to both networks and a use a VLAN for the public network."
+msgstr ""
+
+#: ../../network_setup.rst:340
+# 7e836a807d75421c8c4e20333ce9eb73
+msgid "Make sure \"vlan-tagging\" is enabled on the private interface."
+msgstr ""
+
+#: ../../network_setup.rst:344
+# 89a9bb9d45c8455cba1570bbaade5535
+msgid "Record the public and private interface names. If you used a VLAN for the public interface, add a \".[VLAN TAG]\" after the interface name. For example, if you are using ge-0/0/3 for your public interface and VLAN tag 301, your public interface name would be \"ge-0/0/3.301\". Your private interface name should always be untagged because the CloudStack software automatically creates tagged logical interfaces."
+msgstr ""
+
+#: ../../network_setup.rst:353
+# a55ff6dc6ebe4c809256c3c7a6faf574
+msgid "Create a public security zone and a private security zone. By default, these will already exist and will be called \"untrust\" and \"trust\". Add the public interface to the public zone and the private interface to the private zone. Note down the security zone names."
+msgstr ""
+
+#: ../../network_setup.rst:360
+# fc41753b86ec4b4b82b14557a97c597e
+msgid "Make sure there is a security policy from the private zone to the public zone that allows all traffic."
+msgstr ""
+
+#: ../../network_setup.rst:365
+# dd707a9eacd9454b92552d4f806a59ac
+msgid "Note the username and password of the account you want the CloudStack software to log in to when it is programming rules."
+msgstr ""
+
+#: ../../network_setup.rst:370
+# 566dd89d56bf4f958c4b06abfda1742a
+msgid "Make sure the \"ssh\" and \"xnm-clear-text\" system services are enabled."
+msgstr ""
+
+#: ../../network_setup.rst:374
+# ed31dae2e80f4fa39cebbd2ddfbd4a92
+msgid "If traffic metering is desired:"
+msgstr ""
+
+#: ../../network_setup.rst:378
+# c90044d70dd24e70b8a0889ab219b89a
+msgid "Create an incoming firewall filter and an outgoing firewall filter. These filters should be the same names as your public security zone name and private security zone name respectively. The filters should be set to be \"interface-specific\". For example, here is the configuration where the public zone is \"untrust\" and the private zone is \"trust\":"
+msgstr ""
+
+#: ../../network_setup.rst:397
+# 745b75f8f93f42fd9853468be609c5e3
+msgid "Add the firewall filters to your public interface. For example, a sample configuration output (for public interface ge-0/0/3.0, public security zone untrust, and private security zone trust) is:"
+msgstr ""
+
+#: ../../network_setup.rst:417
+# 146f939647114caf9debb6878ed519f6
+msgid "Make sure all VLANs are brought to the private interface of the SRX."
+msgstr ""
+
+#: ../../network_setup.rst:421
+# 4e3605c672e940e99ad5760c380280b5
+msgid "After the CloudStack Management Server is installed, log in to the CloudStack UI as administrator."
+msgstr ""
+
+#: ../../network_setup.rst:426
+#: ../../network_setup.rst:743
+#: ../../network_setup.rst:802
+#: ../../network_setup.rst:1033
+# ae1fffbd466b4cd5b4f8fbf8b9645b3c
+# ae23db054dc24e528260b2d9d35c7f87
+# e5a816ad48464365b4c9357fb4d93f53
+# 5cb19f8bf7254468a6cfa31fee6d9f17
+msgid "In the left navigation bar, click Infrastructure."
+msgstr ""
+
+#: ../../network_setup.rst:430
+#: ../../network_setup.rst:747
+#: ../../network_setup.rst:806
+#: ../../network_setup.rst:1037
+# 9f5dca40f3fd4b5aa33446dc8e1a78ea
+# 4cf51aaa2b6b4aa0901119d558215d7f
+# 138bc3ac35cb42f591d76eb703059200
+# e751b286f3b24d72b180b9a74be5c90b
+msgid "In Zones, click View More."
+msgstr ""
+
+#: ../../network_setup.rst:434
+#: ../../network_setup.rst:751
+#: ../../network_setup.rst:810
+#: ../../network_setup.rst:1041
+# de65044b14744fd1a655636ebba9d04c
+# 4426371bc34446e0a844ef2c40b6c3a4
+# 264aaeb7409c411ca7fe74f156f5e404
+# b7ba17751ec947d7a2027508413bd618
+msgid "Choose the zone you want to work with."
+msgstr ""
+
+#: ../../network_setup.rst:438
+#: ../../network_setup.rst:1045
+# c84223d0d6eb4889a79cd1134c6ee633
+# 9de0fa487b324a3b89252069d65fdde2
+msgid "Click the Network tab."
+msgstr ""
+
+#: ../../network_setup.rst:442
+#: ../../network_setup.rst:1049
+# 6a84775802d645af9607c2e647825d40
+# 8afb473c71264f8db58d3313895dc9de
+msgid "In the Network Service Providers node of the diagram, click Configure. (You might have to scroll down to see this.)"
+msgstr ""
+
+#: ../../network_setup.rst:447
+# f9985e8b79a74855a02bc63dd83adba2
+msgid "Click SRX."
+msgstr ""
+
+#: ../../network_setup.rst:451
+# c69fcde003714f2ab79347099374920e
+msgid "Click the Add New SRX button (+) and provide the following:"
+msgstr ""
+
+#: ../../network_setup.rst:455
+#: ../../network_setup.rst:1064
+# d2f18f76f7be4e4e8914ec1242146eaa
+# 2388d27c72ba412b9d6f1023b1a7010e
+msgid "IP Address: The IP address of the SRX."
+msgstr ""
+
+#: ../../network_setup.rst:459
+# 8b42fcb9dd124154b97cfa14b72ea1da
+msgid "Username: The user name of the account on the SRX that CloudStack should use."
+msgstr ""
+
+#: ../../network_setup.rst:464
+#: ../../network_setup.rst:787
+# 24c3b92795034ba49f5f240cf9515374
+# 9a706efead294f20ba443bae76ad953a
+msgid "Password: The password of the account."
+msgstr ""
+
+#: ../../network_setup.rst:468
+# e0712b834c9a49239a2e71d4fe93051b
+msgid "Public Interface. The name of the public interface on the SRX. For example, ge-0/0/2. A \".x\" at the end of the interface indicates the VLAN that is in use."
+msgstr ""
+
+#: ../../network_setup.rst:474
+# 3a32a36db9c14830bf7fa21a781c66b0
+msgid "Private Interface: The name of the private interface on the SRX. For example, ge-0/0/1."
+msgstr ""
+
+#: ../../network_setup.rst:479
+# a57513d127974a12b36fec2f5e83c2d7
+msgid "Usage Interface: (Optional) Typically, the public interface is used to meter traffic. If you want to use a different interface, specify its name here"
+msgstr ""
+
+#: ../../network_setup.rst:485
+# 406cb60bc9764b3b9a99908cf6a6df06
+msgid "Number of Retries: The number of times to attempt a command on the SRX before failing. The default value is 2."
+msgstr ""
+
+#: ../../network_setup.rst:490
+# 97e6060d32bb46cda2cb9d0abf73f33f
+msgid "Timeout (seconds): The time to wait for a command on the SRX before considering it failed. Default is 300 seconds."
+msgstr ""
+
+#: ../../network_setup.rst:495
+# 81d96516beb54b17a2902f3ce21fb857
+msgid "Public Network: The name of the public network on the SRX. For example, trust."
+msgstr ""
+
+#: ../../network_setup.rst:500
+# e294fb3485eb4089b6d61ccd0f4fb8e2
+msgid "Private Network: The name of the private network on the SRX. For example, untrust."
+msgstr ""
+
+#: ../../network_setup.rst:505
+# b797dba069484a79adc9589918ec7c71
+msgid "Capacity: The number of networks the device can handle"
+msgstr ""
+
+#: ../../network_setup.rst:509
+# 725e061a6426459caf75e1797c5e3d2f
+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 ""
+
+#: ../../network_setup.rst:515
+#: ../../network_setup.rst:791
+#: ../../network_setup.rst:854
+#: ../../network_setup.rst:1105
+# 2ffb4f8956c1455493d8ba2615ccef21
+# 8bdc57b75b084c49abd55cfa3aa4c461
+# 73c7a7c1e73a4a7e9efa7ac80a43a2d6
+# 2845611bf8ed49d59c438ca261a2b542
+msgid "Click OK."
+msgstr ""
+
+#: ../../network_setup.rst:519
+# 3d95a0ac1f5047f98762b2e375ecd105
+msgid "Click Global Settings. Set the parameter external.network.stats.interval to indicate how often you want CloudStack to fetch network usage statistics from the Juniper SRX. If you are not using the SRX to gather network usage statistics, set to 0."
+msgstr ""
+
+#: ../../network_setup.rst:526
+# c231178a955f4207913ececa53bee4f9
+msgid "External Guest Firewall Integration for Cisco VNMC (Optional)"
+msgstr ""
+
+#: ../../network_setup.rst:528
+# 7ddb13c16c594e2cb97bb4ba91cb9f5b
+msgid "Cisco Virtual Network Management Center (VNMC) provides centralized multi-device and policy management for Cisco Network Virtual Services. You can integrate Cisco VNMC with CloudStack to leverage the firewall and NAT service offered by ASA 1000v Cloud Firewall. Use it in a Cisco Nexus 1000v dvSwitch-enabled cluster in CloudStack. In such a deployment, you will be able to:"
+msgstr ""
+
+#: ../../network_setup.rst:537
+# e7a5392625c243e680f304852391be28
+msgid "Configure Cisco ASA 1000v firewalls. You can configure one per guest network."
+msgstr ""
+
+#: ../../network_setup.rst:542
+# 7a564af5923e4a968086c540c738578a
+msgid "Use Cisco ASA 1000v firewalls to create and apply security profiles that contain ACL policy sets for both ingress and egress traffic."
+msgstr ""
+
+#: ../../network_setup.rst:547
+# 8371cdb35f4640deaf2f5c236cddc61e
+msgid "Use Cisco ASA 1000v firewalls to create and apply Source NAT, Port Forwarding, and Static NAT policy sets."
+msgstr ""
+
+#: ../../network_setup.rst:550
+# d5e7738eaf324d22a9ace729dec0c88a
+msgid "CloudStack supports Cisco VNMC on Cisco Nexus 1000v dvSwich-enabled VMware hypervisors."
+msgstr ""
+
+#: ../../network_setup.rst:554
+# f14bc561643f4f66a0e2abb3bdb98d3e
+msgid "Using Cisco ASA 1000v Firewall, Cisco Nexus 1000v dvSwitch, and Cisco VNMC in a Deployment"
+msgstr ""
+
+#: ../../network_setup.rst:557
+# b368057bd8f24ab99f82b52430b1ecc7
+msgid "Guidelines"
+msgstr ""
+
+#: ../../network_setup.rst:561
+# 4f3bafb81fc448f091dbcb3d582fc81e
+msgid "Cisco ASA 1000v firewall is supported only in Isolated Guest Networks."
+msgstr ""
+
+#: ../../network_setup.rst:566
+# 0d4c08f71c1c40819a64bdf88478b275
+msgid "Cisco ASA 1000v firewall is not supported on VPC."
+msgstr ""
+
+#: ../../network_setup.rst:570
+# a9e4fbac68c64f799b93d744713c6121
+msgid "Cisco ASA 1000v firewall is not supported for load balancing."
+msgstr ""
+
+#: ../../network_setup.rst:574
+# f9f2fd0e77764cb0af893106ac5a2a7e
+msgid "When a guest network is created with Cisco VNMC firewall provider, an additional public IP is acquired along with the Source NAT IP. The Source NAT IP is used for the rules, whereas the additional IP is used to for the ASA outside interface. Ensure that this additional public IP is not released. You can identify this IP as soon as the network is in implemented state and before acquiring any further public IPs. The additional IP is the one that is not marked as Source NAT. You can find the IP used for the ASA outside interface by looking at the Cisco VNMC used in your guest network."
+msgstr ""
+
+#: ../../network_setup.rst:586
+# a2096b8adf6c4d49af83da25561f3875
+msgid "Use the public IP address range from a single subnet. You cannot add IP addresses from different subnets."
+msgstr ""
+
+#: ../../network_setup.rst:591
+# 0771f4bd2f9a43959b94758a937cca5e
+msgid "Only one ASA instance per VLAN is allowed because multiple VLANS cannot be trunked to ASA ports. Therefore, you can use only one ASA instance in a guest network."
+msgstr ""
+
+#: ../../network_setup.rst:597
+# 8d9f9ee56667428ba6117d2114daf7b4
+msgid "Only one Cisco VNMC per zone is allowed."
+msgstr ""
+
+#: ../../network_setup.rst:601
+# e0fd9954d8f0439ca8ca206c92f4e4c3
+msgid "Supported only in Inline mode deployment with load balancer."
+msgstr ""
+
+#: ../../network_setup.rst:605
+# 6ce782eac5b84921842db76a08044e4a
+msgid "The ASA firewall rule is applicable to all the public IPs in the guest network. Unlike the firewall rules created on virtual router, a rule created on the ASA device is not tied to a specific public IP."
+msgstr ""
+
+#: ../../network_setup.rst:611
+# 878d4699ef8343828117e00f9af62701
+msgid "Use a version of Cisco Nexus 1000v dvSwitch that support the vservice command. For example: nexus-1000v.4.2.1.SV1.5.2b.bin"
+msgstr ""
+
+#: ../../network_setup.rst:614
+# cb00c11a6016419b9a93fba46c80a39f
+msgid "Cisco VNMC requires the vservice command to be available on the Nexus switch to create a guest network in CloudStack."
+msgstr ""
+
+#: ../../network_setup.rst:618
+# 6730f26a26bd4708b8823298a0356b1c
+msgid "Prerequisites"
+msgstr ""
+
+#: ../../network_setup.rst:622
+# 833f606f702a44a78fcd8e7d8950fb78
+msgid "Configure Cisco Nexus 1000v dvSwitch in a vCenter environment."
+msgstr ""
+
+#: ../../network_setup.rst:624
+# b9b3441290284f6e924c0ef75077dc10
+msgid "Create Port profiles for both internal and external network interfaces on Cisco Nexus 1000v dvSwitch. Note down the inside port profile, which needs to be provided while adding the ASA appliance to CloudStack."
+msgstr ""
+
+#: ../../network_setup.rst:629
+# 725c5f44ccd74323a75660b46f0bfdd5
+msgid "For information on configuration, see `“Configuring a vSphere Cluster with Nexus 1000v Virtual Switch” <hypervisor_installation.html#configuring-a-vsphere-cluster-with-nexus-1000v-virtual-switch>`_."
+msgstr ""
+
+#: ../../network_setup.rst:634
+# ac60d4b57fc140558392ccffc754f4d4
+msgid "Deploy and configure Cisco VNMC."
+msgstr ""
+
+#: ../../network_setup.rst:636
+# 2c5d754fbd644d6196d8dc6fcb572a9e
+msgid "For more information, see `Installing Cisco Virtual Network Management Center <http://www.cisco.com/en/US/docs/switches/datacenter/vsg/sw/4_2_1_VSG_2_1_1/install_upgrade/guide/b_Cisco_VSG_for_VMware_vSphere_Rel_4_2_1_VSG_2_1_1_and_Cisco_VNMC_Rel_2_1_Installation_and_Upgrade_Guide_chapter_011.html>`_ and `Configuring Cisco Virtual Network Management Center <http://www.cisco.com/en/US/docs/unified_computing/vnmc/sw/1.2/VNMC_GUI_Configuration/b_VNMC_GUI_Configuration_Guide_1_2_chapter_010.html>`_."
+msgstr ""
+
+#: ../../network_setup.rst:641
+# 33cee7c6bf9545908374ee9fd56e563d
+msgid "Register Cisco Nexus 1000v dvSwitch with Cisco VNMC."
+msgstr ""
+
+#: ../../network_setup.rst:643
+# 49e2f38096524c12941a8b94b64e3cbc
+msgid "For more information, see `Registering a Cisco Nexus 1000V with Cisco VNMC <http://www.cisco.com/en/US/docs/switches/datacenter/vsg/sw/4_2_1_VSG_1_2/vnmc_and_vsg_qi/guide/vnmc_vsg_install_5register.html#wp1064301>`_."
+msgstr ""
+
+#: ../../network_setup.rst:648
+# eb70a80e7e4a4a4199e014d7dde29e30
+msgid "Create Inside and Outside port profiles in Cisco Nexus 1000v dvSwitch."
+msgstr ""
+
+#: ../../network_setup.rst:651
+# 6816f3becfb5443a93c615aafae556dd
+msgid "For more information, see `“Configuring a vSphere Cluster with Nexus 1000v Virtual Switch” <hypervisor_installation.html#configuring-a-vsphere-cluster-with-nexus-1000v-virtual-switch>`_."
+msgstr ""
+
+#: ../../network_setup.rst:655
+# d452726321994e95b894e93a4ed80284
+msgid "Deploy and Cisco ASA 1000v appliance."
+msgstr ""
+
+#: ../../network_setup.rst:657
+# 60d9d946998e4fcdba7d84b3a2a74806
+msgid "For more information, see `Setting Up the ASA 1000V Using VNMC <http://www.cisco.com/en/US/docs/security/asa/quick_start/asa1000V/setup_vnmc.html>`_."
+msgstr ""
+
+#: ../../network_setup.rst:659
+# 9f879b1974bf463b99d07f251ac8c9f1
+msgid "Typically, you create a pool of ASA 1000v appliances and register them with CloudStack."
+msgstr ""
+
+#: ../../network_setup.rst:662
+# 89a83288031a4ed681c786256d804b98
+msgid "Specify the following while setting up a Cisco ASA 1000v instance:"
+msgstr ""
+
+#: ../../network_setup.rst:666
+# 5866bc6ab1bb44d6930086d8df496e20
+msgid "VNMC host IP."
+msgstr ""
+
+#: ../../network_setup.rst:670
+# 8849d70ea945435c87ed8566e212f2f7
+msgid "Ensure that you add ASA appliance in VNMC mode."
+msgstr ""
+
+#: ../../network_setup.rst:674
+# dfbd56bf8dc14245855c7b0a81f8adfd
+msgid "Port profiles for the Management and HA network interfaces. This need to be pre-created on Cisco Nexus 1000v dvSwitch."
+msgstr ""
+
+#: ../../network_setup.rst:679
+# 5602a5bfbd9f4393962a9aef3bf2d87d
+msgid "Internal and external port profiles."
+msgstr ""
+
+#: ../../network_setup.rst:683
+# 86f08e2f599148f68fda8a1c8526e125
+msgid "The Management IP for Cisco ASA 1000v appliance. Specify the gateway such that the VNMC IP is reachable."
+msgstr ""
+
+#: ../../network_setup.rst:688
+# 9959e4f977e74e32919025fbcd616e30
+msgid "Administrator credentials"
+msgstr ""
+
+#: ../../network_setup.rst:692
+# 744878dbc4fc41c296198d54a65ba481
+msgid "VNMC credentials"
+msgstr ""
+
+#: ../../network_setup.rst:696
+# f3bdb9d21f4c4ef78859b5469ebccd25
+msgid "Register Cisco ASA 1000v with VNMC."
+msgstr ""
+
+#: ../../network_setup.rst:698
+# 879024b1fdd44637af8f1f3447152daf
+msgid "After Cisco ASA 1000v instance is powered on, register VNMC from the ASA console."
+msgstr ""
+
+#: ../../network_setup.rst:702
+# fb08e857c313421ba7f0f0fc2a961739
+msgid "Using Cisco ASA 1000v Services"
+msgstr ""
+
+#: ../../network_setup.rst:706
+# 0b9f634819c5486d956f8a10a96bcbae
+msgid "Ensure that all the prerequisites are met."
+msgstr ""
+
+#: ../../network_setup.rst:708
+# 0ba06b8d21324aed90acdb495d56cb93
+msgid "See `“Prerequisites” <#prerequisites>`_."
+msgstr ""
+
+#: ../../network_setup.rst:712
+# 6331688e133b41ec907beeaee4be7c47
+msgid "Add a VNMC instance."
+msgstr ""
+
+#: ../../network_setup.rst:714
+# 128113d285044dc992ad8d74376d7c97
+msgid "See `“Adding a VNMC Instance” <#adding-a-vnmc-instance>`_."
+msgstr ""
+
+#: ../../network_setup.rst:718
+# 261faa004f6845d7b99abe9f6e978f70
+msgid "Add a ASA 1000v instance."
+msgstr ""
+
+#: ../../network_setup.rst:720
+# 313e1e8e99a04fa49de774f12841c9d4
+msgid "See `“Adding an ASA 1000v Instance” <#adding-an-asa-1000v-instance>`_."
+msgstr ""
+
+#: ../../network_setup.rst:724
+# 2daa62e2624d48448cab1e759a7ff734
+msgid "Create a Network Offering and use Cisco VNMC as the service provider for desired services."
+msgstr ""
+
+#: ../../network_setup.rst:727
+# 095b04ca794b4d45ae3579b6c2e30b70
+msgid "See `“Creating a Network Offering Using Cisco ASA 1000v” <#creating-a-network-offering-using-cisco-asa-1000v>`_."
+msgstr ""
+
+#: ../../network_setup.rst:731
+# bb596e7d870844859604fb2636fdb45b
+msgid "Create an Isolated Guest Network by using the network offering you just created."
+msgstr ""
+
+#: ../../network_setup.rst:735
+# f909afe140884951824cc8af81a646f3
+msgid "Adding a VNMC Instance"
+msgstr ""
+
+#: ../../network_setup.rst:739
+#: ../../network_setup.rst:798
+#: ../../network_setup.rst:1291
+# 2a23cbce41f345e0aec7d6db622c0c46
+# a0a583e2b36e478d8eabce5113e5b7bd
+# 7ea11e195a2a4f19aa32d7c9a7e85d62
+msgid "Log in to the CloudStack UI as administrator."
+msgstr ""
+
+#: ../../network_setup.rst:755
+#: ../../network_setup.rst:814
+# 590c34870a534e5a945ef859f88447ca
+# 1c39a3cef5144be296a63acf4fa409ec
+msgid "Click the Physical Network tab."
+msgstr ""
+
+#: ../../network_setup.rst:759
+#: ../../network_setup.rst:818
+# c060248b043942599325a7e9e2cc3a32
+# 432b64e9f1254ee0a8d28c29e4cd59f9
+msgid "In the Network Service Providers node of the diagram, click Configure."
+msgstr ""
+
+#: ../../network_setup.rst:762
+#: ../../network_setup.rst:821
+# 567df3c29fd34320820c2ff93d255f9c
+# 3563fe4e08f3418aac963792df62408c
+msgid "You might have to scroll down to see this."
+msgstr ""
+
+#: ../../network_setup.rst:766
+#: ../../network_setup.rst:825
+# fe0ad75aa2324345909fe5123d894e7e
+# 39d89907aff94555abd93cf614542e2e
+msgid "Click Cisco VNMC."
+msgstr ""
+
+#: ../../network_setup.rst:770
+# f4d2612c13954f509738352b195ec590
+msgid "Click View VNMC Devices."
+msgstr ""
+
+#: ../../network_setup.rst:774
+# 280a671674694f8b9ddb6f78d2738bb4
+msgid "Click the Add VNMC Device and provide the following:"
+msgstr ""
+
+#: ../../network_setup.rst:778
+# b6960cf1621343a6bb5bc6c018b688b9
+msgid "Host: The IP address of the VNMC instance."
+msgstr ""
+
+#: ../../network_setup.rst:782
+# b561e3a09023491bbbaf24ae333eda26
+msgid "Username: The user name of the account on the VNMC instance that CloudStack should use."
+msgstr ""
+
+#: ../../network_setup.rst:794
+# a5549d2809bb4c85a07596b4519e145b
+msgid "Adding an ASA 1000v Instance"
+msgstr ""
+
+#: ../../network_setup.rst:829
+# 652419f55d024d92ae3d5b4429f47502
+msgid "Click View ASA 1000v."
+msgstr ""
+
+#: ../../network_setup.rst:833
+# 520764a117b54a54895f7418b5dd6bd9
+msgid "Click the Add CiscoASA1000v Resource and provide the following:"
+msgstr ""
+
+#: ../../network_setup.rst:837
+# 041d3eea38ef4a91be6165d2e1b80540
+msgid "**Host**: The management IP address of the ASA 1000v instance. The IP address is used to connect to ASA 1000V."
+msgstr ""
+
+#: ../../network_setup.rst:842
+# 0b4fca9e3a554236b68fb63674fd2d2b
+msgid "**Inside Port Profile**: The Inside Port Profile configured on Cisco Nexus1000v dvSwitch."
+msgstr ""
+
+#: ../../network_setup.rst:847
+# 9c45084e5ed1456d90d117c7c8e7d325
+msgid "**Cluster**: The VMware cluster to which you are adding the ASA 1000v instance."
+msgstr ""
+
+#: ../../network_setup.rst:850
+# d12959be285b4c84a0664a08dc2b0e3a
+msgid "Ensure that the cluster is Cisco Nexus 1000v dvSwitch enabled."
+msgstr ""
+
+#: ../../network_setup.rst:857
+# 7e7a81b8c6e54bb8999755a49231aa40
+msgid "Creating a Network Offering Using Cisco ASA 1000v"
+msgstr ""
+
+#: ../../network_setup.rst:859
+# a728035550724e399b8d655332a2af43
+msgid "To have Cisco ASA 1000v support for a guest network, create a network offering as follows:"
+msgstr ""
+
+#: ../../network_setup.rst:864
+# 235592f79aeb4e7383f891670812bd62
+msgid "Log in to the CloudStack UI as a user or admin."
+msgstr ""
+
+#: ../../network_setup.rst:868
+# 98ec5c8085be4e22a62453cec3e727c6
+msgid "From the Select Offering drop-down, choose Network Offering."
+msgstr ""
+
+#: ../../network_setup.rst:872
+# 76ed883fe42148418fd05640db3307c7
+msgid "Click Add Network Offering."
+msgstr ""
+
+#: ../../network_setup.rst:876
+# 4078b28dde3b4492a875088625396f69
+msgid "In the dialog, make the following choices:"
+msgstr ""
+
+#: ../../network_setup.rst:880
+# 7a66dd4ce7ac4236a39b3f9bbb2f0e70
+msgid "**Name**: Any desired name for the network offering."
+msgstr ""
+
+#: ../../network_setup.rst:884
+# b21556cf7ba24206984a62e49d577298
+msgid "**Description**: A short description of the offering that can be displayed to users."
+msgstr ""
+
+#: ../../network_setup.rst:889
+# fc650ab9838541d1acccaa8f1bb17428
+msgid "**Network Rate**: Allowed data transfer rate in MB per second."
+msgstr ""
+
+#: ../../network_setup.rst:893
+# f4657f2c370e443dba748ed97ef09101
+msgid "**Traffic Type**: The type of network traffic that will be carried on the network."
+msgstr ""
+
+#: ../../network_setup.rst:898
+# 309bc092f3c9493fa9cd9cc008e9abc9
+msgid "**Guest Type**: Choose whether the guest network is isolated or shared."
+msgstr ""
+
+#: ../../network_setup.rst:903
+# 2092b89e8fd347d3a5975560c6fd8a0f
+msgid "**Persistent**: Indicate whether the guest network is persistent or not. The network that you can provision without having to deploy a VM on it is termed persistent network."
+msgstr ""
+
+#: ../../network_setup.rst:909
+# 225d614ca62f4655b3c22dfda3bcaee7
+msgid "**VPC**: This option indicate whether the guest network is Virtual Private Cloud-enabled. A Virtual Private Cloud (VPC) is a private, isolated part of CloudStack. A VPC can have its own virtual network topology that resembles a traditional physical network. For more information on VPCs, see `“About Virtual Private Clouds” <http://docs.cloudstack.apache.org/projects/cloudstack-administration/en/latest/networking2.html#about-virtual-private-clouds>`_."
+msgstr ""
+
+#: ../../network_setup.rst:917
+# c4d68e7e8c4a485f83a21c1dd68ed9a4
+msgid "**Specify VLAN**: (Isolated guest networks only) Indicate whether a VLAN should be specified when this offering is used."
+msgstr ""
+
+#: ../../network_setup.rst:922
+# 5fcda08e554749d19c354928ac2dc001
+msgid "**Supported Services**: Use Cisco VNMC as the service provider for Firewall, Source NAT, Port Forwarding, and Static NAT to create an Isolated guest network offering."
+msgstr ""
+
+#: ../../network_setup.rst:928
+# 49f6135884b942aca975f5701dcadd9a
+msgid "**System Offering**: Choose the system service offering that you want virtual routers to use in this network."
+msgstr ""
+
+#: ../../network_setup.rst:933
+# 5f37d9b817f84e2d8198ba57a204cace
+msgid "**Conserve mode**: Indicate whether to use conserve mode. In this mode, network resources are allocated only when the first virtual machine starts in the network."
+msgstr ""
+
+#: ../../network_setup.rst:939
+# e87bb070ce554c3d960e91c209213466
+msgid "Click OK"
+msgstr ""
+
+#: ../../network_setup.rst:941
+# 084e3bb8d5a6446f83249cfda489a99a
+msgid "The network offering is created."
+msgstr ""
+
+#: ../../network_setup.rst:944
+# e4503c403ad04eb297f958acd216ce6f
+msgid "Reusing ASA 1000v Appliance in new Guest Networks"
+msgstr ""
+
+#: ../../network_setup.rst:946
+# 92977871fbe94256a46223390b9acb5b
+msgid "You can reuse an ASA 1000v appliance in a new guest network after the necessary cleanup. Typically, ASA 1000v is cleaned up when the logical edge firewall is cleaned up in VNMC. If this cleanup does not happen, you need to reset the appliance to its factory settings for use in new guest networks. As part of this, enable SSH on the appliance and store the SSH credentials by registering on VNMC."
+msgstr ""
+
+#: ../../network_setup.rst:955
+# bc3df2195a414e91856ec648bac7c773
+msgid "Open a command line on the ASA appliance:"
+msgstr ""
+
+#: ../../network_setup.rst:959
+# 218ea4c549694ff7a29509f5cac2e0bc
+msgid "Run the following:"
+msgstr ""
+
+#: ../../network_setup.rst:965
+# 5fd5c2e1e3904eb88b09772395d5b3f0
+msgid "You are prompted with the following message:"
+msgstr ""
+
+#: ../../network_setup.rst:973
+# 6c28078f7e6747bea7924b1c0881e9d9
+msgid "Enter N."
+msgstr ""
+
+#: ../../network_setup.rst:975
+# 9692793acd9f47cda86a9f9a97d7292f
+msgid "You will get the following confirmation message:"
+msgstr ""
+
+#: ../../network_setup.rst:983
+# 280c0bb28bc4480f8fd348cd126043e7
+msgid "Restart the appliance."
+msgstr ""
+
+#: ../../network_setup.rst:987
+# 2a1aec5da1b8471991fe9aafe3416bda
+msgid "Register the ASA 1000v appliance with the VNMC:"
+msgstr ""
+
+#: ../../network_setup.rst:996
+# 5c9054e0fc1e4d4ab5c8358e24833971
+msgid "External Guest Load Balancer Integration (Optional)"
+msgstr ""
+
+#: ../../network_setup.rst:998
+# fd1ea0e7750e431db79221a8c2311a7d
+msgid "CloudStack can optionally use a Citrix NetScaler or BigIP F5 load balancer to provide load balancing services to guests. If this is not enabled, CloudStack will use the software load balancer in the virtual router."
+msgstr ""
+
+#: ../../network_setup.rst:1003
+# 500154d717eb49c2bf29ab754aac709e
+msgid "To install and enable an external load balancer for CloudStack management:"
+msgstr ""
+
+#: ../../network_setup.rst:1008
+# f106290730db48ab949e8470dc2d856e
+msgid "Set up the appliance according to the vendor's directions."
+msgstr ""
+
+#: ../../network_setup.rst:1012
+# f94e5fdf650149139445886199c2d172
+msgid "Connect it to the networks carrying public traffic and management traffic (these could be the same network)."
+msgstr ""
+
+#: ../../network_setup.rst:1017
+# b8ac2d65fdcc4f3db0ea4a915ff5b0eb
+msgid "Record the IP address, username, password, public interface name, and private interface name. The interface names will be something like \"1.1\" or \"1.2\"."
+msgstr ""
+
+#: ../../network_setup.rst:1023
+# 0b3869ded9b7422aa5f56c61b2413e59
+msgid "Make sure that the VLANs are trunked to the management network interface."
+msgstr ""
+
+#: ../../network_setup.rst:1028
+# f5346391b7bf4ccb928f72947d5e37a7
+msgid "After the CloudStack Management Server is installed, log in as administrator to the CloudStack UI."
+msgstr ""
+
+#: ../../network_setup.rst:1054
+# 084625b55cef4b809b077485d04d3391
+msgid "Click NetScaler or F5."
+msgstr ""
+
+#: ../../network_setup.rst:1058
+# 9a5b17fecfa444e29fc91af0fe5e33ba
+msgid "Click the Add button (+) and provide the following:"
+msgstr ""
+
+#: ../../network_setup.rst:1060
+# ef4b3be155c546a79fcbcd4cbfbd1593
+msgid "For NetScaler:"
+msgstr ""
+
+#: ../../network_setup.rst:1068
+# 093492ed293a4dffb1f9348f05034957
+msgid "Username/Password: The authentication credentials to access the device. CloudStack uses these credentials to access the device."
+msgstr ""
+
+#: ../../network_setup.rst:1073
+# 35e04124f1c84f9a9014277a8436ea1b
+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 ""
+
+#: ../../network_setup.rst:1080
+# 125bf77b1db34aeb9e24de050a111841
+msgid "Public interface: Interface of device that is configured to be part of the public network."
+msgstr ""
+
+#: ../../network_setup.rst:1085
+# 7492cd89866b40738540cef8209f9050
+msgid "Private interface: Interface of device that is configured to be part of the private network."
+msgstr ""
+
+#: ../../network_setup.rst:1090
+# 1c3be655ebce444ebb35d687bd3ff069
+msgid "Number of retries. Number of times to attempt a command on the device before considering the operation failed. Default is 2."
+msgstr ""
+
+#: ../../network_setup.rst:1095
+# 307e5a4cc2834d19952438496c0da6f7
+msgid "Capacity: The number of networks the device can handle."
+msgstr ""
+
+#: ../../network_setup.rst:1099
+# c8c3a218340c449fbd05e1d3b426c43a
+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 ""
+
+#: ../../network_setup.rst:1107
+# 1c2067e8634f49f486df0443089a7510
+msgid "The installation and provisioning of the external load balancer is finished. You can proceed to add VMs and NAT or load balancing rules."
+msgstr ""
+
+#: ../../network_setup.rst:1111
+# f74795a8b76c478d9ea49f4c060b6e36
+msgid "Management Server Load Balancing"
+msgstr ""
+
+#: ../../network_setup.rst:1113
+# 567c8073631a4c8bb2dce7c8fe752e4a
+msgid "CloudStack can use a load balancer to provide a virtual IP for multiple Management Servers. The administrator is responsible for creating the load balancer rules for the Management Servers. The application requires persistence or stickiness across multiple sessions. The following chart lists the ports that should be load balanced and whether or not persistence is required."
+msgstr ""
+
+#: ../../network_setup.rst:1120
+# bdb7cdf9792847f984a0461c157fe9f0
+msgid "Even if persistence is not required, enabling it is permitted."
+msgstr ""
+
+#: ../../network_setup.rst:1123
+# fd11840af0204f4293065802c1bcccf9
+msgid "Source Port"
+msgstr ""
+
+#: ../../network_setup.rst:1123
+# b95414a68a464ac3b2b8998460985411
+msgid "Destination Port"
+msgstr ""
+
+#: ../../network_setup.rst:1123
+# f27e6cea2a374e5b8bee0385f48b133c
+msgid "Protocol"
+msgstr ""
+
+#: ../../network_setup.rst:1123
+# 74c3d26966da4578890e32fc1938ae45
+msgid "Persistence Required?"
+msgstr ""
+
+#: ../../network_setup.rst:1125
+# 5df8fb1b300a4a30bb5af7c3c022186c
+msgid "80 or 443"
+msgstr ""
+
+#: ../../network_setup.rst:1125
+# cfc3fe326a0b45849284ca3774c5bcc3
+msgid "8080 (or 20400 with AJP)"
+msgstr ""
+
+#: ../../network_setup.rst:1125
+# e6aad1fb7769468c89576963db456c40
+msgid "HTTP (or AJP)"
+msgstr ""
+
+#: ../../network_setup.rst:1126
+#: ../../network_setup.rst:1126
+# 3a50879507514c51b3b69b1239f9720e
+# cd98da983e9b4cbbbef65bf4f3c1f453
+msgid "8250"
+msgstr ""
+
+#: ../../network_setup.rst:1126
+# f31a7253ecbf4f8b8f0b467c90d93195
+msgid "TCP"
+msgstr ""
+
+#: ../../network_setup.rst:1127
+#: ../../network_setup.rst:1127
+# ad1ef2da5345401e903c332d03a11bce
+# 2226f8a516af49218d52bbafa3dc3aac
+msgid "8096"
+msgstr ""
+
+#: ../../network_setup.rst:1127
+# 2b4aac1cece94d9f83afac06a8691511
+msgid "HTTP"
+msgstr ""
+
+#: ../../network_setup.rst:1130
+# 8491425f0b824c7e981c775d2cf7d808
+msgid "In addition to above settings, the administrator is responsible for setting the 'host' global config value from the management server IP to load balancer virtual IP address. If the 'host' value is not set to the VIP for Port 8250 and one of your management servers crashes, the UI is still available but the system VMs will not be able to contact the management server."
+msgstr ""
+
+#: ../../network_setup.rst:1138
+# 8059024b96f142b6979773cf9a881160
+msgid "Topology Requirements"
+msgstr ""
+
+#: ../../network_setup.rst:1141
+# 1444ad07190f4460a7fdff1373746484
+msgid "Security Requirements"
+msgstr ""
+
+#: ../../network_setup.rst:1143
+# 3541b17430cb43478301bc2645bf3ef0
+msgid "The public Internet must not be able to access port 8096 or port 8250 on the Management Server."
+msgstr ""
+
+#: ../../network_setup.rst:1147
+# 26e78d2085514147ace9f9b5739c1ad2
+msgid "Runtime Internal Communications Requirements"
+msgstr ""
+
+#: ../../network_setup.rst:1151
+# 9d906e5688de466c958551a87dfd7022
+msgid "The Management Servers communicate with each other to coordinate tasks. This communication uses TCP on ports 8250 and 9090."
+msgstr ""
+
+#: ../../network_setup.rst:1156
+# c0d02534268a4b8e8b82947625533220
+msgid "The console proxy VMs connect to all hosts in the zone over the management traffic network. Therefore the management traffic network of any given pod in the zone must have connectivity to the management traffic network of all other pods in the zone."
+msgstr ""
+
+#: ../../network_setup.rst:1163
+# 87c002406b9244db973ff2af601d4d3f
+msgid "The secondary storage VMs and console proxy VMs connect to the Management Server on port 8250. If you are using multiple Management Servers, the load balanced IP address of the Management Servers on port 8250 must be reachable."
+msgstr ""
+
+#: ../../network_setup.rst:1169
+# fc264ff1cd454696acb03d2a67cf1204
+msgid "Storage Network Topology Requirements"
+msgstr ""
+
+#: ../../network_setup.rst:1171
+# 7caa6a59f43e4f0aa83e30390b6947f2
+msgid "The secondary storage NFS export is mounted by the secondary storage VM. Secondary storage traffic goes over the management traffic network, even if there is a separate storage network. Primary storage traffic goes over the storage network, if available. If you choose to place secondary storage NFS servers on the storage network, you must make sure there is a route from the management traffic network to the storage network."
+msgstr ""
+
+#: ../../network_setup.rst:1179
+# e72bba93eaa14fdf947c0501e8bb7590
+msgid "External Firewall Topology Requirements"
+msgstr ""
+
+#: ../../network_setup.rst:1181
+# b0ccd394990143109db9ea289077b2e6
+msgid "When external firewall integration is in place, the public IP VLAN must still be trunked to the Hosts. This is required to support the Secondary Storage VM and Console Proxy VM."
+msgstr ""
+
+#: ../../network_setup.rst:1186
+# 489888eb893c4b1ea88c545c6dade949
+msgid "Advanced Zone Topology Requirements"
+msgstr ""
+
+#: ../../network_setup.rst:1188
+# df77e9811db846f19b0ec3a162674d73
+msgid "With Advanced Networking, separate subnets must be used for private and public networks."
+msgstr ""
+
+#: ../../network_setup.rst:1192
+# 74d3a2eeb37f4d9b9ba84edadf66308a
+msgid "XenServer Topology Requirements"
+msgstr ""
+
+#: ../../network_setup.rst:1194
+# 7797b308cc694dbbb00aee3b0d39a14b
+msgid "The Management Servers communicate with XenServer hosts on ports 22 (ssh), 80 (HTTP), and 443 (HTTPs)."
+msgstr ""
+
+#: ../../network_setup.rst:1198
+# 379eac757de546b79a41a33e570544c9
+msgid "VMware Topology Requirements"
+msgstr ""
+
+#: ../../network_setup.rst:1202
+# 1eade57499624926ac28b320d66fdaf3
+msgid "The Management Server and secondary storage VMs must be able to access vCenter and all ESXi hosts in the zone. To allow the necessary access through the firewall, keep port 443 open."
+msgstr ""
+
+#: ../../network_setup.rst:1208
+# d447b402ae754cfdbd9234aefca1387a
+msgid "The Management Servers communicate with VMware vCenter servers on port 443 (HTTPs)."
+msgstr ""
+
+#: ../../network_setup.rst:1213
+# c3f02a4d30f6482cb8ce88a07befb5ce
+msgid "The Management Servers communicate with the System VMs on port 3922 (ssh) on the management traffic network."
+msgstr ""
+
+#: ../../network_setup.rst:1217
+# 02a932a851ff4b0a83c3c2cd5ab14cfd
+msgid "Hyper-V Topology Requirements"
+msgstr ""
+
+#: ../../network_setup.rst:1219
+# 3fd21dfedf3f4f63834b79c2148cf126
+msgid "CloudStack Management Server communicates with Hyper-V Agent by using HTTPS. For secure communication between the Management Server and the Hyper-V host, open port 8250."
+msgstr ""
+
+#: ../../network_setup.rst:1224
+# 75e24f91bbe745ac9623aa07acd5647c
+msgid "KVM Topology Requirements"
+msgstr ""
+
+#: ../../network_setup.rst:1226
+# 93272304ea934d4fa5f48f7e4abda8be
+msgid "The Management Servers communicate with KVM hosts on port 22 (ssh)."
+msgstr ""
+
+#: ../../network_setup.rst:1229
+# 6d0b050ccfd846c2afb6c9c27210badc
+msgid "LXC Topology Requirements"
+msgstr ""
+
+#: ../../network_setup.rst:1231
+# 0e6f6a206fd14d2d852be83058b0ba7b
+msgid "The Management Servers communicate with LXC hosts on port 22 (ssh)."
+msgstr ""
+
+#: ../../network_setup.rst:1234
+# 1a03b92103ea4a0495946df31bd6964b
+msgid "Guest Network Usage Integration for Traffic Sentinel"
+msgstr ""
+
+#: ../../network_setup.rst:1236
+# a1033461e720442987768d66a5c30817
+msgid "To collect usage data for a guest network, CloudStack needs to pull the data from an external network statistics collector installed on the network. Metering statistics for guest networks are available through CloudStack’s integration with inMon Traffic Sentinel."
+msgstr ""
+
+#: ../../network_setup.rst:1241
+# 7d3d373bf4a5491b896acc71b472ac64
+msgid "Traffic Sentinel is a network traffic usage data collection package. CloudStack can feed statistics from Traffic Sentinel into its own usage records, providing a basis for billing users of cloud infrastructure. Traffic Sentinel uses the traffic monitoring protocol sFlow. Routers and switches generate sFlow records and provide them for collection by Traffic Sentinel, then CloudStack queries the Traffic Sentinel database to obtain this information"
+msgstr ""
+
+#: ../../network_setup.rst:1249
+# 2062c2486edc48e6b7375866343cd941
+msgid "To construct the query, CloudStack determines what guest IPs were in use during the current query interval. This includes both newly assigned IPs and IPs that were assigned in a previous time period and continued to be in use. CloudStack queries Traffic Sentinel for network statistics that apply to these IPs during the time period they remained allocated in CloudStack. The returned data is correlated with the customer account that owned each IP and the timestamps when IPs were assigned and released in order to create billable metering records in CloudStack. When the Usage Server runs, it collects this data."
+msgstr ""
+
+#: ../../network_setup.rst:1259
+# 844664604d9646ceb5255581c912b416
+msgid "To set up the integration between CloudStack and Traffic Sentinel:"
+msgstr ""
+
+#: ../../network_setup.rst:1263
+# 62333109e1844fe29982d2853727fe33
+msgid "On your network infrastructure, install Traffic Sentinel and configure it to gather traffic data. For installation and configuration steps, see inMon documentation at `Traffic Sentinel Documentation <http://inmon.com.>`_."
+msgstr ""
+
+#: ../../network_setup.rst:1270
+# fda8f8f36797492b8992aae7fdbd39c7
+msgid "In the Traffic Sentinel UI, configure Traffic Sentinel to accept script querying from guest users. CloudStack will be the guest user performing the remote queries to gather network usage for one or more IP addresses."
+msgstr ""
+
+#: ../../network_setup.rst:1275
+# e69dc34cb21b46e19bce066edb7c5eb7
+msgid "Click File > Users > Access Control > Reports Query, then select Guest from the drop-down list."
+msgstr ""
+
+#: ../../network_setup.rst:1280
+# a3cd19f6eb1b4de78cec9743ec4788ca
+msgid "On CloudStack, add the Traffic Sentinel host by calling the CloudStack API command addTrafficMonitor. Pass in the URL of the Traffic Sentinel as protocol + host + port (optional); for example, http://10.147.28.100:8080. For the addTrafficMonitor command syntax, see the API Reference at `API Documentation <http://cloudstack.apache.org/docs/api/index.html>`_."
+msgstr ""
+
+#: ../../network_setup.rst:1286
+# ee8e36880d0541bf92a0f4e7c4a09864
+msgid "For information about how to call the CloudStack API, see the Developer’s Guide at `CloudStack API Developer's Guide <http://docs.cloudstack.apache.org/en/latest/index.html#developers>`_."
+msgstr ""
+
+#: ../../network_setup.rst:1295
+# a4a1b0a100374afd8c1629d22699b25f
+msgid "Select Configuration from the Global Settings page, and set the following:"
+msgstr ""
+
+#: ../../network_setup.rst:1298
+# f10ccb68df254c15a5e49fc4b5c9c8ef
+msgid "direct.network.stats.interval: How often you want CloudStack to query Traffic Sentinel."
+msgstr ""
+
+#: ../../network_setup.rst:1302
+# 4ba4da2ed13943aa8cb1c9404c4ef33a
+msgid "Setting Zone VLAN and Running VM Maximums"
+msgstr ""
+
+#: ../../network_setup.rst:1304
+# 43dcbcdcec5b46e9b0a4230c8d01229e
+msgid "In the external networking case, every VM in a zone must have a unique guest IP address. There are two variables that you need to consider in determining how to configure CloudStack to support this: how many Zone VLANs do you expect to have and how many VMs do you expect to have running in the Zone at any one time."
+msgstr ""
+
+#: ../../network_setup.rst:1310
+# 3c06fde7caf545578df853935f441b69
+msgid "Use the following table to determine how to configure CloudStack for your deployment."
+msgstr ""
+
+#: ../../network_setup.rst:1314
+# a848b5f139a04c41bd50a86a1d89bd12
+msgid "guest.vlan.bits"
+msgstr ""
+
+#: ../../network_setup.rst:1314
+# 2f4ceb0e1a304f3e9c1dd7c41932834d
+msgid "Maximum Running VMs per Zone"
+msgstr ""
+
+#: ../../network_setup.rst:1314
+# 056a8c2f7f664fee9548096053ff46ee
+msgid "Maximum Zone VLANs"
+msgstr ""
+
+#: ../../network_setup.rst:1316
+# 4d8f8eea18e548fa928ab017f5d52429
+msgid "12"
+msgstr ""
+
+#: ../../network_setup.rst:1316
+# 51f954229ce747908d7352586f8edb4f
+msgid "4096"
+msgstr ""
+
+#: ../../network_setup.rst:1316
+# 33c91a1d50b74c808d6fce365c83a91e
+msgid "4094"
+msgstr ""
+
+#: ../../network_setup.rst:1317
+# 8027bdd3648d4d638c40c06c1f54c1b7
+msgid "11"
+msgstr ""
+
+#: ../../network_setup.rst:1317
+# 7676db941b41440ba71b48a1088952a8
+msgid "8192"
+msgstr ""
+
+#: ../../network_setup.rst:1317
+# c5866aed4ad3438f84ee69f0f63c109a
+msgid "2048"
+msgstr ""
+
+#: ../../network_setup.rst:1318
+#: ../../network_setup.rst:1319
+# 102e6d7a19264bf297b438181b42e482
+# ea6c3074726849a5a3361c4cac194c44
+msgid "10"
+msgstr ""
+
+#: ../../network_setup.rst:1318
+# 29bbad87ea61413ba224231c60a59aad
+msgid "16384"
+msgstr ""
+
+#: ../../network_setup.rst:1318
+# 155ced14eac945d39bafceb596c3c6a7
+msgid "1024"
+msgstr ""
+
+#: ../../network_setup.rst:1319
+# b94ad2bcf67149a9894d28f4c4751cae
+msgid "32768"
+msgstr ""
+
+#: ../../network_setup.rst:1319
+# 7236907a01e040a9bc8cd8d249d4581d
+msgid "512"
+msgstr ""
+
+#: ../../network_setup.rst:1322
+# f1b8ef6932d04910981997f99bbc94c5
+msgid "Based on your deployment's needs, choose the appropriate value of guest.vlan.bits. Set it as described in Edit the Global Configuration Settings (Optional) section and restart the Management Server."
+msgstr ""
+
[6/7] setup i18n with transifex and sphinx-intl
Posted by se...@apache.org.
http://git-wip-us.apache.org/repos/asf/cloudstack-docs-install/blob/bd81bcc4/source/locale/pot/configuration.pot
----------------------------------------------------------------------
diff --git a/source/locale/pot/configuration.pot b/source/locale/pot/configuration.pot
new file mode 100644
index 0000000..9b44c1e
--- /dev/null
+++ b/source/locale/pot/configuration.pot
@@ -0,0 +1,2565 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2014, Apache Software Foundation
+# This file is distributed under the same license as the Apache CloudStack Installation Documentation package.
+# FIRST AUTHOR <EM...@ADDRESS>, YEAR.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: Apache CloudStack Installation Documentation 4\n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2014-03-31 14:02-0400\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"
+
+#: ../../configuration.rst:17
+# 45acea9adb2548209aa256f577b8e60c
+msgid "Configuring your CloudStack Installation"
+msgstr ""
+
+#: ../../configuration.rst:19
+# 631065640ed942cfb4b792688f02005e
+msgid "This section tells how to add regions, zones, pods, clusters, hosts, storage, and networks to your cloud. If you are unfamiliar with these entities, please begin by looking through `*Cloud Infrastructure Concepts* <http://docs.cloudstack.apache.org/en/latest/concepts.html#cloud-infrastructure-concepts>`_."
+msgstr ""
+
+#: ../../configuration.rst:24
+# f5a36204546f4898aca0e49774b4268d
+msgid "Overview of Provisioning Steps"
+msgstr ""
+
+#: ../../configuration.rst:26
+# 784e7c8091dd47c4825f7cca2dcbd408
+msgid "After the Management Server is installed and running, you can add the compute resources for it to manage. For an overview of how a CloudStack cloud infrastructure is organized, see `“Cloud Infrastructure Overview” <http://docs.cloudstack.apache.org/en/latest/concepts.html#cloud-infrastructure-overview>`_."
+msgstr ""
+
+#: ../../configuration.rst:30
+# 2ca32f075974491ebc5686e00d342541
+msgid "To provision the cloud infrastructure, or to scale it up at any time, follow these procedures:"
+msgstr ""
+
+#: ../../configuration.rst:35
+# 0e10bef9b4fd4b6c9c3da54aa0943ede
+msgid "Define regions (optional). See :ref:`adding-regions`."
+msgstr ""
+
+#: ../../configuration.rst:39
+# 47309dba0b4541a9963e04bb93181dfb
+msgid "Add a zone to the region. See :ref:`adding-a-zone`."
+msgstr ""
+
+#: ../../configuration.rst:43
+# cd172d8cc0d143658c4f14bc7248e2ab
+msgid "Add more pods to the zone (optional). See :ref:`adding-a-pod`."
+msgstr ""
+
+#: ../../configuration.rst:47
+# 05b04a62577748b7a7ba6d8745678d1d
+msgid "Add more clusters to the pod (optional). See :ref:`adding-a-cluster`."
+msgstr ""
+
+#: ../../configuration.rst:51
+# 0bbab9fa3f3945c2bbc869d685ff6eba
+msgid "Add more hosts to the cluster (optional). See :ref:`adding-a-host`."
+msgstr ""
+
+#: ../../configuration.rst:55
+# 89166fce4a6d408db25b86b799dddba5
+msgid "Add primary storage to the cluster. See :ref:`add-primary-storage`."
+msgstr ""
+
+#: ../../configuration.rst:59
+# 8c4300d906564b79ae61166148a5ad29
+msgid "Add secondary storage to the zone. See :ref:`add-secondary-storage`."
+msgstr ""
+
+#: ../../configuration.rst:63
+# 759bf0e850b54c3897a518046e8db0fb
+msgid "Initialize and test the new cloud. See :ref:`initialize-and-test`."
+msgstr ""
+
+#: ../../configuration.rst:65
+# 38485358da2742b4bcd44e36cebc0ffa
+msgid "When you have finished these steps, you will have a deployment with the following basic structure:"
+msgstr ""
+
+#: ../../configuration.rst:68
+# 005c638aefab408fa6f004cf75f9dca7
+msgid "|provisioning-overview.png: Conceptual overview of a basic deployment|"
+msgstr ""
+
+#: ../../configuration.rst:73
+# 692f3a9b339245ffaf0b3e9f4972016f
+msgid "Adding Regions (optional)"
+msgstr ""
+
+#: ../../configuration.rst:75
+# 9ea2b3060e264c53b3da64ecde63cd15
+msgid "Grouping your cloud resources into geographic regions is an optional step when provisioning the cloud. For an overview of regions, see `“About Regions” <http://docs.cloudstack.apache.org/en/latest/concepts.html#about-regions>`_."
+msgstr ""
+
+#: ../../configuration.rst:80
+# 507d56ace2bb449c82f620df66d09baa
+msgid "The First Region: The Default Region"
+msgstr ""
+
+#: ../../configuration.rst:82
+# 4402e8d88d7040f5b1c2ff1c8fd91d59
+msgid "If you do not take action to define regions, then all the zones in your cloud will be automatically grouped into a single default region. This region is assigned the region ID of 1. You can change the name or URL of the default region by displaying the region in the CloudStack UI and clicking the Edit button."
+msgstr ""
+
+#: ../../configuration.rst:89
+# d574a459a37e48ffbd3137b9f9036a6c
+msgid "Adding a Region"
+msgstr ""
+
+#: ../../configuration.rst:91
+# cffff93b262e4e46a634d7078a1da247
+msgid "Use these steps to add a second region in addition to the default region."
+msgstr ""
+
+#: ../../configuration.rst:96
+# 4ee1e8d33fa34a77b44056566a630a21
+msgid "Each region has its own CloudStack instance. Therefore, the first step of creating a new region is to install the Management Server software, on one or more nodes, in the geographic area where you want to set up the new region. Use the steps in the Installation guide. When you come to the step where you set up the database, use the additional command-line flag ``-r <region_id>`` to set a region ID for the new region. The default region is automatically assigned a region ID of 1, so your first additional region might be region 2."
+msgstr ""
+
+#: ../../configuration.rst:111
+# 8027a30d1fc94344bf2e9277e1626db6
+msgid "By the end of the installation procedure, the Management Server should have been started. Be sure that the Management Server installation was successful and complete."
+msgstr ""
+
+#: ../../configuration.rst:117
+# 52664a015f7349fa84dee05151f3bcca
+msgid "Now add the new region to region 1 in CloudStack."
+msgstr ""
+
+#: ../../configuration.rst:121
+# f483b7a4cf1340278641e35267782e82
+msgid "Log in to CloudStack in the first region as root administrator (that is, log in to <region.1.IP.address>:8080/client)."
+msgstr ""
+
+#: ../../configuration.rst:126
+#: ../../configuration.rst:314
+# f2df274d77514d689b134744275e21f3
+# c71cb10cc3fd4d4781b43fdb5c16fd1c
+msgid "In the left navigation bar, click Regions."
+msgstr ""
+
+#: ../../configuration.rst:130
+# b5fea4463f2045d88b232bf196043bcd
+msgid "Click Add Region. In the dialog, fill in the following fields:"
+msgstr ""
+
+#: ../../configuration.rst:134
+# 8ee8fd20450248259811540024c990a0
+msgid "ID. A unique identifying number. Use the same number you set in the database during Management Server installation in the new region; for example, 2."
+msgstr ""
+
+#: ../../configuration.rst:140
+# 95fd6770715c4b55aeca9115d9fb46fd
+msgid "Name. Give the new region a descriptive name."
+msgstr ""
+
+#: ../../configuration.rst:144
+# 2f2298c6957a405bb8744dd91b54f94d
+msgid "Endpoint. The URL where you can log in to the Management Server in the new region. This has the format <region.2.IP.address>:8080/client."
+msgstr ""
+
+#: ../../configuration.rst:150
+# 3ab82c31b3a74fe5b3312e66dc28a461
+msgid "Now perform the same procedure in reverse. Log in to region 2, and add region 1."
+msgstr ""
+
+#: ../../configuration.rst:155
+# 98c8573417e84c86aeee08435cb2abd2
+msgid "Copy the account, user, and domain tables from the region 1 database to the region 2 database."
+msgstr ""
+
+#: ../../configuration.rst:158
+#: ../../configuration.rst:260
+# 1dbd41b2c5e14057a5c2659826e93bb6
+# 53605a0d90e6469e9642a71cc7078b2e
+msgid "In the following commands, it is assumed that you have set the root password on the database, which is a CloudStack recommended best practice. Substitute your own MySQL root password."
+msgstr ""
+
+#: ../../configuration.rst:164
+#: ../../configuration.rst:266
+# ff61de1baec540c4aedec3415f0eae7f
+# 28e79cf3fb634580b620deca1d4a37d3
+msgid "First, run this command to copy the contents of the database:"
+msgstr ""
+
+#: ../../configuration.rst:172
+# 48bb53cad97c4c82b727531405fb923b
+msgid "Then run this command to put the data onto the region 2 database:"
+msgstr ""
+
+#: ../../configuration.rst:180
+# 27deb6616ae84350b4544824caa09d4d
+msgid "Remove project accounts. Run these commands on the region 2 database:"
+msgstr ""
+
+#: ../../configuration.rst:188
+#: ../../configuration.rst:291
+# 06f8398e0d354c36a48ea497d8ce6d1f
+# 74f47c70888f4094ab9d33fe47be802a
+msgid "Set the default zone as null:"
+msgstr ""
+
+#: ../../configuration.rst:196
+# cbdfcba49db84702973a6e70c7018344
+msgid "Restart the Management Servers in region 2."
+msgstr ""
+
+#: ../../configuration.rst:199
+# 0bd858a2349e4056b19dbfdd8015f237
+msgid "Adding Third and Subsequent Regions"
+msgstr ""
+
+#: ../../configuration.rst:201
+# 8f49c3a268244caca74c2078e46b3e4b
+msgid "To add the third region, and subsequent additional regions, the steps are similar to those for adding the second region. However, you must repeat certain steps additional times for each additional region:"
+msgstr ""
+
+#: ../../configuration.rst:207
+# 257d1cb614934e569e3809fc806b8297
+msgid "Install CloudStack in each additional region. Set the region ID for each region during the database setup step."
+msgstr ""
+
+#: ../../configuration.rst:216
+# 395959f794334f5b96786f5f32dcbe21
+msgid "Once the Management Server is running, add your new region to all existing regions by repeatedly using the Add Region button in the UI. For example, if you were adding region 3:"
+msgstr ""
+
+#: ../../configuration.rst:222
+# ca1bcb7c888c4368a294db9991dc3a8a
+msgid "Log in to CloudStack in the first region as root administrator (that is, log in to <region.1.IP.address>:8080/client), and add a region with ID 3, the name of region 3, and the endpoint <region.3.IP.address>:8080/client."
+msgstr ""
+
+#: ../../configuration.rst:229
+# 60d1d4c4c4fa429a887611478e7b2157
+msgid "Log in to CloudStack in the second region as root administrator (that is, log in to <region.2.IP.address>:8080/client), and add a region with ID 3, the name of region 3, and the endpoint <region.3.IP.address>:8080/client."
+msgstr ""
+
+#: ../../configuration.rst:236
+# 918da36c27d6472591edffa778d35170
+msgid "Repeat the procedure in reverse to add all existing regions to the new region. For example, for the third region, add the other two existing regions:"
+msgstr ""
+
+#: ../../configuration.rst:242
+# ff9578a7f14b4498943bb3c8876e73f8
+msgid "Log in to CloudStack in the third region as root administrator (that is, log in to <region.3.IP.address>:8080/client)."
+msgstr ""
+
+#: ../../configuration.rst:247
+# 3f00a1fbcce84212898cfb9fbbd59ba3
+msgid "Add a region with ID 1, the name of region 1, and the endpoint <region.1.IP.address>:8080/client."
+msgstr ""
+
+#: ../../configuration.rst:252
+# 6c19cbd03e3c403eb315c04ca47af953
+msgid "Add a region with ID 2, the name of region 2, and the endpoint <region.2.IP.address>:8080/client."
+msgstr ""
+
+#: ../../configuration.rst:257
+# 3882cd53f34e40869460406733a82068
+msgid "Copy the account, user, and domain tables from any existing region's database to the new region's database."
+msgstr ""
+
+#: ../../configuration.rst:274
+# 4ccc5a29922a4a2280a9be0da19aeec1
+msgid "Then run this command to put the data onto the new region's database. For example, for region 3:"
+msgstr ""
+
+#: ../../configuration.rst:283
+# 37071a5319a24d50849081d6b81e6d24
+msgid "Remove project accounts. Run these commands on the region 3 database:"
+msgstr ""
+
+#: ../../configuration.rst:299
+# 3ac9f60758bf400ebd02bd08b1ca86e9
+msgid "Restart the Management Servers in the new region."
+msgstr ""
+
+#: ../../configuration.rst:302
+# 9836f86191b842b4831d6d6a2db3b8f8
+msgid "Deleting a Region"
+msgstr ""
+
+#: ../../configuration.rst:304
+# e98211bd8aac47418ea332b0550b5230
+msgid "Log in to each of the other regions, navigate to the one you want to delete, and click Remove Region. For example, to remove the third region in a 3-region cloud:"
+msgstr ""
+
+#: ../../configuration.rst:310
+# e9fc61e242db40fba505f4d97358ce02
+msgid "Log in to <region.1.IP.address>:8080/client."
+msgstr ""
+
+#: ../../configuration.rst:318
+# e3e5a9698c904e81807964de50f09c7c
+msgid "Click the name of the region you want to delete."
+msgstr ""
+
+#: ../../configuration.rst:322
+# cbca5543d446453d9e3dd1ee58244f5b
+msgid "Click the Remove Region button."
+msgstr ""
+
+#: ../../configuration.rst:326
+# 05a479643ed54875829839f2cde49ffb
+msgid "Repeat these steps for <region.2.IP.address>:8080/client."
+msgstr ""
+
+#: ../../configuration.rst:331
+# 2dca47eb286a4b60b61bd7f4753ab2ea
+msgid "Adding a Zone"
+msgstr ""
+
+#: ../../configuration.rst:333
+# bcbc148e115c4f6d9b30698f387f88e8
+msgid "When you add a new zone, you will be prompted to configure the zone’s physical network and add the first pod, cluster, host, primary storage, and secondary storage."
+msgstr ""
+
+#: ../../configuration.rst:339
+# c070a051b21c476fa3712937eb02be3b
+msgid "Log in to the CloudStack UI as the root administrator. See `“Log In to the UI” <http://docs.cloudstack.apache.org/projects/cloudstack-administration/en/latest/ui.html#log-in-to-the-ui>`_."
+msgstr ""
+
+#: ../../configuration.rst:343
+# e24fa381bf6b400ab2126637937e5727
+msgid "In the left navigation, choose Infrastructure."
+msgstr ""
+
+#: ../../configuration.rst:347
+# 60f4ee940b6144aea7120c389338c83d
+msgid "On Zones, click View More."
+msgstr ""
+
+#: ../../configuration.rst:351
+# debfb280cfda44518188ca815970b071
+msgid "Click Add Zone. The zone creation wizard will appear."
+msgstr ""
+
+#: ../../configuration.rst:355
+# 7fb77368a32c4567a960fbcdff60f2c6
+msgid "Choose one of the following network types:"
+msgstr ""
+
+#: ../../configuration.rst:359
+# b68848a5a5b4469f806345e6da6a0e92
+msgid "**Basic.** For AWS-style networking. Provides a single network where each VM instance is assigned an IP directly from the network. Guest isolation can be provided through layer-3 means such as security groups (IP address source filtering)."
+msgstr ""
+
+#: ../../configuration.rst:366
+# 296ce061b7ce48eba140de7cd89a5ad7
+msgid "**Advanced.** For more sophisticated network topologies. This network model provides the most flexibility in defining guest networks and providing custom network offerings such as firewall, VPN, or load balancer support."
+msgstr ""
+
+#: ../../configuration.rst:373
+# ef1cbdd846734108a6daeac0750b06ff
+msgid "The rest of the steps differ depending on whether you chose Basic or Advanced. Continue with the steps that apply to you:"
+msgstr ""
+
+#: ../../configuration.rst:378
+# 4fa886d3f2bb49e2b2f240f943c40235
+msgid "`“Basic Zone Configuration” <#basic-zone-configuration>`_"
+msgstr ""
+
+#: ../../configuration.rst:382
+# 0fb43e57483546739b620ef66f4f3f34
+msgid "`“Advanced Zone Configuration” <#advanced-zone-configuration>`_"
+msgstr ""
+
+#: ../../configuration.rst:385
+# 46a30f1db35844d093cd12cfc7fdd58b
+msgid "Basic Zone Configuration"
+msgstr ""
+
+#: ../../configuration.rst:389
+# 4063108d69a94b3e86b9af1ea4dc53b6
+msgid "After you select Basic in the Add Zone wizard and click Next, you will be asked to enter the following details. Then click Next."
+msgstr ""
+
+#: ../../configuration.rst:394
+#: ../../configuration.rst:713
+# 3b236f0b8d7d43a882923b1bdf98d615
+# 80564cf16b304756967f0cfeaba74fc2
+msgid "**Name.** A name for the zone."
+msgstr ""
+
+#: ../../configuration.rst:398
+#: ../../configuration.rst:717
+# 22b0107bfa474078bed0bfd824dc7f29
+# b8f82643eeb64bda851fde32741343f1
+msgid "**DNS 1 and 2.** These are DNS servers for use by guest VMs in the zone. These DNS servers will be accessed via the public network you will add later. The public IP addresses for the zone must have a route to the DNS server named here."
+msgstr ""
+
+#: ../../configuration.rst:405
+# cd406beeec6940b2bd49faa359f8da6d
+msgid "**Internal DNS 1 and Internal DNS 2.** These are DNS servers for use by system VMs in the zone (these are VMs used by CloudStack itself, such as virtual routers, console proxies, and Secondary Storage VMs.) These DNS servers will be accessed via the management traffic network interface of the System VMs. The private IP address you provide for the pods must have a route to the internal DNS server named here."
+msgstr ""
+
+#: ../../configuration.rst:415
+#: ../../configuration.rst:747
+# 2bc3215a0329468e82fc555a22b63eda
+# 4c71ecf694cb4834a7b1b7482ba9012e
+msgid "**Hypervisor.** (Introduced in version 3.0.1) Choose the hypervisor for the first cluster in the zone. You can add clusters with different hypervisors later, after you finish adding the zone."
+msgstr ""
+
+#: ../../configuration.rst:422
+# d17a3bfc42934cd5a219e633ed63bb0a
+msgid "**Network Offering.** Your choice here determines what network services will be available on the network for guest VMs."
+msgstr ""
+
+#: ../../configuration.rst:426
+# ef31becdb3d740bc93ca18d045ea2c22
+msgid "Network Offering"
+msgstr ""
+
+#: ../../configuration.rst:426
+# 517d3e8d90324125ae08ca05a72f6b50
+msgid "Description"
+msgstr ""
+
+#: ../../configuration.rst:428
+# d5860408ab474addacbac1cad4802d1c
+msgid "DefaultSharedNetworkOfferingWithSGService"
+msgstr ""
+
+#: ../../configuration.rst:428
+# 125d81fc283f4bd19b3fc8daf3e15af2
+msgid "If you want to enable security groups for guest traffic isolation, choose this. (See Using Security Groups to Control Traffic to VMs.)"
+msgstr ""
+
+#: ../../configuration.rst:429
+# d2fc219630c64850a2abaaab29c550c3
+msgid "DefaultSharedNetworkOffering"
+msgstr ""
+
+#: ../../configuration.rst:429
+# 5ed8d77948404fb295f04d5f40fab149
+msgid "If you do not need security groups, choose this."
+msgstr ""
+
+#: ../../configuration.rst:430
+# 07b07e49e385490e8ecb558ab588fcf7
+msgid "DefaultSharedNetscalerEIPandELBNetworkOffering"
+msgstr ""
+
+#: ../../configuration.rst:430
+# 090ff14fbc52449e9297d82abe938d1d
+msgid "If you have installed a Citrix NetScaler appliance as part of your zone network, and you will be using its Elastic IP and Elastic Load Balancing features, choose this. With the EIP and ELB features, a basic zone with security groups enabled can offer 1:1 static NAT and load balancing."
+msgstr ""
+
+#: ../../configuration.rst:436
+#: ../../configuration.rst:734
+# e5664a9c31354bfcbf38c1d08f4ebf95
+# 89170104a5ca4af4a33a362bb6e0975d
+msgid "**Network Domain.** (Optional) If you want to assign a special domain name to the guest VM network, specify the DNS suffix."
+msgstr ""
+
+#: ../../configuration.rst:441
+#: ../../configuration.rst:754
+# 64883a8d982347c48817967242eb1008
+# b1f435546f354b9c9a9f4b997fd96080
+msgid "**Public.** A public zone is available to all users. A zone that is not public will be assigned to a particular domain. Only users in that domain will be allowed to create guest VMs in this zone."
+msgstr ""
+
+#: ../../configuration.rst:447
+#: ../../configuration.rst:760
+# 65ef78186d6e4017b077ad2dff55e988
+# 86b0790603144cba93ba056401884952
+msgid "Choose which traffic types will be carried by the physical network."
+msgstr ""
+
+#: ../../configuration.rst:449
+# 29cc0f17f86c44f7a7b79f6336bcdf1a
+msgid "The traffic types are management, public, guest, and storage traffic. For more information about the types, roll over the icons to display their tool tips, or see Basic Zone Network Traffic Types. This screen starts out with some traffic types already assigned. To add more, drag and drop traffic types onto the network. You can also change the network name if desired."
+msgstr ""
+
+#: ../../configuration.rst:458
+# b4e1f8437bde4ff0ac9027cc02c6f071
+msgid "Assign a network traffic label to each traffic type on the physical network. These labels must match the labels you have already defined on the hypervisor host. To assign each label, click the Edit button under the traffic type icon. A popup dialog appears where you can type the label, then click OK."
+msgstr ""
+
+#: ../../configuration.rst:464
+#: ../../configuration.rst:782
+# 51dc8782b20041bf87398e8eba15fc64
+# 154322fa724d4e5782d03ac2ffdc629f
+msgid "These traffic labels will be defined only for the hypervisor selected for the first cluster. For all other hypervisors, the labels can be configured after the zone is created."
+msgstr ""
+
+#: ../../configuration.rst:470
+#: ../../configuration.rst:799
+# ddce4ae13734445fa06e4dc9b5c31214
+# fb9118c520f04f58a34b8a18eae05df1
+msgid "Click Next."
+msgstr ""
+
+#: ../../configuration.rst:474
+# 6efb7b69d5a441d08cb6f36802ca4f31
+msgid "(NetScaler only) If you chose the network offering for NetScaler, you have an additional screen to fill out. Provide the requested details to set up the NetScaler, then click Next."
+msgstr ""
+
+#: ../../configuration.rst:480
+# 9baa9068037c4d619fd05fdbde42b5ac
+msgid "**IP address.** The NSIP (NetScaler IP) address of the NetScaler device."
+msgstr ""
+
+#: ../../configuration.rst:485
+# e14c8c80706143819d4c5f4617b7007a
+msgid "**Username/Password.** The authentication credentials to access the device. CloudStack uses these credentials to access the device."
+msgstr ""
+
+#: ../../configuration.rst:491
+# fcb69d66d64848da9bb79f41e227f037
+msgid "**Type.** NetScaler device type that is being added. It could be NetScaler VPX, NetScaler MPX, or NetScaler SDX. For a comparison of the types, see About Using a NetScaler Load Balancer."
+msgstr ""
+
+#: ../../configuration.rst:497
+# e4cfd62ce8e247cc890173228c356b5d
+msgid "**Public interface.** Interface of NetScaler that is configured to be part of the public network."
+msgstr ""
+
+#: ../../configuration.rst:502
+# 3ce93cfa784f476a863dd0a019f569d6
+msgid "**Private interface.** Interface of NetScaler that is configured to be part of the private network."
+msgstr ""
+
+#: ../../configuration.rst:507
+# 4b2f689747864e6d8bf8e37da5d55539
+msgid "**Number of retries.** Number of times to attempt a command on the device before considering the operation failed. Default is 2."
+msgstr ""
+
+#: ../../configuration.rst:512
+# a36fcf6641e048df98be9001fe4ac14a
+msgid "**Capacity.** Number of guest networks/accounts that will share this NetScaler device."
+msgstr ""
+
+#: ../../configuration.rst:517
+# 4b06adfa22054cbd8484bdeeaa66341b
+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 ""
+
+#: ../../configuration.rst:524
+# 77ed28ed24f34c2fb5c2a2c927e9c78f
+msgid "(NetScaler only) Configure the IP range for public traffic. The IPs in this range will be used for the static NAT capability which you enabled by selecting the network offering for NetScaler with EIP and ELB. Enter the following details, then click Add. If desired, you can repeat this step to add more IP ranges. When done, click Next."
+msgstr ""
+
+#: ../../configuration.rst:532
+#: ../../configuration.rst:809
+# fbe8cc3d3943406c8ebc7dff8a601441
+# 48d9ff0dff8b46e7b21814384a191425
+msgid "**Gateway.** The gateway in use for these IP addresses."
+msgstr ""
+
+#: ../../configuration.rst:536
+#: ../../configuration.rst:813
+# 78f22c4e6109478480c3a2c3a354bd04
+# c521fe80e088471cb2737bcf7668f650
+msgid "**Netmask.** The netmask associated with this IP range."
+msgstr ""
+
+#: ../../configuration.rst:540
+#: ../../configuration.rst:817
+# 23bf2ce061e0493d81fcd9f0f0916845
+# c18179e1c6f44f269bcf9823c1cb0ce8
+msgid "**VLAN.** The VLAN that will be used for public traffic."
+msgstr ""
+
+#: ../../configuration.rst:544
+# 65e21821323840f98638cafb62113317
+msgid "**Start IP/End IP.** A range of IP addresses that are assumed to be accessible from the Internet and will be allocated for access to guest VMs."
+msgstr ""
+
+#: ../../configuration.rst:550
+#: ../../configuration.rst:827
+# a295f9e2c422411783702b29b72824e9
+# 7ef179832e1448af85ce7d5bb289cc9a
+msgid "In a new zone, CloudStack adds the first pod for you. You can always add more pods later. For an overview of what a pod is, see `“About Pods” <http://docs.cloudstack.apache.org/en/latest/concepts.html?highlight=about%20pods#about-pods>`_."
+msgstr ""
+
+#: ../../configuration.rst:554
+#: ../../configuration.rst:831
+# 872951234cad4be787e1ffd7a0fa69c5
+# 73680bf45ad84c6c8283efa909462fcb
+msgid "To configure the first pod, enter the following, then click Next:"
+msgstr ""
+
+#: ../../configuration.rst:558
+#: ../../configuration.rst:835
+# cda299d9e07b4148bd737d8aa4a58f81
+# 5859811ef2ba438a81a3c1b5dcfb8d2b
+msgid "**Pod Name.** A name for the pod."
+msgstr ""
+
+#: ../../configuration.rst:562
+#: ../../configuration.rst:839
+# 531f0303b073461b89623ec4b415887d
+# 3fd8f47d38c54df485e5ff8d6bdd3377
+msgid "**Reserved system gateway.** The gateway for the hosts in that pod."
+msgstr ""
+
+#: ../../configuration.rst:567
+#: ../../configuration.rst:844
+# 541610014dc547b9bd5262bccac65d64
+# b9bdc3ff1fdf4b29b9cb5be6c87bb172
+msgid "**Reserved system netmask.** The network prefix that defines the pod's subnet. Use CIDR notation."
+msgstr ""
+
+#: ../../configuration.rst:572
+#: ../../configuration.rst:1107
+# ec9a0dd4b7634ed69af654a935555ee4
+# 03028cdc0da8495b9e5bc8e1973210c6
+msgid "**Start/End Reserved System IP.** The IP range in the management network that CloudStack uses to manage various system VMs, such as Secondary Storage VMs, Console Proxy VMs, and DHCP. For more information, see System Reserved IP Addresses."
+msgstr ""
+
+#: ../../configuration.rst:579
+# 7bfc5880d8644d23bcf1bc641c90eceb
+msgid "Configure the network for guest traffic. Provide the following, then click Next:"
+msgstr ""
+
+#: ../../configuration.rst:584
+# 5a614d7bcd81432f80fccbfcba8b1131
+msgid "**Guest gateway.** The gateway that the guests should use."
+msgstr ""
+
+#: ../../configuration.rst:588
+# 936792d3ec034c7187678210e4212154
+msgid "**Guest netmask.** The netmask in use on the subnet the guests will use."
+msgstr ""
+
+#: ../../configuration.rst:593
+# 4e4534967671437dabfed4d6388c1054
+msgid "**Guest start IP/End IP.** Enter the first and last IP addresses that define a range that CloudStack can assign to guests."
+msgstr ""
+
+#: ../../configuration.rst:598
+# 8b441ec54a0a43ef9e4015a52ef67b82
+msgid "We strongly recommend the use of multiple NICs. If multiple NICs are used, they may be in a different subnet."
+msgstr ""
+
+#: ../../configuration.rst:603
+# 9b102b8cc83641898482283b66567f5f
+msgid "If one NIC is used, these IPs should be in the same CIDR as the pod CIDR."
+msgstr ""
+
+#: ../../configuration.rst:608
+# cc2bc4092258474fb449f386f8d9e5b7
+msgid "In a new pod, CloudStack adds the first cluster for you. You can always add more clusters later. For an overview of what a cluster is, see About Clusters."
+msgstr ""
+
+#: ../../configuration.rst:612
+#: ../../configuration.rst:865
+# 9dfc5d96e4f246f5bf67701580b42c96
+# 55747277384844dc9df19ca416e9fe67
+msgid "To configure the first cluster, enter the following, then click Next:"
+msgstr ""
+
+#: ../../configuration.rst:616
+# a84cacfa2b9d4b2bbf353e4ae8458ede
+msgid "**Hypervisor.** (Version 3.0.0 only; in 3.0.1, this field is read only) Choose the type of hypervisor software that all hosts in this cluster will run. If you choose VMware, additional fields appear so you can give information about a vSphere cluster. For vSphere servers, we recommend creating the cluster of hosts in vCenter and then adding the entire cluster to CloudStack. See Add Cluster: vSphere."
+msgstr ""
+
+#: ../../configuration.rst:626
+#: ../../configuration.rst:879
+# 951aa047b6be4dac81da77ada5c1abbd
+# 978071a8c4ca49e69596a00092a94cc0
+msgid "**Cluster name.** Enter a name for the cluster. This can be text of your choosing and is not used by CloudStack."
+msgstr ""
+
+#: ../../configuration.rst:631
+# ed928322a0a44bc181d7446a673a2e65
+msgid "In a new cluster, CloudStack adds the first host for you. You can always add more hosts later. For an overview of what a host is, see About Hosts."
+msgstr ""
+
+#: ../../configuration.rst:637
+# c0eef46db65a474b9e07288ad00f722b
+msgid "When you add a hypervisor host to CloudStack, the host must not have any VMs already running."
+msgstr ""
+
+#: ../../configuration.rst:640
+#: ../../configuration.rst:893
+# 33a79b5face34cdd94df6594ea3f66d0
+# 99d62a9d7bac4f52b261ae6cfb2fbe6a
+msgid "Before you can configure the host, you need to install the hypervisor software on the host. You will need to know which version of the hypervisor software version is supported by CloudStack and what additional configuration is required to ensure the host will work with CloudStack. To find these installation details, see:"
+msgstr ""
+
+#: ../../configuration.rst:648
+# 02233aa6e2de42b3a2b7c8e9136f8d9b
+msgid "Citrix XenServer Installation and Configuration"
+msgstr ""
+
+#: ../../configuration.rst:652
+#: ../../configuration.rst:905
+# 8c9b2c7100d14b24a50d0f85b79684db
+# ffc02a27f1b64b7a86dae709431f60b1
+msgid "VMware vSphere Installation and Configuration"
+msgstr ""
+
+#: ../../configuration.rst:656
+# 1a252b54968f466a8cbcb7f06a5dd905
+msgid "KVM vSphere Installation and Configuration"
+msgstr ""
+
+#: ../../configuration.rst:658
+#: ../../configuration.rst:911
+# 774c568eb07a4a2b91208caa80ef09de
+# 5bae2591b30e41e89ebf6c05d5142147
+msgid "To configure the first host, enter the following, then click Next:"
+msgstr ""
+
+#: ../../configuration.rst:662
+#: ../../configuration.rst:915
+# a03e74384aa34baebe355da2e5c8eec4
+# b59ceb3125694b608633c452995c33a0
+msgid "**Host Name.** The DNS name or IP address of the host."
+msgstr ""
+
+#: ../../configuration.rst:666
+# 2a03556389f64c8a94e2e6a2c05eab3a
+msgid "**Username.** The username is root."
+msgstr ""
+
+#: ../../configuration.rst:670
+#: ../../configuration.rst:923
+# 0b80f7877aee4a83bfd151baa2616321
+# 7543731f101b4abda8e663dacbf732ba
+msgid "**Password.** This is the password for the user named above (from your XenServer or KVM install)."
+msgstr ""
+
+#: ../../configuration.rst:675
+# eba07a12b5e64ed89e284a579ff72a44
+msgid "**Host Tags.** (Optional) Any labels that you use to categorize hosts for ease of maintenance. For example, you can set this to the cloud's HA tag (set in the ha.tag global configuration parameter) if you want this host to be used only for VMs with the \"high availability\" feature enabled. For more information, see HA-Enabled Virtual Machines as well as HA for Hosts."
+msgstr ""
+
+#: ../../configuration.rst:684
+# 2482d12c56954e76ae62762c6c6eb1d9
+msgid "In a new cluster, CloudStack adds the first primary storage server for you. You can always add more servers later. For an overview of what primary storage is, see About Primary Storage."
+msgstr ""
+
+#: ../../configuration.rst:688
+#: ../../configuration.rst:942
+# 1d48f3ca3f554345a5616755e055799d
+# 164c7c68103749aa9d95db15b6080a6a
+msgid "To configure the first primary storage server, enter the following, then click Next:"
+msgstr ""
+
+#: ../../configuration.rst:693
+#: ../../configuration.rst:947
+#: ../../configuration.rst:1643
+# d41592ad92964faba6e773967f138853
+# f8da12c75d984391840b5b07d2ab449c
+# 269c18e534db44feac83ee3a0e794f8e
+msgid "**Name.** The name of the storage device."
+msgstr ""
+
+#: ../../configuration.rst:697
+# 79b86cfd84924ff5b7a94f0375688f8f
+msgid "**Protocol.** For XenServer, choose either NFS, iSCSI, or PreSetup. For KVM, choose NFS, SharedMountPoint,CLVM, or RBD. For vSphere choose either VMFS (iSCSI or FiberChannel) or NFS. The remaining fields in the screen vary depending on what you choose here."
+msgstr ""
+
+#: ../../configuration.rst:704
+# ecf97107ce3d4e7c9b440b10f0948215
+msgid "Advanced Zone Configuration"
+msgstr ""
+
+#: ../../configuration.rst:708
+# baa22a12fe374bc08acbc56464b36551
+msgid "After you select Advanced in the Add Zone wizard and click Next, you will be asked to enter the following details. Then click Next."
+msgstr ""
+
+#: ../../configuration.rst:724
+# 1af40c72b46646df88a2cb1de055446c
+msgid "**Internal DNS 1 and Internal DNS 2.** These are DNS servers for use by system VMs in the zone(these are VMs used by CloudStack itself, such as virtual routers, console proxies,and Secondary Storage VMs.) These DNS servers will be accessed via the management traffic network interface of the System VMs. The private IP address you provide for the pods must have a route to the internal DNS server named here."
+msgstr ""
+
+#: ../../configuration.rst:739
+# 415ff8607e2d487eb5812482d3be631d
+msgid "**Guest CIDR.** This is the CIDR that describes the IP addresses in use in the guest virtual networks in this zone. For example, 10.1.1.0/24. As a matter of good practice you should set different CIDRs for different zones. This will make it easier to set up VPNs between networks in different zones."
+msgstr ""
+
+#: ../../configuration.rst:762
+# 977338d53746471aa3fc54436bc40384
+msgid "The traffic types are management, public, guest, and storage traffic. For more information about the types, roll over the icons to display their tool tips, or see `“Advanced Zone Network Traffic Types” <http://docs.cloudstack.apache.org/en/latest/concepts.html?highlight=about%20pods#advanced-zone-network-traffic-types>`_. This screen starts out with one network already configured. If you have multiple physical networks, you need to add more. Drag and drop traffic types onto a greyed-out network and it will become active. You can move the traffic icons from one network to another; for example, if the default traffic types shown for Network 1 do not match your actual setup, you can move them down. You can also change the network names if desired."
+msgstr ""
+
+#: ../../configuration.rst:775
+# bf77e79090334dbdaf7817f868b62d9b
+msgid "(Introduced in version 3.0.1) Assign a network traffic label to each traffic type on each physical network. These labels must match the labels you have already defined on the hypervisor host. To assign each label, click the Edit button under the traffic type icon within each physical network. A popup dialog appears where you can type the label, then click OK."
+msgstr ""
+
+#: ../../configuration.rst:786
+# 3e95b5f1880d49e0ac9f081f589d54ed
+msgid "(VMware only) If you have enabled Nexus dvSwitch in the environment, you must specify the corresponding Ethernet port profile names as network traffic label for each traffic type on the physical network. For more information on Nexus dvSwitch, see Configuring a vSphere Cluster with Nexus 1000v Virtual Switch in the Installation Guide. If you have enabled VMware dvSwitch in the environment, you must specify the corresponding Switch name as network traffic label for each traffic type on the physical network. For more information, see Configuring a VMware Datacenter with VMware Distributed Virtual Switch in the Installation Guide."
+msgstr ""
+
+#: ../../configuration.rst:803
+# 2e09ad96d7ea431b93504f2b462eb18d
+msgid "Configure the IP range for public Internet traffic. Enter the following details, then click Add. If desired, you can repeat this step to add more public Internet IP ranges. When done, click Next."
+msgstr ""
+
+#: ../../configuration.rst:821
+# c040713c23f6478b9faa405acbccd403
+msgid "**Start IP/End IP.** A range of IP addresses that are assumed to be accessible from the Internet and will be allocated for access to guest networks."
+msgstr ""
+
+#: ../../configuration.rst:849
+# 028dd10cccfd4b988a432569b413c67e
+msgid "**Start/End Reserved System IP.** The IP range in the management network that CloudStack uses to manage various system VMs, such as Secondary Storage VMs, Console Proxy VMs, and DHCP. For more information, see `“System Reserved IP Addresses” <http://docs.cloudstack.apache.org/en/latest/concepts.html?highlight=about%20pods#id4>`_."
+msgstr ""
+
+#: ../../configuration.rst:856
+# aef499486dda461e81ca424e5e5b1481
+msgid "Specify a range of VLAN IDs to carry guest traffic for each physical network (see VLAN Allocation Example ), then click Next."
+msgstr ""
+
+#: ../../configuration.rst:861
+# dc8bd3cae1b641ecb806034ed9b636a1
+msgid "In a new pod, CloudStack adds the first cluster for you. You can always add more clusters later. For an overview of what a cluster is, see `“About Clusters” <http://docs.cloudstack.apache.org/en/latest/concepts.html?highlight=about%20pods#about-clusters>`_."
+msgstr ""
+
+#: ../../configuration.rst:869
+# 92202c4f1faa47bfbbc7324abd75c882
+msgid "**Hypervisor.** (Version 3.0.0 only; in 3.0.1, this field is read only) Choose the type of hypervisor software that all hosts in this cluster will run. If you choose VMware, additional fields appear so you can give information about a vSphere cluster. For vSphere servers, we recommend creating the cluster of hosts in vCenter and then adding the entire cluster to CloudStack. See Add Cluster: vSphere ."
+msgstr ""
+
+#: ../../configuration.rst:884
+# 4cda6da8084044bb92061b3e2e0957a2
+msgid "In a new cluster, CloudStack adds the first host for you. You can always add more hosts later. For an overview of what a host is, see `“About Hosts” <http://docs.cloudstack.apache.org/en/latest/concepts.html?highlight=about%20pods#about-hosts>`_."
+msgstr ""
+
+#: ../../configuration.rst:890
+# da82f7ef5c5140ada9ab09e56830a673
+msgid "When you deploy CloudStack, the hypervisor host must not have any VMs already running."
+msgstr ""
+
+#: ../../configuration.rst:901
+# 5feeceb5018240cda528adddb321bc47
+msgid "Citrix XenServer Installation for CloudStack"
+msgstr ""
+
+#: ../../configuration.rst:909
+# d7a322b42ef049738f5b4652dfb5b4a5
+msgid "KVM Installation and Configuration"
+msgstr ""
+
+#: ../../configuration.rst:919
+# 8f8c9491a2ee48a6be489f2a7756790c
+msgid "**Username.** Usually root."
+msgstr ""
+
+#: ../../configuration.rst:928
+# a06fccfe3a1246ac85ece2bb4b394e2e
+msgid "**Host Tags.** (Optional) Any labels that you use to categorize hosts for ease of maintenance. For example, you can set to the cloud's HA tag (set in the ha.tag global configuration parameter) if you want this host to be used only for VMs with the \"high availability\" feature enabled. For more information, see HA-Enabled Virtual Machines as well as HA for Hosts, both in the Administration Guide."
+msgstr ""
+
+#: ../../configuration.rst:938
+# 5805c3e9682a4275bf5df6d2864ba607
+msgid "In a new cluster, CloudStack adds the first primary storage server for you. You can always add more servers later. For an overview of what primary storage is, see `“About Primary Storage” <http://docs.cloudstack.apache.org/en/latest/concepts.html?highlight=about%20pods#about-primary-storage>`_."
+msgstr ""
+
+#: ../../configuration.rst:951
+# 495b8c4c1fa8426bab3a4b45a4b9cd99
+msgid "**Protocol.** For XenServer, choose either NFS, iSCSI, or PreSetup. For KVM, choose NFS, SharedMountPoint, CLVM, and RBD. For vSphere choose either VMFS (iSCSI or FiberChannel) or NFS. The remaining fields in the screen vary depending on what you choose here."
+msgstr ""
+
+#: ../../configuration.rst:958
+# c13c7ab68805492f81644e5ffb68f3ae
+msgid "NFS"
+msgstr ""
+
+#: ../../configuration.rst:960
+#: ../../configuration.rst:974
+#: ../../configuration.rst:993
+# 2578e443ed4149aea95aa6a1c1c249ed
+# 8eff8ab7756342c59d6d437dcc623949
+# b14ee384c5414666bc4dcbff1364f91a
+msgid "**Server.** The IP address or DNS name of the storage device."
+msgstr ""
+
+#: ../../configuration.rst:964
+#: ../../configuration.rst:1056
+# 62379870706c40b39e84a46323cff070
+# f11dd111d0fa4459b077c31828df6297
+msgid "**Path.** The exported path from the server."
+msgstr ""
+
+#: ../../configuration.rst:968
+#: ../../configuration.rst:987
+#: ../../configuration.rst:1002
+#: ../../configuration.rst:1013
+#: ../../configuration.rst:1029
+# 1bc7998a3ae34257ac8ea084b490e3dc
+# 95d89435789d49f58868b82dd77f2364
+# 688fec245b724ee58f46dac116c85768
+# a94b01dd1a9d47a6b0ca747204f38e31
+# 708979b025a2495bb0f1e298cb699e7c
+msgid "**Tags (optional).** The comma-separated list of tags for this storage device. It should be an equivalent set or superset of the tags on your disk offerings."
+msgstr ""
+
+#: ../../configuration.rst:972
+# 1bb64b1d14cb4e398ca842b1c0fbbb63
+msgid "iSCSI"
+msgstr ""
+
+#: ../../configuration.rst:978
+# 01d98c2c029f439085b511af99be85f2
+msgid "**Target IQN.** The IQN of the target. For example, iqn.1986-03.com.sun:02:01ec9bb549-1271378984."
+msgstr ""
+
+#: ../../configuration.rst:983
+# e205a1228c5d40dfa197fbfaba78a098
+msgid "**Lun.** The LUN number. For example, 3."
+msgstr ""
+
+#: ../../configuration.rst:991
+# fac43a474d054620bb8855699c505256
+msgid "preSetup"
+msgstr ""
+
+#: ../../configuration.rst:997
+# d2113879ec38438a85b780a116ae5c65
+msgid "**SR Name-Label.** Enter the name-label of the SR that has been set up outside CloudStack."
+msgstr ""
+
+#: ../../configuration.rst:1006
+# cf5d1b3006a142f8a763f03668105b49
+msgid "SharedMountPoint"
+msgstr ""
+
+#: ../../configuration.rst:1008
+# a09c62d550c445b09625c3c9ac5a79ef
+msgid "**Path.** The path on each host that is where this primary storage is mounted. For example, \"/mnt/primary\"."
+msgstr ""
+
+#: ../../configuration.rst:1017
+# 4e50581b026c4c648544298a1733b7ea
+msgid "VMFS"
+msgstr ""
+
+#: ../../configuration.rst:1019
+# 80e1d3bc39d448e9b8ed33e8619baf1b
+msgid "**Server.** The IP address or DNS name of the vCenter server."
+msgstr ""
+
+#: ../../configuration.rst:1023
+# 7c7e585d505640adb10fc3f6b3641320
+msgid "**Path.** A combination of the datacenter name and the datastore name. The format is \"/\" datacenter name \"/\" datastore name. For example, \"/cloud.dc.VM/cluster1datastore\"."
+msgstr ""
+
+#: ../../configuration.rst:1035
+#: ../../configuration.rst:1719
+# 0171ce820c2c4a7696118d1c25614ff0
+# 39eb891fbcd74644a92e4135608b74d5
+msgid "The tag sets on primary storage across clusters in a Zone must be identical. For example, if cluster A provides primary storage that has tags T1 and T2, all other clusters in the Zone must also provide primary storage that has tags T1 and T2."
+msgstr ""
+
+#: ../../configuration.rst:1042
+# 545dbc66d5a745cf8d40c2e8d3e47fa0
+msgid "In a new zone, CloudStack adds the first secondary storage server for you. For an overview of what secondary storage is, see `“About Secondary Storage” <http://docs.cloudstack.apache.org/en/latest/concepts.html?highlight=about%20pods#about-secondary-storage>`_."
+msgstr ""
+
+#: ../../configuration.rst:1045
+# 823b1d4a44e3422a9edc9639cf1eede3
+msgid "Before you can fill out this screen, you need to prepare the secondary storage by setting up NFS shares and installing the latest CloudStack System VM template. See Adding Secondary Storage :"
+msgstr ""
+
+#: ../../configuration.rst:1051
+# d5ddaf659d0b4a2f9410a5c11c11e461
+msgid "**NFS Server.** The IP address of the server or fully qualified domain name of the server."
+msgstr ""
+
+#: ../../configuration.rst:1060
+# 5cc7167a227445f5832190b7bb063edd
+msgid "Click Launch."
+msgstr ""
+
+#: ../../configuration.rst:1065
+# 8cc40a05112742019e78cdf6894c0d6a
+msgid "Adding a Pod"
+msgstr ""
+
+#: ../../configuration.rst:1067
+# 6aa3cd5eeb4845e2bca43d255c154880
+msgid "When you created a new zone, CloudStack adds the first pod for you. You can add more pods at any time using the procedure in this section."
+msgstr ""
+
+#: ../../configuration.rst:1072
+# 021a4945a1ff4e58bbb34499921172e6
+msgid "Log in to the CloudStack UI. See `“Log In to the UI” <http://docs.cloudstack.apache.org/projects/cloudstack-administration/en/latest/ui.html#log-in-to-the-ui>`_."
+msgstr ""
+
+#: ../../configuration.rst:1076
+# 85d50e8b49d74c3993bc9b5ab25e5fc8
+msgid "In the left navigation, choose Infrastructure. In Zones, click View More, then click the zone to which you want to add a pod."
+msgstr ""
+
+#: ../../configuration.rst:1081
+# 4fc2ea5eed7140159d0cb5082dbad76f
+msgid "Click the Compute and Storage tab. In the Pods node of the diagram, click View All."
+msgstr ""
+
+#: ../../configuration.rst:1086
+# ff9686a2bc574bd184ca92ef5167bcf9
+msgid "Click Add Pod."
+msgstr ""
+
+#: ../../configuration.rst:1090
+# 7ee82f9cc1e1471baf438efd4b23a8fb
+msgid "Enter the following details in the dialog."
+msgstr ""
+
+#: ../../configuration.rst:1094
+# 95c458cb36aa49eab82504d1418f26a9
+msgid "**Name.** The name of the pod."
+msgstr ""
+
+#: ../../configuration.rst:1098
+# 6e8c40c9ee9c4c2f8c156976b6d3543b
+msgid "**Gateway.** The gateway for the hosts in that pod."
+msgstr ""
+
+#: ../../configuration.rst:1102
+# 27a9f5939df04e5f94a11c291941e81c
+msgid "**Netmask.** The network prefix that defines the pod's subnet. Use CIDR notation."
+msgstr ""
+
+#: ../../configuration.rst:1114
+#: ../../configuration.rst:1163
+#: ../../configuration.rst:1726
+# 662b2d56034649b093b45febe21ca216
+# b127e13dd2f0460784ecb2ab7611be91
+# a758abffa675494ab4ece1328d1aacc7
+msgid "Click OK."
+msgstr ""
+
+#: ../../configuration.rst:1119
+# 5bd1d350804f433da261b7a4add24572
+msgid "Adding a Cluster"
+msgstr ""
+
+#: ../../configuration.rst:1121
+# 3577ece05aeb45ecb8111541525be47e
+msgid "You need to tell CloudStack about the hosts that it will manage. Hosts exist inside clusters, so before you begin adding hosts to the cloud, you must add at least one cluster."
+msgstr ""
+
+#: ../../configuration.rst:1126
+# c48b9a0598014690b0cdef9ca56ecee3
+msgid "Add Cluster: KVM or XenServer"
+msgstr ""
+
+#: ../../configuration.rst:1128
+# 055652e4701b4e77ae209a3d051da0a2
+msgid "These steps assume you have already installed the hypervisor on the hosts and logged in to the CloudStack UI."
+msgstr ""
+
+#: ../../configuration.rst:1133
+#: ../../configuration.rst:1205
+# 3eeb9c34a0954b7c8110e08a1b67f793
+# 9195ed5d3bf74deeb07aeb3d923107aa
+msgid "In the left navigation, choose Infrastructure. In Zones, click View More, then click the zone in which you want to add the cluster."
+msgstr ""
+
+#: ../../configuration.rst:1138
+#: ../../configuration.rst:1611
+# 6ce7dcfa7ba9471680bbb2d479610298
+# d76a87db16a14e2d81cfaaf4ae1ff37d
+msgid "Click the Compute tab."
+msgstr ""
+
+#: ../../configuration.rst:1142
+# 6781697240844815b4e33a65740b3568
+msgid "In the Clusters node of the diagram, click View All."
+msgstr ""
+
+#: ../../configuration.rst:1146
+#: ../../configuration.rst:1219
+# 86684fe2765e42cbbf0518ca95fde164
+# fceb91152e4946e4ae3ca08780f8ddb5
+msgid "Click Add Cluster."
+msgstr ""
+
+#: ../../configuration.rst:1150
+# df2e4414d83d49f7a69254062073c25d
+msgid "Choose the hypervisor type for this cluster."
+msgstr ""
+
+#: ../../configuration.rst:1154
+# 4b1d42320c944742a0c9da0c6aad03ab
+msgid "Choose the pod in which you want to create the cluster."
+msgstr ""
+
+#: ../../configuration.rst:1158
+# ddcd8e67c1e14f708d5f640dda1ace24
+msgid "Enter a name for the cluster. This can be text of your choosing and is not used by CloudStack."
+msgstr ""
+
+#: ../../configuration.rst:1166
+# 52e22dae198644b5b21619fdb5427bff
+msgid "Add Cluster: vSphere"
+msgstr ""
+
+#: ../../configuration.rst:1168
+# f1d8499b4f3a4527b31f6bbc13020c92
+msgid "Host management for vSphere is done through a combination of vCenter and the CloudStack admin UI. CloudStack requires that all hosts be in a CloudStack cluster, but the cluster may consist of a single host. As an administrator you must decide if you would like to use clusters of one host or of multiple hosts. Clusters of multiple hosts allow for features like live migration. Clusters also require shared storage such as NFS or iSCSI."
+msgstr ""
+
+#: ../../configuration.rst:1176
+# 639cc06638a24634b344409d5fc0f29b
+msgid "For vSphere servers, we recommend creating the cluster of hosts in vCenter and then adding the entire cluster to CloudStack. Follow these requirements:"
+msgstr ""
+
+#: ../../configuration.rst:1182
+# a552a9750ece4715bbd09d94674c0204
+msgid "Do not put more than 8 hosts in a vSphere cluster"
+msgstr ""
+
+#: ../../configuration.rst:1186
+# 07fedb4ed78e43309d2c117377a2665f
+msgid "Make sure the hypervisor hosts do not have any VMs already running before you add them to CloudStack."
+msgstr ""
+
+#: ../../configuration.rst:1189
+# 024f0bed3a7e461fb5cb771703a34735
+msgid "To add a vSphere cluster to CloudStack:"
+msgstr ""
+
+#: ../../configuration.rst:1193
+# 99e3af8fb94a47b6af9b96993aa3ddf9
+msgid "Create the cluster of hosts in vCenter. Follow the vCenter instructions to do this. You will create a cluster that looks something like this in vCenter."
+msgstr ""
+
+#: ../../configuration.rst:1197
+# af7d7917635a47e99d44b5ef15f45be1
+msgid "|vsphereclient.png: vSphere client|"
+msgstr ""
+
+#: ../../configuration.rst:1201
+# a6f802a9b02f479a84bcaf1fdf55f411
+msgid "Log in to the UI."
+msgstr ""
+
+#: ../../configuration.rst:1210
+# c23593701771448492c69e88eeb2fdc7
+msgid "Click the Compute tab, and click View All on Pods. Choose the pod to which you want to add the cluster."
+msgstr ""
+
+#: ../../configuration.rst:1215
+# 0eb489140e8347b58fd4f55e90ecdb3d
+msgid "Click View Clusters."
+msgstr ""
+
+#: ../../configuration.rst:1223
+# eaa31efa90f943a28e73234e4948e3b3
+msgid "In Hypervisor, choose VMware."
+msgstr ""
+
+#: ../../configuration.rst:1227
+# 484d49c764c44bf1a22f92192128c36f
+msgid "Provide the following information in the dialog. The fields below make reference to the values from vCenter."
+msgstr ""
+
+#: ../../configuration.rst:1230
+# 487fe93679ba4e0da222421e9e4c4fef
+msgid "|addcluster.png: add a cluster|"
+msgstr ""
+
+#: ../../configuration.rst:1234
+# a2588a5230c44e0ab6631f37191c9f05
+msgid "**Cluster Name**: Enter the name of the cluster you created in vCenter. For example, \"cloud.cluster.2.2.1\""
+msgstr ""
+
+#: ../../configuration.rst:1239
+# 139c5b5ced7c44a3b1106cbfebd485ef
+msgid "**vCenter Username**: Enter the username that CloudStack should use to connect to vCenter. This user must have all the administrative privileges."
+msgstr ""
+
+#: ../../configuration.rst:1245
+# 0f46da6afc5f4dac9ccf803cc4601b66
+msgid "**CPU overcommit ratio**: Enter the CPU overcommit ratio for the cluster. The value you enter determines the CPU consumption of each VM in the selected cluster. By increasing the over-provisioning ratio, more resource capacity will be used. If no value is specified, the value is defaulted to 1, which implies no over-provisioning is done."
+msgstr ""
+
+#: ../../configuration.rst:1254
+# c80fd12b0e2645fdb4f5da92f9a48c30
+msgid "**RAM overcommit ratio**: Enter the RAM overcommit ratio for the cluster. The value you enter determines the memory consumption of each VM in the selected cluster. By increasing the over-provisioning ratio, more resource capacity will be used. If no value is specified, the value is defaulted to 1, which implies no over-provisioning is done."
+msgstr ""
+
+#: ../../configuration.rst:1263
+# ed8c978a33c642e1b4c42009224566d8
+msgid "**vCenter Host**: Enter the hostname or IP address of the vCenter server."
+msgstr ""
+
+#: ../../configuration.rst:1268
+# 9f497668e61c49d29335e24237d60c1f
+msgid "**vCenter Password**: Enter the password for the user named above."
+msgstr ""
+
+#: ../../configuration.rst:1272
+# 71e07ec1b69543a0bfd82523b8b2e186
+msgid "**vCenter Datacenter**: Enter the vCenter datacenter that the cluster is in. For example, \"cloud.dc.VM\"."
+msgstr ""
+
+#: ../../configuration.rst:1277
+# d4bbd28c84c841f18df067f9ebd23e01
+msgid "**Override Public Traffic**: Enable this option to override the zone-wide public traffic for the cluster you are creating."
+msgstr ""
+
+#: ../../configuration.rst:1282
+# 226d9fcde0fe480dbfc4bdb58e61101a
+msgid "**Public Traffic vSwitch Type**: This option is displayed only if you enable the Override Public Traffic option. Select a desirable switch. If the vmware.use.dvswitch global parameter is true, the default option will be VMware vNetwork Distributed Virtual Switch."
+msgstr ""
+
+#: ../../configuration.rst:1287
+#: ../../configuration.rst:1319
+# ef5ed1b406c04875b05b7f99083e9798
+# d0128340659843899d633b61f40d6f7d
+msgid "If you have enabled Nexus dvSwitch in the environment, the following parameters for dvSwitch configuration are displayed:"
+msgstr ""
+
+#: ../../configuration.rst:1292
+#: ../../configuration.rst:1324
+# 1a28e958e5c142e9b87e1fb54997fc70
+# f629408d44214fe88b1d7ae5bc5ff009
+msgid "Nexus dvSwitch IP Address: The IP address of the Nexus VSM appliance."
+msgstr ""
+
+#: ../../configuration.rst:1297
+#: ../../configuration.rst:1329
+# 6fc84ac396d34298bc9d963e5af5a56c
+# 1ed7b8810e7943a1aa4c787324501a85
+msgid "Nexus dvSwitch Username: The username required to access the Nexus VSM appliance."
+msgstr ""
+
+#: ../../configuration.rst:1302
+#: ../../configuration.rst:1334
+# 30de309ba01c451c9fa7b7401055d1df
+# 23e30b096bb54eb0a89fd8e31298e87d
+msgid "Nexus dvSwitch Password: The password associated with the username specified above."
+msgstr ""
+
+#: ../../configuration.rst:1307
+# d1b265609f2141fd90ed9172448bbca4
+msgid "**Override Guest Traffic**: Enable this option to override the zone-wide guest traffic for the cluster you are creating."
+msgstr ""
+
+#: ../../configuration.rst:1312
+# 6cc7a2072e8041fe99c4417e58e169c5
+msgid "**Guest Traffic vSwitch Type**: This option is displayed only if you enable the Override Guest Traffic option. Select a desirable switch."
+msgstr ""
+
+#: ../../configuration.rst:1316
+# 2e4dbe764fd24fce83909adbaa5d459a
+msgid "If the vmware.use.dvswitch global parameter is true, the default option will be VMware vNetwork Distributed Virtual Switch."
+msgstr ""
+
+#: ../../configuration.rst:1339
+# 6c5ead7c78fb4c3893e3e5755324deb3
+msgid "There might be a slight delay while the cluster is provisioned. It will automatically display in the UI."
+msgstr ""
+
+#: ../../configuration.rst:1345
+# f18a40a45b3b4c61b08b258f179355ef
+msgid "Adding a Host"
+msgstr ""
+
+#: ../../configuration.rst:1349
+# 6b7c9eb46e0e4f11a6576586dfc74b90
+msgid "Before adding a host to the CloudStack configuration, you must first install your chosen hypervisor on the host. CloudStack can manage hosts running VMs under a variety of hypervisors."
+msgstr ""
+
+#: ../../configuration.rst:1353
+# 522d5b3c849c4f7e9f60227d6cd73806
+msgid "The CloudStack Installation Guide provides instructions on how to install each supported hypervisor and configure it for use with CloudStack. See the appropriate section in the Installation Guide for information about which version of your chosen hypervisor is supported, as well as crucial additional steps to configure the hypervisor hosts for use with CloudStack."
+msgstr ""
+
+#: ../../configuration.rst:1362
+# bc711d58a2c34afd8f452fe3e9de12b4
+msgid "Be sure you have performed the additional CloudStack-specific configuration steps described in the hypervisor installation section for your particular hypervisor."
+msgstr ""
+
+#: ../../configuration.rst:1366
+# f214d5f50d644ebb9e0348cf22f7584a
+msgid "Now add the hypervisor host to CloudStack. The technique to use varies depending on the hypervisor."
+msgstr ""
+
+#: ../../configuration.rst:1371
+# f19ae647c1194e09b4fa86351f6e66bf
+msgid ":ref:`adding-a-host-xenserver-kvm`"
+msgstr ""
+
+#: ../../configuration.rst:1375
+# 74db7e53daa6430db9890cf5d4b68937
+msgid ":ref:`adding-a-host-vsphere`"
+msgstr ""
+
+#: ../../configuration.rst:1380
+# 86203e473ded428a87d9ddc7387b8945
+msgid "Adding a Host (XenServer or KVM)"
+msgstr ""
+
+#: ../../configuration.rst:1382
+# e9d60303c58a447b98a846b68c542923
+msgid "XenServer and KVM hosts can be added to a cluster at any time."
+msgstr ""
+
+#: ../../configuration.rst:1385
+# e8574c2491f84847b1fc81dd87b07300
+msgid "Requirements for XenServer and KVM Hosts"
+msgstr ""
+
+#: ../../configuration.rst:1389
+# 0800caa0d34946708f32a040b507e3a5
+msgid "Make sure the hypervisor host does not have any VMs already running before you add it to CloudStack."
+msgstr ""
+
+#: ../../configuration.rst:1391
+# 6830a4647d3740fea37e17845ef42474
+msgid "Configuration requirements:"
+msgstr ""
+
+#: ../../configuration.rst:1395
+# 9b03954d5f1c42be949de1519d901e77
+msgid "Each cluster must contain only hosts with the identical hypervisor."
+msgstr ""
+
+#: ../../configuration.rst:1399
+# 2aa84dcaa1ef4b64864afbf376809f28
+msgid "For XenServer, do not put more than 8 hosts in a cluster."
+msgstr ""
+
+#: ../../configuration.rst:1403
+# ab9e4541b2f749c7ac049e975cc25029
+msgid "For KVM, do not put more than 16 hosts in a cluster."
+msgstr ""
+
+#: ../../configuration.rst:1405
+# 43f791e8a196457488a703279725b9c8
+msgid "For hardware requirements, see the installation section for your hypervisor in the CloudStack Installation Guide."
+msgstr ""
+
+#: ../../configuration.rst:1409
+# bf113c0fb16d42a2b85f91ae907901c0
+msgid "XenServer Host Additional Requirements"
+msgstr ""
+
+#: ../../configuration.rst:1411
+# ef5a7bd952eb4406a4876f09caac96fc
+msgid "If network bonding is in use, the administrator must cable the new host identically to other hosts in the cluster."
+msgstr ""
+
+#: ../../configuration.rst:1414
+# 5ce3c90d78664585b286502de164418b
+msgid "For all additional hosts to be added to the cluster, run the following command. This will cause the host to join the master in a XenServer pool."
+msgstr ""
+
+#: ../../configuration.rst:1424
+# b0f910819c24499290ea1517cb3894a1
+msgid "When copying and pasting a command, be sure the command has pasted as a single line before executing. Some document viewers may introduce unwanted line breaks in copied text."
+msgstr ""
+
+#: ../../configuration.rst:1426
+# ad1d348fa25e4e3d8fb6486fc087844e
+msgid "With all hosts added to the XenServer pool, run the cloud-setup-bond script. This script will complete the configuration and setup of the bonds on the new hosts in the cluster."
+msgstr ""
+
+#: ../../configuration.rst:1432
+# c00ff2f9f8294ceb822894783fb6a964
+msgid "Copy the script from the Management Server in /usr/share/cloudstack-common/scripts/vm/hypervisor/xenserver/cloud-setup-bonding.sh to the master host and ensure it is executable."
+msgstr ""
+
+#: ../../configuration.rst:1438
+# 32ecd087d8b8425596b9193e24069aea
+msgid "Run the script:"
+msgstr ""
+
+#: ../../configuration.rst:1445
+# 58b5e274046649d7a945955ae04af421
+msgid "KVM Host Additional Requirements"
+msgstr ""
+
+#: ../../configuration.rst:1449
+# 60b344634f504d1ca30de484e7f04333
+msgid "If shared mountpoint storage is in use, the administrator should ensure that the new host has all the same mountpoints (with storage mounted) as the other hosts in the cluster."
+msgstr ""
+
+#: ../../configuration.rst:1455
+# 634564b4d8dc44879b842a564a6a8f9f
+msgid "Make sure the new host has the same network configuration (guest, private, and public network) as other hosts in the cluster."
+msgstr ""
+
+#: ../../configuration.rst:1460
+# 43f6bcb4e87b4a699d9ba84ab8e5d99c
+msgid "If you are using OpenVswitch bridges edit the file agent.properties on the KVM host and set the parameter network.bridge.type to openvswitch before adding the host to CloudStack"
+msgstr ""
+
+#: ../../configuration.rst:1465
+# 825c62bc20d74cf2a9c087190e0ebd0e
+msgid "Adding a XenServer or KVM Host"
+msgstr ""
+
+#: ../../configuration.rst:1469
+# 60390845f5ce4c47b1a35cb34c2907ef
+msgid "If you have not already done so, install the hypervisor software on the host. You will need to know which version of the hypervisor software version is supported by CloudStack and what additional configuration is required to ensure the host will work with CloudStack. To find these installation details, see the appropriate section for your hypervisor in the CloudStack Installation Guide."
+msgstr ""
+
+#: ../../configuration.rst:1478
+# 6cf7001771ee4f22aaeb0b265bf73856
+msgid "Log in to the CloudStack UI as administrator."
+msgstr ""
+
+#: ../../configuration.rst:1482
+# 758173927d4045c2bd035ce5cef81f81
+msgid "In the left navigation, choose Infrastructure. In Zones, click View More, then click the zone in which you want to add the host."
+msgstr ""
+
+#: ../../configuration.rst:1487
+# 647c6eff585d4f0f842f38362662e622
+msgid "Click the Compute tab. In the Clusters node, click View All."
+msgstr ""
+
+#: ../../configuration.rst:1491
+# 40cfa2a9cd29488790252784ab7a98af
+msgid "Click the cluster where you want to add the host."
+msgstr ""
+
+#: ../../configuration.rst:1495
+# 057eca2c4f2e44e1a5b53804376e0bc5
+msgid "Click View Hosts."
+msgstr ""
+
+#: ../../configuration.rst:1499
+# 7a8c33348f2d44e4b2d70a58810caaaa
+msgid "Click Add Host."
+msgstr ""
+
+#: ../../configuration.rst:1503
+# ec6e0c7aaf9c4174a554f0e0723f5afc
+msgid "Provide the following information."
+msgstr ""
+
+#: ../../configuration.rst:1507
+# 65ca0cee75de4f4994bda31d47ca525b
+msgid "Host Name. The DNS name or IP address of the host."
+msgstr ""
+
+#: ../../configuration.rst:1511
+# 07cf33fc7b434b4192dafb636a11c8db
+msgid "Username. Usually root."
+msgstr ""
+
+#: ../../configuration.rst:1515
+# 11dcc36792dc4e4c935b94c172bba23b
+msgid "Password. This is the password for the user from your XenServer or KVM install)."
+msgstr ""
+
+#: ../../configuration.rst:1520
+# 3e82fd166c174e339f57de8eaeeed24a
+msgid "Host Tags (Optional). Any labels that you use to categorize hosts for ease of maintenance. For example, you can set to the cloud's HA tag (set in the ha.tag global configuration parameter) if you want this host to be used only for VMs with the \"high availability\" feature enabled. For more information, see HA-Enabled Virtual Machines as well as HA for Hosts."
+msgstr ""
+
+#: ../../configuration.rst:1527
+# 00e27ee9496447deabd80ae86c90aea6
+msgid "There may be a slight delay while the host is provisioned. It should automatically display in the UI."
+msgstr ""
+
+#: ../../configuration.rst:1532
+# 02dcab0b7281423cbe53bcdc66598c06
+msgid "Repeat for additional hosts."
+msgstr ""
+
+#: ../../configuration.rst:1537
+# 1170b1085c8a49929806adaeba4984f4
+msgid "Adding a Host (vSphere)"
+msgstr ""
+
+#: ../../configuration.rst:1539
+# 516b13b6eed94ded89662174643e96f8
+msgid "For vSphere servers, we recommend creating the cluster of hosts in vCenter and then adding the entire cluster to CloudStack. See Add Cluster: vSphere."
+msgstr ""
+
+#: ../../configuration.rst:1546
+# 8b04ddb51a7b4c9885fc62104fc4b42a
+msgid "Add Primary Storage"
+msgstr ""
+
+#: ../../configuration.rst:1549
+# 9c723d34835c4f49a1d9030ad5ec33ab
+msgid "System Requirements for Primary Storage"
+msgstr ""
+
+#: ../../configuration.rst:1551
+# 277507fb2ddb4df9add4906b2decd2f1
+msgid "Hardware requirements:"
+msgstr ""
+
+#: ../../configuration.rst:1555
+# bbb48644cf8845ed8b32fecfbb85505f
+msgid "Any standards-compliant iSCSI, SMB, or NFS server that is supported by the underlying hypervisor."
+msgstr ""
+
+#: ../../configuration.rst:1560
+# ef23cd94da734d9fbf26c214e18108aa
+msgid "The storage server should be a machine with a large number of disks. The disks should ideally be managed by a hardware RAID controller."
+msgstr ""
+
+#: ../../configuration.rst:1565
+# ff3dd31bccff4213a9bdb209155f64f9
+msgid "Minimum required capacity depends on your needs."
+msgstr ""
+
+#: ../../configuration.rst:1567
+# 56b2085ed3724dcfa4c100c74ba57226
+msgid "When setting up primary storage, follow these restrictions:"
+msgstr ""
+
+#: ../../configuration.rst:1571
+# 176285b9f428472889a6cef403854e17
+msgid "Primary storage cannot be added until a host has been added to the cluster."
+msgstr ""
+
+#: ../../configuration.rst:1576
+# a2938854f0cf49b5bffc1a09ab4af83b
+msgid "If you do not provision shared primary storage, you must set the global configuration parameter system.vm.local.storage.required to true, or else you will not be able to start VMs."
+msgstr ""
+
+#: ../../configuration.rst:1581
+# 253962ae02ef41b9a0e2f8fd5a42f944
+msgid "Adding Primary Storage"
+msgstr ""
+
+#: ../../configuration.rst:1583
+# c07bcd7f4940487cb57bb5ce760ffbc6
+msgid "When you create a new zone, the first primary storage is added as part of that procedure. You can add primary storage servers at any time, such as when adding a new cluster or adding more servers to an existing cluster."
+msgstr ""
+
+#: ../../configuration.rst:1590
+# a85b38c43ef141f08b9cad6f28867d41
+msgid "When using preallocated storage for primary storage, be sure there is nothing on the storage (ex. you have an empty SAN volume or an empty NFS share). Adding the storage to CloudStack will destroy any existing data."
+msgstr ""
+
+#: ../../configuration.rst:1594
+# 8a90764a4357462a876fb062262ee307
+msgid "Primary storage can also be added at the zone level through the CloudStack API (adding zone-level primary storage is not yet supported through the CloudStack UI)."
+msgstr ""
+
+#: ../../configuration.rst:1596
+# a137ab069d1b4fa7b0134fa599d960df
+msgid "Once primary storage has been added at the zone level, it can be managed through the CloudStack UI."
+msgstr ""
+
+#: ../../configuration.rst:1601
+# 6e323f281d44448fb0a6e448744fb964
+msgid "Log in to the CloudStack UI (see `“Log In to the UI” <http://docs.cloudstack.apache.org/projects/cloudstack-administration/en/latest/ui.html#log-in-to-the-ui>`_)."
+msgstr ""
+
+#: ../../configuration.rst:1605
+# ba87f30e4c144e338aefc2e75a45a6ae
+msgid "In the left navigation, choose Infrastructure. In Zones, click View More, then click the zone in which you want to add the primary storage."
+msgstr ""
+
+#: ../../configuration.rst:1615
+# 7a949d3810ac4b4db5981d0739b118fa
+msgid "In the Primary Storage node of the diagram, click View All."
+msgstr ""
+
+#: ../../configuration.rst:1619
+# e5f9d2b146a24dbfb81357cd4b563f53
+msgid "Click Add Primary Storage."
+msgstr ""
+
+#: ../../configuration.rst:1623
+# 344c6f879a52497cba705fb55a6b9dca
+msgid "Provide the following information in the dialog. The information required varies depending on your choice in Protocol."
+msgstr ""
+
+#: ../../configuration.rst:1628
+# 164b87010cbd4d3c8f7120a0dcc97650
+msgid "**Scope.** Indicate whether the storage is available to all hosts in the zone or only to hosts in a single cluster."
+msgstr ""
+
+#: ../../configuration.rst:1633
+# 75eba167538b4751b4d289eb1d35f615
+msgid "**Pod.** (Visible only if you choose Cluster in the Scope field.) The pod for the storage device."
+msgstr ""
+
+#: ../../configuration.rst:1638
+# f7353d4ec1ea43d6b28c7f283a60e066
+msgid "**Cluster.** (Visible only if you choose Cluster in the Scope field.) The cluster for the storage device."
+msgstr ""
+
+#: ../../configuration.rst:1647
+# f54c8190592a41d0869c9635b388c97b
+msgid "**Protocol.** For XenServer, choose either NFS, iSCSI, or PreSetup. For KVM, choose NFS or SharedMountPoint. For vSphere choose either VMFS (iSCSI or FiberChannel) or NFS. For Hyper-V, choose SMB."
+msgstr ""
+
+#: ../../configuration.rst:1654
+# 7c801be5e02349e8b8c110463571f66a
+msgid "**Server (for NFS, iSCSI, or PreSetup).** The IP address or DNS name of the storage device."
+msgstr ""
+
+#: ../../configuration.rst:1659
+# c2e946eb16df4cc083b70045e6a72548
+msgid "**Server (for VMFS).** The IP address or DNS name of the vCenter server."
+msgstr ""
+
+#: ../../configuration.rst:1664
+# 83059961bf0d4bfebd3e4790065df7e5
+msgid "**Path (for NFS).** In NFS this is the exported path from the server."
+msgstr ""
+
+#: ../../configuration.rst:1669
+# fc3c902db29646d894b6073409800676
+msgid "**Path (for VMFS).** In vSphere this is a combination of the datacenter name and the datastore name. The format is \"/\" datacenter name \"/\" datastore name. For example, \"/cloud.dc.VM/cluster1datastore\"."
+msgstr ""
+
+#: ../../configuration.rst:1676
+# 3162d539e68c48bb85baa580cf9799dc
+msgid "**Path (for SharedMountPoint).** With KVM this is the path on each host that is where this primary storage is mounted. For example, \"/mnt/primary\"."
+msgstr ""
+
+#: ../../configuration.rst:1682
+# 35dcd43e792449a2897fb8ecadaa07d1
+msgid "**SMB Username** (for SMB/CIFS): Applicable only if you select SMB/CIFS provider. The username of the account which has the necessary permissions to the SMB shares. The user must be part of the Hyper-V administrator group."
+msgstr ""
+
+#: ../../configuration.rst:1689
+# e7fcc0edb3204a6089af8415f2a4ed14
+msgid "**SMB Password** (for SMB/CIFS): Applicable only if you select SMB/CIFS provider. The password associated with the account."
+msgstr ""
+
+#: ../../configuration.rst:1694
+# 5f46e30f1f384e70be55aaafcb9a88a2
+msgid "**SMB Domain**\\ (for SMB/CIFS): Applicable only if you select SMB/CIFS provider. The Active Directory domain that the SMB share is a part of."
+msgstr ""
+
+#: ../../configuration.rst:1700
+# 86153de53fb44cd0a185befbbc5bccd6
+msgid "**SR Name-Label (for PreSetup).** Enter the name-label of the SR that has been set up outside CloudStack."
+msgstr ""
+
+#: ../../configuration.rst:1705
+# 06e1d069cd564b698d301dbf45b20ca9
+msgid "**Target IQN (for iSCSI).** In iSCSI this is the IQN of the target. For example, iqn.1986-03.com.sun:02:01ec9bb549-1271378984."
+msgstr ""
+
+#: ../../configuration.rst:1710
+# 05c29f124cee49a7a18ee6ba850852b9
+msgid "**Lun # (for iSCSI).** In iSCSI this is the LUN number. For example, 3."
+msgstr ""
+
+#: ../../configuration.rst:1715
+# e62e1da0f5934ff2a0f013ec3ec3058b
+msgid "**Tags (optional).** The comma-separated list of tags for this storage device. It should be an equivalent set or superset of the tags on your disk offerings.."
+msgstr ""
+
+#: ../../configuration.rst:1729
+# 151b19392c7741898b3a10ea36ecf671
+msgid "Configuring a Storage Plug-in"
+msgstr ""
+
+#: ../../configuration.rst:1733
+# eab75074aa7844c99ffd23fa7e1a1070
+msgid "Primary storage that is based on a custom plug-in (ex. SolidFire) must be added through the CloudStack API (described later in this section). There is no support at this time through the CloudStack UI to add this type of primary storage (although most of its features are available through the CloudStack UI)."
+msgstr ""
+
+#: ../../configuration.rst:1737
+# 90c8c28d7c834c57aa7a38031a1f2bdc
+msgid "At this time, a custom storage plug-in, such as the SolidFire storage plug-in, can only be leveraged for data disks (through Disk Offerings)."
+msgstr ""
+
+#: ../../configuration.rst:1741
+# 6885249ac1654e7d981da00285c1fcb7
+msgid "The SolidFire storage plug-in for CloudStack is part of the standard CloudStack install. There is no additional work required to add this component."
+msgstr ""
+
+#: ../../configuration.rst:1743
+# 3ccb3e59e46c41b6a4debd621cbb6d36
+msgid "Adding primary storage that is based on the SolidFire plug-in enables CloudStack to provide hard quality-of-service (QoS) guarantees."
+msgstr ""
+
+#: ../../configuration.rst:1746
+# 4f6abd169ec947368df1728cc97f109b
+msgid "When used with Disk Offerings, an administrator is able to build an environment in which a data disk that a user creates leads to the dynamic creation of a SolidFire volume, which has guaranteed performance. Such a SolidFire volume is associated with one (and only ever one) CloudStack volume, so performance of the CloudStack volume does not vary depending on how heavily other tenants are using the system."
+msgstr ""
+
+#: ../../configuration.rst:1754
+# c4d95dce04ba439592412554601d3611
+msgid "The createStoragePool API has been augmented to support plugable storage providers. The following is a list of parameters to use when adding storage to CloudStack that is based on the SolidFire plug-in:"
+msgstr ""
+
+#: ../../configuration.rst:1760
+# f049ceffa0374c2bbb8a8ac7a702279a
+msgid "command=createStoragePool"
+msgstr ""
+
+#: ../../configuration.rst:1764
+# 01738c180e4a4dc6b9e8e683b2dd79c8
+msgid "scope=zone"
+msgstr ""
+
+#: ../../configuration.rst:1768
+# 5fc8f15b325d42898576fbbd6af29528
+msgid "zoneId=[your zone id]"
+msgstr ""
+
+#: ../../configuration.rst:1772
+# 683b46e47f834303a2e5a78e676ae880
+msgid "name=[name for primary storage]"
+msgstr ""
+
+#: ../../configuration.rst:1776
+# 18c42d58c8f9436993bd1200dfcbbfc7
+msgid "hypervisor=Any"
+msgstr ""
+
+#: ../../configuration.rst:1780
+# 532b8915aa504f19bbf774602615a492
+msgid "provider=SolidFire"
+msgstr ""
+
+#: ../../configuration.rst:1784
+# 45df5cb6ceae470f9204c0840912a7d3
+msgid "capacityIops=[whole number of IOPS from the SAN to give to CloudStack]"
+msgstr ""
+
+#: ../../configuration.rst:1789
+# 50ca458f2225420889935fb44a7810c9
+msgid "capacityBytes=[whole number of bytes from the SAN to give to CloudStack]"
+msgstr ""
+
+#: ../../configuration.rst:1792
+# 674644bd92384aff956b3309f086a608
+msgid "The url parameter is somewhat unique in that its value can contain additional key/value pairs."
+msgstr ""
+
+#: ../../configuration.rst:1795
+# 4a1fcb6340ef4385b1f0d9aaec733be1
+msgid "url=[key/value pairs detailed below (values are URL encoded; for example, '=' is represented as '%3D')]"
+msgstr ""
+
+#: ../../configuration.rst:1800
+# 44fd4a0614654ff3b9ba5a5eb8ee416a
+msgid "MVIP%3D[Management Virtual IP Address] (can be suffixed with :[port number])"
+msgstr ""
+
+#: ../../configuration.rst:1805
+# 1a864bdb824c4997b4309c71a070a06d
+msgid "SVIP%3D[Storage Virtual IP Address] (can be suffixed with :[port number])"
+msgstr ""
+
+#: ../../configuration.rst:1810
+# 3384851f75af48caae7f08585f651d6e
+msgid "clusterAdminUsername%3D[cluster admin's username]"
+msgstr ""
+
+#: ../../configuration.rst:1814
+# 0c099d96bff44a8cac7cb4391c627fda
+msgid "clusterAdminPassword%3D[cluster admin's password]"
+msgstr ""
+
+#: ../../configuration.rst:1818
+# b68979dd06b9494ba5e828cc9a918b7d
+msgid "clusterDefaultMinIops%3D[Min IOPS (whole number) to set for a volume; used if Min IOPS is not specified by administrator or user]"
+msgstr ""
+
+#: ../../configuration.rst:1823
+# 9223ad75e60949b5a27d943713e163e6
+msgid "clusterDefaultMaxIops%3D[Max IOPS (whole number) to set for a volume; used if Max IOPS is not specified by administrator or user]"
+msgstr ""
+
+#: ../../configuration.rst:1828
+# cce939eaa5a841b7857fa7757475f40a
+msgid "clusterDefaultBurstIopsPercentOfMaxIops%3D[Burst IOPS is determined by (Min IOPS \\* clusterDefaultBurstIopsPercentOfMaxIops parameter) (can be a decimal value)]"
+msgstr ""
+
+#: ../../configuration.rst:1835
+# a104528004744c538bcd7c33c8d690d0
+msgid "Add Secondary Storage"
+msgstr ""
+
+#: ../../configuration.rst:1838
+# 404da4bceefa4d30aa205ed12b6aeb96
+msgid "System Requirements for Secondary Storage"
+msgstr ""
+
+#: ../../configuration.rst:1842
+# 48f4a123d83e421790cd8cf0d4bacbe6
+msgid "NFS storage appliance or Linux NFS server"
+msgstr ""
+
+#: ../../configuration.rst:1846
+# 36a7b6d973474e8a982f0774da4b314f
+msgid "SMB/CIFS (Hyper-V)"
+msgstr ""
+
+#: ../../configuration.rst:1850
+# 7489f77496564a7783a2d8996e1842b6
+msgid "(Optional) OpenStack Object Storage (Swift) (see http://swift.openstack.org)"
+msgstr ""
+
+#: ../../configuration.rst:1855
+# 686515fe92bb465a8076822151b26e00
+msgid "100GB minimum capacity"
+msgstr ""
+
+#: ../../configuration.rst:1859
+# 9c33f02b5336493f8b9039a890d83e7f
+msgid "A secondary storage device must be located in the same zone as the guest VMs it serves."
+msgstr ""
+
+#: ../../configuration.rst:1864
+# 949f4c4932f242258575c82418095bac
+msgid "Each Secondary Storage server must be available to all hosts in the zone."
+msgstr ""
+
+#: ../../configuration.rst:1868
+# b29b1459d23144d884bd9042a15e9fe1
+msgid "Adding Secondary Storage"
+msgstr ""
+
+#: ../../configuration.rst:1870
+# c971345996a14eef81e6440a9e6bc831
+msgid "When you create a new zone, the first secondary storage is added as part of that procedure. You can add secondary storage servers at any time to add more servers to an existing zone."
+msgstr ""
+
+#: ../../configuration.rst:1876
+# edf2a4517e6349f9a652899aa9a7ff7c
+msgid "Ensure that nothing is stored on the server. Adding the server to CloudStack will destroy any existing data."
+msgstr ""
+
+#: ../../configuration.rst:1880
+# 73d635cb09e74b47a17145a490c05037
+msgid "To prepare for the zone-based Secondary Staging Store, you should have created and mounted an NFS share during Management Server installation. See `“Prepare NFS Shares” <installation.html#prepare-nfs-shares>`_."
+msgstr ""
+
+#: ../../configuration.rst:1884
+# 1cdcb9eaeaad411c9b63e83ba3508970
+msgid "If you are using an Hyper-V host, ensure that you have created a SMB share."
+msgstr ""
+
+#: ../../configuration.rst:1889
+# 924792c2c045473cbabfc9465070db17
+msgid "Make sure you prepared the system VM template during Management Server installation. See `“Prepare the System VM Template” <installation.html#prepare-the-system-vm-template>`_."
+msgstr ""
+
+#: ../../configuration.rst:1894
+#: ../../configuration.rst:1977
+# 93e67281095a41d3b2fef2ca72b47e7e
+# a8bc19731c9341c78f19aeee52ce1a9b
+msgid "Log in to the CloudStack UI as root administrator."
+msgstr ""
+
+#: ../../configuration.rst:1898
+#: ../../configuration.rst:1981
+# eb50a154a546438ab86b4a1841bdaa8e
+# 545adbfec16b4cc09be027e2a6cbc5dd
+msgid "In the left navigation bar, click Infrastructure."
+msgstr ""
+
+#: ../../configuration.rst:1902
+#: ../../configuration.rst:1985
+# a3463a0d5bb4468fa70f57020c0bc3ac
+# bb1a22311ce24a04b95cb1a6b3b9f558
+msgid "In Secondary Storage, click View All."
+msgstr ""
+
+#: ../../configuration.rst:1906
+# 55ab9fd390db45c6b917dde88a2b1c65
+msgid "Click Add Secondary Storage."
+msgstr ""
+
+#: ../../configuration.rst:1910
+# 45efef2dbd704e9486e092051028383d
+msgid "Fill in the following fields:"
+msgstr ""
+
+#: ../../configuration.rst:1914
+# 4b8af38835af4840b3bfb425f40a828e
+msgid "Name. Give the storage a descriptive name."
+msgstr ""
+
+#: ../../configuration.rst:1918
+# f21b11c130704f20a7ceeb2c57f4c4ef
+msgid "Provider. Choose S3, Swift, NFS, or CIFS then fill in the related fields which appear. The fields will vary depending on the storage provider; for more information, consult the provider's documentation (such as the S3 or Swift website). NFS can be used for zone-based storage, and the others for region-wide storage. For Hyper-V, select SMB/CIFS."
+msgstr ""
+
+#: ../../configuration.rst:1927
+# 4ceb04cb16e947c989eb7ee4f427bcf3
+msgid "Heterogeneous Secondary Storage is not supported in Regions. You can use only a single NFS, S3, or Swift account per region."
+msgstr ""
+
+#: ../../configuration.rst:1931
+# 6015cb77d4304ed893fc2bbdf0b9cf03
+msgid "Create NFS Secondary Staging Store. This box must always be checked."
+msgstr ""
+
+#: ../../configuration.rst:1936
+# 95671b95fafa4be082785f5f9b6f856f
+msgid "Even if the UI allows you to uncheck this box, do not do so. This checkbox and the three fields below it must be filled in. Even when Swift or S3 is used as the secondary storage provider, an NFS staging storage in each zone is still required."
+msgstr ""
+
+#: ../../configuration.rst:1940
+#: ../../configuration.rst:2001
+# d3629e4c228546a78d94d4831195a86c
+# 34252d33d0c74325a99b37eda5505e39
+msgid "Zone. The zone where the NFS Secondary Staging Store is to be located."
+msgstr ""
+
+#: ../../configuration.rst:1945
+# 966a59ac33cc4268a8b09b70d5f635fc
+msgid "**SMB Username**: Applicable only if you select SMB/CIFS provider. The username of the account which has the necessary permissions to the SMB shares. The user must be part of the Hyper-V administrator group."
+msgstr ""
+
+#: ../../configuration.rst:1952
+# bb60190d3f834ab28a5f632797e18023
+msgid "**SMB Password**: Applicable only if you select SMB/CIFS provider. The password associated with the account."
+msgstr ""
+
+#: ../../configuration.rst:1957
+# cfc78758112d4a6ebe136409d75ceed5
+msgid "**SMB Domain**: Applicable only if you select SMB/CIFS provider. The Active Directory domain that the SMB share is a part of."
+msgstr ""
+
+#: ../../configuration.rst:1962
+#: ../../configuration.rst:2006
+# d355f66bc51d48f98f5f9a68d774d4bf
+# 5e043f6b7198448b922748ddfcc7cac4
+msgid "NFS server. The name of the zone's Secondary Staging Store."
+msgstr ""
+
+#: ../../configuration.rst:1966
+#: ../../configuration.rst:2010
+# 1dfad4e6554b4f7e8521b3dd405b2d6c
+# 0662ed9dab95436ca39419cb4edbe572
+msgid "Path. The path to the zone's Secondary Staging Store."
+msgstr ""
+
+#: ../../configuration.rst:1969
+# 1def4186b5594549b9429969eee13669
+msgid "Adding an NFS Secondary Staging Store for Each Zone"
+msgstr ""
+
+#: ../../configuration.rst:1971
+# 033e4435c65642298d1b90c80f9fab24
+msgid "Every zone must have at least one NFS store provisioned; multiple NFS servers are allowed per zone. To provision an NFS Staging Store for a zone:"
+msgstr ""
+
+#: ../../configuration.rst:1989
+# a79291836b5d4b219e4a7ab07029e285
+msgid "In Select View, choose Secondary Staging Store."
+msgstr ""
+
+#: ../../configuration.rst:1993
+# 68d2a29c405f467592311bd93b61945a
+msgid "Click the Add NFS Secondary Staging Store button."
+msgstr ""
+
+#: ../../configuration.rst:1997
+# 5272e9febd594c98b3c3ecc990299212
+msgid "Fill out the dialog box fields, then click OK:"
+msgstr ""
+
+#: ../../configuration.rst:2015
+# c258f5d1bfb4457c85bea1b5fb1ed946
+msgid "Initialize and Test"
+msgstr ""
+
+#: ../../configuration.rst:2017
+# ccbe1af814cb4c55b32e07f6f822982c
+msgid "After everything is configured, CloudStack will perform its initialization. This can take 30 minutes or more, depending on the speed of your network. When the initialization has completed successfully, the administrator's Dashboard should be displayed in the CloudStack UI."
+msgstr ""
+
+#: ../../configuration.rst:2024
+# 3d71a6b46a8d488faf274c75afe3da64
+msgid "Verify that the system is ready. In the left navigation bar, select Templates. Click on the CentOS 5.5 (64bit) no Gui (KVM) template. Check to be sure that the status is \"Download Complete.\" Do not proceed to the next step until this status is displayed."
+msgstr ""
+
+#: ../../configuration.rst:2031
+# 46922512af904edaa8ef1b310d5c1c8a
+msgid "Go to the Instances tab, and filter by My Instances."
+msgstr ""
+
+#: ../../configuration.rst:2035
+# b581dcfaecc94be9911c21caf25d598b
+msgid "Click Add Instance and follow the steps in the wizard."
+msgstr ""
+
+#: ../../configuration.rst:2039
+# af3b39e4ad7a4bce989e3c7133ec4d1d
+msgid "Choose the zone you just added."
+msgstr ""
+
+#: ../../configuration.rst:2043
+# 80993ede56aa4dd5bcddbc7ce9020b10
+msgid "In the template selection, choose the template to use in the VM. If this is a fresh installation, likely only the provided CentOS template is available."
+msgstr ""
+
+#: ../../configuration.rst:2049
+# c3568ecd59d04de592bd86c3fe1192fe
+msgid "Select a service offering. Be sure that the hardware you have allows starting the selected service offering."
+msgstr ""
+
+#: ../../configuration.rst:2054
+# e1e651260fcf467499f277366c5e9d1c
+msgid "In data disk offering, if desired, add another data disk. This is a second volume that will be available to but not mounted in the guest. For example, in Linux on XenServer you will see /dev/xvdb in the guest after rebooting the VM. A reboot is not required if you have a PV-enabled OS kernel in use."
+msgstr ""
+
+#: ../../configuration.rst:2062
+# 8dedfeddf1484e2c859e4d17ef668a09
+msgid "In default network, choose the primary network for the guest. In a trial installation, you would have only one option here."
+msgstr ""
+
+#: ../../configuration.rst:2067
+# 995446b9aadf4338a6efaae7dd17a811
+msgid "Optionally give your VM a name and a group. Use any descriptive text you would like."
+msgstr ""
+
+#: ../../configuration.rst:2072
+# c81ae436339e40318bd93663e7fae90b
+msgid "Click Launch VM. Your VM will be created and started. It might take some time to download the template and complete the VM startup. You can watch the VM’s progress in the Instances screen."
+msgstr ""
+
+#: ../../configuration.rst:2079
+# b528cfe88af44850968d44c478e9fbeb
+msgid "To use the VM, click the View Console button. |ConsoleButton.png: button to launch a console|"
+msgstr ""
+
+#: ../../configuration.rst:2082
+# 47de4c6df3b84eb1bd27cca1dac36e83
+msgid "For more information about using VMs, including instructions for how to allow incoming network traffic to the VM, start, stop, and delete VMs, and move a VM from one host to another, see Working With Virtual Machines in the Administrator’s Guide."
+msgstr ""
+
+#: ../../configuration.rst:2087
+# 7920bce7a20a4430930d72c88deee7c5
+msgid "Congratulations! You have successfully completed a CloudStack Installation."
+msgstr ""
+
+#: ../../configuration.rst:2090
+# ad525ef720224f54817a2a670f3ee8c7
+msgid "If you decide to grow your deployment, you can add more hosts, primary storage, zones, pods, and clusters."
+msgstr ""
+
+#: ../../configuration.rst:2095
+# 414a612c39484fa7bf5a64f347423408
+msgid "Configuration Parameters"
+msgstr ""
+
+#: ../../configuration.rst:2098
+# dbf02580c5f64d1faf5386697392782e
+msgid "About Configuration Parameters"
+msgstr ""
+
+#: ../../configuration.rst:2100
+# eee108e2aa63411eb512e49eabaaaf86
+msgid "CloudStack provides a variety of settings you can use to set limits, configure features, and enable or disable features in the cloud. Once your Management Server is running, you might need to set some of these configuration parameters, depending on what optional features you are setting up. You can set default values at the global level, which will be in effect throughout the cloud unless you override them at a lower level. You can make local settings, which will override the global configuration parameter values, at the level of an account, zone, cluster, or primary storage."
+msgstr ""
+
+#: ../../configuration.rst:2110
+# 273a0d9534c84cacad7e5213fe048c92
+msgid "The documentation for each CloudStack feature should direct you to the names of the applicable parameters. The following table shows a few of the more useful parameters."
+msgstr ""
+
+#: ../../configuration.rst:2115
+#: ../../configuration.rst:2214
+#: ../../configuration.rst:2214
+# 5a0769ed1728410ba2e8099c2116ff69
+# 5273cff9b8ce4272b1165cc74e2e1365
+# 0efb2fd328b44e4b93099509c05b0687
+msgid "Field"
+msgstr ""
+
+#: ../../configuration.rst:2115
+#: ../../configuration.rst:2214
+# 1c7fe5d589fc4fbc999ed4bb0e6b2de4
+# f67b280acbc4403d9526d3c26ce84f03
+msgid "Value"
+msgstr ""
+
+#: ../../configuration.rst:2117
+# a41db4113cf24adcbaf69ed7d07cc855
+msgid "management.network.cidr"
+msgstr ""
+
+#: ../../configuration.rst:2117
+# 6bba269b44fa47f7a69633b1557bc313
+msgid "A CIDR that describes the network that the management CIDRs reside on. This variable must be set for deployments that use vSphere. It is recommended to be set for other deployments as well. Example: 192.168.3.0/24."
+msgstr ""
+
+#: ../../configuration.rst:2118
+# 1af97848abac4e4eb333ded4e965fcda
+msgid "xen.setup.multipath"
+msgstr ""
+
+#: ../../configuration.rst:2118
+# 2da9406129df4abbbefe9edd230bef71
+msgid "For XenServer nodes, this is a true/false variable that instructs CloudStack to enable iSCSI multipath on the XenServer Hosts when they are added. This defaults to false. Set it to true if you would like CloudStack to enable multipath.If this is true for a NFS-based deployment multipath will still be enabled on the XenServer host. However, this does not impact NFS operation and is harmless."
+msgstr ""
+
+#: ../../configuration.rst:2119
+# 84763a41d49f4e74930be28c6d859cda
+msgid "secstorage.allowed.internal.sites"
+msgstr ""
+
+#: ../../configuration.rst:2119
+# c10112ecb1c4451c995e9bfdc339c1d2
+msgid "This is used to protect your internal network from rogue attempts to download arbitrary files using the template download feature. This is a comma-separated list of CIDRs. If a requested URL matches any of these CIDRs the Secondary Storage VM will use the private network interface to fetch the URL. Other URLs will go through the public interface. We suggest you set this to 1 or 2 hardened internal machines where you keep your templates. For example, set it to 192.168.1.66/32."
+msgstr ""
+
+#: ../../configuration.rst:2120
+# 586893028ae24cdbb929d0f3604c434c
+msgid "use.local.storage"
+msgstr ""
+
+#: ../../configuration.rst:2120
+# cbb8ac006c0f4403ae2891ec0152641d
+msgid "Determines whether CloudStack will use storage that is local to the Host for data disks, templates, and snapshots. By default CloudStack will not use this storage. You should change this to true if you want to use local storage and you understand the reliability and feature drawbacks to choosing local storage."
+msgstr ""
+
+#: ../../configuration.rst:2121
+# 652726f6d65c47b9b88065cb7ea6285b
+msgid "host"
+msgstr ""
+
+#: ../../configuration.rst:2121
+# 5f8a36af88c4499cbdf760395a9e3d91
+msgid "This is the IP address of the Management Server. If you are using multiple Management Servers you should enter a load balanced IP address that is reachable via the private network."
+msgstr ""
+
+#: ../../configuration.rst:2122
+# ba59cea1b15445aab942c2d6585a3e15
+m
<TRUNCATED>
[4/7] setup i18n with transifex and sphinx-intl
Posted by se...@apache.org.
http://git-wip-us.apache.org/repos/asf/cloudstack-docs-install/blob/bd81bcc4/source/locale/pot/index.pot
----------------------------------------------------------------------
diff --git a/source/locale/pot/index.pot b/source/locale/pot/index.pot
new file mode 100644
index 0000000..96c6249
--- /dev/null
+++ b/source/locale/pot/index.pot
@@ -0,0 +1,88 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2014, Apache Software Foundation
+# This file is distributed under the same license as the Apache CloudStack Installation Documentation package.
+# FIRST AUTHOR <EM...@ADDRESS>, YEAR.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: Apache CloudStack Installation Documentation 4\n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2014-03-31 14:02-0400\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"
+
+#: ../../index.rst:24
+# 3444a9bac8c1480fb6aeeddde33317aa
+msgid "Quicklinks to CloudStack documentations:"
+msgstr ""
+
+#: ../../index.rst:26
+# de15a84dcd6c4d7f95e3cd6812e961e5
+msgid "`Documentation home <http://docs.cloudstack.apache.org>`_"
+msgstr ""
+
+#: ../../index.rst:27
+# 8cfba20e17424f6eb7c1c27701a7623b
+msgid "`Administration Guide <http://docs.cloudstack.apache.org/projects/cloudstack-administration>`_"
+msgstr ""
+
+#: ../../index.rst:28
+# ceab02648e894c459ace09840dbe7dec
+msgid "`Release Notes <http://docs.cloudstack.apache.org/projects/cloudstack-release-notes>`_"
+msgstr ""
+
+#: ../../index.rst:33
+# 4d03b7ecaf134a00a2c8b3dc4f2d9287
+msgid "Welcome to CloudStack Installation Documentation"
+msgstr ""
+
+#: ../../index.rst:39
+# ab60384766f143609f9d6ce0c7715ad8
+msgid "Choosing a Deployment Architecture"
+msgstr ""
+
+#: ../../index.rst:46
+# 2498e69aef534512a9469d39529cdd57
+msgid "Quick Installation Guide"
+msgstr ""
+
+#: ../../index.rst:53
+# 75622cd0baf949e3b27a45c2700219d7
+msgid "General Installation"
+msgstr ""
+
+#: ../../index.rst:60
+# 7edc5f456b0644da8742337ed23c3e8f
+msgid "Source Installation"
+msgstr ""
+
+#: ../../index.rst:67
+# c87f9d4590b9444bbfb91a1865d694c8
+msgid "Configuration"
+msgstr ""
+
+#: ../../index.rst:74
+# 6841529c30524f33b73ff72b37ba92f1
+msgid "Hypervisor Installation"
+msgstr ""
+
+#: ../../index.rst:81
+# 6898869cb0974aa5abd32cdbea12ae53
+msgid "Network Setup"
+msgstr ""
+
+#: ../../index.rst:88
+# 6ef45fb9e25c422d946bc4f2c85bc631
+msgid "Storage Setup"
+msgstr ""
+
+#: ../../index.rst:95
+# 91d8d3664ff2474788edd798968a650d
+msgid "Optional Installation"
+msgstr ""
+
http://git-wip-us.apache.org/repos/asf/cloudstack-docs-install/blob/bd81bcc4/source/locale/pot/installation.pot
----------------------------------------------------------------------
diff --git a/source/locale/pot/installation.pot b/source/locale/pot/installation.pot
new file mode 100644
index 0000000..1499311
--- /dev/null
+++ b/source/locale/pot/installation.pot
@@ -0,0 +1,1224 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2014, Apache Software Foundation
+# This file is distributed under the same license as the Apache CloudStack Installation Documentation package.
+# FIRST AUTHOR <EM...@ADDRESS>, YEAR.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: Apache CloudStack Installation Documentation 4\n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2014-03-31 14:02-0400\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"
+
+#: ../../installation.rst:17
+# 696f33854b9b4941855f7f25ccc0cf05
+msgid "Installation"
+msgstr ""
+
+#: ../../installation.rst:20
+# ff48e5d805aa4814b39f91561554e3c6
+msgid "Who Should Read This"
+msgstr ""
+
+#: ../../installation.rst:22
+# 7cb4278c79974110a4adf2c885d78470
+msgid "For those who have already gone through a design phase and planned a more sophisticated deployment, or those who are ready to start scaling up a trial installation. With the following procedures, you can start using the more powerful features of CloudStack, such as advanced VLAN networking, high availability, additional network elements such as load balancers and firewalls, and support for multiple hypervisors including Citrix XenServer, KVM, and VMware vSphere."
+msgstr ""
+
+#: ../../installation.rst:31
+# 88b2672c7f5e453eb00bd6db1cda1b4a
+msgid "Overview of Installation Steps"
+msgstr ""
+
+#: ../../installation.rst:33
+# fd612cec65d44d02923190c7d926cad9
+msgid "For anything more than a simple trial installation, you will need guidance for a variety of configuration choices. It is strongly recommended that you read the following:"
+msgstr ""
+
+#: ../../installation.rst:39
+# 8f0a70053a904e2b8961590d565d30d2
+msgid "Choosing a Deployment Architecture"
+msgstr ""
+
+#: ../../installation.rst:43
+# 15f7d10ff7fc4c1b9066536494db9b56
+msgid "Choosing a Hypervisor: Supported Features"
+msgstr ""
+
+#: ../../installation.rst:47
+# 4d261c410eee4e018fd6eb76cc94acda
+msgid "Network Setup"
+msgstr ""
+
+#: ../../installation.rst:51
+# ba3e2e851d234703a2199f76867640dd
+msgid "Storage Setup"
+msgstr ""
+
+#: ../../installation.rst:55
+# 1d8c933b647d4ba1b439cff6a2c438fe
+msgid "Best Practices"
+msgstr ""
+
+#: ../../installation.rst:59
+# d87792c41ab04c53ad2d033319b2d6ca
+msgid "Make sure you have the required hardware ready. See :ref:`minimum-system-requirements`"
+msgstr ""
+
+#: ../../installation.rst:63
+# bf039038d75e4ee687b6a1d022289001
+msgid "Install the Management Server (choose single-node or multi-node). See :ref:`adding-a-zone`"
+msgstr ""
+
+#: ../../installation.rst:68
+# 94bd42ffc2134c80af6f082ae61279c0
+msgid "Log in to the UI. See `*User Interface* <http://docs.cloudstack.apache.org/projects/cloudstack-administration/en/latest/ui.html#log-in-to-the-ui>`_"
+msgstr ""
+
+#: ../../installation.rst:72
+# 06fa7787bac24c1492efd48bd972d502
+msgid "Add a zone. Includes the first pod, cluster, and host. See :ref:`adding-a-host`"
+msgstr ""
+
+#: ../../installation.rst:76
+# d5a0a4aeeeb040c3be7c466bfb0e1796
+msgid "Add more pods (optional). See :ref:`adding-a-pod`"
+msgstr ""
+
+#: ../../installation.rst:80
+# d285264761f043448a6fcdab51466f7d
+msgid "Add more clusters (optional). See :ref:`adding-a-cluster`"
+msgstr ""
+
+#: ../../installation.rst:84
+# 4ea3617136ae46ea9b683058ca52f005
+msgid "Add more hosts (optional). See :ref:`adding-a-host`"
+msgstr ""
+
+#: ../../installation.rst:88
+# 800bae48b52242dab87a5b7b5d3ffc10
+msgid "Add more primary storage (optional). See :ref:`add-primary-storage`"
+msgstr ""
+
+#: ../../installation.rst:92
+# ddb10602e63b4a798a21c8310f752c6d
+msgid "Add more secondary storage (optional). See :ref:`add-secondary-storage`"
+msgstr ""
+
+#: ../../installation.rst:96
+# 3dcafa4b56204a3e9644a390a0aab08d
+msgid "Try using the cloud. See :ref:`initialize-and-test`"
+msgstr ""
+
+#: ../../installation.rst:101
+# f95adbf7a0904e76a96e327bd42de992
+msgid "Minimum System Requirements"
+msgstr ""
+
+#: ../../installation.rst:104
+# 9038ccc4f4e84eeeb573f9125e060402
+msgid "Management Server, Database, and Storage System Requirements"
+msgstr ""
+
+#: ../../installation.rst:106
+# 0334dbfde6734d9091ba902dae561d0c
+msgid "The machines that will run the Management Server and MySQL database must meet the following requirements. The same machines can also be used to provide primary and secondary storage, such as via localdisk or NFS. The Management Server may be placed on a virtual machine."
+msgstr ""
+
+#: ../../installation.rst:113
+# b6da3ed1ea264092bab71c0b6fee8cfb
+msgid "Operating system:"
+msgstr ""
+
+#: ../../installation.rst:117
+# 598001c2c0c84997a36fd01aad6dbea8
+msgid "Preferred: CentOS/RHEL 6.3+ or Ubuntu 12.04(.1)"
+msgstr ""
+
+#: ../../installation.rst:121
+#: ../../installation.rst:157
+# fa3ae1dd550641f49963ecfa900f99ab
+# b2ec9353f7f74026b96e8353e73c2bdc
+msgid "64-bit x86 CPU (more cores results in better performance)"
+msgstr ""
+
+#: ../../installation.rst:125
+#: ../../installation.rst:165
+# 404e3299e82a4d0fb2956ac9cf2ac052
+# a96d98cde62246d1921f3f42cb478299
+msgid "4 GB of memory"
+msgstr ""
+
+#: ../../installation.rst:129
+# e755e7a8c19042f98810f43bafc8eec5
+msgid "250 GB of local disk (more results in better capability; 500 GB recommended)"
+msgstr ""
+
+#: ../../installation.rst:134
+#: ../../installation.rst:173
+# fbe37af0d39349868e45d21f2d95dce3
+# a29efb8ca2a8445cb015ebb5bd714fef
+msgid "At least 1 NIC"
+msgstr ""
+
+#: ../../installation.rst:138
+# 1d6b4d6f426147aa90cc557f4ba25e33
+msgid "Statically allocated IP address"
+msgstr ""
+
+#: ../../installation.rst:142
+# 3ffa37cedc22421f968b8a7a93f94999
+msgid "Fully qualified domain name as returned by the hostname command"
+msgstr ""
+
+#: ../../installation.rst:145
+# e1f5dfd149f54d9fb4f308e7dd6ef31a
+msgid "Host/Hypervisor System Requirements"
+msgstr ""
+
+#: ../../installation.rst:147
+# a141e6c79c4d4ec181c8eba5338ef372
+msgid "The host is where the cloud services run in the form of guest virtual machines. Each host is one machine that meets the following requirements:"
+msgstr ""
+
+#: ../../installation.rst:153
+# f3d101c98ed942559678418020a08c66
+msgid "Must support HVM (Intel-VT or AMD-V enabled)."
+msgstr ""
+
+#: ../../installation.rst:161
+# 30bd13b7de1d409f88c23234ac899f8f
+msgid "Hardware virtualization support required"
+msgstr ""
+
+#: ../../installation.rst:169
+# 99ed44c8b1514d1d9ca0ea3f1961e9d9
+msgid "36 GB of local disk"
+msgstr ""
+
+#: ../../installation.rst:176
+# 0ba2d3e7429b4fbcac124175c6c6848e
+msgid "If DHCP is used for hosts, ensure that no conflict occurs between DHCP server used for these hosts and the DHCP router created by CloudStack."
+msgstr ""
+
+#: ../../installation.rst:180
+# fe147adadd224b7591a5876e39b40551
+msgid "Latest hotfixes applied to hypervisor software"
+msgstr ""
+
+#: ../../installation.rst:184
+# 29179406b7fe48b4a19ca120d48a8cbc
+msgid "When you deploy CloudStack, the hypervisor host must not have any VMs already running"
+msgstr ""
+
+#: ../../installation.rst:189
+# 7fd1b7db7ac54430b9a62f80acf2eaf6
+msgid "All hosts within a cluster must be homogeneous. The CPUs must be of the same type, count, and feature flags."
+msgstr ""
+
+#: ../../installation.rst:192
+# 87c8d49ef26342f8b19ff41fca9335f5
+msgid "Hosts have additional requirements depending on the hypervisor. See the requirements listed at the top of the Installation section for your chosen hypervisor:"
+msgstr ""
+
+#: ../../installation.rst:197
+# a46900299a59438c8bcaa16961ef008c
+msgid "Be sure you fulfill the additional hypervisor requirements and installation steps provided in this Guide. Hypervisor hosts must be properly prepared to work with CloudStack. For example, the requirements for XenServer are listed under Citrix XenServer Installation."
+msgstr ""
+
+#: ../../installation.rst:200
+# 56ebe3b817624994b484997555de259f
+msgid "Configure package repository"
+msgstr ""
+
+#: ../../installation.rst:202
+# 0cdb7f80146b43478ac5c26f65c59b29
+msgid "CloudStack is only distributed from source from the official mirrors. However, members of the CloudStack community may build convenience binaries so that users can install Apache CloudStack without needing to build from source."
+msgstr ""
+
+#: ../../installation.rst:207
+# b1f92887e3cd499f9278b3f9b919c23f
+msgid "If you didn't follow the steps to build your own packages from source in the sections for `“Building RPMs from Source” <building_from_source.html#building-rpms-from-source>`_ or `“Building DEB packages” <building_from_source.html#building-deb-packages>`_ you may find pre-built DEB and RPM packages for your convenience linked from the `downloads <http://cloudstack.apache.org/downloads.html>`_ page."
+msgstr ""
+
+#: ../../installation.rst:213
+# 36c2e294499f41adb78a54952436e955
+msgid "These repositories contain both the Management Server and KVM Hypervisor packages."
+msgstr ""
+
+#: ../../installation.rst:216
+# ab84a44960284510a19c2720e7acb422
+msgid "DEB package repository"
+msgstr ""
+
+#: ../../installation.rst:218
+# cd8bb5ec9815465fa5a7f4afd3481d96
+msgid "You can add a DEB package repository to your apt sources with the following commands. Please note that only packages for Ubuntu 12.04 LTS (precise) are being built at this time."
+msgstr ""
+
+#: ../../installation.rst:222
+# 5b021f6f96c04cb48ac277bab4957e76
+msgid "Use your preferred editor and open (or create) ``/etc/apt/sources.list.d/cloudstack.list``. Add the community provided repository to the file:"
+msgstr ""
+
+#: ../../installation.rst:230
+# 76991f3a13a04de4b31a8970050636b8
+msgid "We now have to add the public key to the trusted keys."
+msgstr ""
+
+#: ../../installation.rst:236
+# fe7c47c14dc348f59e41259a2f93fd9e
+msgid "Now update your local apt cache."
+msgstr ""
+
+#: ../../installation.rst:242
+# 88f8a6c1f55148eebfa98a0a18c3fa23
+msgid "Your DEB package repository should now be configured and ready for use."
+msgstr ""
+
+#: ../../installation.rst:245
+# 0de56ffea1284ea582b56c333398d364
+msgid "RPM package repository"
+msgstr ""
+
+#: ../../installation.rst:247
+# f28dd9390c314092821b287e255bc352
+msgid "There is a RPM package repository for CloudStack so you can easily install on RHEL based platforms."
+msgstr ""
+
+#: ../../installation.rst:250
+# f6aae31ae39b48e98ae9b00a4cab1b3f
+msgid "If you're using an RPM-based system, you'll want to add the Yum repository so that you can install CloudStack with Yum."
+msgstr ""
+
+#: ../../installation.rst:253
+# 2c5fd8c417b7420f91685a5755296cd1
+msgid "Yum repository information is found under ``/etc/yum.repos.d``. You'll see several ``.repo`` files in this directory, each one denoting a specific repository."
+msgstr ""
+
+#: ../../installation.rst:257
+# e589a098abc84dff8a5c900002e44413
+msgid "To add the CloudStack repository, create ``/etc/yum.repos.d/cloudstack.repo`` and insert the following information."
+msgstr ""
+
+#: ../../installation.rst:269
+# 179494fcebc847b2833e80c7d4466eb6
+msgid "Now you should be able to install CloudStack using Yum."
+msgstr ""
+
+#: ../../installation.rst:272
+# ca14246b88024576881cc5a1c43f14ee
+msgid "Management Server Installation"
+msgstr ""
+
+#: ../../installation.rst:275
+# 787d92a26f544922bd7089410f1c2f73
+msgid "Management Server Installation Overview"
+msgstr ""
+
+#: ../../installation.rst:277
+# cfc7bf33cd6d492bb4bbafc2f69bf23a
+msgid "This section describes installing the Management Server. There are two slightly different installation flows, depending on how many Management Server nodes will be in your cloud:"
+msgstr ""
+
+#: ../../installation.rst:283
+# 97f223873b674a3b8cea6e4278d8fce2
+msgid "A single Management Server node, with MySQL on the same node."
+msgstr ""
+
+#: ../../installation.rst:287
+# b127e1c38ea44e7eb7609245f2856522
+msgid "Multiple Management Server nodes, with MySQL on a node separate from the Management Servers."
+msgstr ""
+
+#: ../../installation.rst:290
+# a7cb64a7ad004859baf3b85c4807b4ce
+msgid "In either case, each machine must meet the system requirements described in System Requirements."
+msgstr ""
+
+#: ../../installation.rst:294
+# f311a9f082f243358bd6e1bacb0724c0
+msgid "For the sake of security, be sure the public Internet can not access port 8096 or port 8250 on the Management Server."
+msgstr ""
+
+#: ../../installation.rst:296
+# 81fa7f40aa954c7389c0ddc56e4409fd
+msgid "The procedure for installing the Management Server is:"
+msgstr ""
+
+#: ../../installation.rst:300
+#: ../../installation.rst:327
+# 02acaca57ebb4504b9db45b2442686d6
+# 39c72e56316949fea280e05e177bbd18
+msgid "Prepare the Operating System"
+msgstr ""
+
+#: ../../installation.rst:304
+# 790ce7b3541b43c2bf4b14583a247581
+msgid "(XenServer only) Download and install vhd-util."
+msgstr ""
+
+#: ../../installation.rst:308
+# 6990b7e0088f4f51acd96314383d890f
+msgid "Install the First Management Server"
+msgstr ""
+
+#: ../../installation.rst:312
+# 84d81fe58d2d46889753eecbd978adf8
+msgid "Install and Configure the MySQL database"
+msgstr ""
+
+#: ../../installation.rst:316
+#: ../../installation.rst:943
+# 65c00df0d81d41fd818ef1191ed7ad2a
+# 1620c2310d7b4308bf45f93baa38649c
+msgid "Prepare NFS Shares"
+msgstr ""
+
+#: ../../installation.rst:320
+# 8ac7bcc7dff34b26814031f065442613
+msgid "Prepare and Start Additional Management Servers (optional)"
+msgstr ""
+
+#: ../../installation.rst:324
+#: ../../installation.rst:1274
+# 2ebe94fd439c4a82bc551c3bd80a3a72
+# 9c47dabf23f74fa1afd016220ce3ac03
+msgid "Prepare the System VM Template"
+msgstr ""
+
+#: ../../installation.rst:329
+# 94fb715d86304d52ad6b97b19a96ec4b
+msgid "The OS must be prepared to host the Management Server using the following steps. These steps must be performed on each Management Server node."
+msgstr ""
+
+#: ../../installation.rst:335
+# b63959d08d254fffb3d7c38112791bd7
+msgid "Log in to your OS as root."
+msgstr ""
+
+#: ../../installation.rst:339
+# 0c59e0da09ec46539f219f14fa57f53d
+msgid "Check for a fully qualified hostname."
+msgstr ""
+
+#: ../../installation.rst:345
+# 482686f6346449c69aa4154442ccd6b7
+msgid "This should return a fully qualified hostname such as \"management1.lab.example.org\". If it does not, edit /etc/hosts so that it does."
+msgstr ""
+
+#: ../../installation.rst:351
+# f24bd2a383c34a2ab21f404ec9c2cd7d
+msgid "Make sure that the machine can reach the Internet."
+msgstr ""
+
+#: ../../installation.rst:359
+# 0b873027faa449f4bee3820217b922fa
+msgid "Turn on NTP for time synchronization."
+msgstr ""
+
+#: ../../installation.rst:362
+# a0981835ac67411c927b59c3de1e6575
+msgid "NTP is required to synchronize the clocks of the servers in your cloud."
+msgstr ""
+
+#: ../../installation.rst:364
+# 20e168e7085242d095331cd9d2b80c20
+msgid "Install NTP."
+msgstr ""
+
+#: ../../installation.rst:376
+# 46750ec5f4554a30a4bdc2c761459f70
+msgid "Repeat all of these steps on every host where the Management Server will be installed."
+msgstr ""
+
+#: ../../installation.rst:380
+# 1a936a7d02bb4555a9667786988a7b19
+msgid "Install the Management Server on the First Host"
+msgstr ""
+
+#: ../../installation.rst:382
+# 4713eced035b45ac8ae785502737a330
+msgid "The first step in installation, whether you are installing the Management Server on one host or many, is to install the software on a single node."
+msgstr ""
+
+#: ../../installation.rst:387
+# f4ab68fb34464e799e49169028ac2a47
+msgid "If you are planning to install the Management Server on multiple nodes for high availability, do not proceed to the additional nodes yet. That step will come later."
+msgstr ""
+
+#: ../../installation.rst:389
+# bd5cb32f0a2644a5b613db7d09ce3021
+msgid "The CloudStack Management server can be installed using either RPM or DEB packages. These packages will depend on everything you need to run the Management server."
+msgstr ""
+
+#: ../../installation.rst:394
+# f2a353ac92ca4305bc5cd05c3b67edc3
+msgid "Install on CentOS/RHEL"
+msgstr ""
+
+#: ../../installation.rst:396
+# 215a3f94e0e145be9b64461d8ae5a07d
+msgid "We start by installing the required packages:"
+msgstr ""
+
+#: ../../installation.rst:403
+# 1b6562fea60e4b829c33efaf0eb6285b
+msgid "Install on Ubuntu"
+msgstr ""
+
+#: ../../installation.rst:410
+# 45790ec2046c402dbae2bc46ecefa111
+msgid "Downloading vhd-util"
+msgstr ""
+
+#: ../../installation.rst:412
+# 6b84c5527ace4c579433f8e54803bd59
+msgid "This procedure is required only for installations where XenServer is installed on the hypervisor hosts."
+msgstr ""
+
+#: ../../installation.rst:415
+# f028c6bb2ade4b34a912ba8d49b40423
+msgid "Before setting up the Management Server, download vhd-util from `vhd-util <http://download.cloud.com.s3.amazonaws.com/tools/vhd-util>`_."
+msgstr ""
+
+#: ../../installation.rst:418
+# 5382e69a952f46e0b38ea6c6180dd48f
+msgid "If the Management Server is RHEL or CentOS, copy vhd-util to `/usr/share/cloudstack-common/scripts/vm/hypervisor/xenserver`"
+msgstr ""
+
+#: ../../installation.rst:420
+# f0befb44640d47abaa8e51b020060d63
+msgid "If the Management Server is Ubuntu, copy vhd-util to `/usr/share/cloudstack-common/scripts/vm/hypervisor/xenserver`"
+msgstr ""
+
+#: ../../installation.rst:423
+# cd862b01f8fb480881fd3a46e9c72621
+msgid "Install the database server"
+msgstr ""
+
+#: ../../installation.rst:425
+# 2763f3785e2441a2828e5a4fdea57a4d
+msgid "The CloudStack management server uses a MySQL database server to store its data. When you are installing the management server on a single node, you can install the MySQL server locally. For an installation that has multiple management server nodes, we assume the MySQL database also runs on a separate node."
+msgstr ""
+
+#: ../../installation.rst:431
+# e5f94c1da4e7490b93026bb5fcbaf5d7
+msgid "CloudStack has been tested with MySQL 5.1 and 5.5. These versions are included in RHEL/CentOS and Ubuntu."
+msgstr ""
+
+#: ../../installation.rst:435
+# 544dc7053bde486bb6893e69becbe365
+msgid "Install the Database on the Management Server Node"
+msgstr ""
+
+#: ../../installation.rst:437
+# 0beb8883084b40369a72c32005f0764f
+msgid "This section describes how to install MySQL on the same machine with the Management Server. This technique is intended for a simple deployment that has a single Management Server node. If you have a multi-node Management Server deployment, you will typically use a separate node for MySQL. See :ref:`install-database-on-separate-node`."
+msgstr ""
+
+#: ../../installation.rst:445
+# f9a03153674b4e71931f240af9649a3f
+msgid "Install MySQL from the package repository of your distribution:"
+msgstr ""
+
+#: ../../installation.rst:447
+# 368075ea83e94d6e88eaf47096b0004d
+msgid ":.. sourcecode:: bash"
+msgstr ""
+
+#: ../../installation.rst:449
+# fa3d229b444e4625b8c985e59fa3944e
+msgid "yum install mysql-server"
+msgstr ""
+
+#: ../../installation.rst:457
+# dc612d7dbdaa46b5a5f53f12a3c5dc11
+msgid "Open the MySQL configuration file. The configuration file is ``/etc/my.cnf`` or ``/etc/mysql/my.cnf``, depending on your OS."
+msgstr ""
+
+#: ../../installation.rst:462
+# 82041ff4af184199abf1601fd1d54db5
+msgid "Insert the following lines in the [mysqld] section."
+msgstr ""
+
+#: ../../installation.rst:464
+# 885ee4f72e4b4aaab0ba9b3c7e370ce8
+msgid "You can put these lines below the datadir line. The max\\_connections parameter should be set to 350 multiplied by the number of Management Servers you are deploying. This example assumes one Management Server."
+msgstr ""
+
+#: ../../installation.rst:470
+# 1cfe5cb57e3d43078f0f305b741fb4b3
+msgid "On Ubuntu, you can also create a file `/etc/mysql/conf.d/cloudstack.cnf` and add these directives there. Don't forget to add [mysqld] on the first line of the file."
+msgstr ""
+
+#: ../../installation.rst:482
+#: ../../installation.rst:696
+# 5b9a37699bd0472ab0d8231cc73613cb
+# 1413df8c8c414dcbbdf912a616283d02
+msgid "Start or restart MySQL to put the new configuration into effect."
+msgstr ""
+
+#: ../../installation.rst:484
+#: ../../installation.rst:698
+# b73a323df6154ce887e0b9dc1429377f
+# d6125ea5f46e4983b4196f5624920c09
+msgid "On RHEL/CentOS, MySQL doesn't automatically start after installation. Start it manually."
+msgstr ""
+
+#: ../../installation.rst:491
+#: ../../installation.rst:705
+# dac59fe1582f443d969bdbd6f4981407
+# 8c391ed2a5cf47f9b6a833e041c26640
+msgid "On Ubuntu, restart MySQL."
+msgstr ""
+
+#: ../../installation.rst:499
+#: ../../installation.rst:713
+# a7e8903ec31c4ceea371761681f8c802
+# 0668b848f7ec49e4bd885d8b69806276
+msgid "(CentOS and RHEL only; not required on Ubuntu)"
+msgstr ""
+
+#: ../../installation.rst:502
+# 91837929006f4c079bbff588e501ff7d
+msgid "On RHEL and CentOS, MySQL does not set a root password by default. It is very strongly recommended that you set a root password as a security precaution."
+msgstr ""
+
+#: ../../installation.rst:504
+# 08bce5aebf68455ebbd80d7dbe835acd
+msgid "Run the following command to secure your installation. You can answer \"Y\" to all questions."
+msgstr ""
+
+#: ../../installation.rst:512
+# 41b923848c474e93b9ec26ee1535a7ae
+msgid "CloudStack can be blocked by security mechanisms, such as SELinux. Disable SELinux to ensure + that the Agent has all the required permissions."
+msgstr ""
+
+#: ../../installation.rst:516
+# 2d0d176ffff344969f7752864e4f3456
+msgid "Configure SELinux (RHEL and CentOS):"
+msgstr ""
+
+#: ../../installation.rst:520
+# c0e7f83cb57144ec99d0c7b3821b1722
+msgid "Check whether SELinux is installed on your machine. If not, you can skip this section."
+msgstr ""
+
+#: ../../installation.rst:523
+# 10bc723625a04a0b85ec9cd4889d69c2
+msgid "In RHEL or CentOS, SELinux is installed and enabled by default. You can verify this with:"
+msgstr ""
+
+#: ../../installation.rst:532
+# 505757336d42438b86b3395414db4b33
+msgid "Set the SELINUX variable in ``/etc/selinux/config`` to \"permissive\". This ensures that the permissive setting will be maintained after a system reboot."
+msgstr ""
+
+#: ../../installation.rst:536
+# 17de01838d7447bf89304026d6ea4248
+msgid "In RHEL or CentOS:"
+msgstr ""
+
+#: ../../installation.rst:542
+# 884b52275a58422b99f6cc646091e7f6
+msgid "Change the following line"
+msgstr ""
+
+#: ../../installation.rst:548
+# fd494df390f2417787ec16c50ada6696
+msgid "to this:"
+msgstr ""
+
+#: ../../installation.rst:556
+# bedede3207294745988cf76d203c7f74
+msgid "Set SELinux to permissive starting immediately, without requiring a system reboot."
+msgstr ""
+
+#: ../../installation.rst:565
+# 61969dbdeee745c7a7e2d5ae0b9572ea
+msgid "Set up the database. The following command creates the \"cloud\" user on the database."
+msgstr ""
+
+#: ../../installation.rst:570
+# b15755f3ad7f47e38ed446816aa77a1c
+msgid "In dbpassword, specify the password to be assigned to the \"cloud\" user. You can choose to provide no password although that is not recommended."
+msgstr ""
+
+#: ../../installation.rst:576
+# 6c8db37f146541378973dcc35d219673
+msgid "In deploy-as, specify the username and password of the user deploying the database. In the following command, it is assumed the root user is deploying the database and creating the \"cloud\" user."
+msgstr ""
+
+#: ../../installation.rst:583
+#: ../../installation.rst:776
+# f490b4e80428454ab05842e0b476b6b4
+# bceaae9c7ea64472a2965702148a6db7
+msgid "(Optional) For encryption\\_type, use file or web to indicate the technique used to pass in the database encryption password. Default: file. See :ref:`about-password-key-encryption`."
+msgstr ""
+
+#: ../../installation.rst:589
+# f6d266c86bac4f6aa727f5e3fbf88d8d
+msgid "(Optional) For management\\_server\\_key, substitute the default key that is used to encrypt confidential parameters in the CloudStack properties file. Default: password. It is highly recommended that you replace this with a more secure value. See :ref:`about-password-key-encryption`."
+msgstr ""
+
+#: ../../installation.rst:597
+#: ../../installation.rst:790
+# b6dec23d7ae8477b8a19b7b9d4a79d42
+# ce19fb18ded14573910f1d1240f8b0ee
+msgid "(Optional) For database\\_key, substitute the default key that is used to encrypt confidential parameters in the CloudStack database. Default: password. It is highly recommended that you replace this with a more secure value. See :ref:`about-password-key-encryption`."
+msgstr ""
+
+#: ../../installation.rst:605
+#: ../../installation.rst:798
+# a52db395b3a1486398d2061e4a995e1d
+# 967b3a443b0847c898aee030febf6bd4
+msgid "(Optional) For management\\_server\\_ip, you may explicitly specify cluster management server node IP. If not specified, the local IP address will be used."
+msgstr ""
+
+#: ../../installation.rst:618
+#: ../../installation.rst:811
+# 3a1c16fcfc744ccda91eae6cfb73e0d4
+# 08975ca13089466a8cca56ac67ffe980
+msgid "When this script is finished, you should see a message like “Successfully initialized the database.”"
+msgstr ""
+
+#: ../../installation.rst:622
+# 7afe3094d16e4672853d20b1971f866c
+msgid "If the script is unable to connect to the MySQL database, check the \"localhost\" loopback address in ``/etc/hosts``. It should be pointing to the IPv4 loopback address \"127.0.0.1\" and not the IPv6 loopback address ::1. Alternatively, reconfigure MySQL to bind to the IPv6 loopback interface."
+msgstr ""
+
+#: ../../installation.rst:626
+# c9bfb73655e843678f8eca66dfecad86
+msgid "If you are running the KVM hypervisor on the same machine with the Management Server, edit /etc/sudoers and add the following line:"
+msgstr ""
+
+#: ../../installation.rst:635
+# 57c07dbfac274d28ac58517354250f54
+msgid "Now that the database is set up, you can finish configuring the OS for the Management Server. This command will set up iptables, sudoers, and start the Management Server."
+msgstr ""
+
+#: ../../installation.rst:643
+# aa8843143a1b4f879e749a467dbb5b0f
+msgid "You should see the message “CloudStack Management Server setup is done.”"
+msgstr ""
+
+#: ../../installation.rst:649
+# 42604923b7114f2f8f56af33b3027afa
+msgid "Install the Database on a Separate Node"
+msgstr ""
+
+#: ../../installation.rst:651
+# 9418da5d285c44b8bc4b7210642683a6
+msgid "This section describes how to install MySQL on a standalone machine, separate from the Management Server. This technique is intended for a deployment that includes several Management Server nodes. If you have a single-node Management Server deployment, you will typically use the same node for MySQL. See ` “Install the Database on the Management Server Node” <#install-the-database-on-the-management-server-node>`_."
+msgstr ""
+
+#: ../../installation.rst:659
+# 4abc231ac09f424daf0b99c49119ea44
+msgid "The management server doesn't require a specific distribution for the MySQL node. You can use a distribution or Operating System of your choice. Using the same distribution as the management server is recommended, but not required. See `“Management Server, Database, and Storage System Requirements” <#management-server-database-and-storage-system-requirements>`_."
+msgstr ""
+
+#: ../../installation.rst:663
+# 5588ce27f7694dd4861d3abde3ffbb56
+msgid "Install MySQL from the package repository from your distribution:"
+msgstr ""
+
+#: ../../installation.rst:675
+# 64a8ee358f0a4ec89fd15db99d1be9eb
+msgid "Edit the MySQL configuration (/etc/my.cnf or /etc/mysql/my.cnf, depending on your OS) and insert the following lines in the [mysqld] section. You can put these lines below the datadir line. The max\\_connections parameter should be set to 350 multiplied by the number of Management Servers you are deploying. This example assumes two Management Servers."
+msgstr ""
+
+#: ../../installation.rst:683
+# bd356399448849d6b731cadef7a9099f
+msgid "On Ubuntu, you can also create /etc/mysql/conf.d/cloudstack.cnf file and add these directives there. Don't forget to add [mysqld] on the first line of the file."
+msgstr ""
+
+#: ../../installation.rst:716
+# 1005aab6e20b46708ac4e11551550fdc
+msgid "On RHEL and CentOS, MySQL does not set a root password by default. It is very strongly recommended that you set a root password as a security precaution. Run the following command to secure your installation. You can answer \"Y\" to all questions except \"Disallow root login remotely?\". Remote root login is required to set up the databases."
+msgstr ""
+
+#: ../../installation.rst:724
+# 7f72213f4e3a4874859eaf327495a545
+msgid "If a firewall is present on the system, open TCP port 3306 so external MySQL connections can be established."
+msgstr ""
+
+#: ../../installation.rst:727
+# 218fc8343f084da2953ef13cca2c7549
+msgid "On Ubuntu, UFW is the default firewall. Open the port with this command:"
+msgstr ""
+
+#: ../../installation.rst:734
+# 952910e1965d484697e23ecba711a001
+msgid "On RHEL/CentOS:"
+msgstr ""
+
+#: ../../installation.rst:738
+# 0af9bded27ec4fd6863857d6b779e4ec
+msgid "Edit the /etc/sysconfig/iptables file and add the following line at the beginning of the INPUT chain."
+msgstr ""
+
+#: ../../installation.rst:747
+# 9d5dd58fcbe0435287c2661d3ef9df67
+msgid "Now reload the iptables rules."
+msgstr ""
+
+#: ../../installation.rst:755
+# 73b82b233a564740976c44224975d17e
+msgid "Return to the root shell on your first Management Server."
+msgstr ""
+
+#: ../../installation.rst:759
+# d8833e544e06419bac30a7f0ab57b12b
+msgid "Set up the database. The following command creates the cloud user on the database."
+msgstr ""
+
+#: ../../installation.rst:764
+# 72854dd662234ff1aad983d720c6af79
+msgid "In dbpassword, specify the password to be assigned to the cloud user. You can choose to provide no password."
+msgstr ""
+
+#: ../../installation.rst:769
+# e42a363b2158494fbee560c8c89d44ca
+msgid "In deploy-as, specify the username and password of the user deploying the database. In the following command, it is assumed the root user is deploying the database and creating the cloud user."
+msgstr ""
+
+#: ../../installation.rst:782
+# 811418357feb4bd3a86912d4bd45737b
+msgid "(Optional) For management\\_server\\_key, substitute the default key that is used to encrypt confidential parameters in the CloudStack properties file. Default: password. It is highly recommended that you replace this with a more secure value. See About Password and Key Encryption."
+msgstr ""
+
+#: ../../installation.rst:816
+# 48640c143e14444d8885450a3a0fa282
+msgid "About Password and Key Encryption"
+msgstr ""
+
+#: ../../installation.rst:818
+# f7aec56e25f1405f97e5f0aec09df869
+msgid "CloudStack stores several sensitive passwords and secret keys that are used to provide security. These values are always automatically encrypted:"
+msgstr ""
+
+#: ../../installation.rst:824
+# 122a40909d374d498a62760c5289d744
+msgid "Database secret key"
+msgstr ""
+
+#: ../../installation.rst:828
+# bbba368c37e34d6aa390f26ab2396807
+msgid "Database password"
+msgstr ""
+
+#: ../../installation.rst:832
+# c32eb5a1afcb4e31bcd7590d70d96b0a
+msgid "SSH keys"
+msgstr ""
+
+#: ../../installation.rst:836
+# ca05df1c98684f49acbb801e8c5a4547
+msgid "Compute node root password"
+msgstr ""
+
+#: ../../installation.rst:840
+# a3976901fb494024a55c16f813ce3699
+msgid "VPN password"
+msgstr ""
+
+#: ../../installation.rst:844
+# 0ca66e1a468a4d518185df21b427b76a
+msgid "User API secret key"
+msgstr ""
+
+#: ../../installation.rst:848
+# c0594e34fbe5473694f41b77a96ffe57
+msgid "VNC password"
+msgstr ""
+
+#: ../../installation.rst:850
+# 39fadf09b81f4859b48ce50628bcb429
+msgid "CloudStack uses the Java Simplified Encryption (JASYPT) library. The data values are encrypted and decrypted using a database secret key, which is stored in one of CloudStack’s internal properties files along with the database password. The other encrypted values listed above, such as SSH keys, are in the CloudStack internal database."
+msgstr ""
+
+#: ../../installation.rst:856
+# 2c165f1b802441c1afc3fa3fdabc5d5c
+msgid "Of course, the database secret key itself can not be stored in the open – it must be encrypted. How then does CloudStack read it? A second secret key must be provided from an external source during Management Server startup. This key can be provided in one of two ways: loaded from a file or provided by the CloudStack administrator. The CloudStack database has a configuration setting that lets it know which of these methods will be used. If the encryption type is set to \"file,\" the key must be in a file in a known location. If the encryption type is set to \"web,\" the administrator runs the utility com.cloud.utils.crypt.EncryptionSecretKeySender, which relays the key to the Management Server over a known port."
+msgstr ""
+
+#: ../../installation.rst:868
+# 98e2deeafb9a42389fbceaba35dda3d3
+msgid "The encryption type, database secret key, and Management Server secret key are set during CloudStack installation. They are all parameters to the CloudStack database setup script (cloudstack-setup-databases). The default values are file, password, and password. It is, of course, highly recommended that you change these to more secure keys."
+msgstr ""
+
+#: ../../installation.rst:875
+# 2309cc096471413fb9f006373a732472
+msgid "Changing the Default Password Encryption"
+msgstr ""
+
+#: ../../installation.rst:877
+# a45aa5f4ad954420942c59a819fd3c04
+msgid "Passwords are encoded when creating or updating users. CloudStack allows you to determine the default encoding and authentication mechanism for admin and user logins. Two new configurable lists have been introduced—userPasswordEncoders and userAuthenticators. userPasswordEncoders allows you to configure the order of preference for encoding passwords, whereas userAuthenticators allows you to configure the order in which authentication schemes are invoked to validate user passwords."
+msgstr ""
+
+#: ../../installation.rst:886
+# 66a7bc6d2a054bccaac4bffe5540602d
+msgid "Additionally, the plain text user authenticator has been modified not to convert supplied passwords to their md5 sums before checking them with the database entries. It performs a simple string comparison between retrieved and supplied login passwords instead of comparing the retrieved md5 hash of the stored password against the supplied md5 hash of the password because clients no longer hash the password. The following method determines what encoding scheme is used to encode the password supplied during user creation or modification."
+msgstr ""
+
+#: ../../installation.rst:895
+# 2f0b0bfa672a4424af2fdec284548b99
+msgid "When a new user is created, the user password is encoded by using the first valid encoder loaded as per the sequence specified in the ``UserPasswordEncoders`` property in the ``ComponentContext.xml`` or ``nonossComponentContext.xml`` files. The order of authentication schemes is determined by the ``UserAuthenticators`` property in the same files. If Non-OSS components, such as VMware environments, are to be deployed, modify the ``UserPasswordEncoders`` and ``UserAuthenticators`` lists in the ``nonossComponentContext.xml`` file, for OSS environments, such as XenServer or KVM, modify the ``ComponentContext.xml`` file. It is recommended to make uniform changes across both the files. When a new authenticator or encoder is added, you can add them to this list. While doing so, ensure that the new authenticator or encoder is specified as a bean in both these files. The administrator can change the ordering of both these properties as preferred to change the order of schemes. Modify
the following list properties available in ``client/tomcatconf/nonossComponentContext.xml.in`` or ``client/tomcatconf/componentContext.xml.in`` as applicable, to the desired order:"
+msgstr ""
+
+#: ../../installation.rst:932
+# 4d6a1903dd1442fb93b709113a408fef
+msgid "In the above default ordering, SHA256Salt is used first for ``UserPasswordEncoders``. If the module is found and encoding returns a valid value, the encoded password is stored in the user table's password column. If it fails for any reason, the MD5UserAuthenticator will be tried next, and the order continues. For ``UserAuthenticators``, SHA256Salt authentication is tried first. If it succeeds, the user is logged into the Management server. If it fails, md5 is tried next, and attempts continues until any of them succeeds and the user logs in . If none of them works, the user is returned an invalid credential message."
+msgstr ""
+
+#: ../../installation.rst:945
+# 863e97b69ca04e90a8aa6375cb40c7c1
+msgid "CloudStack needs a place to keep primary and secondary storage (see Cloud Infrastructure Overview). Both of these can be NFS shares. This section tells how to set up the NFS shares before adding the storage to CloudStack."
+msgstr ""
+
+#: ../../installation.rst:952
+# e97f9879b6bf4cfdbd6c2c085765c532
+msgid "NFS is not the only option for primary or secondary storage. For example, you may use Ceph RBD, GlusterFS, iSCSI, and others. The choice of storage system will depend on the choice of hypervisor and whether you are dealing with primary or secondary storage."
+msgstr ""
+
+#: ../../installation.rst:954
+# 3f434e12a13c4cf7850e05104920ba38
+msgid "The requirements for primary and secondary storage are described in:"
+msgstr ""
+
+#: ../../installation.rst:958
+# 705aad15c35b4edb8eb72b0c421bc6dc
+msgid "`“About Primary Storage” <http://docs.cloudstack.apache.org/en/latest/concepts.html#about-primary-storage>`_"
+msgstr ""
+
+#: ../../installation.rst:962
+# 0e2a07b0286c415aa5ead04f998aae2a
+msgid "`“About Secondary Storage” <http://docs.cloudstack.apache.org/en/latest/concepts.html#about-secondary-storage>`_"
+msgstr ""
+
+#: ../../installation.rst:964
+# 5777fe97c6154ecaaf968c01f201e568
+msgid "A production installation typically uses a separate NFS server. See :ref:`using-a-separage-nfs-server`."
+msgstr ""
+
+#: ../../installation.rst:966
+# ff683a9bb6314c7bbdd28978dd4c135d
+msgid "You can also use the Management Server node as the NFS server. This is more typical of a trial installation, but is technically possible in a larger deployment. See :ref:`using-the-management-server-as-the-nfs-server`."
+msgstr ""
+
+#: ../../installation.rst:973
+# efc65b7a55cc4c4799340f95f74b6c3d
+msgid "Using a Separate NFS Server"
+msgstr ""
+
+#: ../../installation.rst:975
+# 6e7ca9f15cfb4f7085f7da650fc87b7d
+msgid "This section tells how to set up NFS shares for secondary and (optionally) primary storage on an NFS server running on a separate node from the Management Server."
+msgstr ""
+
+#: ../../installation.rst:979
+#: ../../installation.rst:1049
+# 301452c38b5945f7aef5889be3191b79
+# 0c78024e8b1a4b6ca24714291717183f
+msgid "The exact commands for the following steps may vary depending on your operating system version."
+msgstr ""
+
+#: ../../installation.rst:983
+# c4c9ae71431d45938ad9fff677569f4a
+msgid "(KVM only) Ensure that no volume is already mounted at your NFS mount point."
+msgstr ""
+
+#: ../../installation.rst:987
+# 6e44029c5e1c46dc812241ab0fe243f2
+msgid "On the storage server, create an NFS share for secondary storage and, if you are using NFS for primary storage as well, create a second NFS share. For example:"
+msgstr ""
+
+#: ../../installation.rst:998
+#: ../../installation.rst:1072
+# b7640fa874db4186b6a2bf230f19ac03
+# b9c23da3777b4d91b9b0e1fde28e736b
+msgid "To configure the new directories as NFS exports, edit /etc/exports. Export the NFS share(s) with rw,async,no\\_root\\_squash,no\\_subtree\\_check. For example:"
+msgstr ""
+
+#: ../../installation.rst:1006
+#: ../../installation.rst:1080
+# e3830758ea004cda917da3baf8a075de
+# c9ffdc6a70e14a818d66f54ebd4711b1
+msgid "Insert the following line."
+msgstr ""
+
+#: ../../installation.rst:1014
+#: ../../installation.rst:1088
+# 88572128aa04498781100aa2d487944a
+# 24fc59cbbff640ee97d81cf420add8e6
+msgid "Export the /export directory."
+msgstr ""
+
+#: ../../installation.rst:1022
+# 2c2f0a3094e0460ba50301cd94d20900
+msgid "On the management server, create a mount point for secondary storage. For example:"
+msgstr ""
+
+#: ../../installation.rst:1031
+# 6697c4c89b2945c0bbcfc21209e6e719
+msgid "Mount the secondary storage on your Management Server. Replace the example NFS server name and NFS share paths below with your own."
+msgstr ""
+
+#: ../../installation.rst:1041
+# bbc49c9dfce54eaa959bfbe08517d1b8
+msgid "Using the Management Server as the NFS Server"
+msgstr ""
+
+#: ../../installation.rst:1043
+# f6507591af8842c0af55a93c562f8a79
+msgid "This section tells how to set up NFS shares for primary and secondary storage on the same node with the Management Server. This is more typical of a trial installation, but is technically possible in a larger deployment. It is assumed that you will have less than 16TB of storage on the host."
+msgstr ""
+
+#: ../../installation.rst:1054
+# e688f9ffd6ff469eb6e8f5ac981922b1
+msgid "On RHEL/CentOS systems, you'll need to install the nfs-utils package:"
+msgstr ""
+
+#: ../../installation.rst:1062
+# 633c87eafb734ea28390d7114a78a66b
+msgid "On the Management Server host, create two directories that you will use for primary and secondary storage. For example:"
+msgstr ""
+
+#: ../../installation.rst:1096
+# d41c0543c03748668a89f0fcb71dab00
+msgid "Edit the /etc/sysconfig/nfs file."
+msgstr ""
+
+#: ../../installation.rst:1102
+# 02201c1c13a5411b83f5f3a7aa610806
+msgid "Uncomment the following lines:"
+msgstr ""
+
+#: ../../installation.rst:1115
+# be0030743b2b41cea5e9c3bbc53b4d38
+msgid "Edit the /etc/sysconfig/iptables file."
+msgstr ""
+
+#: ../../installation.rst:1121
+# ee29346b3d5d40c29a4401d0f2021f15
+msgid "Add the following lines at the beginning of the INPUT chain, where <NETWORK> is the network that you'll be using:"
+msgstr ""
+
+#: ../../installation.rst:1140
+# a8ebd3165ef941f2b5138978f236628d
+msgid "Run the following commands:"
+msgstr ""
+
+#: ../../installation.rst:1149
+# dd7f19829a7f418bb13796c787838544
+msgid "If NFS v4 communication is used between client and server, add your domain to /etc/idmapd.conf on both the hypervisor host and Management Server."
+msgstr ""
+
+#: ../../installation.rst:1157
+# 8bce72b6ccf44e2a8d0cc74f6d4d63db
+msgid "Remove the character # from the beginning of the Domain line in idmapd.conf and replace the value in the file with your own domain. In the example below, the domain is company.com."
+msgstr ""
+
+#: ../../installation.rst:1167
+# aa28f6e3b79943708352a9a88e9648b2
+msgid "Reboot the Management Server host."
+msgstr ""
+
+#: ../../installation.rst:1169
+# fa9a28b42bbb48c8819132441a00cd47
+msgid "Two NFS shares called /export/primary and /export/secondary are now set up."
+msgstr ""
+
+#: ../../installation.rst:1174
+# db0683e6e4d5456eaf91f8c78da576e4
+msgid "It is recommended that you test to be sure the previous steps have been successful."
+msgstr ""
+
+#: ../../installation.rst:1179
+# 8b8e2a741b6f4584bfc01a03b53880e3
+msgid "Log in to the hypervisor host."
+msgstr ""
+
+#: ../../installation.rst:1183
+# ba54a10212384e44a72b95b0e26db17c
+msgid "Be sure NFS and rpcbind are running. The commands might be different depending on your OS. For example:"
+msgstr ""
+
+#: ../../installation.rst:1196
+# 014a57fd157242feb74ad5648a43680e
+msgid "Log back in to the hypervisor host and try to mount the /export directories. For example, substitute your own management server name:"
+msgstr ""
+
+#: ../../installation.rst:1210
+# 2d92aed187234e8cad4ba635cf378c3e
+msgid "Prepare and Start Additional Management Servers"
+msgstr ""
+
+#: ../../installation.rst:1212
+# de1c10c4ea9947949db104f3a954120b
+msgid "For your second and subsequent Management Servers, you will install the Management Server software, connect it to the database, and set up the OS for the Management Server."
+msgstr ""
+
+#: ../../installation.rst:1218
+# deda98fd477d49a5824d234960226b41
+msgid "Perform the steps in `“Prepare the Operating System” <#prepare-the-operating-system>`_ and `“Building RPMs from Source” <building_from_source.html#building-rpms-from-source>`_ or `“Building DEB packages” <building_from_source.html#building-deb-packages>`_ as appropriate."
+msgstr ""
+
+#: ../../installation.rst:1224
+# cf655ea5763f474898548ad8d9591126
+msgid "This step is required only for installations where XenServer is installed on the hypervisor hosts."
+msgstr ""
+
+#: ../../installation.rst:1227
+# 1c57f09222d34ab0901da352e207b930
+msgid "Download vhd-util from `vhd-util <http://download.cloud.com.s3.amazonaws.com/tools/vhd-util>`_"
+msgstr ""
+
+#: ../../installation.rst:1230
+# 4e0e555bc5aa449d94d6912079991072
+msgid "Copy vhd-util to /usr/share/cloudstack-common/scripts/vm/hypervisor/xenserver."
+msgstr ""
+
+#: ../../installation.rst:1235
+# 13f46dfa019941fbb870eb2d2e64aadc
+msgid "Ensure that necessary services are started and set to start on boot."
+msgstr ""
+
+#: ../../installation.rst:1246
+# 85218ac64da94db1a91de5afa591e608
+msgid "Configure the database client. Note the absence of the --deploy-as argument in this case. (For more details about the arguments to this command, see :ref:`install-database-on-separate-node`.)"
+msgstr ""
+
+#: ../../installation.rst:1256
+# 9b9e49f3a0a444c099233576ab3321e4
+msgid "Configure the OS and start the Management Server:"
+msgstr ""
+
+#: ../../installation.rst:1262
+# 60702c567e2947e9aa19c0b5ec947341
+msgid "The Management Server on this node should now be running."
+msgstr ""
+
+#: ../../installation.rst:1266
+# 1dd194414c0944a1b9acbd76fbf20a06
+msgid "Repeat these steps on each additional Management Server."
+msgstr ""
+
+#: ../../installation.rst:1270
+# 2e064e64c3604d30bd6d7dfceb570ce7
+msgid "Be sure to configure a load balancer for the Management Servers. See `“Management Server Load Balancing” <http://docs.cloudstack.apache.org/en/latest/administration_guide.html?highlight=management%20server%20load#management-server-load-balancing>`_."
+msgstr ""
+
+#: ../../installation.rst:1276
+# 8d25149ea0e0441286d509318d647e1a
+msgid "Secondary storage must be seeded with a template that is used for CloudStack system VMs."
+msgstr ""
+
+#: ../../installation.rst:1280
+# 276b16c5387d4689a1693231ea26b1f7
+msgid "When copying and pasting a command, be sure the command has pasted as a single line before executing. Some document viewers may introduce unwanted line breaks in copied text."
+msgstr ""
+
+#: ../../installation.rst:1284
+# 57efaf7df3864902b8ef2abbc73b4fe7
+msgid "On the Management Server, run one or more of the following cloud-install-sys-tmplt commands to retrieve and decompress the system VM template. Run the command for each hypervisor type that you expect end users to run in this Zone."
+msgstr ""
+
+#: ../../installation.rst:1289
+# cf4e3c47521648d8b83c25db16adc62c
+msgid "If your secondary storage mount point is not named /mnt/secondary, substitute your own mount point name."
+msgstr ""
+
+#: ../../installation.rst:1292
+# 9384f6babb1045c182cbc634bb16abcd
+msgid "If you set the CloudStack database encryption type to \"web\" when you set up the database, you must now add the parameter -s <management-server-secret-key>. See :ref:`about-password-key-encryption`."
+msgstr ""
+
+#: ../../installation.rst:1296
+# 5fc96ec6465e4326b964d68cfc4396c9
+msgid "This process will require approximately 5 GB of free space on the local file system and up to 30 minutes each time it runs."
+msgstr ""
+
+#: ../../installation.rst:1301
+# 9e9bde198fcb43d3b927a01bdfa137d5
+msgid "For Hyper-V"
+msgstr ""
+
+#: ../../installation.rst:1309
+# 46a77ceb62484aa88c3491e231b15df4
+msgid "For XenServer:"
+msgstr ""
+
+#: ../../installation.rst:1317
+# 5f4480aedeaa4a2f8f73256e4f2ac00d
+msgid "For vSphere:"
+msgstr ""
+
+#: ../../installation.rst:1325
+# e2b895940e914161bc6cfffb3d156ae6
+msgid "For KVM:"
+msgstr ""
+
+#: ../../installation.rst:1333
+# f8238ce0c40b43c9ab8396a8b02321bc
+msgid "For LXC:"
+msgstr ""
+
+#: ../../installation.rst:1339
+# 5bd5fd295e884baab61eccc5daf0a4ec
+msgid "On Ubuntu, use the following path instead:"
+msgstr ""
+
+#: ../../installation.rst:1347
+# 85ce8593355f46cdb709714d94aa501c
+msgid "If you are using a separate NFS server, perform this step. If you are using the Management Server as the NFS server, you MUST NOT perform this step."
+msgstr ""
+
+#: ../../installation.rst:1351
+# 8ab48e57edc94c65aaeaf9476de618f5
+msgid "When the script has finished, unmount secondary storage and remove the created directory."
+msgstr ""
+
+#: ../../installation.rst:1361
+# 6568fbbe06444b5eb10f413094b1ccab
+msgid "Repeat these steps for each secondary storage server."
+msgstr ""
+
+#: ../../installation.rst:1364
+# 1730814b960b4780b44870649cde8b07
+msgid "Installation Complete! Next Steps"
+msgstr ""
+
+#: ../../installation.rst:1366
+# 6d13368c0331401693f21fdeca1b32b2
+msgid "Congratulations! You have now installed CloudStack Management Server and the database it uses to persist system data."
+msgstr ""
+
+#: ../../installation.rst:1369
+# b550a3b2345246bcb9cde46b834d9425
+msgid "|installation-complete.png: Finished installs with single Management Server and multiple Management Servers|"
+msgstr ""
+
+#: ../../installation.rst:1372
+# c3751fb65ae74573bc9c94685a08ba01
+msgid "What should you do next?"
+msgstr ""
+
+#: ../../installation.rst:1376
+# cada82145db24a15ad53e3d0143b1913
+msgid "Even without adding any cloud infrastructure, you can run the UI to get a feel for what's offered and how you will interact with CloudStack on an ongoing basis. See Log In to the UI."
+msgstr ""
+
+#: ../../installation.rst:1382
+# c731424997214c7eb7e757b58abe6e73
+msgid "When you're ready, add the cloud infrastructure and try running some virtual machines on it, so you can watch how CloudStack manages the infrastructure. See Provision Your Cloud Infrastructure."
+msgstr ""
+
[7/7] git commit: setup i18n with transifex and sphinx-intl
Posted by se...@apache.org.
setup i18n with transifex and sphinx-intl
Project: http://git-wip-us.apache.org/repos/asf/cloudstack-docs-install/repo
Commit: http://git-wip-us.apache.org/repos/asf/cloudstack-docs-install/commit/bd81bcc4
Tree: http://git-wip-us.apache.org/repos/asf/cloudstack-docs-install/tree/bd81bcc4
Diff: http://git-wip-us.apache.org/repos/asf/cloudstack-docs-install/diff/bd81bcc4
Branch: refs/heads/master
Commit: bd81bcc4a775970e7074f9578013174ef7497ef8
Parents: b1f7a0f
Author: Sebastien Goasguen <ru...@gmail.com>
Authored: Mon Mar 31 14:06:48 2014 -0400
Committer: Sebastien Goasguen <ru...@gmail.com>
Committed: Mon Mar 31 14:06:48 2014 -0400
----------------------------------------------------------------------
.gitignore | 1 +
.tx/config | 59 +
Makefile | 4 +-
README.rst | 34 +
source/locale/pot/building_from_source.pot | 433 ++
.../pot/choosing_deployment_architecture.pot | 511 ++
source/locale/pot/configuration.pot | 2565 +++++++
source/locale/pot/hypervisor_installation.pot | 4221 +++++++++++
source/locale/pot/index.pot | 88 +
source/locale/pot/installation.pot | 1224 ++++
source/locale/pot/managing_networks.pot | 6769 ++++++++++++++++++
source/locale/pot/network_setup.pot | 1713 +++++
source/locale/pot/optional_installation.pot | 1252 ++++
source/locale/pot/qig.pot | 682 ++
source/locale/pot/storage_setup.pot | 290 +
15 files changed, 19844 insertions(+), 2 deletions(-)
----------------------------------------------------------------------
http://git-wip-us.apache.org/repos/asf/cloudstack-docs-install/blob/bd81bcc4/.gitignore
----------------------------------------------------------------------
diff --git a/.gitignore b/.gitignore
index 9029067..7eea884 100644
--- a/.gitignore
+++ b/.gitignore
@@ -15,6 +15,7 @@
# under the License.
/build
+/source/locale/pot/.doctrees
# OS generated files #
######################
http://git-wip-us.apache.org/repos/asf/cloudstack-docs-install/blob/bd81bcc4/.tx/config
----------------------------------------------------------------------
diff --git a/.tx/config b/.tx/config
new file mode 100644
index 0000000..1ec5c80
--- /dev/null
+++ b/.tx/config
@@ -0,0 +1,59 @@
+[main]
+host = https://www.transifex.com
+type = PO
+
+[apache-cloudstack-installation-rtd.building_from_source]
+file_filter = source/locale/<lang>/LC_MESSAGES/building_from_source.po
+source_file = source/locale/pot/building_from_source.pot
+source_lang = en
+
+[apache-cloudstack-installation-rtd.choosing_deployment_architecture]
+file_filter = source/locale/<lang>/LC_MESSAGES/choosing_deployment_architecture.po
+source_file = source/locale/pot/choosing_deployment_architecture.pot
+source_lang = en
+
+[apache-cloudstack-installation-rtd.configuration]
+file_filter = source/locale/<lang>/LC_MESSAGES/configuration.po
+source_file = source/locale/pot/configuration.pot
+source_lang = en
+
+[apache-cloudstack-installation-rtd.hypervisor_installation]
+file_filter = source/locale/<lang>/LC_MESSAGES/hypervisor_installation.po
+source_file = source/locale/pot/hypervisor_installation.pot
+source_lang = en
+
+[apache-cloudstack-installation-rtd.index]
+file_filter = source/locale/<lang>/LC_MESSAGES/index.po
+source_file = source/locale/pot/index.pot
+source_lang = en
+
+[apache-cloudstack-installation-rtd.installation]
+file_filter = source/locale/<lang>/LC_MESSAGES/installation.po
+source_file = source/locale/pot/installation.pot
+source_lang = en
+
+[apache-cloudstack-installation-rtd.managing_networks]
+file_filter = source/locale/<lang>/LC_MESSAGES/managing_networks.po
+source_file = source/locale/pot/managing_networks.pot
+source_lang = en
+
+[apache-cloudstack-installation-rtd.network_setup]
+file_filter = source/locale/<lang>/LC_MESSAGES/network_setup.po
+source_file = source/locale/pot/network_setup.pot
+source_lang = en
+
+[apache-cloudstack-installation-rtd.optional_installation]
+file_filter = source/locale/<lang>/LC_MESSAGES/optional_installation.po
+source_file = source/locale/pot/optional_installation.pot
+source_lang = en
+
+[apache-cloudstack-installation-rtd.qig]
+file_filter = source/locale/<lang>/LC_MESSAGES/qig.po
+source_file = source/locale/pot/qig.pot
+source_lang = en
+
+[apache-cloudstack-installation-rtd.storage_setup]
+file_filter = source/locale/<lang>/LC_MESSAGES/storage_setup.po
+source_file = source/locale/pot/storage_setup.pot
+source_lang = en
+
http://git-wip-us.apache.org/repos/asf/cloudstack-docs-install/blob/bd81bcc4/Makefile
----------------------------------------------------------------------
diff --git a/Makefile b/Makefile
index 5187a30..ad6bfb1 100644
--- a/Makefile
+++ b/Makefile
@@ -162,9 +162,9 @@ info:
@echo "makeinfo finished; the Info files are in $(BUILDDIR)/texinfo."
gettext:
- $(SPHINXBUILD) -b gettext $(I18NSPHINXOPTS) $(BUILDDIR)/locale
+ $(SPHINXBUILD) -b gettext $(I18NSPHINXOPTS) source/locale/pot
@echo
- @echo "Build finished. The message catalogs are in $(BUILDDIR)/locale."
+ @echo "Build finished. The message catalogs are in source/locale/pot"
changes:
$(SPHINXBUILD) -b changes $(ALLSPHINXOPTS) $(BUILDDIR)/changes
http://git-wip-us.apache.org/repos/asf/cloudstack-docs-install/blob/bd81bcc4/README.rst
----------------------------------------------------------------------
diff --git a/README.rst b/README.rst
index bb8d609..9d25ba7 100644
--- a/README.rst
+++ b/README.rst
@@ -24,6 +24,40 @@ Website
This installation guide is on-line at <http://cloudstack-installation.readthedocs.org/en/latest/>
+Translation
+===========
+
+Clean the build
+
+::
+ make clean
+
+Generate the .pot files
+
+::
+ make gettext
+
+Generate the .tx/config files with:
+
+::
+ sphinx-intl update-txconfig-resources --pot-dir source/locale/pot --transifex-project-name apache-cloudstack-installation-rtd --locale-dir source/locale
+
+Push the .pot files to transifex with:
+
+::
+ tx push -s
+
+Download the translated strings, for example Japanese (ja):
+
+::
+ tx pull -l ja
+
+Build the translated docs:
+
+::
+ sphinx-intl build --locale-dir source/locale
+ make -e SPHINXOPTS="-D language='ja'" html
+
Feedback
========
http://git-wip-us.apache.org/repos/asf/cloudstack-docs-install/blob/bd81bcc4/source/locale/pot/building_from_source.pot
----------------------------------------------------------------------
diff --git a/source/locale/pot/building_from_source.pot b/source/locale/pot/building_from_source.pot
new file mode 100644
index 0000000..c7a1d7c
--- /dev/null
+++ b/source/locale/pot/building_from_source.pot
@@ -0,0 +1,433 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2014, Apache Software Foundation
+# This file is distributed under the same license as the Apache CloudStack Installation Documentation package.
+# FIRST AUTHOR <EM...@ADDRESS>, YEAR.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: Apache CloudStack Installation Documentation 4\n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2014-03-31 14:02-0400\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"
+
+#: ../../building_from_source.rst:17
+# 5396f27a8ff74a7d8817526ff37ec438
+msgid "Building from Source"
+msgstr ""
+
+#: ../../building_from_source.rst:19
+# 60bf699c76df434992e36d41c5f00bcf
+msgid "The official CloudStack release is always in source code form. You will likely be able to find \"convenience binaries,\" the source is the canonical release. In this section, we'll cover acquiring the source release and building that so that you can deploy it using Maven or create Debian packages or RPMs."
+msgstr ""
+
+#: ../../building_from_source.rst:25
+# 32892fc6365642cd81e9910e84bb80c0
+msgid "Note that building and deploying directly from source is typically not the most efficient way to deploy an IaaS. However, we will cover that method as well as building RPMs or Debian packages for deploying CloudStack."
+msgstr ""
+
+#: ../../building_from_source.rst:30
+# 7e67792d5ec241af80724aa269cc8f40
+msgid "The instructions here are likely version-specific. That is, the method for building from source for the 4.0.x series is different from the 4.1.x series."
+msgstr ""
+
+#: ../../building_from_source.rst:34
+# 59bd739639154797bb627d316198b3d2
+msgid "If you are working with a unreleased version of CloudStack, see the INSTALL.md file in the top-level directory of the release."
+msgstr ""
+
+#: ../../building_from_source.rst:38
+# 54b5d37f192048519bd2ed85a3ddc5b3
+msgid "Getting the release"
+msgstr ""
+
+#: ../../building_from_source.rst:40
+# d3311764aeed4cc0b185062d99f5c4e9
+msgid "You can download the latest CloudStack release from the `Apache CloudStack project download page <http://cloudstack.apache.org/downloads.html>`_."
+msgstr ""
+
+#: ../../building_from_source.rst:43
+# c0f0cbed8f7942dd8cdf0ec15232e760
+msgid "Prior releases are available via archive.apache.org as well. See the downloads page for more information on archived releases."
+msgstr ""
+
+#: ../../building_from_source.rst:46
+# efebd9e2df61457482c9cb8efbadd736
+msgid "You'll notice several links under the 'Latest release' section. A link to a file ending in ``tar.bz2``, as well as a PGP/GPG signature, MD5, and SHA512 file."
+msgstr ""
+
+#: ../../building_from_source.rst:52
+# c8757326ca1c47f989906e77b64c17db
+msgid "The ``tar.bz2`` file contains the Bzip2-compressed tarball with the source code."
+msgstr ""
+
+#: ../../building_from_source.rst:57
+# d1f48a19cc14413e90a8164ef6e496ed
+msgid "The ``.asc`` file is a detached cryptographic signature that can be used to help verify the authenticity of the release."
+msgstr ""
+
+#: ../../building_from_source.rst:62
+# b45289cb4cba4686b60ab976bf75eea1
+msgid "The ``.md5`` file is an MD5 hash of the release to aid in verify the validity of the release download."
+msgstr ""
+
+#: ../../building_from_source.rst:67
+# 637044e3649f406b8e5b6a441ba355c7
+msgid "The ``.sha`` file is a SHA512 hash of the release to aid in verify the validity of the release download."
+msgstr ""
+
+#: ../../building_from_source.rst:71
+# 4da67860f4454b7aa0c0fc6f76b59317
+msgid "Verifying the downloaded release"
+msgstr ""
+
+#: ../../building_from_source.rst:73
+# 184cd04b405b4136b74c0644e4720e2a
+msgid "There are a number of mechanisms to check the authenticity and validity of a downloaded release."
+msgstr ""
+
+#: ../../building_from_source.rst:77
+# 787318aa8f2049098a34030e7bb9220d
+msgid "Getting the KEYS"
+msgstr ""
+
+#: ../../building_from_source.rst:79
+# af2e7aafde3c45d79c93d848f16df84f
+msgid "To enable you to verify the GPG signature, you will need to download the `KEYS <http://www.apache.org/dist/cloudstack/KEYS>`_ file."
+msgstr ""
+
+#: ../../building_from_source.rst:82
+# b7351a3de11b4d5783f051a524e6d6d9
+msgid "You next need to import those keys, which you can do by running:"
+msgstr ""
+
+#: ../../building_from_source.rst:89
+# 6a67d67c239c4450b6b0454f78e1e976
+msgid "GPG"
+msgstr ""
+
+#: ../../building_from_source.rst:91
+# c41516ba45df4b8c8c82f0437fd1cf0f
+msgid "The CloudStack project provides a detached GPG signature of the release. To check the signature, run the following command:"
+msgstr ""
+
+#: ../../building_from_source.rst:98
+# 06a586af894b41a191ca74d565fd5646
+msgid "If the signature is valid you will see a line of output that contains 'Good signature'."
+msgstr ""
+
+#: ../../building_from_source.rst:102
+# 7c1c3790e01440f88dc8e8f108c69180
+msgid "MD5"
+msgstr ""
+
+#: ../../building_from_source.rst:104
+# e47ab7059cdf4276968ef9219d824967
+msgid "In addition to the cryptographic signature, CloudStack has an MD5 checksum that you can use to verify the download matches the release. You can verify this hash by executing the following command:"
+msgstr ""
+
+#: ../../building_from_source.rst:112
+# 471b0fafe73b4bebb48f271b2be0323b
+msgid "If this successfully completes you should see no output. If there is any output from them, then there is a difference between the hash you generated locally and the hash that has been pulled from the server."
+msgstr ""
+
+#: ../../building_from_source.rst:117
+# a42234cf484d448ea3a079cc44d505c4
+msgid "SHA512"
+msgstr ""
+
+#: ../../building_from_source.rst:119
+# f6904f51119c4bd7a0e6d9d42868d7cd
+msgid "In addition to the MD5 hash, the CloudStack project provides a SHA512 cryptographic hash to aid in assurance of the validity of the downloaded release. You can verify this hash by executing the following command:"
+msgstr ""
+
+#: ../../building_from_source.rst:127
+# 2b02e428976242d5a9513dc999f80d9a
+msgid "If this command successfully completes you should see no output. If there is any output from them, then there is a difference between the hash you generated locally and the hash that has been pulled from the server."
+msgstr ""
+
+#: ../../building_from_source.rst:133
+# 20ae79e8693540af926f68f5b8a08da3
+msgid "Prerequisites for building Apache CloudStack"
+msgstr ""
+
+#: ../../building_from_source.rst:135
+# 8de67a9fdaea48faa67ab89f641adc4b
+msgid "There are a number of prerequisites needed to build CloudStack. This document assumes compilation on a Linux system that uses RPMs or DEBs for package management."
+msgstr ""
+
+#: ../../building_from_source.rst:139
+# 9c13e54d32b5455aaab36099aa2535a4
+msgid "You will need, at a minimum, the following to compile CloudStack:"
+msgstr ""
+
+#: ../../building_from_source.rst:143
+# 0146a3cb86884d318cf934c639b76449
+msgid "Maven (version 3)"
+msgstr ""
+
+#: ../../building_from_source.rst:147
+# 005189dfa25b4c66b039e0267fdbea5e
+msgid "Java (OpenJDK 1.6 or Java 7/OpenJDK 1.7)"
+msgstr ""
+
+#: ../../building_from_source.rst:151
+# 2c58fc00271e445e861705983b16a5f3
+msgid "Apache Web Services Common Utilities (ws-commons-util)"
+msgstr ""
+
+#: ../../building_from_source.rst:155
+# 989f684d1b8a456bac9a81d3f924d16f
+msgid "MySQL"
+msgstr ""
+
+#: ../../building_from_source.rst:159
+# 44ef1202eb3e4c61b84f22fbc433a538
+msgid "MySQLdb (provides Python database API)"
+msgstr ""
+
+#: ../../building_from_source.rst:163
+# e84e7644c89a4669991bc0a1013171c1
+msgid "Tomcat 6 (not 6.0.35)"
+msgstr ""
+
+#: ../../building_from_source.rst:167
+# fe2b1db48eb9421d937189144b944911
+msgid "genisoimage"
+msgstr ""
+
+#: ../../building_from_source.rst:171
+# bc55f42faeef4adbb28f3b39cfe334ef
+msgid "rpmbuild or dpkg-dev"
+msgstr ""
+
+#: ../../building_from_source.rst:174
+# 7b45a167b6874f9a8ba73a17d7f1a6c5
+msgid "Extracting source"
+msgstr ""
+
+#: ../../building_from_source.rst:176
+# 3b2090380fcf4c12ad2638d91cb45d43
+msgid "Extracting the CloudStack release is relatively simple and can be done with a single command as follows:"
+msgstr ""
+
+#: ../../building_from_source.rst:183
+# 0f5f07d38bd54fb2a0e69c6fb28e1967
+msgid "You can now move into the directory:"
+msgstr ""
+
+#: ../../building_from_source.rst:190
+# aa9e9e76ff6441498d8531802e1afa7e
+msgid "Building DEB packages"
+msgstr ""
+
+#: ../../building_from_source.rst:192
+# 0eca44ba0f1c4b3ba1e65ab3a0268db9
+msgid "In addition to the bootstrap dependencies, you'll also need to install several other dependencies. Note that we recommend using Maven 3, which is not currently available in 12.04.1 LTS. So, you'll also need to add a PPA repository that includes Maven 3. After running the command ``add-apt-repository``, you will be prompted to continue and a GPG key will be added."
+msgstr ""
+
+#: ../../building_from_source.rst:207
+# 8014eb3c824248f28bfaff9deeabaced
+msgid "While we have defined, and you have presumably already installed the bootstrap prerequisites, there are a number of build time prerequisites that need to be resolved. CloudStack uses maven for dependency resolution. You can resolve the buildtime depdencies for CloudStack by running:"
+msgstr ""
+
+#: ../../building_from_source.rst:217
+# f6f09e0f7e3c49129fe0c281cc144489
+msgid "Now that we have resolved the dependencies we can move on to building CloudStack and packaging them into DEBs by issuing the following command."
+msgstr ""
+
+#: ../../building_from_source.rst:225
+# f345823b71dc4836a97a160bfbb40a9e
+msgid "This command will build the following debian packages. You should have all of the following:"
+msgstr ""
+
+#: ../../building_from_source.rst:239
+# 88e77857a4fa4e9b80e912d82a405591
+msgid "Setting up an APT repo"
+msgstr ""
+
+#: ../../building_from_source.rst:241
+# 7db71198e1aa4db08ce8f174f11546aa
+msgid "After you've created the packages, you'll want to copy them to a system where you can serve the packages over HTTP. You'll create a directory for the packages and then use ``dpkg-scanpackages`` to create ``Packages.gz``, which holds information about the archive structure. Finally, you'll add the repository to your system(s) so you can install the packages using APT."
+msgstr ""
+
+#: ../../building_from_source.rst:248
+# 882df6f5a6a542e08af5d64a8c440f9b
+msgid "The first step is to make sure that you have the **dpkg-dev** package installed. This should have been installed when you pulled in the **debhelper** application previously, but if you're generating ``Packages.gz`` on a different system, be sure that it's installed there as well."
+msgstr ""
+
+#: ../../building_from_source.rst:258
+# 6b45808c7afe48eab8f0e54e28996c78
+msgid "The next step is to copy the DEBs to the directory where they can be served over HTTP. We'll use ``/var/www/cloudstack/repo`` in the examples, but change the directory to whatever works for you."
+msgstr ""
+
+#: ../../building_from_source.rst:271
+# 9f7bfa37a80641409e1400b8548efb29
+msgid "You can safely ignore the warning about a missing override file."
+msgstr ""
+
+#: ../../building_from_source.rst:273
+# d8e564f896ea416898d007e9d49d6718
+msgid "Now you should have all of the DEB packages and ``Packages.gz`` in the ``binary`` directory and available over HTTP. (You may want to use ``wget`` or ``curl`` to test this before moving on to the next step.)"
+msgstr ""
+
+#: ../../building_from_source.rst:278
+# c7c808299766447184af66ba621c649f
+msgid "Configuring your machines to use the APT repository"
+msgstr ""
+
+#: ../../building_from_source.rst:280
+# dfdd1c5b583743d0b5156002e9f3ffb9
+msgid "Now that we have created the repository, you need to configure your machine to make use of the APT repository. You can do this by adding a repository file under ``/etc/apt/sources.list.d``. Use your preferred editor to create ``/etc/apt/sources.list.d/cloudstack.list`` with this line:"
+msgstr ""
+
+#: ../../building_from_source.rst:290
+# 8cad604cc3474e2bb424225f2d519465
+msgid "Now that you have the repository info in place, you'll want to run another update so that APT knows where to find the CloudStack packages."
+msgstr ""
+
+#: ../../building_from_source.rst:297
+# ae0dd676f4ec4158b5f3bd6fd9c6c414
+msgid "You can now move on to the instructions under Install on Ubuntu."
+msgstr ""
+
+#: ../../building_from_source.rst:300
+# 99e76b064e8447a78d810b22c43f6f41
+msgid "Building RPMs from Source"
+msgstr ""
+
+#: ../../building_from_source.rst:302
+# f2be124577f84dd497fb762733f58ef8
+msgid "As mentioned previously in `“Prerequisites for building Apache CloudStack” <#prerequisites-for-building-apache-cloudstack>`_, you will need to install several prerequisites before you can build packages for CloudStack. Here we'll assume you're working with a 64-bit build of CentOS or Red Hat Enterprise Linux."
+msgstr ""
+
+#: ../../building_from_source.rst:316
+# 147d967fe07344fda8b630d94ecbf22e
+msgid "Next, you'll need to install build-time dependencies for CloudStack with Maven. We're using Maven 3, so you'll want to `grab a Maven 3 tarball <http://maven.apache.org/download.cgi>`_ and uncompress it in your home directory (or whatever location you prefer):"
+msgstr ""
+
+#: ../../building_from_source.rst:329
+# 1a9e316005174aeaa91a7dcfbaade092
+msgid "Maven also needs to know where Java is, and expects the JAVA\\_HOME environment variable to be set:"
+msgstr ""
+
+#: ../../building_from_source.rst:336
+# 4ab8a6164f45425aa7186cdf64e8d55e
+msgid "Verify that Maven is installed correctly:"
+msgstr ""
+
+#: ../../building_from_source.rst:342
+# 3843f8810db04c80a8eee7f3cae3f4bf
+msgid "You probably want to ensure that your environment variables will survive a logout/reboot. Be sure to update ``~/.bashrc`` with the PATH and JAVA\\_HOME variables."
+msgstr ""
+
+#: ../../building_from_source.rst:346
+# 490ba6dd066441edb4adc61fb071e8a7
+msgid "Building RPMs for CloudStack is fairly simple. Assuming you already have the source downloaded and have uncompressed the tarball into a local directory, you're going to be able to generate packages in just a few minutes."
+msgstr ""
+
+#: ../../building_from_source.rst:353
+# e0cc268134ba44c9a96d06b97e687c39
+msgid "Packaging has Changed. If you've created packages for CloudStack previously, you should be aware that the process has changed considerably since the project has moved to using Apache Maven. Please be sure to follow the steps in this section closely."
+msgstr ""
+
+#: ../../building_from_source.rst:356
+# b79c6f303f0544719c940cfc32027819
+msgid "Generating RPMS"
+msgstr ""
+
+#: ../../building_from_source.rst:358
+# 03b60158092748f6aa6b7d5994c892d2
+msgid "Now that we have the prerequisites and source, you will cd to the `packaging/centos63/` directory."
+msgstr ""
+
+#: ../../building_from_source.rst:364
+# 3154e33699074662a1395386b9c3a4a8
+msgid "Generating RPMs is done using the ``package.sh`` script:"
+msgstr ""
+
+#: ../../building_from_source.rst:370
+# 68d539d69bc54749a69f503b004525b0
+msgid "That will run for a bit and then place the finished packages in ``dist/rpmbuild/RPMS/x86_64/``."
+msgstr ""
+
+#: ../../building_from_source.rst:373
+# 6ba124f893f243f7af26aefe9811bc73
+msgid "You should see the following RPMs in that directory:"
+msgstr ""
+
+#: ../../building_from_source.rst:386
+# 370fc4f0661540ca95e53491f26361ea
+msgid "Creating a yum repo"
+msgstr ""
+
+#: ../../building_from_source.rst:388
+# bbc6c3630b1a44dd92fe24fb24a32c43
+msgid "While RPMs is a useful packaging format - it's most easily consumed from Yum repositories over a network. The next step is to create a Yum Repo with the finished packages:"
+msgstr ""
+
+#: ../../building_from_source.rst:404
+# 7ca5148dbc3f47a195336d3ea4dc066d
+msgid "The files and directories within ``~/tmp/repo`` can now be uploaded to a web server and serve as a yum repository."
+msgstr ""
+
+#: ../../building_from_source.rst:408
+# 3c1f1920404c4b4b9aed29b8216a8ca1
+msgid "Configuring your systems to use your new yum repository"
+msgstr ""
+
+#: ../../building_from_source.rst:410
+# bbc87560e0c642ecbfa67f722b3b9693
+msgid "Now that your yum repository is populated with RPMs and metadata we need to configure the machines that need to install CloudStack. Create a file named ``/etc/yum.repos.d/cloudstack.repo`` with this information:"
+msgstr ""
+
+#: ../../building_from_source.rst:422
+# b398f895b7ff4282b6613bad45a98c08
+msgid "Completing this step will allow you to easily install CloudStack on a number of machines across the network."
+msgstr ""
+
+#: ../../building_from_source.rst:426
+# 478d4e8b829044e8949f587dd0f09b52
+msgid "Building Non-OSS"
+msgstr ""
+
+#: ../../building_from_source.rst:428
+# 2fe549e0cdc44e51ba030c3fa3499914
+msgid "If you need support for the VMware, NetApp, F5, NetScaler, SRX, or any other non-Open Source Software (nonoss) plugins, you'll need to download a few components on your own and follow a slightly different procedure to build from source."
+msgstr ""
+
+#: ../../building_from_source.rst:435
+# 46d5a64c225c401c8e2b16f77095e6f3
+msgid "Some of the plugins supported by CloudStack cannot be distributed with CloudStack for licensing reasons. In some cases, some of the required libraries/JARs are under a proprietary license. In other cases, the required libraries may be under a license that's not compatible with `Apache's licensing guidelines for third-party products <http://www.apache.org/legal/resolved.html#category-x>`_."
+msgstr ""
+
+#: ../../building_from_source.rst:439
+# b30c64ffa9bb46819fc70c71f7606020
+msgid "To build the Non-OSS plugins, you'll need to have the requisite JARs installed under the ``deps`` directory."
+msgstr ""
+
+#: ../../building_from_source.rst:442
+# 965deab2226a46d98c7e5962c98f344e
+msgid "Because these modules require dependencies that can't be distributed with CloudStack you'll need to download them yourself. Links to the most recent dependencies are listed on the `*How to build CloudStack* <https://cwiki.apache.org/confluence/display/CLOUDSTACK/How+to+build+CloudStack>`_ page on the wiki."
+msgstr ""
+
+#: ../../building_from_source.rst:449
+# 78a1f8deba41498f80a2f83003d44bc3
+msgid "You may also need to download `vhd-util <http://download.cloud.com.s3.amazonaws.com/tools/vhd-util>`_, which was removed due to licensing issues. You'll copy vhd-util to the ``scripts/vm/hypervisor/xenserver/`` directory."
+msgstr ""
+
+#: ../../building_from_source.rst:456
+# b4c294257936418c9d6c6889ce615a13
+msgid "Once you have all the dependencies copied over, you'll be able to build CloudStack with the ``noredist`` option:"
+msgstr ""
+
+#: ../../building_from_source.rst:466
+# c135a16bcffe490da30abf3c3425ccdb
+msgid "Once you've built CloudStack with the ``noredist`` profile, you can package it using the `“Building RPMs from Source” <#building-rpms-from-source>`_ or `“Building DEB packages” <#building-deb-packages>`_ instructions."
+msgstr ""
+
http://git-wip-us.apache.org/repos/asf/cloudstack-docs-install/blob/bd81bcc4/source/locale/pot/choosing_deployment_architecture.pot
----------------------------------------------------------------------
diff --git a/source/locale/pot/choosing_deployment_architecture.pot b/source/locale/pot/choosing_deployment_architecture.pot
new file mode 100644
index 0000000..fbf1045
--- /dev/null
+++ b/source/locale/pot/choosing_deployment_architecture.pot
@@ -0,0 +1,511 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2014, Apache Software Foundation
+# This file is distributed under the same license as the Apache CloudStack Installation Documentation package.
+# FIRST AUTHOR <EM...@ADDRESS>, YEAR.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: Apache CloudStack Installation Documentation 4\n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2014-03-31 14:02-0400\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"
+
+#: ../../choosing_deployment_architecture.rst:17
+# 52edd48cc24f4706b9641e18921e1dfc
+msgid "Choosing a Deployment Architecture"
+msgstr ""
+
+#: ../../choosing_deployment_architecture.rst:19
+# 4ebda8e26c5642b79a5e800fb698afcf
+msgid "The architecture used in a deployment will vary depending on the size and purpose of the deployment. This section contains examples of deployment architecture, including a small-scale deployment useful for test and trial deployments and a fully-redundant large-scale setup for production deployments."
+msgstr ""
+
+#: ../../choosing_deployment_architecture.rst:26
+# e6eca26710584474b1704256861555bd
+msgid "Small-Scale Deployment"
+msgstr ""
+
+#: ../../choosing_deployment_architecture.rst:28
+# 504a3c65a9d44537bca5bac7444ffe77
+msgid "|Small-Scale Deployment|"
+msgstr ""
+
+#: ../../choosing_deployment_architecture.rst:30
+# f11bad72391b4deb92c5d7118b32d881
+msgid "This diagram illustrates the network architecture of a small-scale CloudStack deployment."
+msgstr ""
+
+#: ../../choosing_deployment_architecture.rst:35
+# 6ba24ea751eb44d985b826558267d392
+msgid "A firewall provides a connection to the Internet. The firewall is configured in NAT mode. The firewall forwards HTTP requests and API calls from the Internet to the Management Server. The Management Server resides on the management network."
+msgstr ""
+
+#: ../../choosing_deployment_architecture.rst:42
+# 3426fafddfbd47eca9b6e972998e3bae
+msgid "A layer-2 switch connects all physical servers and storage."
+msgstr ""
+
+#: ../../choosing_deployment_architecture.rst:46
+# ef86a72ce6a44739aa9e46e68b64df56
+msgid "A single NFS server functions as both the primary and secondary storage."
+msgstr ""
+
+#: ../../choosing_deployment_architecture.rst:51
+# f507e94ad4584311980de03cd3e8915b
+msgid "The Management Server is connected to the management network."
+msgstr ""
+
+#: ../../choosing_deployment_architecture.rst:54
+# 1ffca21a6b404d6894a747a4583dbad8
+msgid "Large-Scale Redundant Setup"
+msgstr ""
+
+#: ../../choosing_deployment_architecture.rst:56
+# 99045d1800c5403d892894a8d4fc8002
+msgid "|Large-Scale Redundant Setup|"
+msgstr ""
+
+#: ../../choosing_deployment_architecture.rst:58
+# d6858644d12a4f22b3de25594cedc309
+msgid "This diagram illustrates the network architecture of a large-scale CloudStack deployment."
+msgstr ""
+
+#: ../../choosing_deployment_architecture.rst:63
+# c4c3f668a4a145c1ac376c5ee607dccb
+msgid "A layer-3 switching layer is at the core of the data center. A router redundancy protocol like VRRP should be deployed. Typically high-end core switches also include firewall modules. Separate firewall appliances may also be used if the layer-3 switch does not have integrated firewall capabilities. The firewalls are configured in NAT mode. The firewalls provide the following functions:"
+msgstr ""
+
+#: ../../choosing_deployment_architecture.rst:72
+# a23de965c5ec447c84154204ca887790
+msgid "Forwards HTTP requests and API calls from the Internet to the Management Server. The Management Server resides on the management network."
+msgstr ""
+
+#: ../../choosing_deployment_architecture.rst:78
+# 90da3245af0d4917b933c01a6c8f8332
+msgid "When the cloud spans multiple zones, the firewalls should enable site-to-site VPN such that servers in different zones can directly reach each other."
+msgstr ""
+
+#: ../../choosing_deployment_architecture.rst:84
+# 69cfdebf1e6e4d549b52b88a593df61e
+msgid "A layer-2 access switch layer is established for each pod. Multiple switches can be stacked to increase port count. In either case, redundant pairs of layer-2 switches should be deployed."
+msgstr ""
+
+#: ../../choosing_deployment_architecture.rst:90
+# 3902d59efe794d8da02773b18a3144ff
+msgid "The Management Server cluster (including front-end load balancers, Management Server nodes, and the MySQL database) is connected to the management network through a pair of load balancers."
+msgstr ""
+
+#: ../../choosing_deployment_architecture.rst:96
+# 1f11aed9571044e9b9fc673435cb0de7
+msgid "Secondary storage servers are connected to the management network."
+msgstr ""
+
+#: ../../choosing_deployment_architecture.rst:100
+# ea82de9a210d4a228f110dfe9ecdfb1e
+msgid "Each pod contains storage and computing servers. Each storage and computing server should have redundant NICs connected to separate layer-2 access switches."
+msgstr ""
+
+#: ../../choosing_deployment_architecture.rst:105
+# 7ceefe1102644c9ab58eed60cdb7f2bd
+msgid "Separate Storage Network"
+msgstr ""
+
+#: ../../choosing_deployment_architecture.rst:107
+# 983feefb13f1459ba566781908bfcd93
+msgid "In the large-scale redundant setup described in the previous section, storage traffic can overload the management network. A separate storage network is optional for deployments. Storage protocols such as iSCSI are sensitive to network delays. A separate storage network ensures guest network traffic contention does not impact storage performance."
+msgstr ""
+
+#: ../../choosing_deployment_architecture.rst:114
+# edd1971372014c5abd34993129275f55
+msgid "Multi-Node Management Server"
+msgstr ""
+
+#: ../../choosing_deployment_architecture.rst:116
+# cb554f7ea8af4b899da19bad60af3f11
+msgid "The CloudStack Management Server is deployed on one or more front-end servers connected to a single MySQL database. Optionally a pair of hardware load balancers distributes requests from the web. A backup management server set may be deployed using MySQL replication at a remote site to add DR capabilities."
+msgstr ""
+
+#: ../../choosing_deployment_architecture.rst:122
+# 0507a6b19f114eb08708577219e394af
+msgid "|Multi-Node Management Server|"
+msgstr ""
+
+#: ../../choosing_deployment_architecture.rst:124
+# 2afcbc3e300d490d8526df89fe36c54f
+msgid "The administrator must decide the following."
+msgstr ""
+
+#: ../../choosing_deployment_architecture.rst:128
+# 6ea7062b2c3e4d67b082de9b02757b4e
+msgid "Whether or not load balancers will be used."
+msgstr ""
+
+#: ../../choosing_deployment_architecture.rst:132
+# 7625aabc231a4cddb9af421ea15281d0
+msgid "How many Management Servers will be deployed."
+msgstr ""
+
+#: ../../choosing_deployment_architecture.rst:136
+# ed2af9d37ed34e6e89c234099fcccb4b
+msgid "Whether MySQL replication will be deployed to enable disaster recovery."
+msgstr ""
+
+#: ../../choosing_deployment_architecture.rst:140
+# be8d00f78d464cc2aa58e01d300a948b
+msgid "Multi-Site Deployment"
+msgstr ""
+
+#: ../../choosing_deployment_architecture.rst:142
+# 1fff976cf3344b6a8c06c3b56d9568ef
+msgid "The CloudStack platform scales well into multiple sites through the use of zones. The following diagram shows an example of a multi-site deployment."
+msgstr ""
+
+#: ../../choosing_deployment_architecture.rst:146
+# ef026e2d1151436eb064cd8bf77db549
+msgid "|Example Of A Multi-Site Deployment|"
+msgstr ""
+
+#: ../../choosing_deployment_architecture.rst:148
+# 7ea2ca98a7094edab2212c4e776e349b
+msgid "Data Center 1 houses the primary Management Server as well as zone 1. The MySQL database is replicated in real time to the secondary Management Server installation in Data Center 2."
+msgstr ""
+
+#: ../../choosing_deployment_architecture.rst:152
+# 39563946112d4b07afc28800922068ee
+msgid "|Separate Storage Network|"
+msgstr ""
+
+#: ../../choosing_deployment_architecture.rst:154
+# e7cc868c4aa64cbe80807d7809ce58cb
+msgid "This diagram illustrates a setup with a separate storage network. Each server has four NICs, two connected to pod-level network switches and two connected to storage network switches."
+msgstr ""
+
+#: ../../choosing_deployment_architecture.rst:158
+# 6157f0ee2cf84c49ac9f4f4ca1cdb0cd
+msgid "There are two ways to configure the storage network:"
+msgstr ""
+
+#: ../../choosing_deployment_architecture.rst:162
+# cc2bdc7b44e146c18dfb9826c12b15f0
+msgid "Bonded NIC and redundant switches can be deployed for NFS. In NFS deployments, redundant switches and bonded NICs still result in one network (one CIDR block+ default gateway address)."
+msgstr ""
+
+#: ../../choosing_deployment_architecture.rst:168
+# 0aa73c8538074a00b5b5305e33db5ed4
+msgid "iSCSI can take advantage of two separate storage networks (two CIDR blocks each with its own default gateway). Multipath iSCSI client can failover and load balance between separate storage networks."
+msgstr ""
+
+#: ../../choosing_deployment_architecture.rst:172
+# 0e03920329f540e08c1ea89e9a7d05dd
+msgid "|NIC Bonding And Multipath I/O|"
+msgstr ""
+
+#: ../../choosing_deployment_architecture.rst:174
+# 9219775ffce04cada583a2d12a90524f
+msgid "This diagram illustrates the differences between NIC bonding and Multipath I/O (MPIO). NIC bonding configuration involves only one network. MPIO involves two separate networks."
+msgstr ""
+
+#: ../../choosing_deployment_architecture.rst:180
+# 0b1fe0948d434c1baf1a34edbb1847a0
+msgid "Choosing a Hypervisor"
+msgstr ""
+
+#: ../../choosing_deployment_architecture.rst:182
+# f9313ca35f6f4589aed2bea3122829e7
+msgid "CloudStack supports many popular hypervisors. Your cloud can consist entirely of hosts running a single hypervisor, or you can use multiple hypervisors. Each cluster of hosts must run the same hypervisor."
+msgstr ""
+
+#: ../../choosing_deployment_architecture.rst:186
+# a54304966f514ffabe4dfad79eedc5eb
+msgid "You might already have an installed base of nodes running a particular hypervisor, in which case, your choice of hypervisor has already been made. If you are starting from scratch, you need to decide what hypervisor software best suits your needs. A discussion of the relative advantages of each hypervisor is outside the scope of our documentation. However, it will help you to know which features of each hypervisor are supported by CloudStack. The following table provides this information."
+msgstr ""
+
+#: ../../choosing_deployment_architecture.rst:195
+# 3693e4b064964090ac1242961e0a8946
+msgid "Feature"
+msgstr ""
+
+#: ../../choosing_deployment_architecture.rst:195
+# d3865d119f144b4d9207d2fd8e7578b9
+msgid "XenServer 6.0.2"
+msgstr ""
+
+#: ../../choosing_deployment_architecture.rst:195
+# b48b4cda653049f1a9422c908232ff17
+msgid "vSphere 4.1/5.0"
+msgstr ""
+
+#: ../../choosing_deployment_architecture.rst:195
+# fed595ccd4cc4c4a9623807e16fefde5
+msgid "KVM - RHEL 6.2"
+msgstr ""
+
+#: ../../choosing_deployment_architecture.rst:195
+# d393ed42dc224b8684dbf6d8ab9d99c2
+msgid "Bare Metal"
+msgstr ""
+
+#: ../../choosing_deployment_architecture.rst:197
+# 1ba867f8783d4ac38bca542e7a1248be
+msgid "Network Throttling"
+msgstr ""
+
+#: ../../choosing_deployment_architecture.rst:197
+#: ../../choosing_deployment_architecture.rst:197
+#: ../../choosing_deployment_architecture.rst:198
+#: ../../choosing_deployment_architecture.rst:198
+#: ../../choosing_deployment_architecture.rst:199
+#: ../../choosing_deployment_architecture.rst:199
+#: ../../choosing_deployment_architecture.rst:199
+#: ../../choosing_deployment_architecture.rst:200
+#: ../../choosing_deployment_architecture.rst:200
+#: ../../choosing_deployment_architecture.rst:200
+#: ../../choosing_deployment_architecture.rst:201
+#: ../../choosing_deployment_architecture.rst:201
+#: ../../choosing_deployment_architecture.rst:201
+#: ../../choosing_deployment_architecture.rst:201
+#: ../../choosing_deployment_architecture.rst:202
+#: ../../choosing_deployment_architecture.rst:202
+#: ../../choosing_deployment_architecture.rst:203
+#: ../../choosing_deployment_architecture.rst:203
+#: ../../choosing_deployment_architecture.rst:203
+#: ../../choosing_deployment_architecture.rst:206
+#: ../../choosing_deployment_architecture.rst:206
+#: ../../choosing_deployment_architecture.rst:206
+#: ../../choosing_deployment_architecture.rst:207
+#: ../../choosing_deployment_architecture.rst:207
+# be052665fb9c4db6abf644607c11a2ce
+# a4b89b4ef4524eaa817ecdc80d28220e
+# 19def2d9dbcc4ab2b156efdb3105c12c
+# 9ea945d4e8004ddc87df1fc03980dce1
+# 4b880eb52259476c8b34809b91f7d3a3
+# 5b1d1cb21d6e45418d722dfddd325379
+# f403583dce4044a984df0474dbd133ad
+# e854f5913eee4b7c8abc33a936ef79f5
+# 639f24e5f94f42c98eb830f204f15720
+# 80f0710f7c8b47a481f04b3014a226c1
+# 699e94d60d9e4854a476539896363037
+# aa96059d21ac4ebcba125d36c1152217
+# 8e95523da0cb41bfb474406df9fb8145
+# 27cff33f4c064fbeb2f9f48ecef6f1cb
+# 086c38882e6b42ab8947506109c27cfd
+# e3902495150d4d56979b58303e1c731c
+# 2020f8688efe46629b40a7250d3111d0
+# 66c69ff810ef4413bfb1945563069a19
+# 513c35fbd6f04423bd9c3d783a99b4dc
+# 84cff98be301475280c880d4da63670b
+# d91c60035cce41bf94a8091fb6c37bb3
+# 47bdf8e2d92f4d3a8a2817cc47bed1ed
+# c160f1f7b53544bc91fdbfae297359cb
+# 11fbe78348e24da89d9e7307aee4769c
+msgid "Yes"
+msgstr ""
+
+#: ../../choosing_deployment_architecture.rst:197
+#: ../../choosing_deployment_architecture.rst:198
+#: ../../choosing_deployment_architecture.rst:198
+#: ../../choosing_deployment_architecture.rst:204
+#: ../../choosing_deployment_architecture.rst:204
+#: ../../choosing_deployment_architecture.rst:204
+#: ../../choosing_deployment_architecture.rst:205
+#: ../../choosing_deployment_architecture.rst:205
+#: ../../choosing_deployment_architecture.rst:207
+# cd83b27113e841ac916e00bcd1082008
+# 1947bdafae1f4b5a9061c6eb1cb2b99c
+# d3de86e130104668a664aa03d61c32a6
+# c0adf6e94804483a9dbfd425bab70401
+# fa80ad1123b1402aaac21bfc7d19b636
+# 5dd1209f3e2a41d7aa8489e8ace6aadf
+# 280839b6b2744ce58570ac30f941863b
+# b2a56672e17b4744bf8c11d6f41f42db
+# 2838338f3d264292ac265635c4cec016
+msgid "No"
+msgstr ""
+
+#: ../../choosing_deployment_architecture.rst:197
+#: ../../choosing_deployment_architecture.rst:199
+#: ../../choosing_deployment_architecture.rst:200
+#: ../../choosing_deployment_architecture.rst:202
+#: ../../choosing_deployment_architecture.rst:203
+#: ../../choosing_deployment_architecture.rst:204
+#: ../../choosing_deployment_architecture.rst:205
+#: ../../choosing_deployment_architecture.rst:206
+#: ../../choosing_deployment_architecture.rst:207
+# b2723a3c2a3d40bb8905525b93d521db
+# df278255008f48bba701f08e2746a45b
+# 41891d2dfaec4726afd7af756ccf6ae3
+# 7de26acf53854ee19c25494093e873d8
+# e5b105be128f4a0f9b5a4b0ea089b340
+# c86cc373ee974129bcbc17d0c34fd3a9
+# 29d8fb39d33d44089307d76a24192b93
+# f2adc402745f4312b27cc7579ba3549a
+# 899efc660f874882befc3436419f4150
+msgid "N/A"
+msgstr ""
+
+#: ../../choosing_deployment_architecture.rst:198
+# 46133f6d28554c339a302a0bc5a80174
+msgid "Security groups in zones that use basic networking"
+msgstr ""
+
+#: ../../choosing_deployment_architecture.rst:199
+# 067683e3c1a940c483f5c2a1156135ec
+msgid "iSCSI"
+msgstr ""
+
+#: ../../choosing_deployment_architecture.rst:200
+# cca8044dd01e463d90beaec88dd13bfd
+msgid "FibreChannel"
+msgstr ""
+
+#: ../../choosing_deployment_architecture.rst:201
+# 9b3992c401fb484aa373c97609af73d5
+msgid "Local Disk"
+msgstr ""
+
+#: ../../choosing_deployment_architecture.rst:202
+# d7598b6aa7a24f3f890494e960b14b72
+msgid "HA"
+msgstr ""
+
+#: ../../choosing_deployment_architecture.rst:202
+# 2f14e2bad82d4187b34b6ecf7b185397
+msgid "Yes (Native)"
+msgstr ""
+
+#: ../../choosing_deployment_architecture.rst:203
+# 991329dd067d4fc0b84a473c2b9738d6
+msgid "Snapshots of local disk"
+msgstr ""
+
+#: ../../choosing_deployment_architecture.rst:204
+# 82d0be0fc5014fb199a1e335495bb0e4
+msgid "Local disk as data disk"
+msgstr ""
+
+#: ../../choosing_deployment_architecture.rst:205
+# 9606914b8d0d42e4bf6a230c8b66b0a4
+msgid "Work load balancing"
+msgstr ""
+
+#: ../../choosing_deployment_architecture.rst:205
+# e51f36058e824167a36e9ae71df467fc
+msgid "DRS"
+msgstr ""
+
+#: ../../choosing_deployment_architecture.rst:206
+# 71c333daaabe476ab414b0a03b7ae88e
+msgid "Manual live migration of VMs from host to host"
+msgstr ""
+
+#: ../../choosing_deployment_architecture.rst:207
+# c47b20ce94d448a4aa6add55bd117597
+msgid "Conserve management traffic IP address by using link local network to communicate with virtual router"
+msgstr ""
+
+#: ../../choosing_deployment_architecture.rst:212
+# cb5323a6d0ef49c283024dd46d0b4ef0
+msgid "Best Practices"
+msgstr ""
+
+#: ../../choosing_deployment_architecture.rst:214
+# adc9a356d253458ca9d971565f3bf1b3
+msgid "Deploying a cloud is challenging. There are many different technology choices to make, and CloudStack is flexible enough in its configuration that there are many possible ways to combine and configure the chosen technology. This section contains suggestions and requirements about cloud deployments."
+msgstr ""
+
+#: ../../choosing_deployment_architecture.rst:220
+# c077c29e871a451085be2f9d93d6ce0b
+msgid "These should be treated as suggestions and not absolutes. However, we do encourage anyone planning to build a cloud outside of these guidelines to seek guidance and advice on the project mailing lists."
+msgstr ""
+
+#: ../../choosing_deployment_architecture.rst:225
+# c312a003df984d1e99a7daef9dff794b
+msgid "Process Best Practices"
+msgstr ""
+
+#: ../../choosing_deployment_architecture.rst:229
+# abc014ba86804cf1b60a7e800d7692d1
+msgid "A staging system that models the production environment is strongly advised. It is critical if customizations have been applied to CloudStack."
+msgstr ""
+
+#: ../../choosing_deployment_architecture.rst:235
+# 4422c6e1832a4ede9621424bc85274ad
+msgid "Allow adequate time for installation, a beta, and learning the system. Installs with basic networking can be done in hours. Installs with advanced networking usually take several days for the first attempt, with complicated installations taking longer. For a full production system, allow at least 4-8 weeks for a beta to work through all of the integration issues. You can get help from fellow users on the cloudstack-users mailing list."
+msgstr ""
+
+#: ../../choosing_deployment_architecture.rst:244
+# e404a3ea1a28429ca6f54d86384ce11e
+msgid "Setup Best Practices"
+msgstr ""
+
+#: ../../choosing_deployment_architecture.rst:248
+# 2c6d3efd9c624e11861404be6de4db3e
+msgid "Each host should be configured to accept connections only from well-known entities such as the CloudStack Management Server or your network monitoring software."
+msgstr ""
+
+#: ../../choosing_deployment_architecture.rst:254
+# ef5b0d453e974244b9f46701aae6a09a
+msgid "Use multiple clusters per pod if you need to achieve a certain switch density."
+msgstr ""
+
+#: ../../choosing_deployment_architecture.rst:259
+# bb554a90a44a4d678ac338f55d01f8ee
+msgid "Primary storage mountpoints or LUNs should not exceed 6 TB in size. It is better to have multiple smaller primary storage elements per cluster than one large one."
+msgstr ""
+
+#: ../../choosing_deployment_architecture.rst:265
+# 3a69638a02c74393987657eaef675207
+msgid "When exporting shares on primary storage, avoid data loss by restricting the range of IP addresses that can access the storage. See \"Linux NFS on Local Disks and DAS\" or \"Linux NFS on iSCSI\"."
+msgstr ""
+
+#: ../../choosing_deployment_architecture.rst:271
+# ccf0998ec590457198f2ba04de50f1fa
+msgid "NIC bonding is straightforward to implement and provides increased reliability."
+msgstr ""
+
+#: ../../choosing_deployment_architecture.rst:276
+# d5767cccb17c4f4e857a0446daa2e67b
+msgid "10G networks are generally recommended for storage access when larger servers that can support relatively more VMs are used."
+msgstr ""
+
+#: ../../choosing_deployment_architecture.rst:281
+# 34ffd751b3bb476ba1f3f2e608b93d3d
+msgid "Host capacity should generally be modeled in terms of RAM for the guests. Storage and CPU may be overprovisioned. RAM may not. RAM is usually the limiting factor in capacity designs."
+msgstr ""
+
+#: ../../choosing_deployment_architecture.rst:287
+# 6d2c0b24d26849a19a4b45b81b27574d
+msgid "(XenServer) Configure the XenServer dom0 settings to allocate more memory to dom0. This can enable XenServer to handle larger numbers of virtual machines. We recommend 2940 MB of RAM for XenServer dom0. For instructions on how to do this, see `http://support.citrix.com/article/CTX126531 <http://support.citrix.com/article/CTX126531>`_. The article refers to XenServer 5.6, but the same information applies to XenServer 6.0."
+msgstr ""
+
+#: ../../choosing_deployment_architecture.rst:296
+# d527abb1d09c439194238f9a516c50c5
+msgid "Maintenance Best Practices"
+msgstr ""
+
+#: ../../choosing_deployment_architecture.rst:300
+# e86da3bff33947e2907910514580b7bf
+msgid "Monitor host disk space. Many host failures occur because the host's root disk fills up from logs that were not rotated adequately."
+msgstr ""
+
+#: ../../choosing_deployment_architecture.rst:305
+# c53de7cac3554464bfb3b37704d3aa62
+msgid "Monitor the total number of VM instances in each cluster, and disable allocation to the cluster if the total is approaching the maximum that the hypervisor can handle. Be sure to leave a safety margin to allow for the possibility of one or more hosts failing, which would increase the VM load on the other hosts as the VMs are redeployed. Consult the documentation for your chosen hypervisor to find the maximum permitted number of VMs per host, then use CloudStack global configuration settings to set this as the default limit. Monitor the VM activity in each cluster and keep the total number of VMs below a safe level that allows for the occasional host failure. For example, if there are N hosts in the cluster, and you want to allow for one host in the cluster to be down at any given time, the total number of VM instances you can permit in the cluster is at most (N-1) \\* (per-host-limit). Once a cluster reaches this number of VMs, use the CloudStack UI to disable allocation to t
he cluster."
+msgstr ""
+
+#: ../../choosing_deployment_architecture.rst:323
+# 89ae9c94778c48a2a29f1b11ff95a571
+msgid "The lack of up-do-date hotfixes can lead to data corruption and lost VMs."
+msgstr ""
+
+#: ../../choosing_deployment_architecture.rst:325
+# 28c8fb8da4a24ab4b15726bb4efb7ead
+msgid "Be sure all the hotfixes provided by the hypervisor vendor are applied. Track the release of hypervisor patches through your hypervisor vendor’s support channel, and apply patches as soon as possible after they are released. CloudStack will not track or notify you of required hypervisor patches. It is essential that your hosts are completely up to date with the provided hypervisor patches. The hypervisor vendor is likely to refuse to support any system that is not up to date with patches."
+msgstr ""
+