[1/6] setup i18n with transifex and sphinx-intl

[se...@apache.org]

Repository: cloudstack-docs
Updated Branches:
  refs/heads/master 3a335d31d -> 7d6892fd2


http://git-wip-us.apache.org/repos/asf/cloudstack-docs/blob/7d6892fd/rtd/source/locale/pot/plugins.pot
----------------------------------------------------------------------
diff --git a/rtd/source/locale/pot/plugins.pot b/rtd/source/locale/pot/plugins.pot
new file mode 100644
index 0000000..54cbfa3
--- /dev/null
+++ b/rtd/source/locale/pot/plugins.pot
@@ -0,0 +1,783 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2014, Apache CloudStack
+# This file is distributed under the same license as the Apache CloudStack package.
+# FIRST AUTHOR <EM...@ADDRESS>, YEAR.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: Apache CloudStack 4.3\n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2014-03-31 13:49-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"
+
+#: ../../plugins.rst:2
+# 379a7814be5a45bcadcc0fd536656b4f
+msgid "Plugins"
+msgstr ""
+
+#: ../../plugins.rst:6
+# 276ba73433bd44b49f3176b4fdcaf5a9
+msgid "Storage Plugins"
+msgstr ""
+
+#: ../../plugins.rst:8
+# 358954e5ae1b4bca9b9314f8cbd00da8
+msgid "This section gives an outline of how to implement a plugin to integrate a third-party storage provider. For details and an example, you will need to read the code."
+msgstr ""
+
+#: ../../plugins.rst:12
+# bcbf1c53396a440f8f0a50ed5591f57b
+msgid "Example code is available at: `plugins/storage/volume/sample`"
+msgstr ""
+
+#: ../../plugins.rst:14
+# 7943819f1f8a49bfb21b6aedfc6864dd
+msgid "Third party storage providers can integrate with CloudStack to provide either primary storage or secondary storage. For example, CloudStack provides plugins for Amazon Simple Storage Service (S3) or OpenStack Object Storage (Swift). The S3 plugin can be used for any object storage that supports the Amazon S3 interface."
+msgstr ""
+
+#: ../../plugins.rst:20
+# e8a7044f1e9642cea286930007548cff
+msgid "Additional third party object storages that do not support the S3 interface can be integrated with CloudStack by writing plugin software that uses the object storage plugin framework. Several new interfaces are available so that storage providers can develop vendor-specific plugins based on well-defined contracts that can be seamlessly managed by CloudStack."
+msgstr ""
+
+#: ../../plugins.rst:27
+# 0a515957cb6e4b4bbe92c1331577f84f
+msgid "Artifacts such as templates, ISOs and snapshots are kept in storage which CloudStack refers to as secondary storage. To improve scalability and performance, as when a number of hosts access secondary storage concurrently, object storage can be used for secondary storage. Object storage can also provide built-in high availability capability. When using object storage, access to secondary storage data can be made available across multiple zones in a region. This is a huge benefit, as it is no longer necessary to copy templates, snapshots etc. across zones as would be needed in an environment using only zone-based NFS storage."
+msgstr ""
+
+#: ../../plugins.rst:37
+# 6648eb6e267b443f83e38ff557fa9dcd
+msgid "The user enables a storage plugin through the UI. A new dialog box choice is offered to select the storage provider. Depending on which provider is selected, additional input fields may appear so that the user can provide the additional details required by that provider, such as a user name and password for a third-party storage account."
+msgstr ""
+
+#: ../../plugins.rst:44
+# 79590964b2d94df7b8ee961a9f0e1c77
+msgid "Overview of How to Write a Storage Plugin"
+msgstr ""
+
+#: ../../plugins.rst:46
+# 81da42c9a3fd43a6ae81de0def33d980
+msgid "To add a third-party storage option to CloudStack, follow these general steps (explained in more detail later in this section):"
+msgstr ""
+
+#: ../../plugins.rst:49
+# a59f1b6a6401428b8df44ef5c815b529
+msgid "Implement the following interfaces in Java:"
+msgstr ""
+
+#: ../../plugins.rst:51
+# d4706d7bd37f4ecfb17e700d567de04b
+msgid "DataStoreDriver"
+msgstr ""
+
+#: ../../plugins.rst:53
+# 4059bcbbcc9f42aea6d8eaaff7e19d45
+msgid "DataStoreLifecycle"
+msgstr ""
+
+#: ../../plugins.rst:55
+# cd23139c1ca9496f95616a6447c7982f
+msgid "DataStoreProvider"
+msgstr ""
+
+#: ../../plugins.rst:57
+# 0b42430ad6754a7cb5d98d5ef1b9cfbb
+msgid "VMSnapshotStrategy (if you want to customize the VM snapshot functionality)"
+msgstr ""
+
+#: ../../plugins.rst:60
+# 58743ad0ef874f8a82ec02659f100b2c
+msgid "Hardcode your plugin's required additional input fields into the code for the Add Secondary Storage or Add Primary Storage dialog box."
+msgstr ""
+
+#: ../../plugins.rst:63
+# 3db5b1bcf41c43d2b41395ec10bb9f0a
+msgid "Place your .jar file in `plugins/storage/volume/` or `plugins/storage/image/`."
+msgstr ""
+
+#: ../../plugins.rst:65
+# cb55ad5ab266458ca52e817fff92e46c
+msgid "Edit `/client/tomcatconf/componentContext.xml.in`."
+msgstr ""
+
+#: ../../plugins.rst:67
+# eb20fc9877d64f35ab554e9466f4658f
+msgid "Edit `client/pom.xml`."
+msgstr ""
+
+#: ../../plugins.rst:70
+# 9688b201ec7a44d9bec3f68a3834f661
+msgid "Implementing DataStoreDriver"
+msgstr ""
+
+#: ../../plugins.rst:72
+# 6b45021dacd74b4db08570aca747baaf
+msgid "DataStoreDriver contains the code that CloudStack will use to provision the object store, when needed."
+msgstr ""
+
+#: ../../plugins.rst:75
+#: ../../plugins.rst:99
+#: ../../plugins.rst:118
+# 110e2faf453d4019acc78dc1de958e03
+# 50d2a350ffdd446ebed3501451547a93
+# 36623b0788e84ae7b8fe9cbaa8793214
+msgid "You must implement the following methods:"
+msgstr ""
+
+#: ../../plugins.rst:77
+# 978b91799e7a441483f89ee5094951c7
+msgid "getTO()"
+msgstr ""
+
+#: ../../plugins.rst:79
+# c5f4d5267f494a3d8103694ff97230cc
+msgid "getStoreTO()"
+msgstr ""
+
+#: ../../plugins.rst:81
+# ceab640d5f294e33b654eeb341a236f6
+msgid "createAsync()"
+msgstr ""
+
+#: ../../plugins.rst:83
+# d40f5f65b6c142e3982b32e617d13ee1
+msgid "deleteAsync()"
+msgstr ""
+
+#: ../../plugins.rst:85
+#: ../../plugins.rst:135
+# 1c581d60ec8f437b946609e5005d4615
+# 6ee9c079baf14294b50ac646b0b17148
+msgid "The following methods are optional:"
+msgstr ""
+
+#: ../../plugins.rst:87
+# a4ddd58fad6a4efab4f54031b45b1895
+msgid "resize()"
+msgstr ""
+
+#: ../../plugins.rst:89
+# 07a3e3904a8f4e23ab9d2719ceadc3bb
+msgid "canCopy() is optional. If you set it to true, then you must implement copyAsync()."
+msgstr ""
+
+#: ../../plugins.rst:93
+# dfa07e5db908457d8cf4ab3ea629351f
+msgid "Implementing DataStoreLifecycle"
+msgstr ""
+
+#: ../../plugins.rst:95
+# 3508baad34c349f18bee1a469dbdd2f4
+msgid "DataStoreLifecycle contains the code to manage the storage operations for ongoing use of the storage. Several operations are needed, like create, maintenance mode, delete, etc."
+msgstr ""
+
+#: ../../plugins.rst:101
+# be7eccc5cbf94427ab62c3ac621e0904
+msgid "initialize()"
+msgstr ""
+
+#: ../../plugins.rst:103
+# 05c12b7857f9409a85b667444db0bf4b
+msgid "maintain()"
+msgstr ""
+
+#: ../../plugins.rst:105
+# e2cdf5a6cbfc40df9637fbd1625d0739
+msgid "cancelMaintain()"
+msgstr ""
+
+#: ../../plugins.rst:107
+# c531bef6c8934f778fd67919afa4e0b2
+msgid "deleteDataStore()"
+msgstr ""
+
+#: ../../plugins.rst:109
+# a37c6307cd0243c795a40ca093011f09
+msgid "Implement one of the attach\\*() methods depending on what scope you want the storage to have: attachHost(), attachCluster(), or attachZone()."
+msgstr ""
+
+#: ../../plugins.rst:114
+# 8dfafd1749a144f7889ee0f225b66288
+msgid "Implementing DataStoreProvider"
+msgstr ""
+
+#: ../../plugins.rst:116
+# b7400386153243b39742ffb719dda277
+msgid "DataStoreProvider contains the main code of the data store."
+msgstr ""
+
+#: ../../plugins.rst:120
+# d46222d7926a42f19c4b4716e4afc608
+msgid "getDatastoreLifeCycle()"
+msgstr ""
+
+#: ../../plugins.rst:122
+# a69737a8b6ab40d39e67a74c899e5574
+msgid "getDataStoreDriver()"
+msgstr ""
+
+#: ../../plugins.rst:124
+# ce12672ec9844f7c8d88a9d3871e8bdd
+msgid "getTypes(). Returns one or more types of storage for which this data store provider can be used. For secondary object storage, return IMAGE, and for a Secondary Staging Store, return ImageCache."
+msgstr ""
+
+#: ../../plugins.rst:128
+# 683ccb9981724336886a1597876d99da
+msgid "configure(). First initialize the lifecycle implementation and the driver implementation, then call registerDriver() to register the new object store provider instance with CloudStack."
+msgstr ""
+
+#: ../../plugins.rst:132
+# 6eae2e2f3984408d83382a7e643ac1ea
+msgid "getName(). Returns the unique name of your provider; for example, this can be used to get the name to display in the UI."
+msgstr ""
+
+#: ../../plugins.rst:137
+# 1d479396becb4f31907471b9247b47cf
+msgid "getHostListener() is optional; it's for monitoring the status of the host."
+msgstr ""
+
+#: ../../plugins.rst:141
+# 52eaa6fa0b484432a9bd1bbc77a5c37d
+msgid "Implementing VMSnapshotStrategy"
+msgstr ""
+
+#: ../../plugins.rst:143
+# 9ad0037ad86d4a1b8d1f135cefbbc6c5
+msgid "VMSnapshotStrategy has the following methods:"
+msgstr ""
+
+#: ../../plugins.rst:145
+# 20970991ba784f3b9d54cf1cfe12f8e6
+msgid "takeVMSnapshot()"
+msgstr ""
+
+#: ../../plugins.rst:147
+# 9bff86587100420e93573c9bee23e992
+msgid "deleteVMSnapshot()"
+msgstr ""
+
+#: ../../plugins.rst:149
+# 3a52e11272284484a6e72f035dee36c8
+msgid "revertVMSnapshot()"
+msgstr ""
+
+#: ../../plugins.rst:151
+# f3306e4fc05f4c4fb6065e8be9ae7790
+msgid "canHandle(). For a given VM snapshot, tells whether this implementation of VMSnapshotStrategy can handle it."
+msgstr ""
+
+#: ../../plugins.rst:155
+# 992261ff6c7e418da8e50ffc311bdd92
+msgid "Place the .jar File in the Right Directory"
+msgstr ""
+
+#: ../../plugins.rst:157
+# 525e7141d0414c5990833d09bda59b48
+msgid "For a secondary storage plugin, place your .jar file here:"
+msgstr ""
+
+#: ../../plugins.rst:163
+# 95400fb6d085440797180cf692b4bf94
+msgid "For a primary storage plugin, place your .jar file here:"
+msgstr ""
+
+#: ../../plugins.rst:170
+# f9bace45b78d4ca1b3581f1978438637
+msgid "Edit Configuration Files"
+msgstr ""
+
+#: ../../plugins.rst:172
+# 076d6a8e32c547ef9774ce76b6956107
+msgid "First, edit the following file tell CloudStack to include your .jar file. Add a line to this file to tell the CloudStack Management Server that it now has a dependency on your code:"
+msgstr ""
+
+#: ../../plugins.rst:180
+# 41863713ce5b44af8daa29b52ea9b884
+msgid "Place some facts about your code in the following file so CloudStack can run it:"
+msgstr ""
+
+#: ../../plugins.rst:187
+# b918b6ed56d140ff8013cb47574e0e42
+msgid "In the section “Deployment configurations of various adapters,” add this:"
+msgstr ""
+
+#: ../../plugins.rst:194
+# 30190892871c43188cf466ccd65f65d7
+msgid "In the section “Storage Providers,” add this:"
+msgstr ""
+
+#: ../../plugins.rst:203
+# 2ae7b51840ee4af992fc223832fc4671
+msgid "Minimum Required Interfaces"
+msgstr ""
+
+#: ../../plugins.rst:205
+# 8b945071a1ca4028a8e4d66b660e9a37
+msgid "The classes, interfaces, and methods used by CloudStack from the Amazon Web Services (AWS) Java SDK are listed in this section. An object storage that supports the S3 interface is minimally required to support the below in order to be compatible with CloudStack."
+msgstr ""
+
+#: ../../plugins.rst:211
+# 608dc2680b3647418a090b59602e0fae
+msgid "Interface AmazonS3"
+msgstr ""
+
+#: ../../plugins.rst:213
+# aee399034a2f4543badc14a61f4c271d
+msgid "http://docs.aws.amazon.com/AWSJavaSDK/latest/javadoc/com/amazonaws/services/s3/AmazonS3.html"
+msgstr ""
+
+#: ../../plugins.rst:216
+#: ../../plugins.rst:292
+#: ../../plugins.rst:305
+# 524902fe6335491e90113db2e7dcf32c
+# e98040534c694fa79fa31e2055d1952d
+# 14a01140525943f992129262e3d80f7d
+msgid "Modifier and Type"
+msgstr ""
+
+#: ../../plugins.rst:216
+#: ../../plugins.rst:292
+#: ../../plugins.rst:305
+# 425d6aa0a9064b96a9ca0885a619c38d
+# f6a0c9e17a6243779f44932ea5a23c89
+# 9a049f576a8e4962950b98430348d2a4
+msgid "Method and Description"
+msgstr ""
+
+#: ../../plugins.rst:219
+# dab6c8ccc228474bbdee27d4828d4f54
+msgid "Bucket"
+msgstr ""
+
+#: ../../plugins.rst:219
+# b5245e58b4104653874763bf3ebc456b
+msgid "createBucket(String bucketName)"
+msgstr ""
+
+#: ../../plugins.rst:221
+# 098525d2951148a3ab0b98ccc0daa468
+msgid "Creates a new Amazon S3 bucket with the specified name in the default (US) region, Region.US\\_Standard."
+msgstr ""
+
+#: ../../plugins.rst:224
+#: ../../plugins.rst:246
+#: ../../plugins.rst:275
+#: ../../plugins.rst:279
+# 10e1e53e84814a759d18a529af6afb21
+# 19df007e41794cdcb5068190dc725b50
+# 9b936bfde7324c11bc53237bee0ab743
+# f9e2310af56643ea89a85e7a49179a42
+msgid "void"
+msgstr ""
+
+#: ../../plugins.rst:224
+# d0edd5f0784c4d0d80b649435413969c
+msgid "deleteObject(String bucketName, String key)"
+msgstr ""
+
+#: ../../plugins.rst:226
+# b000a048de2c4b73a38deb0f3453329e
+msgid "Deletes the specified object in the specified bucket."
+msgstr ""
+
+#: ../../plugins.rst:228
+# 93db5db5c5d04b14996eee4cced36b84
+msgid "ObjectMetadata"
+msgstr ""
+
+#: ../../plugins.rst:228
+# 6c36346fa1884122b6103c28b5d4bdd7
+msgid "getObject(GetObjectRequest getObjectRequest, File destinationFile)"
+msgstr ""
+
+#: ../../plugins.rst:231
+# 733bb2a121894a158b4dbed604144383
+msgid "Gets the object metadata for the object stored in Amazon S3 under the specified bucket and key, and saves the object contents to the specified file."
+msgstr ""
+
+#: ../../plugins.rst:235
+# 69058f54f58342d094836ad752e4d4e7
+msgid "S3Object"
+msgstr ""
+
+#: ../../plugins.rst:235
+# 8e4699041a0a403594cff314173bad13
+msgid "getObject(String bucketName, String key)"
+msgstr ""
+
+#: ../../plugins.rst:237
+# 565e5ccbf07643d8bdb2e31697118021
+msgid "Gets the object stored in Amazon S3 under the specified bucket and key."
+msgstr ""
+
+#: ../../plugins.rst:240
+# e434609fbde942f7b2667a2bd2b74526
+msgid "URL"
+msgstr ""
+
+#: ../../plugins.rst:240
+# 0049113021404c0398d28d0090fc4e86
+msgid "generatePresignedUrl(String bucketName, String key, Date expiration, HttpMethod method)"
+msgstr ""
+
+#: ../../plugins.rst:243
+# 4a6a23c7ae664c61a5d54eab6c49bddd
+msgid "Returns a pre-signed URL for accessing an Amazon S3 resource."
+msgstr ""
+
+#: ../../plugins.rst:246
+# 904cfc6f8c244f8fbfc859e381069663
+msgid "deleteBucket(String bucketName)"
+msgstr ""
+
+#: ../../plugins.rst:248
+# e1dac24bb0e14b4697219c79b113fd7f
+msgid "Deletes the specified bucket."
+msgstr ""
+
+#: ../../plugins.rst:250
+# 8cdb948275894bdb97c1b8b5f6e249ed
+msgid "List<Bucket>"
+msgstr ""
+
+#: ../../plugins.rst:250
+# 4948cb9aa0fe47b5a0b4133c51aac5ae
+msgid "listBuckets()"
+msgstr ""
+
+#: ../../plugins.rst:252
+# a7f7c254dfc743e6986d6f87157e8ca1
+msgid "Returns a list of all Amazon S3 buckets that the authenticated sender of the request owns."
+msgstr ""
+
+#: ../../plugins.rst:255
+# 3e40fd85e1734299b80d1a20543aa634
+msgid "ObjectListing"
+msgstr ""
+
+#: ../../plugins.rst:255
+# bb216e1e97f64c06b56d8b5d63f55e6f
+msgid "listObjects(String bucketName, String prefix)"
+msgstr ""
+
+#: ../../plugins.rst:257
+# 410a7878aa1a423a8924f0639fd9d503
+msgid "Returns a list of summary information about the objects in the specified bucket."
+msgstr ""
+
+#: ../../plugins.rst:260
+#: ../../plugins.rst:264
+#: ../../plugins.rst:269
+# c9d4c91129ea44d3b04bc4fec6625e45
+# bdebb85f1c164924b617faf009556842
+# 07c5d99ac05a4fa288989e3abc26136a
+msgid "PutObjectResult"
+msgstr ""
+
+#: ../../plugins.rst:260
+# a026c1f32bfb4bb5880c29ae0a65e253
+msgid "putObject(PutObjectRequest putObjectRequest)"
+msgstr ""
+
+#: ../../plugins.rst:262
+# 4f55cf31f4d241e1822a673575690fd8
+msgid "Uploads a new object to the specified Amazon S3 bucket."
+msgstr ""
+
+#: ../../plugins.rst:264
+# 3bc33b26a775484088543c50ccd242b9
+msgid "putObject(String bucketName, String key, File file)"
+msgstr ""
+
+#: ../../plugins.rst:266
+# 7da2800a6855410ba7aba90d4eb247f9
+msgid "Uploads the specified file to Amazon S3 under the specified bucket and key name."
+msgstr ""
+
+#: ../../plugins.rst:269
+# 84b1447f696947f188e49d20266ab31a
+msgid "putObject(String bucketName, String key, InputStream input, ObjectMetadata metadata)"
+msgstr ""
+
+#: ../../plugins.rst:272
+# ffd50b9c64944d7c94b59db13f429502
+msgid "Uploads the specified input stream and object metadata to Amazon S3 under the specified bucket and key name."
+msgstr ""
+
+#: ../../plugins.rst:275
+# 6ff9f7752d544dce87370cff755b5c04
+msgid "setEndpoint(String endpoint)"
+msgstr ""
+
+#: ../../plugins.rst:277
+# bb223a72df024071bd3fcf9a104ea867
+msgid "Overrides the default endpoint for this client."
+msgstr ""
+
+#: ../../plugins.rst:279
+# a1c7af6f2ced47df89b4f06a106004ea
+msgid "setObjectAcl(String bucketName, String key, CannedAccessControlList acl)"
+msgstr ""
+
+#: ../../plugins.rst:282
+# fc1eb83daba44fb8b3d7c874b1b78eb4
+msgid "Sets the CannedAccessControlList for the specified object in Amazon S3 using one of the pre-configured CannedAccessControlLists."
+msgstr ""
+
+#: ../../plugins.rst:287
+# 0ca9dc98fa69442da459049fa130bb3e
+msgid "*Class TransferManager*"
+msgstr ""
+
+#: ../../plugins.rst:289
+# af0a0cd7fe054fa0b429690eb93d7f08
+msgid "http://docs.aws.amazon.com/AWSJavaSDK/latest/javadoc/com/amazonaws/services/s3/transfer/TransferManager.html"
+msgstr ""
+
+#: ../../plugins.rst:295
+#: ../../plugins.rst:308
+# 3bf5fd4667e14704827091487cba6732
+# 063f2d2856ac430f82e49cb6a131a104
+msgid "Upload"
+msgstr ""
+
+#: ../../plugins.rst:295
+#: ../../plugins.rst:308
+# 85985bdb07bb4407ac643217da6cc939
+# bcb6b7381776465fbad331f3a2f1fa72
+msgid "upload(PutObjectRequest putObjectRequest)"
+msgstr ""
+
+#: ../../plugins.rst:297
+#: ../../plugins.rst:310
+# bae421e1a5db4ee7a2dab5d554ec7198
+# aa005a5c26e74b76a91b4f14cefed7b1
+msgid "Schedules a new transfer to upload data to Amazon S3."
+msgstr ""
+
+#: ../../plugins.rst:300
+# 62992df00ab34f92971b3885d85b3bfc
+msgid "*Class PutObjectRequest*"
+msgstr ""
+
+#: ../../plugins.rst:302
+# e6c803af72274ebc9580b6a7f60bdb67
+msgid "http://docs.aws.amazon.com/AWSJavaSDK/latest/javadoc/com/amazonaws/services/s3/model/PutObjectRequest.html"
+msgstr ""
+
+#: ../../plugins.rst:315
+# 047cb9e48a3d481c934d16c02bd9a87d
+msgid "Third Party UI Plugins"
+msgstr ""
+
+#: ../../plugins.rst:317
+# be7d0e07285f4351bda1ceb9a1fb337b
+msgid "Using the new third-party plugin framework, you can write and install extensions to CloudStack. The installed and enabled plugins will appear in the UI alongside the other features. The code for the plugin is simply placed in a special directory within CloudStack’s installed code at any time after CloudStack installation. The new plugin appears only when it is enabled by the cloud administrator."
+msgstr ""
+
+#: ../../plugins.rst:328
+# 21c50cf0d5564016b44442790fe84fb1
+msgid "The left navigation bar of the CloudStack UI has a new Plugins button to help you work with UI plugins."
+msgstr ""
+
+#: ../../plugins.rst:332
+# 3181ee393ee54ca0bec634ac6c3ff3ff
+msgid "How to Write a Plugin: Overview"
+msgstr ""
+
+#: ../../plugins.rst:334
+# 7e214f0cab7b4e82bc7b17125b4d573d
+msgid "The basic procedure for writing a plugin is:"
+msgstr ""
+
+#: ../../plugins.rst:336
+# 08098d9c051a422f9f119e12fb801b90
+msgid "Write the code and create the other files needed. You will need the plugin code itself (in Javascript), a thumbnail image, the plugin listing, and a CSS file."
+msgstr ""
+
+#: ../../plugins.rst:344
+# 23807d67ae0347b3bf61aac8b62dab08
+msgid "All UI plugins have the following set of files:"
+msgstr ""
+
+#: ../../plugins.rst:359
+# 26387214ce7d4db38de919e4af305edc
+msgid "The same files must also be present at `/tomcat/webapps/client/plugins`."
+msgstr ""
+
+#: ../../plugins.rst:362
+# 88678459528c45bcb71214b6c06cbe00
+msgid "The CloudStack administrator adds the folder containing your plugin code under the CloudStack PLUGINS folder."
+msgstr ""
+
+#: ../../plugins.rst:369
+# b7a4f78ddc254478acac9a6d4896db7f
+msgid "The administrator also adds the name of your plugin to the plugin.js file in the PLUGINS folder."
+msgstr ""
+
+#: ../../plugins.rst:376
+# b4a1e6dcbbe943b7b02eff49df570e25
+msgid "The next time the user refreshes the UI in the browser, your plugin will appear in the left navigation bar."
+msgstr ""
+
+#: ../../plugins.rst:384
+# ad4d6a6816c34431bad231e9fdf8b2c4
+msgid "How to Write a Plugin: Implementation Details"
+msgstr ""
+
+#: ../../plugins.rst:386
+# 32860106c46f407caa5037981b45fd0a
+msgid "This section requires an understanding of JavaScript and the CloudStack API. You don't need knowledge of specific frameworks for this tutorial (jQuery, etc.), since the CloudStack UI handles the front-end rendering for you."
+msgstr ""
+
+#: ../../plugins.rst:391
+# d43ce7e869b44abb8aa8ced854031f33
+msgid "There is much more to the CloudStack UI framework than can be described here. The UI is very flexible to handle many use cases, so there are countless options and variations. The best reference right now is to read the existing code for the main UI, which is in the /ui folder. Plugins are written in a very similar way to the main UI."
+msgstr ""
+
+#: ../../plugins.rst:397
+# c983b0a3b2e34f47891a7f3e21d300aa
+msgid "**Create the directory to hold your plugin.**"
+msgstr ""
+
+#: ../../plugins.rst:399
+# 7fcc90ae1483437c8452ecd3a63cb12e
+msgid "All plugins are composed of set of required files in the directory /ui/plugins/pluginID, where pluginID is a short name for your plugin. It's recommended that you prefix your folder name (for example, bfMyPlugin) to avoid naming conflicts with other people's plugins."
+msgstr ""
+
+#: ../../plugins.rst:405
+# cea645979e1e42dfa9fb8a4e6c835b14
+msgid "In this example, the plugin is named csMyFirstPlugin."
+msgstr ""
+
+#: ../../plugins.rst:418
+# dac80f13146d46d69f6024199420a5f1
+msgid "**Change to your new plugin directory.**"
+msgstr ""
+
+#: ../../plugins.rst:425
+# 4649d30c029947efb26e9689fe4d0a42
+msgid "**Set up the listing.**"
+msgstr ""
+
+#: ../../plugins.rst:427
+# da3530d14f3141bf8fd825e1d590183a
+msgid "Add the file `config.js`, using your favorite editor."
+msgstr ""
+
+#: ../../plugins.rst:433
+# 7a6b02d1946d4f2293b3fec3d21d8545
+msgid "Add the following content to config.js. This information will be displayed on the plugin listing page in the UI:"
+msgstr ""
+
+#: ../../plugins.rst:449
+# e5bb9ce4c369479cbe7cc590e7865105
+msgid "**Add a new main section.**"
+msgstr ""
+
+#: ../../plugins.rst:451
+# c6a54f8b6b2542779303438bf225ead2
+msgid "Add the file csMyFirstPlugin.js, using your favorite editor."
+msgstr ""
+
+#: ../../plugins.rst:457
+# e9a74896a2564517ab0b1cad702af069
+msgid "Add the following content to csMyFirstPlugin.js:"
+msgstr ""
+
+#: ../../plugins.rst:477
+# 6b508943154f4a91ad9212145454b729
+msgid "**Register the plugin.**"
+msgstr ""
+
+#: ../../plugins.rst:479
+# 99232d63e1574ee0a219e4f47db26c12
+msgid "You now have the minimal content needed to run the plugin, so you can activate the plugin in the UI by adding it to plugins.js. First, edit the file:"
+msgstr ""
+
+#: ../../plugins.rst:489
+# aecc1460eb7a4f39bfc2974ccbd9c8df
+msgid "Now add the following to plugins.js:"
+msgstr ""
+
+#: ../../plugins.rst:500
+# dda46490dded4befab18cc890e4a8685
+msgid "**Check the plugin in the UI.**"
+msgstr ""
+
+#: ../../plugins.rst:502
+# 64676cd9d1b945ccbb61f2660ad70c96
+msgid "First, copy all the plugin code that you have created so far to `/tomcat/webapps/client/plugins`. Then refresh the browser and click Plugins in the side navigation bar. You should see your new plugin."
+msgstr ""
+
+#: ../../plugins.rst:506
+# 3b028f17d2f94b28966e30fe979808a7
+msgid "**Make the plugin do something.**"
+msgstr ""
+
+#: ../../plugins.rst:508
+# 6c65b20c7e6f487ca68539eab0b480d3
+msgid "Right now, you just have placeholder content in the new plugin. It's time to add real code. In this example, you will write a basic list view, which renders data from an API call. You will list all virtual machines owned by the logged-in user. To do this, replace the 'show' function in the plugin code with a 'listView' block, containing the required syntax for a list view. To get the data, use the listVirtualMachines API call. Without any parameters, it will return VMs only for your active user. Use the provided 'apiCall' helper method to handle the server call. Of course, you are free to use any other method for making the AJAX call (for example, jQuery's $.ajax method)."
+msgstr ""
+
+#: ../../plugins.rst:520
+# 813e82c6e71c4a11b86c8fcb1997906b
+msgid "First, open your plugin's JavaScript source file in your favorite editor:"
+msgstr ""
+
+#: ../../plugins.rst:529
+# 2d33a542619b4d55a0e9f87a9516a1dd
+msgid "Add the following code in csMyFirstPlugin.js:"
+msgstr ""
+
+#: ../../plugins.rst:573
+# 436498903a8348ca82d0c2b7e7c474bd
+msgid "**Test the plugin.**"
+msgstr ""
+
+#: ../../plugins.rst:575
+# fc6df374ec774dcca802ea34ff7af4c1
+msgid "First, copy all the plugin code that you have created so far to `/tomcat/webapps/client/plugins`. Then refresh the browser. You can see that your placeholder content was replaced with a list table, containing 4 columns of virtual machine data."
+msgstr ""
+
+#: ../../plugins.rst:580
+# ac308906d1774a4181bf17b00da818ea
+msgid "**Add an action button.**"
+msgstr ""
+
+#: ../../plugins.rst:582
+# 83bd0fe3cefa45a393d1a3ff21a4ce34
+msgid "Let's add an action button to the list view, which will reboot the VM. To do this, add an actions block under listView. After specifying the correct format, the actions will appear automatically to the right of each row of data."
+msgstr ""
+
+#: ../../plugins.rst:592
+# 7d22cbd6ab2c4a4da120584e0b7e9dfb
+msgid "Now add the following new code in csMyFirstPlugin.js. (The dots ... show where we have omitted some existing code for the sake of space. Don't actually cut and paste that part):"
+msgstr ""
+
+#: ../../plugins.rst:677
+# 5acc3c90549c46adaff6a95a22b18e8d
+msgid "**Add the thumbnail icon.**"
+msgstr ""
+
+#: ../../plugins.rst:679
+# 645ff826822448548982c45e8aa9e189
+msgid "Create an icon file; it should be square, about 50x50 pixels, and named `icon.png`. Copy it into the same directory with your plugin code: `cloudstack/ui/plugins/csMyFirstPlugin/icon.png`."
+msgstr ""
+
+#: ../../plugins.rst:683
+# dc9c9e24edb440f6a5daefbe14510efe
+msgid "**Add the stylesheet.**"
+msgstr ""
+
+#: ../../plugins.rst:685
+# 176437827f1047cbbfb1eb8b39f7f054
+msgid "Create a CSS file, with the same name as your `.js` file. Copy it into the same directory with your plugin code: `cloudstack/ui/plugins/csMyFirstPlugin/csMyFirstPlugin.css`."
+msgstr ""
+

[5/6] setup i18n with transifex and sphinx-intl

[se...@apache.org]

http://git-wip-us.apache.org/repos/asf/cloudstack-docs/blob/7d6892fd/rtd/source/locale/pot/concepts.pot
----------------------------------------------------------------------
diff --git a/rtd/source/locale/pot/concepts.pot b/rtd/source/locale/pot/concepts.pot
new file mode 100644
index 0000000..de31e09
--- /dev/null
+++ b/rtd/source/locale/pot/concepts.pot
@@ -0,0 +1,1181 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2014, Apache CloudStack
+# This file is distributed under the same license as the Apache CloudStack package.
+# FIRST AUTHOR <EM...@ADDRESS>, YEAR.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: Apache CloudStack 4.3\n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2014-03-31 13:49-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"
+
+#: ../../concepts.rst:17
+# ff38df278b6b427bbcc0ae8629300425
+msgid "Concepts and Terminology"
+msgstr ""
+
+#: ../../concepts.rst:20
+# 987b7e9834864335a292b23b7606342e
+msgid "What is Apache CloudStack?"
+msgstr ""
+
+#: ../../concepts.rst:22
+# 6a80177e5b404ca29f3615856b3d4a04
+msgid "Apache CloudStack is an open source Infrastructure-as-a-Service platform that manages and orchestrates pools of storage, network, and computer resources to build a public or private IaaS compute cloud."
+msgstr ""
+
+#: ../../concepts.rst:26
+# cd99442cc2de4607a6e68ee786158ed2
+msgid "With CloudStack you can:"
+msgstr ""
+
+#: ../../concepts.rst:28
+# 5f469cd298a84339b85ef95dc9ecd9f0
+msgid "Set up an on-demand elastic cloud computing service."
+msgstr ""
+
+#: ../../concepts.rst:29
+# f049916f533a4760aab64b754de21b0c
+msgid "Allow end-users to provision resources"
+msgstr ""
+
+#: ../../concepts.rst:32
+# e5df4fdaa57241ba861ec065ad290a8a
+msgid "What can Apache CloudStack do?"
+msgstr ""
+
+#: ../../concepts.rst:35
+# b32ee3c0a8b04a219624f36f45a80294
+msgid "Multiple Hypervisor Support"
+msgstr ""
+
+#: ../../concepts.rst:37
+# b2e92c0efc86485ea0a439a293873fc4
+msgid "CloudStack works with a variety of hypervisors and hypervisor-like technologies. A single cloud can contain multiple hypervisor implementations. As of the current release CloudStack supports:"
+msgstr ""
+
+#: ../../concepts.rst:41
+# 9a8cf08e323f44ca8d021cfeab657895
+msgid "vSphere (via vCenter)"
+msgstr ""
+
+#: ../../concepts.rst:42
+# 3d49790c67b943a69aa298d7269a1182
+msgid "KVM"
+msgstr ""
+
+#: ../../concepts.rst:43
+# 181151d4c9b74cf59ab1e9107275c932
+msgid "Xenserver"
+msgstr ""
+
+#: ../../concepts.rst:44
+# b556e16fe3ae461db6af3d65b7a1f610
+msgid "LXC"
+msgstr ""
+
+#: ../../concepts.rst:45
+# 79e7d36bd64245359e12a587e6274d52
+msgid "BareMetal (via IPMI)"
+msgstr ""
+
+#: ../../concepts.rst:48
+# 3182482cabe247af9482c3762fef3017
+msgid "Massively Scalable Infrastructure Management"
+msgstr ""
+
+#: ../../concepts.rst:50
+# 589db3182dac49e398ea50a422f61063
+msgid "CloudStack can manage tens of thousands of physical servers installed in geographically distributed datacenters. The management server scales near-linearly eliminating the need for cluster-level management servers. Maintenance or other outages of the management server can occur without affecting the virtual machines running in the cloud."
+msgstr ""
+
+#: ../../concepts.rst:56
+# f36ad8bee3e44cc2a4452cc4d88c412d
+msgid "Automatic Cloud Configuration Management"
+msgstr ""
+
+#: ../../concepts.rst:58
+# 954df973e0c04df59010d279b937d870
+msgid "CloudStack automatically configures the network and storage settings for each virtual machine deployment. Internally, a pool of virtual appliances support the operation of configuration of the cloud itself. These appliances offer services such as firewalling, routing, DHCP, VPN, console proxy, storage acces, and storage replication. The extensive use of horizontally scalable virtual machines simplifies the installation and ongoing operation of a cloud."
+msgstr ""
+
+#: ../../concepts.rst:65
+# 9b74733aa28741a7b6964e1807a72a8d
+msgid "Graphical User Interface"
+msgstr ""
+
+#: ../../concepts.rst:67
+# b55d7ad93d7f43c0a0654409b017e085
+msgid "CloudStack offers an administrators web interface used for provisioning and managing the cloud, as well as an end-user's Web interface, used for running VMs and managing VM templates. The UI can be customized to reflect the desired service provider or enterprise look and feel."
+msgstr ""
+
+#: ../../concepts.rst:72
+# 13e4ba5fb045431c96bd6a6bfb9b0c47
+msgid "API"
+msgstr ""
+
+#: ../../concepts.rst:74
+# 4cca4c0057904d119293daf854c492f9
+msgid "CloudStack provides a REST-like API for the operation, management and use of the cloud."
+msgstr ""
+
+#: ../../concepts.rst:77
+# 907642e40be7483abe15bd11b1d0d2bd
+msgid "AWS EC2 API Support"
+msgstr ""
+
+#: ../../concepts.rst:79
+# b4859925ffba4cb7bcb78e512b2e12f2
+msgid "CloudStack provides an EC2 API translation layer to permit the common EC2 tools to be used in the use of a CloudStack cloud."
+msgstr ""
+
+#: ../../concepts.rst:83
+# 9ca0dfd02bab44a5b2876118360bdec5
+msgid "High Availability"
+msgstr ""
+
+#: ../../concepts.rst:85
+# abc3111162074f78a5f125d52fbd39ed
+msgid "CloudStack has a number of features to increase the availability of the system. The Management Server itself may be deployed in a multi-node installation where the servers are load balanced. MySQL may be configured to use replication to provide for failover in the event of database loss. For the hosts, CloudStack supports NIC bonding and the use of separate networks for storage as well as iSCSI Multipath."
+msgstr ""
+
+#: ../../concepts.rst:91
+# 65f38b6a98244d4792c02eeccaa2d263
+msgid "Deployment Architecture Overview"
+msgstr ""
+
+#: ../../concepts.rst:93
+# f7691551cecf4795845273b7644abc9c
+msgid "Generally speaking, most CloudStack deployments consist of the management server and the resources to be managed. During deployment you inform the management server of the resources to be managed, such as IP address blocks, storage devices, hypervisors, and VLANs."
+msgstr ""
+
+#: ../../concepts.rst:97
+# 387390681232476cbc3cb6d9a688e686
+msgid "The minimum installation consists of one machine running the CloudStack Management Server and another machine to act as the cloud infrastructure (in this case, a very simple infrastructure consisting of one host running hypervisor software). In its smallest deployment, a single machine can act as both the Management Server and the hypervisor host (using the KVM hypervisor)."
+msgstr ""
+
+#: ../../concepts.rst:104
+# 10ca735f9c5c46fca39647ac1347679d
+msgid "A more full-featured installation consists of a highly-available multi-node Management Server installation and up to tens of thousands of hosts using any of severa  networking technologies."
+msgstr ""
+
+#: ../../concepts.rst:108
+# b8652ea0066c4053b12682ffc7f30bef
+msgid "Management Server Overview"
+msgstr ""
+
+#: ../../concepts.rst:110
+# 240ebb34afe94a58a48015d44079f040
+msgid "The management server orchestrates and allocates the resources in your cloud deployment."
+msgstr ""
+
+#: ../../concepts.rst:112
+# 2f94d5a92bab47fdb3859bebfb9afbdc
+msgid "The management server typically runs on a dedicated machine or as a virtual machine.  It controls allocation of virtual machines to hosts and assigns storage and IP addresses to the virtual machine instances. The Management Server runs in an Apache Tomcat container and requires a MySQL database for persistence."
+msgstr ""
+
+#: ../../concepts.rst:116
+# 8d0f35882eb24bc5a9c08c78e5602f5c
+msgid "The management server:"
+msgstr ""
+
+#: ../../concepts.rst:118
+# 4652f2e494364fbcb4839028180aba00
+msgid "Provides the web interface for both the adminstrator and end user."
+msgstr ""
+
+#: ../../concepts.rst:119
+# 74adcdb7447943d1b1104f8eb37ea363
+msgid "Provides the API interfaces for both the CloudStack API as well as the EC2 interface."
+msgstr ""
+
+#: ../../concepts.rst:120
+# 6d0efeb2362f4c7ca1aada6c7440bfe0
+msgid "Manages the assignment of guest VMs to a specific compute resource"
+msgstr ""
+
+#: ../../concepts.rst:121
+# b03e3bd8fdf548c9944fc3cbe1bb9cf6
+msgid "Manages the assignment of public and private IP addresses."
+msgstr ""
+
+#: ../../concepts.rst:122
+# 6c8133776eff4190a0c969b1055aa3f9
+msgid "Allocates storage during the VM instantiation process."
+msgstr ""
+
+#: ../../concepts.rst:123
+# 11de99b9ee284066b17ec2fde6453b3d
+msgid "Manages snapshots, disk images (templates), and ISO images."
+msgstr ""
+
+#: ../../concepts.rst:124
+# 108fdcfb117d44c9b11484184f31c574
+msgid "Provides a single point of configuration for your cloud."
+msgstr ""
+
+#: ../../concepts.rst:127
+# 300f4224ac2c4a568eca39a7a357259c
+msgid "Cloud Infrastructure Overview"
+msgstr ""
+
+#: ../../concepts.rst:129
+# b091b998016d49d0ace3cdc25e5b6162
+msgid "Resources within the cloud are managed as follows:"
+msgstr ""
+
+#: ../../concepts.rst:131
+# 335c3f2f7ec1419e9cd654c116d3eb4d
+msgid "Regions: A collection of one or more geographically proximate zones managed by one or more management servers."
+msgstr ""
+
+#: ../../concepts.rst:132
+# 7a077b2a461042058ee95b2d8841bd4b
+msgid "Zones: Typically, a zone is equivalent to a single datacenter. A zone consists of one or more pods and secondary storage."
+msgstr ""
+
+#: ../../concepts.rst:133
+# 32477360a735403d9ca2bc7e91cd0a54
+msgid "Pods: A pod is usually a rack, or row of racks that includes a layer-2 switch and one or more clusters."
+msgstr ""
+
+#: ../../concepts.rst:134
+# d33af50f42ee45deb987f9d2ade53d3b
+msgid "Clusters: A cluster consists of one or more homogenous hosts and primary storage."
+msgstr ""
+
+#: ../../concepts.rst:135
+# 7e093aff5e3e4a00b8f88936620ba58f
+msgid "Host: A single compute node within a cluster; often a hypervisor."
+msgstr ""
+
+#: ../../concepts.rst:136
+# 2bf7c321a3654f468a29cb08b28a73ac
+msgid "Primary Storage: A storage resource typically provided to a single cluster for the actual running of instance disk images. (Zone-wide primary storage is an option, though not typically used.)"
+msgstr ""
+
+#: ../../concepts.rst:137
+# b06340fcd44f47b4a40c4938b7341f94
+msgid "Secondary Storage: A zone-wide resource which stores disk templates, ISO images, and snapshots."
+msgstr ""
+
+#: ../../concepts.rst:140
+# e9cf76fee1ec498689b0ff20dc126e6e
+msgid "Networking Overview"
+msgstr ""
+
+#: ../../concepts.rst:142
+# c467409211f94b9687be3a2b1bfad489
+msgid "CloudStack offers many types of networking, but they typically fall into one of two scenarios:"
+msgstr ""
+
+#: ../../concepts.rst:144
+# 0821d08ee93b4d2bb76708b03c48edbd
+msgid "Basic: Most analogous to AWS-classic style networking. Provides a single flat layer-2 network where guest isolation is provided at layer-3 by the hypervisors bridge device."
+msgstr ""
+
+#: ../../concepts.rst:145
+# f3617b6f83354f55b99b92296dde725e
+msgid "Advanced: This typically uses layer-2 isolation such as VLANs, though this category also includes SDN technologies such as Nicira NVP."
+msgstr ""
+
+#: ../../concepts.rst:148
+# 62d443310175475fb835841598392342
+msgid "Cloud Infrastructure Concepts"
+msgstr ""
+
+#: ../../concepts.rst:151
+# 59126a61842545aaa3d96c7df0083839
+msgid "Regions"
+msgstr ""
+
+#: ../../concepts.rst:153
+#: ../../concepts.rst:402
+# 8e46c2fc89f347aaa6f615b273af1310
+# 4ad01c974c564a24b124ceb41761b136
+msgid "To increase reliability of the cloud, you can optionally group resources into multiple geographic regions. A region is the largest available organizational unit within a CloudStack deployment. A region is made up of several availability zones, where each zone is roughly equivalent to a datacenter. Each region is controlled by its own cluster of Management Servers, running in one of the zones. The zones in a region are typically located in close geographical proximity. Regions are a useful technique for providing fault tolerance and disaster recovery."
+msgstr ""
+
+#: ../../concepts.rst:159
+#: ../../concepts.rst:411
+# f6701bba7648406e948b876a1ba58a27
+# 6058afa6bec24d22a3cbc7a92907bff2
+msgid "By grouping zones into regions, the cloud can achieve higher availability and scalability. User accounts can span regions, so that users can deploy VMs in multiple, widely-dispersed regions. Even if one of the regions becomes unavailable, the services are still available to the end-user through VMs deployed in another region. And by grouping communities of zones under their own nearby Management Servers, the latency of communications within the cloud is reduced compared to managing widely-dispersed zones from a single central Management Server."
+msgstr ""
+
+#: ../../concepts.rst:165
+#: ../../concepts.rst:420
+# c561a80250434a22aedb0c4c6a4cfca9
+# 9e21ac69dc3443a4941d601f7b41f710
+msgid "Usage records can also be consolidated and tracked at the region level, creating reports or invoices for each geographic region."
+msgstr ""
+
+#: ../../concepts.rst:169
+#: ../../concepts.rst:425
+# 5cea4050a14f4de3aeb38b46a59ecf7d
+# b2ff55bd20544ec8bd4e3c24e6fd70e5
+msgid "Regions are visible to the end user. When a user starts a guest VM on a particular CloudStack Management Server, the user is implicitly selecting that region for their guest. Users might also be required to copy their private templates to additional regions to enable creation of guest VMs using their templates in those regions."
+msgstr ""
+
+#: ../../concepts.rst:174
+# 627923ada10e4c1d9789a4f0e7f2ccda
+msgid "Zones"
+msgstr ""
+
+#: ../../concepts.rst:176
+#: ../../concepts.rst:434
+# befd4aa4b3dd4d3595caf74ccc51913d
+# 657a047026eb4fc5a89e6adc6a503ce5
+msgid "A zone is the second largest organizational unit within a CloudStack deployment. A zone typically corresponds to a single datacenter, although it is permissible to have multiple zones in a datacenter. The benefit of organizing infrastructure into zones is to provide physical isolation and redundancy. For example, each zone can have its own power supply and network uplink, and the zones can be widely separated geographically (though this is not required)."
+msgstr ""
+
+#: ../../concepts.rst:181
+#: ../../concepts.rst:442
+# 6ac4581b29d346ea80c2ca28ac1cc9f3
+# 34a3804509f94e56983cbab9a7da8f08
+msgid "A zone consists of:"
+msgstr ""
+
+#: ../../concepts.rst:183
+#: ../../concepts.rst:446
+# a2a93c49ced7443d83c7142de3b2a3c0
+# 77fe19c6a8914f919c7c7b4480fb997c
+msgid "One or more pods. Each pod contains one or more clusters of hosts and one or more primary storage servers."
+msgstr ""
+
+#: ../../concepts.rst:184
+#: ../../concepts.rst:451
+# 54cd3d09a9564596820af0c2f8b797bb
+# 93dac9bd873040cbada20aa49f354fcc
+msgid "A zone may contain one or more primary storage servers, which are shared by all the pods in the zone."
+msgstr ""
+
+#: ../../concepts.rst:185
+#: ../../concepts.rst:456
+# 8d1c7e07b86444689288ea82e3aa0030
+# 30a6aa1442b8422f8104af67f4b60826
+msgid "Secondary storage, which is shared by all the pods in the zone."
+msgstr ""
+
+#: ../../concepts.rst:189
+#: ../../concepts.rst:460
+# e909b5cd25384b6aa06daffc782174fb
+# de76395efb94465997ef2167d697a2d2
+msgid "Zones are visible to the end user. When a user starts a guest VM, the user must select a zone for their guest. Users might also be required to copy their private templates to additional zones to enable creation of guest VMs using their templates in those zones."
+msgstr ""
+
+#: ../../concepts.rst:193
+#: ../../concepts.rst:465
+# a9272fa6b4eb48c6ad285e9101107348
+# fa18323b0b154fbebcebfbb7bab34110
+msgid "Zones can be public or private. Public zones are visible to all users. This means that any user may create a guest in that zone. Private zones are reserved for a specific domain. Only users in that domain or its subdomains may create guests in that zone."
+msgstr ""
+
+#: ../../concepts.rst:197
+#: ../../concepts.rst:470
+# 4c4175c4e26e463d85b384047c1d8e3e
+# a0e4c6875a6c40768a31d50fc7abd630
+msgid "Hosts in the same zone are directly accessible to each other without having to go through a firewall. Hosts in different zones can access each other through statically configured VPN tunnels."
+msgstr ""
+
+#: ../../concepts.rst:200
+#: ../../concepts.rst:474
+# 95fe6ba9ef1b41e782dd2e013f9d2f50
+# b36589880a184eaf9d929db8343b3c07
+msgid "For each zone, the administrator must decide the following."
+msgstr ""
+
+#: ../../concepts.rst:202
+#: ../../concepts.rst:478
+# 42fc2b04eee74bc09c075228d211be72
+# befd465185ff45ffa60c9c045efec837
+msgid "How many pods to place in each zone."
+msgstr ""
+
+#: ../../concepts.rst:203
+#: ../../concepts.rst:482
+# 4dc60d42d89a49b4aaad76ad544427b1
+# 7c2885cf066c4472b4bf878e2b9df225
+msgid "How many clusters to place in each pod."
+msgstr ""
+
+#: ../../concepts.rst:204
+#: ../../concepts.rst:486
+# 65e4c970f3e84dd3a17cc9a4914851d8
+# 9aeacb01116544fdaffe228e91991884
+msgid "How many hosts to place in each cluster."
+msgstr ""
+
+#: ../../concepts.rst:205
+#: ../../concepts.rst:490
+# f1bc4eba9d894b9eb9cc2a80b5ddb82b
+# a25998f735d641f0a212c2a16614ef2f
+msgid "(Optional) How many primary storage servers to place in each zone and total capacity for these storage servers."
+msgstr ""
+
+#: ../../concepts.rst:206
+#: ../../concepts.rst:495
+# 4636b44eada0412e872b0aa5af561d30
+# b87141f2b24d4e11ac49523c0d11b5f1
+msgid "How many primary storage servers to place in each cluster and total capacity for these storage servers."
+msgstr ""
+
+#: ../../concepts.rst:207
+#: ../../concepts.rst:500
+# 1d0a58823e334c73bfc38780900b48f3
+# 6bd68b9edccd42059714a8901af3daac
+msgid "How much secondary storage to deploy in a zone."
+msgstr ""
+
+#: ../../concepts.rst:209
+#: ../../concepts.rst:506
+# e8eea81aa4f44f4ea7f4222b67b8c089
+# 6b6f3bde7fec42df8cb8a6dc2affde8d
+msgid "In order to support zone-wide functions for VMware, CloudStack is aware of VMware Datacenters and can map each Datacenter to a CloudStack zone. To enable features like storage live migration and zone-wide primary storage for VMware hosts, CloudStack has to make sure that a zone contains only a single VMware Datacenter. Therefore, when you are creating a new CloudStack zone, you can select a VMware Datacenter for the zone. If you are provisioning multiple VMware Datacenters, each one will be set up as a single zone in CloudStack."
+msgstr ""
+
+#: ../../concepts.rst:216
+# 173494bd553249c39dcf3a1c12004242
+msgid "Pods"
+msgstr ""
+
+#: ../../concepts.rst:218
+# 9e239f33815b400a9afc4ca6a60cd8b1
+msgid "A pod often represents a single rack or row of racks. Hosts in the same pod are in the same subnet. A pod is the second-largest organizational unit within a CloudStack deployment. Pods are contained within zones. Each zone can contain one or more pods. A pod consists of one or more clusters of hosts and one or more primary storage servers. Pods are not visible to the end user."
+msgstr ""
+
+#: ../../concepts.rst:226
+# 9d49a4c915274ae88d14c5470f3cfc23
+msgid "Clusters"
+msgstr ""
+
+#: ../../concepts.rst:228
+# f3bef6825da94521ac3bc7880437d870
+msgid "A cluster consists of one or more hosts and one or more primary storage resources."
+msgstr ""
+
+#: ../../concepts.rst:230
+# 186f42983c01472b9bdb24347e815860
+msgid "A cluster provides a way to group hosts. To be precise, a cluster is a XenServer server pool, a set of KVM servers, or a VMware cluster preconfigured in vCenter. The hosts in a cluster should all have identical hardware, run the same hypervisor, are on the same subnet, and access the same shared primary storage. Virtual machine instances (VMs) can be live-migrated from one host to another within the same cluster, without interrupting service to the user."
+msgstr ""
+
+#: ../../concepts.rst:235
+# 4ef41b7c4493491d97e7520dfbb30e0b
+msgid "The size of the cluster is limited by the underlying hypervisor, although the CloudStack recommends less in most cases; see Best Practices."
+msgstr ""
+
+#: ../../concepts.rst:237
+#: ../../concepts.rst:555
+# 4bd7939a698c4b01b082b24a8b558dee
+# dcc625b8d81c4a7ebf62c75b0b9d8bf4
+msgid "Even when local storage is used exclusively, clusters are still required organizationally, even if there is just one host per cluster."
+msgstr ""
+
+#: ../../concepts.rst:239
+#: ../../concepts.rst:558
+# 068d2e011a0a4368915669d0468b364f
+# 412c8e80c5454415bc755f5805748fbb
+msgid "When VMware is used, every VMware cluster is managed by a vCenter server. An Administrator must register the vCenter server with CloudStack. There may be multiple vCenter servers per zone. Each vCenter server may manage multiple VMware clusters."
+msgstr ""
+
+#: ../../concepts.rst:243
+# e12a2e41a6a04a0c8c2a3c68c7859819
+msgid "Hosts"
+msgstr ""
+
+#: ../../concepts.rst:245
+# 6db43fe675294bdd8fde6a9a20828633
+msgid "A host is a single physical computer. Hosts provide the computing resources that run the guest machines."
+msgstr ""
+
+#: ../../concepts.rst:247
+# 30f88a20767d405385974a2927010c8b
+msgid "The host is the smallest organizational unit within a CloudStack deployment and are not visible to an end user."
+msgstr ""
+
+#: ../../concepts.rst:251
+# de600353067c4e9498a2ac9999fc8d02
+msgid "Primary Storage"
+msgstr ""
+
+#: ../../concepts.rst:253
+# 350198ae9ce54694a6bdba01506da107
+msgid "Primary storage is associated with a cluster and/or a zone. It stores the disk volumes for all of the VMs running on hosts in that cluster. You can add multiple primary storage servers to a cluster or a zone (at least one is required at the cluster level). Primary storage is typically located close to the hosts for increased performance. CloudStack manages the allocation of guest virtual disks to particular primary storage devices."
+msgstr ""
+
+#: ../../concepts.rst:258
+# c057cc657d3c4c7a86217ff789836ed7
+msgid "Primary storage can be either static or dynamic. Static primary storage is what CloudStack has traditionally supported. In this model, the administrator must present CloudStack with a certain amount of preallocated storage (ex. a volume from a SAN) and CloudStack can place many of its volumes on this storage. In the newer, dynamic model, the administrator can present CloudStack with a storage system itself (i.e. a SAN). CloudStack, working in concert with a plug-in developed for that storage system, can dynamically create volumes on the storage system. A valuable use for this ability is Quality of Service (QoS). If a volume created in CloudStack can be backed by a dedicated volume on a SAN (i.e. a one-to-one mapping between a SAN volume and a CloudStack volume) and the SAN provides QoS functionality, then CloudStack can also orchestrate storage QoS."
+msgstr ""
+
+#: ../../concepts.rst:267
+# 8a6a29004f7a48709a1a3d41399d49ec
+msgid "CloudStack is designed to work with all standards-compliant iSCSI and NFS servers that are supported by the underlying hypervisor"
+msgstr ""
+
+#: ../../concepts.rst:269
+# e5eb6c77e9ab45499723e6a4e4c6c27b
+msgid "You may also use local disks as secondary storage, though naturally they don't support live migration."
+msgstr ""
+
+#: ../../concepts.rst:272
+# 4499a9e52aa140a19473933eba3de16a
+msgid "Secondary Storage"
+msgstr ""
+
+#: ../../concepts.rst:274
+#: ../../concepts.rst:671
+# b34204827cfa4c779a1ffced2aa92966
+# 18608ded92924bbf96719cc289392636
+msgid "Secondary storage stores the following:"
+msgstr ""
+
+#: ../../concepts.rst:276
+#: ../../concepts.rst:675
+# 7bc4f80d01b5421db9ae4aeafd947957
+# 167d579993404a03bdb768d3e2b539fd
+msgid "Templates — OS images that can be used to boot VMs and can include additional configuration information, such as installed applications"
+msgstr ""
+
+#: ../../concepts.rst:277
+#: ../../concepts.rst:680
+# 5d98b266bb7245d580a56f8482c39262
+# 0b521b2715f340b7845c94b5fb9cdfd4
+msgid "ISO images — disc images containing data or bootable media for operating systems"
+msgstr ""
+
+#: ../../concepts.rst:278
+#: ../../concepts.rst:685
+# 889bfdad47d64b1fa536a8f40327e0a3
+# 301a1b6d4f6e453d81190810735d3a31
+msgid "Disk volume snapshots — saved copies of VM data which can be used for data recovery or to create new templates"
+msgstr ""
+
+#: ../../concepts.rst:280
+# f05dcac39d704557a0f970fc82cbaf2a
+msgid "The items in secondary storage are available to all hosts in the scope of the secondary storage, which may be defined as per zone or per region. CloudStack supports both NFS and Object Storage supporting either the AWS S3 API or the Swift API as a backing store for Secondary Storage."
+msgstr ""
+
+#: ../../concepts.rst:285
+# 08cfb9856b0a491a8b80bc7aca0e3656
+msgid "Physical Networks"
+msgstr ""
+
+#: ../../concepts.rst:287
+# 4e976e231c45495abc1b5a8f3c17a35d
+msgid "One or more physical networks can be associated with each zone. The physical network typically corresponds to a physical NIC on the host. Each physical network can carry one or more types of network traffic. The choices of traffic type for each network vary depending on your network choices."
+msgstr ""
+
+#: ../../concepts.rst:291
+# 2bad69755ad4458c9fd7b719a88583f2
+msgid "A physical network is the actual network hardware and wiring in a zone. A zone can have multiple physical networks."
+msgstr ""
+
+#: ../../concepts.rst:293
+# 8dc1bebd2d62453f86443cd1b1ed64f2
+msgid "An administrator can:"
+msgstr ""
+
+#: ../../concepts.rst:294
+#: ../../concepts.rst:730
+# 673e055e17e449dcb0ab7cf4e312eb87
+# 4e613ff0b38f47518010324627f2f97b
+msgid "Add/Remove/Update physical networks in a zone"
+msgstr ""
+
+#: ../../concepts.rst:295
+#: ../../concepts.rst:734
+# 6139f902423b47d5b552ae8c19fbcb9c
+# abfd546cfd074ee59013001e4049007a
+msgid "Configure VLANs on the physical network"
+msgstr ""
+
+#: ../../concepts.rst:296
+#: ../../concepts.rst:738
+# 6965d16293b1455c96af0cf908e27b24
+# a09235b0dc774dca9a55392cc7169fe4
+msgid "Configure a name so the network can be recognized by hypervisors"
+msgstr ""
+
+#: ../../concepts.rst:297
+#: ../../concepts.rst:742
+# a0487172ebf546bbbeb1f3df2f50803a
+# c7ab9b29c64b41ba969d89046a76446c
+msgid "Configure the service providers (firewalls, load balancers, etc.) available on a physical network"
+msgstr ""
+
+#: ../../concepts.rst:298
+# b06a129c42574e568380dc64dae12288
+msgid "Configure the IP addresses available to a physical network"
+msgstr ""
+
+#: ../../concepts.rst:299
+#: ../../concepts.rst:751
+# 644023d6849e4861bab38317f62597e8
+# 203d396f0f254b709f521965921090ad
+msgid "Specify what type of traffic is carried on the physical network, as well as other properties like network speed"
+msgstr ""
+
+#: ../../concepts.rst:302
+# 716989fb6e6f4b9b9d99d9c945a6ce82
+msgid "Basic Zone Network Types"
+msgstr ""
+
+#: ../../concepts.rst:304
+#: ../../concepts.rst:757
+# 7e70c69401c3482b88aa41e69bdd57f0
+# a9a7d4c0251b4e36adfbe567da895890
+msgid "When basic networking is used, there can be only one physical network in the zone. That physical network carries the following traffic types:"
+msgstr ""
+
+#: ../../concepts.rst:306
+# 3ac12abeccbd494bad6d9245e62c5422
+msgid "Guest: When end users run VMs, they generate guest traffic. The guest VMs communicate with each other over a network that can be referred to as the guest network. Each pod in a basic zone is a broadcast domain, and therefore each pod has a different IP range for the guest network. The administrator must configure the IP range for each pod."
+msgstr ""
+
+#: ../../concepts.rst:307
+# bff3dd3f0f654c659142572359fae389
+msgid "Management: When CloudStack's internal resources communicate with each other, they generate management traffic. This includes communication between hosts, system VMs (VMs used by CloudStack to perform various tasks in the cloud), and any other component that communicates directly with the CloudStack Management Server. You must configure the IP range for the system VMs to use."
+msgstr ""
+
+#: ../../concepts.rst:308
+# a44d404aec22436cad1c2299d1bbd4a3
+msgid "Public: Public traffic is generated when VMs in the cloud access the Internet. Publicly accessible IPs must be allocated for this purpose. End users can use the CloudStack UI to acquire these IPs to implement NAT between their guest network and the public network, as described in Acquiring a New IP Address."
+msgstr ""
+
+#: ../../concepts.rst:309
+# 42a656c708254cf6a1496e932c0ff068
+msgid "Storage: While labeled \"storage\" this is specifically about secondary storage, and doesn't affect traffic for primary storage. This includes traffic such as VM templates and snapshots, which is sent between the secondary storage VM and secondary storage servers. CloudStack uses a separate Network Interface Controller (NIC) named storage NIC for storage network traffic. Use of a storage NIC that always operates on a high bandwidth network allows fast template and snapshot copying. You must configure the IP range to use for the storage network."
+msgstr ""
+
+#: ../../concepts.rst:311
+#: ../../concepts.rst:802
+# da1af1bd6d90428b849863c866cb558c
+# 191007504ed74f12a036b7b4aa80eb02
+msgid "In a basic network, configuring the physical network is fairly straightforward. In most cases, you only need to configure one guest network to carry traffic that is generated by guest VMs. If you use a NetScaler load balancer and enable its elastic IP and elastic load balancing (EIP and ELB) features, you must also configure a network to carry public traffic. CloudStack takes care of presenting the necessary network configuration steps to you in the UI when you add a new zone."
+msgstr ""
+
+#: ../../concepts.rst:317
+#: ../../concepts.rst:811
+# 52ed9564f5564301b8ca7f7a28d52230
+# 7f7851b143664a31bc5ad1359cd44999
+msgid "Basic Zone Guest IP Addresses"
+msgstr ""
+
+#: ../../concepts.rst:319
+#: ../../concepts.rst:813
+# 7cdc690d38a74425b1fa34daa7d4dc53
+# 3b96868afb964f30b8e97dc558e5d353
+msgid "When basic networking is used, CloudStack will assign IP addresses in the CIDR of the pod to the guests in that pod. The administrator must add a Direct IP range on the pod for this purpose. These IPs are in the same VLAN as the hosts."
+msgstr ""
+
+#: ../../concepts.rst:323
+# c30cdaafea804e4b9de562c8c9caa9cc
+msgid "Advanced Zone Network Types"
+msgstr ""
+
+#: ../../concepts.rst:325
+# fcc04e4ceff84117b3e53bee51437f89
+msgid "When advanced networking is used, there can be multiple physical networks in the zone. Each physical network can carry one or more traffic types, and you need to let CloudStack know which type of network traffic you want each network to carry."
+msgstr ""
+
+#: ../../concepts.rst:328
+# 5a0e6b3314644c8dbef972f02423c28d
+msgid "The traffic types in an advanced zone are:"
+msgstr ""
+
+#: ../../concepts.rst:330
+# 90065dd487b34a26b77e5cc55ed0b4f4
+msgid "**Guest**: When end users run VMs, they generate guest traffic. The guest VMs communicate with each other over a network that can be referred to as the guest network. This network can be isolated or shared. In an isolated guest network, the administrator needs to reserve VLAN ranges to provide isolation for each CloudStack account’s network (potentially a large number of VLANs). In a shared guest network, all guest VMs share a single network."
+msgstr ""
+
+#: ../../concepts.rst:331
+# d2eb0c505d0342ddb32f2ea044d23de6
+msgid "**Management**: When CloudStack’s internal resources communicate with each other, they generate management traffic. This includes communication between hosts, system VMs (VMs used by CloudStack to perform various tasks in the cloud), and any other component that communicates directly with the CloudStack Management Server. You must configure the IP range for the system VMs to use."
+msgstr ""
+
+#: ../../concepts.rst:332
+# a2a81b57809f4d1d8155613824407cfb
+msgid "**Public**: Public traffic is generated when VMs in the cloud access the Internet. Publicly accessible IPs must be allocated for this purpose. End users can use the CloudStack UI to acquire these IPs to implement NAT between their guest network and the public network, as described in “Acquiring a New IP Address” in the Administration Guide."
+msgstr ""
+
+#: ../../concepts.rst:333
+# cc48dcce460248a09e15337063a76c63
+msgid "**Storage**: While labeled \"storage\" this is specifically about secondary storage, and doesn't affect traffic for primary storage. This includes traffic such as VM templates and snapshots, which is sent between the secondary storage VM and secondary storage servers. CloudStack uses a separate Network Interface Controller (NIC) named storage NIC for storage network traffic. Use of a storage NIC that always operates on a high bandwidth network allows fast template and snapshot copying. You must configure the IP range to use for the storage network."
+msgstr ""
+
+#: ../../concepts.rst:335
+# 59b04a547a534553b2b5574c99c8946f
+msgid "These traffic types can each be on a separate physical network, or they can be combined with certain restrictions."
+msgstr ""
+
+#: ../../concepts.rst:338
+#: ../../concepts.rst:872
+# 581125884ee848b19adc4c4310344c2c
+# 6ca1da8a16104aee9f75283327a76b31
+msgid "Advanced Zone Guest IP Addresses"
+msgstr ""
+
+#: ../../concepts.rst:340
+#: ../../concepts.rst:874
+# 5fb5522293ec4ebf836f183a1c0724fb
+# 76db0a52e18245018be54f6193d9ab7d
+msgid "When advanced networking is used, the administrator can create additional networks for use by the guests. These networks can span the zone and be available to all accounts, or they can be scoped to a single account, in which case only the named account may create guests that attach to these networks. The networks are defined by a VLAN ID, IP range, and gateway. The administrator may provision thousands of these networks if desired. Additionally, the administrator can reserve a part of the IP address space for non-CloudStack VMs and servers."
+msgstr ""
+
+#: ../../concepts.rst:347
+#: ../../concepts.rst:884
+# d892c1cc5ef94dd2a238710fcc62b3f3
+# d3231b1597e54924af2efe64f2752996
+msgid "Advanced Zone Public IP Addresses"
+msgstr ""
+
+#: ../../concepts.rst:349
+# 48529282c66f4e818c596eac0b22f4dc
+msgid "In an advanced network, Public IP addresses are typically on one or more dedicated VLANs and are routed or NATed to guest VMs."
+msgstr ""
+
+#: ../../concepts.rst:352
+#: ../../concepts.rst:895
+# bef5f9b7dcf848d5a23e159598861bde
+# 21efd19a0a61497e903a5c90ac00c17a
+msgid "System Reserved IP Addresses"
+msgstr ""
+
+#: ../../concepts.rst:354
+#: ../../concepts.rst:897
+# 4e508c81014d4e29887a3293b9782831
+# 6e227bc9e49e4306a7fa72e1b0475ad0
+msgid "In each zone, you need to configure a range of reserved IP addresses for the management network. This network carries communication between the CloudStack Management Server and various system VMs, such as Secondary Storage VMs, Console Proxy VMs, and DHCP."
+msgstr ""
+
+#: ../../concepts.rst:357
+#: ../../concepts.rst:902
+# d385f28804a049149e1dc7d64f1b8b78
+# 3264c18fd3ca489c96c9bf34f7e08f47
+msgid "The reserved IP addresses must be unique across the cloud. You cannot, for example, have a host in one zone which has the same private IP address as a host in another zone."
+msgstr ""
+
+#: ../../concepts.rst:360
+#: ../../concepts.rst:906
+# 8bd3ab39146d465fb707abed820432bf
+# d78c6b7284f8455e8e2708bd1ddb8f31
+msgid "The hosts in a pod are assigned private IP addresses. These are typically RFC1918 addresses. The Console Proxy and Secondary Storage system VMs are also allocated private IP addresses in the CIDR of the pod that they are created in."
+msgstr ""
+
+#: ../../concepts.rst:363
+# ddc8e2a3b2324070a33acc6eae3de7bf
+msgid "Make sure computing servers and Management Servers use IP addresses outside of the System Reserved IP range. In example, suppose the System Reserved IP range starts at 192.168.154.2 and ends at 192.168.154.7. CloudStack can use .2 to .7 for System VMs. This leaves the rest of the pod CIDR, from .8 to .254, for the Management Server and hypervisor hosts."
+msgstr ""
+
+#: ../../concepts.rst:368
+# eca6adde7164436e95f9f0b7ca27f3d2
+msgid "In all zones"
+msgstr ""
+
+#: ../../concepts.rst:370
+#: ../../concepts.rst:920
+# 805296fd2460493e9da6efef11a237d8
+# 97254c396f974c28899a695da5a256bc
+msgid "Provide private IPs for the system in each pod and provision them in CloudStack."
+msgstr ""
+
+#: ../../concepts.rst:372
+#: ../../concepts.rst:923
+# dd17defbc77844f3ae99664b2dd14669
+# 9d974eb2e59d418e95c8cab21c4cb765
+msgid "For KVM and XenServer, the recommended number of private IPs per pod is one per host. If you expect a pod to grow, add enough private IPs now to accommodate the growth."
+msgstr ""
+
+#: ../../concepts.rst:376
+# 201c6ab211a6483299774ba062c21759
+msgid "In a zone that uses advanced networking"
+msgstr ""
+
+#: ../../concepts.rst:378
+#: ../../concepts.rst:929
+# b83e478a382d49189d28f20d21deefb3
+# 7d09c246921c4149a7e2cf0b1354861b
+msgid "For zones with advanced networking, we recommend provisioning enough private IPs for your total number of customers, plus enough for the required CloudStack System VMs. Typically, about 10 additional IPs are required for the System VMs. For more information about System VMs, see the section on working with SystemVMs in the Administrator's Guide."
+msgstr ""
+
+#: ../../concepts.rst:382
+#: ../../concepts.rst:935
+# 007bfa0acd5a48689fc6a288169b4152
+# 21bf97bde5264f9f8d6b8c7b250e8559
+msgid "When advanced networking is being used, the number of private IP addresses available in each pod varies depending on which hypervisor is running on the nodes in that pod. Citrix XenServer and KVM use link-local addresses, which in theory provide more than 65,000 private IP addresses within the address block. As the pod grows over time, this should be more than enough for any reasonable number of hosts as well as IP addresses for guest virtual routers. VMWare ESXi, by contrast uses any administrator-specified subnetting scheme, and the typical administrator provides only 255 IPs per pod. Since these are shared by physical machines, the guest virtual router, and other entities, it is possible to run out of private IPs when scaling up a pod whose nodes are running ESXi."
+msgstr ""
+
+#: ../../concepts.rst:390
+#: ../../concepts.rst:948
+# 87751541797d455d9a8895a446a4c699
+# fd6f72eb0ae04120aec4b9d55dc8e9d3
+msgid "To ensure adequate headroom to scale private IP space in an ESXi pod that uses advanced networking, use one or both of the following techniques:"
+msgstr ""
+
+#: ../../concepts.rst:392
+#: ../../concepts.rst:954
+# 27d54cfd61944602a6e4c1a6620312e2
+# 0c5aa832bb5d431c9a6bcf25d0ceb6cb
+msgid "Specify a larger CIDR block for the subnet. A subnet mask with a /20 suffix will provide more than 4,000 IP addresses."
+msgstr ""
+
+#: ../../concepts.rst:393
+# 670cb02dfb504639b0c10af5a1b05736
+msgid "Create multiple pods, each with its own subnet. In example, if you create 10 pods and each pod has 255 IPs, this will provide 2,550 IP addresses."
+msgstr ""
+
+#: ../../concepts.rst:397
+# 48f643ed242e4501b8761273a71ee960
+msgid "CloudStack Terminology"
+msgstr ""
+
+#: ../../concepts.rst:400
+# 7f83b27f3b074d4798ba28ebaa8e9dc5
+msgid "About Regions"
+msgstr ""
+
+#: ../../concepts.rst:423
+# 77489477fc9c4ac182a3e03f1cdd9a6d
+msgid "|region-overview.png: Nested structure of a region.|"
+msgstr ""
+
+#: ../../concepts.rst:432
+# 8c52014de7f74a86a087cdd0b524c3bd
+msgid "About Zones"
+msgstr ""
+
+#: ../../concepts.rst:458
+# c2a0e65f22b04f279dadce7331a885e2
+msgid "|zone-overview.png: Nested structure of a simple zone.|"
+msgstr ""
+
+#: ../../concepts.rst:502
+# 9b94cbd4c96c462caa6d4012880e39d2
+msgid "When you add a new zone using the CloudStack UI, you will be prompted to configure the zone’s physical network and add the first pod, cluster, host, primary storage, and secondary storage."
+msgstr ""
+
+#: ../../concepts.rst:517
+# dba480aeca244d718b2d6ebcafea03e9
+msgid "If you are upgrading from a previous CloudStack version, and your existing deployment contains a zone with clusters from multiple VMware Datacenters, that zone will not be forcibly migrated to the new model. It will continue to function as before. However, any new zone-wide operations, such as zone-wide primary storage and live storage migration, will not be available in that zone."
+msgstr ""
+
+#: ../../concepts.rst:520
+# 54db4ee812af4afeb4022ba56f6042c2
+msgid "About Pods"
+msgstr ""
+
+#: ../../concepts.rst:522
+# aae3ab7a910741328f9dea985ae6c141
+msgid "A pod often represents a single rack. Hosts in the same pod are in the same subnet. A pod is the third-largest organizational unit within a CloudStack deployment. Pods are contained within zones. Each zone can contain one or more pods. A pod consists of one or more clusters of hosts and one or more primary storage servers. Pods are not visible to the end user."
+msgstr ""
+
+#: ../../concepts.rst:529
+# 4c861ca60e304b1fb87ad569764097d7
+msgid "|pod-overview.png: Nested structure of a simple pod|"
+msgstr ""
+
+#: ../../concepts.rst:532
+# 096b727fd7444148a2c51998c1132116
+msgid "About Clusters"
+msgstr ""
+
+#: ../../concepts.rst:534
+# d8d6efc761534d708ee129f70a0e5cc5
+msgid "A cluster provides a way to group hosts. To be precise, a cluster is a XenServer server pool, a set of KVM servers, , or a VMware cluster preconfigured in vCenter. The hosts in a cluster all have identical hardware, run the same hypervisor, are on the same subnet, and access the same shared primary storage. Virtual machine instances (VMs) can be live-migrated from one host to another within the same cluster, without interrupting service to the user."
+msgstr ""
+
+#: ../../concepts.rst:542
+# 7351147d578e4ecda91e712f39534df2
+msgid "A cluster is the fourth-largest organizational unit within a CloudStack deployment. Clusters are contained within pods, and pods are contained within zones. Size of the cluster is limited by the underlying hypervisor, although the CloudStack recommends less in most cases; see Best Practices."
+msgstr ""
+
+#: ../../concepts.rst:548
+# f4244191ac2a41058ff5d2202e0aaa51
+msgid "A cluster consists of one or more hosts and one or more primary storage servers."
+msgstr ""
+
+#: ../../concepts.rst:551
+# 0b0cb15f7bec487eb3099ea1c494db01
+msgid "|cluster-overview.png: Structure of a simple cluster|"
+msgstr ""
+
+#: ../../concepts.rst:553
+# 3ee369925fad4ae2b64b0d10eeeae914
+msgid "CloudStack allows multiple clusters in a cloud deployment."
+msgstr ""
+
+#: ../../concepts.rst:564
+# 3a0b47da5f2b4880a1e6c5463b4138f7
+msgid "About Hosts"
+msgstr ""
+
+#: ../../concepts.rst:566
+# 205fdc6d2c01429b9ed6756a4b980ded
+msgid "A host is a single computer. Hosts provide the computing resources that run guest virtual machines. Each host has hypervisor software installed on it to manage the guest VMs. For example, a host can be a Citrix XenServer server, a Linux KVM-enabled server, an ESXi server, or a Windows Hyper-V server."
+msgstr ""
+
+#: ../../concepts.rst:572
+# 97449427b2834b5a910f749370834a3c
+msgid "The host is the smallest organizational unit within a CloudStack deployment. Hosts are contained within clusters, clusters are contained within pods, pods are contained within zones, and zones can be contained within regions."
+msgstr ""
+
+#: ../../concepts.rst:577
+# 58a7f1c53f844ff292a15d04befeb5ce
+msgid "Hosts in a CloudStack deployment:"
+msgstr ""
+
+#: ../../concepts.rst:581
+# f671a906b30a42e1a516954f4e20c606
+msgid "Provide the CPU, memory, storage, and networking resources needed to host the virtual machines"
+msgstr ""
+
+#: ../../concepts.rst:586
+# 765e1241863645eba92568a45ac677f4
+msgid "Interconnect using a high bandwidth TCP/IP network and connect to the Internet"
+msgstr ""
+
+#: ../../concepts.rst:591
+# 5820e8689f01475b9e873d5dc6179a6f
+msgid "May reside in multiple data centers across different geographic locations"
+msgstr ""
+
+#: ../../concepts.rst:596
+# 062511e0a1fa417bad68cce103d84666
+msgid "May have different capacities (different CPU speeds, different amounts of RAM, etc.), although the hosts within a cluster must all be homogeneous"
+msgstr ""
+
+#: ../../concepts.rst:600
+# 23aec79990ea417598eea7c77847a775
+msgid "Additional hosts can be added at any time to provide more capacity for guest VMs."
+msgstr ""
+
+#: ../../concepts.rst:603
+# e1adace21ae0456dbcf93531f4957248
+msgid "CloudStack automatically detects the amount of CPU and memory resources provided by the hosts."
+msgstr ""
+
+#: ../../concepts.rst:606
+# e6b130b004b7446aa1601c31a04ec880
+msgid "Hosts are not visible to the end user. An end user cannot determine which host their guest has been assigned to."
+msgstr ""
+
+#: ../../concepts.rst:609
+# 855a204e524044c0b8b0966e23500edc
+msgid "For a host to function in CloudStack, you must do the following:"
+msgstr ""
+
+#: ../../concepts.rst:613
+# 8a6eda274c124ba7a819d60409feda29
+msgid "Install hypervisor software on the host"
+msgstr ""
+
+#: ../../concepts.rst:617
+# 05c37b7642704df08b323c1676a611ef
+msgid "Assign an IP address to the host"
+msgstr ""
+
+#: ../../concepts.rst:621
+# b5a14bffa6c0494094b1437abbdffb24
+msgid "Ensure the host is connected to the CloudStack Management Server."
+msgstr ""
+
+#: ../../concepts.rst:624
+# 0461535a3ff54eb890711bd518df5a2f
+msgid "About Primary Storage"
+msgstr ""
+
+#: ../../concepts.rst:626
+# 61eabe7827a34e75a9280dc9d6ae6a01
+msgid "Primary storage is associated with a cluster or (in KVM and VMware) a zone, and it stores the disk volumes for all the VMs running on hosts."
+msgstr ""
+
+#: ../../concepts.rst:629
+# 8a0469a7335942a787a9af2154ccfd35
+msgid "You can add multiple primary storage servers to a cluster or zone. At least one is required. It is typically located close to the hosts for increased performance. CloudStack manages the allocation of guest virtual disks to particular primary storage devices."
+msgstr ""
+
+#: ../../concepts.rst:634
+# e8bd1c7d24f44522bf5c9321d36534eb
+msgid "It is useful to set up zone-wide primary storage when you want to avoid extra data copy operations. With cluster-based primary storage, data in the primary storage is directly available only to VMs within that cluster. If a VM in a different cluster needs some of the data, it must be copied from one cluster to another, using the zone's secondary storage as an intermediate step. This operation can be unnecessarily time-consuming."
+msgstr ""
+
+#: ../../concepts.rst:642
+# c7f83a84661a43f2b010ab9aef5cca67
+msgid "For Hyper-V, SMB/CIFS storage is supported. Note that Zone-wide Primary Storage is not supported in Hyper-V."
+msgstr ""
+
+#: ../../concepts.rst:645
+# b634131439874a00a2ee27850bce0321
+msgid "CloudStack is designed to work with all standards-compliant iSCSI and NFS servers that are supported by the underlying hypervisor, including, for example:"
+msgstr ""
+
+#: ../../concepts.rst:651
+# 679f58d91ca547b381015341a15876e7
+msgid "SolidFire for iSCSI"
+msgstr ""
+
+#: ../../concepts.rst:655
+# 0074b93405934cd9af05d2d7dee1eff7
+msgid "Dell EqualLogic™ for iSCSI"
+msgstr ""
+
+#: ../../concepts.rst:659
+# 7bbec1e2cd6d4562a07d26dc3729c274
+msgid "Network Appliances filers for NFS and iSCSI"
+msgstr ""
+
+#: ../../concepts.rst:663
+# 09fab1fa10654e6fb7cd7d11c6bfc186
+msgid "Scale Computing for NFS"
+msgstr ""
+
+#: ../../concepts.rst:665
+# 3538437e1d8841d68caca6d2cfc38a49
+msgid "If you intend to use only local disk for your installation, you can skip adding separate primary storage."
+msgstr ""
+
+#: ../../concepts.rst:669
+# ad3da3f468ca4f31b1ad424695d356d6
+msgid "About Secondary Storage"
+msgstr ""
+
+#: ../../concepts.rst:688
+# 75d27a88966c4c6dae20b8fa670b8993
+msgid "The items in secondary storage are available to all hosts in the scope of the secondary storage, which may be defined as per zone or per region."
+msgstr ""
+
+#: ../../concepts.rst:692
+# ed4098415be54095b396714cb7c514c3
+msgid "To make items in secondary storage available to all hosts throughout the cloud, you can add object storage in addition to the zone-based NFS Secondary Staging Store. It is not necessary to copy templates and snapshots from one zone to another, as would be required when using zone NFS alone. Everything is available everywhere."
+msgstr ""
+
+#: ../../concepts.rst:698
+# 79c26db02f0249f8b6c794319a0ea2b1
+msgid "For Hyper-V hosts, SMB/CIFS storage is supported."
+msgstr ""
+
+#: ../../concepts.rst:700
+# 913e44de9bcd4ad39ef301e44f9f4912
+msgid "CloudStack provides plugins that enable both OpenStack Object Storage (Swift, `swift.openstack.org <http://swift.openstack.org>`__) and Amazon Simple Storage Service (S3) object storage. When using one of these storage plugins, you configure Swift or S3 storage for the entire CloudStack, then set up the NFS Secondary Staging Store for each zone. The NFS storage in each zone acts as a staging area through which all templates and other secondary storage data pass before being forwarded to Swift or S3. The backing object storage acts as a cloud-wide resource, making templates and other data available to any zone in the cloud."
+msgstr ""
+
+#: ../../concepts.rst:713
+# 923b43f36d6a43779d097362df5eeecc
+msgid "Heterogeneous Secondary Storage is not supported in Regions. For example, you cannot set up multiple zones, one using NFS secondary and the other using S3 or Swift secondary."
+msgstr ""
+
+#: ../../concepts.rst:716
+# 61ac7438b69a4a86af94a1bf2fe64fe3
+msgid "About Physical Networks"
+msgstr ""
+
+#: ../../concepts.rst:718
+# 4dcdb324118640269de7380c6bee06f1
+msgid "Part of adding a zone is setting up the physical network. One or (in an advanced zone) more physical networks can be associated with each zone. The network corresponds to a NIC on the hypervisor host. Each physical network can carry one or more types of network traffic. The choices of traffic type for each network vary depending on whether you are creating a zone with basic networking or advanced networking."
+msgstr ""
+
+#: ../../concepts.rst:725
+# f7b77ed223b4433987d4702a01fb8c47
+msgid "A physical network is the actual network hardware and wiring in a zone. A zone can have multiple physical networks. An administrator can:"
+msgstr ""
+
+#: ../../concepts.rst:747
+# 24d09735b0ca4143ad8978d89842d154
+msgid "Configure the IP addresses trunked to a physical network"
+msgstr ""
+
+#: ../../concepts.rst:755
+# bd87d1fd70d34ff3958228f36bf6538e
+msgid "Basic Zone Network Traffic Types"
+msgstr ""
+
+#: ../../concepts.rst:762
+# a9dadbb1895845ecaffeb810b06b7ec8
+msgid "Guest. When end users run VMs, they generate guest traffic. The guest VMs communicate with each other over a network that can be referred to as the guest network. Each pod in a basic zone is a broadcast domain, and therefore each pod has a different IP range for the guest network. The administrator must configure the IP range for each pod."
+msgstr ""
+
+#: ../../concepts.rst:770
+# dc406b9190ce4cc48f7f4b3443ff4cda
+msgid "Management. When CloudStack's internal resources communicate with each other, they generate management traffic. This includes communication between hosts, system VMs (VMs used by CloudStack to perform various tasks in the cloud), and any other component that communicates directly with the CloudStack Management Server. You must configure the IP range for the system VMs to use."
+msgstr ""
+
+#: ../../concepts.rst:779
+# 39db7e6a26f746ceb0672acda7fd8080
+msgid "We strongly recommend the use of separate NICs for management traffic and guest traffic."
+msgstr ""
+
+#: ../../concepts.rst:784
+# 3ee341c4481d464d9ade2fe2546540d8
+msgid "Public. Public traffic is generated when VMs in the cloud access the Internet. Publicly accessible IPs must be allocated for this purpose. End users can use the CloudStack UI to acquire these IPs to implement NAT between their guest network and the public network, as described in Acquiring a New IP Address."
+msgstr ""
+
+#: ../../concepts.rst:792
+#: ../../concepts.rst:856
+# 9f0a166f4cdd4eaba88ff44521189e57
+# d61ccfa4d6b6457189863747e25fe247
+msgid "Storage. While labeled \"storage\" this is specifically about secondary storage, and doesn't affect traffic for primary storage. This includes traffic such as VM templates and snapshots, which is sent between the secondary storage VM and secondary storage servers. CloudStack uses a separate Network Interface Controller (NIC) named storage NIC for storage network traffic. Use of a storage NIC that always operates on a high bandwidth network allows fast template and snapshot copying. You must configure the IP range to use for the storage network."
+msgstr ""
+
+#: ../../concepts.rst:819
+# c58251d2d6c34f4eaef1b3e7b07bee7b
+msgid "Advanced Zone Network Traffic Types"
+msgstr ""
+
+#: ../../concepts.rst:821
+# 64b15543219244289efe314f52a850aa
+msgid "When advanced networking is used, there can be multiple physical networks in the zone. Each physical network can carry one or more traffic types, and you need to let CloudStack know which type of network traffic you want each network to carry. The traffic types in an advanced zone are:"
+msgstr ""
+
+#: ../../concepts.rst:829
+# 6d72677dcf1d4796a4ed9b8e2bfd36c7
+msgid "Guest. When end users run VMs, they generate guest traffic. The guest VMs communicate with each other over a network that can be referred to as the guest network. This network can be isolated or shared. In an isolated guest network, the administrator needs to reserve VLAN ranges to provide isolation for each CloudStack account’s network (potentially a large number of VLANs). In a shared guest network, all guest VMs share a single network."
+msgstr ""
+
+#: ../../concepts.rst:839
+# 00a3aa2f55574d10ac98903ab4705480
+msgid "Management. When CloudStack’s internal resources communicate with each other, they generate management traffic. This includes communication between hosts, system VMs (VMs used by CloudStack to perform various tasks in the cloud), and any other component that communicates directly with the CloudStack Management Server. You must configure the IP range for the system VMs to use."
+msgstr ""
+
+#: ../../concepts.rst:848
+# b04011567f254066b55ed823e80437c1
+msgid "Public. Public traffic is generated when VMs in the cloud access the Internet. Publicly accessible IPs must be allocated for this purpose. End users can use the CloudStack UI to acquire these IPs to implement NAT between their guest network and the public network, as described in “Acquiring a New IP Address” in the Administration Guide."
+msgstr ""
+
+#: ../../concepts.rst:866
+# c0e1e92bce5348458d8da10a51171774
+msgid "These traffic types can each be on a separate physical network, or they can be combined with certain restrictions. When you use the Add Zone wizard in the UI to create a new zone, you are guided into making only valid choices."
+msgstr ""
+
+#: ../../concepts.rst:886
+# db963f68933d4705bbfd94377585e0e5
+msgid "When advanced networking is used, the administrator can create additional networks for use by the guests. These networks can span the zone and be available to all accounts, or they can be scoped to a single account, in which case only the named account may create guests that attach to these networks. The networks are defined by a VLAN ID, IP range, and gateway. The administrator may provision thousands of these networks if desired."
+msgstr ""
+
+#: ../../concepts.rst:911
+# fb0ea82f51c14b77915b642a9480bc28
+msgid "Make sure computing servers and Management Servers use IP addresses outside of the System Reserved IP range. For example, suppose the System Reserved IP range starts at 192.168.154.2 and ends at 192.168.154.7. CloudStack can use .2 to .7 for System VMs. This leaves the rest of the pod CIDR, from .8 to .254, for the Management Server and hypervisor hosts."
+msgstr ""
+
+#: ../../concepts.rst:918
+# e772bcd2076945f1803767331cb65080
+msgid "**In all zones:**"
+msgstr ""
+
+#: ../../concepts.rst:927
+# 5cd0b2295fe54192bdb8dbae7d2e902a
+msgid "**In a zone that uses advanced networking:**"
+msgstr ""
+
+#: ../../concepts.rst:959
+# 6851d74b7aa544dda60f5c0e80f5a2db
+msgid "Create multiple pods, each with its own subnet. For example, if you create 10 pods and each pod has 255 IPs, this will provide 2,550 IP addresses."
+msgstr ""
+

[3/6] setup i18n with transifex and sphinx-intl

[se...@apache.org]

http://git-wip-us.apache.org/repos/asf/cloudstack-docs/blob/7d6892fd/rtd/source/locale/pot/developer_guide.pot
----------------------------------------------------------------------
diff --git a/rtd/source/locale/pot/developer_guide.pot b/rtd/source/locale/pot/developer_guide.pot
new file mode 100644
index 0000000..2e6995b
--- /dev/null
+++ b/rtd/source/locale/pot/developer_guide.pot
@@ -0,0 +1,528 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2014, Apache CloudStack
+# This file is distributed under the same license as the Apache CloudStack package.
+# FIRST AUTHOR <EM...@ADDRESS>, YEAR.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: Apache CloudStack 4.3\n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2014-03-31 13:49-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"
+
+#: ../../developer_guide.rst:2
+# bb72baa2a42c478fa65fa1c9b410f0b6
+msgid "CloudStack Installation from Source for Developers"
+msgstr ""
+
+#: ../../developer_guide.rst:4
+# d5339eb5aa3a4e4797040c45829f7a12
+msgid "This book is aimed at CloudStack developers who need to build the code. These instructions are valid on a Ubuntu 12.04 and CentOS 6.4 systems and were tested with the 4.2 release of Apache CloudStack, please adapt them if you are on a different operating system or using a newer/older version of CloudStack. This book is composed of the following sections:"
+msgstr ""
+
+#: ../../developer_guide.rst:10
+# 2513ed5b50064ad5baea6e2d6ca56667
+msgid "Installation of the prerequisites"
+msgstr ""
+
+#: ../../developer_guide.rst:11
+# b609f7feda6e484ab28214d803d9ddb4
+msgid "Compiling and installation from source"
+msgstr ""
+
+#: ../../developer_guide.rst:12
+# 04a3de1bd1d548b5a551870f1087bba4
+msgid "Using the CloudStack simulator"
+msgstr ""
+
+#: ../../developer_guide.rst:13
+# df71d1f0b01c4b44a75c4d216cd5f03f
+msgid "Installation with DevCloud the CloudStack sandbox"
+msgstr ""
+
+#: ../../developer_guide.rst:14
+# fecac2ddc3b4418588b49180b4d1e60b
+msgid "Building your own packages"
+msgstr ""
+
+#: ../../developer_guide.rst:15
+#: ../../developer_guide.rst:458
+# fc80af4f6f25482088389dc04fc822c8
+# f6c0d2e4f50d4f1a8ce2a237d8fa69e2
+msgid "The CloudStack API"
+msgstr ""
+
+#: ../../developer_guide.rst:16
+#: ../../developer_guide.rst:596
+# 2956ea125ee24f14a451fd03a284d663
+# f78027510f8a487f8d4e8bf274978c61
+msgid "Testing the AWS API interface"
+msgstr ""
+
+#: ../../developer_guide.rst:20
+# 74ac0a26ef2e4fad99f218beafca959b
+msgid "Prerequisites"
+msgstr ""
+
+#: ../../developer_guide.rst:22
+# d62a80da8f72450fb3042984efc65381
+msgid "In this section we'll look at installing the dependencies you'll need for Apache CloudStack development."
+msgstr ""
+
+#: ../../developer_guide.rst:26
+# 1293735d08304e438df4d231fd9a602c
+msgid "On Ubuntu 12.04"
+msgstr ""
+
+#: ../../developer_guide.rst:28
+#: ../../developer_guide.rst:105
+# d1ad39d0193e4fdfb1b38a70a5409bfd
+# be623c5672e64a878c69313bd57bf97d
+msgid "First update and upgrade your system:"
+msgstr ""
+
+#: ../../developer_guide.rst:35
+# 515cc3ee920143b0a86beef63bd6d782
+msgid "NTP might already be installed, check it with ``service ntp status``. If it's not then install NTP to synchronize the clocks:"
+msgstr ""
+
+#: ../../developer_guide.rst:42
+#: ../../developer_guide.rst:118
+# 4a52a01411eb42b98e46f94978008eb4
+# 2c13eaff12c04b18af30f899add0eb45
+msgid "Install ``openjdk``. As we're using Linux, OpenJDK is our first choice."
+msgstr ""
+
+#: ../../developer_guide.rst:48
+# f04daa6be11c45beae58c455901d8f6c
+msgid "Install ``tomcat6``, note that the new version of tomcat on `Ubuntu <http://packages.ubuntu.com/precise/all/tomcat6>`__ is the 6.0.35 version."
+msgstr ""
+
+#: ../../developer_guide.rst:56
+#: ../../developer_guide.rst:141
+# 35da40eb45c84d80bce02f7e347c27f7
+# 9b90bffd5d744e20acf7be0491b4ce65
+msgid "Next, we'll install MySQL if it's not already present on the system."
+msgstr ""
+
+#: ../../developer_guide.rst:62
+#: ../../developer_guide.rst:147
+# e26c79313e5e4528aba516b8b8ece9d8
+# d8fb218502874578a85a5b15da88c447
+msgid "Remember to set the correct ``mysql`` password in the CloudStack properties file. Mysql should be running but you can check it's status with:"
+msgstr ""
+
+#: ../../developer_guide.rst:70
+# 706465b6a843445099c5b27e7d83a8d7
+msgid "Developers wanting to build CloudStack from source will want to install the following additional packages. If you dont' want to build from source just jump to the next section."
+msgstr ""
+
+#: ../../developer_guide.rst:74
+#: ../../developer_guide.rst:155
+# f2054657f7a740a3a913c84c8b106f75
+# fdc1c399ba0c41d49fdd4f90b0a4b203
+msgid "Install ``git`` to later clone the CloudStack source code:"
+msgstr ""
+
+#: ../../developer_guide.rst:80
+# 36e58aa93a534a019dcd4bb2d179b1dc
+msgid "Install ``Maven`` to later build CloudStack"
+msgstr ""
+
+#: ../../developer_guide.rst:86
+#: ../../developer_guide.rst:185
+# 266630e646c14f149a80a8080bc4a605
+# b362ed17e6ea43919b1119134acbee67
+msgid "This should have installed Maven 3.0, check the version number with ``mvn --version``"
+msgstr ""
+
+#: ../../developer_guide.rst:89
+#: ../../developer_guide.rst:188
+# 0b84891f11754ca1b6aa57d307b41da0
+# 7eea27fb13d64a71afe4098449f7941a
+msgid "A little bit of Python can be used (e.g simulator), install the Python package management tools:"
+msgstr ""
+
+#: ../../developer_guide.rst:96
+#: ../../developer_guide.rst:207
+# f241bf5ebf2b426c8ca5da09dd3c2926
+# 872eab2916d24aa2b16ef1dec59b6ae4
+msgid "Finally install ``mkisofs`` with:"
+msgstr ""
+
+#: ../../developer_guide.rst:103
+# 4c8d5bdb7efc4ad297090744e0b5041b
+msgid "On centOS 6.4"
+msgstr ""
+
+#: ../../developer_guide.rst:112
+# 7bf47463418146c19a2a78e6eb8c704a
+msgid "If not already installed, install NTP for clock synchornization"
+msgstr ""
+
+#: ../../developer_guide.rst:124
+# 3eb3a55c55a64e89bf977cacab10742b
+msgid "Install ``tomcat6``, note that the version of tomcat6 in the default CentOS 6.4 repo is 6.0.24, so we will grab the 6.0.35 version. The 6.0.24 version will be installed anyway as a dependency to cloudstack."
+msgstr ""
+
+#: ../../developer_guide.rst:133
+# 152fbd52e1674b388c1563eee33ac833
+msgid "Setup tomcat6 system wide by creating a file ``/etc/profile.d/tomcat.sh`` with the following content:"
+msgstr ""
+
+#: ../../developer_guide.rst:161
+# 890e6701f64c4b778299fbb766c03a08
+msgid "Install ``Maven`` to later build CloudStack. Grab the 3.0.5 release from the Maven `website <http://maven.apache.org/download.cgi>`__"
+msgstr ""
+
+#: ../../developer_guide.rst:171
+# e4f4020b65d54bcca21983184d1ebf14
+msgid "Setup Maven system wide by creating a ``/etc/profile.d/maven.sh`` file with the following content:"
+msgstr ""
+
+#: ../../developer_guide.rst:179
+# 93a2a4707fbb4f3c9dca441314ef0f5b
+msgid "Log out and log in again and you will have maven in your PATH:"
+msgstr ""
+
+#: ../../developer_guide.rst:195
+# 705ab873d8594008836944d2fdb91ad0
+msgid "To install python-pip you might want to setup the Extra Packages for Enterprise Linux (EPEL) repo"
+msgstr ""
+
+#: ../../developer_guide.rst:204
+# 54199fd0c3f14def8421b213f70c72cd
+msgid "Then update you repository cache ``yum update`` and install pip ``yum -y install python-pip``"
+msgstr ""
+
+#: ../../developer_guide.rst:215
+# 436a0377e85244e6a89d96d94c6beef9
+msgid "Installing from Source"
+msgstr ""
+
+#: ../../developer_guide.rst:217
+# b4b0b7748d0e448b9c381f7675f7806b
+msgid "CloudStack uses git for source version control, if you know little about `git <http://book.git-scm.com/>`__ is a good start. Once you have git setup on your machine, pull the source with:"
+msgstr ""
+
+#: ../../developer_guide.rst:225
+# 959ab8583f1c488096ee96002d7430bb
+msgid "To build the latest stable release:"
+msgstr ""
+
+#: ../../developer_guide.rst:231
+# 32c17b3a428d4f13a0424591bc786dbb
+msgid "To compile Apache CloudStack, go to the cloudstack source folder and run:"
+msgstr ""
+
+#: ../../developer_guide.rst:238
+# 0a54ef76f0e64d71b6a360f37d44a53f
+msgid "If you want to skip the tests add ``-DskipTests`` to the command above. Do NOT use ``-Dmaven.test.skip=true`` because that will break the build."
+msgstr ""
+
+#: ../../developer_guide.rst:241
+# f0271a41ba4f45f690af10f47502929e
+msgid "You will have made sure to set the proper db password in ``utils/conf/db.properties``"
+msgstr ""
+
+#: ../../developer_guide.rst:244
+# 54b58ef51d8e4ad285647fe474a79982
+msgid "Deploy the database next:"
+msgstr ""
+
+#: ../../developer_guide.rst:250
+# 2122fb6f613d43a781c2f4007e3fd921
+msgid "Run Apache CloudStack with jetty for testing. Note that ``tomcat`` maybe be running on port 8080, stop it before you use ``jetty``"
+msgstr ""
+
+#: ../../developer_guide.rst:257
+# 5b053ff2ea4742869f84d9168092cd85
+msgid "Log Into Apache CloudStack:"
+msgstr ""
+
+#: ../../developer_guide.rst:259
+# 0257fca9cb6a4e7cb348b6a94d6c5c16
+msgid "Open your Web browser and use this URL to connect to CloudStack:"
+msgstr ""
+
+#: ../../developer_guide.rst:265
+# 3c66106a410a484db9f40c126c10d71f
+msgid "Replace ``localhost`` with the IP of your management server if need be."
+msgstr ""
+
+#: ../../developer_guide.rst:267
+# 0bb7c9cacc68411b8f2531ede4d1864d
+msgid "If you have iptables enabled, you may have to open the ports used by CloudStack. Specifically, ports 8080, 8250, and 9090."
+msgstr ""
+
+#: ../../developer_guide.rst:269
+# 66464a03df3a4a21898be477a7ba82ce
+msgid "You can now start configuring a Zone, playing with the API. Of course we did not setup any infrastructure, there is no storage, no hypervisors...etc. However you can run tests using the simulator. The following section shows you how to use the simulator so that you don't have to setup a physical infrastructure."
+msgstr ""
+
+#: ../../developer_guide.rst:276
+# 7b8da57d07b6433591f284e715d12591
+msgid "Using the Simulator"
+msgstr ""
+
+#: ../../developer_guide.rst:278
+# c5a7fd74375f49ba9b6ac5f20c8b62a3
+msgid "CloudStack comes with a simulator based on Python bindings called *Marvin*. Marvin is available in the CloudStack source code or on Pypi. With Marvin you can simulate your data center infrastructure by providing CloudStack with a configuration file that defines the number of zones/pods/clusters/hosts, types of storage etc. You can then develop and test the CloudStack management server *as if* it was managing your production infrastructure."
+msgstr ""
+
+#: ../../developer_guide.rst:286
+# 910cc167b7ea42cdaf3c2c8194ae8a2b
+msgid "Do a clean build:"
+msgstr ""
+
+#: ../../developer_guide.rst:292
+# 60dfd43a808f43efa474d6c33f97a310
+msgid "Deploy the database:"
+msgstr ""
+
+#: ../../developer_guide.rst:299
+# c2ddf475c9a4458095381fdf5b36b7c8
+msgid "Install marvin. Note that you will need to have installed ``pip`` properly in the prerequisites step."
+msgstr ""
+
+#: ../../developer_guide.rst:306
+# 1dc977631ad34ca7a239c5ecbb85e4ee
+msgid "Stop jetty (from any previous runs)"
+msgstr ""
+
+#: ../../developer_guide.rst:312
+# e2356af9ad664188b84f183581bee912
+msgid "Start jetty"
+msgstr ""
+
+#: ../../developer_guide.rst:318
+# 81afb780da8545b6acc1c20b0e58af14
+msgid "Setup a basic zone with Marvin. In a separate shell://"
+msgstr ""
+
+#: ../../developer_guide.rst:324
+# 1c70455811e54629bfd79ac64c3fc76a
+msgid "At this stage log in the CloudStack management server at http://localhost:8080/client with the credentials admin/password, you should see a fully configured basic zone infrastructure. To simulate an advanced zone replace ``basic.cfg`` with ``advanced.cfg``."
+msgstr ""
+
+#: ../../developer_guide.rst:329
+# fc4686e3709d491c95f3817ca634b9aa
+msgid "You can now run integration tests, use the API etc..."
+msgstr ""
+
+#: ../../developer_guide.rst:332
+# f43ce08473a443e0bce6cb55638ff6fb
+msgid "Using DevCloud"
+msgstr ""
+
+#: ../../developer_guide.rst:334
+# d99c1e63a66443539d663a0cba7beca0
+msgid "The Installing from source section will only get you to the point of runnign the management server, it does not get you any hypervisors. The simulator section gets you a simulated datacenter for testing. With DevCloud you can run at least one hypervisor and add it to your management server the way you would a real physical machine."
+msgstr ""
+
+#: ../../developer_guide.rst:340
+# 168253f881c04354b99dca74e7f5b0f1
+msgid "`DevCloud <https://cwiki.apache.org/confluence/display/CLOUDSTACK/DevCloud>`__ is the CloudStack sandbox, the standard version is a VirtualBox based image. There is also a KVM based image for it. Here we only show steps with the VirtualBox image. For KVM see the `wiki <https://cwiki.apache.org/confluence/display/CLOUDSTACK/devcloud-kvm>`__."
+msgstr ""
+
+#: ../../developer_guide.rst:346
+# 356c77a0078f47408537fe8f1e31d6dd
+msgid "\\*\\* DevCloud Pre-requisites"
+msgstr ""
+
+#: ../../developer_guide.rst:348
+# 11bd2fad2f484f2f8b8c6b7ed60b1250
+msgid "Install `VirtualBox <http://www.virtualbox.org>`__ on your machine"
+msgstr ""
+
+#: ../../developer_guide.rst:350
+# d7bc0d03f3444e498f06a605608b9052
+msgid "Run VirtualBox and under >Preferences create a *host-only interface* on which you disable the DHCP server"
+msgstr ""
+
+#: ../../developer_guide.rst:353
+# 5c0b9c8ea6014082898304ea288ea1cf
+msgid "Download the DevCloud `image <http://people.apache.org/~bhaisaab/cloudstack/devcloud/devcloud2.ova>`__"
+msgstr ""
+
+#: ../../developer_guide.rst:356
+# e0a8e6ff6f5e4fcf9e0249f0ba785ecc
+msgid "In VirtualBox, under File > Import Appliance import the DevCloud image."
+msgstr ""
+
+#: ../../developer_guide.rst:359
+# c4ddca1ab8fd40938573ab654fbc2169
+msgid "Verify the settings under > Settings and check the ``enable PAE`` option in the processor menu"
+msgstr ""
+
+#: ../../developer_guide.rst:362
+# 086a74de91ec46829227fe969cbf8b0c
+msgid "Once the VM has booted try to ``ssh`` to it with credentials: ``root/password``"
+msgstr ""
+
+#: ../../developer_guide.rst:365
+# 5306cafba5b649ff96137347bd6739cf
+msgid "ssh root@192.168.56.10"
+msgstr ""
+
+#: ../../developer_guide.rst:368
+# ba0b24b4a7914152bf9c97b90f0456d9
+msgid "Adding DevCloud as an Hypervisor"
+msgstr ""
+
+#: ../../developer_guide.rst:370
+# 90a83e4e6fc246f383835f00daea0315
+msgid "Picking up from a clean build:"
+msgstr ""
+
+#: ../../developer_guide.rst:377
+# 18e7f5520af948fd9f6cd2215ddd2b4f
+msgid "At this stage install marvin similarly than with the simulator:"
+msgstr ""
+
+#: ../../developer_guide.rst:383
+# 4081a35f553c4690b8c41bed96c20e81
+msgid "Start the management server"
+msgstr ""
+
+#: ../../developer_guide.rst:389
+# cd9dceaaa6d3449f8260f7987d24e0e4
+msgid "Then you are going to configure CloudStack to use the running DevCloud instance:"
+msgstr ""
+
+#: ../../developer_guide.rst:397
+# 2a20e453295741e0addd797848f68254
+msgid "If you are curious, check the ``devcloud.cfg`` file and see how the data center is defined: 1 Zone, 1 Pod, 1 Cluster, 1 Host, 1 primary Storage, 1 Seondary Storage, all provided by Devcloud."
+msgstr ""
+
+#: ../../developer_guide.rst:401
+# 287ad3cc0fc64288a0f2cae9770decb2
+msgid "You can now log in the management server at ``http://localhost:8080/client`` and start experimenting with the UI or the API."
+msgstr ""
+
+#: ../../developer_guide.rst:405
+# a35e6fa14ec84e00acef35655b70837a
+msgid "Do note that the management server is running in your local machine and that DevCloud is used only as a n Hypervisor. You could potentially run the management server within DevCloud as well, or memory granted, run multiple DevClouds."
+msgstr ""
+
+#: ../../developer_guide.rst:411
+# 0b216797731e464fb1daa87f7f9dce1c
+msgid "Building Packages"
+msgstr ""
+
+#: ../../developer_guide.rst:413
+# aa52ec9b95b94fff98aeb64a23855ff5
+msgid "Working from source is necessary when developing CloudStack. As mentioned earlier this is not primarily intended for users. However some may want to modify the code for their own use and specific infrastructure. The may also need to build their own packages for security reasons and due to network connectivity constraints. This section shows you the gist of how to build packages. We assume that the reader will know how to create a repository to serve this packages. The complete documentation is available on the `website <http://cloudstack.apache.org/docs/en-US/Apache_CloudStack/4.2.0/html/Installation_Guide/sect-source-builddebs.html>`__"
+msgstr ""
+
+#: ../../developer_guide.rst:423
+# 2dc15f1c96914156a0e85887844d8a90
+msgid "To build debian packages you will need couple extra packages that we did not need to install for source compilation:"
+msgstr ""
+
+#: ../../developer_guide.rst:431
+# e0134f646f2b416ca19265ef188af9a7
+msgid "Then build the packages with:"
+msgstr ""
+
+#: ../../developer_guide.rst:437
+# 7fc94e8e24f64ccbb9a5f7e2a1a0fefc
+msgid "One directory up from the CloudStack root dir you will find:"
+msgstr ""
+
+#: ../../developer_guide.rst:452
+# 9e40c2af8b5d4ff088904366476f5d4b
+msgid "Of course the community provides a repository for these packages and you can use it instead of building your own packages and putting them in your own repo. Instructions on how to use this community repository are available in the installation book."
+msgstr ""
+
+#: ../../developer_guide.rst:460
+# 7c104d4cd0fe475e863b91f53449a5c5
+msgid "The CloudStack API is a query based API using http that return results in XML or JSON. It is used to implement the default web UI. This API is not a standard like `OGF OCCI <http://www.ogf.org/gf/group_info/view.php?group=occi-wg>`__ or `DMTF CIMI <http://dmtf.org/standards/cloud>`__ but is easy to learn. Mapping exists between the AWS API and the CloudStack API as will be seen in the next section. Recently a Google Compute Engine interface was also developed that maps the GCE REST API to the CloudStack API described here. The API `docs <http://cloudstack.apache.org/docs/api/>`__ are a good start to learn the extent of the API. Multiple clients exist on `github <https://github.com/search?q=cloudstack+client&ref=cmdform>`__ to use this API, you should be able to find one in your favorite language. The reference documentation for the API and changes that might occur from version to version is availble `on-line <http://cloudstack.apache.org/docs/en-US/Apache_CloudStack/4.1.1/htm
 l/Developers_Guide/index.html>`__. This short section is aimed at providing a quick summary to give you a base understanding of how to use this API. As a quick start, a good way to explore the API is to navigate the dashboard with a firebug console (or similar developer console) to study the queries."
+msgstr ""
+
+#: ../../developer_guide.rst:481
+# 0bcb8dd851254f9b9b0240917b405d84
+msgid "In a succint statement, the CloudStack query API can be used via http GET requests made against your cloud endpoint (e.g http://localhost:8080/client/api). The API name is passed using the ``command`` key and the various parameters for this API call are passed as key value pairs. The request is signed using the access key and secret key of the user making the call. Some calls are synchronous while some are asynchronous, this is documented in the API `docs <http://cloudstack.apache.org/docs/api/>`__. Asynchronous calls return a ``jobid``, the status and result of a job can be queried with the ``queryAsyncJobResult`` call. Let's get started and give an example of calling the ``listUsers`` API in Python."
+msgstr ""
+
+#: ../../developer_guide.rst:493
+# cb1f2074fce34b94ad77db3be1d917ce
+msgid "First you will need to generate keys to make requests. Going through the dashboard, go under ``Accounts`` select the appropriate account then click on ``Show Users`` select the intended users and generate keys using the ``Generate Keys`` icon. You will see an ``API Key`` and ``Secret Key`` field being generated. The keys will be of the form:"
+msgstr ""
+
+#: ../../developer_guide.rst:504
+# f06d2f79776845b69c69945a988dc02d
+msgid "Open a Python shell and import the basic modules necessary to make the request. Do note that this request could be made many different ways, this is just a low level example. The ``urllib*`` modules are used to make the http request and do url encoding. The ``hashlib`` module gives us the sha1 hash function. It used to geenrate the ``hmac`` (Keyed Hashing for Message Authentication) using the secretkey. The result is encoded using the ``base64`` module."
+msgstr ""
+
+#: ../../developer_guide.rst:524
+# 1bc86523e28745838203bfdeacc85364
+msgid "Define the endpoint of the Cloud, the command that you want to execute, the type of the response (i.e XML or JSON) and the keys of the user. Note that we do not put the secretkey in our request dictionary because it is only used to compute the hmac."
+msgstr ""
+
+#: ../../developer_guide.rst:538
+# 4096823c52da4b9d97971621c6bbdee5
+msgid "Build the base request string, the combination of all the key/pairs of the request, url encoded and joined with ampersand."
+msgstr ""
+
+#: ../../developer_guide.rst:547
+# 475167fa6f4f4187bc62b8c7b7dac9e1
+msgid "Compute the signature with hmac, do a 64 bit encoding and a url encoding, the string used for the signature is similar to the base request string shown above but the keys/values are lower cased and joined in a sorted order"
+msgstr ""
+
+#: ../../developer_guide.rst:568
+# e8ab8e0b9eaf4b9183fd8784025e5828
+msgid "Finally, build the entire string by joining the baseurl, the request str and the signature. Then do an http GET:"
+msgstr ""
+
+#: ../../developer_guide.rst:586
+# 34385cfcf355434bbfec59e948728211
+msgid "All the clients that you will find on github will implement this signature technique, you should not have to do it by hand. Now that you have explored the API through the UI and that you understand how to make low level calls, pick your favorite client of use `CloudMonkey <https://pypi.python.org/pypi/cloudmonkey/>`__. CloudMonkey is a sub-project of Apache CloudStack and gives operators/developers the ability to use any of the API methods. It has nice auto-completion and help feature as well as an API discovery mechanism since 4.2."
+msgstr ""
+
+#: ../../developer_guide.rst:598
+# 4bf1c04a89934aca9d24a5a585888739
+msgid "While the native CloudStack API is not a standard, CloudStack provides a AWS EC2 compatible interface. It has the great advantage that existing tools written with EC2 libraries can be re-used against a CloudStack based cloud. In the installation books we described how to run this interface from installing packages. In this section we show you how to compile the interface with ``maven`` and test it with Python boto module."
+msgstr ""
+
+#: ../../developer_guide.rst:606
+# a7d617f55dc447a49c45f903bced3aa6
+msgid "Starting from a running management server (with DevCloud for instance), start the AWS API interface in a separate shell with:"
+msgstr ""
+
+#: ../../developer_guide.rst:613
+# aa447203e885410e967cab647e8fa684
+msgid "Log into the CloudStack UI ``http://localhost:8080/client``, go to *Service Offerings* and edit one of the compute offerings to have the name ``m1.small`` or any of the other AWS EC2 instance types."
+msgstr ""
+
+#: ../../developer_guide.rst:617
+# 84e4d20e634f4ceab2d6ae95fe0bc920
+msgid "With access and secret keys generated for a user you should now be able to use Python `Boto <http://docs.pythonboto.org/en/latest/>`__ module:"
+msgstr ""
+
+#: ../../developer_guide.rst:636
+# 662e136af4714221a6a0414e4e68f928
+msgid "Note the new ``api_version`` number in the connection object and also note that there was no user registration to make like in previous CloudStack releases."
+msgstr ""
+
+#: ../../developer_guide.rst:641
+# b2bbf2564c724ebe98d0ac08c0ec5e58
+msgid "Conclusions"
+msgstr ""
+
+#: ../../developer_guide.rst:643
+# 590c4edda76644fe9a6410b6b2cb10fd
+msgid "CloudStack is a mostly Java application running with Tomcat and Mysql. It consists of a management server and depending on the hypervisors being used, an agent installed on the hypervisor farm. To complete a Cloud infrastructure however you will also need some Zone wide storage a.k.a Secondary Storage and some Cluster wide storage a.k.a Primary storage. The choice of hypervisor, storage solution and type of Zone (i.e Basic vs. Advanced) will dictate how complex your installation can be. As a quick start, you might want to consider KVM+NFS and a Basic Zone."
+msgstr ""
+
+#: ../../developer_guide.rst:653
+# 035523d6dcd4492cb920fdd912716794
+msgid "If you've run into any problems with this, please ask on the cloudstack-dev `mailing list </mailing-lists.html>`__."
+msgstr ""
+

http://git-wip-us.apache.org/repos/asf/cloudstack-docs/blob/7d6892fd/rtd/source/locale/pot/index.pot
----------------------------------------------------------------------
diff --git a/rtd/source/locale/pot/index.pot b/rtd/source/locale/pot/index.pot
new file mode 100644
index 0000000..94276b8
--- /dev/null
+++ b/rtd/source/locale/pot/index.pot
@@ -0,0 +1,78 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2014, Apache CloudStack
+# This file is distributed under the same license as the Apache CloudStack package.
+# FIRST AUTHOR <EM...@ADDRESS>, YEAR.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: Apache CloudStack 4.3\n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2014-03-31 13:49-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:7
+# 23c03bcc367d4722babe767a2ded0a0a
+msgid "Welcome to CloudStack Documentation !"
+msgstr ""
+
+#: ../../index.rst:12
+# 3351811001dc4ad88fd1c24e26edc842
+msgid "We are in the process of changing documentation format as well as hosting mechanism. Please be patient with us as we migrate our entire documentation to this new setup."
+msgstr ""
+
+#: ../../index.rst:16
+# 0c1f1b982e1f4ea0ab2e59763b54e0af
+msgid "Introduction"
+msgstr ""
+
+#: ../../index.rst:24
+# e5a4d610461549f2b9e9052a9bd37144
+msgid "Navigating the docs"
+msgstr ""
+
+#: ../../index.rst:26
+# b6ac1efdb8e346ad887e3d1bca3353cf
+msgid "Now that you have gone over the basic concepts of CloudStack you are ready to dive into the installation and operation."
+msgstr ""
+
+#: ../../index.rst:28
+# cbfe4ed11b86453ba3a3afc35075b554
+msgid "See the `Installation Guide <http://docs.cloudstack.apache.org/projects/cloudstack-installation>`_"
+msgstr ""
+
+#: ../../index.rst:30
+# 5fede185b96b42dea9024c0107dc3cbd
+msgid "See the `Administration Guide <http://docs.cloudstack.apache.org/projects/cloudstack-administration>`_"
+msgstr ""
+
+#: ../../index.rst:32
+# 0e4c89a1c62a42c687b191be08fce2bd
+msgid "See the `Release Notes <http://docs.cloudstack.apache.org/projects/cloudstack-release-notes>`_"
+msgstr ""
+
+#: ../../index.rst:34
+# ceeeb54aa3c144398acf5e519ee0948d
+msgid "Below you will find very specific documentation on advanced networking_ which you can skip if you are just getting started."
+msgstr ""
+
+#: ../../index.rst:36
+# bbf8a8d000f444838cea0bbca7cba655
+msgid "Developers will also find below a short developers_ guide."
+msgstr ""
+
+#: ../../index.rst:41
+# 8f8db100dd114a79a5c5ccb6e82fb3b9
+msgid "Advanced Networking Guides"
+msgstr ""
+
+#: ../../index.rst:56
+# 0fbbad32147342afad57da40b4b35f6d
+msgid "Developers Guide"
+msgstr ""
+

[6/6] git commit: setup i18n with transifex and sphinx-intl

[se...@apache.org]

setup i18n with transifex and sphinx-intl


Project: http://git-wip-us.apache.org/repos/asf/cloudstack-docs/repo
Commit: http://git-wip-us.apache.org/repos/asf/cloudstack-docs/commit/7d6892fd
Tree: http://git-wip-us.apache.org/repos/asf/cloudstack-docs/tree/7d6892fd
Diff: http://git-wip-us.apache.org/repos/asf/cloudstack-docs/diff/7d6892fd

Branch: refs/heads/master
Commit: 7d6892fd23c4d9511c5e53939319a7bd08303792
Parents: 3a335d3
Author: Sebastien Goasguen <ru...@gmail.com>
Authored: Mon Mar 31 14:04:51 2014 -0400
Committer: Sebastien Goasguen <ru...@gmail.com>
Committed: Mon Mar 31 14:04:51 2014 -0400

----------------------------------------------------------------------
 rtd/Makefile                                   |    4 +-
 rtd/README.rst                                 |   34 +
 rtd/source/locale/pot/administration_guide.pot | 1011 +++++++
 rtd/source/locale/pot/alloc.pot                |  409 +++
 rtd/source/locale/pot/ansible.pot              |  383 +++
 rtd/source/locale/pot/concepts.pot             | 1181 ++++++++
 rtd/source/locale/pot/dev.pot                  | 2817 +++++++++++++++++++
 rtd/source/locale/pot/developer_guide.pot      |  528 ++++
 rtd/source/locale/pot/index.pot                |   78 +
 rtd/source/locale/pot/networking.pot           | 1940 +++++++++++++
 rtd/source/locale/pot/plugins.pot              |  783 ++++++
 11 files changed, 9166 insertions(+), 2 deletions(-)
----------------------------------------------------------------------


http://git-wip-us.apache.org/repos/asf/cloudstack-docs/blob/7d6892fd/rtd/Makefile
----------------------------------------------------------------------
diff --git a/rtd/Makefile b/rtd/Makefile
index e1d6dd9..5401d7c 100644
--- a/rtd/Makefile
+++ b/rtd/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/blob/7d6892fd/rtd/README.rst
----------------------------------------------------------------------
diff --git a/rtd/README.rst b/rtd/README.rst
index 9aa0887..9468435 100644
--- a/rtd/README.rst
+++ b/rtd/README.rst
@@ -24,6 +24,40 @@ Website
 
 These docs are on-line at <http://docs.cloudstack.apache.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-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/blob/7d6892fd/rtd/source/locale/pot/administration_guide.pot
----------------------------------------------------------------------
diff --git a/rtd/source/locale/pot/administration_guide.pot b/rtd/source/locale/pot/administration_guide.pot
new file mode 100644
index 0000000..b26c37d
--- /dev/null
+++ b/rtd/source/locale/pot/administration_guide.pot
@@ -0,0 +1,1011 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2014, Apache CloudStack
+# This file is distributed under the same license as the Apache CloudStack package.
+# FIRST AUTHOR <EM...@ADDRESS>, YEAR.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: Apache CloudStack 4.3\n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2014-03-31 13:49-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"
+
+#: ../../administration_guide.rst:2
+# f93ee7d929a94d1aa72564b1870baf22
+msgid "Apache CloudStack Administration Guide"
+msgstr ""
+
+#: ../../administration_guide.rst:5
+# 991318d1af8b4843b6b599dd8efc6fd3
+msgid "Backups"
+msgstr ""
+
+#: ../../administration_guide.rst:8
+# 917231f850524d1ba0f1eb122f495ede
+msgid "Monitoring"
+msgstr ""
+
+#: ../../administration_guide.rst:11
+# 7ad6e9ad4b414f67a22054dcabf5fd93
+msgid "SNMP"
+msgstr ""
+
+#: ../../administration_guide.rst:13
+# a61d4132541c4dc6aa18461706c73805
+msgid "CloudStack will send alerts for a number of"
+msgstr ""
+
+#: ../../administration_guide.rst:16
+# e9b1920a542846c4b6dd7350f24604ff
+msgid "Syslog"
+msgstr ""
+
+#: ../../administration_guide.rst:19
+# 79a88d29791844eb871f809b9f93b92a
+msgid "AMQP"
+msgstr ""
+
+#: ../../administration_guide.rst:22
+# 3b8760c6578349c3b77f6f4ea36bbd5a
+msgid "JMX"
+msgstr ""
+
+#: ../../administration_guide.rst:25
+# b39837fbf8d44f1782538f8355388429
+msgid "API Queries"
+msgstr ""
+
+#: ../../administration_guide.rst:29
+# 2e929ed37ab146e999d737a2a372af41
+msgid "Usage"
+msgstr ""
+
+#: ../../administration_guide.rst:32
+# 4c07a35f678448539c1b8e6cf720d6a0
+msgid "Tuning"
+msgstr ""
+
+#: ../../administration_guide.rst:35
+# 9eae43d89b224ca89534b9a12061f257
+msgid "Configuration Parameters"
+msgstr ""
+
+#: ../../administration_guide.rst:38
+# 3975ef164d6744b2a634522261de942b
+msgid "System Reliability and Availability"
+msgstr ""
+
+#: ../../administration_guide.rst:41
+# 2c563940c8a04c2dadce14ae1234e87a
+msgid "HA for Management Server"
+msgstr ""
+
+#: ../../administration_guide.rst:43
+# 8c3d685775114722b0287e3aa03c4f11
+msgid "The CloudStack Management Server should be deployed in a multi-node configuration such that it is not susceptible to individual server failures. The Management Server itself (as distinct from the MySQL database) is stateless and may be placed behind a load balancer."
+msgstr ""
+
+#: ../../administration_guide.rst:45
+# 98974855279a4cbaa867412f06e89600
+msgid "Normal operation of Hosts is not impacted by an outage of all Management Serves. All guest VMs will continue to work."
+msgstr ""
+
+#: ../../administration_guide.rst:47
+# b5c9018bcbc8477db8c34093fc16116c
+msgid "When the Management Server is down, no new VMs can be created, and the end user and admin UI, API, dynamic load distribution, and HA will cease to work."
+msgstr ""
+
+#: ../../administration_guide.rst:50
+# 5fc98a91cc354695bb9eff610b8667e7
+msgid "Management Server Load Balancing"
+msgstr ""
+
+#: ../../administration_guide.rst:52
+# 84b4167f5b1a4b4c9744f07cff1bab35
+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 ""
+
+#: ../../administration_guide.rst:55
+# cd27881746f04a0d929b9b6efd8b3d32
+msgid "Source port"
+msgstr ""
+
+#: ../../administration_guide.rst:55
+# 91f8db675e8f450a8bcd25455b6bd233
+msgid "Destination port"
+msgstr ""
+
+#: ../../administration_guide.rst:55
+# 2ed27a6df81448a9aa9c47172789d416
+msgid "Protocol"
+msgstr ""
+
+#: ../../administration_guide.rst:55
+# 644cdfa1ecaa49d496e7178d9d07fc69
+msgid "Persistence Required?"
+msgstr ""
+
+#: ../../administration_guide.rst:57
+# b656bdc5be594529bb49cddceb0bda5e
+msgid "80 or 443"
+msgstr ""
+
+#: ../../administration_guide.rst:57
+# e16e25248cb14bae876a878e767125b0
+msgid "8080 (or 20400 with AJP)"
+msgstr ""
+
+#: ../../administration_guide.rst:57
+# ce20e784c0e24c4ea83294648499787e
+msgid "HTTP (or AJP)"
+msgstr ""
+
+#: ../../administration_guide.rst:57
+#: ../../administration_guide.rst:58
+# ab33be8dc5424aedb9ee5f24062b29c5
+# 46d9c33fc2274527b9346717f23cfad5
+msgid "Yes"
+msgstr ""
+
+#: ../../administration_guide.rst:58
+#: ../../administration_guide.rst:58
+# e9feebce20be4306bd10338e1ff06068
+# 11f22c09784940779d1699defd245efe
+msgid "8250"
+msgstr ""
+
+#: ../../administration_guide.rst:58
+# a791a4167bcb4daca73ecd1b64a23fa2
+msgid "TCP"
+msgstr ""
+
+#: ../../administration_guide.rst:61
+# 33d8b086229e4f19a53a623fb5e62a13
+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 ""
+
+#: ../../administration_guide.rst:64
+# 2006569208ac4cf7bf748dff1cfe0953
+msgid "Limiting the Rate of API Requests"
+msgstr ""
+
+#: ../../administration_guide.rst:66
+# fcee3fe6cc9d43c0a398617ba6470d26
+msgid "You can limit the rate at which API requests can be placed for each account. This is useful to avoid malicious attacks on the Management Server, prevent performance degradation, and provide fairness to all accounts."
+msgstr ""
+
+#: ../../administration_guide.rst:68
+# 19fee786cade47c6a5592329e9b61745
+msgid "If the number of API calls exceeds the threshold, an error message is returned for any additional API calls. The caller will have to retry these API calls at another time."
+msgstr ""
+
+#: ../../administration_guide.rst:71
+# ad4394d6414847698ae7ba0e0f06ce30
+msgid "Configuring the API Request Rate"
+msgstr ""
+
+#: ../../administration_guide.rst:73
+# f1b90e13ad004a9d86dff559e7cddd6f
+msgid "To control the API request rate, use the following global configuration settings:"
+msgstr ""
+
+#: ../../administration_guide.rst:75
+# 9516f8c3a536423eaadf5546bc517da5
+msgid "api.throttling.enabled - Enable/Disable API throttling. By default, this setting is false, so API throttling is not enabled."
+msgstr ""
+
+#: ../../administration_guide.rst:76
+# b54b779ffe264d118f981c55fe99e7a7
+msgid "api.throttling.interval (in seconds) - Time interval during which the number of API requests is to be counted. When the interval has passed, the API count is reset to 0."
+msgstr ""
+
+#: ../../administration_guide.rst:77
+# a7bea7af86a04d71b340651cadc683c1
+msgid "api.throttling.max - Maximum number of APIs that can be placed within the api.throttling.interval period."
+msgstr ""
+
+#: ../../administration_guide.rst:78
+# 83fa5f527dd84379bd9b795c5b5312c6
+msgid "api.throttling.cachesize - Cache size for storing API counters. Use a value higher than the total number of accounts managed by the cloud. One cache entry is needed for each account, to store the running API total for that account."
+msgstr ""
+
+#: ../../administration_guide.rst:81
+# 20c51c7e8faf419484e834d822f70c51
+msgid "Limitations on API Throttling"
+msgstr ""
+
+#: ../../administration_guide.rst:83
+# 71af836eabc940d5bb07abee65674cb7
+msgid "The following limitations exist in the current implementation of this feature:"
+msgstr ""
+
+#: ../../administration_guide.rst:85
+# 9e18534ecf064499bb0a36dc67ac205b
+msgid "In a deployment with multiple Management Servers, the cache is not synchronized across them. In this case, CloudStack might not be able to ensure that only the exact desired number of API requests are allowed. In the worst case, the number of API calls that might be allowed is (number of Management Servers) * (api.throttling.max)."
+msgstr ""
+
+#: ../../administration_guide.rst:86
+# a96908c8874b46d9b7c8178344780dc7
+msgid "The API commands resetApiLimit and getApiLimit are limited to the Management Server where the API is invoked."
+msgstr ""
+
+#: ../../administration_guide.rst:89
+# 93858f39b7614989bc3678c8cd1df365
+msgid "HA-Enabled Virtual Machines"
+msgstr ""
+
+#: ../../administration_guide.rst:91
+# 0d6415d5b5574039a38efe8b1de02cf6
+msgid "The user can specify a virtual machine as HA-enabled. By default, all virtual router VMs and Elastic Load Balancing VMs are automatically configured as HA-enabled. When an HA-enabled VM crashes, CloudStack detects the crash and restarts the VM automatically within the same Availability Zone. HA is never performed across different Availability Zones. CloudStack has a conservative policy towards restarting VMs and ensures that there will never be two instances of the same VM running at the same time. The Management Server attempts to start the VM on another Host in the same cluster."
+msgstr ""
+
+#: ../../administration_guide.rst:93
+# 486b5760db6f46c3af439c515638845f
+msgid "VM HA is not supported when the VM is using local storage."
+msgstr ""
+
+#: ../../administration_guide.rst:96
+# f75f84bdde994ee38e2355c7c09804cb
+msgid "Dedicated HA Hosts"
+msgstr ""
+
+#: ../../administration_guide.rst:98
+# 4afa4063f74d44709ca6f06c01f4ef5e
+msgid "One or more hosts can be designated for use only by HA-enabled VMs that are restarting due to a host failure. Setting up a pool of such dedicated HA hosts as the recovery destination for all HA-enabled VMs is useful to:"
+msgstr ""
+
+#: ../../administration_guide.rst:100
+# c85d9a411f3d445fa32d5756aa4eb8b0
+msgid "Make it easier to determine which VMs have been restarted as part of the CloudStack high-availability function. If a VM is running on a dedicated HA host, then it must be an HA-enabled VM whose original host failed. (With one exception: It is possible for an administrator to manually migrate any VM to a dedicated HA host.)."
+msgstr ""
+
+#: ../../administration_guide.rst:101
+# e8278e9aa42f4badb54a36dcf4bbb83f
+msgid "Keep HA-enabled VMs from restarting on hosts which may be reserved for other purposes."
+msgstr ""
+
+#: ../../administration_guide.rst:103
+# b601599b35184733b326c909fcd39e4c
+msgid "The dedicated HA option is set through a special host tag when the host is created. To allow the administrator to dedicate hosts to only HA-enabled VMs, set the global configuration variable ha.tag to the desired tag (for example, \"ha_host\"), and restart the Management Server. Enter the value in the Host Tags field when adding the host(s) that you want to dedicate to HA-enabled VMs."
+msgstr ""
+
+#: ../../administration_guide.rst:106
+# 04fc21b488b04cbeb84c04decd054192
+msgid "Primary Storage Outage and Data Loss"
+msgstr ""
+
+#: ../../administration_guide.rst:108
+# abba717b117a4182a128d7d3da4ca9e5
+msgid "When a primary storage outage occurs the hypervisor immediately stops all VMs stored on that storage device. Guests that are marked for HA will be restarted as soon as practical when the primary storage comes back on line. With NFS, the hypervisor may allow the virtual machines to continue running depending on the nature of the issue. For example, an NFS hang will cause the guest VMs to be suspended until storage connectivity is restored.Primary storage is not designed to be backed up. Individual volumes in primary storage can be backed up using snapshots."
+msgstr ""
+
+#: ../../administration_guide.rst:111
+# 58deb58752c8404f988211162156aafe
+msgid "Secondary Storage Outage and Data Loss"
+msgstr ""
+
+#: ../../administration_guide.rst:113
+# c131fb29bcb44bac876dfd75bd2da66f
+msgid "For a Zone that has only one secondary storage server, a secondary storage outage will have feature level impact to the system but will not impact running guest VMs. It may become impossible to create a VM with the selected template for a user. A user may also not be able to save snapshots or examine/restore saved snapshots. These features will automatically be available when the secondary storage comes back online."
+msgstr ""
+
+#: ../../administration_guide.rst:115
+# 3f319f23eed9475f90dd4375c5b143e9
+msgid "Secondary storage data loss will impact recently added user data including templates, snapshots, and ISO images. Secondary storage should be backed up periodically. Multiple secondary storage servers can be provisioned within each zone to increase the scalability of the system."
+msgstr ""
+
+#: ../../administration_guide.rst:118
+# 63431ac28ab94015bc3d22a2c9aa5588
+msgid "Managing System VMs"
+msgstr ""
+
+#: ../../administration_guide.rst:120
+# 9cc6d4d767c94824b178fe69f6d3cdd6
+msgid "CloudStack uses several types of system virtual machines to perform tasks in the cloud. In general CloudStack manages these system VMs and creates, starts, and stops them as needed based on scale and immediate needs. However, the administrator should be aware of them and their roles to assist in debugging issues."
+msgstr ""
+
+#: ../../administration_guide.rst:122
+# 266cccfbc6e745ffacd810b2ff7f20c6
+msgid "You can configure the system.vm.random.password parameter to create a random system VM password to ensure higher security. If you reset the value for system.vm.random.password to true and restart the Management Server, a random password is generated and stored encrypted in the database. You can view the decrypted password under the system.vm.password global parameter on the CloudStack UI or by calling the listConfigurations API."
+msgstr ""
+
+#: ../../administration_guide.rst:125
+# 6e644c2ed32b473cb4385b23cefe3063
+msgid "The System VM Template"
+msgstr ""
+
+#: ../../administration_guide.rst:127
+# dae55d4f72894cdfb4f76d76684dcc89
+msgid "The System VMs come from a single template. The System VM has the following characteristics:"
+msgstr ""
+
+#: ../../administration_guide.rst:129
+# 4ca2782f2c2a47999695afbc38836c65
+msgid "Debian 6.0 (\"Squeeze\"), 2.6.32 kernel with the latest security patches from the Debian security APT repository"
+msgstr ""
+
+#: ../../administration_guide.rst:130
+# 3c22e6bff3f74fd9a021e96bae35f25f
+msgid "Has a minimal set of packages installed thereby reducing the attack surface"
+msgstr ""
+
+#: ../../administration_guide.rst:131
+# ea7e6186b6c0472098727daa064a051b
+msgid "32-bit for enhanced performance on Xen/VMWare"
+msgstr ""
+
+#: ../../administration_guide.rst:132
+# d9a9609f2bff4a49bdf88a77257782dd
+msgid "pvops kernel with Xen PV drivers, KVM virtio drivers, and VMware tools for optimum performance on all hypervisors"
+msgstr ""
+
+#: ../../administration_guide.rst:133
+# 99dccc1bfff645c8a364e8e49f0f6c21
+msgid "Xen tools inclusion allows performance monitoring"
+msgstr ""
+
+#: ../../administration_guide.rst:134
+# 50f216bb2fc0492c84ab67700014248e
+msgid "Latest versions of HAProxy, iptables, IPsec, and Apache from debian repository ensures improved security and speed"
+msgstr ""
+
+#: ../../administration_guide.rst:135
+# d114044a0adb4170a56fb3c8c214d032
+msgid "Latest version of JRE from Sun/Oracle ensures improved security and speed"
+msgstr ""
+
+#: ../../administration_guide.rst:138
+# 6a535f3f13ad438d9c47d244bdd057fa
+msgid "Accessing System VMs"
+msgstr ""
+
+#: ../../administration_guide.rst:140
+# 7a5c16c43c6247e48e18cd3e7fcd6495
+msgid "It may sometimes be necessary to access System VMs for diagnostics of certain issues, for example if you are experiencing SSVM (Secondary Storage VM) connection issues. Use the steps below in order to connect to the SSH console of a running System VM."
+msgstr ""
+
+#: ../../administration_guide.rst:142
+# f13f9e8ecc4148f18b10202f85506f55
+msgid "Accessing System VMs over the network requires the use of private keys and connecting to System VMs SSH Daemon on port 3922. XenServer/KVM Hypervisors store this key at /root/.ssh/id_rsa.cloud on each CloudStack agent. To access System VMs running on ESXi, the key is stored on the management server at /var/lib/cloudstack/management/.ssh/id_rsa."
+msgstr ""
+
+#: ../../administration_guide.rst:144
+# 1e8067437ee2421db9b197daa00bae7c
+msgid "Find the details of the System VM #. Log in with admin privileges to the CloudStack UI. #. Click Infrastructure, then System VMs, and then click the name of a running VM. #. Take a note of the 'Host', 'Private IP Address' and 'Link Local IP Address' of the System VM you wish to access."
+msgstr ""
+
+#: ../../administration_guide.rst:148
+# bd2ce6ef46d04462a075510c7534980b
+msgid "XenServer/KVM Hypervisors #. Connect to the Host of which the System VM is running. #. SSH to the 'Link Local IP Address' of the System VM from the Host on which the VM is running."
+msgstr ""
+
+#: ../../administration_guide.rst:151
+# 6433ce3a240d4b2b9c627bd2a5de1dfe
+msgid "Format: ssh -i <path-to-private-key> <link-local-ip> -p 3922 Example: root@faith:~# ssh -i /root/.ssh/id_rsa.cloud 169.254.3.93 -p 3922"
+msgstr ""
+
+#: ../../administration_guide.rst:153
+# de9f86caeb63454e8c576f34193cf7ab
+msgid "ESXi Hypervisors #. Connect to your CloudStack Management Server. #. ESXi users should SSH to the private IP address of the System VM."
+msgstr ""
+
+#: ../../administration_guide.rst:156
+# dcc9b190ecda432bbde1662354d32bef
+msgid "Format: ssh -i <path-to-private-key> <vm-private-ip> -p 3922 Example: root@management:~# ssh -i /var/lib/cloudstack/management/.ssh/id_rsa 172.16.0.250 -p 3922"
+msgstr ""
+
+#: ../../administration_guide.rst:160
+# 2e86ae8ea7464bbd9beeb726acb8b043
+msgid "Multiple System VM Support for VMware"
+msgstr ""
+
+#: ../../administration_guide.rst:162
+# 561c949006c243cf961bff0f079dfe07
+msgid "Every CloudStack zone has single System VM for template processing tasks such as downloading templates, uploading templates, and uploading ISOs. In a zone where VMware is being used, additional System VMs can be launched to process VMware-specific tasks such as taking snapshots and creating private templates. The CloudStack management server launches additional System VMs for VMware-specific tasks as the load increases. The management server monitors and weights all commands sent to these System VMs and performs dynamic load balancing and scaling-up of more System VMs."
+msgstr ""
+
+#: ../../administration_guide.rst:165
+# 912e4a1374ac4bf2925b070cb244ce2a
+msgid "Console Proxy"
+msgstr ""
+
+#: ../../administration_guide.rst:167
+# 22ad7a0de1064dda80e4f083405157f6
+msgid "The Console Proxy is a type of System Virtual Machine that has a role in presenting a console view via the web UI. It connects the user’s browser to the VNC port made available via the hypervisor for the console of the guest. Both the administrator and end user web UIs offer a console connection."
+msgstr ""
+
+#: ../../administration_guide.rst:169
+# e5867fc657414edaa8f94d3deee5fd49
+msgid "Clicking a console icon brings up a new window. The AJAX code downloaded into that window refers to the public IP address of a console proxy VM. There is exactly one public IP address allocated per console proxy VM. The AJAX application connects to this IP. The console proxy then proxies the connection to the VNC port for the requested VM on the Host hosting the guest."
+msgstr ""
+
+#: ../../administration_guide.rst:171
+# fea1c6871dc84d9a921bc61b226fa67b
+msgid "The console proxy VM will periodically report its active session count to the Management Server. The default reporting interval is five seconds. This can be changed through standard Management Server configuration with the parameter consoleproxy.loadscan.interval."
+msgstr ""
+
+#: ../../administration_guide.rst:173
+# f93efafb07bb4c65af3fd841829ed70d
+msgid "Assignment of guest VM to console proxy is determined by first determining if the guest VM has a previous session associated with a console proxy. If it does, the Management Server will assign the guest VM to the target Console Proxy VM regardless of the load on the proxy VM. Failing that, the first available running Console Proxy VM that has the capacity to handle new sessions is used."
+msgstr ""
+
+#: ../../administration_guide.rst:175
+# 79a72a9b6fba4469a648e9e7b4bca111
+msgid "Console proxies can be restarted by administrators but this will interrupt existing console sessions for users."
+msgstr ""
+
+#: ../../administration_guide.rst:178
+# 839f885b3021494684f423b34ea819ce
+msgid "Using a SSL Certificate for the Console Proxy"
+msgstr ""
+
+#: ../../administration_guide.rst:180
+# 13867cd7762344ab9077f325f8730cfa
+msgid "The console viewing functionality uses a dynamic DNS service under the domain name realhostip.com to assist in providing SSL security to console sessions. The console proxy is assigned a public IP address. In order to avoid browser warnings for mismatched SSL certificates, the URL for the new console window is set to the form of https://aaa-bbb-ccc-ddd.realhostip.com. You will see this URL during console session creation. CloudStack includes the realhostip.com SSL certificate in the console proxy VM. Of course, CloudStack cannot know about the DNS A records for our customers' public IPs prior to shipping the software. CloudStack therefore runs a dynamic DNS server that is authoritative for the realhostip.com domain. It maps the aaa-bbb-ccc-ddd part of the DNS name to the IP address aaa.bbb.ccc.ddd on lookups. This allows the browser to correctly connect to the console proxy's public IP, where it then expects and receives a SSL certificate for realhostip.com, and SSL is set up
  without browser warnings."
+msgstr ""
+
+#: ../../administration_guide.rst:183
+# 7bc985d7c4fa46998631086a174c7e33
+msgid "Changing the Console Proxy SSL Certificate and Domain"
+msgstr ""
+
+#: ../../administration_guide.rst:185
+# be495135cea0497eabd43f1977563093
+msgid "If the administrator prefers, it is possible for the URL of the customer's console session to show a domain other than realhostip.com. The administrator can customize the displayed domain by selecting a different domain and uploading a new SSL certificate and private key. The domain must run a DNS service that is capable of resolving queries for addresses of the form aaa-bbb-ccc-ddd.your.domain to an IPv4 IP address in the form aaa.bbb.ccc.ddd, for example, 202.8.44.1. To change the console proxy domain, SSL certificate, and private key:"
+msgstr ""
+
+#: ../../administration_guide.rst:187
+# 6e1c3859863545bca1234725d578d62c
+msgid "Set up dynamic name resolution or populate all possible DNS names in your public IP range into your existing DNS server with the format aaa-bbb-ccc-ddd.company.com -> aaa.bbb.ccc.ddd."
+msgstr ""
+
+#: ../../administration_guide.rst:188
+# ea592a9486d243eb998954bfcc5621cf
+msgid "Generate the private key and certificate signing request (CSR). When you are using openssl to generate private/public key pairs and CSRs, for the private key that you are going to paste into the CloudStack UI, be sure to convert it into PKCS#8 format."
+msgstr ""
+
+#: ../../administration_guide.rst:190
+# 75aacc2da9c4408caa2777a4b4c9a49d
+msgid "Generate a new 2048-bit private key::"
+msgstr ""
+
+#: ../../administration_guide.rst:192
+# a047f4c4f4ec402c926de521dd46a5cc
+msgid "openssl genrsa -des3 -out yourprivate.key 2048"
+msgstr ""
+
+#: ../../administration_guide.rst:194
+# 54f81ed070be40d48f5bed678a7eb8ed
+msgid "Generate a new certificate CSR::"
+msgstr ""
+
+#: ../../administration_guide.rst:196
+# 4260ff8e5ab7400cb292e890d7b0aa9d
+msgid "openssl req -new -key yourprivate.key -out yourcertificate.csr"
+msgstr ""
+
+#: ../../administration_guide.rst:198
+# a8c4e79660e34691a4a73a719fb9eb31
+msgid "Head to the website of your favorite trusted Certificate Authority, purchase an SSL certificate, and submit the CSR. You should receive a valid certificate in return"
+msgstr ""
+
+#: ../../administration_guide.rst:199
+# 29bb21dc37ce46f78fffa06e4b71302a
+msgid "Convert your private key format into PKCS#8 encrypted format.::"
+msgstr ""
+
+#: ../../administration_guide.rst:201
+# a2fa3e01cb89457190182d716691c200
+msgid "openssl pkcs8 -topk8 -in yourprivate.key -out yourprivate.pkcs8.encrypted.key"
+msgstr ""
+
+#: ../../administration_guide.rst:203
+# b62ad584d36048da8a20f050f4a18f85
+msgid "Convert your PKCS#8 encrypted private key into the PKCS#8 format that is compliant with CloudStack::"
+msgstr ""
+
+#: ../../administration_guide.rst:205
+# a5ccd5855fb5436696cb211da2ee0ba3
+msgid "openssl pkcs8 -in yourprivate.pkcs8.encrypted.key -out yourprivate.pkcs8.key"
+msgstr ""
+
+#: ../../administration_guide.rst:207
+# 7d5fd6db293b4d33afe9046cb296bb4d
+msgid "In the Update SSL Certificate screen of the CloudStack UI, paste the following: *. The certificate you've just generated. *. The private key you've just generated. *. The desired new domain name; for example, company.com"
+msgstr ""
+
+#: ../../administration_guide.rst:212
+# 6d79a146218c4624b5cf981d5bff6257
+msgid "4. The desired new domain name; for example, company.com This stops all currently running console proxy VMs, then restarts them with the new certificate and key. Users might notice a brief interruption in console availability."
+msgstr ""
+
+#: ../../administration_guide.rst:215
+# 8e998b147518419b8c5503db597b2855
+msgid "The Management Server generates URLs of the form \"aaa-bbb-ccc-ddd.company.com\" after this change is made. The new console requests will be served with the new DNS domain name, certificate, and key."
+msgstr ""
+
+#: ../../administration_guide.rst:218
+# d2d3d433bf244542bd961449d46e5899
+msgid "Virtual Router"
+msgstr ""
+
+#: ../../administration_guide.rst:220
+# 9b86999a5c224420bd803344df34468f
+msgid "The virtual router is a type of System Virtual Machine. The virtual router is one of the most frequently used service providers in CloudStack. The end user has no direct access to the virtual router. Users can ping the virtual router and take actions that affect it (such as setting up port forwarding), but users do not have SSH access into the virtual router."
+msgstr ""
+
+#: ../../administration_guide.rst:222
+# a70cb88cc6e3420cabb4f6491fc94ac2
+msgid "Virtual routers can be restarted by administrators, but this will interrupt public network access and other services for end users. A basic test in debugging networking issues is to attempt to ping the virtual router from a guest VM. Some of the characteristics of the virtual router are determined by its associated system service offering.."
+msgstr ""
+
+#: ../../administration_guide.rst:225
+# 1a9122077ee64356a9bba962146fa923
+msgid "Configuring the Virtual Router"
+msgstr ""
+
+#: ../../administration_guide.rst:227
+# 7580f3cac07348bc846c961a3f909830
+msgid "You can set the following: *. IP range *. Supported network services *. Default domain name for the network serviced by the virtual router *. Gateway IP address *. How often CloudStack fetches network usage statistics from CloudStack virtual routers. If you want to collect traffic metering data from the virtual router, set the global configuration parameter router.stats.interval. If you are not using the virtual router to gather network usage statistics, set it to 0."
+msgstr ""
+
+#: ../../administration_guide.rst:235
+# d6b114ce9869442589bdf6a3497ec9f2
+msgid "Upgrading a Virtual Router with System Service Offerings"
+msgstr ""
+
+#: ../../administration_guide.rst:237
+# e32118155eeb466d8480f0c1b7dd3722
+msgid "When CloudStack creates a virtual router, it uses default settings which are defined in a default system service offering. See Section 8.2, “System Service Offerings”. All the virtual routers in a single guest network use the same system service offering. You can upgrade the capabilities of the virtual router by creating and applying a custom system service offering. Define your custom system service offering. Associate the system service offering with a network offering. Apply the network offering to the network where you want the virtual routers to use the new system service offering."
+msgstr ""
+
+#: ../../administration_guide.rst:243
+# 601dda89c2494c4ab1bd253484d3e712
+msgid "Best Practices for Virtual Routers"
+msgstr ""
+
+#: ../../administration_guide.rst:245
+# 7a7205873af44801aeda6f66a69b801d
+msgid "Restarting a virtual router from a hypervisor console deletes all the iptables rules. To work around this issue, stop the virtual router and start it from the CloudStack UI."
+msgstr ""
+
+#: ../../administration_guide.rst:246
+# 454b3914655c456cad86c222d18f6b0c
+msgid "Do not use the destroyRouter API when only one router is available in the network, because restartNetwork API with the cleanup=false parameter can't recreate it later. If you want to destroy and recreate the single router available in the network, use the restartNetwork API with the cleanup=true parameter."
+msgstr ""
+
+#: ../../administration_guide.rst:249
+# 06dc6516cdef42669857d3cfe718cdcd
+msgid "Secondary Storage VM"
+msgstr ""
+
+#: ../../administration_guide.rst:251
+# 62c65c2618d843f9b268de2c88c8be0a
+msgid "In addition to the hosts, CloudStack’s Secondary Storage VM mounts and writes to secondary storage. Submissions to secondary storage go through the Secondary Storage VM. The Secondary Storage VM can retrieve templates and ISO images from URLs using a variety of protocols. The secondary storage VM provides a background task that takes care of a variety of secondary storage activities: downloading a new template to a Zone, copying templates between Zones, and snapshot backups. The administrator can log in to the secondary storage VM if needed."
+msgstr ""
+
+#: ../../administration_guide.rst:258
+# b2b7431b44ed44b98582c98087d894a7
+msgid "Storage Administration"
+msgstr ""
+
+#: ../../administration_guide.rst:261
+# 4d40f40b40294722a88f1949a46cbde9
+msgid "Hypervisor Host Management"
+msgstr ""
+
+#: ../../administration_guide.rst:264
+# 9a05a7311fa54e3e9926dc5f7cd573a3
+msgid "Maintenance mode"
+msgstr ""
+
+#: ../../administration_guide.rst:266
+# 0a40fb0dc55148c8b9150737a3838c80
+msgid "Maintenance mode makes a host unavailable to have new virtual machines allocated to it. It also starts a process by which running virtual machines are live migrated to other available hosts within the same cluster. It should be noted that the live migration is not universally perfect, and you may end up with recalcitrant virtual machines which are unable to be live migrated. This can be due to lack of hypervisor-specific tooling or other problems."
+msgstr ""
+
+#: ../../administration_guide.rst:269
+# 49b847172c8b4366b82efcce5987d880
+msgid "vCenter and Maintenance mode"
+msgstr ""
+
+#: ../../administration_guide.rst:271
+# 034dd713a7d44a43825529cca70afb32
+msgid "To enter maintenance mode on a vCenter host, both vCenter and CloudStack must be used in concert. CloudStack and vCenter have separate maintenance modes that work closely together."
+msgstr ""
+
+#: ../../administration_guide.rst:273
+# ffa262f627384c329ab46dfe92cb40cc
+msgid "Place the host into CloudStack's \"scheduled maintenance\" mode. This does not invoke the vCenter maintenance mode, but only causes VMs to be migrated off the host When the CloudStack maintenance mode is requested, the host first moves into the Prepare for Maintenance state. In this state it cannot be the target of new guest VM starts. Then all VMs will be migrated off the server. Live migration will be used to move VMs off the host. This allows the guests to be migrated to other hosts with no disruption to the guests. After this migration is completed, the host will enter the Ready for Maintenance mode."
+msgstr ""
+
+#: ../../administration_guide.rst:274
+# 75b75474bea1490ea5ea35271fd988a7
+msgid "Wait for the \"Ready for Maintenance\" indicator to appear in the UI."
+msgstr ""
+
+#: ../../administration_guide.rst:275
+# 3be72549ff1f4fd4a3c3b471f1a9865d
+msgid "Now use vCenter to perform whatever actions are necessary to maintain the host. During this time, the host cannot be the target of new VM allocations."
+msgstr ""
+
+#: ../../administration_guide.rst:276
+# 0c977a03a8644901bc53be37b0312ad1
+msgid "When the maintenance tasks are complete, take the host out of maintenance mode as follows: a. First use vCenter to exit the vCenter maintenance mode. This makes the host ready for CloudStack to reactivate it. b. Then use CloudStack's administrator UI to cancel the CloudStack maintenance mode When the host comes back online, the VMs that were migrated off of it may be migrated back to it manually and new VMs can be added."
+msgstr ""
+
+#: ../../administration_guide.rst:281
+# 6c1a9c2e7ff1400daa889815e4ffb33d
+msgid "XenServer Maintenance Mode"
+msgstr ""
+
+#: ../../administration_guide.rst:283
+# 805f4ccfdd5e40e88e3ccdd57585f19e
+msgid "XenServer, you can take a server offline temporarily by using the Maintenance Mode feature in XenCenter. When you place a server into Maintenance Mode, all running VMs are automatically migrated from it to another host in the same pool. If the server is the pool master, a new master will also be selected for the pool. While a server is Maintenance Mode, you cannot create or start any VMs on it."
+msgstr ""
+
+#: ../../administration_guide.rst:286
+# bcf2b628e6944e33bab4fb118d72de69
+msgid "To place a XenServer host in Maintenace Mode"
+msgstr ""
+
+#: ../../administration_guide.rst:288
+# be9fc81b21864113b444bcdfa60d8575
+msgid "In the Resources pane, select the server, then do one of the following: *. Right-click, then click Enter Maintenance Mode on the shortcut menu. *. On the Server menu, click Enter Maintenance Mode."
+msgstr ""
+
+#: ../../administration_guide.rst:291
+# d8fa3fc85b964c7981677d1619752eb0
+msgid "Click Enter Maintenance Mode."
+msgstr ""
+
+#: ../../administration_guide.rst:293
+# c0374cf7ce0d48559f5120e3d205f078
+msgid "The server's status in the Resources pane shows when all running VMs have been successfully migrated off the server."
+msgstr ""
+
+#: ../../administration_guide.rst:296
+# 1e19387e9ad04b7d94c1a7cf05e3a773
+msgid "To take a Xenserver host out of Maintenance mode"
+msgstr ""
+
+#: ../../administration_guide.rst:298
+# 94d2cbc337c64bdf8d607a5df92e98a5
+msgid "In the Resources pane, select the server, then do one of the following: *Right-click, then click Exit Maintenance Mode on the shortcut menu. *On the Server menu, click Exit Maintenance Mode."
+msgstr ""
+
+#: ../../administration_guide.rst:301
+# c9326e7208a64ca684a56a38cc7aa332
+msgid "Click Exit Maintenance Mode."
+msgstr ""
+
+#: ../../administration_guide.rst:304
+# ec570b7fa796494eafbaf074c90f322e
+msgid "Disabling and enabling Zones, Pods, and Clusters"
+msgstr ""
+
+#: ../../administration_guide.rst:306
+# 5694f1e98fe849d297e898a5da8648ac
+msgid "You can enable or disable a zone, pod, or cluster without permanently removing it from the cloud. This is useful for maintenance or when there are problems that make a portion of the cloud infrastructure unreliable. No new allocations will be made to a disabled zone, pod, or cluster until its state is returned to Enabled. When a zone, pod, or cluster is first added to the cloud, it is Disabled by default. To disable and enable a zone, pod, or cluster:"
+msgstr ""
+
+#: ../../administration_guide.rst:309
+# 83dc1490b2104f3bbf4e3639c0430c61
+msgid "Log in to the CloudStack UI as administrator"
+msgstr ""
+
+#: ../../administration_guide.rst:310
+#: ../../administration_guide.rst:431
+# 3ed8e3e52e234f45b1c0f052ca458bcc
+# cd6f4bb9146e4e9a9018c3066dacab5b
+msgid "In the left navigation bar, click Infrastructure."
+msgstr ""
+
+#: ../../administration_guide.rst:311
+# 5e006224fa21497ea7151f8cd9aae1bb
+msgid "In Zones, click View More."
+msgstr ""
+
+#: ../../administration_guide.rst:312
+# 4d77f0e634da42b9ae2447f2fd463d88
+msgid "If you are disabling or enabling a zone, find the name of the zone in the list, and click the Enable/Disable button."
+msgstr ""
+
+#: ../../administration_guide.rst:313
+# 6b2d8b9b33b444d7a0810e78cd39367d
+msgid "If you are disabling or enabling a pod or cluster, click the name of the zone that contains the pod or cluster."
+msgstr ""
+
+#: ../../administration_guide.rst:314
+# f3afc7444ff340848e9db06e1c2344e5
+msgid "Click the Compute tab."
+msgstr ""
+
+#: ../../administration_guide.rst:315
+# dbd6f2cda70a423e8fce05cbf8e07f34
+msgid "In the Pods or Clusters node of the diagram, click View All."
+msgstr ""
+
+#: ../../administration_guide.rst:316
+# 8b38f319abc447e880ee490e347ca82a
+msgid "Click the pod or cluster name in the list."
+msgstr ""
+
+#: ../../administration_guide.rst:317
+# fe5bc552f0c64f7797c894cf1412d2a7
+msgid "Click the Enable/Disable button."
+msgstr ""
+
+#: ../../administration_guide.rst:320
+# 96b1b42987f04136b94d358fe109e27d
+msgid "Removing hypervisor hosts"
+msgstr ""
+
+#: ../../administration_guide.rst:322
+# 21b14acd77c843d6b304b5e5ada65b2c
+msgid "Hosts can be removed from the cloud as needed. The procedure to remove a host depends on the hypervisor type."
+msgstr ""
+
+#: ../../administration_guide.rst:325
+# 5764a1f3b5504905ab2716b487b14b73
+msgid "Removing XenServer and KVM Hosts"
+msgstr ""
+
+#: ../../administration_guide.rst:326
+# 64851f97d4864165a918d783aacf2146
+msgid "A node cannot be removed from a cluster until it has been placed in maintenance mode. This will ensure that all of the VMs on it have been migrated to other Hosts. To remove a Host from CloudStack:"
+msgstr ""
+
+#: ../../administration_guide.rst:328
+# 8501b1b8ed96490c8f082644861760be
+msgid "Place the node in maintenance mode."
+msgstr ""
+
+#: ../../administration_guide.rst:329
+# 742504a2363043eda29d9583a580bbba
+msgid "For KVM, stop the cloud-agent service."
+msgstr ""
+
+#: ../../administration_guide.rst:330
+# 25e529a1ed534077b4554684f796e60a
+msgid "Use the UI option to remove the node."
+msgstr ""
+
+#: ../../administration_guide.rst:331
+# 3748d1e9df464087a1ffe1ff96240883
+msgid "Then you may power down the Host, re-use its IP address, re-install it, etc"
+msgstr ""
+
+#: ../../administration_guide.rst:334
+# 89d630d304df4b6da185b6f8838b61b9
+msgid "Removing vSphere Hosts"
+msgstr ""
+
+#: ../../administration_guide.rst:335
+# 1219da8f0bd7440190e8d553858df5f4
+msgid "To remove this type of host, first place it in maintenance mode, as described above. Then use CloudStack to remove the host. CloudStack will not direct commands to a host that has been removed using CloudStack. However, the host may still exist in the vCenter cluster."
+msgstr ""
+
+#: ../../administration_guide.rst:338
+# a0f69abb2cf4444c99110f98389cafc3
+msgid "Changing hypervisor host password"
+msgstr ""
+
+#: ../../administration_guide.rst:339
+# f2496529c2a74ac4bc7b4b7c41a8871c
+msgid "The password for a XenServer Node, KVM Node, or vSphere Node may be changed in the database. Note that all Nodes in a Cluster must have the same password. To change a hosts password:"
+msgstr ""
+
+#: ../../administration_guide.rst:342
+# 52f8f40fb2b042d395ff895d8275629a
+msgid "Identify all hosts in the cluster."
+msgstr ""
+
+#: ../../administration_guide.rst:343
+# ebc1674d6b164834ab5680e033835ee3
+msgid "Change the password on all hosts in the cluster. Now the password for the host and the password known to CloudStack will not match. Operations on the cluster will fail until the two passwords match."
+msgstr ""
+
+#: ../../administration_guide.rst:344
+# 5364fca0ca7e4a3c918da14795d570eb
+msgid "Get the list of host IDs for the host in the cluster where you are changing the password. You will need to access the database to determine these host IDs. For each hostname \"h\" (or vSphere cluster) that you are changing the password for, execute: ::"
+msgstr ""
+
+#: ../../administration_guide.rst:346
+# 5f9a5267e03246a0b8a4fe18c602cb11
+msgid "mysql> select id from cloud.host where name like '%h%';"
+msgstr ""
+
+#: ../../administration_guide.rst:348
+# 4d1c5ebe23a94d6d91adabbb787b83c9
+msgid "Update the passwords for the host in the database. In this example, we change the passwords for hosts with IDs 5, 10, and 12 to \"password\".::"
+msgstr ""
+
+#: ../../administration_guide.rst:350
+# 44c4b8a1b4874a33885b01d27e877d63
+msgid "mysql> update cloud.host set password='password' where id=5 or id=10 or id=12;"
+msgstr ""
+
+#: ../../administration_guide.rst:353
+# e80d3d60b8b24290920db5afafb13f4c
+msgid "Overprovisioning and Service Offering Limits"
+msgstr ""
+
+#: ../../administration_guide.rst:355
+# 1883429edbe74fdd8a5fb620aec5fdb6
+msgid "CPU and memory (RAM) over-provisioning factors can be set for each cluster to change the number of VMs that can run on each host in the cluster. This helps optimize the use of resources. By increasing the over-provisioning ratio, more resource capacity will be used. If the ratio is set to 1, no over-provisioning is done."
+msgstr ""
+
+#: ../../administration_guide.rst:357
+# 37b343a408374b90a7a4000a86cf66c1
+msgid "The administrator can also set global default over-provisioning ratios in the cpu.overprovisioning.factor and mem.overprovisioning.factor global configuration variables. The default value of these variables is 1: over-provisioning is turned off by default. Over-provisioning ratios are dynamically substituted in CloudStack's capacity calculations. For example:::"
+msgstr ""
+
+#: ../../administration_guide.rst:367
+# 10a7f91d1b664361837ca349ac15d8fe
+msgid "The administrator can specify a memory over-provisioning ratio, and can specify both CPU and memory over-provisioning ratios on a per-cluster basis. In any given cloud, the optimum number of VMs for each host is affected by such things as the hypervisor, storage, and hardware configuration. These may be different for each cluster in the same cloud. A single global over-provisioning setting can not provide the best utilization for all the different clusters in the cloud. It has to be set for the lowest common denominator. The per-cluster setting provides a finer granularity for better utilization of resources, no matter where the CloudStack placement algorithm decides to place a VM."
+msgstr ""
+
+#: ../../administration_guide.rst:370
+# b0413938593f4a7786b951b21e507d09
+msgid "The overprovisioning settings can be used along with dedicated resources (assigning a specific cluster to an account) to effectively offer different levels of service to different accounts. For example, an account paying for a more expensive level of service could be assigned to a dedicated cluster with an over-provisioning ratio of 1, and a lower-paying account to a cluster with a ratio of 2."
+msgstr ""
+
+#: ../../administration_guide.rst:372
+# 1aaa3fd0e30b4b059a45d437ea210c2e
+msgid "When a new host is added to a cluster, CloudStack will assume the host has the capability to perform the CPU and RAM over-provisioning which is configured for that cluster. It is up to the administrator to be sure the host is actually suitable for the level of over-provisioning which has been set."
+msgstr ""
+
+#: ../../administration_guide.rst:375
+# 69e7d2a62c294b1387f1bc52a47e9a2a
+msgid "Limitations on over-provisioning in KVM and XenServer"
+msgstr ""
+
+#: ../../administration_guide.rst:377
+# d0da750d0eac48eca9e90d923eebab99
+msgid "In XenServer, due to a constraint of this hypervisor, you can not use an over-provisioning factor greater than 4."
+msgstr ""
+
+#: ../../administration_guide.rst:379
+# cb6f018a43e24fea81857c044855d950
+msgid "KVM can not manage memory allocation to VMs dynamically. CloudStack sets the minimum and maximum amount of memory that a VM can use. The hypervisor adjusts the memory within the set limits based on the memory contention."
+msgstr ""
+
+#: ../../administration_guide.rst:382
+# fe616dbc701e4b61a912343f7be00b58
+msgid "Requirements for Over-Provisioning"
+msgstr ""
+
+#: ../../administration_guide.rst:384
+# 445d78119e204479b74e8418f43a6d37
+msgid "Several prerequisites are required in order for over-provisioning to function properly. The feature is dependent on the OS type, hypervisor capabilities, and certain scripts. It is the administrator's responsibility to ensure that these requirements are met."
+msgstr ""
+
+#: ../../administration_guide.rst:387
+# 0ffbd97c59c2417e8a097daf7b7d19c5
+msgid "Balloon Driver"
+msgstr ""
+
+#: ../../administration_guide.rst:389
+# 499993d9952a44ec935372610be1ba69
+msgid "All VMs should have a balloon driver installed in them. The hypervisor communicates with the balloon driver to free up and make the memory available to a VM."
+msgstr ""
+
+#: ../../administration_guide.rst:392
+#: ../../administration_guide.rst:412
+# 4b2a1ef88e894648b0ee154892e11076
+# 631a9ce321b249d8b30164201011194f
+msgid "XenServer"
+msgstr ""
+
+#: ../../administration_guide.rst:394
+# e5a221eef356494a85f9ff179af25612
+msgid "The balloon driver can be found as a part of xen pv or PVHVM drivers. The xen pvhvm drivers are included in upstream linux kernels 2.6.36+."
+msgstr ""
+
+#: ../../administration_guide.rst:397
+# 2e279386f6e64c04b48f7683628a149e
+msgid "VMware"
+msgstr ""
+
+#: ../../administration_guide.rst:399
+# 90e5b561b31e44a6b8d4ab785d75cfc2
+msgid "The balloon driver can be found as a part of the VMware tools. All the VMs that are deployed in a over-provisioned cluster should have the VMware tools installed."
+msgstr ""
+
+#: ../../administration_guide.rst:402
+# 17b7036f18dc4a279cbd09dc97d887b6
+msgid "KVM"
+msgstr ""
+
+#: ../../administration_guide.rst:404
+# 90644866fa4f42ba8eb2772327104c08
+msgid "All VMs are required to support the virtio drivers. These drivers are installed in all Linux kernel versions 2.6.25 and greater. The administrator must set CONFIG_VIRTIO_BALLOON=y in the virtio configuration."
+msgstr ""
+
+#: ../../administration_guide.rst:407
+# fb51035c29d44f61a1cd1ca69db4f08c
+msgid "Hypervisor capabilities"
+msgstr ""
+
+#: ../../administration_guide.rst:409
+# 3dc6760bd76a49fb82e221c82c02a49a
+msgid "The hypervisor must be capable of using the memory ballooning."
+msgstr ""
+
+#: ../../administration_guide.rst:414
+# a2c2cbb7fc304f1eaedc4f80bc0080a7
+msgid "The DMC (Dynamic Memory Control) capability of the hypervisor should be enabled. Only XenServer Advanced and above versions have this feature."
+msgstr ""
+
+#: ../../administration_guide.rst:417
+# 69e523e5c1a54ce6b70499c8e815d2df
+msgid "VMware, KVM"
+msgstr ""
+
+#: ../../administration_guide.rst:419
+# 4b9a57bcf0c44c0881b43f78263e659a
+msgid "Memory ballooning is supported by default."
+msgstr ""
+
+#: ../../administration_guide.rst:422
+# 842b46aac75e4b55bc95a2884df153b1
+msgid "Setting Over-Provisioning Rations"
+msgstr ""
+
+#: ../../administration_guide.rst:424
+# 8d093dbea4db42028ab4bf0469d67452
+msgid "There are two ways the root admin can set CPU and RAM over-provisioning ratios. First, the global configuration settings cpu.overprovisioning.factor and mem.overprovisioning.factor will be applied when a new cluster is created. Later, the ratios can be modified for an existing cluster."
+msgstr ""
+
+#: ../../administration_guide.rst:426
+# d585ebbb38104db185a30519f122ef38
+msgid "Only VMs deployed after the change are affected by the new setting. If you want VMs deployed before the change to adopt the new over-provisioning ratio, you must stop and restart the VMs. When this is done, CloudStack recalculates or scales the used and reserved capacities based on the new over-provisioning ratios, to ensure that CloudStack is correctly tracking the amount of free capacity."
+msgstr ""
+
+#: ../../administration_guide.rst:428
+# b3bf39b26142443c92ac98f1aa4e7be4
+msgid "To change the over-provisioning ratios for an existing cluster:"
+msgstr ""
+
+#: ../../administration_guide.rst:430
+# 95630036ec0e4f9ba1f10054990ba84d
+msgid "Log in as administrator to the CloudStack UI."
+msgstr ""
+
+#: ../../administration_guide.rst:432
+# a64dd51e12c547658db1ade7de98ebd2
+msgid "Under Clusters, click View All."
+msgstr ""
+
+#: ../../administration_guide.rst:433
+# 23c09f71b4e04bad89d9fc8af656468c
+msgid "Select the cluster you want to work with, and click the Edit button."
+msgstr ""
+
+#: ../../administration_guide.rst:434
+# 0e804d9f17db4c8a981a54fd41556317
+msgid "Fill in your desired over-provisioning multipliers in the fields CPU overcommit ratio and RAM overcommit ratio. The value which is intially shown in these fields is the default value inherited from the global configuration settings."
+msgstr ""
+
+#: ../../administration_guide.rst:437
+# c2d182c3388a4abda55289726d7ffcd7
+msgid "Service Offering Limits and Over-Provisioning"
+msgstr ""
+
+#: ../../administration_guide.rst:439
+# 35ebc55bb645476192b0b7676f94c260
+msgid "Service offering limits (e.g. 1 GHz, 1 core) are strictly enforced for core count. For example, a guest with a service offering of one core will have only one core available to it regardless of other activity on the Host."
+msgstr ""
+
+#: ../../administration_guide.rst:441
+# 35b941c26c5e4016b305ed1742023a82
+msgid "Service offering limits for gigahertz are enforced only in the presence of contention for CPU resources. For example, suppose that a guest was created with a service offering of 1 GHz on a Host that has 2 GHz cores, and that guest is the only guest running on the Host. The guest will have the full 2 GHz available to it. When multiple guests are attempting to use the CPU a weighting factor is used to schedule CPU resources. The weight is based on the clock speed in the service offering. Guests receive a CPU allocation that is proportionate to the GHz in the service offering. For example, a guest created from a 2 GHz service offering will receive twice the CPU allocation as a guest created from a 1 GHz service offering. CloudStack does not perform memory over-provisioning."
+msgstr ""
+

http://git-wip-us.apache.org/repos/asf/cloudstack-docs/blob/7d6892fd/rtd/source/locale/pot/alloc.pot
----------------------------------------------------------------------
diff --git a/rtd/source/locale/pot/alloc.pot b/rtd/source/locale/pot/alloc.pot
new file mode 100644
index 0000000..749cb05
--- /dev/null
+++ b/rtd/source/locale/pot/alloc.pot
@@ -0,0 +1,409 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2014, Apache CloudStack
+# This file is distributed under the same license as the Apache CloudStack package.
+# FIRST AUTHOR <EM...@ADDRESS>, YEAR.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: Apache CloudStack 4.3\n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2014-03-31 13:49-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"
+
+#: ../../alloc.rst:2
+# b24b21f06cc04967a756901f0d0e77cb
+msgid "Allocators"
+msgstr ""
+
+#: ../../alloc.rst:4
+# 89923eb3bf724b2e92cc7759fbd32e24
+msgid "CloudStack enables administrators to write custom allocators that will choose the Host to place a new guest and the storage host from which to allocate guest virtual disk images."
+msgstr ""
+
+#: ../../alloc.rst:8
+# adab67c72cee443ea0a9fd7a032019e1
+msgid "These are following categories of allocators currently supported:"
+msgstr ""
+
+#: ../../alloc.rst:10
+# 4cdc118725374ee9ba93e57fa19bd227
+msgid "HostAllocators - Allows you to create custom rules to determine which physical host to allocate the guest virtual machines on."
+msgstr ""
+
+#: ../../alloc.rst:13
+# 44ca87f9ea7b4395b5a77aba97b5f8dc
+msgid "StoragePoolAllocators - Allows you to create custom rules to determine which storage pool to allocate the guest virtual machines on."
+msgstr ""
+
+#: ../../alloc.rst:18
+# 6c45cb067c19470da4aeb3e1a20e7e6b
+msgid "Implementing a custom HostAllocator"
+msgstr ""
+
+#: ../../alloc.rst:20
+# 0b22e37a87484153896f253084682a27
+msgid "HostAllocators are written by extending com.cloud.agent.manager.allocator.HostAllocator interface."
+msgstr ""
+
+#: ../../alloc.rst:24
+# 9d13e0b0954e44ffb4460f1f6e76ce3b
+msgid "HostAllocator Interface"
+msgstr ""
+
+#: ../../alloc.rst:26
+# ebabcdc234ab4c7bbf51975a632bea1d
+msgid "The interface defines the following two methods."
+msgstr ""
+
+#: ../../alloc.rst:53
+# b7e66f063c6f489a811321cfc2adbe49
+msgid "A custom HostAllocator can be written by implementing the ‘allocateTo’ method"
+msgstr ""
+
+#: ../../alloc.rst:57
+# 8e50e53c1b264c018cacc95a7a595be9
+msgid "Input Parameters for the method ‘HostAllocator :: allocateTo’"
+msgstr ""
+
+#: ../../alloc.rst:59
+#: ../../alloc.rst:205
+# 101cff90e33d45349e556f5acb90097d
+# f7743f3c0bab4b85a9a542e74fb0fc79
+msgid "*com.cloud.vm.VirtualMachineProfile vmProfile*"
+msgstr ""
+
+#: ../../alloc.rst:61
+#: ../../alloc.rst:207
+# 500f68497c304bb398a46d0f2c71cb82
+# a93dfc81e89e40049463bcf61823d254
+msgid "VirtualMachineProfile describes one virtual machine. This allows the adapters like Allocators to process the information in the virtual machine and make determinations on what the virtual machine profile should look like before it is actually started on the hypervisor."
+msgstr ""
+
+#: ../../alloc.rst:66
+# 7bb65f8cf85c40249c4c86e4013ebb08
+msgid "HostAllocators can make use of the following information present in the VirtualMachineProfile:"
+msgstr ""
+
+#: ../../alloc.rst:69
+# ab33f4550b4b4f5398dae9ff967613e7
+msgid "The ServiceOffering that specifies configuration like requested CPU speed, RAM etc necessary for the guest VM."
+msgstr ""
+
+#: ../../alloc.rst:72
+#: ../../alloc.rst:218
+# 8a58c120af2d48a5891cbebf324799a1
+# 66bd396fb4e04a1d87abd92a050c6ea1
+msgid "The VirtualMachineTemplate, the template to be used to start the VM."
+msgstr ""
+
+#: ../../alloc.rst:74
+#: ../../alloc.rst:220
+# 00608807ab6f46499f2a0479d4c9f5ec
+# 6431648fde024c25b24826374f86a887
+msgid "*com.cloud.deploy.DeploymentPlan plan*"
+msgstr ""
+
+#: ../../alloc.rst:76
+#: ../../alloc.rst:222
+# e5dd1566033a4a7cbdbe5e874416dbac
+# 6e2d9db891cc4a9e9840ceb384aaa5f0
+msgid "DeploymentPlan should specify:"
+msgstr ""
+
+#: ../../alloc.rst:78
+#: ../../alloc.rst:224
+# 7516a5bc7a9a4162a650275c5cd52a60
+# 7bcc7157b86045ebb6ecb62127995eeb
+msgid "dataCenterId: The data center the VM should deploy in"
+msgstr ""
+
+#: ../../alloc.rst:80
+# 9acd60a116b94beea25811ec07007a22
+msgid "podId: The pod the Vm should deploy in; null if no preference"
+msgstr ""
+
+#: ../../alloc.rst:82
+#: ../../alloc.rst:228
+# 81ba4443812c44e7ae390dde322cd2f0
+# f8ef1a4988214cbd84faa3bd3c7bb4d8
+msgid "clusterId: The cluster the VM should deploy in; null if no preference"
+msgstr ""
+
+#: ../../alloc.rst:84
+#: ../../alloc.rst:230
+# 1e9ad629bf7546baa1ef733ff7649794
+# 7d31ebe319f04eae8fc914f0d9b15dfd
+msgid "poolId: The storage pool the VM should be created in; null if no preference"
+msgstr ""
+
+#: ../../alloc.rst:87
+# a56db2027fc14fe8851adbb0d20f4bb3
+msgid "*com.cloud.host.Host.Type type*"
+msgstr ""
+
+#: ../../alloc.rst:89
+# 117330d5149346e893940824a7cc0f13
+msgid "Type of the Host needed for this guest VM. Currently com.cloud.host.Host.Type interface defines the following Host types:"
+msgstr ""
+
+#: ../../alloc.rst:92
+# f4c862266e0748c3b82a54cc3cf4e11b
+msgid "Storage"
+msgstr ""
+
+#: ../../alloc.rst:94
+# 5e8cacd550d34cbf9f4a2331d9047508
+msgid "Routing"
+msgstr ""
+
+#: ../../alloc.rst:96
+# c2c7fa103b0d42d9a048b9ba94539d7e
+msgid "SecondaryStorage"
+msgstr ""
+
+#: ../../alloc.rst:98
+# 7039d6864f4641c88b963761815441d9
+msgid "ConsoleProxy"
+msgstr ""
+
+#: ../../alloc.rst:100
+# 188966fdb5ea4866b645a73c1f46203e
+msgid "ExternalFirewall"
+msgstr ""
+
+#: ../../alloc.rst:102
+# 886ce574c22f470b86d2e2dabc4dedf8
+msgid "ExternalLoadBalancer"
+msgstr ""
+
+#: ../../alloc.rst:104
+#: ../../alloc.rst:233
+# 98d8618b11f4418394a49756ee34f0d1
+# 73004922ca734363a23b1828058ada96
+msgid "*com.cloud.deploy.DeploymentPlanner.ExcludeList avoid*"
+msgstr ""
+
+#: ../../alloc.rst:106
+# 3e92b2a746b94fe28d77bcf0dc7cd07d
+msgid "The ExcludeList specifies what datacenters, pods, clusters, hosts, storagePools should not be considered for allocating this guest VM. HostAllocators should avoid the hosts that are mentioned in ExcludeList.hostIds."
+msgstr ""
+
+#: ../../alloc.rst:111
+#: ../../alloc.rst:240
+# 448bc6d6adae4fdcb730025e56873627
+# 40756f9187a944b2b7d94c9d1382494f
+msgid "Set Long dcIds;"
+msgstr ""
+
+#: ../../alloc.rst:113
+#: ../../alloc.rst:242
+# d2504f426a0049d0ace9b214c6bd7953
+# 6140ffc617dc4a2985bfb74a278d41b9
+msgid "Set Long podIds;"
+msgstr ""
+
+#: ../../alloc.rst:115
+#: ../../alloc.rst:244
+# 8aa146a476c7463595b14b96873a20e3
+# 86deaf0d209249dfa759b338c46ac0be
+msgid "Set Long clusterIds;"
+msgstr ""
+
+#: ../../alloc.rst:117
+#: ../../alloc.rst:246
+# 9fdc441f089941d5943c1136f1b86e2a
+# 610a66aed6e64b46be125b1294931664
+msgid "Set Long hostIds;"
+msgstr ""
+
+#: ../../alloc.rst:119
+#: ../../alloc.rst:248
+# b5399df37cd7423883f64b670d07cf47
+# ebe7497409b8407a9fee2cd3565ba6db
+msgid "Set Long poolIds;"
+msgstr ""
+
+#: ../../alloc.rst:121
+#: ../../alloc.rst:250
+# 4d44cc93626b4131bb652953a2560628
+# ea297796ac634038b897f044d98d9bad
+msgid "*int returnUpTo*"
+msgstr ""
+
+#: ../../alloc.rst:123
+# 4afa7f5bef3c4ae583c38ffb62a765f9
+msgid "This specifies return up to that many available hosts for this guest VM."
+msgstr ""
+
+#: ../../alloc.rst:125
+# eab39d31cb4247efb1538ccb5bf6c7ba
+msgid "To get all possible hosts, set this value to -1."
+msgstr ""
+
+#: ../../alloc.rst:128
+# 3224e4b69b424d29ba834cc170599b1e
+msgid "Reference HostAllocator implementation"
+msgstr ""
+
+#: ../../alloc.rst:130
+# 44a1d6e9f79d426b9d3fc47dac17f086
+msgid "Refer com.cloud.agent.manager.allocator.impl.FirstFitAllocator that implements the HostAllocator interface. This allocator checks available hosts in the specified datacenter, Pod, Cluster and considering the given ServiceOffering requirements."
+msgstr ""
+
+#: ../../alloc.rst:135
+# 5562696f2a6e4158b2317f8674a65764
+msgid "If returnUpTo = 1, this allocator would return the first Host that fits the requirements of the guest VM."
+msgstr ""
+
+#: ../../alloc.rst:139
+# 354cd895a9f1419f951f2d2dbb480147
+msgid "Loading a custom HostAllocator"
+msgstr ""
+
+#: ../../alloc.rst:141
+# 54e588e1b5a242c79a961cf83b931c9a
+msgid "Write a custom HostAllocator class, implementing the interface described above."
+msgstr ""
+
+#: ../../alloc.rst:144
+#: ../../alloc.rst:273
+# f9c0a0a8e19b463ead48dd0f181efe00
+# 25506beab7514a94b9a14938e4a568bf
+msgid "Package the code into a JAR file and make the JAR available in the classpath of the Management Server/tomcat."
+msgstr ""
+
+#: ../../alloc.rst:147
+#: ../../alloc.rst:276
+# 4af2d8a69dee48cd8a7c3ccfbac5631c
+# 928c5259176f4c829c12d2c3e07b307b
+msgid "Modify the components.xml and components-premium.xml files found in /client/ tomcatconf as follows."
+msgstr ""
+
+#: ../../alloc.rst:150
+# 840bb1bb0bab49d3a0ac320ed3041f64
+msgid "Search for ‘HostAllocator’ in these files."
+msgstr ""
+
+#: ../../alloc.rst:159
+# c835db1603ac49fbadd6d4e7d60dbad8
+msgid "Replace the FirstFitAllocator with your class name. Optionally, you can change the name of the adapter as well."
+msgstr ""
+
+#: ../../alloc.rst:162
+#: ../../alloc.rst:290
+# 85c3d7ba304941cfa509a7b52f2bd205
+# f95ca1d23efe456ab39d2e725a2036a0
+msgid "Restart the Management Server."
+msgstr ""
+
+#: ../../alloc.rst:165
+# 15bff855293d4273b95a3b617b5df378
+msgid "Implementing a custom StoragePoolAllocator"
+msgstr ""
+
+#: ../../alloc.rst:167
+# 73bf3330eb4f417ab2560cc855d3cc6d
+msgid "StoragePoolAllocators are written by extending com.cloud.storage.allocator. StoragePoolAllocator interface."
+msgstr ""
+
+#: ../../alloc.rst:171
+# a94ec7aeb9984f75b53356320e64d512
+msgid "StoragePoolAllocator Interface"
+msgstr ""
+
+#: ../../alloc.rst:173
+# 95dffe7e76f944b09ba93c62a7e293f1
+msgid "A custom StoragePoolAllocator can be written by implementing the ‘allocateTo’ method."
+msgstr ""
+
+#: ../../alloc.rst:191
+# 5d8387e6a7894494aeca6ddeb48b53ff
+msgid "This interface also contains some other methods to support some legacy code. However your custom allocator can extend the existing com.cloud.storage.allocator. AbstractStoragePoolAllocator. This class provides default implementation for all the other interface methods."
+msgstr ""
+
+#: ../../alloc.rst:197
+# 34b5c706a80b43819ad96e48f36ec5d4
+msgid "Input Parameters for the method ‘StoragePoolAllocator :: allocateTo’"
+msgstr ""
+
+#: ../../alloc.rst:199
+# b3487e08c96843719a022eb9c673d711
+msgid "*com.cloud.vm.DiskProfile dskCh*"
+msgstr ""
+
+#: ../../alloc.rst:201
+# aba86c4ec9ec4269b17b4b00cfe428a6
+msgid "DiskCharacteristics describes a disk and what functionality is required from it. It specifies the storage pool tags if any to be used while searching for a storage pool."
+msgstr ""
+
+#: ../../alloc.rst:212
+# e09f9104505143559febc21f3b4a8d3b
+msgid "StoragePoolAllocators can make use of the following information present in the VirtualMachineProfile:"
+msgstr ""
+
+#: ../../alloc.rst:215
+# 456e11be56f04f1a8fe2f16c00df57f8
+msgid "The VirtualMachine instance that specifies properties of the guest VM."
+msgstr ""
+
+#: ../../alloc.rst:226
+# 76cafb6cdcd649f78d4f82df21085297
+msgid "podId: The pod the VM should deploy in; null if no preference"
+msgstr ""
+
+#: ../../alloc.rst:235
+# 7c73dbba2b6440949b2b97677bb271cc
+msgid "The ExcludeList specifies what datacenters, pods, clusters, hosts, storagePools should not be considered for allocating this guest VM. StoragePoolAllocators should avoid the pools that are mentioned in ExcludeList.poolIds"
+msgstr ""
+
+#: ../../alloc.rst:252
+# 21093c1b8fb642689c24b0232e85c441
+msgid "This specifies return up to that many available pools for this guest VM"
+msgstr ""
+
+#: ../../alloc.rst:254
+# 12487cb7610942068f5cec67e00e73dd
+msgid "To get all possible pools, set this value to -1"
+msgstr ""
+
+#: ../../alloc.rst:257
+# 88ed7f8e81914e3681b4391f15d60939
+msgid "Reference StoragePoolAllocator implementation"
+msgstr ""
+
+#: ../../alloc.rst:259
+# 3808521ba2eb425db2239e0fe1d0789b
+msgid "Refer com.cloud.storage.allocator.FirstFitStoragePoolAllocator that implements the StoragePoolAllocator interface. This allocator checks available pools in the specified datacenter, Pod, Cluster and considering the given DiskProfile characteristics."
+msgstr ""
+
+#: ../../alloc.rst:264
+# f50dfc1dbce44eddbe27be2f26df3ac7
+msgid "If returnUpTo = 1, this allocator would return the first Storage Pool that fits the requirements of the guest VM."
+msgstr ""
+
+#: ../../alloc.rst:268
+# 9c246f19fb0f49918c77cf5f2b5d6119
+msgid "Loading a custom StoragePoolAllocator"
+msgstr ""
+
+#: ../../alloc.rst:270
+# 5fc036623a834bd792b5e222c530c9fb
+msgid "Write a custom StoragePoolAllocator class, implementing the interface described above."
+msgstr ""
+
+#: ../../alloc.rst:279
+# f74bddd68a3b40169de9e67da02f8edc
+msgid "Search for ‘StoragePoolAllocator’ in these files."
+msgstr ""
+
+#: ../../alloc.rst:287
+# 33990be5d35e4bcb83bf38a712d31e58
+msgid "Replace the FirstFitStoragePoolAllocator with your class name. Optionally, you can change the name of the adapter as well."
+msgstr ""
+

http://git-wip-us.apache.org/repos/asf/cloudstack-docs/blob/7d6892fd/rtd/source/locale/pot/ansible.pot
----------------------------------------------------------------------
diff --git a/rtd/source/locale/pot/ansible.pot b/rtd/source/locale/pot/ansible.pot
new file mode 100644
index 0000000..0ea3a7e
--- /dev/null
+++ b/rtd/source/locale/pot/ansible.pot
@@ -0,0 +1,383 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2014, Apache CloudStack
+# This file is distributed under the same license as the Apache CloudStack package.
+# FIRST AUTHOR <EM...@ADDRESS>, YEAR.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: Apache CloudStack 4.3\n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2014-03-31 13:49-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"
+
+#: ../../ansible.rst:2
+# 1859d2f68f21412b8db2824edfae907f
+msgid "Deploying CloudStack with Ansible"
+msgstr ""
+
+#: ../../ansible.rst:4
+# 6e30eb00e6aa452eb537f0340f2f7556
+msgid "In this article, `Paul Angus <https://twitter.com/CloudyAngus>`__ Cloud Architect at ShapeBlue takes a look at using Ansible to Deploy an Apache CloudStack cloud."
+msgstr ""
+
+#: ../../ansible.rst:9
+# 17351fc3621b4e56afb679f57b7eb2fc
+msgid "What is Ansible"
+msgstr ""
+
+#: ../../ansible.rst:11
+# e0cbed0b5b6f4f81ac4a47ef3b9fcbec
+msgid "Ansible is a deployment and configuration management tool similar in intent to Chef and Puppet. It allows (usually) DevOps teams to orchestrate the deployment and configuration of their environments without having to re-write custom scripts to make changes."
+msgstr ""
+
+#: ../../ansible.rst:16
+# 9ac502daf71441a5add7f1779cb19b62
+msgid "Like Chef and Puppet, Ansible is designed to be idempotent, these means that you determine the state you want a host to be in and Ansible will decide if it needs to act in order to achieve that state."
+msgstr ""
+
+#: ../../ansible.rst:21
+# 91a4a9ec711e4564a704919e51ad288a
+msgid "There’s already Chef and Puppet, so what’s the fuss about Ansible?"
+msgstr ""
+
+#: ../../ansible.rst:23
+# 85246b43e8e4405b97abc46c4c48ad1c
+msgid "Let’s take it as a given that configuration management makes life much easier (and is quite cool), Ansible only needs an SSH connection to the hosts that you’re going to manage to get started. While Ansible requires Python 2.4 or greater to on the host you’re going to manage in order to leverage the vast majority of its functionality, it is able to connect to hosts which don’t have Python installed in order to then install Python, so it’s not really a problem. This greatly simplifies the deployment procedure for hosts, avoiding the need to pre-install agents onto the clients before the configuration management can take over."
+msgstr ""
+
+#: ../../ansible.rst:33
+# f9c8d470e48a46a3bf54200afc699d6d
+msgid "Ansible will allow you to connect as any user to a managed host (with that user’s privileges) or by using public/private keys – allowing fully automated management."
+msgstr ""
+
+#: ../../ansible.rst:37
+# e4cd5c2b100b42f287d4ff22be7e0154
+msgid "There also doesn’t need to be a central server to run everything, as long as your playbooks and inventories are in-sync you can create as many Ansible servers as you need (generally a bit of Git pushing and pulling will do the trick)."
+msgstr ""
+
+#: ../../ansible.rst:42
+# e0edcb5a78fb43e69bef735a58ee8659
+msgid "Finally – its structure and language is pretty simple and clean. I’ve found it a bit tricky to get the syntax correct for variables in some circumstances, but otherwise I’ve found it one of the easier tools to get my head around."
+msgstr ""
+
+#: ../../ansible.rst:48
+# f7e6bae4e21c4e209fc35954999298f2
+msgid "So let’s see something"
+msgstr ""
+
+#: ../../ansible.rst:50
+# 8ab9c7fec0dc4be49ad4e125357f4d7a
+msgid "For this example we’re going to create an Ansible server which will then deploy a CloudStack server. Both of these servers will be CentOS 6.4 virtual machines."
+msgstr ""
+
+#: ../../ansible.rst:55
+# 5f0e94b7659b4d409b333b789158e84e
+msgid "Installing Ansible"
+msgstr ""
+
+#: ../../ansible.rst:57
+# 915043a5d8904bb7aa64f2dde8a92391
+msgid "Installing Ansible is blessedly easy. We generally prefer to use CentOS so to install Ansible you run the following commands on the Ansible server."
+msgstr ""
+
+#: ../../ansible.rst:66
+# 36f217057d324ed58620a8813c3eabef
+msgid "And that’s it."
+msgstr ""
+
+#: ../../ansible.rst:68
+# cf61954055d44444975ccf8a7a78a916
+msgid "*(There is a commercial version which has more features such as callback to request configurations and a RESTful API and also support. The installation of this is different)*"
+msgstr ""
+
+#: ../../ansible.rst:72
+# 9363f0968af64b6aa46bb5905cf4251a
+msgid "By default Ansible uses /etc/ansible to store your playbooks, I tend to move it, but there’s no real problem with using the default location. Create yourself a little directory structure to get started with. The documentation recommends something like this:"
+msgstr ""
+
+#: ../../ansible.rst:79
+# 9868b1e2ebd24ceab9858c7787e9ccba
+msgid "Playbooks"
+msgstr ""
+
+#: ../../ansible.rst:81
+# 0d8e95c78ba84d22bf1b0ee3038508ea
+msgid "Ansible uses playbooks to specify the state in which you wish the target host to be in to be able to accomplish its role. Ansible playbooks are written in YAML format."
+msgstr ""
+
+#: ../../ansible.rst:86
+# a1f7c79f3f724cdba81c303040553b5e
+msgid "Modules"
+msgstr ""
+
+#: ../../ansible.rst:88
+# 564296611bdb46e6a8bd0a38db4b8e01
+msgid "To get Ansible to do things you specify the hosts a playbook will act upon and then call modules and supply arguments which determine what Ansible will do to those hosts."
+msgstr ""
+
+#: ../../ansible.rst:92
+# ebb846fa6db14f94b4b7a4cc98607749
+msgid "To keep things simple, this example is a cut-down version of a full deployment. This example creates a single management server with a local MySQL server and assumes you have your secondary storage already provisioned somewhere. For this example I’m also not going to include securing the MySQL server, configuring NTP or using Ansible to configure the networking on the hosts either. Although normally we’d use Ansible to do exactly that."
+msgstr ""
+
+#: ../../ansible.rst:100
+# d040b1b00b08437fafc87fa3320b0e4a
+msgid "The pre-requisites to this CloudStack build are:"
+msgstr ""
+
+#: ../../ansible.rst:102
+# cce9101b609045a2b3f394516d45093e
+msgid "A CentOS 6.4 host to install CloudStack on"
+msgstr ""
+
+#: ../../ansible.rst:103
+# e207a3f7f037488ea1b6328c91e33806
+msgid "An IP address already assigned on the ACS management host"
+msgstr ""
+
+#: ../../ansible.rst:104
+# fe440835a2a74cf48eb7c18ea908839e
+msgid "The ACS management host should have a resolvable FQDN (either through DNS or the host file on the ACS management host)"
+msgstr ""
+
+#: ../../ansible.rst:106
+# 41450f1731f14a729024313ec6a710fe
+msgid "Internet connectivity on the ACS management host"
+msgstr ""
+
+#: ../../ansible.rst:109
+# b5ddaceb1e764f74b2813ea96969445c
+msgid "Planning"
+msgstr ""
+
+#: ../../ansible.rst:111
+# 013969c7e2b9492db82e2d33164297c4
+msgid "The first step I use is to list all of the tasks I think I’ll need and group them or split them into logical blocks. So for this deployment of CloudStack I’d start with:"
+msgstr ""
+
+#: ../../ansible.rst:115
+# dd9e1395ccef429988e3e88376d858e7
+msgid "Configure selinux"
+msgstr ""
+
+#: ../../ansible.rst:116
+# 99b8406503ab4f12aae62a87d020722b
+msgid "(libselinux-python required for Ansible to work with selinux enabled hosts)"
+msgstr ""
+
+#: ../../ansible.rst:118
+# db945f8d47d0492a9162d0b8c17b048c
+msgid "Install and configure MySQL"
+msgstr ""
+
+#: ../../ansible.rst:119
+# d53d2720f9634906b3db980400d04d91
+msgid "(Python MySQL-DB required for Ansible MySQL module)"
+msgstr ""
+
+#: ../../ansible.rst:120
+# 7d22acf5b782426c8bcf68228188559b
+msgid "Install cloud-client"
+msgstr ""
+
+#: ../../ansible.rst:121
+# e2bcdc7a20274f28a27eec8996498c23
+msgid "Seed secondary storage"
+msgstr ""
+
+#: ../../ansible.rst:123
+# be33c86aba4945c585fce7c88942d496
+msgid "Ansible is built around the idea of hosts having roles, so generally you would group or manage your hosts by their roles. So now to create some roles for these tasks"
+msgstr ""
+
+#: ../../ansible.rst:127
+# e13ff16771754ed485d9e2c92d16debc
+msgid "I’ve created:"
+msgstr ""
+
+#: ../../ansible.rst:129
+# 7935027693af496e861255a6bc772036
+msgid "cloudstack-manager"
+msgstr ""
+
+#: ../../ansible.rst:130
+# 99590b1bc4024a08b0c0f182dbc60ef8
+msgid "mysql"
+msgstr ""
+
+#: ../../ansible.rst:132
+# a18f24daf8924855a44a9d0e633c94fc
+msgid "First up we need to tell Ansible where to find our CloudStack management host. In the root Ansible directory there is a file called ‘hosts’ (/etc/Ansible/hosts) add a section like this:"
+msgstr ""
+
+#: ../../ansible.rst:141
+# 7b170fd6a43342619530fb0aeee059d2
+msgid "where xxx.xxx.xxx.xxx is the ip address of your ACS management host."
+msgstr ""
+
+#: ../../ansible.rst:144
+# 144ffdd76bc148f39f790ada64cd4fc0
+msgid "MySQL"
+msgstr ""
+
+#: ../../ansible.rst:146
+# d7a41e7d8b9744e385f2a53ad29f8fdd
+msgid "So let’s start with the MySQL server.  We’ll need to create a task within the mysql role directory called main.yml. The ‘task’ in this case to have MySQL running and configured on the target host. The contents of the file will look like this:"
+msgstr ""
+
+#: ../../ansible.rst:207
+# 26122051675049278058cecdb173238d
+msgid "This needs to be saved as `/etc/ansible/roles/mysql/tasks/main.yml`"
+msgstr ""
+
+#: ../../ansible.rst:209
+# b896847dc3d748e6813c7bad10be7b4b
+msgid "As explained earlier, this playbook in fact describes the state of the host rather than setting out commands to be run. For instance, we specify certain lines which must be in the my.cnf file and allow Ansible to decide whether or not it needs to add them."
+msgstr ""
+
+#: ../../ansible.rst:214
+# 09f9988a7cc441068987429418680739
+msgid "Most of the modules are self-explanatory once you see them, but to run through them briefly;"
+msgstr ""
+
+#: ../../ansible.rst:217
+# 5c1e4a497ed64e27ace8c66aa718abf8
+msgid "The ‘yum’ module is used to specify which packages are required, the ‘service’ module controls the running of services, while the ‘mysql\\_user’ module controls mysql user configuration. The ‘lineinfile’ module controls the contents in a file."
+msgstr ""
+
+#: ../../ansible.rst:222
+# f9b01f4c803e4686b8176db909562c4b
+msgid "We have a couple of variables which need declaring.  You could do that within this playbook or its ‘parent’ playbook, or as a higher level variable. I’m going to declare them in a higher level playbook. More on this later."
+msgstr ""
+
+#: ../../ansible.rst:227
+# b129bd6c3c1f4252acbf6e3ab39da0d8
+msgid "That’s enough to provision a MySQL server. Now for the management server."
+msgstr ""
+
+#: ../../ansible.rst:232
+# e2a69788c8914660a4e7ec5a1da788fc
+msgid "CloudStack Management server service"
+msgstr ""
+
+#: ../../ansible.rst:234
+# f86e9d9aed5f4b688eeab2232617abf4
+msgid "For the management server role we create a main.yml task like this:"
+msgstr ""
+
+#: ../../ansible.rst:268
+# 374da105e3c441a993c731bb823d37ef
+msgid "Save this as `/etc/ansible/roles/cloudstack-management/tasks/main.yml`"
+msgstr ""
+
+#: ../../ansible.rst:270
+# 81313977c7c34c23b2bee532e64d64b8
+msgid "Now we have some new elements to deal with. The Ansible template module uses Jinja2 based templating.  As we’re doing a simplified example here, the Jinja template for the cloudstack.repo won’t have any variables in it, so it would simply look like this:"
+msgstr ""
+
+#: ../../ansible.rst:283
+# 780fbe6357154bcf831d03abbffa1a0c
+msgid "This is saved in `/etc/ansible/roles/cloudstack-manager/templates/cloudstack.repo.j2`"
+msgstr ""
+
+#: ../../ansible.rst:285
+# 0e150c1a3bd147d783217e662e64a456
+msgid "That gives us the packages installed, we need to set up the database. To do this I’ve created a separate task called setupdb.yml"
+msgstr ""
+
+#: ../../ansible.rst:297
+# f140c48ee40e495bbf6e4f00451188a7
+msgid "Save this as: `/etc/ansible/roles/cloudstack-management/tasks/setupdb.yml`"
+msgstr ""
+
+#: ../../ansible.rst:299
+# ab0ad808c1b74a0da1d3701114d7d265
+msgid "As there isn’t (as yet) a CloudStack module, Ansible doesn’t inherently know whether or not the databases have already been provisioned, therefore this step is not currently idempotent and will overwrite any previously provisioned databases."
+msgstr ""
+
+#: ../../ansible.rst:304
+# 61bbd93955ed4ef680b0005e6fe4c4db
+msgid "There are some more variables here for us to declare later."
+msgstr ""
+
+#: ../../ansible.rst:308
+# 907d082c8f834643a0a0d47f85ed7853
+msgid "System VM Templates:"
+msgstr ""
+
+#: ../../ansible.rst:311
+# 892ba69b5c9e4077b755762af5b353c0
+msgid "Finally we would want to seed the system VM templates into the secondary storage.  The playbook for this would look as follows:"
+msgstr ""
+
+#: ../../ansible.rst:335
+# 245722e5625e41b3be3d67384dbd309b
+msgid "Save this as `/etc/ansible/roles/cloudstack-manager/tasks/seedstorage.yml`"
+msgstr ""
+
+#: ../../ansible.rst:337
+# b224369b3afb4d0ab4107842e7794d39
+msgid "Again, there isn’t a CloudStack module so Ansible will always run this even if the secondary storage already has the templates in it."
+msgstr ""
+
+#: ../../ansible.rst:342
+# 5ebfbb97903b40ba85dc1668a1618296
+msgid "Bringing it all together"
+msgstr ""
+
+#: ../../ansible.rst:344
+# c265f43e11a743239b94833df8f80ba4
+msgid "Ansible can use playbooks which run other playbooks, this allows us to group these playbooks together and declare variables across all of the individual playbooks. So in the Ansible playbook directory create a file called deploy-cloudstack.yml, which would look like this:"
+msgstr ""
+
+#: ../../ansible.rst:373
+# 5451f71073da4c428c19974c633cda87
+msgid "Save this as `/etc/ansible/deploy-cloudstack.yml`  inserting the IP address and path for your secondary storage and changing the passwords if you wish to."
+msgstr ""
+
+#: ../../ansible.rst:379
+# 51f57532edfe47a3bf340a6ef3ec8005
+msgid "To run this go to the Ansible directory (cd /etc/ansible ) and run:"
+msgstr ""
+
+#: ../../ansible.rst:385
+# 7f15fe37a51a461ebd1554bd3b9b606c
+msgid "‘-k’ tells Ansible to ask you for the root password to connect to the remote host."
+msgstr ""
+
+#: ../../ansible.rst:388
+# 0eb541457f53444395a4f37fcf63cbea
+msgid "Now log in to the CloudStack UI on the new management server."
+msgstr ""
+
+#: ../../ansible.rst:393
+# 7adf17b4cc68467c9cbc81ee862c3753
+msgid "How is this example different from a production deployment?"
+msgstr ""
+
+#: ../../ansible.rst:395
+# 55f1b360102642c992d5a63319701117
+msgid "In a production deployment, the Ansible playbooks would configure multiple management servers connected to master/slave replicating MySQL databases along with any other infrastructure components required and deploy and configure the hypervisor hosts. We would also have a dedicated file describing the hosts in the environment and a dedicated file containing variables which describe the environment."
+msgstr ""
+
+#: ../../ansible.rst:402
+# 9767e9a1a97c49f99bdbb781b67a14b4
+msgid "The advantage of using a configuration management tool such as Ansible is that we can specify components like the MySQL database VIP once and use it multiple times when configuring the MySQL server itself and other components which need to use that information."
+msgstr ""
+
+#: ../../ansible.rst:409
+# 95500bea3a42402b9097acfd1246c320
+msgid "Acknowledgements"
+msgstr ""
+
+#: ../../ansible.rst:411
+# b26a941e90e445beab8646793a36fe57
+msgid "Thanks to Shanker Balan for introducing me to Ansible and a load of handy hints along the way."
+msgstr ""
+

[2/6] setup i18n with transifex and sphinx-intl

[se...@apache.org]

http://git-wip-us.apache.org/repos/asf/cloudstack-docs/blob/7d6892fd/rtd/source/locale/pot/networking.pot
----------------------------------------------------------------------
diff --git a/rtd/source/locale/pot/networking.pot b/rtd/source/locale/pot/networking.pot
new file mode 100644
index 0000000..c27f11e
--- /dev/null
+++ b/rtd/source/locale/pot/networking.pot
@@ -0,0 +1,1940 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2014, Apache CloudStack
+# This file is distributed under the same license as the Apache CloudStack package.
+# FIRST AUTHOR <EM...@ADDRESS>, YEAR.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: Apache CloudStack 4.3\n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2014-03-31 13:49-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"
+
+#: ../../networking/autoscale_without_netscaler.rst:2
+# 6d7543ab9fc046888af483d6a88b3fea
+msgid "Configuring AutoScale without using NetScaler"
+msgstr ""
+
+#: ../../networking/autoscale_without_netscaler.rst:4
+# c9d0712245864f35982f232729bae189
+msgid "This feature is currently only available on the master branch and will be released in the 4.4 release."
+msgstr ""
+
+#: ../../networking/autoscale_without_netscaler.rst:7
+# c06b36bcc0e945ed8ec5e832340e956d
+msgid "What is AutoScaling?"
+msgstr ""
+
+#: ../../networking/autoscale_without_netscaler.rst:9
+# 9ef0e0f6d684458099daa4e2cbd8604b
+msgid "AutoScaling allows you to scale your back-end services or application VMs up or down seamlessly and automatically according to the conditions you define. With AutoScaling enabled, you can ensure that the number of VMs you are using seamlessly scale up when demand increases, and automatically decreases when demand subsides. Thus it helps you save compute costs by terminating underused VMs automatically and launching new VMs when you need them, without the need for manual intervention."
+msgstr ""
+
+#: ../../networking/autoscale_without_netscaler.rst:12
+# d507077958d348a6a693de6775bfe989
+msgid "Hypervisor support"
+msgstr ""
+
+#: ../../networking/autoscale_without_netscaler.rst:14
+# f9b069efcb974b079122d2c95723e601
+msgid "At that time, AutoScaling without NetScaler only supports for Xenserver. We are working to support KVM also."
+msgstr ""
+
+#: ../../networking/autoscale_without_netscaler.rst:17
+#: ../../networking/midonet.rst:46
+#: ../../networking/nicira-plugin.rst:54
+#: ../../networking/ovs-plugin.rst:51
+# d15bd6b6f1064d51bfaf9e80a5565e96
+# 642427380e4746dc891e7fc38b37579c
+# 7f80ef902c494483b24d6d578c1d80d6
+# e49601d54ace43859a71cb43a746b49c
+msgid "Prerequisites"
+msgstr ""
+
+#: ../../networking/autoscale_without_netscaler.rst:19
+# a3a685cf58fd4c9da4004b4f0ecfc871
+msgid "Before you configure an AutoScale rule, consider the following:"
+msgstr ""
+
+#: ../../networking/autoscale_without_netscaler.rst:21
+# f58b7e2821534230a2dd48d7c0439189
+msgid "Ensure that the necessary template is prepared before configuring AutoScale. Firstly you must install the PV-driver, which helps Xenserver collect performance parameters (CPU and memory) into VMs. Beside, When a VM is deployed by using a template and when it comes up, the application should be up and running."
+msgstr ""
+
+#: ../../networking/autoscale_without_netscaler.rst:24
+# bd06b9d81c444e9ebf31854526b8c67f
+msgid "Configuration"
+msgstr ""
+
+#: ../../networking/autoscale_without_netscaler.rst:26
+# f5b4b5fcd129488a826127aefa0a2c4a
+msgid "Specify the following:"
+msgstr ""
+
+#: ../../networking/autoscale_without_netscaler.rst:30
+# 12cb34f03c3d4ef8b03fbd8a70bacc25
+msgid "Template: A template consists of a base OS image and application. A template is used to provision the new instance of an application on a scaleup action. When a VM is deployed from a template, the VM can start taking the traffic from the load balancer without any admin intervention. For example, if the VM is deployed for a Web service, it should have the Web server running, the database connected, and so on."
+msgstr ""
+
+#: ../../networking/autoscale_without_netscaler.rst:32
+# 417240213f024697b69eceede3796359
+msgid "Compute offering: A predefined set of virtual hardware attributes, including CPU speed, number of CPUs, and RAM size, that the user can select when creating a new virtual machine instance. Choose one of the compute offerings to be used while provisioning a VM instance as part of scaleup action."
+msgstr ""
+
+#: ../../networking/autoscale_without_netscaler.rst:34
+# 4bcdcc4590a84f1385fa772041cea3cc
+msgid "Min Instance: The minimum number of active VM instances that is assigned to a load balancing rule. The active VM instances are the application instances that are up and serving the traffic, and are being load balanced. This parameter ensures that a load balancing rule has at least the configured number of active VM instances are available to serve the traffic."
+msgstr ""
+
+#: ../../networking/autoscale_without_netscaler.rst:36
+# d0c371a515394389bb7add6a02f00eb4
+msgid "Max Instance: Maximum number of active VM instances that should be assigned to a load balancing rule. This parameter defines the upper limit of active VM instances that can be assigned to a load balancing rule."
+msgstr ""
+
+#: ../../networking/autoscale_without_netscaler.rst:38
+# 80fcbe70099f4105a927b595228409e4
+msgid "Specifying a large value for the maximum instance parameter might result in provisioning large number of VM instances, which in turn leads to a single load balancing rule exhausting the VM instances limit specified at the account or domain level."
+msgstr ""
+
+#: ../../networking/autoscale_without_netscaler.rst:40
+# b8283e1247a741a988e15d29da160851
+msgid "Specify the following scale-up and scale-down policies:"
+msgstr ""
+
+#: ../../networking/autoscale_without_netscaler.rst:42
+# b2806defc678481a8198f37f837b7904
+msgid "Duration: The duration, in seconds, for which the conditions you specify must be true to trigger a scaleup action. The conditions defined should hold true for the entire duration you specify for an AutoScale action to be invoked."
+msgstr ""
+
+#: ../../networking/autoscale_without_netscaler.rst:44
+# 31426b6f769148b2bef529c22ca6553b
+msgid "Counter: The performance counters expose the state of the monitored instances. We added two new counter to work with that feature:"
+msgstr ""
+
+#: ../../networking/autoscale_without_netscaler.rst:46
+# 526679bfa9d3462180ab853fa20f8680
+msgid "Linux User CPU [native] - percentage"
+msgstr ""
+
+#: ../../networking/autoscale_without_netscaler.rst:47
+# bdb11da3ca3c45a082b4acc27901d16c
+msgid "Linux User RAM [native] - percentage"
+msgstr ""
+
+#: ../../networking/autoscale_without_netscaler.rst:49
+# a04a71965cb04316be4c79fdb9244b25
+msgid "Remember to choose one of them. If you choose anything else, the autoscaling will not work."
+msgstr ""
+
+#: ../../networking/autoscale_without_netscaler.rst:51
+# 966b02f38d1f4928b5c562133bf8a0fe
+msgid "Operator: The following five relational operators are supported in AutoScale feature: Greater than, Less than, Less than or equal to, Greater than or equal to, and Equal to."
+msgstr ""
+
+#: ../../networking/autoscale_without_netscaler.rst:53
+# 64b33fb24e6f4bf280e7d0137f7de18b
+msgid "Threshold: Threshold value to be used for the counter. Once the counter defined above breaches the threshold value, the AutoScale feature initiates a scaleup or scaledown action."
+msgstr ""
+
+#: ../../networking/autoscale_without_netscaler.rst:55
+# 80ff783a33004fb9b41f00e516ca4b5f
+msgid "Add: Click Add to add the condition."
+msgstr ""
+
+#: ../../networking/autoscale_without_netscaler.rst:57
+# c9330ee4e4ec4a0fab4fba627aef3692
+msgid "Additionally, if you want to configure the advanced settings, click Show advanced settings, and specify the following:"
+msgstr ""
+
+#: ../../networking/autoscale_without_netscaler.rst:59
+# 81ad44e324de4a7981892ca55611000e
+msgid "Polling interval: Frequency in which the conditions, combination of counter, operator and threshold, are to be evaluated before taking a scale up or down action. The default polling interval is 30 seconds."
+msgstr ""
+
+#: ../../networking/autoscale_without_netscaler.rst:61
+# 6269ce68ba3644a7aef1617b8a06b037
+msgid "Quiet Time: This is the cool down period after an AutoScale action is initiated. The time includes the time taken to complete provisioning a VM instance from its template and the time taken by an application to be ready to serve traffic. This quiet time allows the fleet to come up to a stable state before any action can take place. The default is 300 seconds."
+msgstr ""
+
+#: ../../networking/autoscale_without_netscaler.rst:63
+# c6e65c1812814496bd1282ec97c7df0c
+msgid "Destroy VM Grace Period: The duration in seconds, after a scaledown action is initiated, to wait before the VM is destroyed as part of scaledown action. This is to ensure graceful close of any pending sessions or transactions being served by the VM marked for destroy. The default is 120 seconds."
+msgstr ""
+
+#: ../../networking/autoscale_without_netscaler.rst:65
+# 6a90629fb18546df9eef77cb74d6d15e
+msgid "Apply: Click Apply to create the AutoScale configuration."
+msgstr ""
+
+#: ../../networking/autoscale_without_netscaler.rst:68
+# ba9c7c2d58454a53940874911d9edefe
+msgid "Disabling and Enabling an AutoScale Configuration"
+msgstr ""
+
+#: ../../networking/autoscale_without_netscaler.rst:70
+# 58935b9d39ad4fdaaf8cc7d4a8a4c69b
+msgid "If you want to perform any maintenance operation on the AutoScale VM instances, disable the AutoScale configuration. When the AutoScale configuration is disabled, no scaleup or scaledown action is performed. You can use this downtime for the maintenance activities. To disable the AutoScale configuration, click the Disable AutoScale button."
+msgstr ""
+
+#: ../../networking/autoscale_without_netscaler.rst:72
+# 3e4ba6cb6d1b4bc79688675cbe57c75b
+msgid "The button toggles between enable and disable, depending on whether AutoScale is currently enabled or not. After the maintenance operations are done, you can enable the AutoScale configuration back. To enable, open the AutoScale configuration page again, then click the Enable AutoScale button."
+msgstr ""
+
+#: ../../networking/autoscale_without_netscaler.rst:75
+# 9ce87103773042ca88fd9b14d20ffe70
+msgid "Updating an AutoScale Configuration"
+msgstr ""
+
+#: ../../networking/autoscale_without_netscaler.rst:77
+# c9cea96d124b46f4ab55f5b5b212453b
+msgid "You can update the various parameters and add or delete the conditions in a scaleup or scaledown rule. Before you update an AutoScale configuration, ensure that you disable the AutoScale load balancer rule by clicking the Disable AutoScale button. After you modify the required AutoScale parameters, click Apply. To apply the new AutoScale policies, open the AutoScale configuration page again, then click the Enable AutoScale button."
+msgstr ""
+
+#: ../../networking/autoscale_without_netscaler.rst:81
+# 6738decbbf98438eaf0a2fc8f5d260d6
+msgid "Runtime Considerations"
+msgstr ""
+
+#: ../../networking/autoscale_without_netscaler.rst:83
+# 217b68ea35fc4cf2a5ad264d0e24f2db
+msgid "An administrator should not assign a VM to a load balancing rule which is configured for AutoScale."
+msgstr ""
+
+#: ../../networking/autoscale_without_netscaler.rst:85
+# 7ea14773c17b47cc98fb83abe744e19e
+msgid "Making API calls outside the context of AutoScale, such as destroyVM, on an autoscaled VM leaves the load balancing configuration in an inconsistent state. Though VM is destroyed from the load balancer rule, it continues be showed as a service assigned to a rule inside the context of AutoScale."
+msgstr ""
+
+#: ../../networking/ipv6.rst:2
+# 9063c69b83cc4675b677f47968689ba7
+msgid "IPv6 Support in CloudStack"
+msgstr ""
+
+#: ../../networking/ipv6.rst:4
+# 41c57b3d50204fb7963f34ab1d591afd
+msgid "CloudStack supports Internet Protocol version 6 (IPv6), the recent version of the Internet Protocol (IP) that defines routing the network traffic. IPv6 uses a 128-bit address that exponentially expands the current address space that is available to the users. IPv6 addresses consist of eight groups of four hexadecimal digits separated by colons, for example, 5001:0dt8:83a3:1012:1000:8s2e:0870:7454. CloudStack supports IPv6 for public IPs in shared networks. With IPv6 support, VMs in shared networks can obtain both IPv4 and IPv6 addresses from the DHCP server. You can deploy VMs either in a IPv6 or IPv4 network, or in a dual network environment. If IPv6 network is used, the VM generates a link-local IPv6 address by itself, and receives a stateful IPv6 address from the DHCPv6 server."
+msgstr ""
+
+#: ../../networking/ipv6.rst:17
+# 79ebb2325f5b4e8e8cac37bfa0d04fa5
+msgid "IPv6 is supported only on KVM and XenServer hypervisors. The IPv6 support is only an experimental feature."
+msgstr ""
+
+#: ../../networking/ipv6.rst:20
+# 53b327c0565745c58193a2a636f6b508
+msgid "Here's the sequence of events when IPv6 is used:"
+msgstr ""
+
+#: ../../networking/ipv6.rst:24
+# 8a26e433fd0b476792d0bf704b27cdcf
+msgid "The administrator creates an IPv6 shared network in an advanced zone."
+msgstr ""
+
+#: ../../networking/ipv6.rst:28
+# bae33a2f19004456a2ab80520bf87e3f
+msgid "The user deploys a VM in an IPv6 shared network."
+msgstr ""
+
+#: ../../networking/ipv6.rst:32
+# d94e348fb434423788634e5ad292b053
+msgid "The user VM generates an IPv6 link local address by itself, and gets an IPv6 global or site local address through DHCPv6."
+msgstr ""
+
+#: ../../networking/ipv6.rst:37
+# 2251bd2a3fae426e8c8833a37fb1e8ed
+msgid "Prerequisites and Guidelines"
+msgstr ""
+
+#: ../../networking/ipv6.rst:39
+# b0a1bb7836c9452d92a65788bee8b8a3
+msgid "Consider the following:"
+msgstr ""
+
+#: ../../networking/ipv6.rst:43
+# afe38a72dbd14cdeb4d9dc752f130e59
+msgid "CIDR size must be 64 for IPv6 networks."
+msgstr ""
+
+#: ../../networking/ipv6.rst:47
+# c8ea1b7c1a9c49539151a78f22659658
+msgid "The DHCP client of the guest VMs should support generating DUID based on Link-layer Address (DUID- LL). DUID-LL derives from the MAC address of guest VMs, and therefore the user VM can be identified by using DUID. See `Dynamic Host Configuration Protocol for IPv6 <http://tools.ietf.org/html/rfc3315>`__\\ for more information."
+msgstr ""
+
+#: ../../networking/ipv6.rst:55
+# 8ddad136696547268df22d1813bf7ed4
+msgid "The gateway of the guest network generates Router Advisement and Response messages to Router Solicitation. The M (Managed Address Configuration) flag of Router Advisement should enable stateful IP address configuration. Set the M flag to where the end nodes receive their IPv6 addresses from the DHCPv6 server as opposed to the router or switch."
+msgstr ""
+
+#: ../../networking/ipv6.rst:62
+# 018ea1acf74f45559953f36b219c962f
+msgid "The M flag is the 1-bit Managed Address Configuration flag for Router"
+msgstr ""
+
+#: ../../networking/ipv6.rst:63
+# 0fe982af1fb44ffa95b13393cb6bcd97
+msgid "Advisement. When set, Dynamic Host Configuration Protocol (DHCPv6) is available for address configuration in addition to any IPs set by using stateless address auto-configuration."
+msgstr ""
+
+#: ../../networking/ipv6.rst:69
+# 93db14f646d24aa5acffca5d20338975
+msgid "Use the System VM template exclusively designed to support IPv6. Download the System VM template from `http://cloudstack.apt-get.eu/systemvm/ <http://cloudstack.apt-get.eu/systemvm/>`__."
+msgstr ""
+
+#: ../../networking/ipv6.rst:75
+# 516cb011d5914d10b3c49e9796299f74
+msgid "The concept of Default Network applies to IPv6 networks. However, unlike IPv4 CloudStack does not control the routing information of IPv6 in shared network; the choice of Default Network will not affect the routing in the user VM."
+msgstr ""
+
+#: ../../networking/ipv6.rst:82
+# e72596a773f14d379a92ec92afa10cce
+msgid "In a multiple shared network, the default route is set by the rack router, rather than the DHCP server, which is out of CloudStack control. Therefore, in order for the user VM to get only the default route from the default NIC, modify the configuration of the user VM, and set non-default NIC's ``accept_ra`` to 0 explicitly. The ``accept_ra`` parameter accepts Router Advertisements and auto-configure ``/proc/sys/net/ipv6/conf/interface`` with received data."
+msgstr ""
+
+#: ../../networking/ipv6.rst:92
+# dcaf10acb3f34de380f2eec1b9170253
+msgid "Limitations of IPv6 in CloudStack"
+msgstr ""
+
+#: ../../networking/ipv6.rst:94
+# fb2bfd214ac547ff97ee00d937f01b02
+msgid "The following are not yet supported:"
+msgstr ""
+
+#: ../../networking/ipv6.rst:98
+# db335d19e6c047379e156b18f9d937f4
+msgid "Security groups"
+msgstr ""
+
+#: ../../networking/ipv6.rst:102
+# a3ea0a4439b1496fb507520690094baf
+msgid "Userdata and metadata"
+msgstr ""
+
+#: ../../networking/ipv6.rst:106
+# 6b8f88ad9ab547138fbd3e9f40c83d7f
+msgid "Passwords"
+msgstr ""
+
+#: ../../networking/ipv6.rst:109
+# 0d4771d5873a429984066fed90876c50
+msgid "Guest VM Configuration for DHCPv6"
+msgstr ""
+
+#: ../../networking/ipv6.rst:111
+# 01d0d92255b34c64a62845f02b8a8a4e
+msgid "For the guest VMs to get IPv6 address, run dhclient command manually on each of the VMs. Use DUID-LL to set up dhclient."
+msgstr ""
+
+#: ../../networking/ipv6.rst:114
+# f81673230f4447d680980559d7175a57
+msgid "The IPv6 address is lost when a VM is stopped and started. Therefore,"
+msgstr ""
+
+#: ../../networking/ipv6.rst:115
+# bb68d3447803467fa644192f3ee97415
+msgid "use the same procedure to get an IPv6 address when a VM is stopped and started."
+msgstr ""
+
+#: ../../networking/ipv6.rst:120
+# 1ac57146ad144c0e889d7f366e9df765
+msgid "Set up dhclient by using DUID-LL."
+msgstr ""
+
+#: ../../networking/ipv6.rst:122
+# cca1077553b14ea588e13553ca5d6a15
+msgid "Perform the following for DHCP Client 4.2 and above:"
+msgstr ""
+
+#: ../../networking/ipv6.rst:126
+# 8fdbfe4d8c434120b67eb59e81d51d8b
+msgid "Run the following command on the selected VM to get the dhcpv6 offer from VR:"
+msgstr ""
+
+#: ../../networking/ipv6.rst:133
+# 656eff7b6ce241928e7a9cb840be833e
+msgid "Perform the following for DHCP Client 4.1:"
+msgstr ""
+
+#: ../../networking/ipv6.rst:137
+# a4d789246cad41a1b4d23bd3ed929217
+msgid "Open the following to the dhclient configuration file:"
+msgstr ""
+
+#: ../../networking/ipv6.rst:145
+# 77af02d23c8e47f3b22d8d204a1870ae
+msgid "Add the following to the dhclient configuration file:"
+msgstr ""
+
+#: ../../networking/ipv6.rst:153
+# 21b6ea25a4a748cf8e91acdaf3003e19
+msgid "Get IPv6 address from DHCP server as part of the system or network restart."
+msgstr ""
+
+#: ../../networking/ipv6.rst:156
+# b6c0f47d45b34e44acaaca779414b9cd
+msgid "Based on the operating systems, perform the following:"
+msgstr ""
+
+#: ../../networking/ipv6.rst:158
+# ccd975fe312049fd896c38cc020b3fa9
+msgid "On CentOS 6.2:"
+msgstr ""
+
+#: ../../networking/ipv6.rst:162
+# 0b3572ab3af943e48535af636ead58c5
+msgid "Open the Ethernet interface configuration file:"
+msgstr ""
+
+#: ../../networking/ipv6.rst:168
+# b65f97c19a704a6d9d47de7c27b6c154
+msgid "The ``ifcfg-eth0`` file controls the first NIC in a system."
+msgstr ""
+
+#: ../../networking/ipv6.rst:172
+#: ../../networking/ipv6.rst:197
+#: ../../networking/ipv6.rst:218
+# b294b17bb15c4c6e93597ac4fb108b8f
+# 0afbae1c0d984242acfb32d4639fb73d
+# 796e2de0cb9a4194ab47d7f51f720614
+msgid "Make the necessary configuration changes, as given below:"
+msgstr ""
+
+#: ../../networking/ipv6.rst:189
+#: ../../networking/ipv6.rst:210
+# 9f45f88d1d0543bcb315e99481fddf64
+# e374feefe5c04ff09a138d5020e42aa9
+msgid "Open the following:"
+msgstr ""
+
+#: ../../networking/ipv6.rst:206
+# f72a159dff2c4923a6fb4cdc96baefdd
+msgid "On Ubuntu 12.10"
+msgstr ""
+
+#: ../../networking/midonet.rst:2
+# f4e5c6a4da61434aa40dd7ba93484347
+msgid "The MidoNet Plugin"
+msgstr ""
+
+#: ../../networking/midonet.rst:5
+# 5b3351f0b1bc467ab6133d431de2a226
+msgid "Introduction to the MidoNet Plugin"
+msgstr ""
+
+#: ../../networking/midonet.rst:7
+# 43f5b5c6fc1241dfb632510a30e519ae
+msgid "The MidoNet plugin allows CloudStack to use the MidoNet virtualized networking solution as a provider for CloudStack networks and services. For more information on MidoNet and how it works, see http://www.midokura.com/midonet/."
+msgstr ""
+
+#: ../../networking/midonet.rst:13
+# c889a6c491c042388e4a20497669eb79
+msgid "Features of the MidoNet Plugin"
+msgstr ""
+
+#: ../../networking/midonet.rst:15
+# 835bde43c8534aefac5e1ccd81e317f4
+msgid "In CloudStack 4.2.0 only the KVM hypervisor is supported for use in combination with MidoNet."
+msgstr ""
+
+#: ../../networking/midonet.rst:18
+# cb53a8ffabf047298535ec3e31beb1ad
+msgid "In CloudStack release 4.2.0 this plugin supports several services in the Advanced Isolated network mode."
+msgstr ""
+
+#: ../../networking/midonet.rst:21
+# 5408bf0f7ed04335a07c1ac3f3448d26
+msgid "When tenants create new isolated layer 3 networks, instead of spinning up extra Virtual Router VMs, the relevant L3 elements (routers etc) are created in the MidoNet virtual topology by making the appropriate calls to the MidoNet API. Instead of using VLANs, isolation is provided by MidoNet."
+msgstr ""
+
+#: ../../networking/midonet.rst:27
+# 08c1c37a1bbd47dc96340d462ad72de6
+msgid "Aside from the above service (Connectivity), several extra features are supported in the 4.2.0 release:"
+msgstr ""
+
+#: ../../networking/midonet.rst:30
+#: ../../networking/nicira-plugin.rst:135
+#: ../../networking/nicira-plugin.rst:171
+#: ../../networking/nicira-plugin.rst:249
+#: ../../networking/ovs-plugin.rst:165
+#: ../../networking/ovs-plugin.rst:201
+# 49b7d4c5843d48e6a4d1903891dae0d5
+# ce613877293142fcb602392053011779
+# ef05554567b64823a676c47eb718aca1
+# 2d54607e20174f57bb939e3a4e34290b
+# 6785cd841d124fba8786fbffe6cddc8e
+# 19964c1d31624c81bece37d61d6b9f12
+msgid "DHCP"
+msgstr ""
+
+#: ../../networking/midonet.rst:32
+# 0114445c01474c868169c1cc09fcf6a3
+msgid "Firewall (ingress)"
+msgstr ""
+
+#: ../../networking/midonet.rst:34
+#: ../../networking/nicira-plugin.rst:23
+#: ../../networking/nicira-plugin.rst:145
+#: ../../networking/nicira-plugin.rst:177
+#: ../../networking/nicira-plugin.rst:257
+#: ../../networking/ovs-plugin.rst:175
+#: ../../networking/ovs-plugin.rst:207
+# cc25fff9d5124386ade225fd5bd434b9
+# 114e75dc258c41639ef45e1509e70e6a
+# 756d3782de384f7fa56ece273f820f1f
+# a59f45b448464b9c901841cb1c22fa73
+# 112c6589b3f0476fa047e31ff811c08a
+# 8ee18467dfbd4b41a9978d7b19ef330c
+# aaf6aab6d1244928b9202443ed4ef6b5
+msgid "Source NAT"
+msgstr ""
+
+#: ../../networking/midonet.rst:36
+#: ../../networking/nicira-plugin.rst:25
+#: ../../networking/nicira-plugin.rst:147
+#: ../../networking/nicira-plugin.rst:179
+#: ../../networking/nicira-plugin.rst:259
+#: ../../networking/ovs-plugin.rst:22
+#: ../../networking/ovs-plugin.rst:177
+#: ../../networking/ovs-plugin.rst:209
+# 5b959f094f524c5bad49148c2f11da16
+# bcacdbd92685435e8f2a5df1a1dd3b88
+# c13412cc9cce43e7a004eae8f13befe2
+# 85c67b794ccd46c0b46abaebd7630ec5
+# 0f45e03e929e49058061a4a2e0443085
+# bd9381baaa4d4fb7b4c942427d3ea4f3
+# f4d9288c69e545b1a9259940ea478a01
+# 1f40ca7af9414412b7526701cf836922
+msgid "Static NAT"
+msgstr ""
+
+#: ../../networking/midonet.rst:38
+#: ../../networking/nicira-plugin.rst:27
+#: ../../networking/ovs-plugin.rst:24
+# 0de776336a694f4dafd899038007d024
+# 992479d12e61499ca18b368c020bc4f1
+# 513cd51fab824f0cacb77ff2a6753ed0
+msgid "Port Forwarding"
+msgstr ""
+
+#: ../../networking/midonet.rst:40
+# 5ecfd1fd0fc6494988c5a472673fbc7d
+msgid "The plugin has been tested with MidoNet version 12.12. (Caddo)."
+msgstr ""
+
+#: ../../networking/midonet.rst:43
+# b8b2387b8d4b4e849ba66caea5e01c81
+msgid "Using the MidoNet Plugin"
+msgstr ""
+
+#: ../../networking/midonet.rst:48
+# 2668ec6a367641e69ff49062e49ce7e6
+msgid "In order to use the MidoNet plugin, the compute hosts must be running the MidoNet Agent, and the MidoNet API server must be available. Please consult the MidoNet User Guide for more information. The following section describes the CloudStack side setup."
+msgstr ""
+
+#: ../../networking/midonet.rst:53
+# 99b96e8acec34a0d8d7c21d78e2703fd
+msgid "CloudStack needs to have at least one physical network with the isolation method set to \"MIDO\". This network should be enabled for the Guest and Public traffic types."
+msgstr ""
+
+#: ../../networking/midonet.rst:57
+# 8b171ca5cb9e484397531f31e7b4d842
+msgid "Next, we need to set the following CloudStack settings under \"Global Settings\" in the UI:"
+msgstr ""
+
+#: ../../networking/midonet.rst:61
+# b69a22dee5ce48f4938914d6c4377874
+msgid "Setting Name"
+msgstr ""
+
+#: ../../networking/midonet.rst:61
+# db6dfe91d7fc49a7a23c8ec6f5589d9b
+msgid "Description"
+msgstr ""
+
+#: ../../networking/midonet.rst:61
+# 8ce816e9b802465f8f5f6375c4bda427
+msgid "Example"
+msgstr ""
+
+#: ../../networking/midonet.rst:63
+# 9b5539562d8347e5a40e744f9b8086e7
+msgid "midonet.apiserver.address"
+msgstr ""
+
+#: ../../networking/midonet.rst:63
+# a95222e0e61e4a3c9b250cd37d5cf298
+msgid "Specify the address at which the Midonet API server can be contacted"
+msgstr ""
+
+#: ../../networking/midonet.rst:63
+# 4188583e5177441b9821e4f5f89578a2
+msgid "http://192.168.1.144:8081/midolmanj-mgmt"
+msgstr ""
+
+#: ../../networking/midonet.rst:65
+# 665afa499ac44b54a7a8c0e53a749d66
+msgid "midonet.providerrouter.id"
+msgstr ""
+
+#: ../../networking/midonet.rst:65
+# 78c4feefb6d543d1ba12f3992e48e7fa
+msgid "Specifies the UUID of the Midonet provider router"
+msgstr ""
+
+#: ../../networking/midonet.rst:65
+# f7035c39c3a04d189249f37810cd413f
+msgid "d7c5e6a3-e2f4-426b-b728-b7ce6a0448e5"
+msgstr ""
+
+#: ../../networking/midonet.rst:68
+# 65914ae089bc4ab6ad82c66df94e9d49
+msgid "Table: CloudStack settings"
+msgstr ""
+
+#: ../../networking/midonet.rst:70
+# 20e830daf68a461a81d396114ad184ec
+msgid "We also want MidoNet to take care of public traffic, so in *componentContext.xml* we need to replace this line:"
+msgstr ""
+
+#: ../../networking/midonet.rst:78
+# 00b49b309af944c58397a9f4dbf0ff2a
+msgid "With this:"
+msgstr ""
+
+#: ../../networking/midonet.rst:85
+# 6c11d6b3c68e4451a5ca2b6c31e2c584
+msgid "On the compute host, MidoNet takes advantage of per-traffic type VIF driver support in CloudStack KVM."
+msgstr ""
+
+#: ../../networking/midonet.rst:88
+# d02ca0b479ba4720b56679504af434b7
+msgid "In agent.properties, we set the following to make MidoNet take care of Guest and Public traffic:"
+msgstr ""
+
+#: ../../networking/midonet.rst:96
+# 29db8f221b5641ea84be16cfdf0202f0
+msgid "This is explained further in MidoNet User Guide."
+msgstr ""
+
+#: ../../networking/midonet.rst:99
+# 3a516331b1ea440298354c98069645bb
+msgid "Enabling the MidoNet service provider via the UI"
+msgstr ""
+
+#: ../../networking/midonet.rst:101
+# 830c1e31051e44c98c0f34a05952b2f7
+msgid "To allow CloudStack to use the MidoNet Plugin the network service provider needs to be enabled on the physical network."
+msgstr ""
+
+#: ../../networking/midonet.rst:104
+# cb5416ba9cad4f6b82d36a759957167f
+msgid "The steps to enable via the UI are as follows:"
+msgstr ""
+
+#: ../../networking/midonet.rst:106
+# 3c9f034a471d460fa1e78d7fc0d23038
+msgid "In the left navbar, click Infrastructure"
+msgstr ""
+
+#: ../../networking/midonet.rst:108
+# bcb7494347d2406d87ebd01a0c91fb20
+msgid "In Zones, click View All"
+msgstr ""
+
+#: ../../networking/midonet.rst:110
+# 95f2fb5dc5884524a69094143f6bb76d
+msgid "Click the name of the Zone on which you are setting up MidoNet"
+msgstr ""
+
+#: ../../networking/midonet.rst:112
+# 188fd04a8ae145fda2c3a8c890d5462e
+msgid "Click the Physical Network tab"
+msgstr ""
+
+#: ../../networking/midonet.rst:114
+# 1e542d7390884d2bad2f3c47877542b1
+msgid "Click the Name of the Network on which you are setting up MidoNet"
+msgstr ""
+
+#: ../../networking/midonet.rst:116
+# aaaf74a3d52b42ebae8f4e88c8b40355
+msgid "Click Configure on the Network Service Providers box"
+msgstr ""
+
+#: ../../networking/midonet.rst:118
+# 04d5bfd6646f4a97989e347474116368
+msgid "Click on the name MidoNet"
+msgstr ""
+
+#: ../../networking/midonet.rst:120
+# 642adc3b1cf44faab16425e912c923f5
+msgid "Click the Enable Provider button in the Network tab"
+msgstr ""
+
+#: ../../networking/midonet.rst:123
+# cf7eda3b5d3f4866846e763c3caf4b70
+msgid "Enabling the MidoNet service provider via the API"
+msgstr ""
+
+#: ../../networking/midonet.rst:125
+# c59c00a7fa6f46119faf3eca40367b44
+msgid "To enable via the API, use the following API calls:"
+msgstr ""
+
+#: ../../networking/midonet.rst:127
+# 8282ec8f110b4fe89bffca6181a46725
+msgid "*addNetworkServiceProvider*"
+msgstr ""
+
+#: ../../networking/midonet.rst:129
+# 60147b795fda499aa9cf7558014d88d5
+msgid "name = \"MidoNet\""
+msgstr ""
+
+#: ../../networking/midonet.rst:131
+# bcc67ccf4214467e8e400256884b5a51
+msgid "physicalnetworkid = <the uuid of the physical network>"
+msgstr ""
+
+#: ../../networking/midonet.rst:133
+# ea8ad1ea1ce440f293268c6ce2be6c7d
+msgid "*updateNetworkServiceProvider*"
+msgstr ""
+
+#: ../../networking/midonet.rst:135
+# 4415a0b5d7c345c297f91727eda61212
+msgid "id = <the provider uuid returned by the previous call>"
+msgstr ""
+
+#: ../../networking/midonet.rst:137
+# df55f4d520bf4f90a9d0988e752af678
+msgid "state = \"Enabled\""
+msgstr ""
+
+#: ../../networking/midonet.rst:140
+#: ../../networking/nicira-plugin.rst:338
+#: ../../networking/ovs-plugin.rst:226
+# dfc989938200446f8f7792e0488afccf
+# 82db7e6f7b3144439a90257872b027ff
+# 05f9bc2018e743d09a919067bab537a8
+msgid "Revision History"
+msgstr ""
+
+#: ../../networking/midonet.rst:142
+# 65c949887213426e8c750fcc37c11160
+msgid "0-0 Wed Mar 13 2013 Dave Cahill dcahill@midokura.com Documentation created for 4.2.0 version of the MidoNet Plugin"
+msgstr ""
+
+#: ../../networking/nicira-plugin.rst:2
+# 5a81d39c1e9e4666b11b0d2062315f8b
+msgid "The Nicira NVP Plugin"
+msgstr ""
+
+#: ../../networking/nicira-plugin.rst:5
+# cb5aa76e8916452dbe92065c109fda58
+msgid "Introduction to the Nicira NVP Plugin"
+msgstr ""
+
+#: ../../networking/nicira-plugin.rst:7
+# 0c134c3d04de4ba49f31e0c3f0108144
+msgid "The Nicira NVP plugin adds Nicira NVP as one of the available SDN implementations in CloudStack. With the plugin an exisiting Nicira NVP setup can be used by CloudStack to implement isolated guest networks and to provide additional services like routing and NAT."
+msgstr ""
+
+#: ../../networking/nicira-plugin.rst:13
+# 5d2369e469d14a4d9cf445bcd893c1cc
+msgid "Features of the Nicira NVP Plugin"
+msgstr ""
+
+#: ../../networking/nicira-plugin.rst:15
+# 6aff4bc970e04090b584058d98f39113
+msgid "The following table lists the CloudStack network services provided by the Nicira NVP Plugin."
+msgstr ""
+
+#: ../../networking/nicira-plugin.rst:19
+#: ../../networking/ovs-plugin.rst:18
+# 618aa9ed3ee14e63890a722f29d34f8f
+# 0b2e8bbc17194ce1a6f82dd96bd13b78
+msgid "Network Service"
+msgstr ""
+
+#: ../../networking/nicira-plugin.rst:19
+#: ../../networking/nicira-plugin.rst:38
+#: ../../networking/ovs-plugin.rst:18
+#: ../../networking/ovs-plugin.rst:37
+# d3962c8e69d44b74bd77cd1c575b7792
+# 8328a42be97a41c8aa575ee34b6fcf9b
+# dba6e8a2bae44ea484d6c5fe146e30f1
+# a31335a8c7454a1a8dd94f2772c9b0b2
+msgid "CloudStack version"
+msgstr ""
+
+#: ../../networking/nicira-plugin.rst:19
+# f5d14881fe124e5ebcc4ac0f736bfbf8
+msgid "NVP version"
+msgstr ""
+
+#: ../../networking/nicira-plugin.rst:21
+#: ../../networking/nicira-plugin.rst:151
+#: ../../networking/nicira-plugin.rst:183
+#: ../../networking/nicira-plugin.rst:265
+#: ../../networking/ovs-plugin.rst:20
+#: ../../networking/ovs-plugin.rst:181
+#: ../../networking/ovs-plugin.rst:215
+# 31df7547b72748daaa738f7796b5d45f
+# c61de43323664b898739f2d79f6353a2
+# be88317c512544d79d822bf5bcb8c7cc
+# 63f4305ccce749aa98ab4fca8ad01a7e
+# d08c3df5e050478e9e467de862f6212f
+# 7756125b529445188dfa228957dea3d5
+# 51b720e6b5b24589aafe127499b9815a
+msgid "Virtual Networking"
+msgstr ""
+
+#: ../../networking/nicira-plugin.rst:21
+#: ../../networking/nicira-plugin.rst:40
+#: ../../networking/ovs-plugin.rst:20
+#: ../../networking/ovs-plugin.rst:39
+# 1f8de4ae2cf948f784c605ef8accd105
+# 1afbc018f09c416797709cef931c5b78
+# e2b0698af48b47659311b5f9c8c7d735
+# 2ccb535cbc8444d7b5f09a2531fad22a
+msgid ">= 4.0"
+msgstr ""
+
+#: ../../networking/nicira-plugin.rst:21
+# 45109fe45d4c41c09733a1c206754e23
+msgid ">= 2.2.1"
+msgstr ""
+
+#: ../../networking/nicira-plugin.rst:23
+#: ../../networking/nicira-plugin.rst:25
+#: ../../networking/nicira-plugin.rst:27
+#: ../../networking/nicira-plugin.rst:42
+# 7ab01a4140024745b65ddd03be090f5c
+# 574293701d7844b1971e1f620a2d75ac
+# 19f979d2da69435e9c609234c0ed80a1
+# 2754366ea78e49f78fb7f27bc85da121
+msgid ">= 4.1"
+msgstr ""
+
+#: ../../networking/nicira-plugin.rst:23
+#: ../../networking/nicira-plugin.rst:25
+#: ../../networking/nicira-plugin.rst:27
+# 62a2875bd16e44409061c004560b584e
+# 1f25483790be4a13aa0f8d5d1c9516dc
+# e06ac671db424fee844691f37c4a0b4a
+msgid ">= 3.0.1"
+msgstr ""
+
+#: ../../networking/nicira-plugin.rst:30
+#: ../../networking/ovs-plugin.rst:29
+# e54b61fd04a34850aa0d2c8836e91428
+# 03569648f6cf400a81547171df27afe6
+msgid "Table: Supported Services"
+msgstr ""
+
+#: ../../networking/nicira-plugin.rst:32
+#: ../../networking/ovs-plugin.rst:31
+# fe134237dd3c41eeaf00bf7b5e90cd0b
+# 1e2ef00d06a148a7a074c4e8ad341963
+msgid "The Virtual Networking service was originally called 'Connectivity' in CloudStack 4.0"
+msgstr ""
+
+#: ../../networking/nicira-plugin.rst:35
+# ed15aa5806314c3fb2f34341ec69e7b2
+msgid "The following hypervisors are supported by the Nicira NVP Plugin."
+msgstr ""
+
+#: ../../networking/nicira-plugin.rst:38
+#: ../../networking/ovs-plugin.rst:37
+#: ../../networking/vxlan.rst:15
+# 6e79e2b14d884902adec144d58c0615b
+# 9dade5da23f44b52abad25189603005b
+# e127c87468024894ad783fbe0121c009
+msgid "Hypervisor"
+msgstr ""
+
+#: ../../networking/nicira-plugin.rst:40
+#: ../../networking/ovs-plugin.rst:39
+# e5da1a2aebc84c168d9f5a3429e7be98
+# 8d14a15a62954f4587194401c7aa71d4
+msgid "XenServer"
+msgstr ""
+
+#: ../../networking/nicira-plugin.rst:42
+#: ../../networking/ovs-plugin.rst:41
+#: ../../networking/vxlan.rst:15
+# 41413a228a0741fd8b8f0d7d541f1373
+# b0ff6e7152884e1792c9c977f7204b5d
+# f9510dd06b0040de93865b0d84796393
+msgid "KVM"
+msgstr ""
+
+#: ../../networking/nicira-plugin.rst:45
+#: ../../networking/ovs-plugin.rst:44
+# d81b53ff53a44951a380e29b9c6db7df
+# 7196efd73f5a4c01bc053a00bc2e4d97
+msgid "Table: Supported Hypervisors"
+msgstr ""
+
+#: ../../networking/nicira-plugin.rst:47
+# f63025ea491548c1bed572ab06439e2f
+msgid "Please refer to the Nicira NVP configuration guide on how to prepare the hypervisors for Nicira NVP integration."
+msgstr ""
+
+#: ../../networking/nicira-plugin.rst:51
+# a0c72bc47354485cb25a1cf0d6b73bbb
+msgid "Configuring the Nicira NVP Plugin"
+msgstr ""
+
+#: ../../networking/nicira-plugin.rst:56
+# 93da17b4cc344e97bf764847d0e20f12
+msgid "Before enabling the Nicira NVP plugin the NVP Controller needs to be configured. Please review the NVP User Guide on how to do that."
+msgstr ""
+
+#: ../../networking/nicira-plugin.rst:59
+# 13a1a3abe3da4254bccf580f00103ca7
+msgid "Make sure you have the following information ready:"
+msgstr ""
+
+#: ../../networking/nicira-plugin.rst:61
+# 524d6581dc15405f9b3304a7403faf24
+msgid "The IP address of the NVP Controller"
+msgstr ""
+
+#: ../../networking/nicira-plugin.rst:63
+# a533d9652e3443849a8c2f21a6abd1a0
+msgid "The username to access the API"
+msgstr ""
+
+#: ../../networking/nicira-plugin.rst:65
+# 70aa49763ae14501bffaf353e46ad140
+msgid "The password to access the API"
+msgstr ""
+
+#: ../../networking/nicira-plugin.rst:67
+# dd7aa1c5a8b14a6ea68ab52a9bbc00c0
+msgid "The UUID of the Transport Zone that contains the hypervisors in this Zone"
+msgstr ""
+
+#: ../../networking/nicira-plugin.rst:70
+# 1ecd9bc2a14b4726a1a7eec1331ba0ea
+msgid "The UUID of the Gateway Service used to provide router and NAT services."
+msgstr ""
+
+#: ../../networking/nicira-plugin.rst:74
+# e25bf818aecf40409312b9add51d8914
+msgid "The gateway service uuid is optional and is used for Layer 3 services only (SourceNat, StaticNat and PortForwarding)"
+msgstr ""
+
+#: ../../networking/nicira-plugin.rst:78
+#: ../../networking/ovs-plugin.rst:62
+# be1fb34770334288bc4f3e86eac3448e
+# a9d10c0c1d5b46ebb765172d5a41e610
+msgid "Zone Configuration"
+msgstr ""
+
+#: ../../networking/nicira-plugin.rst:80
+# 245e6e002d5c4d448ca331c29392751f
+msgid "CloudStack needs to have at least one physical network with the isolation method set to \"STT\". This network should be enabled for the Guest traffic type."
+msgstr ""
+
+#: ../../networking/nicira-plugin.rst:84
+# 6d8d7a099e344032b83c39376904b5c0
+msgid "The Guest traffic type should be configured with the traffic label that matches the name of the Integration Bridge on the hypervisor. See the Nicira NVP User Guide for more details on how to set this up in XenServer or KVM."
+msgstr ""
+
+#: ../../networking/nicira-plugin.rst:94
+#: ../../networking/ovs-plugin.rst:141
+# 5adf72459a4d481a8a809a15a643954a
+# 3c583190756a4b1d8480134c93515228
+msgid "Enabling the service provider"
+msgstr ""
+
+#: ../../networking/nicira-plugin.rst:96
+# f48b20ae59ea49ff8ab3e6b842c2f77f
+msgid "The Nicira NVP provider is disabled by default. Navigate to the \"Network Service Providers\" configuration of the physical network with the STT isolation type. Navigate to the Nicira NVP provider and press the \"Enable Provider\" button."
+msgstr ""
+
+#: ../../networking/nicira-plugin.rst:101
+# d9006bf7e42e4a4caffb126799e04756
+msgid "CloudStack 4.0 does not have the UI interface to configure the Nicira NVP plugin. Configuration needs to be done using the API directly."
+msgstr ""
+
+#: ../../networking/nicira-plugin.rst:110
+# 9d2d62d686ae4d9f83a1a1e9083c7974
+msgid "Device Management"
+msgstr ""
+
+#: ../../networking/nicira-plugin.rst:112
+# cb620ac34ed6482f8820f59b902fdf9b
+msgid "In CloudStack a Nicira NVP setup is considered a \"device\" that can be added and removed from a physical network. To complete the configuration of the Nicira NVP plugin a device needs to be added to the physical network. Press the \"Add NVP Controller\" button on the provider panel and enter the configuration details."
+msgstr ""
+
+#: ../../networking/nicira-plugin.rst:123
+#: ../../networking/ovs-plugin.rst:153
+# c68f6f105758477bb153fa55a6d89824
+# 541f0595f05f4f6b848945774fa978e6
+msgid "Network Offerings"
+msgstr ""
+
+#: ../../networking/nicira-plugin.rst:125
+# c110a9dda09c4f5cbd4fe818ae3f9bd3
+msgid "Using the Nicira NVP plugin requires a network offering with Virtual Networking enabled and configured to use the NiciraNvp element. Typical use cases combine services from the Virtual Router appliance and the Nicira NVP plugin."
+msgstr ""
+
+#: ../../networking/nicira-plugin.rst:131
+#: ../../networking/nicira-plugin.rst:169
+#: ../../networking/nicira-plugin.rst:245
+#: ../../networking/ovs-plugin.rst:161
+#: ../../networking/ovs-plugin.rst:199
+# d11f5b34530745449796c4378664d8f9
+# 1151cc3e359e4f3caf7029ad0e23ba9e
+# bae2c53a24aa4438a52b5425973327b5
+# abbb6c562b014227b3953d4cd5268e48
+# 6b44ce13956d476db147cbd7a82cb152
+msgid "Service"
+msgstr ""
+
+#: ../../networking/nicira-plugin.rst:131
+#: ../../networking/nicira-plugin.rst:169
+#: ../../networking/nicira-plugin.rst:245
+#: ../../networking/ovs-plugin.rst:161
+#: ../../networking/ovs-plugin.rst:199
+# b7143394676041f3bc4c8ad0a8469195
+# fe1bb58eda974fc7abd9738556c892b1
+# ba2cc68f1ecc4542a40d411546b65af4
+# cf717075d6d74475b45d0fc2cd2058c5
+# 4d2a2b9215ef410ea5ebb21ad692af05
+msgid "Provider"
+msgstr ""
+
+#: ../../networking/nicira-plugin.rst:133
+#: ../../networking/nicira-plugin.rst:247
+#: ../../networking/ovs-plugin.rst:163
+# b65b3ee91ca34d20946f693ce05d4034
+# 969ee76a22ee4bc5afeb620adbb41223
+# 7c03de44f9ec4344b9f9c7de192971cd
+msgid "VPN"
+msgstr ""
+
+#: ../../networking/nicira-plugin.rst:133
+#: ../../networking/nicira-plugin.rst:135
+#: ../../networking/nicira-plugin.rst:137
+#: ../../networking/nicira-plugin.rst:139
+#: ../../networking/nicira-plugin.rst:141
+#: ../../networking/nicira-plugin.rst:143
+#: ../../networking/nicira-plugin.rst:145
+#: ../../networking/nicira-plugin.rst:147
+#: ../../networking/nicira-plugin.rst:149
+#: ../../networking/nicira-plugin.rst:171
+#: ../../networking/nicira-plugin.rst:173
+#: ../../networking/nicira-plugin.rst:175
+#: ../../networking/ovs-plugin.rst:163
+#: ../../networking/ovs-plugin.rst:165
+#: ../../networking/ovs-plugin.rst:167
+#: ../../networking/ovs-plugin.rst:169
+#: ../../networking/ovs-plugin.rst:173
+#: ../../networking/ovs-plugin.rst:175
+#: ../../networking/ovs-plugin.rst:201
+#: ../../networking/ovs-plugin.rst:203
+#: ../../networking/ovs-plugin.rst:205
+#: ../../networking/ovs-plugin.rst:207
+# 6bb38e5eff67483a80799e862b90a124
+# 777951d5dbd4419ca2a25e414bcc7591
+# d10b1e05ea064c9a91819119c8cbda9e
+# bf47cc26fa794985a7bf910d61248b21
+# e931c891651d43fcb8d27a57e0f7e8f9
+# 019b3d5bd11b48f2b10509ba58a380df
+# 5d337fd5e0d74eafbd860b79f190f32f
+# c6ca2df243a4423baf7a00847b8c50e2
+# 22ea972bf5064cf48bdbd8beab4574aa
+# 3af8c5a80e49430599c7f126f3b0c751
+# 0e0e35ffd2524ac4a956dc4bfb162948
+# 4a7f16dcf0434ae79b3dc9057050c06e
+# 1144b076cb5d4db99bb36f56afae9bac
+# 0a20026bac144d6ea321101034e427b0
+# 13f8ccfb544e4830b5ecd3b27c7ae757
+# 75f20c559a4e41dc9d6d4bd593a12e36
+# 57c3fd888a914375a37f95535d6d4a6b
+# 15446ee0c8e048898567bb5032a49f59
+# 25700ed7799f4cdca6f2685c84ea0fea
+# 9a644998b5e74fd9a41b518199f5ce34
+# c4e514a822f844f7bbd003be750ccac8
+# 27a0898b87144cb29250777f16082d9a
+msgid "VirtualRouter"
+msgstr ""
+
+#: ../../networking/nicira-plugin.rst:137
+#: ../../networking/nicira-plugin.rst:173
+#: ../../networking/nicira-plugin.rst:251
+#: ../../networking/ovs-plugin.rst:167
+#: ../../networking/ovs-plugin.rst:203
+# bc5830c742c04ccb932d4a21bf61dfba
+# b5e769e11e364694ae8495a6f8141407
+# d68ae4be18c4489a8d7ad5dc21a239da
+# ad8f4409b4734bad99428c468d656f20
+# 28d60e4ec08644959d354bed45917592
+msgid "DNS"
+msgstr ""
+
+#: ../../networking/nicira-plugin.rst:139
+#: ../../networking/ovs-plugin.rst:169
+# 5dbbf495e13c479486e733c1aaaee2b8
+# 20a037a6abbb429a975af056016135fa
+msgid "Firewall"
+msgstr ""
+
+#: ../../networking/nicira-plugin.rst:141
+#: ../../networking/nicira-plugin.rst:253
+#: ../../networking/ovs-plugin.rst:171
+# dc7afd6a74b1471a8e123e41c26453fa
+# 5559e64b2a46440e8aa9901e19d33b92
+# f40748c9c69c4dc1bfce45c3fe98659d
+msgid "Load Balancer"
+msgstr ""
+
+#: ../../networking/nicira-plugin.rst:143
+#: ../../networking/nicira-plugin.rst:175
+#: ../../networking/nicira-plugin.rst:255
+#: ../../networking/ovs-plugin.rst:173
+#: ../../networking/ovs-plugin.rst:205
+# b62a7e934b13466bbdfe5ad26d1dbf53
+# 885b162963ad48e6974ccd23426f57fa
+# 5fac16f4f2194d50a920361031fbc661
+# 5b5f0ec76735461b9a446a11ec469eb9
+# 0d6707ddaca049cfa168740106127322
+msgid "User Data"
+msgstr ""
+
+#: ../../networking/nicira-plugin.rst:149
+#: ../../networking/nicira-plugin.rst:181
+#: ../../networking/nicira-plugin.rst:261
+#: ../../networking/ovs-plugin.rst:179
+#: ../../networking/ovs-plugin.rst:211
+# 8b82c6fa4c9c4cddb6f4c1ca8c0683a6
+# 065e08db00404b8f89b223fe90ab1b29
+# 1bb7705e53734ad99e28325655bcc586
+# 09d688dc773945f98c75862ba10ed000
+# a80e84a19fd946c3be08c3473e496973
+msgid "Post Forwarding"
+msgstr ""
+
+#: ../../networking/nicira-plugin.rst:151
+#: ../../networking/nicira-plugin.rst:177
+#: ../../networking/nicira-plugin.rst:179
+#: ../../networking/nicira-plugin.rst:181
+#: ../../networking/nicira-plugin.rst:183
+#: ../../networking/nicira-plugin.rst:265
+#: ../../networking/nicira-plugin.rst:316
+# f79e81a377e24effb74f5f89551e3549
+# 3852e0bc80634ce7b88f50163b68d857
+# 87727014789943899c8e78513637d1ab
+# edd6581341c1480cbec0aa25d03d72b0
+# 2c64489bc4fe49dba21a248db0edf772
+# 50340451a1ad4b558a855a411fa9f9d0
+# 31ec210d01c5430cb7b65e64fc559a17
+msgid "NiciraNVP"
+msgstr ""
+
+#: ../../networking/nicira-plugin.rst:154
+#: ../../networking/ovs-plugin.rst:184
+# d1bd6cbe9f5d42068d72ff50c7e82d79
+# c3f06b80ac50400aa7add1dbc7d55308
+msgid "Table: Isolated network offering with regular services from the Virtual Router."
+msgstr ""
+
+#: ../../networking/nicira-plugin.rst:162
+# a78995044b664d38884f6e91114bc873
+msgid "The tag in the network offering should be set to the name of the physical network with the NVP provider."
+msgstr ""
+
+#: ../../networking/nicira-plugin.rst:165
+#: ../../networking/ovs-plugin.rst:195
+# 1a00a98b97234956860ea67999daa3db
+# d5005e0409714e719720bdd204ef72ff
+msgid "Isolated network with network services. The virtual router is still required to provide network services like dns and dhcp."
+msgstr ""
+
+#: ../../networking/nicira-plugin.rst:186
+#: ../../networking/ovs-plugin.rst:218
+# da5d426b8c74472aad063a8c695c4fd0
+# 38eeebf828e94e64b0973ab2a5940847
+msgid "Table: Isolated network offering with network services"
+msgstr ""
+
+#: ../../networking/nicira-plugin.rst:189
+# 96d160fe57ea4da6a6f718f3daf6338d
+msgid "Using the Nicira NVP plugin with VPC"
+msgstr ""
+
+#: ../../networking/nicira-plugin.rst:192
+# d1ec478dd3074e4e9c7b29606ea10ee6
+msgid "Supported VPC features"
+msgstr ""
+
+#: ../../networking/nicira-plugin.rst:194
+# ba8e48822f2a46ca80ff6b208f107ca5
+msgid "The Nicira NVP plugin supports CloudStack VPC to a certain extent. Starting with CloudStack version 4.1 VPCs can be deployed using NVP isolated networks."
+msgstr ""
+
+#: ../../networking/nicira-plugin.rst:198
+# d5f40344da8041c09b3571801e9ba1f2
+msgid "It is not possible to use a Nicira NVP Logical Router for as a VPC Router"
+msgstr ""
+
+#: ../../networking/nicira-plugin.rst:201
+# f1c3905dd9c840398de7c1409b3357b8
+msgid "It is not possible to connect a private gateway using a Nicira NVP Logical Switch"
+msgstr ""
+
+#: ../../networking/nicira-plugin.rst:205
+# 7065f8a39b504e49b39858dab512b447
+msgid "VPC Offering with Nicira NVP"
+msgstr ""
+
+#: ../../networking/nicira-plugin.rst:207
+# 89ff2e7e4c8c49df8a8a155f80f6f70f
+msgid "To allow a VPC to use the Nicira NVP plugin to provision networks, a new VPC offering needs to be created which allows the Virtual Networking service to be implemented by NiciraNVP."
+msgstr ""
+
+#: ../../networking/nicira-plugin.rst:211
+# bda837a0d67e4989ae3c409c9d35c475
+msgid "This is not currently possible with the UI. The API does provide the proper calls to create a VPC offering with Virtual Networking enabled. However due to a limitation in the 4.1 API it is not possible to select the provider for this network service. To configure the VPC offering with the NiciraNVP provider edit the database table 'vpc\\_offering\\_service\\_map' and change the provider to NiciraNvp for the service 'Connectivity'"
+msgstr ""
+
+#: ../../networking/nicira-plugin.rst:219
+# ac4f3b0154084c0483a97ad89415e100
+msgid "It is also possible to update the default VPC offering by adding a row to the 'vpc\\_offering\\_service\\_map' with service 'Connectivity' and provider 'NiciraNvp'"
+msgstr ""
+
+#: ../../networking/nicira-plugin.rst:228
+# 543b60828f814713b96ae87fc487ea48
+msgid "When creating a new VPC offering please note that the UI does not allow you to select a VPC offering yet. The VPC needs to be created using the API with the offering UUID."
+msgstr ""
+
+#: ../../networking/nicira-plugin.rst:233
+# 22a1220a7f2c48968771c9d2290d2a02
+msgid "VPC Network Offerings"
+msgstr ""
+
+#: ../../networking/nicira-plugin.rst:235
+# a08bef2a55e34b0e90b0626b1996943a
+msgid "The VPC needs specific network offerings with the VPC flag enabled. Otherwise these network offerings are identical to regular network offerings. To allow VPC networks with a Nicira NVP isolated network the offerings need to support the Virtual Networking service with the NiciraNVP provider."
+msgstr ""
+
+#: ../../networking/nicira-plugin.rst:241
+# a385bb41b1aa473c9c44ad9b14c49d11
+msgid "In a typical configuration two network offerings need to be created. One with the loadbalancing service enabled and one without loadbalancing."
+msgstr ""
+
+#: ../../networking/nicira-plugin.rst:247
+#: ../../networking/nicira-plugin.rst:249
+#: ../../networking/nicira-plugin.rst:251
+#: ../../networking/nicira-plugin.rst:253
+#: ../../networking/nicira-plugin.rst:255
+#: ../../networking/nicira-plugin.rst:257
+#: ../../networking/nicira-plugin.rst:259
+#: ../../networking/nicira-plugin.rst:261
+#: ../../networking/nicira-plugin.rst:263
+# d07087f1c69c455a834109561b0cfde2
+# 6530274146874b219df8e4775e3f6034
+# 5be193885d0b4645a68639153a591dcf
+# 9e3399ae187d4a58aff25d7c81205a34
+# 8a4e3ab19ca741e89aefb76bb9ba5ba7
+# 06565101b5a74ab48d6b91266e6ac9b1
+# 2e35b697aa564ccdbd28a8b573cd6c20
+# 31060b1bfc784f7085e25206b8ccd85b
+# 0980ef0687a8410c86496abb6b3e8a06
+msgid "VpcVirtualRouter"
+msgstr ""
+
+#: ../../networking/nicira-plugin.rst:263
+# 00c30e3971c14821ae0ed06455eb5709
+msgid "NetworkACL"
+msgstr ""
+
+#: ../../networking/nicira-plugin.rst:268
+# 519a6c52784246919dee03ed6e35eb4b
+msgid "Table: VPC Network Offering with Loadbalancing"
+msgstr ""
+
+#: ../../networking/nicira-plugin.rst:271
+# 3a5f7b0d37ed456692acd60a4715d5c4
+msgid "Troubleshooting the Nicira NVP Plugin"
+msgstr ""
+
+#: ../../networking/nicira-plugin.rst:274
+# 3fd7e8170bb64421911c19a02274bd53
+msgid "UUID References"
+msgstr ""
+
+#: ../../networking/nicira-plugin.rst:276
+# 789d734c55d84be699048adbabf4dad3
+msgid "The plugin maintains several references in the CloudStack database to items created on the NVP Controller."
+msgstr ""
+
+#: ../../networking/nicira-plugin.rst:279
+# edea32c3b89046ffa67ed4aea6bb7a6f
+msgid "Every guest network that is created will have its broadcast type set to Lswitch and if the network is in state \"Implemented\", the broadcast URI will have the UUID of the Logical Switch that was created for this network on the NVP Controller."
+msgstr ""
+
+#: ../../networking/nicira-plugin.rst:284
+# 6b8e3360507443389cc13e1cd24a7fc2
+msgid "The Nics that are connected to one of the Logical Switches will have their Logical Switch Port UUID listed in the nicira\\_nvp\\_nic\\_map table"
+msgstr ""
+
+#: ../../networking/nicira-plugin.rst:287
+# 1cebca6fd8304afe97371edf8d995d7e
+msgid "All devices created on the NVP Controller will have a tag set to domain-account of the owner of the network, this string can be used to search for items in the NVP Controller."
+msgstr ""
+
+#: ../../networking/nicira-plugin.rst:292
+# 6af46290da7d4824b2d5b357097fbd61
+msgid "Database tables"
+msgstr ""
+
+#: ../../networking/nicira-plugin.rst:294
+# d5f5219626854f709e657fcd621767a6
+msgid "The following tables are added to the cloud database for the Nicira NVP Plugin"
+msgstr ""
+
+#: ../../networking/nicira-plugin.rst:298
+#: ../../networking/nicira-plugin.rst:310
+#: ../../networking/nicira-plugin.rst:326
+# 53c8b3b2f25c4f47bbb53c7db9196b51
+# 0c142416faf547e4a149fa19d4a29f34
+# af2397e101774456b392ae473a8ac616
+msgid "id"
+msgstr ""
+
+#: ../../networking/nicira-plugin.rst:298
+#: ../../networking/nicira-plugin.rst:310
+#: ../../networking/nicira-plugin.rst:326
+# 42bc0a25597f4099acca8c07abb0d47f
+# 6b9bf4f773774fccae37b49f7f45179d
+# ef7b099241fd44889d8af022a2c0d408
+msgid "auto incrementing id"
+msgstr ""
+
+#: ../../networking/nicira-plugin.rst:300
+# a33c26507ef541d784a022a6d515e0f5
+msgid "logicalswitch"
+msgstr ""
+
+#: ../../networking/nicira-plugin.rst:300
+# 75292eb7b6194cc9a7d194e1faec0388
+msgid "uuid of the logical switch this port is connected to"
+msgstr ""
+
+#: ../../networking/nicira-plugin.rst:302
+# 668bf5ade1a2492b9cf0f6a15d1aa8b8
+msgid "logicalswitchport"
+msgstr ""
+
+#: ../../networking/nicira-plugin.rst:302
+# 094b2c0685c34d8698ea4121fc4a88eb
+msgid "uuid of the logical switch port for this nic"
+msgstr ""
+
+#: ../../networking/nicira-plugin.rst:304
+# cdb4155d3476483aa07c869bc8ac78b6
+msgid "nic"
+msgstr ""
+
+#: ../../networking/nicira-plugin.rst:304
+# caecd436ae884261a3bfadede5ab9dce
+msgid "the CloudStack uuid for this nic, reference to the nics table"
+msgstr ""
+
+#: ../../networking/nicira-plugin.rst:307
+# 6c10a96d48d84ae8b9190cb8c626b697
+msgid "Table: nicira\\_nvp\\_nic\\_map"
+msgstr ""
+
+#: ../../networking/nicira-plugin.rst:312
+# 6eb2d75abc814d21b629814fbac9664e
+msgid "uuid"
+msgstr ""
+
+#: ../../networking/nicira-plugin.rst:312
+# 34350d0d06cf4418b61a4cbe92abdf05
+msgid "UUID identifying this device"
+msgstr ""
+
+#: ../../networking/nicira-plugin.rst:314
+# 935c6786ee0048d99f0c9dcb139ed85a
+msgid "physical\\_network\\_id"
+msgstr ""
+
+#: ../../networking/nicira-plugin.rst:314
+# ea440688d7f643f6b11b83ca3a040128
+msgid "the physical network this device is configured on"
+msgstr ""
+
+#: ../../networking/nicira-plugin.rst:316
+# cd3800860ac044f898a3245467008af5
+msgid "provider\\_name"
+msgstr ""
+
+#: ../../networking/nicira-plugin.rst:318
+# 87bc5c5f703b4270a808133d3860792e
+msgid "device\\_name"
+msgstr ""
+
+#: ../../networking/nicira-plugin.rst:318
+# 97ca0c7c7ea74734830b00d6ee3b614e
+msgid "display name for this device"
+msgstr ""
+
+#: ../../networking/nicira-plugin.rst:320
+# 2baacc960233427e91829af5f967d22a
+msgid "host\\_id"
+msgstr ""
+
+#: ../../networking/nicira-plugin.rst:320
+# 7d1bc27e2b5e4329864c15cca9089af6
+msgid "reference to the host table with the device configuration"
+msgstr ""
+
+#: ../../networking/nicira-plugin.rst:323
+# f71a43d6ec914205a351c27e9432fa1b
+msgid "Table: external\\_nicira\\_nvp\\_devices"
+msgstr ""
+
+#: ../../networking/nicira-plugin.rst:328
+# 30f1c62a6bc3479eaa3fca1c99a342cb
+msgid "logicalrouter\\_uuid"
+msgstr ""
+
+#: ../../networking/nicira-plugin.rst:328
+# 24fc0e08e3844c049250201f0f5a6943
+msgid "uuid of the logical router"
+msgstr ""
+
+#: ../../networking/nicira-plugin.rst:330
+# b654ff3c1d7b40ffb8cd27a0e5eb292f
+msgid "network\\_id"
+msgstr ""
+
+#: ../../networking/nicira-plugin.rst:330
+# 5e919015c2e44058b7abcca55fdba0b3
+msgid "id of the network this router is linked to"
+msgstr ""
+
+#: ../../networking/nicira-plugin.rst:333
+# 70287e5e55d24b1ab49f44b0dbb4f0f8
+msgid "Table: nicira\\_nvp\\_router\\_map"
+msgstr ""
+
+#: ../../networking/nicira-plugin.rst:335
+# dde40d6b8f274f58b2ee49ac2d5e8ca1
+msgid "nicira\\_nvp\\_router\\_map is only available in CloudStack 4.1 and above"
+msgstr ""
+
+#: ../../networking/nicira-plugin.rst:340
+# 3698c81ecf44478bb41133498b56e83f
+msgid "0-0 Wed Oct 03 2012 Hugo Trippaers hugo@apache.org Documentation created for 4.0.0-incubating version of the NVP Plugin 1-0 Wed May 22 2013 Hugo Trippaers hugo@apache.org Documentation updated for CloudStack 4.1.0"
+msgstr ""
+
+#: ../../networking/ovs-plugin.rst:2
+# 0c186222f32b4bbda715262783ba3cf7
+msgid "The OVS Plugin"
+msgstr ""
+
+#: ../../networking/ovs-plugin.rst:5
+# 8063b6a753804137b6b5a38c53764c89
+msgid "Introduction to the OVS Plugin"
+msgstr ""
+
+#: ../../networking/ovs-plugin.rst:7
+# 738b7d7d38ef40d097cb25594387ba11
+msgid "The OVS plugin is the native SDN implementations in CloudStack, using GRE isolation method. The plugin can be used by CloudStack to implement isolated guest networks and to provide additional services like NAT, port forwarding and load balancing."
+msgstr ""
+
+#: ../../networking/ovs-plugin.rst:12
+# 8738288471674363afa921ecbaec1867
+msgid "Features of the OVS Plugin"
+msgstr ""
+
+#: ../../networking/ovs-plugin.rst:14
+# e2c0a6c8d2a54c11ab038aea7437ee1c
+msgid "The following table lists the CloudStack network services provided by the OVS Plugin."
+msgstr ""
+
+#: ../../networking/ovs-plugin.rst:22
+#: ../../networking/ovs-plugin.rst:24
+#: ../../networking/ovs-plugin.rst:26
+#: ../../networking/ovs-plugin.rst:41
+# 94b705d1919f42dc93ee3bde143cc9e4
+# a8bcd55c8af9483bab85a27e2e858463
+# c5adedbd9c034eebb5de1bd95a2782ad
+# d66b2462d1d74e5dba6272e9ca905e7b
+msgid ">= 4.3"
+msgstr ""
+
+#: ../../networking/ovs-plugin.rst:26
+#: ../../networking/ovs-plugin.rst:213
+# 1c98b0381c96437a88b133d8ac4fc504
+# 3870fad2a1c2490e91bada596aa92f94
+msgid "Load Balancing"
+msgstr ""
+
+#: ../../networking/ovs-plugin.rst:34
+# ab32a538a9b2476abf00b78f369ad247
+msgid "The following hypervisors are supported by the OVS Plugin."
+msgstr ""
+
+#: ../../networking/ovs-plugin.rst:48
+# d1f299f091ce45a3b5596dc0a9a978f1
+msgid "Configuring the OVS Plugin"
+msgstr ""
+
+#: ../../networking/ovs-plugin.rst:53
+# a5997f6fd754488ba5c92e4603cf1c1f
+msgid "Before enabling the OVS plugin the hypervisor needs to be install OpenvSwitch. Default, XenServer has already installed OpenvSwitch. However, you must install OpenvSwitch manually on KVM. CentOS 6.4 and OpenvSwitch 1.10 are recommended."
+msgstr ""
+
+#: ../../networking/ovs-plugin.rst:55
+# 42c5d4f701cd475f82263345ed2643f8
+msgid "KVM hypervisor:"
+msgstr ""
+
+#: ../../networking/ovs-plugin.rst:57
+# ff6b9ce75064465faf40f28294a4a4d2
+msgid "CentOS 6.4 is recommended."
+msgstr ""
+
+#: ../../networking/ovs-plugin.rst:58
+# aec6d4e64ef34c9785419abc0d40a4ff
+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 ""
+
+#: ../../networking/ovs-plugin.rst:64
+# 59bc3e26166b49929ac57352426c0e1b
+msgid "CloudStack needs to have at least one physical network with the isolation method set to “GRE”. This network should be enabled for the Guest traffic type."
+msgstr ""
+
+#: ../../networking/ovs-plugin.rst:69
+# 577a289d75244f688fe34676d433f6cf
+msgid "With KVM, the traffic type should be configured with the traffic label that matches the name of the Integration Bridge on the hypervisor. For example, you should set the traffic label as following: - Management & Storage traffic: cloudbr0 - Guest & Public traffic: cloudbr1 See KVM networking configuration guide for more detail."
+msgstr ""
+
+#: ../../networking/ovs-plugin.rst:81
+# 37d246b9af8c4143b25810d171f5673e
+msgid "Agent Configuration"
+msgstr ""
+
+#: ../../networking/ovs-plugin.rst:83
+# e95ef7c66b834737824020929e57a510
+msgid "Only for KVM hypervisor"
+msgstr ""
+
+#: ../../networking/ovs-plugin.rst:85
+# 198013b8c9c5432ab8c266399deacab1
+msgid "Configure network interfaces:"
+msgstr ""
+
+#: ../../networking/ovs-plugin.rst:133
+# 9af721992b2946409aef0299c78bef7e
+msgid "Edit /etc/cloudstack/agent/agent.properties"
+msgstr ""
+
+#: ../../networking/ovs-plugin.rst:143
+# 682ec9ff48d647e7a1202dcef28c0ee7
+msgid "The OVS provider is disabled by default. Navigate to the \"Network Service Providers\" configuration of the physical network with the GRE isolation type. Navigate to the OVS provider and press the \"Enable Provider\" button."
+msgstr ""
+
+#: ../../networking/ovs-plugin.rst:155
+# 840e28ff519d454cb23bab644b4b6ec2
+msgid "Using the OVS plugin requires a network offering with Virtual Networking enabled and configured to use the OVS element. Typical use cases combine services from the Virtual Router appliance and the OVS plugin."
+msgstr ""
+
+#: ../../networking/ovs-plugin.rst:171
+#: ../../networking/ovs-plugin.rst:177
+#: ../../networking/ovs-plugin.rst:179
+#: ../../networking/ovs-plugin.rst:181
+#: ../../networking/ovs-plugin.rst:209
+#: ../../networking/ovs-plugin.rst:211
+#: ../../networking/ovs-plugin.rst:213
+#: ../../networking/ovs-plugin.rst:215
+# 1d3b225edb8b482d8c582f632dc71313
+# ebdef897609040a283a250c5c1eb4151
+# b6ca83ff9ff7470ebc1a3af094449997
+# 32cdce0ada9d4fad837c1757dfe00cb6
+# cb5fd652d72044879d30e2b4818b3f15
+# c84ee4d20f7c48c488cbb6ed7a552ab3
+# dcc48e27341c45c2a35622f24fd2e194
+# f8560d7a491c4087a8e64879c3cb7d16
+msgid "OVS"
+msgstr ""
+
+#: ../../networking/ovs-plugin.rst:192
+# 849b742162ee49498b9dd99abddfcda0
+msgid "The tag in the network offering should be set to the name of the physical network with the OVS provider."
+msgstr ""
+
+#: ../../networking/ovs-plugin.rst:221
+# 231676daf7d6469585cec8201d618078
+msgid "Using the OVS plugin with VPC"
+msgstr ""
+
+#: ../../networking/ovs-plugin.rst:223
+# aa4e41d6c1444a668af3748de69e5281
+msgid "OVS plugin does not work with VPC at that time"
+msgstr ""
+
+#: ../../networking/ovs-plugin.rst:228
+# f8d4fdca37ad453c9e9d478e4bcd1e63
+msgid "0-0 Mon Dec 2 2013 Nguyen Anh Tu tuna@apache.org Documentation created for 4.3.0 version of the OVS Plugin"
+msgstr ""
+
+#: ../../networking/vxlan.rst:2
+# aba9a0debf774aa0944cb432adf8ef5d
+msgid "The VXLAN Plugin"
+msgstr ""
+
+#: ../../networking/vxlan.rst:5
+# 7e47773835b34f62b638c9063c13ac0d
+msgid "System Requirements for VXLAN"
+msgstr ""
+
+#: ../../networking/vxlan.rst:7
+# 0856b955a54e4897a16abb275756a9fd
+msgid "In PRODUCT 4.X.0, this plugin only supports the KVM hypervisor with the standard linux bridge."
+msgstr ""
+
+#: ../../networking/vxlan.rst:10
+# 3d2b1751d05a45d9a07403171f7f5925
+msgid "The following table lists the requirements for the hypervisor."
+msgstr ""
+
+#: ../../networking/vxlan.rst:13
+# cf661800742e45b78795a27fc183b902
+msgid "Item"
+msgstr ""
+
+#: ../../networking/vxlan.rst:13
+# 819ffab2f6da41e09ffcda38bcfe555e
+msgid "Requirement"
+msgstr ""
+
+#: ../../networking/vxlan.rst:13
+#: ../../networking/vxlan.rst:30
+# 43dad0f458fd4256af5210266203e63e
+# c2000a1583f74039ba4e81e33d1bfb4f
+msgid "Note"
+msgstr ""
+
+#: ../../networking/vxlan.rst:15
+# e5bde3c30dc5441eb12a4ec4b45e7060
+msgid "OvsVifDriver is not supported by this plugin in PRODUCT 4.X, use BridgeVifDriver (default)."
+msgstr ""
+
+#: ../../networking/vxlan.rst:17
+# 3911379ce0704038bd265efc35b968d5
+msgid "Linux kernel"
+msgstr ""
+
+#: ../../networking/vxlan.rst:17
+# 0481712b141d4f3e94139b17db34afd5
+msgid "version >= 3.7, VXLAN kernel module enabled"
+msgstr ""
+
+#: ../../networking/vxlan.rst:17
+# 09493271ea8b4c26b832bf6444ecc41c
+msgid "It is recommended to use kernel >=3.9, since Linux kernel categorizes the VXLAN driver as experimental <3.9."
+msgstr ""
+
+#: ../../networking/vxlan.rst:19
+# 5aeec29ada874c7399081093439a08b4
+msgid "iproute2"
+msgstr ""
+
+#: ../../networking/vxlan.rst:19
+# e8eb5592e8704feb9938a222c6bd37a9
+msgid "matches kernel version"
+msgstr ""
+
+#: ../../networking/vxlan.rst:22
+# 752c3ff3115d4533938927673fc8256e
+msgid "Table: Hypervisor Requirement for VXLAN"
+msgstr ""
+
+#: ../../networking/vxlan.rst:25
+# 972f006525e946c7a239d2ebaecca487
+msgid "Linux Distributions that meet the requirements"
+msgstr ""
+
+#: ../../networking/vxlan.rst:27
+# db3d7314090e428dbd26878e44b96698
+msgid "The following table lists distributions which meet requirements."
+msgstr ""
+
+#: ../../networking/vxlan.rst:30
+# e489f83c058d4843b0edddf4d5f7ed80
+msgid "Distribution"
+msgstr ""
+
+#: ../../networking/vxlan.rst:30
+# a6be099619614c06ac446220c77210a8
+msgid "Release Version"
+msgstr ""
+
+#: ../../networking/vxlan.rst:30
+# 7aa86d66ab7f4d9c8cf8188e6f9f021f
+msgid "Kernel Version (Date confirmed)"
+msgstr ""
+
+#: ../../networking/vxlan.rst:32
+# e9ecad2cccc74cb7aa00b46a5e3a0570
+msgid "Ubuntu"
+msgstr ""
+
+#: ../../networking/vxlan.rst:32
+# edbdd7c57081462e8d40ef0d9656151d
+msgid "13.04"
+msgstr ""
+
+#: ../../networking/vxlan.rst:32
+# 29f1312a9ae74bb99e6a7ec4c3693240
+msgid "3.8.0 (2013/07/23)"
+msgstr ""
+
+#: ../../networking/vxlan.rst:34
+# 5cd45188355b4d0eb21163ec4a720324
+msgid "Fedora"
+msgstr ""
+
+#: ../../networking/vxlan.rst:34
+# 34d9f4bac41e4a0691bcc15d3ee2468a
+msgid ">= 17"
+msgstr ""
+
+#: ../../networking/vxlan.rst:34
+# daff7db17c0042bb9cf674241df52912
+msgid "3.9.10 (2013/07/23)"
+msgstr ""
+
+#: ../../networking/vxlan.rst:34
+# 3008367b713047198803fa848a0ee4db
+msgid "Latest kernel packages are available in \"update\" repository."
+msgstr ""
+
+#: ../../networking/vxlan.rst:36
+# a2d7c1bb423341cca75ddda74037bdb1
+msgid "CentOS"
+msgstr ""
+
+#: ../../networking/vxlan.rst:36
+# 02acedd346e5464dbc4493b0f3ff205b
+msgid ">= 6.5"
+msgstr ""
+
+#: ../../networking/vxlan.rst:36
+# f87b94fed04c4aa6a0022f519a578d18
+msgid "2.6.32-431.3.1.el6.x86\\_64 (2014/01/21)"
+msgstr ""
+
+#: ../../networking/vxlan.rst:39
+# 164f35e12f76425285cbc95de79c38e9
+msgid "Table: List of Linux distributions which meet the hypervisor requirements"
+msgstr ""
+
+#: ../../networking/vxlan.rst:43
+# eca34e237e7347a982fefa12a663cc49
+msgid "Check the capability of your system"
+msgstr ""
+
+#: ../../networking/vxlan.rst:45
+# 23645375c0fe4e68a7096b4418965490
+msgid "To check the capability of your system, execute the following commands."
+msgstr ""
+
+#: ../../networking/vxlan.rst:59
+# 08ea45b15b224cedbd7c5b25ee9d8fb2
+msgid "Advanced: Build kernel and iproute2"
+msgstr ""
+
+#: ../../networking/vxlan.rst:61
+# 50467500d4d54ffe8e06d413c70fc679
+msgid "Even if your system doesn't support VXLAN, you can compile the kernel and iproute2 by yourself. The following procedure is an example for CentOS 6.4."
+msgstr ""
+
+#: ../../networking/vxlan.rst:66
+# 3cbc89b3e65049b5a8af5067dfd3b12f
+msgid "Build kernel"
+msgstr ""
+
+#: ../../networking/vxlan.rst:116
+# 96113e7068244ddcbc74d0628b23b864
+msgid "Build iproute2"
+msgstr ""
+
+#: ../../networking/vxlan.rst:134
+# 13971197a0884005b1bbec7e88751a55
+msgid "Please use rebuild kernel and tools at your own risk."
+msgstr ""
+
+#: ../../networking/vxlan.rst:137
+# 6082e428d1cb4b658d787c71d0ad1dd5
+msgid "Configure PRODUCT to use VXLAN Plugin"
+msgstr ""
+
+#: ../../networking/vxlan.rst:140
+# 51018b2e8a20496c95143f40c4c2e7b1
+msgid "Configure hypervisor"
+msgstr ""
+
+#: ../../networking/vxlan.rst:143
+# 1bda3ef5767243159c1f32723071aedf
+msgid "Configure hypervisor: KVM"
+msgstr ""
+
+#: ../../networking/vxlan.rst:145
+# 0b30975586c54132a8722bffbd37f88d
+msgid "In addition to \"KVM Hypervisor Host Installation\" in \"PRODUCT Installation Guide\", you have to configure the following item on the host."
+msgstr ""
+
+#: ../../networking/vxlan.rst:150
+# e86c1c67cbc246b284db4bdc68b79c64
+msgid "Create bridge interface with IPv4 address"
+msgstr ""
+
+#: ../../networking/vxlan.rst:152
+# 6856ea7ca74549fb91a97823fda39f40
+msgid "This plugin requires an IPv4 address on the KVM host to terminate and originate VXLAN traffic. The address should be assinged to a physical interface or a bridge interface bound to a physical interface. Both a private address or a public address are fine for the purpose. It is not required to be in the same subnet for all hypervisors in a zone, but they should be able to reach each other via IP multicast with UDP/8472 port. A name of a physical interface or a name of a bridge interface bound to a physical interface can be used as a traffic label. Physical interface name fits for almost all cases, but if physical interface name differs per host, you may use a bridge to set a same name. If you would like to use a bridge name as a traffic label, you may create a bridge in this way."
+msgstr ""
+
+#: ../../networking/vxlan.rst:165
+# 43bd2f0570fd4eaab96d1220d515286a
+msgid "Let ``cloudbr1`` be the bridge interface for the instances' private network."
+msgstr ""
+
+#: ../../networking/vxlan.rst:169
+#: ../../networking/vxlan.rst:288
+# 8ee47f12c6e140c29727a53e1411a9ff
+# a92bdc6a59d1445bb35f02ae1bbf2ff8
+msgid "Configure in RHEL or CentOS"
+msgstr ""
+
+#: ../../networking/vxlan.rst:171
+# 625b6babbbe14c7297b1db229a8e1bae
+msgid "When you configured the ``cloudbr1`` interface as below,"
+msgstr ""
+
+#: ../../networking/vxlan.rst:190
+#: ../../networking/vxlan.rst:246
+# 904e121f26a14fde81c4de98e7b24c0e
+# 6cf0b410f0a8449d8e65149baf7ce094
+msgid "you would change the configuration similar to below."
+msgstr ""
+
+#: ../../networking/vxlan.rst:207
+#: ../../networking/vxlan.rst:318
+# db9a28a25978461db08f0fdf995ea8c3
+# 00e194cf8c824537a2b5b8e26458dd30
+msgid "Configure in Ubuntu"
+msgstr ""
+
+#: ../../networking/vxlan.rst:209
+# 2a74cc1f2afd4082bdbf0ba50f6a629f
+msgid "When you configured ``cloudbr1`` as below,"
+msgstr ""
+
+#: ../../networking/vxlan.rst:282
+# cbe3d7f5a83f4d898797c7e80eb79049
+msgid "Configure iptables to pass XVLAN packets"
+msgstr ""
+
+#: ../../networking/vxlan.rst:284
+# 2f4c96bb0b4e40dfbdab9874f6891a33
+msgid "Since VXLAN uses UDP packet to forward encapsulated the L2 frames, UDP/8472 port must be opened."
+msgstr ""
+
+#: ../../networking/vxlan.rst:290
+# 22017b1c949f41099cfc19e25c2322c1
+msgid "RHEL and CentOS use iptables for firewalling the system, you can open extra ports by executing the following iptable commands:"
+msgstr ""
+
+#: ../../networking/vxlan.rst:298
+# 494b6216726d4b41ac1143c03c93ede2
+msgid "These iptable settings are not persistent accross reboots, we have to save them first."
+msgstr ""
+
+#: ../../networking/vxlan.rst:306
+#: ../../networking/vxlan.rst:332
+# e4c7fa92a9c0468e8da1450958c88fba
+# 65ea92e3dff5470387625254bb1c42db
+msgid "With this configuration you should be able to restart the network, although a reboot is recommended to see if everything works properly."
+msgstr ""
+
+#: ../../networking/vxlan.rst:315
+#: ../../networking/vxlan.rst:341
+# 2d1c77a3ce254c0eb8fac95e5895d8ae
+# 765412ce099b4da18bc65bc977dacabd
+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 ""
+
+#: ../../networking/vxlan.rst:320
+# 854fd1560d9344e8ac82043d2db28452
+msgid "The default firewall under Ubuntu is UFW (Uncomplicated FireWall), which is a Python wrapper around iptables."
+msgstr ""
+
+#: ../../networking/vxlan.rst:323
+# f90c18bbf2c14a2394917bc8afb0d9fe
+msgid "To open the required ports, execute the following commands:"
+msgstr ""
+
+#: ../../networking/vxlan.rst:330
+# 88a38bd1e33c46929e6fc18a9447362a
+msgid "By default UFW is not enabled on Ubuntu. Executing these commands with the firewall disabled does not enable the firewall."
+msgstr ""
+
+#: ../../networking/vxlan.rst:344
+# 55f975bbaf7f4dffa989e42598176360
+msgid "Setup zone using VXLAN"
+msgstr ""
+
+#: ../../networking/vxlan.rst:346
+# 151a7ea2c74744eeb7e1c0a2c6efa55e
+msgid "In almost all parts of zone setup, you can just follow the advanced zone setup istruction in \"PRODUCT Installation Guide\" to use this plugin. It is not required to add a network element nor to reconfigure the network offering. The only thing you have to do is configure the physical network to use VXLAN as the isolation method for Guest Network."
+msgstr ""
+
+#: ../../networking/vxlan.rst:353
+# b98161ffc6e94d978fedfabfa111e148
+msgid "Configure the physical network"
+msgstr ""
+
+#: ../../networking/vxlan.rst:357
+# 90b276bf94d1402aa0ee2596f2721705
+msgid "CloudStack needs to have one physical network for Guest Traffic with the isolation method set to \"VXLAN\"."
+msgstr ""
+
+#: ../../networking/vxlan.rst:362
+# 280cd3cc511c4f9da067fdd49db6975c
+msgid "Guest Network traffic label should be the name of the physical interface or the name of the bridge interface and the bridge interface and they should have an IPv4 address. See ? for details."
+msgstr ""
+
+#: ../../networking/vxlan.rst:367
+# d5a846d9f8a148b49d60346f4b1adfb5
+msgid "Configure the guest traffic"
+msgstr ""
+
+#: ../../networking/vxlan.rst:371
+# c1b08286a7fc47958c0620ea96d11201
+msgid "Specify a range of VNIs you would like to use for carrying guest network traffic."
+msgstr ""
+
+#: ../../networking/vxlan.rst:374
+# aa3c048fba4b4a53a4bb2e3016f33a1f
+msgid "VNI must be unique per zone and no duplicate VNIs can exist in the zone. Exercise care when designing your VNI allocation policy."
+msgstr ""
+

[4/6] setup i18n with transifex and sphinx-intl

[se...@apache.org]

http://git-wip-us.apache.org/repos/asf/cloudstack-docs/blob/7d6892fd/rtd/source/locale/pot/dev.pot
----------------------------------------------------------------------
diff --git a/rtd/source/locale/pot/dev.pot b/rtd/source/locale/pot/dev.pot
new file mode 100644
index 0000000..e97c9d1
--- /dev/null
+++ b/rtd/source/locale/pot/dev.pot
@@ -0,0 +1,2817 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2014, Apache CloudStack
+# This file is distributed under the same license as the Apache CloudStack package.
+# FIRST AUTHOR <EM...@ADDRESS>, YEAR.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: Apache CloudStack 4.3\n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2014-03-31 13:49-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"
+
+#: ../../dev.rst:2
+# 88f847a36ab24727950459a3432c0d4e
+msgid "Programmer Guide"
+msgstr ""
+
+#: ../../dev.rst:4
+# 0f57e8ddad1c42e484b86fabd6e7c7fd
+msgid "This guide shows how to develop CloudStack, use the API for operation and integration, access the usage data and use CloudStack specific tools to ease development, testing and integration."
+msgstr ""
+
+#: ../../dev.rst:9
+# b4dde114728d4a729b84dad8a71507ad
+msgid "The CloudStack API"
+msgstr ""
+
+#: ../../dev.rst:12
+# 2faafa276d4e4ec88166c7c604c83c2e
+msgid "Getting Started"
+msgstr ""
+
+#: ../../dev.rst:14
+# d2952855db3649debf7352fd97ca4dbd
+msgid "To get started using the CloudStack API, you should have the following:"
+msgstr ""
+
+#: ../../dev.rst:18
+# 6e34aa46096b49b5be7da378474756f6
+msgid "URL of the CloudStack server you wish to integrate with."
+msgstr ""
+
+#: ../../dev.rst:22
+# e20e5d4ce4794e1691532c2ae747fad4
+msgid "Both the API Key and Secret Key for an account. This should have been generated by the administrator of the cloud instance and given to you."
+msgstr ""
+
+#: ../../dev.rst:28
+# ce44c9141f7e47ab901755a829921fc4
+msgid "Familiarity with HTTP GET/POST and query strings."
+msgstr ""
+
+#: ../../dev.rst:32
+# 44afe433c3ba402592498a6d55054c3a
+msgid "Knowledge of either XML or JSON."
+msgstr ""
+
+#: ../../dev.rst:36
+# 8cc15fe3964b44f3bf7f5b081a63501a
+msgid "Knowledge of a programming language that can generate HTTP requests; for example, Java or PHP."
+msgstr ""
+
+#: ../../dev.rst:40
+# 0d1fd7417b374a92a6e8ff42c7de5f5f
+msgid "Roles"
+msgstr ""
+
+#: ../../dev.rst:42
+# a07a254a222b4b028ebfea899f24c427
+msgid "The CloudStack API supports three access roles:"
+msgstr ""
+
+#: ../../dev.rst:46
+# 392ae4bd66d64586966361344f43d7cb
+msgid "Root Admin. Access to all features of the cloud, including both virtual and physical resource management."
+msgstr ""
+
+#: ../../dev.rst:51
+# 37c6d4ae56ed4b8a9ad98403b5e5c96c
+msgid "Domain Admin. Access to only the virtual resources of the clouds that belong to the administrator’s domain."
+msgstr ""
+
+#: ../../dev.rst:56
+# b6ead3abd7c6436e98f8add08e0b6550
+msgid "User. Access to only the features that allow management of the user’s virtual instances, storage, and network."
+msgstr ""
+
+#: ../../dev.rst:60
+# d72c3200f2224e248b1fe29033daa2d8
+msgid "API Reference Documentation"
+msgstr ""
+
+#: ../../dev.rst:62
+# d579042449a446acbbc65afcb8262fe6
+msgid "You can find all the API reference documentation at the below site:"
+msgstr ""
+
+#: ../../dev.rst:64
+# bcdf9d282f994c9e9cfc62a64151533a
+msgid "`http://cloudstack.apache.org/docs/api/ <http://cloudstack.apache.org/docs/api/>`__"
+msgstr ""
+
+#: ../../dev.rst:68
+# fdfacdd621784fc297905261cad0e2b0
+msgid "Making API Requests"
+msgstr ""
+
+#: ../../dev.rst:70
+# e1e9b59b70534ede8be8075893d353bf
+msgid "All CloudStack API requests are submitted in the form of a HTTP GET/POST with an associated command and any parameters. A request is composed of the following whether in HTTP or HTTPS:"
+msgstr ""
+
+#: ../../dev.rst:76
+# c71e5c34c5184f5480acb14acce1b2fd
+msgid "CloudStack API URL: This is the web services API entry point(for example, http://www.cloud.com:8080/client/api)"
+msgstr ""
+
+#: ../../dev.rst:81
+# 4af664897d734c228901165674b5f9c9
+msgid "Command: The web services command you wish to execute, such as start a virtual machine or create a disk volume"
+msgstr ""
+
+#: ../../dev.rst:86
+# 8161421f5e1e4ce4995d92771ed5f337
+msgid "Parameters: Any additional required or optional parameters for the command"
+msgstr ""
+
+#: ../../dev.rst:89
+# e7a76dd2b0b44e78be07604e1c297fa6
+msgid "A sample API GET request looks like the following:"
+msgstr ""
+
+#: ../../dev.rst:93
+#: ../../dev.rst:218
+# 839ab4dd86ff46168b63999452785de2
+# 92503d159e174305aea2ec57b9970197
+msgid "http://localhost:8080/client/api?command=deployVirtualMachine&serviceOfferingId=1&diskOfferingId=1&templateId=2&zoneId=4&apiKey=miVr6X7u6bN_sdahOBpjNejPgEsT35eXq-jB8CG20YI3yaxXcgpyuaIRmFI_EJTVwZ0nUkkJbPmY3y2bciKwFQ&signature=Lxx1DM40AjcXU%2FcaiK8RAP0O1hU%3D"
+msgstr ""
+
+#: ../../dev.rst:95
+# c4dcb67b67be49aa97bf850855f2e570
+msgid "Or in a more readable format:"
+msgstr ""
+
+#: ../../dev.rst:108
+# 5658859b97f84f9fb99df745f03051dd
+msgid "The first line is the CloudStack API URL. This is the Cloud instance you wish to interact with."
+msgstr ""
+
+#: ../../dev.rst:111
+# cb39ff065be04c6d9928471bb0a63195
+msgid "The second line refers to the command you wish to execute. In our example, we are attempting to deploy a fresh new virtual machine. It is preceded by a (?) to separate itself from the CloudStack API URL."
+msgstr ""
+
+#: ../../dev.rst:115
+# f871421126304dc095187dd439c11227
+msgid "Lines 3-6 are the parameters for this given command. To see the command and its request parameters, please refer to the appropriate section in the CloudStack API documentation. Each parameter field-value pair (field=value) is preceded by an ampersand character (&)."
+msgstr ""
+
+#: ../../dev.rst:120
+# e21bba7a1c744465ad31aaac4e06e929
+msgid "Line 7 is the user API Key that uniquely identifies the account. See Signing API Requests on page 7."
+msgstr ""
+
+#: ../../dev.rst:123
+# e26911e8e5064274b96a833855baf9c1
+msgid "Line 8 is the signature hash created to authenticate the user account executing the API command."
+msgstr ""
+
+#: ../../dev.rst:127
+# cd3619220ee145afb7e0d7fe3d447341
+msgid "Signing API Requests"
+msgstr ""
+
+#: ../../dev.rst:129
+# 3e2a0ec5c9de4183869e2a5669dc91e6
+msgid "Whether you access the CloudStack API with HTTP or HTTPS, it must still be signed so that CloudStack can verify the caller has been authenticated and authorized to execute the command. Make sure that you have both the API Key and Secret Key provided by the CloudStack administrator for your account before proceeding with the signing process."
+msgstr ""
+
+#: ../../dev.rst:136
+# d443f5ac0cce419f98b4469aa4c74efc
+msgid "To show how to sign a request, we will re-use the previous example."
+msgstr ""
+
+#: ../../dev.rst:140
+# aae90ce3351a4bb8a5e8c0331cbf00cd
+msgid "http://http://localhost:8080/client/api?command=deployVirtualMachine&serviceOfferingId=1&diskOfferingId=1&templateId=2&zoneId=4&apiKey=miVr6X7u6bN_sdahOBpjNejPgEsT35eXq-jB8CG20YI3yaxXcgpyuaIRmFI_EJTVwZ0nUkkJbPmY3y2bciKwFQ&signature=Lxx1DM40AjcXU%2FcaiK8RAP0O1hU%3D"
+msgstr ""
+
+#: ../../dev.rst:142
+# 35dcfbf008ad4133ad5dc64fb30232fe
+msgid "Breaking this down, we have several distinct parts to this URL."
+msgstr ""
+
+#: ../../dev.rst:146
+# 6abafe49687f4dee8772fec806d0fbd0
+msgid "Base URL: This is the base URL to the CloudStack Management Server."
+msgstr ""
+
+#: ../../dev.rst:154
+# 502701cea95040dd901c250e2d0e8059
+msgid "API Path: This is the path to the API Servlet that processes the incoming requests."
+msgstr ""
+
+#: ../../dev.rst:163
+# 5fd2fb195663434b8eae0db2e905f7f3
+msgid "Command String: This part of the query string comprises of the command, its parameters, and the API Key that identifies the account."
+msgstr ""
+
+#: ../../dev.rst:166
+# 6d8b992821454cf78809f60e02caf972
+msgid "As with all query string parameters of field-value pairs, the \"field\""
+msgstr ""
+
+#: ../../dev.rst:167
+# 32e9c80b9e674a428009e106c65505ac
+msgid "component is case insensitive while all \"value\" values are case sensitive."
+msgstr ""
+
+#: ../../dev.rst:171
+# 833166ee436145508ce6902e1aeffc36
+msgid "command=deployVirtualMachine&serviceOfferingId=1&diskOfferingId=1&templateId=2&zoneId=4&apiKey=miVr6X7u6bN_sdahOBpjNejPgEsT35eXq-jB8CG20YI3yaxXcgpyuaIRmFI_EJTVwZ0nUkkJbPmY3y2bciKwFQ"
+msgstr ""
+
+#: ../../dev.rst:175
+# e0507ec466f2491b916cafe05332028e
+msgid "Signature: This is the signature of the command string that is generated using a combination of the user’s Secret Key and the HMAC SHA-1 hashing algorithm."
+msgstr ""
+
+#: ../../dev.rst:183
+# 56bc11e5a54743cead5ba505735d0f79
+msgid "Every API request has the format Base URL+API Path+Command String+Signature."
+msgstr ""
+
+#: ../../dev.rst:186
+# 66917cd0ddef4cbfa9969c8c62803fd5
+msgid "To generate the signature."
+msgstr ""
+
+#: ../../dev.rst:190
+# c1d626c724ca48c2bb66f26a7036f65c
+msgid "For each field-value pair (as separated by a '&') in the Command String, URL encode each value so that it can be safely sent via HTTP GET."
+msgstr ""
+
+#: ../../dev.rst:194
+# 849f31408097498fbc9fb864c4435713
+msgid "Make sure all spaces are encoded as \"%20\" rather than \"+\"."
+msgstr ""
+
+#: ../../dev.rst:198
+# 20123502d7d44283b033a23b098a6cd4
+msgid "Lower case the entire Command String and sort it alphabetically via the field for each field-value pair. The result of this step would look like the following."
+msgstr ""
+
+#: ../../dev.rst:207
+# 53d9f03880b24e7992cd7b942d23ecbc
+msgid "Take the sorted Command String and run it through the HMAC SHA-1 hashing algorithm (most programming languages offer a utility method to do this) with the user’s Secret Key. Base64 encode the resulting byte array in UTF-8 so that it can be safely transmitted via HTTP. The final string produced after Base64 encoding should be \"Lxx1DM40AjcXU%2FcaiK8RAP0O1hU%3D\"."
+msgstr ""
+
+#: ../../dev.rst:214
+# 20f9ee5f604b44fe82bf083906283ebc
+msgid "By reconstructing the final URL in the format Base URL+API Path+Command String+Signature, the final URL should look like:"
+msgstr ""
+
+#: ../../dev.rst:218
+# 2734f0e154c9498c9f65854c74d2b783
+msgid "::"
+msgstr ""
+
+#: ../../dev.rst:221
+# 3ce7bf410679444083db2b9723ce5a09
+msgid "How to sign an API call with Python"
+msgstr ""
+
+#: ../../dev.rst:223
+# 45495f340169452bbd9d83500c6b54d7
+msgid "To illustrate the procedure used to sign API calls we present a step by step interactive session using Python."
+msgstr ""
+
+#: ../../dev.rst:226
+# a9445dca7193488db115b1dd27e16395
+msgid "First import the required modules:"
+msgstr ""
+
+#: ../../dev.rst:241
+# 24398af487f5422ea5406e130f926fbe
+msgid "Define the endpoint of the Cloud, the command that you want to execute and the keys of the user."
+msgstr ""
+
+#: ../../dev.rst:254
+# b8f133da9e9845f584a2d15536349c5b
+msgid "Build the request string:"
+msgstr ""
+
+#: ../../dev.rst:263
+# dc2504e7f3ee48a6ba9653dbb4da0589
+msgid "Compute the signature with hmac, do a 64 bit encoding and a url encoding:"
+msgstr ""
+
+#: ../../dev.rst:285
+# f894c91edede40f89c0ad62bbb5248bc
+msgid "Finally, build the entire string and do an http GET:"
+msgstr ""
+
+#: ../../dev.rst:298
+# 1fce99e27cc64e45990fc200e6766c42
+msgid "Enabling API Call Expiration"
+msgstr ""
+
+#: ../../dev.rst:300
+# 9624c8d51175474abd13be2f82f22b03
+msgid "You can set an expiry timestamp on API calls to prevent replay attacks over non-secure channels, such as HTTP. The server tracks the expiry timestamp you have specified and rejects all the subsequent API requests that come in after this validity period."
+msgstr ""
+
+#: ../../dev.rst:305
+# 514e9deb7f1643fda9234008bffaa453
+msgid "To enable this feature, add the following parameters to the API request:"
+msgstr ""
+
+#: ../../dev.rst:309
+# 832359e119854ea5bb64af41c59b2258
+msgid "signatureVersion=3: If the signatureVersion parameter is missing or is not equal to 3, the expires parameter is ignored in the API request."
+msgstr ""
+
+#: ../../dev.rst:315
+# feb0edf3984b47e6bff184977e549c3a
+msgid "expires=YYYY-MM-DDThh:mm:ssZ: Specifies the date and time at which the signature included in the request is expired. The timestamp is expressed in the YYYY-MM-DDThh:mm:ssZ format, as specified in the ISO 8601 standard."
+msgstr ""
+
+#: ../../dev.rst:320
+# 486d0b76a367414699a9cf2679731557
+msgid "For example:"
+msgstr ""
+
+#: ../../dev.rst:326
+# e69f535ec1054617ba6b1f945568616d
+msgid "A sample API request with expiration is given below:"
+msgstr ""
+
+#: ../../dev.rst:330
+# cb3c57ee68b64c18a36b87f60302039e
+msgid "http://<IPAddress>:8080/client/api?command=listZones&signatureVersion=3&expires=2011-10-10T12:00:00+0530&apiKey=miVr6X7u6bN_sdahOBpjNejPgEsT35eXq-jB8CG20YI3yaxXcgpyuaIRmFI_EJTVwZ0nUkkJbPmY3y2bciKwFQ&signature=Lxx1DM40AjcXU%2FcaiK8RAP0O1hU%3D"
+msgstr ""
+
+#: ../../dev.rst:334
+# c4ce501303704bfca5c61ce887cb649d
+msgid "Limiting the Rate of API Requests"
+msgstr ""
+
+#: ../../dev.rst:336
+# 0efa32dc30464f9f84f8beaedac11307
+msgid "You can limit the rate at which API requests can be placed for each account. This is useful to avoid malicious attacks on the Management Server, prevent performance degradation, and provide fairness to all accounts."
+msgstr ""
+
+#: ../../dev.rst:341
+# 72c69812e9714487a4215ddf8895699d
+msgid "If the number of API calls exceeds the threshold, an error message is returned for any additional API calls. The caller will have to retry these API calls at another time."
+msgstr ""
+
+#: ../../dev.rst:346
+# 5bf3283a5a704f7d91d1c78dd39ca2d6
+msgid "Configuring the API Request Rate"
+msgstr ""
+
+#: ../../dev.rst:348
+# b20bb6dcdfa0405495e11fa07c1911a4
+msgid "To control the API request rate, use the following global configuration settings:"
+msgstr ""
+
+#: ../../dev.rst:353
+# 93448fd2551e4687864f59929f698391
+msgid "`api.throttling.enabled` - Enable/Disable API throttling. By default, this setting is false, so API throttling is not enabled."
+msgstr ""
+
+#: ../../dev.rst:358
+# d92963ed9fdc414199763fb36436dabf
+msgid "`api.throttling.interval` (in seconds) - Time interval during which the number of API requests is to be counted. When the interval has passed, the API count is reset to 0."
+msgstr ""
+
+#: ../../dev.rst:364
+# e226e0fe5d9f4905a28c7b087de7867f
+msgid "`api.throttling.max` - Maximum number of APIs that can be placed within the `api.throttling.interval` period."
+msgstr ""
+
+#: ../../dev.rst:369
+# ef2be420b80540f3a805c54f6308d99b
+msgid "`api.throttling.cachesize` - Cache size for storing API counters. Use a value higher than the total number of accounts managed by the cloud. One cache entry is needed for each account, to store the running API total for that account."
+msgstr ""
+
+#: ../../dev.rst:375
+# 57cca97fd0c641a28479d2225b0aed15
+msgid "Limitations on API Throttling"
+msgstr ""
+
+#: ../../dev.rst:377
+# 20ee349cff1142938abd48470a0ac379
+msgid "The following limitations exist in the current implementation of this feature."
+msgstr ""
+
+#: ../../dev.rst:380
+# 2d10220a408149aeaf19331f5fa06f93
+msgid "Even with these limitations, CloudStack is still able to effectively use"
+msgstr ""
+
+#: ../../dev.rst:381
+# 6f2e12e0cf55408ea86a8c65d298202a
+msgid "API throttling to avoid malicious attacks causing denial of service."
+msgstr ""
+
+#: ../../dev.rst:386
+# f0469961f74243e887c7e7b93b00b36d
+msgid "In a deployment with multiple Management Servers, the cache is not synchronized across them. In this case, CloudStack might not be able to ensure that only the exact desired number of API requests are allowed. In the worst case, the number of API calls that might be allowed is (number of Management Servers) \\* (api.throttling.max)."
+msgstr ""
+
+#: ../../dev.rst:394
+# a45bc58c314d41a3bc4016b34304248c
+msgid "The API commands resetApiLimit and getApiLimit are limited to the Management Server where the API is invoked."
+msgstr ""
+
+#: ../../dev.rst:398
+# ff3c016220c6457a8c596adbe284cb4e
+msgid "API Responses"
+msgstr ""
+
+#: ../../dev.rst:401
+# 15968f1e84944fb2abdb573b78b32727
+msgid "Response Formats: XML and JSON"
+msgstr ""
+
+#: ../../dev.rst:403
+# 9efb63e9197e421d94628f73f0cb03ac
+msgid "CloudStack supports two formats as the response to an API call. The default response is XML. If you would like the response to be in JSON, add `&response=json` to the Command String."
+msgstr ""
+
+#: ../../dev.rst:407
+# 177028ee76cd4d94b66b45d6ef644cb1
+msgid "The two response formats differ in how they handle blank fields. In JSON, if there is no value for a response field, it will not appear in the response. If all the fields were empty, there might be no response at all. In XML, even if there is no value to be returned, an empty field will be returned as a placeholder XML element."
+msgstr ""
+
+#: ../../dev.rst:413
+# 824259cd2e9a405598c12835bb76ecb8
+msgid "Sample XML Response:"
+msgstr ""
+
+#: ../../dev.rst:427
+# 97dd89cd0fee43c6a3cae91abccb2b78
+msgid "Sample JSON Response:"
+msgstr ""
+
+#: ../../dev.rst:446
+# 58212032f7154c1883e84432d8e4d731
+msgid "Maximum Result Pages Returned"
+msgstr ""
+
+#: ../../dev.rst:448
+# 7f37d69d4d574e64a9a8ab88ef46a41d
+msgid "For each cloud, there is a default upper limit on the number of results that any API command will return in a single page. This is to help prevent overloading the cloud servers and prevent DOS attacks. For example, if the page size limit is 500 and a command returns 10,000 results, the command will return 20 pages."
+msgstr ""
+
+#: ../../dev.rst:454
+# efbf23a9cd034a62ab0615e69055eca7
+msgid "The default page size limit can be different for each cloud. It is set in the global configuration parameter `default.page.size`. If your cloud has many users with lots of VMs, you might need to increase the value of this parameter. At the same time, be careful not to set it so high that your site can be taken down by an enormous return from an API call. For more information about how to set global configuration parameters, see \"Describe Your Deployment\" in the Installation Guide."
+msgstr ""
+
+#: ../../dev.rst:462
+# 0265adcbb3e04c42ad6b93eba4793e37
+msgid "To decrease the page size limit for an individual API command, override the global setting with the page and pagesize parameters, which are available in any list\\* command (listCapabilities, listDiskOfferings, etc.)."
+msgstr ""
+
+#: ../../dev.rst:469
+# 85f5e1e695134081a55593c632d76fd3
+msgid "Both parameters must be specified together."
+msgstr ""
+
+#: ../../dev.rst:473
+# a1d697103c2d4059b7ce8e1ee7f22d46
+msgid "The value of the pagesize parameter must be smaller than the value of default.page.size. That is, you can not increase the number of possible items in a result page, only decrease it."
+msgstr ""
+
+#: ../../dev.rst:477
+# d6ed74d6611848a290eb5fb93eee5c6f
+msgid "For syntax information on the list\\* commands, see the API Reference."
+msgstr ""
+
+#: ../../dev.rst:480
+# 5bcdc2f0b4454ad1ac6b3733f52eac9b
+msgid "Error Handling"
+msgstr ""
+
+#: ../../dev.rst:482
+# 916ce269074b4dbb8c87b25f9013d681
+msgid "If an error occurs while processing an API request, the appropriate response in the format specified is returned. Each error response consists of an error code and an error text describing what possibly can go wrong. Below is a list of possible error codes:"
+msgstr ""
+
+#: ../../dev.rst:487
+# 66c32999ce2a406ba8eb54f875480eb3
+msgid "You can now find the CloudStack-specific error code in the exception response for each type of exception. The following list of error codes is added to the new class named CSExceptionErrorCode."
+msgstr ""
+
+#: ../../dev.rst:491
+# ccebf00b44ad4eb3a4215373acb07b44
+msgid "4250 : \"com.cloud.utils.exception.CloudRuntimeException\""
+msgstr ""
+
+#: ../../dev.rst:493
+# ed256ade3d414e38979e51608aa2801d
+msgid "4255 : \"com.cloud.utils.exception.ExceptionUtil\""
+msgstr ""
+
+#: ../../dev.rst:495
+# ed0d3d0b1d4b49ae85d70de2ad5d7e62
+msgid "4260 : \"com.cloud.utils.exception.ExecutionException\""
+msgstr ""
+
+#: ../../dev.rst:497
+# 11dbbbbb5d9e467484d307bccb64880d
+msgid "4265 : \"com.cloud.utils.exception.HypervisorVersionChangedException\""
+msgstr ""
+
+#: ../../dev.rst:499
+# 55e75631973241099121d893bfa860cd
+msgid "4270 : \"com.cloud.utils.exception.RuntimeCloudException\""
+msgstr ""
+
+#: ../../dev.rst:501
+# 65da6007d7254cb289c2091ee83ab2d7
+msgid "4275 : \"com.cloud.exception.CloudException\""
+msgstr ""
+
+#: ../../dev.rst:503
+# f131941c3b794e56978128a95bc282fc
+msgid "4280 : \"com.cloud.exception.AccountLimitException\""
+msgstr ""
+
+#: ../../dev.rst:505
+# 4e613b7caeb94249a8a341b3b9074a88
+msgid "4285 : \"com.cloud.exception.AgentUnavailableException\""
+msgstr ""
+
+#: ../../dev.rst:507
+# e9df4f85e8ad4785a8e557c376fdf043
+msgid "4290 : \"com.cloud.exception.CloudAuthenticationException\""
+msgstr ""
+
+#: ../../dev.rst:509
+# 4504f51121f74de0a8639ffcfc17e0c9
+msgid "4295 : \"com.cloud.exception.CloudExecutionException\""
+msgstr ""
+
+#: ../../dev.rst:511
+# 265aea8998a24d649fa88365c8bd2f15
+msgid "4300 : \"com.cloud.exception.ConcurrentOperationException\""
+msgstr ""
+
+#: ../../dev.rst:513
+# e2d91e1ac20a4cadaa1b971c4c7ff3fe
+msgid "4305 : \"com.cloud.exception.ConflictingNetworkSettingsException\""
+msgstr ""
+
+#: ../../dev.rst:515
+# 9421e3203b5b4e1c847bffbbf5a9bbe4
+msgid "4310 : \"com.cloud.exception.DiscoveredWithErrorException\""
+msgstr ""
+
+#: ../../dev.rst:517
+# bed8f76dc0cf41d387694eeda72d4365
+msgid "4315 : \"com.cloud.exception.HAStateException\""
+msgstr ""
+
+#: ../../dev.rst:519
+# 3d66fe1fbad84905a0267f4c81df270a
+msgid "4320 : \"com.cloud.exception.InsufficientAddressCapacityException\""
+msgstr ""
+
+#: ../../dev.rst:521
+# 762132c12835488abe023b285ddaaaf0
+msgid "4325 : \"com.cloud.exception.InsufficientCapacityException\""
+msgstr ""
+
+#: ../../dev.rst:523
+# ca329206e01944308f28c189618e1ca5
+msgid "4330 : \"com.cloud.exception.InsufficientNetworkCapacityException\""
+msgstr ""
+
+#: ../../dev.rst:525
+# 842cd2cceb2f4beead8fba9b3ff8eb16
+msgid "4335 : \"com.cloud.exception.InsufficientServerCapacityException\""
+msgstr ""
+
+#: ../../dev.rst:527
+# 0436b78cc6ef458992b9308f1c35e12c
+msgid "4340 : \"com.cloud.exception.InsufficientStorageCapacityException\""
+msgstr ""
+
+#: ../../dev.rst:529
+# 57175a79979a460d86c7c40cee15441c
+msgid "4345 : \"com.cloud.exception.InternalErrorException\""
+msgstr ""
+
+#: ../../dev.rst:531
+# 99c3e63e69d941368c3b155918669905
+msgid "4350 : \"com.cloud.exception.InvalidParameterValueException\""
+msgstr ""
+
+#: ../../dev.rst:533
+# fa28472261294bc39d5a70a149f7ad11
+msgid "4355 : \"com.cloud.exception.ManagementServerException\""
+msgstr ""
+
+#: ../../dev.rst:535
+# a3deb030592844e5a9cd5bcd4f04ae31
+msgid "4360 : \"com.cloud.exception.NetworkRuleConflictException\""
+msgstr ""
+
+#: ../../dev.rst:537
+# fa6bfc0a9f894c3a99ff80b18ac8eed4
+msgid "4365 : \"com.cloud.exception.PermissionDeniedException\""
+msgstr ""
+
+#: ../../dev.rst:539
+# 9c9b5d4e5be2488691ec292bbf274c44
+msgid "4370 : \"com.cloud.exception.ResourceAllocationException\""
+msgstr ""
+
+#: ../../dev.rst:541
+# a6bd0b470fb347df81cd0c05972ffdf5
+msgid "4375 : \"com.cloud.exception.ResourceInUseException\""
+msgstr ""
+
+#: ../../dev.rst:543
+# 9a964f1cede94d71a70f71335abdb3c4
+msgid "4380 : \"com.cloud.exception.ResourceUnavailableException\""
+msgstr ""
+
+#: ../../dev.rst:545
+# 6651d4a6e3934a62acfdabcb4cb54861
+msgid "4385 : \"com.cloud.exception.StorageUnavailableException\""
+msgstr ""
+
+#: ../../dev.rst:547
+# 7b33be0641984ca4a244e4e72ecc25ee
+msgid "4390 : \"com.cloud.exception.UnsupportedServiceException\""
+msgstr ""
+
+#: ../../dev.rst:549
+# cc42b4fc26144e9591c1994a14433387
+msgid "4395 : \"com.cloud.exception.VirtualMachineMigrationException\""
+msgstr ""
+
+#: ../../dev.rst:551
+# d1b52de5031041a49c255578c83d3066
+msgid "4400 : \"com.cloud.exception.AccountLimitException\""
+msgstr ""
+
+#: ../../dev.rst:553
+# 62c4d7f5e4c4497085dd6408ed374de8
+msgid "4405 : \"com.cloud.exception.AgentUnavailableException\""
+msgstr ""
+
+#: ../../dev.rst:555
+# 8a8742dbe79a4f4f9cc57806a91dd668
+msgid "4410 : \"com.cloud.exception.CloudAuthenticationException\""
+msgstr ""
+
+#: ../../dev.rst:557
+# e6bc37bad0c24deeb12e990e5d2d9846
+msgid "4415 : \"com.cloud.exception.CloudException\""
+msgstr ""
+
+#: ../../dev.rst:559
+# 29bdcde3a3824b758d135a6556a23400
+msgid "4420 : \"com.cloud.exception.CloudExecutionException\""
+msgstr ""
+
+#: ../../dev.rst:561
+# 4026eb49a4b84d2abca965c0a9fba59d
+msgid "4425 : \"com.cloud.exception.ConcurrentOperationException\""
+msgstr ""
+
+#: ../../dev.rst:563
+# 79ca0947ecda4b5bb1a7bfe6daf43fb9
+msgid "4430 : \"com.cloud.exception.ConflictingNetworkSettingsException\""
+msgstr ""
+
+#: ../../dev.rst:565
+# 687ea642c68f42ba98a5db0263593ac2
+msgid "4435 : \"com.cloud.exception.ConnectionException\""
+msgstr ""
+
+#: ../../dev.rst:567
+# 8a6eafd640a04650ba06e78b3d1d0fb7
+msgid "4440 : \"com.cloud.exception.DiscoveredWithErrorException\""
+msgstr ""
+
+#: ../../dev.rst:569
+# 444014c160aa4020887cfa88de787f72
+msgid "4445 : \"com.cloud.exception.DiscoveryException\""
+msgstr ""
+
+#: ../../dev.rst:571
+# 99f689ad42894544b243accb4ce0575f
+msgid "4450 : \"com.cloud.exception.HAStateException\""
+msgstr ""
+
+#: ../../dev.rst:573
+# c70428b1eaf6453fa93427732c5084fb
+msgid "4455 : \"com.cloud.exception.InsufficientAddressCapacityException\""
+msgstr ""
+
+#: ../../dev.rst:575
+# df47d21577f843c7a08f97fe35c4b2ba
+msgid "4460 : \"com.cloud.exception.InsufficientCapacityException\""
+msgstr ""
+
+#: ../../dev.rst:577
+# 55edef8ad41a404e82248b1a84037b8f
+msgid "4465 : \"com.cloud.exception.InsufficientNetworkCapacityException\""
+msgstr ""
+
+#: ../../dev.rst:579
+# ff2df775bee341c1a76830cea07f961e
+msgid "4470 : \"com.cloud.exception.InsufficientServerCapacityException\""
+msgstr ""
+
+#: ../../dev.rst:581
+# e67dd04cf5a54cb38a565390d3826d6d
+msgid "4475 : \"com.cloud.exception.InsufficientStorageCapacityException\""
+msgstr ""
+
+#: ../../dev.rst:583
+# b9d6b1ef0f3d452eaef2b46177152cf6
+msgid "4480 : \"com.cloud.exception.InsufficientVirtualNetworkCapcityException\""
+msgstr ""
+
+#: ../../dev.rst:585
+# 3cbb6383b39f44e2b85fbb4254bf68bb
+msgid "4485 : \"com.cloud.exception.InternalErrorException\""
+msgstr ""
+
+#: ../../dev.rst:587
+# 67b8b777ef2040478db5c426e0b2f3a4
+msgid "4490 : \"com.cloud.exception.InvalidParameterValueException\""
+msgstr ""
+
+#: ../../dev.rst:589
+# dca641bdb0584421b4b791107452c489
+msgid "4495 : \"com.cloud.exception.ManagementServerException\""
+msgstr ""
+
+#: ../../dev.rst:591
+# 8f1377661f654d838990891fcae375b0
+msgid "4500 : \"com.cloud.exception.NetworkRuleConflictException\""
+msgstr ""
+
+#: ../../dev.rst:593
+# 3082fbc9cb744b37927d3b3e86431091
+msgid "4505 : \"com.cloud.exception.PermissionDeniedException\""
+msgstr ""
+
+#: ../../dev.rst:595
+# ae210e7072ee49f7bf0ac85d099851e5
+msgid "4510 : \"com.cloud.exception.ResourceAllocationException\""
+msgstr ""
+
+#: ../../dev.rst:597
+# 7497da0b15ca4f64a1ce434ccf1099b8
+msgid "4515 : \"com.cloud.exception.ResourceInUseException\""
+msgstr ""
+
+#: ../../dev.rst:599
+# 8efb71e351de4403a66a04382f40a873
+msgid "4520 : \"com.cloud.exception.ResourceUnavailableException\""
+msgstr ""
+
+#: ../../dev.rst:601
+# 811f5d8995f54d72a2fa1c09d0720bc7
+msgid "4525 : \"com.cloud.exception.StorageUnavailableException\""
+msgstr ""
+
+#: ../../dev.rst:603
+# 7dd4324f99194117890076e5bab85c37
+msgid "4530 : \"com.cloud.exception.UnsupportedServiceException\""
+msgstr ""
+
+#: ../../dev.rst:605
+# 1a6ba33177d5419c9d3feed1f6ab0aca
+msgid "4535 : \"com.cloud.exception.VirtualMachineMigrationException\""
+msgstr ""
+
+#: ../../dev.rst:607
+# 8eefebfb00ee405abce8f9a00d2ce812
+msgid "9999 : \"org.apache.cloudstack.api.ServerApiException\""
+msgstr ""
+
+#: ../../dev.rst:609
+# 5318790ebacb45cb81706d1aa5b0ec4b
+msgid "An HTTP error code of 401 is always returned if API request was rejected due to bad signatures, missing API Keys, or the user simply did not have the permissions to execute the command."
+msgstr ""
+
+#: ../../dev.rst:614
+# b084cf11fe95484aa67688b00c8361b8
+msgid "Asynchronous Commands"
+msgstr ""
+
+#: ../../dev.rst:616
+# 8704f9a4fde4479ebca7b958ee9ea9fa
+msgid "Asynchronous commands were introduced in CloudStack 2.x. Commands are designated as asynchronous when they can potentially take a long period of time to complete such as creating a snapshot or disk volume. They differ from synchronous commands by the following:"
+msgstr ""
+
+#: ../../dev.rst:623
+# 17dd9ece69d74a08af583815c6938a2b
+msgid "They are identified in the API Reference by an (A)."
+msgstr ""
+
+#: ../../dev.rst:627
+# faf96453a5d9414f93cd2ceec901d1b3
+msgid "They will immediately return a job ID to refer to the job that will be responsible in processing the command."
+msgstr ""
+
+#: ../../dev.rst:632
+# 3567f44c20fd40fabaa906479c1ea490
+msgid "If executed as a \"create\" resource command, it will return the resource ID as well as the job ID."
+msgstr ""
+
+#: ../../dev.rst:635
+# cb1f99a392db43a990c7eb63bc00e600
+msgid "You can periodically check the status of the job by making a simple API call to the command, `queryAsyncJobResult` and passing in the job ID."
+msgstr ""
+
+#: ../../dev.rst:640
+# db2db81abce24e009335f15e6c0db86f
+msgid "Job Status"
+msgstr ""
+
+#: ../../dev.rst:642
+# 7fe5da2e577b4ecaa7d1e16cb76d3117
+msgid "The key to using an asynchronous command is the job ID that is returned immediately once the command has been executed. With the job ID, you can periodically check the job status by making calls to queryAsyncJobResult command. The command will return three possible job status integer values:"
+msgstr ""
+
+#: ../../dev.rst:650
+# 2ede3d8a734b40d691b99e058ef4c94c
+msgid "0 - Job is still in progress. Continue to periodically poll for any status changes."
+msgstr ""
+
+#: ../../dev.rst:655
+# 64e0214bb67c4717b6b3c18109d38f0d
+msgid "1 - Job has successfully completed. The job will return any successful response values associated with command that was originally executed."
+msgstr ""
+
+#: ../../dev.rst:661
+# c35e1393c870448fb9ab896f0ff1e7eb
+msgid "2 - Job has failed to complete. Please check the \"jobresultcode\" tag for failure reason code and \"jobresult\" for the failure reason."
+msgstr ""
+
+#: ../../dev.rst:665
+# 3667e152b1f1432fbd13a0805138b39f
+msgid "Example"
+msgstr ""
+
+#: ../../dev.rst:667
+# b86f8fe120ea4e979bd0f140876f85cc
+msgid "The following shows an example of using an asynchronous command. Assume the API command:"
+msgstr ""
+
+#: ../../dev.rst:674
+# f2282484364642e197b91d6a86328513
+msgid "CloudStack will immediately return a job ID and any other additional data."
+msgstr ""
+
+#: ../../dev.rst:684
+# 335a315726c743f4898691c4e3f1ac78
+msgid "Using the job ID, you can periodically poll for the results by using the queryAsyncJobResult command."
+msgstr ""
+
+#: ../../dev.rst:691
+# 3c14ddbd950048a0a91b9e3883c711ff
+msgid "Three possible results could come from this query."
+msgstr ""
+
+#: ../../dev.rst:693
+# ab8d636b7eee440199c9d60d4c319d16
+msgid "Job is still pending:"
+msgstr ""
+
+#: ../../dev.rst:703
+# 3f89d22e928242f88bcc14721c7323f3
+msgid "Job has succeeded:"
+msgstr ""
+
+#: ../../dev.rst:757
+# cd3a69591de442d0bf5f0d300459402d
+msgid "Job has failed:"
+msgstr ""
+
+#: ../../dev.rst:772
+# 4fd111a3a74b4dc38f376af537acdb93
+msgid "Event Types"
+msgstr ""
+
+#: ../../dev.rst:775
+# 477d5dc73bfe41ad9c7eda2987ac5e85
+msgid "Types"
+msgstr ""
+
+#: ../../dev.rst:775
+# fa4d32c97cf544f9b3cf3f47187c6155
+msgid "Events"
+msgstr ""
+
+#: ../../dev.rst:777
+# 2ff2614b2a7b42488d9a425b1803b899
+msgid "VM"
+msgstr ""
+
+#: ../../dev.rst:777
+# 087b18b695a14ce98e9f093181181a80
+msgid "VM.CREATE"
+msgstr ""
+
+#: ../../dev.rst:779
+# 14dece28da0f4b12b4ebee77a028b033
+msgid "VM.DESTROY"
+msgstr ""
+
+#: ../../dev.rst:781
+# c2dcbb7f0ff74f3ab392f306338c5a7c
+msgid "VM.START"
+msgstr ""
+
+#: ../../dev.rst:783
+# 1da7e95ff42941d79420631065b78e36
+msgid "VM.STOP"
+msgstr ""
+
+#: ../../dev.rst:785
+# 21d3b2775cdf4f1d8d95b8a6091c29af
+msgid "VM.REBOOT"
+msgstr ""
+
+#: ../../dev.rst:787
+# 99de318cd5794f7b812164f36c9b41d0
+msgid "VM.UPDATE"
+msgstr ""
+
+#: ../../dev.rst:789
+# a84b920924934dd88d9e6a382cc76748
+msgid "VM.UPGRADE"
+msgstr ""
+
+#: ../../dev.rst:791
+# ef5fd09876944c13bf2089f20759f460
+msgid "VM.DYNAMIC.SCALE"
+msgstr ""
+
+#: ../../dev.rst:793
+# 98d863622caa45cabc5e91577c9af8f2
+msgid "VM.RESETPASSWORD"
+msgstr ""
+
+#: ../../dev.rst:795
+# 9a2ca792849c47ddbb2e1fe34bf96718
+msgid "VM.RESETSSHKEY"
+msgstr ""
+
+#: ../../dev.rst:797
+# 7fe6dddc53d74a458c7b06b548bbb0ab
+msgid "VM.MIGRATE"
+msgstr ""
+
+#: ../../dev.rst:799
+# f5bb29d40e5942e49a4f38bd8bc947a6
+msgid "VM.MOVE"
+msgstr ""
+
+#: ../../dev.rst:801
+# 1cf27c3b2adf4078b1bed7b82f6b1754
+msgid "VM.RESTORE"
+msgstr ""
+
+#: ../../dev.rst:803
+# 6cc42b9032264e4aa02b906b78e308a6
+msgid "Domain Router"
+msgstr ""
+
+#: ../../dev.rst:803
+# b5bf7240eb1848bf929535a8ce5e45d1
+msgid "ROUTER.CREATE"
+msgstr ""
+
+#: ../../dev.rst:805
+# e170804cd908478f88cabdbca054d215
+msgid "ROUTER.DESTROY"
+msgstr ""
+
+#: ../../dev.rst:807
+# 4ed310f34c2547f68c21efc7c7dfb3d8
+msgid "ROUTER.START"
+msgstr ""
+
+#: ../../dev.rst:809
+# 8ee01c4eb9b542ad85537c42c720d8b3
+msgid "ROUTER.STOP"
+msgstr ""
+
+#: ../../dev.rst:811
+# 620890a493944dd183ee1edbe2356449
+msgid "ROUTER.REBOOT"
+msgstr ""
+
+#: ../../dev.rst:813
+# 64f00d974f9d46c1a43ffce7cfc00d07
+msgid "ROUTER.HA"
+msgstr ""
+
+#: ../../dev.rst:815
+# b8c151857e26407ba93493cdce5d0cab
+msgid "ROUTER.UPGRADE"
+msgstr ""
+
+#: ../../dev.rst:817
+# a8772cc955ca464488f7d6de1d1e0d41
+msgid "Console proxy"
+msgstr ""
+
+#: ../../dev.rst:817
+# db641bb0472546a5883f7ea1b0c3b1f2
+msgid "PROXY.CREATE"
+msgstr ""
+
+#: ../../dev.rst:819
+# 534375819956448dbcfb6f8c17e2e77b
+msgid "PROXY.DESTROY"
+msgstr ""
+
+#: ../../dev.rst:821
+# 6cf282d189704578820f8b28fa73ebbc
+msgid "PROXY.START"
+msgstr ""
+
+#: ../../dev.rst:823
+# 8634f9c421e64dbfb4106108e59aa3eb
+msgid "PROXY.STOP"
+msgstr ""
+
+#: ../../dev.rst:825
+# ae0139513aa74deaa2d6533b357b55b0
+msgid "PROXY.REBOOT"
+msgstr ""
+
+#: ../../dev.rst:827
+# 3729e7afd0224ed3b105aebc7750df28
+msgid "PROXY.HA"
+msgstr ""
+
+#: ../../dev.rst:829
+# 03afd42a6ff24a45bc315f2a514eb9c5
+msgid "VNC Console Events"
+msgstr ""
+
+#: ../../dev.rst:829
+# ea07e9e5008446a7b7f08e25faf8a0cb
+msgid "VNC.CONNECT"
+msgstr ""
+
+#: ../../dev.rst:831
+# 0e78144836de4034ae415843728c6cac
+msgid "VNC.DISCONNECT"
+msgstr ""
+
+#: ../../dev.rst:833
+# b4e9ed895d6f44aaa84461bc939dbfc2
+msgid "Network Events"
+msgstr ""
+
+#: ../../dev.rst:833
+# e32578c6790e4694a736931b06b7ff38
+msgid "NET.IPASSIGN"
+msgstr ""
+
+#: ../../dev.rst:835
+# 66e20530b70b480e9e08a4727320b69e
+msgid "NET.IPRELEASE"
+msgstr ""
+
+#: ../../dev.rst:837
+# edd59ba63ff5451aa0c5668101c6d3c1
+msgid "PORTABLE.IPASSIGN"
+msgstr ""
+
+#: ../../dev.rst:839
+# 3fbfe209784043f1bb38ca9a42e17d72
+msgid "PORTABLE.IPRELEASE"
+msgstr ""
+
+#: ../../dev.rst:841
+# dd097f8a6e10461cb34b90d4587fbbc9
+msgid "NET.RULEADD"
+msgstr ""
+
+#: ../../dev.rst:843
+# 7abbc44cd8c94daeaaa8e243967ebb86
+msgid "NET.RULEDELETE"
+msgstr ""
+
+#: ../../dev.rst:845
+# 8b6decb3262a43a4a90b330d68c3913e
+msgid "NET.RULEMODIFY"
+msgstr ""
+
+#: ../../dev.rst:847
+# 1ef01bed0801421596a29a58d7e1d868
+msgid "NETWORK.CREATE"
+msgstr ""
+
+#: ../../dev.rst:849
+# 5fa56b58104442028954e0ddd1c67caf
+msgid "NETWORK.DELETE"
+msgstr ""
+
+#: ../../dev.rst:851
+# 57ebc3932bea4adb9f234f0f901937dc
+msgid "NETWORK.UPDATE"
+msgstr ""
+
+#: ../../dev.rst:853
+# 56b89fb2707e4da9949d6052d3ad61f3
+msgid "FIREWALL.OPEN"
+msgstr ""
+
+#: ../../dev.rst:855
+# afb1aacc89014c62bb0ade25fe8e0915
+msgid "FIREWALL.CLOSE"
+msgstr ""
+
+#: ../../dev.rst:857
+# 973a258897ba41a7a0ad1ab2aca396ce
+msgid "NIC Events"
+msgstr ""
+
+#: ../../dev.rst:857
+# d2804a9e8a0b42208bcb06eb85ad66ea
+msgid "NIC.CREATE"
+msgstr ""
+
+#: ../../dev.rst:859
+# 47bb842256964eaa80aa949409ac2528
+msgid "NIC.DELETE"
+msgstr ""
+
+#: ../../dev.rst:861
+# f13c5ecd11584efbbfb32d2a5fc7060f
+msgid "NIC.UPDATE"
+msgstr ""
+
+#: ../../dev.rst:863
+# 7ef0554c83ba4b0ba7f7a8dad3102914
+msgid "NIC.DETAIL.ADD"
+msgstr ""
+
+#: ../../dev.rst:865
+# c31611b4c4fa481886c165977ec2c1da
+msgid "NIC.DETAIL.UPDATE"
+msgstr ""
+
+#: ../../dev.rst:867
+# dcb91cb2687d4a168a875c38d674eabc
+msgid "NIC.DETAIL.REMOVE"
+msgstr ""
+
+#: ../../dev.rst:869
+# 2fb546bc324249b3895856f3949ff5b0
+msgid "Load Balancers"
+msgstr ""
+
+#: ../../dev.rst:869
+# c1726be0d0774ac6aa26a79118127d5c
+msgid "LB.ASSIGN.TO.RULE"
+msgstr ""
+
+#: ../../dev.rst:871
+# 09da0eaa1af146e38148140c2efd9a9a
+msgid "LB.REMOVE.FROM.RULE"
+msgstr ""
+
+#: ../../dev.rst:873
+# 635428fd7a664b51a8ebea428855ce66
+msgid "LB.CREATE"
+msgstr ""
+
+#: ../../dev.rst:875
+# 7a4a8b841e0341e7a22243fe6c6e1dcd
+msgid "LB.DELETE"
+msgstr ""
+
+#: ../../dev.rst:877
+# ee971ca17057454f97e33187982f550b
+msgid "LB.STICKINESSPOLICY.CREATE"
+msgstr ""
+
+#: ../../dev.rst:879
+# c2393b5d398b49bc85f1866098a4a4fc
+msgid "LB.STICKINESSPOLICY.DELETE"
+msgstr ""
+
+#: ../../dev.rst:881
+# 35260a926bd14945934522a2b2d715a2
+msgid "LB.HEALTHCHECKPOLICY.CREATE"
+msgstr ""
+
+#: ../../dev.rst:883
+# b92f67d67c15428b9a147f11698da158
+msgid "LB.HEALTHCHECKPOLICY.DELETE"
+msgstr ""
+
+#: ../../dev.rst:885
+# 003d3810251843e9b4c82fe606be43af
+msgid "LB.UPDATE"
+msgstr ""
+
+#: ../../dev.rst:887
+# 464a1cde83014f9aa3faa7c99d77625c
+msgid "Global Load Balancer rules"
+msgstr ""
+
+#: ../../dev.rst:887
+# 41b26bff91d84bb2b2139d7fdc9d33eb
+msgid "GLOBAL.LB.ASSIGN"
+msgstr ""
+
+#: ../../dev.rst:889
+# 3ac45158cb2d4912a974f0984fa0a7fa
+msgid "GLOBAL.LB.REMOVE"
+msgstr ""
+
+#: ../../dev.rst:891
+# c9427518c3d34703b95f6eb252443f6d
+msgid "GLOBAL.LB.CREATE"
+msgstr ""
+
+#: ../../dev.rst:893
+# 72e796805a5645538a36c5f8cffd203e
+msgid "GLOBAL.LB.DELETE"
+msgstr ""
+
+#: ../../dev.rst:895
+# e64dd258f032416fa873cc2ec7168c6a
+msgid "GLOBAL.LB.UPDATE"
+msgstr ""
+
+#: ../../dev.rst:897
+# f159d834b1164c2aa3271730dffe0969
+msgid "Account events"
+msgstr ""
+
+#: ../../dev.rst:897
+# c03a996579ca498db0ab5dbaa26de6e0
+msgid "ACCOUNT.ENABLE"
+msgstr ""
+
+#: ../../dev.rst:899
+# 9abced699c07425985b4e3f50a1e82b9
+msgid "ACCOUNT.DISABLE"
+msgstr ""
+
+#: ../../dev.rst:901
+# af40529a74fb4d3e948e336013107e2f
+msgid "ACCOUNT.CREATE"
+msgstr ""
+
+#: ../../dev.rst:903
+# 804d0b3521ee4d3f9f359a9ffa6dedf2
+msgid "ACCOUNT.DELETE"
+msgstr ""
+
+#: ../../dev.rst:905
+# d9324c6675a34f07ada12c83bd90f259
+msgid "ACCOUNT.UPDATE"
+msgstr ""
+
+#: ../../dev.rst:907
+# 1584515abe07488d9c1ebe76f4c3f83e
+msgid "ACCOUNT.MARK.DEFAULT.ZONE"
+msgstr ""
+
+#: ../../dev.rst:909
+# 89003da38b5a421dbf2a50717bf3065e
+msgid "UserVO Events"
+msgstr ""
+
+#: ../../dev.rst:909
+# 3b342997f3dd496e9d5bcca934120251
+msgid "USER.LOGIN"
+msgstr ""
+
+#: ../../dev.rst:911
+# 067db23da7124ada888755206590e575
+msgid "USER.LOGOUT"
+msgstr ""
+
+#: ../../dev.rst:913
+# 9b29d8a91f944c829e1f2acff5f63b14
+msgid "USER.CREATE"
+msgstr ""
+
+#: ../../dev.rst:915
+# eafa3a5913e347b8b7f87c3079d872b0
+msgid "USER.DELETE"
+msgstr ""
+
+#: ../../dev.rst:917
+# c3d626a3dac14a278faf60b7889da651
+msgid "USER.DISABLE"
+msgstr ""
+
+#: ../../dev.rst:919
+# 444fc2dd12ef42459abd494142a50ade
+msgid "USER.UPDATE"
+msgstr ""
+
+#: ../../dev.rst:921
+# 31a1e444fc424f96a39d6cf61c195a7c
+msgid "USER.ENABLE"
+msgstr ""
+
+#: ../../dev.rst:923
+# be704e9963a045d588fbafd11b8ef0b7
+msgid "USER.LOCK"
+msgstr ""
+
+#: ../../dev.rst:925
+# ff939cdbfb174e6ba2f38a79e93597f2
+msgid "Registering SSH keypair events"
+msgstr ""
+
+#: ../../dev.rst:925
+# 56dac4f833b842a1a18c48bba6352e8d
+msgid "REGISTER.SSH.KEYPAIR"
+msgstr ""
+
+#: ../../dev.rst:928
+# 69f8bb424fb34ee2a1983188fbe1691d
+msgid "Register for user API and secret keys"
+msgstr ""
+
+#: ../../dev.rst:928
+# 0c115305735e44bfb98342afa46588b4
+msgid "REGISTER.USER.KEY"
+msgstr ""
+
+#: ../../dev.rst:932
+# 1c7d40a0c63d4c61a21abee9c4205ba6
+msgid "Template Events"
+msgstr ""
+
+#: ../../dev.rst:932
+# 4a7c0eb790ae40eba4c6f49ef416c9da
+msgid "TEMPLATE.CREATE"
+msgstr ""
+
+#: ../../dev.rst:934
+# cf5d7b4f4e9540cf8f7c789ff4ee300b
+msgid "TEMPLATE.DELETE"
+msgstr ""
+
+#: ../../dev.rst:936
+# 9c493c95524a4533a143f55ab04c28fb
+msgid "TEMPLATE.UPDATE"
+msgstr ""
+
+#: ../../dev.rst:938
+# c873bf23024543159c8e93721961609a
+msgid "TEMPLATE.DOWNLOAD.START"
+msgstr ""
+
+#: ../../dev.rst:940
+# c2b7dd18c6264c00b019556150d2cd37
+msgid "TEMPLATE.DOWNLOAD.SUCCESS"
+msgstr ""
+
+#: ../../dev.rst:942
+# 695a7ce33a55441b8b8800a31e587187
+msgid "TEMPLATE.DOWNLOAD.FAILED"
+msgstr ""
+
+#: ../../dev.rst:944
+# efc5f38eedd04ebb8831f86502ae9766
+msgid "TEMPLATE.COPY"
+msgstr ""
+
+#: ../../dev.rst:946
+# 237c07b2d3494deeacae4fdde5355af8
+msgid "TEMPLATE.EXTRACT"
+msgstr ""
+
+#: ../../dev.rst:948
+# e97449a8070047b7a1524bcdc3576164
+msgid "TEMPLATE.UPLOAD"
+msgstr ""
+
+#: ../../dev.rst:950
+# b50c3621c3684513963429cbff9d44a7
+msgid "TEMPLATE.CLEANUP"
+msgstr ""
+
+#: ../../dev.rst:952
+# 31af437baa534384a6122a8688bfad52
+msgid "Volume Events"
+msgstr ""
+
+#: ../../dev.rst:952
+# d98424bf1fcc48da8f4bf407bf8a37c4
+msgid "VOLUME.CREATE"
+msgstr ""
+
+#: ../../dev.rst:954
+# 1e8ca3f13cfd4e578bf8e4abc22a9349
+msgid "VOLUME.DELETE"
+msgstr ""
+
+#: ../../dev.rst:956
+# 711ca9115b574945b76811a3c54194d8
+msgid "VOLUME.ATTACH"
+msgstr ""
+
+#: ../../dev.rst:958
+# dfda68fbc1554ff4917635954f2c3117
+msgid "VOLUME.DETACH"
+msgstr ""
+
+#: ../../dev.rst:960
+# 2aae2a6617a84bf8afcbacb113bc9964
+msgid "VOLUME.EXTRACT"
+msgstr ""
+
+#: ../../dev.rst:962
+# c504b0688f854062820da9e1fbc4497e
+msgid "VOLUME.UPLOAD"
+msgstr ""
+
+#: ../../dev.rst:964
+# 9063bcc457a64df6a241822a9b054efd
+msgid "VOLUME.MIGRATE"
+msgstr ""
+
+#: ../../dev.rst:966
+# 2a35d4168abd446abd88441c9568faa9
+msgid "VOLUME.RESIZE"
+msgstr ""
+
+#: ../../dev.rst:968
+# 2297293b53bd4857b4e60b00fefa9d57
+msgid "VOLUME.DETAIL.UPDATE"
+msgstr ""
+
+#: ../../dev.rst:970
+# f05b0f0e1c824577a7364153487eef46
+msgid "VOLUME.DETAIL.ADD"
+msgstr ""
+
+#: ../../dev.rst:972
+# 7cfe6be5841e4fe680c8d1a3836394ba
+msgid "VOLUME.DETAIL.REMOVE"
+msgstr ""
+
+#: ../../dev.rst:974
+# e75a27c6b791458ab493ac0695b482ed
+msgid "Domains"
+msgstr ""
+
+#: ../../dev.rst:974
+# e4dec4a668a341a3be00504a11820dd3
+msgid "DOMAIN.CREATE"
+msgstr ""
+
+#: ../../dev.rst:976
+# f9cb908cc14c434e9daf37a73ecb3edf
+msgid "DOMAIN.DELETE"
+msgstr ""
+
+#: ../../dev.rst:978
+# fa86ece523294cd695a664379793934d
+msgid "DOMAIN.UPDATE"
+msgstr ""
+
+#: ../../dev.rst:980
+# 332b61c96e9b43cda511a1187019b95d
+msgid "Snapshots"
+msgstr ""
+
+#: ../../dev.rst:980
+# a1bdfb5ce327403abf92c4a9fff3dc7a
+msgid "SNAPSHOT.CREATE"
+msgstr ""
+
+#: ../../dev.rst:982
+# 4d1f5d870261420e818d673b4253baa9
+msgid "SNAPSHOT.DELETE"
+msgstr ""
+
+#: ../../dev.rst:984
+# 9391c45700ee4c70a8041819fb3bb61f
+msgid "SNAPSHOTPOLICY.CREATE"
+msgstr ""
+
+#: ../../dev.rst:986
+# 28c24f345f9e492babd8da4788d47a05
+msgid "SNAPSHOTPOLICY.UPDATE"
+msgstr ""
+
+#: ../../dev.rst:988
+# bf31c9b68314463ba99544fd24bdb370
+msgid "SNAPSHOTPOLICY.DELETE"
+msgstr ""
+
+#: ../../dev.rst:990
+# 6e32d7c362fc46eab940c281b50f153a
+msgid "ISO"
+msgstr ""
+
+#: ../../dev.rst:990
+# ce6946bf3c2f4dbfb112b8f4e7ca61b7
+msgid "ISO.CREATE"
+msgstr ""
+
+#: ../../dev.rst:992
+# 375c9e47499e432187e2035ad70b622f
+msgid "ISO.DELETE"
+msgstr ""
+
+#: ../../dev.rst:994
+# d35b4b7ac0844458bf92e4c037c0c35f
+msgid "ISO.COPY"
+msgstr ""
+
+#: ../../dev.rst:996
+# 640bdcedac1d436aaa23a3c74547e67d
+msgid "ISO.ATTACH"
+msgstr ""
+
+#: ../../dev.rst:998
+# 85297a9ad7f244ba926f1a447495f28a
+msgid "ISO.DETACH"
+msgstr ""
+
+#: ../../dev.rst:1000
+# 2e87e726a12b4cfba535cda2c15438af
+msgid "ISO.EXTRACT"
+msgstr ""
+
+#: ../../dev.rst:1002
+# 1105026873ee40e4b9cadef2e98debc6
+msgid "ISO.UPLOAD"
+msgstr ""
+
+#: ../../dev.rst:1004
+# 8fbc8cb673c94a5aa7ed5f4fc68800e5
+msgid "SSVM"
+msgstr ""
+
+#: ../../dev.rst:1004
+# 9e46ea023ded4544902aa174f045d643
+msgid "SSVM.CREATE"
+msgstr ""
+
+#: ../../dev.rst:1006
+# 64b4115f71a448d58999c72cc7bb9a25
+msgid "SSVM.DESTROY"
+msgstr ""
+
+#: ../../dev.rst:1008
+# a93ffcfd9c4741ce8596774daaafe157
+msgid "SSVM.START"
+msgstr ""
+
+#: ../../dev.rst:1010
+# cf0729d95bed4a7ca381547be9cd8d7a
+msgid "SSVM.STOP"
+msgstr ""
+
+#: ../../dev.rst:1012
+# b78e6d90ed5a431981d02081e8ed52d1
+msgid "SSVM.REBOOT"
+msgstr ""
+
+#: ../../dev.rst:1014
+# de758884dcd7492ba8f9d0fffa2b115f
+msgid "SSVM.HA"
+msgstr ""
+
+#: ../../dev.rst:1016
+# ffd6bd7086104744a78972955fdf5b63
+msgid "Service Offerings"
+msgstr ""
+
+#: ../../dev.rst:1016
+# b70fa1e9f97a4d968e140e59ff2efa0c
+msgid "SERVICE.OFFERING.CREATE"
+msgstr ""
+
+#: ../../dev.rst:1018
+# 83cf0b49f2c04f8ca4fcd3714393c8f6
+msgid "SERVICE.OFFERING.EDIT"
+msgstr ""
+
+#: ../../dev.rst:1020
+# 51d961c2c39847ac86a124b58cadef1e
+msgid "SERVICE.OFFERING.DELETE"
+msgstr ""
+
+#: ../../dev.rst:1022
+# 78aa61a6e6104d24b9e8c97eadab6e89
+msgid "Disk Offerings"
+msgstr ""
+
+#: ../../dev.rst:1022
+# 0be7fc96572d47d5a89a14a090506ed9
+msgid "DISK.OFFERING.CREATE"
+msgstr ""
+
+#: ../../dev.rst:1024
+# 0009799f038e4aea882d889e92384af0
+msgid "DISK.OFFERING.EDIT"
+msgstr ""
+
+#: ../../dev.rst:1026
+# ae3e98e623a347b8b73a59f51bee0e68
+msgid "DISK.OFFERING.DELETE"
+msgstr ""
+
+#: ../../dev.rst:1028
+# 6c9be6933b934f11a591770ee201f9e1
+msgid "Network offerings"
+msgstr ""
+
+#: ../../dev.rst:1028
+# da996264ebd54802b0d22dffcdd41238
+msgid "NETWORK.OFFERING.CREATE"
+msgstr ""
+
+#: ../../dev.rst:1030
+# 105e37949f1b4553913a95975659efdc
+msgid "NETWORK.OFFERING.ASSIGN"
+msgstr ""
+
+#: ../../dev.rst:1032
+# ea544f05c05e424d8f41bba4675e3b4b
+msgid "NETWORK.OFFERING.EDIT"
+msgstr ""
+
+#: ../../dev.rst:1034
+# 91a42fe69b794608a089e54d49ef3b91
+msgid "NETWORK.OFFERING.REMOVE"
+msgstr ""
+
+#: ../../dev.rst:1036
+# e0e7111502454f53b6ee3c22661c42c1
+msgid "NETWORK.OFFERING.DELETE"
+msgstr ""
+
+#: ../../dev.rst:1038
+# 0d0bf72de6e4438aac8923733f75b0a5
+msgid "Pods"
+msgstr ""
+
+#: ../../dev.rst:1038
+# ace72761444544f18eceaf727effef84
+msgid "POD.CREATE"
+msgstr ""
+
+#: ../../dev.rst:1040
+# 94c28b64ba2a484fb88157737697b852
+msgid "POD.EDIT"
+msgstr ""
+
+#: ../../dev.rst:1042
+# 6ff8d9286fac49cf808875b23e50f539
+msgid "POD.DELETE"
+msgstr ""
+
+#: ../../dev.rst:1044
+# 1467c66608c14660998c64c30fb1a4c0
+msgid "Zones"
+msgstr ""
+
+#: ../../dev.rst:1044
+# 5c3804942cd341bfb76b5b564e70a91b
+msgid "ZONE.CREATE"
+msgstr ""
+
+#: ../../dev.rst:1046
+# 8fe574fc8629445fabf6651c9639dea8
+msgid "ZONE.EDIT"
+msgstr ""
+
+#: ../../dev.rst:1048
+# e076fd7ad346426fa004e64ccf91e21f
+msgid "ZONE.DELETE"
+msgstr ""
+
+#: ../../dev.rst:1050
+# 46c94df1984840e7a714fdba1a10ec82
+msgid "VLANs/IP ranges"
+msgstr ""
+
+#: ../../dev.rst:1050
+# 895d9b6d3d834ed580993209e08c3474
+msgid "VLAN.IP.RANGE.CREATE"
+msgstr ""
+
+#: ../../dev.rst:1052
+# ab95f80c48e24256a5685db3b07f9c5f
+msgid "VLAN.IP.RANGE.DELETE"
+msgstr ""
+
+#: ../../dev.rst:1054
+# 63f68eca92f449b6b450026407799c2e
+msgid "VLAN.IP.RANGE.DEDICATE"
+msgstr ""
+
+#: ../../dev.rst:1056
+# 5ed41e8a0f804109800f2485a932ac34
+msgid "VLAN.IP.RANGE.RELEASE"
+msgstr ""
+
+#: ../../dev.rst:1058
+# 2a3a189785c141409c0a77036a394ac2
+msgid "STORAGE.IP.RANGE.CREATE"
+msgstr ""
+
+#: ../../dev.rst:1060
+# 11dee92eaf1b42fb8297f7d3445cdf42
+msgid "STORAGE.IP.RANGE.DELETE"
+msgstr ""
+
+#: ../../dev.rst:1062
+# 02cbc1b176bf44fc89fb912aaa842d5b
+msgid "STORAGE.IP.RANGE.UPDATE"
+msgstr ""
+
+#: ../../dev.rst:1064
+# c94b4a15b7b3432c85c6dd1a64ec2ba0
+msgid "Configuration Table"
+msgstr ""
+
+#: ../../dev.rst:1064
+# e258aaf5b13942dea329e7a9cb02bc0c
+msgid "CONFIGURATION.VALUE.EDIT"
+msgstr ""
+
+#: ../../dev.rst:1067
+# fa0ab24f4e0646c9be9005eda7e214be
+msgid "Security Groups"
+msgstr ""
+
+#: ../../dev.rst:1067
+# 607a8809376d4e3a9fb5147668ab7f23
+msgid "SG.AUTH.INGRESS"
+msgstr ""
+
+#: ../../dev.rst:1069
+# 9ffbea0b8ee94394b413b8e542ca36a0
+msgid "SG.REVOKE.INGRESS"
+msgstr ""
+
+#: ../../dev.rst:1071
+# 0907ae0daa2a4a97880a33aea22f7ab2
+msgid "SG.AUTH.EGRESS"
+msgstr ""
+
+#: ../../dev.rst:1073
+# 07e432a9c8494d89a35cef7a1284e03b
+msgid "SG.REVOKE.EGRESS"
+msgstr ""
+
+#: ../../dev.rst:1075
+# 54026fb2a6294cf2b0cbd14da8d6246d
+msgid "SG.CREATE"
+msgstr ""
+
+#: ../../dev.rst:1077
+# ff28fa3d071247bd811857b1d6355671
+msgid "SG.DELETE"
+msgstr ""
+
+#: ../../dev.rst:1079
+# e1a67631e2914cbfb2245ebe482488c1
+msgid "SG.ASSIGN"
+msgstr ""
+
+#: ../../dev.rst:1081
+# ef980dd60e0b4ca3aa3c241fe6f1e051
+msgid "SG.REMOVE"
+msgstr ""
+
+#: ../../dev.rst:1083
+# 7c7ab578207e4305918d6bf7c8891671
+msgid "Host"
+msgstr ""
+
+#: ../../dev.rst:1083
+# 67ef96f70e1f43a2a35be93e10a18555
+msgid "HOST.RECONNECT"
+msgstr ""
+
+#: ../../dev.rst:1085
+# 5e8cbc3ef6ac4829a9aeaddf9e5b8368
+msgid "Maintenance"
+msgstr ""
+
+#: ../../dev.rst:1085
+# df753f25151f4d4b8cfc942915ee8eda
+msgid "MAINT.CANCEL"
+msgstr ""
+
+#: ../../dev.rst:1087
+# a6281f29bc684656bfef1ef3f107ee5c
+msgid "MAINT.CANCEL.PS"
+msgstr ""
+
+#: ../../dev.rst:1089
+# 6b1cdae2b61c404aaa7bfa74cf561ab2
+msgid "MAINT.PREPARE"
+msgstr ""
+
+#: ../../dev.rst:1091
+# 1a7651b09ce240f8accaeb6243b72a09
+msgid "MAINT.PREPARE.PS"
+msgstr ""
+
+#: ../../dev.rst:1093
+# f35d8679d0ab41158f0a0253ef992d5e
+msgid "VPN"
+msgstr ""
+
+#: ../../dev.rst:1093
+# 6d37121536084cfcb28a6e5f1ddd63a0
+msgid "VPN.REMOTE.ACCESS.CREATE"
+msgstr ""
+
+#: ../../dev.rst:1095
+# b26c3d13b7a640bcaa1b31cd101003e6
+msgid "VPN.REMOTE.ACCESS.DESTROY"
+msgstr ""
+
+#: ../../dev.rst:1097
+# 03e51d7400474807b95af6af01f2abcf
+msgid "VPN.USER.ADD"
+msgstr ""
+
+#: ../../dev.rst:1099
+# 0887283d2b7d47e99ed511a653b19eb6
+msgid "VPN.USER.REMOVE"
+msgstr ""
+
+#: ../../dev.rst:1101
+# 0c7c48a65ed444cab6ffadcc5f3e0f35
+msgid "VPN.S2S.VPN.GATEWAY.CREATE"
+msgstr ""
+
+#: ../../dev.rst:1103
+# 088c8bddcda3437ba38c84c64ed4dd8b
+msgid "VPN.S2S.VPN.GATEWAY.DELETE"
+msgstr ""
+
+#: ../../dev.rst:1105
+# f2d842d577b641bb80d42eea7815e307
+msgid "VPN.S2S.CUSTOMER.GATEWAY.CREATE"
+msgstr ""
+
+#: ../../dev.rst:1107
+# 8f9e54e0a03d48d682bb6ebbf1e264bd
+msgid "VPN.S2S.CUSTOMER.GATEWAY.DELETE"
+msgstr ""
+
+#: ../../dev.rst:1109
+# 0ecb424bff794dfe8f901acfce93d691
+msgid "VPN.S2S.CUSTOMER.GATEWAY.UPDATE"
+msgstr ""
+
+#: ../../dev.rst:1111
+# 3a7665c215d645eb9ef4051ad64228f1
+msgid "VPN.S2S.CONNECTION.CREATE"
+msgstr ""
+
+#: ../../dev.rst:1113
+# 8f5a8ae08b534beb9e0ef1af501017d2
+msgid "VPN.S2S.CONNECTION.DELETE"
+msgstr ""
+
+#: ../../dev.rst:1115
+# 17214507d9f14f5c8ebc878d4033675b
+msgid "VPN.S2S.CONNECTION.RESET"
+msgstr ""
+
+#: ../../dev.rst:1117
+# 71e70a0125374d7e8474cae1f20309fc
+msgid "Network"
+msgstr ""
+
+#: ../../dev.rst:1117
+# 2de54588bd304e5dafe5aa0c2b9c4da3
+msgid "NETWORK.RESTART"
+msgstr ""
+
+#: ../../dev.rst:1119
+# af862cac0842498798cdb70ce8ee2ac7
+msgid "Custom certificates"
+msgstr ""
+
+#: ../../dev.rst:1119
+# c4c6edfceadd496ca1cd3ceba59efafa
+msgid "UPLOAD.CUSTOM.CERTIFICATE"
+msgstr ""
+
+#: ../../dev.rst:1122
+# 28dcff1303834708b3620092652de860
+msgid "OneToOnenat"
+msgstr ""
+
+#: ../../dev.rst:1122
+# a6992e10d43d46cab03bcf39abfe742a
+msgid "STATICNAT.ENABLE"
+msgstr ""
+
+#: ../../dev.rst:1124
+# 639558116a054b13947f4525c89330ca
+msgid "STATICNAT.DISABLE"
+msgstr ""
+
+#: ../../dev.rst:1126
+# 10d2bd0eba47406883e95627ac65dae8
+msgid "ZONE.VLAN.ASSIGN"
+msgstr ""
+
+#: ../../dev.rst:1128
+# 055f3349617943379586168c9e8a4dd0
+msgid "ZONE.VLAN.RELEASE"
+msgstr ""
+
+#: ../../dev.rst:1130
+# a400a4a312b44772a14f04265a18e2f0
+msgid "Projects"
+msgstr ""
+
+#: ../../dev.rst:1130
+# 92043a54ddef4d929b14554c9f9eeebd
+msgid "PROJECT.CREATE"
+msgstr ""
+
+#: ../../dev.rst:1132
+# 91c7c55cacd14ad9b709804ab65fa25c
+msgid "PROJECT.UPDATE"
+msgstr ""
+
+#: ../../dev.rst:1134
+# cefa689b18154e09b114141438d171ac
+msgid "PROJECT.DELETE"
+msgstr ""
+
+#: ../../dev.rst:1136
+# 2a165e4549a8462e95ce3bd956226722
+msgid "PROJECT.ACTIVATE"
+msgstr ""
+
+#: ../../dev.rst:1138
+# 55e9f1af12854c9e80e5dc26a2a20a10
+msgid "PROJECT.SUSPEND"
+msgstr ""
+
+#: ../../dev.rst:1140
+# 3fbf10e620754801917eca5cce0cb06a
+msgid "PROJECT.ACCOUNT.ADD"
+msgstr ""
+
+#: ../../dev.rst:1142
+# 10152d2739d24a018e0ff295ee719fb2
+msgid "PROJECT.INVITATION.UPDATE"
+msgstr ""
+
+#: ../../dev.rst:1144
+# 0281e748e87f42e4ae5dc419f5fe5a2c
+msgid "PROJECT.INVITATION.REMOVE"
+msgstr ""
+
+#: ../../dev.rst:1146
+# a79b5f168feb4d3cb393383c54a2ecba
+msgid "PROJECT.ACCOUNT.REMOVE"
+msgstr ""
+
+#: ../../dev.rst:1148
+# f57c1a43fa0a49b39e475e79668e2a85
+msgid "Network as a Service"
+msgstr ""
+
+#: ../../dev.rst:1148
+# 228f56d86cd34d538773621b26be1d0a
+msgid "NETWORK.ELEMENT.CONFIGURE"
+msgstr ""
+
+#: ../../dev.rst:1151
+# 637555fe29dc456fa2128bb20a03ce07
+msgid "Physical Network Events"
+msgstr ""
+
+#: ../../dev.rst:1151
+# 5a143eeef182460da69f52203355f297
+msgid "PHYSICAL.NETWORK.CREATE"
+msgstr ""
+
+#: ../../dev.rst:1153
+# 18fff6851b71468ba3a024c224b5da38
+msgid "PHYSICAL.NETWORK.DELETE"
+msgstr ""
+
+#: ../../dev.rst:1155
+# 27194312cabd497a868c18814812b788
+msgid "PHYSICAL.NETWORK.UPDATE"
+msgstr ""
+
+#: ../../dev.rst:1157
+# a9e59d6750e44ff1a62705d3f85a0180
+msgid "Physical Network Service Provider Events"
+msgstr ""
+
+#: ../../dev.rst:1157
+# 075aca1844e445f6b43546beb174c2d6
+msgid "SERVICE.PROVIDER.CREATE"
+msgstr ""
+
+#: ../../dev.rst:1159
+# 5644882c962c4bc8a09c1389af4fc80c
+msgid "SERVICE.PROVIDER.DELETE"
+msgstr ""
+
+#: ../../dev.rst:1161
+# 3eee170522344c9ab1c095beb07cb81e
+msgid "SERVICE.PROVIDER.UPDATE"
+msgstr ""
+
+#: ../../dev.rst:1163
+# b5ac0b14b4ba477484d60bc53dc37bee
+msgid "Physical Network Traffic Type Events"
+msgstr ""
+
+#: ../../dev.rst:1163
+# 2126c2311d9b4f5eab41b797d7f1c79d
+msgid "TRAFFIC.TYPE.CREATE"
+msgstr ""
+
+#: ../../dev.rst:1165
+# f574f7fa432249d4b77d9ef69c2a438e
+msgid "TRAFFIC.TYPE.DELETE"
+msgstr ""
+
+#: ../../dev.rst:1167
+# 5e3ebc4061f44d9fa2b360be1919056b
+msgid "TRAFFIC.TYPE.UPDATE"
+msgstr ""
+
+#: ../../dev.rst:1169
+#: ../../dev.rst:1239
+# 5694676d0fea49f9be10a19d945eb6f3
+# f2c2a8b2a29a4914b5ba80db28d4a9e5
+msgid "External network device events"
+msgstr ""
+
+#: ../../dev.rst:1169
+# 3a40fe68f0ba4769be7f068a47498353
+msgid "PHYSICAL.LOADBALANCER.ADD"
+msgstr ""
+
+#: ../../dev.rst:1171
+# a9d01a930a2a4d449d348de6ce22f321
+msgid "PHYSICAL.LOADBALANCER.DELETE"
+msgstr ""
+
+#: ../../dev.rst:1173
+# 860d3fb2956f4f2d94665c35e57b996f
+msgid "PHYSICAL.LOADBALANCER.CONFIGURE"
+msgstr ""
+
+#: ../../dev.rst:1175
+# 99432960a5dc4084825347f24bb1d90b
+msgid "External switch management device events"
+msgstr ""
+
+#: ../../dev.rst:1179
+# cab557c970b1454493f950d61bcbf762
+msgid "For example: Cisco Nexus 1000v Virtual Supervisor Module."
+msgstr ""
+
+#: ../../dev.rst:1175
+# 57e1cf12e3db43eebfada0791ec75ed0
+msgid "SWITCH.MGMT.ADD"
+msgstr ""
+
+#: ../../dev.rst:1177
+# ad8a274c736a46f9bcd06daea2799101
+msgid "SWITCH.MGMT.DELETE"
+msgstr ""
+
+#: ../../dev.rst:1179
+# da4cbe6b2a6043d6abf9f6154f742d49
+msgid "SWITCH.MGMT.CONFIGURE"
+msgstr ""
+
+#: ../../dev.rst:1181
+# 29f7513425ad46359b65a47845f157a7
+msgid "SWITCH.MGMT.ENABLE"
+msgstr ""
+
+#: ../../dev.rst:1183
+# 67f7640000c74f07b2f6ab5f6651fcb6
+msgid "SWITCH.MGMT.DISABLE"
+msgstr ""
+
+#: ../../dev.rst:1185
+# 635749d2fe074c6d83e919d072819672
+msgid "PHYSICAL.FIREWALL.ADD"
+msgstr ""
+
+#: ../../dev.rst:1187
+# 63291158ae1045188bbd373cd3a79356
+msgid "PHYSICAL.FIREWALL.DELETE"
+msgstr ""
+
+#: ../../dev.rst:1189
+# 795f61d09f344fa9b211823d019e221c
+msgid "PHYSICAL.FIREWALL.CONFIGURE"
+msgstr ""
+
+#: ../../dev.rst:1191
+# 89cf06cca36c4a4ca5ba897ddbaf4d58
+msgid "VPC"
+msgstr ""
+
+#: ../../dev.rst:1191
+# 7e9d36a793144a0b8e35ed7695caaa69
+msgid "VPC.CREATE"
+msgstr ""
+
+#: ../../dev.rst:1193
+# bf14a605bb5b47c78733f6ee22cba2ce
+msgid "VPC.UPDATE"
+msgstr ""
+
+#: ../../dev.rst:1195
+# dfc4073a3c464c60a671151b192904d1
+msgid "VPC.DELETE"
+msgstr ""
+
+#: ../../dev.rst:1197
+# 9d60ce613d2d46f5a8ce5a1602c880e6
+msgid "VPC.RESTART"
+msgstr ""
+
+#: ../../dev.rst:1199
+# d0c21aaa24f44b78b782c07b899cd78e
+msgid "Network ACL"
+msgstr ""
+
+#: ../../dev.rst:1199
+# ed5aeefb83d6466bb0ce40d2218326cf
+msgid "NETWORK.ACL.CREATE"
+msgstr ""
+
+#: ../../dev.rst:1201
+# 02e6f982f8d44f538e252c70789133e0
+msgid "NETWORK.ACL.DELETE"
+msgstr ""
+
+#: ../../dev.rst:1203
+# f8b87afb1b404efc89ab5f7559fe6361
+msgid "NETWORK.ACL.REPLACE"
+msgstr ""
+
+#: ../../dev.rst:1205
+# 431c84963d904458ba23b47a76e28dc5
+msgid "NETWORK.ACL.ITEM.CREATE"
+msgstr ""
+
+#: ../../dev.rst:1207
+# f01a3c3a38844cdf8ec3b5ea4a3be85b
+msgid "NETWORK.ACL.ITEM.UPDATE"
+msgstr ""
+
+#: ../../dev.rst:1209
+# 9069cff1a8f94fc88d3d5e2c6f19d926
+msgid "NETWORK.ACL.ITEM.DELETE"
+msgstr ""
+
+#: ../../dev.rst:1211
+# 654b46e911374c35807fc71e16876959
+msgid "VPC offerings"
+msgstr ""
+
+#: ../../dev.rst:1211
+# b5b644a13c774295a90b59a869535251
+msgid "VPC.OFFERING.CREATE"
+msgstr ""
+
+#: ../../dev.rst:1213
+# d247a74805a541e584e97fa223e8feba
+msgid "VPC.OFFERING.UPDATE"
+msgstr ""
+
+#: ../../dev.rst:1215
+# 96d8c963e2e34d198297fb38ae2ba154
+msgid "VPC.OFFERING.DELETE"
+msgstr ""
+
+#: ../../dev.rst:1217
+# 074d3b974dcb43c993cb065450f1f25f
+msgid "Private gateway"
+msgstr ""
+
+#: ../../dev.rst:1217
+# 2f84b8f7a0014c1f9772e0474ccd0a88
+msgid "PRIVATE.GATEWAY.CREATE"
+msgstr ""
+
+#: ../../dev.rst:1219
+# ddfe7767f2894438a228e7d8aaa01bdb
+msgid "PRIVATE.GATEWAY.DELETE"
+msgstr ""
+
+#: ../../dev.rst:1221
+# 3982ad2d0af648859177e40c742c6fa8
+msgid "Static routes"
+msgstr ""
+
+#: ../../dev.rst:1221
+# 97a6cb1cbd7f4d8380e3d064753e4a76
+msgid "STATIC.ROUTE.CREATE"
+msgstr ""
+
+#: ../../dev.rst:1223
+# 0744a134a90a41bd94043e89f981c290
+msgid "STATIC.ROUTE.DELETE"
+msgstr ""
+
+#: ../../dev.rst:1225
+# 4054268ea7184437a13fe652f634b83d
+msgid "Tag-related events"
+msgstr ""
+
+#: ../../dev.rst:1225
+# 8297ba38795649f08afd5d95df3fad35
+msgid "CREATE\\_TAGS"
+msgstr ""
+
+#: ../../dev.rst:1227
+# e41461c480c3456c9ba4331a54b5bda2
+msgid "DELETE\\_TAGS"
+msgstr ""
+
+#: ../../dev.rst:1229
+# 6fbca5203601434498b01a51b644f63a
+msgid "Meta data-related events"
+msgstr ""
+
+#: ../../dev.rst:1229
+# cdb5effcff30492eabdd3e895719c19c
+msgid "CREATE\\_RESOURCE\\_DETAILS"
+msgstr ""
+
+#: ../../dev.rst:1231
+# 76c4af5b2fe64580b664adf8a6556de7
+msgid "DELETE\\_RESOURCE\\_DETAILS"
+msgstr ""
+
+#: ../../dev.rst:1233
+# 8b326f8e2d4b4c91844b9dbe972362e5
+msgid "VM snapshot events"
+msgstr ""
+
+#: ../../dev.rst:1233
+# e81388d5cf2f4d0bbca408d9f51e8832
+msgid "VMSNAPSHOT.CREATE"
+msgstr ""
+
+#: ../../dev.rst:1235
+# e4e79cfe40ac470cbfe2b740a15c8a22
+msgid "VMSNAPSHOT.DELETE"
+msgstr ""
+
+#: ../../dev.rst:1237
+# e8afb9179ee041b5bcf21671db55c610
+msgid "VMSNAPSHOT.REVERTTO"
+msgstr ""
+
+#: ../../dev.rst:1239
+# b01153a95b404dd6a739d7ca7cb5dc6f
+msgid "PHYSICAL.NVPCONTROLLER.ADD"
+msgstr ""
+
+#: ../../dev.rst:1241
+# 632af0c1da5e4d4ca79199a8d9217275
+msgid "PHYSICAL.NVPCONTROLLER.DELETE"
+msgstr ""
+
+#: ../../dev.rst:1243
+# c41b43b4e47c418a94954dcf4659630d
+msgid "PHYSICAL.NVPCONTROLLER.CONFIGURE"
+msgstr ""
+
+#: ../../dev.rst:1245
+# 2446bc5f48f947f898a30d4ee2429108
+msgid "AutoScale"
+msgstr ""
+
+#: ../../dev.rst:1245
+# 5ce3e63a54dd4c15b1f5cc7cd2bcc96b
+msgid "COUNTER.CREATE"
+msgstr ""
+
+#: ../../dev.rst:1247
+# 00d5ea5c3142408d9ed52d952433ea55
+msgid "COUNTER.DELETE"
+msgstr ""
+
+#: ../../dev.rst:1249
+# d46552187a2e4093bab6cd33120c01b6
+msgid "CONDITION.CREATE"
+msgstr ""
+
+#: ../../dev.rst:1251
+# f74458c9c9e2474195caea1ab66d0258
+msgid "CONDITION.DELETE"
+msgstr ""
+
+#: ../../dev.rst:1253
+# 6b2d513100e040ad908533a2626ef58e
+msgid "AUTOSCALEPOLICY.CREATE"
+msgstr ""
+
+#: ../../dev.rst:1255
+# 4d492b6b5f894eccb34a579d6df18197
+msgid "AUTOSCALEPOLICY.UPDATE"
+msgstr ""
+
+#: ../../dev.rst:1257
+# 3bb42c29abb3473daeb32d519bd56d5e
+msgid "AUTOSCALEPOLICY.DELETE"
+msgstr ""
+
+#: ../../dev.rst:1259
+# 4cc4026a3d5b4a4eb635f09ce0f2439a
+msgid "AUTOSCALEVMPROFILE.CREATE"
+msgstr ""
+
+#: ../../dev.rst:1261
+# caa130acb2734766a3e5b0442a5c5ade
+msgid "AUTOSCALEVMPROFILE.DELETE"
+msgstr ""
+
+#: ../../dev.rst:1263
+# 6be5dec329464b0e8ec5e0305d09a5a2
+msgid "AUTOSCALEVMPROFILE.UPDATE"
+msgstr ""
+
+#: ../../dev.rst:1265
+# b370a64985ba4ab5ab0106cd97ae31b3
+msgid "AUTOSCALEVMGROUP.CREATE"
+msgstr ""
+
+#: ../../dev.rst:1267
+# e33476c0ee31487ea856c938d33f3b2d
+msgid "AUTOSCALEVMGROUP.DELETE"
+msgstr ""
+
+#: ../../dev.rst:1269
+# 88dff327d5ca43de814a3a5c9e068457
+msgid "AUTOSCALEVMGROUP.UPDATE"
+msgstr ""
+
+#: ../../dev.rst:1271
+# 11de45d76eda4776915a59e50e18ac68
+msgid "AUTOSCALEVMGROUP.ENABLE"
+msgstr ""
+
+#: ../../dev.rst:1273
+# 5145ef5e7a374588bc5c5c9173da6b01
+msgid "AUTOSCALEVMGROUP.DISABLE"
+msgstr ""
+
+#: ../../dev.rst:1275
+# ecf312f56bc644759dd02b247dbaca35
+msgid "PHYSICAL.DHCP.ADD"
+msgstr ""
+
+#: ../../dev.rst:1277
+# 12239c1e044c4de38c61d2910f135b81
+msgid "PHYSICAL.DHCP.DELETE"
+msgstr ""
+
+#: ../../dev.rst:1279
+# d3925718fc1a48cb913d438ae47c8e52
+msgid "PHYSICAL.PXE.ADD"
+msgstr ""
+
+#: ../../dev.rst:1281
+# f23e06df5fa94c41b341d3afdc34cbdb
+msgid "PHYSICAL.PXE.DELETE"
+msgstr ""
+
+#: ../../dev.rst:1283
+# e981870078114b04b0378178faa81720
+msgid "AG.CREATE"
+msgstr ""
+
+#: ../../dev.rst:1285
+# 061397efbf934a16aa0435b029f6cb31
+msgid "AG.DELETE"
+msgstr ""
+
+#: ../../dev.rst:1287
+# 26a254121f3f467e844419710c78642a
+msgid "AG.ASSIGN"
+msgstr ""
+
+#: ../../dev.rst:1289
+# ebcf9520267b4a90a5c265dc76d00d95
+msgid "AG.REMOVE"
+msgstr ""
+
+#: ../../dev.rst:1291
+# be2c1b9db8c34740a1fe20628ab40f01
+msgid "VM.AG.UPDATE"
+msgstr ""
+
+#: ../../dev.rst:1293
+# a709d3732f46421cbcda9f5ac24eb305
+msgid "INTERNALLBVM.START"
+msgstr ""
+
+#: ../../dev.rst:1295
+# b6715cc86c994240b485e949bf1598e3
+msgid "INTERNALLBVM.STOP"
+msgstr ""
+
+#: ../../dev.rst:1297
+# 8421ad90aacf46edb14a274ec36395aa
+msgid "HOST.RESERVATION.RELEASE"
+msgstr ""
+
+#: ../../dev.rst:1299
+# 3a084fff72bf4c489d3164e6160ad4cb
+msgid "Dedicated guest vlan range"
+msgstr ""
+
+#: ../../dev.rst:1299
+# 71cf76d6a1f44cf79780eac797da01c9
+msgid "GUESTVLANRANGE.DEDICATE"
+msgstr ""
+
+#: ../../dev.rst:1301
+# 36c642904da14b8fa59d5e8134d82009
+msgid "GUESTVLANRANGE.RELEASE"
+msgstr ""
+
+#: ../../dev.rst:1303
+# 030e512c5a554106b872744ce40bcc55
+msgid "PORTABLE.IP.RANGE.CREATE"
+msgstr ""
+
+#: ../../dev.rst:1305
+# 896dc2d533814346800fda0e0e063e93
+msgid "PORTABLE.IP.RANGE.DELETE"
+msgstr ""
+
+#: ../../dev.rst:1307
+# e3dae733d43349feb5161a9e30d1371c
+msgid "PORTABLE.IP.TRANSFER"
+msgstr ""
+
+#: ../../dev.rst:1309
+# 8ec3cf7227864b018dddef09969ae817
+msgid "Dedicated Resources"
+msgstr ""
+
+#: ../../dev.rst:1309
+# 5fb2eec5fe874352b3b7fd3760285739
+msgid "DEDICATE.RESOURCE"
+msgstr ""
+
+#: ../../dev.rst:1311
+# d0cc51dc064a418e841a4a46cb9e6751
+msgid "DEDICATE.RESOURCE.RELEASE"
+msgstr ""
+
+#: ../../dev.rst:1313
+# b5cb673ae0b64c499ae9788823168239
+msgid "VM.RESERVATION.CLEANUP"
+msgstr ""
+
+#: ../../dev.rst:1315
+# 04b13e6b43974f82976c390d6110071d
+msgid "UCS.ASSOCIATEPROFILE"
+msgstr ""
+
+#: ../../dev.rst:1317
+# b6423fa0906c455f829ae87b6f2d29b0
+msgid "UCS.DISASSOCIATEPROFILE"
+msgstr ""
+
+#: ../../dev.rst:1321
+# d5c3019aa78c437fa7ed6a0497abffaf
+msgid "Time Zones"
+msgstr ""
+
+#: ../../dev.rst:1323
+# 116de5edf8e449378280c02a410c56f1
+msgid "The following time zone identifiers are accepted by PRODUCT. There are several places that have a time zone as a required or optional parameter. These include scheduling recurring snapshots, creating a user, and specifying the usage time zone in the Configuration table."
+msgstr ""
+
+#: ../../dev.rst:1329
+# 826b28ef0e904dc38481fba5de6f01d8
+msgid "Etc/GMT+12"
+msgstr ""
+
+#: ../../dev.rst:1329
+# d1ee5ea0cf8b482d9f9bb58ae6f25d3b
+msgid "Etc/GMT+11"
+msgstr ""
+
+#: ../../dev.rst:1329
+# bf29b6e911df40d489b5dcc001ccf668
+msgid "Pacific/Samoa"
+msgstr ""
+
+#: ../../dev.rst:1331
+# 0f032e031e684469963d0d3313b53728
+msgid "Pacific/Honolulu"
+msgstr ""
+
+#: ../../dev.rst:1331
+# b4c90f9e4db84df3aa650cc650a5cd80
+msgid "US/Alaska"
+msgstr ""
+
+#: ../../dev.rst:1331
+# dcde82c56f6845dc8d6d1c12e2a5a643
+msgid "America/Los\\_Angeles"
+msgstr ""
+
+#: ../../dev.rst:1333
+# 2db93cf46c004a5a869e073a4642580d
+msgid "Mexico/BajaNorte"
+msgstr ""
+
+#: ../../dev.rst:1333
+# 34c07dd5cb5f420e97c5508ab975bf3c
+msgid "US/Arizona"
+msgstr ""
+
+#: ../../dev.rst:1333
+# a13b8c545eae434ba626d2dc036b461c
+msgid "US/Mountain"
+msgstr ""
+
+#: ../../dev.rst:1335
+# b6fede29ab21428ca0682e4cccf4f5b1
+msgid "America/Chihuahua"
+msgstr ""
+
+#: ../../dev.rst:1335
+# 634c419e82934a0ea351b3d99c3d6561
+msgid "America/Chicago"
+msgstr ""
+
+#: ../../dev.rst:1335
+# 656848e4004b4a9a9f2c21a789e36572
+msgid "America/Costa\\_Rica"
+msgstr ""
+
+#: ../../dev.rst:1337
+# 7c4d4c2391be4ca29fbb3a9fea5351e8
+msgid "America/Mexico\\_City"
+msgstr ""
+
+#: ../../dev.rst:1337
+# aee23664cb9d4182b2feae400a38a11e
+msgid "Canada/Saskatchewan"
+msgstr ""
+
+#: ../../dev.rst:1337
+# 10d105410731498f89d87ad6efc87a70
+msgid "America/Bogota"
+msgstr ""
+
+#: ../../dev.rst:1339
+# 5fa4882f1b3d4f12b87a03edec888952
+msgid "America/New\\_York"
+msgstr ""
+
+#: ../../dev.rst:1339
+# b81535c4904044cb99d950c6ff3b73c2
+msgid "America/Caracas"
+msgstr ""
+
+#: ../../dev.rst:1339
+# 7467c1ea627a4a6b943e9dc11519c148
+msgid "America/Asuncion"
+msgstr ""
+
+#: ../../dev.rst:1341
+# 3f5598da34fc494eb60836684683e9d1
+msgid "America/Cuiaba"
+msgstr ""
+
+#: ../../dev.rst:1341
+# b44bd176077846608c9154828fe17bcf
+msgid "America/Halifax"
+msgstr ""
+
+#: ../../dev.rst:1341
+# c5a671425aa645e48ca5e6be639d3b47
+msgid "America/La\\_Paz"
+msgstr ""
+
+#: ../../dev.rst:1343
+# a0e45644509541e29e7ff3892d29a43f
+msgid "America/Santiago"
+msgstr ""
+
+#: ../../dev.rst:1343
+# 29dc0b49bfca4c04a4dae85abef0fd73
+msgid "America/St\\_Johns"
+msgstr ""
+
+#: ../../dev.rst:1343
+# 58a82f8d3d494e66a34d3e0c237636db
+msgid "America/Araguaina"
+msgstr ""
+
+#: ../../dev.rst:1345
+# 5eb2f12569994569b889e252c121cab4
+msgid "America/Argentina/Buenos\\_Aires"
+msgstr ""
+
+#: ../../dev.rst:1345
+# c0e280db42da49069491a621fb47e797
+msgid "America/Cayenne"
+msgstr ""
+
+#: ../../dev.rst:1345
+# 3b6ac15163534a83ad4912f04b6f647c
+msgid "America/Godthab"
+msgstr ""
+
+#: ../../dev.rst:1347
+# 53214010b12741a291c22600879bec15
+msgid "America/Montevideo"
+msgstr ""
+
+#: ../../dev.rst:1347
+# ed82003665954529b286afe7c3469042
+msgid "Etc/GMT+2"
+msgstr ""
+
+#: ../../dev.rst:1347
+# 51d8d1bb8ab2480d98d28b9f9a447b4d
+msgid "Atlantic/Azores"
+msgstr ""
+
+#: ../../dev.rst:1349
+# c61f4b615d274d368cad81dcdbb9b7a2
+msgid "Atlantic/Cape\\_Verde"
+msgstr ""
+
+#: ../../dev.rst:1349
+# f9d4e688062c42fbafbfe3a9c4f58b4c
+msgid "Africa/Casablanca"
+msgstr ""
+
+#: ../../dev.rst:1349
+# 9b681fc4d898424c9fabfdb630ee269b
+msgid "Etc/UTC"
+msgstr ""
+
+#: ../../dev.rst:1351
+# a67e41b70bea47fd9cbdcbde39993cfc
+msgid "Atlantic/Reykjavik"
+msgstr ""
+
+#: ../../dev.rst:1351
+# 50c1ed24011c4ba0ad7d2253d5ca7cea
+msgid "Europe/London"
+msgstr ""
+
+#: ../../dev.rst:1351
+# 4484c135ceaa41068801eca54c861c94
+msgid "CET"
+msgstr ""
+
+#: ../../dev.rst:1353
+# bce1e8f01b3d42d4b7d49bf033474acb
+msgid "Europe/Bucharest"
+msgstr ""
+
+#: ../../dev.rst:1353
+# 7d1b52a170d74857ae27f2aedd17dc98
+msgid "Africa/Johannesburg"
+msgstr ""
+
+#: ../../dev.rst:1353
+# f231b78cbc48480684461d7bc739ef8e
+msgid "Asia/Beirut"
+msgstr ""
+
+#: ../../dev.rst:1355
+# 6747f64e178249d48a4d77c1bdbc5193
+msgid "Africa/Cairo"
+msgstr ""
+
+#: ../../dev.rst:1355
+# 33156f8d830c4ca4b4b1ba771de526d9
+msgid "Asia/Jerusalem"
+msgstr ""
+
+#: ../../dev.rst:1355
+# afcbe08d5e2546ea9b2f1c65664408db
+msgid "Europe/Minsk"
+msgstr ""
+
+#: ../../dev.rst:1357
+# 0f082c471d22446a80ceb0c1d6db6724
+msgid "Europe/Moscow"
+msgstr ""
+
+#: ../../dev.rst:1357
+# 3b743c29a1e44d82b03502baa0493920
+msgid "Africa/Nairobi"
+msgstr ""
+
+#: ../../dev.rst:1357
+# d4ad3b6a25534b3d99fb57bfe804a9f6
+msgid "Asia/Karachi"
+msgstr ""
+
+#: ../../dev.rst:1359
+# 7336fd24e11a49919c81b27808f8f7b3
+msgid "Asia/Kolkata"
+msgstr ""
+
+#: ../../dev.rst:1359
+# 9be1ff8a167945d18ed0f5d337d72dbe
+msgid "Asia/Bangkok"
+msgstr ""
+
+#: ../../dev.rst:1359
+# 507cb5a2068046cdb526c37a2b4781ab
+msgid "Asia/Shanghai"
+msgstr ""
+
+#: ../../dev.rst:1361
+# f03e006791a144b390c53cb1eedfb979
+msgid "Asia/Kuala\\_Lumpur"
+msgstr ""
+
+#: ../../dev.rst:1361
+# e16d88cb949b4c23b61fced79bb9be74
+msgid "Australia/Perth"
+msgstr ""
+
+#: ../../dev.rst:1361
+# c1eeabdd9492421ca820326d5f5a6bdb
+msgid "Asia/Taipei"
+msgstr ""
+
+#: ../../dev.rst:1363
+# cdb1296e6ff247f1bec854c83d5d3c5d
+msgid "Asia/Tokyo"
+msgstr ""
+
+#: ../../dev.rst:1363
+# 681168bfa81f4148b15066fe97341e46
+msgid "Asia/Seoul"
+msgstr ""
+
+#: ../../dev.rst:1363
+# 88d44fd632124c8fb29a909a45acdac7
+msgid "Australia/Adelaide"
+msgstr ""
+
+#: ../../dev.rst:1365
+# 6edbd9d03d5b418a8abc9baa6828c62e
+msgid "Australia/Darwin"
+msgstr ""
+
+#: ../../dev.rst:1365
+# c2da9953f84043caaf3e3a4b58c8e3da
+msgid "Australia/Brisbane"
+msgstr ""
+
+#: ../../dev.rst:1365
+# 0d793eb4459e4c22991796e567924f99
+msgid "Australia/Canberra"
+msgstr ""
+
+#: ../../dev.rst:1367
+# e524313a85ba4b209c5de1d49051d1b8
+msgid "Pacific/Guam"
+msgstr ""
+
+#: ../../dev.rst:1367
+# 8e890fe610da40a782aa5ae36e97ccff
+msgid "Pacific/Auckland"
+msgstr ""
+