You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cloudstack.apache.org by se...@apache.org on 2014/06/30 11:44:39 UTC
[9/9] git commit: New tx/config and pot files in preparation for 4.4
cut
New tx/config and pot files in preparation for 4.4 cut
Project: http://git-wip-us.apache.org/repos/asf/cloudstack-docs-install/repo
Commit: http://git-wip-us.apache.org/repos/asf/cloudstack-docs-install/commit/bdc55a40
Tree: http://git-wip-us.apache.org/repos/asf/cloudstack-docs-install/tree/bdc55a40
Diff: http://git-wip-us.apache.org/repos/asf/cloudstack-docs-install/diff/bdc55a40
Branch: refs/heads/master
Commit: bdc55a40562f7b1b3db3c47d50d016ee2d8ee174
Parents: 909731c
Author: Sebastien Goasguen <ru...@gmail.com>
Authored: Mon Jun 30 11:44:19 2014 +0200
Committer: Sebastien Goasguen <ru...@gmail.com>
Committed: Mon Jun 30 11:44:19 2014 +0200
----------------------------------------------------------------------
.tx/config | 25 +
source/locale/pot/building_from_source.pot | 328 +--
.../pot/choosing_deployment_architecture.pot | 488 ++--
source/locale/pot/configuration.pot | 2239 +++++++++---------
source/locale/pot/hypervisor/hyperv.pot | 449 ++++
source/locale/pot/hypervisor/kvm.pot | 949 ++++++++
source/locale/pot/hypervisor/lxc.pot | 621 +++++
source/locale/pot/hypervisor/vsphere.pot | 1681 +++++++++++++
source/locale/pot/hypervisor/xenserver.pot | 944 ++++++++
source/locale/pot/index.pot | 78 +-
source/locale/pot/installation.pot | 1028 ++++----
source/locale/pot/network_setup.pot | 1466 ++++++------
source/locale/pot/optional_installation.pot | 1066 ++++-----
source/locale/pot/qig.pot | 540 ++---
source/locale/pot/storage_setup.pot | 240 +-
15 files changed, 8398 insertions(+), 3744 deletions(-)
----------------------------------------------------------------------
http://git-wip-us.apache.org/repos/asf/cloudstack-docs-install/blob/bdc55a40/.tx/config
----------------------------------------------------------------------
diff --git a/.tx/config b/.tx/config
index 1ec5c80..144c93d 100644
--- a/.tx/config
+++ b/.tx/config
@@ -57,3 +57,28 @@ file_filter = source/locale/<lang>/LC_MESSAGES/storage_setup.po
source_file = source/locale/pot/storage_setup.pot
source_lang = en
+[apache-cloudstack-installation-rtd.hypervisor--hyperv]
+file_filter = source/locale/<lang>/LC_MESSAGES/hypervisor/hyperv.po
+source_file = source/locale/pot/hypervisor/hyperv.pot
+source_lang = en
+
+[apache-cloudstack-installation-rtd.hypervisor--kvm]
+file_filter = source/locale/<lang>/LC_MESSAGES/hypervisor/kvm.po
+source_file = source/locale/pot/hypervisor/kvm.pot
+source_lang = en
+
+[apache-cloudstack-installation-rtd.hypervisor--lxc]
+file_filter = source/locale/<lang>/LC_MESSAGES/hypervisor/lxc.po
+source_file = source/locale/pot/hypervisor/lxc.pot
+source_lang = en
+
+[apache-cloudstack-installation-rtd.hypervisor--vsphere]
+file_filter = source/locale/<lang>/LC_MESSAGES/hypervisor/vsphere.po
+source_file = source/locale/pot/hypervisor/vsphere.pot
+source_lang = en
+
+[apache-cloudstack-installation-rtd.hypervisor--xenserver]
+file_filter = source/locale/<lang>/LC_MESSAGES/hypervisor/xenserver.po
+source_file = source/locale/pot/hypervisor/xenserver.pot
+source_lang = en
+
http://git-wip-us.apache.org/repos/asf/cloudstack-docs-install/blob/bdc55a40/source/locale/pot/building_from_source.pot
----------------------------------------------------------------------
diff --git a/source/locale/pot/building_from_source.pot b/source/locale/pot/building_from_source.pot
index c7a1d7c..1433375 100644
--- a/source/locale/pot/building_from_source.pot
+++ b/source/locale/pot/building_from_source.pot
@@ -8,7 +8,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Apache CloudStack Installation Documentation 4\n"
"Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2014-03-31 14:02-0400\n"
+"POT-Creation-Date: 2014-06-30 11:42+0200\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EM...@ADDRESS>\n"
"Language-Team: LANGUAGE <LL...@li.org>\n"
@@ -16,418 +16,418 @@ msgstr ""
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
-#: ../../building_from_source.rst:17
-# 5396f27a8ff74a7d8817526ff37ec438
+#: ../../building_from_source.rst:18
+# ef11ea68beec49c5871db512f598d676
msgid "Building from Source"
msgstr ""
-#: ../../building_from_source.rst:19
-# 60bf699c76df434992e36d41c5f00bcf
+#: ../../building_from_source.rst:20
+# 2a043bdd667b4d9293f70ad36316281e
msgid "The official CloudStack release is always in source code form. You will likely be able to find \"convenience binaries,\" the source is the canonical release. In this section, we'll cover acquiring the source release and building that so that you can deploy it using Maven or create Debian packages or RPMs."
msgstr ""
-#: ../../building_from_source.rst:25
-# 32892fc6365642cd81e9910e84bb80c0
+#: ../../building_from_source.rst:26
+# 34b9935b1b234772875a5632f77cc973
msgid "Note that building and deploying directly from source is typically not the most efficient way to deploy an IaaS. However, we will cover that method as well as building RPMs or Debian packages for deploying CloudStack."
msgstr ""
-#: ../../building_from_source.rst:30
-# 7e67792d5ec241af80724aa269cc8f40
+#: ../../building_from_source.rst:31
+# dc09a8fd969d4628811a6127bb066d15
msgid "The instructions here are likely version-specific. That is, the method for building from source for the 4.0.x series is different from the 4.1.x series."
msgstr ""
-#: ../../building_from_source.rst:34
-# 59bd739639154797bb627d316198b3d2
+#: ../../building_from_source.rst:35
+# 1122421db6114fc9919baefb86af655a
msgid "If you are working with a unreleased version of CloudStack, see the INSTALL.md file in the top-level directory of the release."
msgstr ""
-#: ../../building_from_source.rst:38
-# 54b5d37f192048519bd2ed85a3ddc5b3
+#: ../../building_from_source.rst:40
+# 70eb2ab692764b6dbb6ea174f0062a59
msgid "Getting the release"
msgstr ""
-#: ../../building_from_source.rst:40
-# d3311764aeed4cc0b185062d99f5c4e9
+#: ../../building_from_source.rst:42
+# 16e7f13a2bf342fd9eff4ec10614bfb7
msgid "You can download the latest CloudStack release from the `Apache CloudStack project download page <http://cloudstack.apache.org/downloads.html>`_."
msgstr ""
-#: ../../building_from_source.rst:43
-# c0f0cbed8f7942dd8cdf0ec15232e760
+#: ../../building_from_source.rst:46
+# 66ddf14b21c1450b84222ff24a97c8a1
msgid "Prior releases are available via archive.apache.org as well. See the downloads page for more information on archived releases."
msgstr ""
-#: ../../building_from_source.rst:46
-# efebd9e2df61457482c9cb8efbadd736
+#: ../../building_from_source.rst:49
+# ffcd1760171b4c22aadfbdf0a143c2f3
msgid "You'll notice several links under the 'Latest release' section. A link to a file ending in ``tar.bz2``, as well as a PGP/GPG signature, MD5, and SHA512 file."
msgstr ""
-#: ../../building_from_source.rst:52
-# c8757326ca1c47f989906e77b64c17db
+#: ../../building_from_source.rst:53
+# 25bd15343d884479bb06e47381b678fd
msgid "The ``tar.bz2`` file contains the Bzip2-compressed tarball with the source code."
msgstr ""
-#: ../../building_from_source.rst:57
-# d1f48a19cc14413e90a8164ef6e496ed
+#: ../../building_from_source.rst:56
+# 3d236d0dfc154c268fed0612bdd129ce
msgid "The ``.asc`` file is a detached cryptographic signature that can be used to help verify the authenticity of the release."
msgstr ""
-#: ../../building_from_source.rst:62
-# b45289cb4cba4686b60ab976bf75eea1
+#: ../../building_from_source.rst:59
+# 6d4f2dc258d643b8b8733a59476db314
msgid "The ``.md5`` file is an MD5 hash of the release to aid in verify the validity of the release download."
msgstr ""
-#: ../../building_from_source.rst:67
-# 637044e3649f406b8e5b6a441ba355c7
+#: ../../building_from_source.rst:62
+# 3a3f100d4fce444482fc82808ddc6b88
msgid "The ``.sha`` file is a SHA512 hash of the release to aid in verify the validity of the release download."
msgstr ""
-#: ../../building_from_source.rst:71
-# 4da67860f4454b7aa0c0fc6f76b59317
+#: ../../building_from_source.rst:67
+# 5b9f966ab0404b0895cad4a389bc200c
msgid "Verifying the downloaded release"
msgstr ""
-#: ../../building_from_source.rst:73
-# 184cd04b405b4136b74c0644e4720e2a
+#: ../../building_from_source.rst:69
+# db3e51bdf33d4742a685c0d6162f05a4
msgid "There are a number of mechanisms to check the authenticity and validity of a downloaded release."
msgstr ""
-#: ../../building_from_source.rst:77
-# 787318aa8f2049098a34030e7bb9220d
+#: ../../building_from_source.rst:74
+# a41259b8a7754a1d968844b286750d17
msgid "Getting the KEYS"
msgstr ""
-#: ../../building_from_source.rst:79
-# af2e7aafde3c45d79c93d848f16df84f
+#: ../../building_from_source.rst:76
+# 070bfe72ade6433292ddf947a78ff960
msgid "To enable you to verify the GPG signature, you will need to download the `KEYS <http://www.apache.org/dist/cloudstack/KEYS>`_ file."
msgstr ""
-#: ../../building_from_source.rst:82
-# b7351a3de11b4d5783f051a524e6d6d9
+#: ../../building_from_source.rst:79
+# 639635ff8564492fb4965f5da6a4215f
msgid "You next need to import those keys, which you can do by running:"
msgstr ""
-#: ../../building_from_source.rst:89
-# 6a67d67c239c4450b6b0454f78e1e976
+#: ../../building_from_source.rst:87
+# 7cad52cd29334223a2eb5a524fa31229
msgid "GPG"
msgstr ""
-#: ../../building_from_source.rst:91
-# c41516ba45df4b8c8c82f0437fd1cf0f
+#: ../../building_from_source.rst:89
+# 108a752dff73440c9de3ffbca5f64843
msgid "The CloudStack project provides a detached GPG signature of the release. To check the signature, run the following command:"
msgstr ""
-#: ../../building_from_source.rst:98
-# 06a586af894b41a191ca74d565fd5646
+#: ../../building_from_source.rst:96
+# 7b1992ef9c664f60bed1e3da72b53326
msgid "If the signature is valid you will see a line of output that contains 'Good signature'."
msgstr ""
-#: ../../building_from_source.rst:102
-# 7c1c3790e01440f88dc8e8f108c69180
+#: ../../building_from_source.rst:101
+# 2f3891019c1c4d879aea2ce4a283292a
msgid "MD5"
msgstr ""
-#: ../../building_from_source.rst:104
-# e47ab7059cdf4276968ef9219d824967
+#: ../../building_from_source.rst:103
+# ddbbe1736210472d8f2c8d157a51884d
msgid "In addition to the cryptographic signature, CloudStack has an MD5 checksum that you can use to verify the download matches the release. You can verify this hash by executing the following command:"
msgstr ""
-#: ../../building_from_source.rst:112
-# 471b0fafe73b4bebb48f271b2be0323b
+#: ../../building_from_source.rst:111
+# 9490a741b6b049feb039b5dd8c7bace1
msgid "If this successfully completes you should see no output. If there is any output from them, then there is a difference between the hash you generated locally and the hash that has been pulled from the server."
msgstr ""
#: ../../building_from_source.rst:117
-# a42234cf484d448ea3a079cc44d505c4
+# a34badbd49654f2e9c9040981cdfa1be
msgid "SHA512"
msgstr ""
#: ../../building_from_source.rst:119
-# f6904f51119c4bd7a0e6d9d42868d7cd
+# 8137cfe2c2df43c587b7bfed84c0612e
msgid "In addition to the MD5 hash, the CloudStack project provides a SHA512 cryptographic hash to aid in assurance of the validity of the downloaded release. You can verify this hash by executing the following command:"
msgstr ""
#: ../../building_from_source.rst:127
-# 2b02e428976242d5a9513dc999f80d9a
+# 45114708d09246febbeee238d2b1e303
msgid "If this command successfully completes you should see no output. If there is any output from them, then there is a difference between the hash you generated locally and the hash that has been pulled from the server."
msgstr ""
-#: ../../building_from_source.rst:133
-# 20ae79e8693540af926f68f5b8a08da3
+#: ../../building_from_source.rst:134
+# 48a54f38aeb04d938f6ce37e3ed8b1d3
msgid "Prerequisites for building Apache CloudStack"
msgstr ""
-#: ../../building_from_source.rst:135
-# 8de67a9fdaea48faa67ab89f641adc4b
+#: ../../building_from_source.rst:136
+# 4d1bceb893204853a12377f796db8762
msgid "There are a number of prerequisites needed to build CloudStack. This document assumes compilation on a Linux system that uses RPMs or DEBs for package management."
msgstr ""
-#: ../../building_from_source.rst:139
-# 9c13e54d32b5455aaab36099aa2535a4
+#: ../../building_from_source.rst:140
+# d618af2b2ace42e1a270c753a9be20e6
msgid "You will need, at a minimum, the following to compile CloudStack:"
msgstr ""
-#: ../../building_from_source.rst:143
-# 0146a3cb86884d318cf934c639b76449
+#: ../../building_from_source.rst:142
+# 06302615cd204c05bb9ee7c9a463a336
msgid "Maven (version 3)"
msgstr ""
-#: ../../building_from_source.rst:147
-# 005189dfa25b4c66b039e0267fdbea5e
+#: ../../building_from_source.rst:144
+# 12e01c26b3b343d39e522dbde2704e6f
msgid "Java (OpenJDK 1.6 or Java 7/OpenJDK 1.7)"
msgstr ""
-#: ../../building_from_source.rst:151
-# 2c58fc00271e445e861705983b16a5f3
+#: ../../building_from_source.rst:146
+# fad73fd5cd0d43dba668f37c6d2baaa5
msgid "Apache Web Services Common Utilities (ws-commons-util)"
msgstr ""
-#: ../../building_from_source.rst:155
-# 989f684d1b8a456bac9a81d3f924d16f
+#: ../../building_from_source.rst:148
+# 3cd08240ad30472e8a18797edea67732
msgid "MySQL"
msgstr ""
-#: ../../building_from_source.rst:159
-# 44ef1202eb3e4c61b84f22fbc433a538
+#: ../../building_from_source.rst:150
+# 34fdc352ce70420ebf3d4c32e0ef790e
msgid "MySQLdb (provides Python database API)"
msgstr ""
-#: ../../building_from_source.rst:163
-# e84e7644c89a4669991bc0a1013171c1
+#: ../../building_from_source.rst:152
+# b94e3afe30b04baa84d114d1cc67e56b
msgid "Tomcat 6 (not 6.0.35)"
msgstr ""
-#: ../../building_from_source.rst:167
-# fe2b1db48eb9421d937189144b944911
+#: ../../building_from_source.rst:154
+# 6269e20f8b1248af837e3d75b2d56cf7
msgid "genisoimage"
msgstr ""
-#: ../../building_from_source.rst:171
-# bc55f42faeef4adbb28f3b39cfe334ef
+#: ../../building_from_source.rst:156
+# d43cbcb988fd42e08c351dfdaaa519aa
msgid "rpmbuild or dpkg-dev"
msgstr ""
-#: ../../building_from_source.rst:174
-# 7b45a167b6874f9a8ba73a17d7f1a6c5
+#: ../../building_from_source.rst:160
+# 27d74522549f4b85ac4bcd78e737b72c
msgid "Extracting source"
msgstr ""
-#: ../../building_from_source.rst:176
-# 3b2090380fcf4c12ad2638d91cb45d43
+#: ../../building_from_source.rst:162
+# 25f6064ab9e64561948107df87e2d317
msgid "Extracting the CloudStack release is relatively simple and can be done with a single command as follows:"
msgstr ""
-#: ../../building_from_source.rst:183
-# 0f5f07d38bd54fb2a0e69c6fb28e1967
+#: ../../building_from_source.rst:169
+# 78aa3b8b39704c1f8561b069d0cfcb4d
msgid "You can now move into the directory:"
msgstr ""
-#: ../../building_from_source.rst:190
-# aa9e9e76ff6441498d8531802e1afa7e
+#: ../../building_from_source.rst:177
+# c46dc00000204d2cb73ae63e116bc55a
msgid "Building DEB packages"
msgstr ""
-#: ../../building_from_source.rst:192
-# 0eca44ba0f1c4b3ba1e65ab3a0268db9
+#: ../../building_from_source.rst:179
+# 4b6cce4d00f748ada32203791b19b088
msgid "In addition to the bootstrap dependencies, you'll also need to install several other dependencies. Note that we recommend using Maven 3, which is not currently available in 12.04.1 LTS. So, you'll also need to add a PPA repository that includes Maven 3. After running the command ``add-apt-repository``, you will be prompted to continue and a GPG key will be added."
msgstr ""
-#: ../../building_from_source.rst:207
-# 8014eb3c824248f28bfaff9deeabaced
+#: ../../building_from_source.rst:194
+# 283980d16b48466bb2a2d3b17ff1fede
msgid "While we have defined, and you have presumably already installed the bootstrap prerequisites, there are a number of build time prerequisites that need to be resolved. CloudStack uses maven for dependency resolution. You can resolve the buildtime depdencies for CloudStack by running:"
msgstr ""
-#: ../../building_from_source.rst:217
-# f6f09e0f7e3c49129fe0c281cc144489
+#: ../../building_from_source.rst:204
+# 7e08137b290649cda9b8e9b728ff33aa
msgid "Now that we have resolved the dependencies we can move on to building CloudStack and packaging them into DEBs by issuing the following command."
msgstr ""
-#: ../../building_from_source.rst:225
-# f345823b71dc4836a97a160bfbb40a9e
+#: ../../building_from_source.rst:212
+# ec3f8fd379b7417294d5b01ce47f367f
msgid "This command will build the following debian packages. You should have all of the following:"
msgstr ""
-#: ../../building_from_source.rst:239
-# 88e77857a4fa4e9b80e912d82a405591
+#: ../../building_from_source.rst:227
+# 8521111f14944fbc8f62bfb2f4cb8a0b
msgid "Setting up an APT repo"
msgstr ""
-#: ../../building_from_source.rst:241
-# 7db71198e1aa4db08ce8f174f11546aa
+#: ../../building_from_source.rst:229
+# f937d1aff1e74e8d8869d99a5dcf0315
msgid "After you've created the packages, you'll want to copy them to a system where you can serve the packages over HTTP. You'll create a directory for the packages and then use ``dpkg-scanpackages`` to create ``Packages.gz``, which holds information about the archive structure. Finally, you'll add the repository to your system(s) so you can install the packages using APT."
msgstr ""
-#: ../../building_from_source.rst:248
-# 882df6f5a6a542e08af5d64a8c440f9b
+#: ../../building_from_source.rst:236
+# 77189e27fd6648db96421e68ea2197c7
msgid "The first step is to make sure that you have the **dpkg-dev** package installed. This should have been installed when you pulled in the **debhelper** application previously, but if you're generating ``Packages.gz`` on a different system, be sure that it's installed there as well."
msgstr ""
-#: ../../building_from_source.rst:258
-# 6b45808c7afe48eab8f0e54e28996c78
+#: ../../building_from_source.rst:246
+# ca7c2a636f664075b7104554ed4ea25d
msgid "The next step is to copy the DEBs to the directory where they can be served over HTTP. We'll use ``/var/www/cloudstack/repo`` in the examples, but change the directory to whatever works for you."
msgstr ""
-#: ../../building_from_source.rst:271
-# 9f7bfa37a80641409e1400b8548efb29
+#: ../../building_from_source.rst:258
+# 5aed13bc18cc47d0a3d386be28663478
msgid "You can safely ignore the warning about a missing override file."
msgstr ""
-#: ../../building_from_source.rst:273
-# d8e564f896ea416898d007e9d49d6718
+#: ../../building_from_source.rst:260
+# 2ab43ed9a4ad40339e0b43646ae7e6a7
msgid "Now you should have all of the DEB packages and ``Packages.gz`` in the ``binary`` directory and available over HTTP. (You may want to use ``wget`` or ``curl`` to test this before moving on to the next step.)"
msgstr ""
-#: ../../building_from_source.rst:278
-# c7c808299766447184af66ba621c649f
+#: ../../building_from_source.rst:266
+# 410e592ce4134e54a0c21c37dc761c1d
msgid "Configuring your machines to use the APT repository"
msgstr ""
-#: ../../building_from_source.rst:280
-# dfdd1c5b583743d0b5156002e9f3ffb9
+#: ../../building_from_source.rst:268
+# ec3e958425e048aa8e4fb1916ef372de
msgid "Now that we have created the repository, you need to configure your machine to make use of the APT repository. You can do this by adding a repository file under ``/etc/apt/sources.list.d``. Use your preferred editor to create ``/etc/apt/sources.list.d/cloudstack.list`` with this line:"
msgstr ""
-#: ../../building_from_source.rst:290
-# 8cad604cc3474e2bb424225f2d519465
+#: ../../building_from_source.rst:278
+# affbe297a4444a9e9d87f2bb39672d9f
msgid "Now that you have the repository info in place, you'll want to run another update so that APT knows where to find the CloudStack packages."
msgstr ""
-#: ../../building_from_source.rst:297
-# ae0dd676f4ec4158b5f3bd6fd9c6c414
+#: ../../building_from_source.rst:285
+# 2806875948bd4534b353edcf499fd5af
msgid "You can now move on to the instructions under Install on Ubuntu."
msgstr ""
-#: ../../building_from_source.rst:300
-# 99e76b064e8447a78d810b22c43f6f41
+#: ../../building_from_source.rst:289
+# f14be60974c1461e99bd00a8090db43a
msgid "Building RPMs from Source"
msgstr ""
-#: ../../building_from_source.rst:302
-# f2be124577f84dd497fb762733f58ef8
+#: ../../building_from_source.rst:291
+# 8f87d648db12475a82e931fdba69af9d
msgid "As mentioned previously in `“Prerequisites for building Apache CloudStack” <#prerequisites-for-building-apache-cloudstack>`_, you will need to install several prerequisites before you can build packages for CloudStack. Here we'll assume you're working with a 64-bit build of CentOS or Red Hat Enterprise Linux."
msgstr ""
-#: ../../building_from_source.rst:316
-# 147d967fe07344fda8b630d94ecbf22e
+#: ../../building_from_source.rst:305
+# c37ae1838eb34ab694493fa102119691
msgid "Next, you'll need to install build-time dependencies for CloudStack with Maven. We're using Maven 3, so you'll want to `grab a Maven 3 tarball <http://maven.apache.org/download.cgi>`_ and uncompress it in your home directory (or whatever location you prefer):"
msgstr ""
-#: ../../building_from_source.rst:329
-# 1a9e316005174aeaa91a7dcfbaade092
+#: ../../building_from_source.rst:318
+# afb9d4d455cc4a689b58d254dcd9896d
msgid "Maven also needs to know where Java is, and expects the JAVA\\_HOME environment variable to be set:"
msgstr ""
-#: ../../building_from_source.rst:336
-# 4ab8a6164f45425aa7186cdf64e8d55e
+#: ../../building_from_source.rst:325
+# a8eaac2e266d48dabaf04dff48781e01
msgid "Verify that Maven is installed correctly:"
msgstr ""
-#: ../../building_from_source.rst:342
-# 3843f8810db04c80a8eee7f3cae3f4bf
+#: ../../building_from_source.rst:331
+# 76c3a8ce403d460bbd79e42edb06fb62
msgid "You probably want to ensure that your environment variables will survive a logout/reboot. Be sure to update ``~/.bashrc`` with the PATH and JAVA\\_HOME variables."
msgstr ""
-#: ../../building_from_source.rst:346
-# 490ba6dd066441edb4adc61fb071e8a7
+#: ../../building_from_source.rst:335
+# 7e91515caf2d407b8196d2bb067f12f6
msgid "Building RPMs for CloudStack is fairly simple. Assuming you already have the source downloaded and have uncompressed the tarball into a local directory, you're going to be able to generate packages in just a few minutes."
msgstr ""
-#: ../../building_from_source.rst:353
-# e0cc268134ba44c9a96d06b97e687c39
+#: ../../building_from_source.rst:341
+# bf6a8f0ff1ab4b5ab8af48ee83cedda3
msgid "Packaging has Changed. If you've created packages for CloudStack previously, you should be aware that the process has changed considerably since the project has moved to using Apache Maven. Please be sure to follow the steps in this section closely."
msgstr ""
-#: ../../building_from_source.rst:356
-# b79c6f303f0544719c940cfc32027819
+#: ../../building_from_source.rst:348
+# a058ef55f9d544c59a3d9167d13e55f7
msgid "Generating RPMS"
msgstr ""
-#: ../../building_from_source.rst:358
-# 03b60158092748f6aa6b7d5994c892d2
+#: ../../building_from_source.rst:350
+# b30e84d7601d4d81a71bcd33b034f374
msgid "Now that we have the prerequisites and source, you will cd to the `packaging/centos63/` directory."
msgstr ""
-#: ../../building_from_source.rst:364
-# 3154e33699074662a1395386b9c3a4a8
+#: ../../building_from_source.rst:357
+# 9f33b2b9cbfd4211ab425cf8bb35a9d9
msgid "Generating RPMs is done using the ``package.sh`` script:"
msgstr ""
-#: ../../building_from_source.rst:370
-# 68d539d69bc54749a69f503b004525b0
+#: ../../building_from_source.rst:363
+# b91a6668f8414cfaac447e79705af239
msgid "That will run for a bit and then place the finished packages in ``dist/rpmbuild/RPMS/x86_64/``."
msgstr ""
-#: ../../building_from_source.rst:373
-# 6ba124f893f243f7af26aefe9811bc73
+#: ../../building_from_source.rst:366
+# 027abcc96e1144cfbd6511ca4c31b35d
msgid "You should see the following RPMs in that directory:"
msgstr ""
-#: ../../building_from_source.rst:386
-# 370fc4f0661540ca95e53491f26361ea
+#: ../../building_from_source.rst:380
+# fe5a036719b948639b86eb45194cbb45
msgid "Creating a yum repo"
msgstr ""
-#: ../../building_from_source.rst:388
-# bbc6c3630b1a44dd92fe24fb24a32c43
+#: ../../building_from_source.rst:382
+# fa6516e0378d40b8b6571d4f92e5cf60
msgid "While RPMs is a useful packaging format - it's most easily consumed from Yum repositories over a network. The next step is to create a Yum Repo with the finished packages:"
msgstr ""
-#: ../../building_from_source.rst:404
-# 7ca5148dbc3f47a195336d3ea4dc066d
+#: ../../building_from_source.rst:398
+# 7db0ebdd90574721be216ccf32b72064
msgid "The files and directories within ``~/tmp/repo`` can now be uploaded to a web server and serve as a yum repository."
msgstr ""
-#: ../../building_from_source.rst:408
-# 3c1f1920404c4b4b9aed29b8216a8ca1
+#: ../../building_from_source.rst:403
+# 34af5e2901ba47ad90a764c39024011a
msgid "Configuring your systems to use your new yum repository"
msgstr ""
-#: ../../building_from_source.rst:410
-# bbc87560e0c642ecbfa67f722b3b9693
+#: ../../building_from_source.rst:405
+# 3e7e415e4d0f430b8eeb67194f885455
msgid "Now that your yum repository is populated with RPMs and metadata we need to configure the machines that need to install CloudStack. Create a file named ``/etc/yum.repos.d/cloudstack.repo`` with this information:"
msgstr ""
-#: ../../building_from_source.rst:422
-# b398f895b7ff4282b6613bad45a98c08
+#: ../../building_from_source.rst:417
+# 16a2be281d5d4d11bdb334ea963026db
msgid "Completing this step will allow you to easily install CloudStack on a number of machines across the network."
msgstr ""
-#: ../../building_from_source.rst:426
-# 478d4e8b829044e8949f587dd0f09b52
+#: ../../building_from_source.rst:422
+# 592481f4523641afa7fb8b6ef7a582c3
msgid "Building Non-OSS"
msgstr ""
-#: ../../building_from_source.rst:428
-# 2fe549e0cdc44e51ba030c3fa3499914
+#: ../../building_from_source.rst:424
+# 056563e7eea94421b05d5fcd09befd25
msgid "If you need support for the VMware, NetApp, F5, NetScaler, SRX, or any other non-Open Source Software (nonoss) plugins, you'll need to download a few components on your own and follow a slightly different procedure to build from source."
msgstr ""
-#: ../../building_from_source.rst:435
-# 46d5a64c225c401c8e2b16f77095e6f3
+#: ../../building_from_source.rst:430
+# f6587f3c5b644126b1ed2229b15c648b
msgid "Some of the plugins supported by CloudStack cannot be distributed with CloudStack for licensing reasons. In some cases, some of the required libraries/JARs are under a proprietary license. In other cases, the required libraries may be under a license that's not compatible with `Apache's licensing guidelines for third-party products <http://www.apache.org/legal/resolved.html#category-x>`_."
msgstr ""
-#: ../../building_from_source.rst:439
-# b30c64ffa9bb46819fc70c71f7606020
+#: ../../building_from_source.rst:437
+# bc2bb0c113ac453e9f9b4468b91f1139
msgid "To build the Non-OSS plugins, you'll need to have the requisite JARs installed under the ``deps`` directory."
msgstr ""
-#: ../../building_from_source.rst:442
-# 965deab2226a46d98c7e5962c98f344e
+#: ../../building_from_source.rst:440
+# a59479563c7742e49beb8e5ecb8efba1
msgid "Because these modules require dependencies that can't be distributed with CloudStack you'll need to download them yourself. Links to the most recent dependencies are listed on the `*How to build CloudStack* <https://cwiki.apache.org/confluence/display/CLOUDSTACK/How+to+build+CloudStack>`_ page on the wiki."
msgstr ""
-#: ../../building_from_source.rst:449
-# 78a1f8deba41498f80a2f83003d44bc3
+#: ../../building_from_source.rst:446
+# d9d9d34be2604c18a3b9107dbf384181
msgid "You may also need to download `vhd-util <http://download.cloud.com.s3.amazonaws.com/tools/vhd-util>`_, which was removed due to licensing issues. You'll copy vhd-util to the ``scripts/vm/hypervisor/xenserver/`` directory."
msgstr ""
-#: ../../building_from_source.rst:456
-# b4c294257936418c9d6c6889ce615a13
+#: ../../building_from_source.rst:451
+# bfbd7215ff0345f183a7946f620b1368
msgid "Once you have all the dependencies copied over, you'll be able to build CloudStack with the ``noredist`` option:"
msgstr ""
-#: ../../building_from_source.rst:466
-# c135a16bcffe490da30abf3c3425ccdb
+#: ../../building_from_source.rst:459
+# 252d45f71b814e409bdd693e44584f8e
msgid "Once you've built CloudStack with the ``noredist`` profile, you can package it using the `“Building RPMs from Source” <#building-rpms-from-source>`_ or `“Building DEB packages” <#building-deb-packages>`_ instructions."
msgstr ""
http://git-wip-us.apache.org/repos/asf/cloudstack-docs-install/blob/bdc55a40/source/locale/pot/choosing_deployment_architecture.pot
----------------------------------------------------------------------
diff --git a/source/locale/pot/choosing_deployment_architecture.pot b/source/locale/pot/choosing_deployment_architecture.pot
index fbf1045..7226ee2 100644
--- a/source/locale/pot/choosing_deployment_architecture.pot
+++ b/source/locale/pot/choosing_deployment_architecture.pot
@@ -8,7 +8,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Apache CloudStack Installation Documentation 4\n"
"Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2014-03-31 14:02-0400\n"
+"POT-Creation-Date: 2014-06-30 11:42+0200\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EM...@ADDRESS>\n"
"Language-Team: LANGUAGE <LL...@li.org>\n"
@@ -16,496 +16,496 @@ msgstr ""
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
-#: ../../choosing_deployment_architecture.rst:17
-# 52edd48cc24f4706b9641e18921e1dfc
+#: ../../choosing_deployment_architecture.rst:18
+# 2c4ff27205844a38ba74b1ffed7d0d4c
msgid "Choosing a Deployment Architecture"
msgstr ""
-#: ../../choosing_deployment_architecture.rst:19
-# 4ebda8e26c5642b79a5e800fb698afcf
+#: ../../choosing_deployment_architecture.rst:20
+# b26daf37d81247238775fca77b416ae2
msgid "The architecture used in a deployment will vary depending on the size and purpose of the deployment. This section contains examples of deployment architecture, including a small-scale deployment useful for test and trial deployments and a fully-redundant large-scale setup for production deployments."
msgstr ""
-#: ../../choosing_deployment_architecture.rst:26
-# e6eca26710584474b1704256861555bd
+#: ../../choosing_deployment_architecture.rst:28
+# 2f09e208c05a4a5aa8f3c9f87ed50c25
msgid "Small-Scale Deployment"
msgstr ""
-#: ../../choosing_deployment_architecture.rst:28
-# 504a3c65a9d44537bca5bac7444ffe77
+#: ../../choosing_deployment_architecture.rst:30
+# 068dcc56cbd24a0083450026b9402fd6
msgid "|Small-Scale Deployment|"
msgstr ""
-#: ../../choosing_deployment_architecture.rst:30
-# f11bad72391b4deb92c5d7118b32d881
+#: ../../choosing_deployment_architecture.rst:32
+# 97e93e20540547229fc5d499cd5d3fc5
msgid "This diagram illustrates the network architecture of a small-scale CloudStack deployment."
msgstr ""
#: ../../choosing_deployment_architecture.rst:35
-# 6ba24ea751eb44d985b826558267d392
+# d0e9d1cd6d02485fbb7569bbcac7691f
msgid "A firewall provides a connection to the Internet. The firewall is configured in NAT mode. The firewall forwards HTTP requests and API calls from the Internet to the Management Server. The Management Server resides on the management network."
msgstr ""
-#: ../../choosing_deployment_architecture.rst:42
-# 3426fafddfbd47eca9b6e972998e3bae
+#: ../../choosing_deployment_architecture.rst:40
+# 3a9520fd64a74db8b3fc06b9204f08a2
msgid "A layer-2 switch connects all physical servers and storage."
msgstr ""
-#: ../../choosing_deployment_architecture.rst:46
-# ef86a72ce6a44739aa9e46e68b64df56
+#: ../../choosing_deployment_architecture.rst:42
+# cd028d62b82f44ffbe0173ee7583fdee
msgid "A single NFS server functions as both the primary and secondary storage."
msgstr ""
-#: ../../choosing_deployment_architecture.rst:51
-# f507e94ad4584311980de03cd3e8915b
+#: ../../choosing_deployment_architecture.rst:45
+# de231b4108f546bc9a6ce6fc4468768c
msgid "The Management Server is connected to the management network."
msgstr ""
-#: ../../choosing_deployment_architecture.rst:54
-# 1ffca21a6b404d6894a747a4583dbad8
+#: ../../choosing_deployment_architecture.rst:49
+# 361b0a48cf54455a94238a38750ee7b9
msgid "Large-Scale Redundant Setup"
msgstr ""
-#: ../../choosing_deployment_architecture.rst:56
-# 99045d1800c5403d892894a8d4fc8002
+#: ../../choosing_deployment_architecture.rst:51
+# 38cdbfb68cca4fd8bc4df9bc1ecd694a
msgid "|Large-Scale Redundant Setup|"
msgstr ""
-#: ../../choosing_deployment_architecture.rst:58
-# d6858644d12a4f22b3de25594cedc309
+#: ../../choosing_deployment_architecture.rst:53
+# 0933dd6019474cfc97b03f67506bc999
msgid "This diagram illustrates the network architecture of a large-scale CloudStack deployment."
msgstr ""
-#: ../../choosing_deployment_architecture.rst:63
-# c4c3f668a4a145c1ac376c5ee607dccb
+#: ../../choosing_deployment_architecture.rst:56
+# e3f81067d12242558eaf4684bb364861
msgid "A layer-3 switching layer is at the core of the data center. A router redundancy protocol like VRRP should be deployed. Typically high-end core switches also include firewall modules. Separate firewall appliances may also be used if the layer-3 switch does not have integrated firewall capabilities. The firewalls are configured in NAT mode. The firewalls provide the following functions:"
msgstr ""
-#: ../../choosing_deployment_architecture.rst:72
-# a23de965c5ec447c84154204ca887790
+#: ../../choosing_deployment_architecture.rst:63
+# a68bb7cb39bd42afa4d9e29f84fa3457
msgid "Forwards HTTP requests and API calls from the Internet to the Management Server. The Management Server resides on the management network."
msgstr ""
-#: ../../choosing_deployment_architecture.rst:78
-# 90da3245af0d4917b933c01a6c8f8332
+#: ../../choosing_deployment_architecture.rst:67
+# 69f7f256ee7341c98affe498692cd667
msgid "When the cloud spans multiple zones, the firewalls should enable site-to-site VPN such that servers in different zones can directly reach each other."
msgstr ""
-#: ../../choosing_deployment_architecture.rst:84
-# 69cfdebf1e6e4d549b52b88a593df61e
+#: ../../choosing_deployment_architecture.rst:71
+# b779613fe6004e40bb248aaeb76d8bc3
msgid "A layer-2 access switch layer is established for each pod. Multiple switches can be stacked to increase port count. In either case, redundant pairs of layer-2 switches should be deployed."
msgstr ""
-#: ../../choosing_deployment_architecture.rst:90
-# 3902d59efe794d8da02773b18a3144ff
+#: ../../choosing_deployment_architecture.rst:75
+# 2032fc16630e41529475a4622c4fb9a2
msgid "The Management Server cluster (including front-end load balancers, Management Server nodes, and the MySQL database) is connected to the management network through a pair of load balancers."
msgstr ""
-#: ../../choosing_deployment_architecture.rst:96
-# 1f11aed9571044e9b9fc673435cb0de7
+#: ../../choosing_deployment_architecture.rst:79
+# cbcfb563ab554774b485b977d456e814
msgid "Secondary storage servers are connected to the management network."
msgstr ""
-#: ../../choosing_deployment_architecture.rst:100
-# ea82de9a210d4a228f110dfe9ecdfb1e
+#: ../../choosing_deployment_architecture.rst:81
+# ed99b388e7464d338ce1e290c13e3e7b
msgid "Each pod contains storage and computing servers. Each storage and computing server should have redundant NICs connected to separate layer-2 access switches."
msgstr ""
-#: ../../choosing_deployment_architecture.rst:105
-# 7ceefe1102644c9ab58eed60cdb7f2bd
+#: ../../choosing_deployment_architecture.rst:87
+# 741500f6260941e79f28d53a5986fc43
msgid "Separate Storage Network"
msgstr ""
-#: ../../choosing_deployment_architecture.rst:107
-# 983feefb13f1459ba566781908bfcd93
+#: ../../choosing_deployment_architecture.rst:89
+# 1ef36fbcddb24180bf412b41f03bcbc4
msgid "In the large-scale redundant setup described in the previous section, storage traffic can overload the management network. A separate storage network is optional for deployments. Storage protocols such as iSCSI are sensitive to network delays. A separate storage network ensures guest network traffic contention does not impact storage performance."
msgstr ""
-#: ../../choosing_deployment_architecture.rst:114
-# edd1971372014c5abd34993129275f55
+#: ../../choosing_deployment_architecture.rst:97
+# b813bc439dea4888b8dddbc9122afe9a
msgid "Multi-Node Management Server"
msgstr ""
-#: ../../choosing_deployment_architecture.rst:116
-# cb554f7ea8af4b899da19bad60af3f11
+#: ../../choosing_deployment_architecture.rst:99
+# 35591778160a4e25a505e5dcd507198f
msgid "The CloudStack Management Server is deployed on one or more front-end servers connected to a single MySQL database. Optionally a pair of hardware load balancers distributes requests from the web. A backup management server set may be deployed using MySQL replication at a remote site to add DR capabilities."
msgstr ""
-#: ../../choosing_deployment_architecture.rst:122
-# 0507a6b19f114eb08708577219e394af
+#: ../../choosing_deployment_architecture.rst:105
+# faff12b3c7c142f59b2a12926ab7c9f7
msgid "|Multi-Node Management Server|"
msgstr ""
-#: ../../choosing_deployment_architecture.rst:124
-# 2afcbc3e300d490d8526df89fe36c54f
+#: ../../choosing_deployment_architecture.rst:107
+# ee629ff1681e4b38bfddfac64b76c7d6
msgid "The administrator must decide the following."
msgstr ""
-#: ../../choosing_deployment_architecture.rst:128
-# 6ea7062b2c3e4d67b082de9b02757b4e
+#: ../../choosing_deployment_architecture.rst:109
+# 3e9822c46e86433cb6d9f4ecbbacda1e
msgid "Whether or not load balancers will be used."
msgstr ""
-#: ../../choosing_deployment_architecture.rst:132
-# 7625aabc231a4cddb9af421ea15281d0
+#: ../../choosing_deployment_architecture.rst:111
+# ab341a95aac3496581377672055b241d
msgid "How many Management Servers will be deployed."
msgstr ""
-#: ../../choosing_deployment_architecture.rst:136
-# ed2af9d37ed34e6e89c234099fcccb4b
+#: ../../choosing_deployment_architecture.rst:113
+# 2dbc1c3c22db42958e785984f5ef93e4
msgid "Whether MySQL replication will be deployed to enable disaster recovery."
msgstr ""
-#: ../../choosing_deployment_architecture.rst:140
-# be8d00f78d464cc2aa58e01d300a948b
+#: ../../choosing_deployment_architecture.rst:118
+# 4858e0bbf6f14d6b990948aacc6e0b74
msgid "Multi-Site Deployment"
msgstr ""
-#: ../../choosing_deployment_architecture.rst:142
-# 1fff976cf3344b6a8c06c3b56d9568ef
+#: ../../choosing_deployment_architecture.rst:120
+# 31bb0ebb88974050a79e6f0aec7c6778
msgid "The CloudStack platform scales well into multiple sites through the use of zones. The following diagram shows an example of a multi-site deployment."
msgstr ""
-#: ../../choosing_deployment_architecture.rst:146
-# ef026e2d1151436eb064cd8bf77db549
+#: ../../choosing_deployment_architecture.rst:124
+# 72c760ffa57b48a0a2ce31a545672acb
msgid "|Example Of A Multi-Site Deployment|"
msgstr ""
-#: ../../choosing_deployment_architecture.rst:148
-# 7ea2ca98a7094edab2212c4e776e349b
+#: ../../choosing_deployment_architecture.rst:126
+# 3680185677f54baeb03396c0c6e6b91b
msgid "Data Center 1 houses the primary Management Server as well as zone 1. The MySQL database is replicated in real time to the secondary Management Server installation in Data Center 2."
msgstr ""
-#: ../../choosing_deployment_architecture.rst:152
-# 39563946112d4b07afc28800922068ee
+#: ../../choosing_deployment_architecture.rst:130
+# 44f2f283a3dd4992ba843cd1a6ad29b9
msgid "|Separate Storage Network|"
msgstr ""
-#: ../../choosing_deployment_architecture.rst:154
-# e7cc868c4aa64cbe80807d7809ce58cb
+#: ../../choosing_deployment_architecture.rst:132
+# 85a51dc8edc24f37b0483d2b5d46a1dd
msgid "This diagram illustrates a setup with a separate storage network. Each server has four NICs, two connected to pod-level network switches and two connected to storage network switches."
msgstr ""
-#: ../../choosing_deployment_architecture.rst:158
-# 6157f0ee2cf84c49ac9f4f4ca1cdb0cd
+#: ../../choosing_deployment_architecture.rst:136
+# 56c244202346479080d0963357ce6a01
msgid "There are two ways to configure the storage network:"
msgstr ""
-#: ../../choosing_deployment_architecture.rst:162
-# cc2bdc7b44e146c18dfb9826c12b15f0
+#: ../../choosing_deployment_architecture.rst:138
+# 774def02c93d4401aa0961c701e2a346
msgid "Bonded NIC and redundant switches can be deployed for NFS. In NFS deployments, redundant switches and bonded NICs still result in one network (one CIDR block+ default gateway address)."
msgstr ""
-#: ../../choosing_deployment_architecture.rst:168
-# 0aa73c8538074a00b5b5305e33db5ed4
+#: ../../choosing_deployment_architecture.rst:142
+# 42c329aa74164a2a91b1cb061a594df0
msgid "iSCSI can take advantage of two separate storage networks (two CIDR blocks each with its own default gateway). Multipath iSCSI client can failover and load balance between separate storage networks."
msgstr ""
-#: ../../choosing_deployment_architecture.rst:172
-# 0e03920329f540e08c1ea89e9a7d05dd
+#: ../../choosing_deployment_architecture.rst:146
+# 709e7b87aca14df39855bc39efbde210
msgid "|NIC Bonding And Multipath I/O|"
msgstr ""
-#: ../../choosing_deployment_architecture.rst:174
-# 9219775ffce04cada583a2d12a90524f
+#: ../../choosing_deployment_architecture.rst:148
+# b9cd0b7d1c614f24855cf4e9755e9070
msgid "This diagram illustrates the differences between NIC bonding and Multipath I/O (MPIO). NIC bonding configuration involves only one network. MPIO involves two separate networks."
msgstr ""
-#: ../../choosing_deployment_architecture.rst:180
-# 0b1fe0948d434c1baf1a34edbb1847a0
+#: ../../choosing_deployment_architecture.rst:154
+# 36df70c98ae746549452fa36e1ca87e3
msgid "Choosing a Hypervisor"
msgstr ""
-#: ../../choosing_deployment_architecture.rst:182
-# f9313ca35f6f4589aed2bea3122829e7
+#: ../../choosing_deployment_architecture.rst:156
+# f236302a8db24c13a141a20573581062
msgid "CloudStack supports many popular hypervisors. Your cloud can consist entirely of hosts running a single hypervisor, or you can use multiple hypervisors. Each cluster of hosts must run the same hypervisor."
msgstr ""
-#: ../../choosing_deployment_architecture.rst:186
-# a54304966f514ffabe4dfad79eedc5eb
+#: ../../choosing_deployment_architecture.rst:160
+# ebd33f6eb3b64168ac6543a23dac1afd
msgid "You might already have an installed base of nodes running a particular hypervisor, in which case, your choice of hypervisor has already been made. If you are starting from scratch, you need to decide what hypervisor software best suits your needs. A discussion of the relative advantages of each hypervisor is outside the scope of our documentation. However, it will help you to know which features of each hypervisor are supported by CloudStack. The following table provides this information."
msgstr ""
-#: ../../choosing_deployment_architecture.rst:195
-# 3693e4b064964090ac1242961e0a8946
+#: ../../choosing_deployment_architecture.rst:169
+# 6095a38fe5eb4ce7acbb1c158db98231
msgid "Feature"
msgstr ""
-#: ../../choosing_deployment_architecture.rst:195
-# d3865d119f144b4d9207d2fd8e7578b9
+#: ../../choosing_deployment_architecture.rst:169
+# 4a7ee7865ca548379bf859592ddb19f8
msgid "XenServer 6.0.2"
msgstr ""
-#: ../../choosing_deployment_architecture.rst:195
-# b48b4cda653049f1a9422c908232ff17
+#: ../../choosing_deployment_architecture.rst:169
+# 09198080ae1c486ebd9470b6c99b387f
msgid "vSphere 4.1/5.0"
msgstr ""
-#: ../../choosing_deployment_architecture.rst:195
-# fed595ccd4cc4c4a9623807e16fefde5
+#: ../../choosing_deployment_architecture.rst:169
+# 1870d6331a364df4a087d4f6f3368ab9
msgid "KVM - RHEL 6.2"
msgstr ""
-#: ../../choosing_deployment_architecture.rst:195
-# d393ed42dc224b8684dbf6d8ab9d99c2
+#: ../../choosing_deployment_architecture.rst:169
+# d3c9ece508424f81897e3280902508b0
msgid "Bare Metal"
msgstr ""
-#: ../../choosing_deployment_architecture.rst:197
-# 1ba867f8783d4ac38bca542e7a1248be
+#: ../../choosing_deployment_architecture.rst:171
+# 970a9d80bc134222b3218d026302891b
msgid "Network Throttling"
msgstr ""
-#: ../../choosing_deployment_architecture.rst:197
-#: ../../choosing_deployment_architecture.rst:197
-#: ../../choosing_deployment_architecture.rst:198
-#: ../../choosing_deployment_architecture.rst:198
-#: ../../choosing_deployment_architecture.rst:199
-#: ../../choosing_deployment_architecture.rst:199
-#: ../../choosing_deployment_architecture.rst:199
-#: ../../choosing_deployment_architecture.rst:200
-#: ../../choosing_deployment_architecture.rst:200
-#: ../../choosing_deployment_architecture.rst:200
-#: ../../choosing_deployment_architecture.rst:201
-#: ../../choosing_deployment_architecture.rst:201
-#: ../../choosing_deployment_architecture.rst:201
-#: ../../choosing_deployment_architecture.rst:201
-#: ../../choosing_deployment_architecture.rst:202
-#: ../../choosing_deployment_architecture.rst:202
-#: ../../choosing_deployment_architecture.rst:203
-#: ../../choosing_deployment_architecture.rst:203
-#: ../../choosing_deployment_architecture.rst:203
-#: ../../choosing_deployment_architecture.rst:206
-#: ../../choosing_deployment_architecture.rst:206
-#: ../../choosing_deployment_architecture.rst:206
-#: ../../choosing_deployment_architecture.rst:207
-#: ../../choosing_deployment_architecture.rst:207
-# be052665fb9c4db6abf644607c11a2ce
-# a4b89b4ef4524eaa817ecdc80d28220e
-# 19def2d9dbcc4ab2b156efdb3105c12c
-# 9ea945d4e8004ddc87df1fc03980dce1
-# 4b880eb52259476c8b34809b91f7d3a3
-# 5b1d1cb21d6e45418d722dfddd325379
-# f403583dce4044a984df0474dbd133ad
-# e854f5913eee4b7c8abc33a936ef79f5
-# 639f24e5f94f42c98eb830f204f15720
-# 80f0710f7c8b47a481f04b3014a226c1
-# 699e94d60d9e4854a476539896363037
-# aa96059d21ac4ebcba125d36c1152217
-# 8e95523da0cb41bfb474406df9fb8145
-# 27cff33f4c064fbeb2f9f48ecef6f1cb
-# 086c38882e6b42ab8947506109c27cfd
-# e3902495150d4d56979b58303e1c731c
-# 2020f8688efe46629b40a7250d3111d0
-# 66c69ff810ef4413bfb1945563069a19
-# 513c35fbd6f04423bd9c3d783a99b4dc
-# 84cff98be301475280c880d4da63670b
-# d91c60035cce41bf94a8091fb6c37bb3
-# 47bdf8e2d92f4d3a8a2817cc47bed1ed
-# c160f1f7b53544bc91fdbfae297359cb
-# 11fbe78348e24da89d9e7307aee4769c
+#: ../../choosing_deployment_architecture.rst:171
+#: ../../choosing_deployment_architecture.rst:171
+#: ../../choosing_deployment_architecture.rst:172
+#: ../../choosing_deployment_architecture.rst:172
+#: ../../choosing_deployment_architecture.rst:173
+#: ../../choosing_deployment_architecture.rst:173
+#: ../../choosing_deployment_architecture.rst:173
+#: ../../choosing_deployment_architecture.rst:174
+#: ../../choosing_deployment_architecture.rst:174
+#: ../../choosing_deployment_architecture.rst:174
+#: ../../choosing_deployment_architecture.rst:175
+#: ../../choosing_deployment_architecture.rst:175
+#: ../../choosing_deployment_architecture.rst:175
+#: ../../choosing_deployment_architecture.rst:175
+#: ../../choosing_deployment_architecture.rst:176
+#: ../../choosing_deployment_architecture.rst:176
+#: ../../choosing_deployment_architecture.rst:177
+#: ../../choosing_deployment_architecture.rst:177
+#: ../../choosing_deployment_architecture.rst:177
+#: ../../choosing_deployment_architecture.rst:180
+#: ../../choosing_deployment_architecture.rst:180
+#: ../../choosing_deployment_architecture.rst:180
+#: ../../choosing_deployment_architecture.rst:181
+#: ../../choosing_deployment_architecture.rst:181
+# 4fec162cda76433cb982cfc313dcdbe6
+# 1f8cc79d716140189e60a08ebf4687bf
+# 91a8ee2ecce64c71b1eecf843f67deed
+# 2989a051bcd34ea987938c8a7e30b013
+# 9cbaf270ddd6408c8101622f74c7b266
+# 12e9d689493a44049c4874afa2dbadd3
+# f9a1370f394c49a8967531ffb6e1b423
+# 91b5581980864170b9693104a2f61d3c
+# c231f1df091e4ceeb60e89845db5f10b
+# 2852be6028ec46659ae8bf5cac551b29
+# 755b64ababd34e04b82a384d357fc6e4
+# 3e558e80e7bc4878b80739772dfb4a06
+# 227928dd0cf1488b873ce21a5b4842d2
+# 6ca963616f6a42098fed6641c7711e35
+# f36be7f0603b44f5aa77a248d3a97e5e
+# 996c7caeb3384d93be1ce49f570cb8ce
+# 5d9e3cabc113463e8b6c3fb75b182456
+# 159c98b022e14645bef4499b7c0c0235
+# f55810d73d0246b38a1495e4af5ec4bc
+# 0867769fdd5046d0832752148daf908d
+# c25243683e1449f0b89ee3d3b1881025
+# 87e8128b3ae84f228c87a33a892a23ec
+# 9fc4d908264143e682ddec06aaafe205
+# 0bb1aaf47c0543659d4e09d9f91cd185
msgid "Yes"
msgstr ""
-#: ../../choosing_deployment_architecture.rst:197
-#: ../../choosing_deployment_architecture.rst:198
-#: ../../choosing_deployment_architecture.rst:198
-#: ../../choosing_deployment_architecture.rst:204
-#: ../../choosing_deployment_architecture.rst:204
-#: ../../choosing_deployment_architecture.rst:204
-#: ../../choosing_deployment_architecture.rst:205
-#: ../../choosing_deployment_architecture.rst:205
-#: ../../choosing_deployment_architecture.rst:207
-# cd83b27113e841ac916e00bcd1082008
-# 1947bdafae1f4b5a9061c6eb1cb2b99c
-# d3de86e130104668a664aa03d61c32a6
-# c0adf6e94804483a9dbfd425bab70401
-# fa80ad1123b1402aaac21bfc7d19b636
-# 5dd1209f3e2a41d7aa8489e8ace6aadf
-# 280839b6b2744ce58570ac30f941863b
-# b2a56672e17b4744bf8c11d6f41f42db
-# 2838338f3d264292ac265635c4cec016
+#: ../../choosing_deployment_architecture.rst:171
+#: ../../choosing_deployment_architecture.rst:172
+#: ../../choosing_deployment_architecture.rst:172
+#: ../../choosing_deployment_architecture.rst:178
+#: ../../choosing_deployment_architecture.rst:178
+#: ../../choosing_deployment_architecture.rst:178
+#: ../../choosing_deployment_architecture.rst:179
+#: ../../choosing_deployment_architecture.rst:179
+#: ../../choosing_deployment_architecture.rst:181
+# 3cb5cc62ebb54cae80640aabea621255
+# 86b2047f134d4b8a8af64d25bea97315
+# 5ca5465c16114b58ab0aaaf014969e31
+# fc76b86618fb433780039d59ce9cf302
+# 0cd9cc48eb624d829d99923f98ab2d5f
+# 748e481678464f27b851cb867b2d78b2
+# 1215b1b0f7e44472adcf474168869721
+# db4ae4f299a14dd097a941a94920c9c0
+# c8744cfc965e4794935294c98d6aae14
msgid "No"
msgstr ""
-#: ../../choosing_deployment_architecture.rst:197
-#: ../../choosing_deployment_architecture.rst:199
-#: ../../choosing_deployment_architecture.rst:200
-#: ../../choosing_deployment_architecture.rst:202
-#: ../../choosing_deployment_architecture.rst:203
-#: ../../choosing_deployment_architecture.rst:204
-#: ../../choosing_deployment_architecture.rst:205
-#: ../../choosing_deployment_architecture.rst:206
-#: ../../choosing_deployment_architecture.rst:207
-# b2723a3c2a3d40bb8905525b93d521db
-# df278255008f48bba701f08e2746a45b
-# 41891d2dfaec4726afd7af756ccf6ae3
-# 7de26acf53854ee19c25494093e873d8
-# e5b105be128f4a0f9b5a4b0ea089b340
-# c86cc373ee974129bcbc17d0c34fd3a9
-# 29d8fb39d33d44089307d76a24192b93
-# f2adc402745f4312b27cc7579ba3549a
-# 899efc660f874882befc3436419f4150
+#: ../../choosing_deployment_architecture.rst:171
+#: ../../choosing_deployment_architecture.rst:173
+#: ../../choosing_deployment_architecture.rst:174
+#: ../../choosing_deployment_architecture.rst:176
+#: ../../choosing_deployment_architecture.rst:177
+#: ../../choosing_deployment_architecture.rst:178
+#: ../../choosing_deployment_architecture.rst:179
+#: ../../choosing_deployment_architecture.rst:180
+#: ../../choosing_deployment_architecture.rst:181
+# 63afe958cfa44895bc62e896586ee40f
+# 199baf6fe3444dd48443901731e0ad62
+# ece293ab433448bd95772d3de229bcf6
+# fc04754e8df54fd7b280d1e2d9973a9f
+# 258bacf04ab349cc80b6f7d9ec2c0d7b
+# 9d861363c0d54ccb831b9a52f67834f6
+# be8b43bee82341ce8c679239ccd5e71e
+# 89c3130f25d348d1abc3081a0a033720
+# cfcd30df2f204091be6335cf2b116e44
msgid "N/A"
msgstr ""
-#: ../../choosing_deployment_architecture.rst:198
-# 46133f6d28554c339a302a0bc5a80174
+#: ../../choosing_deployment_architecture.rst:172
+# 6f727e19a82c4be4b3d885ee30c3bd5e
msgid "Security groups in zones that use basic networking"
msgstr ""
-#: ../../choosing_deployment_architecture.rst:199
-# 067683e3c1a940c483f5c2a1156135ec
+#: ../../choosing_deployment_architecture.rst:173
+# 97e1ffe107c74bd4846cf646d1b9543e
msgid "iSCSI"
msgstr ""
-#: ../../choosing_deployment_architecture.rst:200
-# cca8044dd01e463d90beaec88dd13bfd
+#: ../../choosing_deployment_architecture.rst:174
+# 2ea33b37f3de4e91b56a3f97d94654b7
msgid "FibreChannel"
msgstr ""
-#: ../../choosing_deployment_architecture.rst:201
-# 9b3992c401fb484aa373c97609af73d5
+#: ../../choosing_deployment_architecture.rst:175
+# b1c9732e6c15420a87ad6e0dd96052ef
msgid "Local Disk"
msgstr ""
-#: ../../choosing_deployment_architecture.rst:202
-# d7598b6aa7a24f3f890494e960b14b72
+#: ../../choosing_deployment_architecture.rst:176
+# 490c55011c344c2cad34b7ed6f88fade
msgid "HA"
msgstr ""
-#: ../../choosing_deployment_architecture.rst:202
-# 2f14e2bad82d4187b34b6ecf7b185397
+#: ../../choosing_deployment_architecture.rst:176
+# 1aa446ba2cf44112bb3b742a8435bc70
msgid "Yes (Native)"
msgstr ""
-#: ../../choosing_deployment_architecture.rst:203
-# 991329dd067d4fc0b84a473c2b9738d6
+#: ../../choosing_deployment_architecture.rst:177
+# d46bd32966d54085a61343d211a063d1
msgid "Snapshots of local disk"
msgstr ""
-#: ../../choosing_deployment_architecture.rst:204
-# 82d0be0fc5014fb199a1e335495bb0e4
+#: ../../choosing_deployment_architecture.rst:178
+# 954f1dc69e8945f9a3e8d1363d10feb9
msgid "Local disk as data disk"
msgstr ""
-#: ../../choosing_deployment_architecture.rst:205
-# 9606914b8d0d42e4bf6a230c8b66b0a4
+#: ../../choosing_deployment_architecture.rst:179
+# e31cc2bd3ce340ae9976c8166beb44cb
msgid "Work load balancing"
msgstr ""
-#: ../../choosing_deployment_architecture.rst:205
-# e51f36058e824167a36e9ae71df467fc
+#: ../../choosing_deployment_architecture.rst:179
+# 9b6952490df5422e8c9dc96b96e06914
msgid "DRS"
msgstr ""
-#: ../../choosing_deployment_architecture.rst:206
-# 71c333daaabe476ab414b0a03b7ae88e
+#: ../../choosing_deployment_architecture.rst:180
+# 276af5d2a4d94ebdb3319fbbe859a74e
msgid "Manual live migration of VMs from host to host"
msgstr ""
-#: ../../choosing_deployment_architecture.rst:207
-# c47b20ce94d448a4aa6add55bd117597
+#: ../../choosing_deployment_architecture.rst:181
+# a6ffb0bdac29407e86b5edc37f932c8c
msgid "Conserve management traffic IP address by using link local network to communicate with virtual router"
msgstr ""
-#: ../../choosing_deployment_architecture.rst:212
-# cb5323a6d0ef49c283024dd46d0b4ef0
+#: ../../choosing_deployment_architecture.rst:186
+# eb354934ad0c4f1e92a9aa56494e083e
msgid "Best Practices"
msgstr ""
-#: ../../choosing_deployment_architecture.rst:214
-# adc9a356d253458ca9d971565f3bf1b3
+#: ../../choosing_deployment_architecture.rst:188
+# 42fc8f2d41c548c0b39e0f03816bd496
msgid "Deploying a cloud is challenging. There are many different technology choices to make, and CloudStack is flexible enough in its configuration that there are many possible ways to combine and configure the chosen technology. This section contains suggestions and requirements about cloud deployments."
msgstr ""
-#: ../../choosing_deployment_architecture.rst:220
-# c077c29e871a451085be2f9d93d6ce0b
+#: ../../choosing_deployment_architecture.rst:194
+# 68e273347ac34898aaaddc10df7c5d4d
msgid "These should be treated as suggestions and not absolutes. However, we do encourage anyone planning to build a cloud outside of these guidelines to seek guidance and advice on the project mailing lists."
msgstr ""
-#: ../../choosing_deployment_architecture.rst:225
-# c312a003df984d1e99a7daef9dff794b
+#: ../../choosing_deployment_architecture.rst:200
+# ba21db935b174028b86bb1e6442669d7
msgid "Process Best Practices"
msgstr ""
-#: ../../choosing_deployment_architecture.rst:229
-# abc014ba86804cf1b60a7e800d7692d1
+#: ../../choosing_deployment_architecture.rst:202
+# cefb1b21faf04019abc16cccabd19d30
msgid "A staging system that models the production environment is strongly advised. It is critical if customizations have been applied to CloudStack."
msgstr ""
-#: ../../choosing_deployment_architecture.rst:235
-# 4422c6e1832a4ede9621424bc85274ad
+#: ../../choosing_deployment_architecture.rst:206
+# ea64ea072f3746d2b3463aafdc14532b
msgid "Allow adequate time for installation, a beta, and learning the system. Installs with basic networking can be done in hours. Installs with advanced networking usually take several days for the first attempt, with complicated installations taking longer. For a full production system, allow at least 4-8 weeks for a beta to work through all of the integration issues. You can get help from fellow users on the cloudstack-users mailing list."
msgstr ""
-#: ../../choosing_deployment_architecture.rst:244
-# e404a3ea1a28429ca6f54d86384ce11e
+#: ../../choosing_deployment_architecture.rst:216
+# 67f17d3accb24ff48c29830624f9a607
msgid "Setup Best Practices"
msgstr ""
-#: ../../choosing_deployment_architecture.rst:248
-# 2c6d3efd9c624e11861404be6de4db3e
+#: ../../choosing_deployment_architecture.rst:218
+# 81402254fd3a4dd888d02f4a884a1d0b
msgid "Each host should be configured to accept connections only from well-known entities such as the CloudStack Management Server or your network monitoring software."
msgstr ""
-#: ../../choosing_deployment_architecture.rst:254
-# ef5b0d453e974244b9f46701aae6a09a
+#: ../../choosing_deployment_architecture.rst:222
+# 7481cf7faac5484b8339bb8e4d75b6c8
msgid "Use multiple clusters per pod if you need to achieve a certain switch density."
msgstr ""
-#: ../../choosing_deployment_architecture.rst:259
-# bb554a90a44a4d678ac338f55d01f8ee
+#: ../../choosing_deployment_architecture.rst:225
+# fd7badb077d04065b340d43fd79a4eec
msgid "Primary storage mountpoints or LUNs should not exceed 6 TB in size. It is better to have multiple smaller primary storage elements per cluster than one large one."
msgstr ""
-#: ../../choosing_deployment_architecture.rst:265
-# 3a69638a02c74393987657eaef675207
+#: ../../choosing_deployment_architecture.rst:229
+# 6ed9bc75682247bfbc913cf9df8e21f1
msgid "When exporting shares on primary storage, avoid data loss by restricting the range of IP addresses that can access the storage. See \"Linux NFS on Local Disks and DAS\" or \"Linux NFS on iSCSI\"."
msgstr ""
-#: ../../choosing_deployment_architecture.rst:271
-# ccf0998ec590457198f2ba04de50f1fa
+#: ../../choosing_deployment_architecture.rst:233
+# 5e4ab60bb7e7405180895617b9a6efe1
msgid "NIC bonding is straightforward to implement and provides increased reliability."
msgstr ""
-#: ../../choosing_deployment_architecture.rst:276
-# d5767cccb17c4f4e857a0446daa2e67b
+#: ../../choosing_deployment_architecture.rst:236
+# ff514643a50b4a478172c6dbe1a9befe
msgid "10G networks are generally recommended for storage access when larger servers that can support relatively more VMs are used."
msgstr ""
-#: ../../choosing_deployment_architecture.rst:281
-# 34ffd751b3bb476ba1f3f2e608b93d3d
+#: ../../choosing_deployment_architecture.rst:239
+# 570bde20d1b84f1ea78c02bab25c0f7d
msgid "Host capacity should generally be modeled in terms of RAM for the guests. Storage and CPU may be overprovisioned. RAM may not. RAM is usually the limiting factor in capacity designs."
msgstr ""
-#: ../../choosing_deployment_architecture.rst:287
-# 6d2c0b24d26849a19a4b45b81b27574d
+#: ../../choosing_deployment_architecture.rst:243
+# 1910d3f68a634d0fb53fdd5f4bde6b8e
msgid "(XenServer) Configure the XenServer dom0 settings to allocate more memory to dom0. This can enable XenServer to handle larger numbers of virtual machines. We recommend 2940 MB of RAM for XenServer dom0. For instructions on how to do this, see `http://support.citrix.com/article/CTX126531 <http://support.citrix.com/article/CTX126531>`_. The article refers to XenServer 5.6, but the same information applies to XenServer 6.0."
msgstr ""
-#: ../../choosing_deployment_architecture.rst:296
-# d527abb1d09c439194238f9a516c50c5
+#: ../../choosing_deployment_architecture.rst:254
+# c33ddae286b44338ab9b330c918e8e39
msgid "Maintenance Best Practices"
msgstr ""
-#: ../../choosing_deployment_architecture.rst:300
-# e86da3bff33947e2907910514580b7bf
+#: ../../choosing_deployment_architecture.rst:256
+# ae92610bc5164452b9e9527e5f3a8eec
msgid "Monitor host disk space. Many host failures occur because the host's root disk fills up from logs that were not rotated adequately."
msgstr ""
-#: ../../choosing_deployment_architecture.rst:305
-# c53de7cac3554464bfb3b37704d3aa62
+#: ../../choosing_deployment_architecture.rst:259
+# 731977493e6d46559ca32f493189b8f4
msgid "Monitor the total number of VM instances in each cluster, and disable allocation to the cluster if the total is approaching the maximum that the hypervisor can handle. Be sure to leave a safety margin to allow for the possibility of one or more hosts failing, which would increase the VM load on the other hosts as the VMs are redeployed. Consult the documentation for your chosen hypervisor to find the maximum permitted number of VMs per host, then use CloudStack global configuration settings to set this as the default limit. Monitor the VM activity in each cluster and keep the total number of VMs below a safe level that allows for the occasional host failure. For example, if there are N hosts in the cluster, and you want to allow for one host in the cluster to be down at any given time, the total number of VM instances you can permit in the cluster is at most (N-1) \\* (per-host-limit). Once a cluster reaches this number of VMs, use the CloudStack UI to disable allocation to t
he cluster."
msgstr ""
-#: ../../choosing_deployment_architecture.rst:323
-# 89ae9c94778c48a2a29f1b11ff95a571
+#: ../../choosing_deployment_architecture.rst:276
+# edcacc73b0b64b318b84f0f38e00e8d9
msgid "The lack of up-do-date hotfixes can lead to data corruption and lost VMs."
msgstr ""
-#: ../../choosing_deployment_architecture.rst:325
-# 28c8fb8da4a24ab4b15726bb4efb7ead
+#: ../../choosing_deployment_architecture.rst:278
+# 07e8bf01dab44bb2b1ab4f52a8be4264
msgid "Be sure all the hotfixes provided by the hypervisor vendor are applied. Track the release of hypervisor patches through your hypervisor vendor’s support channel, and apply patches as soon as possible after they are released. CloudStack will not track or notify you of required hypervisor patches. It is essential that your hosts are completely up to date with the provided hypervisor patches. The hypervisor vendor is likely to refuse to support any system that is not up to date with patches."
msgstr ""