setup i18n with transifex and sphinx-intl
Project: http://git-wip-us.apache.org/repos/asf/cloudstack-docs-install/repo Commit: http://git-wip-us.apache.org/repos/asf/cloudstack-docs-install/commit/bd81bcc4 Tree: http://git-wip-us.apache.org/repos/asf/cloudstack-docs-install/tree/bd81bcc4 Diff: http://git-wip-us.apache.org/repos/asf/cloudstack-docs-install/diff/bd81bcc4 Branch: refs/heads/master Commit: bd81bcc4a775970e7074f9578013174ef7497ef8 Parents: b1f7a0f Author: Sebastien Goasguen <[email protected]> Authored: Mon Mar 31 14:06:48 2014 -0400 Committer: Sebastien Goasguen <[email protected]> Committed: Mon Mar 31 14:06:48 2014 -0400 ---------------------------------------------------------------------- .gitignore | 1 + .tx/config | 59 + Makefile | 4 +- README.rst | 34 + source/locale/pot/building_from_source.pot | 433 ++ .../pot/choosing_deployment_architecture.pot | 511 ++ source/locale/pot/configuration.pot | 2565 +++++++ source/locale/pot/hypervisor_installation.pot | 4221 +++++++++++ source/locale/pot/index.pot | 88 + source/locale/pot/installation.pot | 1224 ++++ source/locale/pot/managing_networks.pot | 6769 ++++++++++++++++++ source/locale/pot/network_setup.pot | 1713 +++++ source/locale/pot/optional_installation.pot | 1252 ++++ source/locale/pot/qig.pot | 682 ++ source/locale/pot/storage_setup.pot | 290 + 15 files changed, 19844 insertions(+), 2 deletions(-) ---------------------------------------------------------------------- http://git-wip-us.apache.org/repos/asf/cloudstack-docs-install/blob/bd81bcc4/.gitignore ---------------------------------------------------------------------- diff --git a/.gitignore b/.gitignore index 9029067..7eea884 100644 --- a/.gitignore +++ b/.gitignore @@ -15,6 +15,7 @@ # under the License. /build +/source/locale/pot/.doctrees # OS generated files # ###################### http://git-wip-us.apache.org/repos/asf/cloudstack-docs-install/blob/bd81bcc4/.tx/config ---------------------------------------------------------------------- diff --git a/.tx/config b/.tx/config new file mode 100644 index 0000000..1ec5c80 --- /dev/null +++ b/.tx/config @@ -0,0 +1,59 @@ +[main] +host = https://www.transifex.com +type = PO + +[apache-cloudstack-installation-rtd.building_from_source] +file_filter = source/locale/<lang>/LC_MESSAGES/building_from_source.po +source_file = source/locale/pot/building_from_source.pot +source_lang = en + +[apache-cloudstack-installation-rtd.choosing_deployment_architecture] +file_filter = source/locale/<lang>/LC_MESSAGES/choosing_deployment_architecture.po +source_file = source/locale/pot/choosing_deployment_architecture.pot +source_lang = en + +[apache-cloudstack-installation-rtd.configuration] +file_filter = source/locale/<lang>/LC_MESSAGES/configuration.po +source_file = source/locale/pot/configuration.pot +source_lang = en + +[apache-cloudstack-installation-rtd.hypervisor_installation] +file_filter = source/locale/<lang>/LC_MESSAGES/hypervisor_installation.po +source_file = source/locale/pot/hypervisor_installation.pot +source_lang = en + +[apache-cloudstack-installation-rtd.index] +file_filter = source/locale/<lang>/LC_MESSAGES/index.po +source_file = source/locale/pot/index.pot +source_lang = en + +[apache-cloudstack-installation-rtd.installation] +file_filter = source/locale/<lang>/LC_MESSAGES/installation.po +source_file = source/locale/pot/installation.pot +source_lang = en + +[apache-cloudstack-installation-rtd.managing_networks] +file_filter = source/locale/<lang>/LC_MESSAGES/managing_networks.po +source_file = source/locale/pot/managing_networks.pot +source_lang = en + +[apache-cloudstack-installation-rtd.network_setup] +file_filter = source/locale/<lang>/LC_MESSAGES/network_setup.po +source_file = source/locale/pot/network_setup.pot +source_lang = en + +[apache-cloudstack-installation-rtd.optional_installation] +file_filter = source/locale/<lang>/LC_MESSAGES/optional_installation.po +source_file = source/locale/pot/optional_installation.pot +source_lang = en + +[apache-cloudstack-installation-rtd.qig] +file_filter = source/locale/<lang>/LC_MESSAGES/qig.po +source_file = source/locale/pot/qig.pot +source_lang = en + +[apache-cloudstack-installation-rtd.storage_setup] +file_filter = source/locale/<lang>/LC_MESSAGES/storage_setup.po +source_file = source/locale/pot/storage_setup.pot +source_lang = en + http://git-wip-us.apache.org/repos/asf/cloudstack-docs-install/blob/bd81bcc4/Makefile ---------------------------------------------------------------------- diff --git a/Makefile b/Makefile index 5187a30..ad6bfb1 100644 --- a/Makefile +++ b/Makefile @@ -162,9 +162,9 @@ info: @echo "makeinfo finished; the Info files are in $(BUILDDIR)/texinfo." gettext: - $(SPHINXBUILD) -b gettext $(I18NSPHINXOPTS) $(BUILDDIR)/locale + $(SPHINXBUILD) -b gettext $(I18NSPHINXOPTS) source/locale/pot @echo - @echo "Build finished. The message catalogs are in $(BUILDDIR)/locale." + @echo "Build finished. The message catalogs are in source/locale/pot" changes: $(SPHINXBUILD) -b changes $(ALLSPHINXOPTS) $(BUILDDIR)/changes http://git-wip-us.apache.org/repos/asf/cloudstack-docs-install/blob/bd81bcc4/README.rst ---------------------------------------------------------------------- diff --git a/README.rst b/README.rst index bb8d609..9d25ba7 100644 --- a/README.rst +++ b/README.rst @@ -24,6 +24,40 @@ Website This installation guide is on-line at <http://cloudstack-installation.readthedocs.org/en/latest/> +Translation +=========== + +Clean the build + +:: + make clean + +Generate the .pot files + +:: + make gettext + +Generate the .tx/config files with: + +:: + sphinx-intl update-txconfig-resources --pot-dir source/locale/pot --transifex-project-name apache-cloudstack-installation-rtd --locale-dir source/locale + +Push the .pot files to transifex with: + +:: + tx push -s + +Download the translated strings, for example Japanese (ja): + +:: + tx pull -l ja + +Build the translated docs: + +:: + sphinx-intl build --locale-dir source/locale + make -e SPHINXOPTS="-D language='ja'" html + Feedback ======== http://git-wip-us.apache.org/repos/asf/cloudstack-docs-install/blob/bd81bcc4/source/locale/pot/building_from_source.pot ---------------------------------------------------------------------- diff --git a/source/locale/pot/building_from_source.pot b/source/locale/pot/building_from_source.pot new file mode 100644 index 0000000..c7a1d7c --- /dev/null +++ b/source/locale/pot/building_from_source.pot @@ -0,0 +1,433 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2014, Apache Software Foundation +# This file is distributed under the same license as the Apache CloudStack Installation Documentation package. +# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: Apache CloudStack Installation Documentation 4\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2014-03-31 14:02-0400\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n" +"Language-Team: LANGUAGE <[email protected]>\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" + +#: ../../building_from_source.rst:17 +# 5396f27a8ff74a7d8817526ff37ec438 +msgid "Building from Source" +msgstr "" + +#: ../../building_from_source.rst:19 +# 60bf699c76df434992e36d41c5f00bcf +msgid "The official CloudStack release is always in source code form. You will likely be able to find \"convenience binaries,\" the source is the canonical release. In this section, we'll cover acquiring the source release and building that so that you can deploy it using Maven or create Debian packages or RPMs." +msgstr "" + +#: ../../building_from_source.rst:25 +# 32892fc6365642cd81e9910e84bb80c0 +msgid "Note that building and deploying directly from source is typically not the most efficient way to deploy an IaaS. However, we will cover that method as well as building RPMs or Debian packages for deploying CloudStack." +msgstr "" + +#: ../../building_from_source.rst:30 +# 7e67792d5ec241af80724aa269cc8f40 +msgid "The instructions here are likely version-specific. That is, the method for building from source for the 4.0.x series is different from the 4.1.x series." +msgstr "" + +#: ../../building_from_source.rst:34 +# 59bd739639154797bb627d316198b3d2 +msgid "If you are working with a unreleased version of CloudStack, see the INSTALL.md file in the top-level directory of the release." +msgstr "" + +#: ../../building_from_source.rst:38 +# 54b5d37f192048519bd2ed85a3ddc5b3 +msgid "Getting the release" +msgstr "" + +#: ../../building_from_source.rst:40 +# d3311764aeed4cc0b185062d99f5c4e9 +msgid "You can download the latest CloudStack release from the `Apache CloudStack project download page <http://cloudstack.apache.org/downloads.html>`_." +msgstr "" + +#: ../../building_from_source.rst:43 +# c0f0cbed8f7942dd8cdf0ec15232e760 +msgid "Prior releases are available via archive.apache.org as well. See the downloads page for more information on archived releases." +msgstr "" + +#: ../../building_from_source.rst:46 +# efebd9e2df61457482c9cb8efbadd736 +msgid "You'll notice several links under the 'Latest release' section. A link to a file ending in ``tar.bz2``, as well as a PGP/GPG signature, MD5, and SHA512 file." +msgstr "" + +#: ../../building_from_source.rst:52 +# c8757326ca1c47f989906e77b64c17db +msgid "The ``tar.bz2`` file contains the Bzip2-compressed tarball with the source code." +msgstr "" + +#: ../../building_from_source.rst:57 +# d1f48a19cc14413e90a8164ef6e496ed +msgid "The ``.asc`` file is a detached cryptographic signature that can be used to help verify the authenticity of the release." +msgstr "" + +#: ../../building_from_source.rst:62 +# b45289cb4cba4686b60ab976bf75eea1 +msgid "The ``.md5`` file is an MD5 hash of the release to aid in verify the validity of the release download." +msgstr "" + +#: ../../building_from_source.rst:67 +# 637044e3649f406b8e5b6a441ba355c7 +msgid "The ``.sha`` file is a SHA512 hash of the release to aid in verify the validity of the release download." +msgstr "" + +#: ../../building_from_source.rst:71 +# 4da67860f4454b7aa0c0fc6f76b59317 +msgid "Verifying the downloaded release" +msgstr "" + +#: ../../building_from_source.rst:73 +# 184cd04b405b4136b74c0644e4720e2a +msgid "There are a number of mechanisms to check the authenticity and validity of a downloaded release." +msgstr "" + +#: ../../building_from_source.rst:77 +# 787318aa8f2049098a34030e7bb9220d +msgid "Getting the KEYS" +msgstr "" + +#: ../../building_from_source.rst:79 +# af2e7aafde3c45d79c93d848f16df84f +msgid "To enable you to verify the GPG signature, you will need to download the `KEYS <http://www.apache.org/dist/cloudstack/KEYS>`_ file." +msgstr "" + +#: ../../building_from_source.rst:82 +# b7351a3de11b4d5783f051a524e6d6d9 +msgid "You next need to import those keys, which you can do by running:" +msgstr "" + +#: ../../building_from_source.rst:89 +# 6a67d67c239c4450b6b0454f78e1e976 +msgid "GPG" +msgstr "" + +#: ../../building_from_source.rst:91 +# c41516ba45df4b8c8c82f0437fd1cf0f +msgid "The CloudStack project provides a detached GPG signature of the release. To check the signature, run the following command:" +msgstr "" + +#: ../../building_from_source.rst:98 +# 06a586af894b41a191ca74d565fd5646 +msgid "If the signature is valid you will see a line of output that contains 'Good signature'." +msgstr "" + +#: ../../building_from_source.rst:102 +# 7c1c3790e01440f88dc8e8f108c69180 +msgid "MD5" +msgstr "" + +#: ../../building_from_source.rst:104 +# e47ab7059cdf4276968ef9219d824967 +msgid "In addition to the cryptographic signature, CloudStack has an MD5 checksum that you can use to verify the download matches the release. You can verify this hash by executing the following command:" +msgstr "" + +#: ../../building_from_source.rst:112 +# 471b0fafe73b4bebb48f271b2be0323b +msgid "If this successfully completes you should see no output. If there is any output from them, then there is a difference between the hash you generated locally and the hash that has been pulled from the server." +msgstr "" + +#: ../../building_from_source.rst:117 +# a42234cf484d448ea3a079cc44d505c4 +msgid "SHA512" +msgstr "" + +#: ../../building_from_source.rst:119 +# f6904f51119c4bd7a0e6d9d42868d7cd +msgid "In addition to the MD5 hash, the CloudStack project provides a SHA512 cryptographic hash to aid in assurance of the validity of the downloaded release. You can verify this hash by executing the following command:" +msgstr "" + +#: ../../building_from_source.rst:127 +# 2b02e428976242d5a9513dc999f80d9a +msgid "If this command successfully completes you should see no output. If there is any output from them, then there is a difference between the hash you generated locally and the hash that has been pulled from the server." +msgstr "" + +#: ../../building_from_source.rst:133 +# 20ae79e8693540af926f68f5b8a08da3 +msgid "Prerequisites for building Apache CloudStack" +msgstr "" + +#: ../../building_from_source.rst:135 +# 8de67a9fdaea48faa67ab89f641adc4b +msgid "There are a number of prerequisites needed to build CloudStack. This document assumes compilation on a Linux system that uses RPMs or DEBs for package management." +msgstr "" + +#: ../../building_from_source.rst:139 +# 9c13e54d32b5455aaab36099aa2535a4 +msgid "You will need, at a minimum, the following to compile CloudStack:" +msgstr "" + +#: ../../building_from_source.rst:143 +# 0146a3cb86884d318cf934c639b76449 +msgid "Maven (version 3)" +msgstr "" + +#: ../../building_from_source.rst:147 +# 005189dfa25b4c66b039e0267fdbea5e +msgid "Java (OpenJDK 1.6 or Java 7/OpenJDK 1.7)" +msgstr "" + +#: ../../building_from_source.rst:151 +# 2c58fc00271e445e861705983b16a5f3 +msgid "Apache Web Services Common Utilities (ws-commons-util)" +msgstr "" + +#: ../../building_from_source.rst:155 +# 989f684d1b8a456bac9a81d3f924d16f +msgid "MySQL" +msgstr "" + +#: ../../building_from_source.rst:159 +# 44ef1202eb3e4c61b84f22fbc433a538 +msgid "MySQLdb (provides Python database API)" +msgstr "" + +#: ../../building_from_source.rst:163 +# e84e7644c89a4669991bc0a1013171c1 +msgid "Tomcat 6 (not 6.0.35)" +msgstr "" + +#: ../../building_from_source.rst:167 +# fe2b1db48eb9421d937189144b944911 +msgid "genisoimage" +msgstr "" + +#: ../../building_from_source.rst:171 +# bc55f42faeef4adbb28f3b39cfe334ef +msgid "rpmbuild or dpkg-dev" +msgstr "" + +#: ../../building_from_source.rst:174 +# 7b45a167b6874f9a8ba73a17d7f1a6c5 +msgid "Extracting source" +msgstr "" + +#: ../../building_from_source.rst:176 +# 3b2090380fcf4c12ad2638d91cb45d43 +msgid "Extracting the CloudStack release is relatively simple and can be done with a single command as follows:" +msgstr "" + +#: ../../building_from_source.rst:183 +# 0f5f07d38bd54fb2a0e69c6fb28e1967 +msgid "You can now move into the directory:" +msgstr "" + +#: ../../building_from_source.rst:190 +# aa9e9e76ff6441498d8531802e1afa7e +msgid "Building DEB packages" +msgstr "" + +#: ../../building_from_source.rst:192 +# 0eca44ba0f1c4b3ba1e65ab3a0268db9 +msgid "In addition to the bootstrap dependencies, you'll also need to install several other dependencies. Note that we recommend using Maven 3, which is not currently available in 12.04.1 LTS. So, you'll also need to add a PPA repository that includes Maven 3. After running the command ``add-apt-repository``, you will be prompted to continue and a GPG key will be added." +msgstr "" + +#: ../../building_from_source.rst:207 +# 8014eb3c824248f28bfaff9deeabaced +msgid "While we have defined, and you have presumably already installed the bootstrap prerequisites, there are a number of build time prerequisites that need to be resolved. CloudStack uses maven for dependency resolution. You can resolve the buildtime depdencies for CloudStack by running:" +msgstr "" + +#: ../../building_from_source.rst:217 +# f6f09e0f7e3c49129fe0c281cc144489 +msgid "Now that we have resolved the dependencies we can move on to building CloudStack and packaging them into DEBs by issuing the following command." +msgstr "" + +#: ../../building_from_source.rst:225 +# f345823b71dc4836a97a160bfbb40a9e +msgid "This command will build the following debian packages. You should have all of the following:" +msgstr "" + +#: ../../building_from_source.rst:239 +# 88e77857a4fa4e9b80e912d82a405591 +msgid "Setting up an APT repo" +msgstr "" + +#: ../../building_from_source.rst:241 +# 7db71198e1aa4db08ce8f174f11546aa +msgid "After you've created the packages, you'll want to copy them to a system where you can serve the packages over HTTP. You'll create a directory for the packages and then use ``dpkg-scanpackages`` to create ``Packages.gz``, which holds information about the archive structure. Finally, you'll add the repository to your system(s) so you can install the packages using APT." +msgstr "" + +#: ../../building_from_source.rst:248 +# 882df6f5a6a542e08af5d64a8c440f9b +msgid "The first step is to make sure that you have the **dpkg-dev** package installed. This should have been installed when you pulled in the **debhelper** application previously, but if you're generating ``Packages.gz`` on a different system, be sure that it's installed there as well." +msgstr "" + +#: ../../building_from_source.rst:258 +# 6b45808c7afe48eab8f0e54e28996c78 +msgid "The next step is to copy the DEBs to the directory where they can be served over HTTP. We'll use ``/var/www/cloudstack/repo`` in the examples, but change the directory to whatever works for you." +msgstr "" + +#: ../../building_from_source.rst:271 +# 9f7bfa37a80641409e1400b8548efb29 +msgid "You can safely ignore the warning about a missing override file." +msgstr "" + +#: ../../building_from_source.rst:273 +# d8e564f896ea416898d007e9d49d6718 +msgid "Now you should have all of the DEB packages and ``Packages.gz`` in the ``binary`` directory and available over HTTP. (You may want to use ``wget`` or ``curl`` to test this before moving on to the next step.)" +msgstr "" + +#: ../../building_from_source.rst:278 +# c7c808299766447184af66ba621c649f +msgid "Configuring your machines to use the APT repository" +msgstr "" + +#: ../../building_from_source.rst:280 +# dfdd1c5b583743d0b5156002e9f3ffb9 +msgid "Now that we have created the repository, you need to configure your machine to make use of the APT repository. You can do this by adding a repository file under ``/etc/apt/sources.list.d``. Use your preferred editor to create ``/etc/apt/sources.list.d/cloudstack.list`` with this line:" +msgstr "" + +#: ../../building_from_source.rst:290 +# 8cad604cc3474e2bb424225f2d519465 +msgid "Now that you have the repository info in place, you'll want to run another update so that APT knows where to find the CloudStack packages." +msgstr "" + +#: ../../building_from_source.rst:297 +# ae0dd676f4ec4158b5f3bd6fd9c6c414 +msgid "You can now move on to the instructions under Install on Ubuntu." +msgstr "" + +#: ../../building_from_source.rst:300 +# 99e76b064e8447a78d810b22c43f6f41 +msgid "Building RPMs from Source" +msgstr "" + +#: ../../building_from_source.rst:302 +# f2be124577f84dd497fb762733f58ef8 +msgid "As mentioned previously in `âPrerequisites for building Apache CloudStackâ <#prerequisites-for-building-apache-cloudstack>`_, you will need to install several prerequisites before you can build packages for CloudStack. Here we'll assume you're working with a 64-bit build of CentOS or Red Hat Enterprise Linux." +msgstr "" + +#: ../../building_from_source.rst:316 +# 147d967fe07344fda8b630d94ecbf22e +msgid "Next, you'll need to install build-time dependencies for CloudStack with Maven. We're using Maven 3, so you'll want to `grab a Maven 3 tarball <http://maven.apache.org/download.cgi>`_ and uncompress it in your home directory (or whatever location you prefer):" +msgstr "" + +#: ../../building_from_source.rst:329 +# 1a9e316005174aeaa91a7dcfbaade092 +msgid "Maven also needs to know where Java is, and expects the JAVA\\_HOME environment variable to be set:" +msgstr "" + +#: ../../building_from_source.rst:336 +# 4ab8a6164f45425aa7186cdf64e8d55e +msgid "Verify that Maven is installed correctly:" +msgstr "" + +#: ../../building_from_source.rst:342 +# 3843f8810db04c80a8eee7f3cae3f4bf +msgid "You probably want to ensure that your environment variables will survive a logout/reboot. Be sure to update ``~/.bashrc`` with the PATH and JAVA\\_HOME variables." +msgstr "" + +#: ../../building_from_source.rst:346 +# 490ba6dd066441edb4adc61fb071e8a7 +msgid "Building RPMs for CloudStack is fairly simple. Assuming you already have the source downloaded and have uncompressed the tarball into a local directory, you're going to be able to generate packages in just a few minutes." +msgstr "" + +#: ../../building_from_source.rst:353 +# e0cc268134ba44c9a96d06b97e687c39 +msgid "Packaging has Changed. If you've created packages for CloudStack previously, you should be aware that the process has changed considerably since the project has moved to using Apache Maven. Please be sure to follow the steps in this section closely." +msgstr "" + +#: ../../building_from_source.rst:356 +# b79c6f303f0544719c940cfc32027819 +msgid "Generating RPMS" +msgstr "" + +#: ../../building_from_source.rst:358 +# 03b60158092748f6aa6b7d5994c892d2 +msgid "Now that we have the prerequisites and source, you will cd to the `packaging/centos63/` directory." +msgstr "" + +#: ../../building_from_source.rst:364 +# 3154e33699074662a1395386b9c3a4a8 +msgid "Generating RPMs is done using the ``package.sh`` script:" +msgstr "" + +#: ../../building_from_source.rst:370 +# 68d539d69bc54749a69f503b004525b0 +msgid "That will run for a bit and then place the finished packages in ``dist/rpmbuild/RPMS/x86_64/``." +msgstr "" + +#: ../../building_from_source.rst:373 +# 6ba124f893f243f7af26aefe9811bc73 +msgid "You should see the following RPMs in that directory:" +msgstr "" + +#: ../../building_from_source.rst:386 +# 370fc4f0661540ca95e53491f26361ea +msgid "Creating a yum repo" +msgstr "" + +#: ../../building_from_source.rst:388 +# bbc6c3630b1a44dd92fe24fb24a32c43 +msgid "While RPMs is a useful packaging format - it's most easily consumed from Yum repositories over a network. The next step is to create a Yum Repo with the finished packages:" +msgstr "" + +#: ../../building_from_source.rst:404 +# 7ca5148dbc3f47a195336d3ea4dc066d +msgid "The files and directories within ``~/tmp/repo`` can now be uploaded to a web server and serve as a yum repository." +msgstr "" + +#: ../../building_from_source.rst:408 +# 3c1f1920404c4b4b9aed29b8216a8ca1 +msgid "Configuring your systems to use your new yum repository" +msgstr "" + +#: ../../building_from_source.rst:410 +# bbc87560e0c642ecbfa67f722b3b9693 +msgid "Now that your yum repository is populated with RPMs and metadata we need to configure the machines that need to install CloudStack. Create a file named ``/etc/yum.repos.d/cloudstack.repo`` with this information:" +msgstr "" + +#: ../../building_from_source.rst:422 +# b398f895b7ff4282b6613bad45a98c08 +msgid "Completing this step will allow you to easily install CloudStack on a number of machines across the network." +msgstr "" + +#: ../../building_from_source.rst:426 +# 478d4e8b829044e8949f587dd0f09b52 +msgid "Building Non-OSS" +msgstr "" + +#: ../../building_from_source.rst:428 +# 2fe549e0cdc44e51ba030c3fa3499914 +msgid "If you need support for the VMware, NetApp, F5, NetScaler, SRX, or any other non-Open Source Software (nonoss) plugins, you'll need to download a few components on your own and follow a slightly different procedure to build from source." +msgstr "" + +#: ../../building_from_source.rst:435 +# 46d5a64c225c401c8e2b16f77095e6f3 +msgid "Some of the plugins supported by CloudStack cannot be distributed with CloudStack for licensing reasons. In some cases, some of the required libraries/JARs are under a proprietary license. In other cases, the required libraries may be under a license that's not compatible with `Apache's licensing guidelines for third-party products <http://www.apache.org/legal/resolved.html#category-x>`_." +msgstr "" + +#: ../../building_from_source.rst:439 +# b30c64ffa9bb46819fc70c71f7606020 +msgid "To build the Non-OSS plugins, you'll need to have the requisite JARs installed under the ``deps`` directory." +msgstr "" + +#: ../../building_from_source.rst:442 +# 965deab2226a46d98c7e5962c98f344e +msgid "Because these modules require dependencies that can't be distributed with CloudStack you'll need to download them yourself. Links to the most recent dependencies are listed on the `*How to build CloudStack* <https://cwiki.apache.org/confluence/display/CLOUDSTACK/How+to+build+CloudStack>`_ page on the wiki." +msgstr "" + +#: ../../building_from_source.rst:449 +# 78a1f8deba41498f80a2f83003d44bc3 +msgid "You may also need to download `vhd-util <http://download.cloud.com.s3.amazonaws.com/tools/vhd-util>`_, which was removed due to licensing issues. You'll copy vhd-util to the ``scripts/vm/hypervisor/xenserver/`` directory." +msgstr "" + +#: ../../building_from_source.rst:456 +# b4c294257936418c9d6c6889ce615a13 +msgid "Once you have all the dependencies copied over, you'll be able to build CloudStack with the ``noredist`` option:" +msgstr "" + +#: ../../building_from_source.rst:466 +# c135a16bcffe490da30abf3c3425ccdb +msgid "Once you've built CloudStack with the ``noredist`` profile, you can package it using the `âBuilding RPMs from Sourceâ <#building-rpms-from-source>`_ or `âBuilding DEB packagesâ <#building-deb-packages>`_ instructions." +msgstr "" + http://git-wip-us.apache.org/repos/asf/cloudstack-docs-install/blob/bd81bcc4/source/locale/pot/choosing_deployment_architecture.pot ---------------------------------------------------------------------- diff --git a/source/locale/pot/choosing_deployment_architecture.pot b/source/locale/pot/choosing_deployment_architecture.pot new file mode 100644 index 0000000..fbf1045 --- /dev/null +++ b/source/locale/pot/choosing_deployment_architecture.pot @@ -0,0 +1,511 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2014, Apache Software Foundation +# This file is distributed under the same license as the Apache CloudStack Installation Documentation package. +# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: Apache CloudStack Installation Documentation 4\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2014-03-31 14:02-0400\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n" +"Language-Team: LANGUAGE <[email protected]>\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" + +#: ../../choosing_deployment_architecture.rst:17 +# 52edd48cc24f4706b9641e18921e1dfc +msgid "Choosing a Deployment Architecture" +msgstr "" + +#: ../../choosing_deployment_architecture.rst:19 +# 4ebda8e26c5642b79a5e800fb698afcf +msgid "The architecture used in a deployment will vary depending on the size and purpose of the deployment. This section contains examples of deployment architecture, including a small-scale deployment useful for test and trial deployments and a fully-redundant large-scale setup for production deployments." +msgstr "" + +#: ../../choosing_deployment_architecture.rst:26 +# e6eca26710584474b1704256861555bd +msgid "Small-Scale Deployment" +msgstr "" + +#: ../../choosing_deployment_architecture.rst:28 +# 504a3c65a9d44537bca5bac7444ffe77 +msgid "|Small-Scale Deployment|" +msgstr "" + +#: ../../choosing_deployment_architecture.rst:30 +# f11bad72391b4deb92c5d7118b32d881 +msgid "This diagram illustrates the network architecture of a small-scale CloudStack deployment." +msgstr "" + +#: ../../choosing_deployment_architecture.rst:35 +# 6ba24ea751eb44d985b826558267d392 +msgid "A firewall provides a connection to the Internet. The firewall is configured in NAT mode. The firewall forwards HTTP requests and API calls from the Internet to the Management Server. The Management Server resides on the management network." +msgstr "" + +#: ../../choosing_deployment_architecture.rst:42 +# 3426fafddfbd47eca9b6e972998e3bae +msgid "A layer-2 switch connects all physical servers and storage." +msgstr "" + +#: ../../choosing_deployment_architecture.rst:46 +# ef86a72ce6a44739aa9e46e68b64df56 +msgid "A single NFS server functions as both the primary and secondary storage." +msgstr "" + +#: ../../choosing_deployment_architecture.rst:51 +# f507e94ad4584311980de03cd3e8915b +msgid "The Management Server is connected to the management network." +msgstr "" + +#: ../../choosing_deployment_architecture.rst:54 +# 1ffca21a6b404d6894a747a4583dbad8 +msgid "Large-Scale Redundant Setup" +msgstr "" + +#: ../../choosing_deployment_architecture.rst:56 +# 99045d1800c5403d892894a8d4fc8002 +msgid "|Large-Scale Redundant Setup|" +msgstr "" + +#: ../../choosing_deployment_architecture.rst:58 +# d6858644d12a4f22b3de25594cedc309 +msgid "This diagram illustrates the network architecture of a large-scale CloudStack deployment." +msgstr "" + +#: ../../choosing_deployment_architecture.rst:63 +# c4c3f668a4a145c1ac376c5ee607dccb +msgid "A layer-3 switching layer is at the core of the data center. A router redundancy protocol like VRRP should be deployed. Typically high-end core switches also include firewall modules. Separate firewall appliances may also be used if the layer-3 switch does not have integrated firewall capabilities. The firewalls are configured in NAT mode. The firewalls provide the following functions:" +msgstr "" + +#: ../../choosing_deployment_architecture.rst:72 +# a23de965c5ec447c84154204ca887790 +msgid "Forwards HTTP requests and API calls from the Internet to the Management Server. The Management Server resides on the management network." +msgstr "" + +#: ../../choosing_deployment_architecture.rst:78 +# 90da3245af0d4917b933c01a6c8f8332 +msgid "When the cloud spans multiple zones, the firewalls should enable site-to-site VPN such that servers in different zones can directly reach each other." +msgstr "" + +#: ../../choosing_deployment_architecture.rst:84 +# 69cfdebf1e6e4d549b52b88a593df61e +msgid "A layer-2 access switch layer is established for each pod. Multiple switches can be stacked to increase port count. In either case, redundant pairs of layer-2 switches should be deployed." +msgstr "" + +#: ../../choosing_deployment_architecture.rst:90 +# 3902d59efe794d8da02773b18a3144ff +msgid "The Management Server cluster (including front-end load balancers, Management Server nodes, and the MySQL database) is connected to the management network through a pair of load balancers." +msgstr "" + +#: ../../choosing_deployment_architecture.rst:96 +# 1f11aed9571044e9b9fc673435cb0de7 +msgid "Secondary storage servers are connected to the management network." +msgstr "" + +#: ../../choosing_deployment_architecture.rst:100 +# ea82de9a210d4a228f110dfe9ecdfb1e +msgid "Each pod contains storage and computing servers. Each storage and computing server should have redundant NICs connected to separate layer-2 access switches." +msgstr "" + +#: ../../choosing_deployment_architecture.rst:105 +# 7ceefe1102644c9ab58eed60cdb7f2bd +msgid "Separate Storage Network" +msgstr "" + +#: ../../choosing_deployment_architecture.rst:107 +# 983feefb13f1459ba566781908bfcd93 +msgid "In the large-scale redundant setup described in the previous section, storage traffic can overload the management network. A separate storage network is optional for deployments. Storage protocols such as iSCSI are sensitive to network delays. A separate storage network ensures guest network traffic contention does not impact storage performance." +msgstr "" + +#: ../../choosing_deployment_architecture.rst:114 +# edd1971372014c5abd34993129275f55 +msgid "Multi-Node Management Server" +msgstr "" + +#: ../../choosing_deployment_architecture.rst:116 +# cb554f7ea8af4b899da19bad60af3f11 +msgid "The CloudStack Management Server is deployed on one or more front-end servers connected to a single MySQL database. Optionally a pair of hardware load balancers distributes requests from the web. A backup management server set may be deployed using MySQL replication at a remote site to add DR capabilities." +msgstr "" + +#: ../../choosing_deployment_architecture.rst:122 +# 0507a6b19f114eb08708577219e394af +msgid "|Multi-Node Management Server|" +msgstr "" + +#: ../../choosing_deployment_architecture.rst:124 +# 2afcbc3e300d490d8526df89fe36c54f +msgid "The administrator must decide the following." +msgstr "" + +#: ../../choosing_deployment_architecture.rst:128 +# 6ea7062b2c3e4d67b082de9b02757b4e +msgid "Whether or not load balancers will be used." +msgstr "" + +#: ../../choosing_deployment_architecture.rst:132 +# 7625aabc231a4cddb9af421ea15281d0 +msgid "How many Management Servers will be deployed." +msgstr "" + +#: ../../choosing_deployment_architecture.rst:136 +# ed2af9d37ed34e6e89c234099fcccb4b +msgid "Whether MySQL replication will be deployed to enable disaster recovery." +msgstr "" + +#: ../../choosing_deployment_architecture.rst:140 +# be8d00f78d464cc2aa58e01d300a948b +msgid "Multi-Site Deployment" +msgstr "" + +#: ../../choosing_deployment_architecture.rst:142 +# 1fff976cf3344b6a8c06c3b56d9568ef +msgid "The CloudStack platform scales well into multiple sites through the use of zones. The following diagram shows an example of a multi-site deployment." +msgstr "" + +#: ../../choosing_deployment_architecture.rst:146 +# ef026e2d1151436eb064cd8bf77db549 +msgid "|Example Of A Multi-Site Deployment|" +msgstr "" + +#: ../../choosing_deployment_architecture.rst:148 +# 7ea2ca98a7094edab2212c4e776e349b +msgid "Data Center 1 houses the primary Management Server as well as zone 1. The MySQL database is replicated in real time to the secondary Management Server installation in Data Center 2." +msgstr "" + +#: ../../choosing_deployment_architecture.rst:152 +# 39563946112d4b07afc28800922068ee +msgid "|Separate Storage Network|" +msgstr "" + +#: ../../choosing_deployment_architecture.rst:154 +# e7cc868c4aa64cbe80807d7809ce58cb +msgid "This diagram illustrates a setup with a separate storage network. Each server has four NICs, two connected to pod-level network switches and two connected to storage network switches." +msgstr "" + +#: ../../choosing_deployment_architecture.rst:158 +# 6157f0ee2cf84c49ac9f4f4ca1cdb0cd +msgid "There are two ways to configure the storage network:" +msgstr "" + +#: ../../choosing_deployment_architecture.rst:162 +# cc2bdc7b44e146c18dfb9826c12b15f0 +msgid "Bonded NIC and redundant switches can be deployed for NFS. In NFS deployments, redundant switches and bonded NICs still result in one network (one CIDR block+ default gateway address)." +msgstr "" + +#: ../../choosing_deployment_architecture.rst:168 +# 0aa73c8538074a00b5b5305e33db5ed4 +msgid "iSCSI can take advantage of two separate storage networks (two CIDR blocks each with its own default gateway). Multipath iSCSI client can failover and load balance between separate storage networks." +msgstr "" + +#: ../../choosing_deployment_architecture.rst:172 +# 0e03920329f540e08c1ea89e9a7d05dd +msgid "|NIC Bonding And Multipath I/O|" +msgstr "" + +#: ../../choosing_deployment_architecture.rst:174 +# 9219775ffce04cada583a2d12a90524f +msgid "This diagram illustrates the differences between NIC bonding and Multipath I/O (MPIO). NIC bonding configuration involves only one network. MPIO involves two separate networks." +msgstr "" + +#: ../../choosing_deployment_architecture.rst:180 +# 0b1fe0948d434c1baf1a34edbb1847a0 +msgid "Choosing a Hypervisor" +msgstr "" + +#: ../../choosing_deployment_architecture.rst:182 +# f9313ca35f6f4589aed2bea3122829e7 +msgid "CloudStack supports many popular hypervisors. Your cloud can consist entirely of hosts running a single hypervisor, or you can use multiple hypervisors. Each cluster of hosts must run the same hypervisor." +msgstr "" + +#: ../../choosing_deployment_architecture.rst:186 +# a54304966f514ffabe4dfad79eedc5eb +msgid "You might already have an installed base of nodes running a particular hypervisor, in which case, your choice of hypervisor has already been made. If you are starting from scratch, you need to decide what hypervisor software best suits your needs. A discussion of the relative advantages of each hypervisor is outside the scope of our documentation. However, it will help you to know which features of each hypervisor are supported by CloudStack. The following table provides this information." +msgstr "" + +#: ../../choosing_deployment_architecture.rst:195 +# 3693e4b064964090ac1242961e0a8946 +msgid "Feature" +msgstr "" + +#: ../../choosing_deployment_architecture.rst:195 +# d3865d119f144b4d9207d2fd8e7578b9 +msgid "XenServer 6.0.2" +msgstr "" + +#: ../../choosing_deployment_architecture.rst:195 +# b48b4cda653049f1a9422c908232ff17 +msgid "vSphere 4.1/5.0" +msgstr "" + +#: ../../choosing_deployment_architecture.rst:195 +# fed595ccd4cc4c4a9623807e16fefde5 +msgid "KVM - RHEL 6.2" +msgstr "" + +#: ../../choosing_deployment_architecture.rst:195 +# d393ed42dc224b8684dbf6d8ab9d99c2 +msgid "Bare Metal" +msgstr "" + +#: ../../choosing_deployment_architecture.rst:197 +# 1ba867f8783d4ac38bca542e7a1248be +msgid "Network Throttling" +msgstr "" + +#: ../../choosing_deployment_architecture.rst:197 +#: ../../choosing_deployment_architecture.rst:197 +#: ../../choosing_deployment_architecture.rst:198 +#: ../../choosing_deployment_architecture.rst:198 +#: ../../choosing_deployment_architecture.rst:199 +#: ../../choosing_deployment_architecture.rst:199 +#: ../../choosing_deployment_architecture.rst:199 +#: ../../choosing_deployment_architecture.rst:200 +#: ../../choosing_deployment_architecture.rst:200 +#: ../../choosing_deployment_architecture.rst:200 +#: ../../choosing_deployment_architecture.rst:201 +#: ../../choosing_deployment_architecture.rst:201 +#: ../../choosing_deployment_architecture.rst:201 +#: ../../choosing_deployment_architecture.rst:201 +#: ../../choosing_deployment_architecture.rst:202 +#: ../../choosing_deployment_architecture.rst:202 +#: ../../choosing_deployment_architecture.rst:203 +#: ../../choosing_deployment_architecture.rst:203 +#: ../../choosing_deployment_architecture.rst:203 +#: ../../choosing_deployment_architecture.rst:206 +#: ../../choosing_deployment_architecture.rst:206 +#: ../../choosing_deployment_architecture.rst:206 +#: ../../choosing_deployment_architecture.rst:207 +#: ../../choosing_deployment_architecture.rst:207 +# be052665fb9c4db6abf644607c11a2ce +# a4b89b4ef4524eaa817ecdc80d28220e +# 19def2d9dbcc4ab2b156efdb3105c12c +# 9ea945d4e8004ddc87df1fc03980dce1 +# 4b880eb52259476c8b34809b91f7d3a3 +# 5b1d1cb21d6e45418d722dfddd325379 +# f403583dce4044a984df0474dbd133ad +# e854f5913eee4b7c8abc33a936ef79f5 +# 639f24e5f94f42c98eb830f204f15720 +# 80f0710f7c8b47a481f04b3014a226c1 +# 699e94d60d9e4854a476539896363037 +# aa96059d21ac4ebcba125d36c1152217 +# 8e95523da0cb41bfb474406df9fb8145 +# 27cff33f4c064fbeb2f9f48ecef6f1cb +# 086c38882e6b42ab8947506109c27cfd +# e3902495150d4d56979b58303e1c731c +# 2020f8688efe46629b40a7250d3111d0 +# 66c69ff810ef4413bfb1945563069a19 +# 513c35fbd6f04423bd9c3d783a99b4dc +# 84cff98be301475280c880d4da63670b +# d91c60035cce41bf94a8091fb6c37bb3 +# 47bdf8e2d92f4d3a8a2817cc47bed1ed +# c160f1f7b53544bc91fdbfae297359cb +# 11fbe78348e24da89d9e7307aee4769c +msgid "Yes" +msgstr "" + +#: ../../choosing_deployment_architecture.rst:197 +#: ../../choosing_deployment_architecture.rst:198 +#: ../../choosing_deployment_architecture.rst:198 +#: ../../choosing_deployment_architecture.rst:204 +#: ../../choosing_deployment_architecture.rst:204 +#: ../../choosing_deployment_architecture.rst:204 +#: ../../choosing_deployment_architecture.rst:205 +#: ../../choosing_deployment_architecture.rst:205 +#: ../../choosing_deployment_architecture.rst:207 +# cd83b27113e841ac916e00bcd1082008 +# 1947bdafae1f4b5a9061c6eb1cb2b99c +# d3de86e130104668a664aa03d61c32a6 +# c0adf6e94804483a9dbfd425bab70401 +# fa80ad1123b1402aaac21bfc7d19b636 +# 5dd1209f3e2a41d7aa8489e8ace6aadf +# 280839b6b2744ce58570ac30f941863b +# b2a56672e17b4744bf8c11d6f41f42db +# 2838338f3d264292ac265635c4cec016 +msgid "No" +msgstr "" + +#: ../../choosing_deployment_architecture.rst:197 +#: ../../choosing_deployment_architecture.rst:199 +#: ../../choosing_deployment_architecture.rst:200 +#: ../../choosing_deployment_architecture.rst:202 +#: ../../choosing_deployment_architecture.rst:203 +#: ../../choosing_deployment_architecture.rst:204 +#: ../../choosing_deployment_architecture.rst:205 +#: ../../choosing_deployment_architecture.rst:206 +#: ../../choosing_deployment_architecture.rst:207 +# b2723a3c2a3d40bb8905525b93d521db +# df278255008f48bba701f08e2746a45b +# 41891d2dfaec4726afd7af756ccf6ae3 +# 7de26acf53854ee19c25494093e873d8 +# e5b105be128f4a0f9b5a4b0ea089b340 +# c86cc373ee974129bcbc17d0c34fd3a9 +# 29d8fb39d33d44089307d76a24192b93 +# f2adc402745f4312b27cc7579ba3549a +# 899efc660f874882befc3436419f4150 +msgid "N/A" +msgstr "" + +#: ../../choosing_deployment_architecture.rst:198 +# 46133f6d28554c339a302a0bc5a80174 +msgid "Security groups in zones that use basic networking" +msgstr "" + +#: ../../choosing_deployment_architecture.rst:199 +# 067683e3c1a940c483f5c2a1156135ec +msgid "iSCSI" +msgstr "" + +#: ../../choosing_deployment_architecture.rst:200 +# cca8044dd01e463d90beaec88dd13bfd +msgid "FibreChannel" +msgstr "" + +#: ../../choosing_deployment_architecture.rst:201 +# 9b3992c401fb484aa373c97609af73d5 +msgid "Local Disk" +msgstr "" + +#: ../../choosing_deployment_architecture.rst:202 +# d7598b6aa7a24f3f890494e960b14b72 +msgid "HA" +msgstr "" + +#: ../../choosing_deployment_architecture.rst:202 +# 2f14e2bad82d4187b34b6ecf7b185397 +msgid "Yes (Native)" +msgstr "" + +#: ../../choosing_deployment_architecture.rst:203 +# 991329dd067d4fc0b84a473c2b9738d6 +msgid "Snapshots of local disk" +msgstr "" + +#: ../../choosing_deployment_architecture.rst:204 +# 82d0be0fc5014fb199a1e335495bb0e4 +msgid "Local disk as data disk" +msgstr "" + +#: ../../choosing_deployment_architecture.rst:205 +# 9606914b8d0d42e4bf6a230c8b66b0a4 +msgid "Work load balancing" +msgstr "" + +#: ../../choosing_deployment_architecture.rst:205 +# e51f36058e824167a36e9ae71df467fc +msgid "DRS" +msgstr "" + +#: ../../choosing_deployment_architecture.rst:206 +# 71c333daaabe476ab414b0a03b7ae88e +msgid "Manual live migration of VMs from host to host" +msgstr "" + +#: ../../choosing_deployment_architecture.rst:207 +# c47b20ce94d448a4aa6add55bd117597 +msgid "Conserve management traffic IP address by using link local network to communicate with virtual router" +msgstr "" + +#: ../../choosing_deployment_architecture.rst:212 +# cb5323a6d0ef49c283024dd46d0b4ef0 +msgid "Best Practices" +msgstr "" + +#: ../../choosing_deployment_architecture.rst:214 +# adc9a356d253458ca9d971565f3bf1b3 +msgid "Deploying a cloud is challenging. There are many different technology choices to make, and CloudStack is flexible enough in its configuration that there are many possible ways to combine and configure the chosen technology. This section contains suggestions and requirements about cloud deployments." +msgstr "" + +#: ../../choosing_deployment_architecture.rst:220 +# c077c29e871a451085be2f9d93d6ce0b +msgid "These should be treated as suggestions and not absolutes. However, we do encourage anyone planning to build a cloud outside of these guidelines to seek guidance and advice on the project mailing lists." +msgstr "" + +#: ../../choosing_deployment_architecture.rst:225 +# c312a003df984d1e99a7daef9dff794b +msgid "Process Best Practices" +msgstr "" + +#: ../../choosing_deployment_architecture.rst:229 +# abc014ba86804cf1b60a7e800d7692d1 +msgid "A staging system that models the production environment is strongly advised. It is critical if customizations have been applied to CloudStack." +msgstr "" + +#: ../../choosing_deployment_architecture.rst:235 +# 4422c6e1832a4ede9621424bc85274ad +msgid "Allow adequate time for installation, a beta, and learning the system. Installs with basic networking can be done in hours. Installs with advanced networking usually take several days for the first attempt, with complicated installations taking longer. For a full production system, allow at least 4-8 weeks for a beta to work through all of the integration issues. You can get help from fellow users on the cloudstack-users mailing list." +msgstr "" + +#: ../../choosing_deployment_architecture.rst:244 +# e404a3ea1a28429ca6f54d86384ce11e +msgid "Setup Best Practices" +msgstr "" + +#: ../../choosing_deployment_architecture.rst:248 +# 2c6d3efd9c624e11861404be6de4db3e +msgid "Each host should be configured to accept connections only from well-known entities such as the CloudStack Management Server or your network monitoring software." +msgstr "" + +#: ../../choosing_deployment_architecture.rst:254 +# ef5b0d453e974244b9f46701aae6a09a +msgid "Use multiple clusters per pod if you need to achieve a certain switch density." +msgstr "" + +#: ../../choosing_deployment_architecture.rst:259 +# bb554a90a44a4d678ac338f55d01f8ee +msgid "Primary storage mountpoints or LUNs should not exceed 6 TB in size. It is better to have multiple smaller primary storage elements per cluster than one large one." +msgstr "" + +#: ../../choosing_deployment_architecture.rst:265 +# 3a69638a02c74393987657eaef675207 +msgid "When exporting shares on primary storage, avoid data loss by restricting the range of IP addresses that can access the storage. See \"Linux NFS on Local Disks and DAS\" or \"Linux NFS on iSCSI\"." +msgstr "" + +#: ../../choosing_deployment_architecture.rst:271 +# ccf0998ec590457198f2ba04de50f1fa +msgid "NIC bonding is straightforward to implement and provides increased reliability." +msgstr "" + +#: ../../choosing_deployment_architecture.rst:276 +# d5767cccb17c4f4e857a0446daa2e67b +msgid "10G networks are generally recommended for storage access when larger servers that can support relatively more VMs are used." +msgstr "" + +#: ../../choosing_deployment_architecture.rst:281 +# 34ffd751b3bb476ba1f3f2e608b93d3d +msgid "Host capacity should generally be modeled in terms of RAM for the guests. Storage and CPU may be overprovisioned. RAM may not. RAM is usually the limiting factor in capacity designs." +msgstr "" + +#: ../../choosing_deployment_architecture.rst:287 +# 6d2c0b24d26849a19a4b45b81b27574d +msgid "(XenServer) Configure the XenServer dom0 settings to allocate more memory to dom0. This can enable XenServer to handle larger numbers of virtual machines. We recommend 2940 MB of RAM for XenServer dom0. For instructions on how to do this, see `http://support.citrix.com/article/CTX126531 <http://support.citrix.com/article/CTX126531>`_. The article refers to XenServer 5.6, but the same information applies to XenServer 6.0." +msgstr "" + +#: ../../choosing_deployment_architecture.rst:296 +# d527abb1d09c439194238f9a516c50c5 +msgid "Maintenance Best Practices" +msgstr "" + +#: ../../choosing_deployment_architecture.rst:300 +# e86da3bff33947e2907910514580b7bf +msgid "Monitor host disk space. Many host failures occur because the host's root disk fills up from logs that were not rotated adequately." +msgstr "" + +#: ../../choosing_deployment_architecture.rst:305 +# c53de7cac3554464bfb3b37704d3aa62 +msgid "Monitor the total number of VM instances in each cluster, and disable allocation to the cluster if the total is approaching the maximum that the hypervisor can handle. Be sure to leave a safety margin to allow for the possibility of one or more hosts failing, which would increase the VM load on the other hosts as the VMs are redeployed. Consult the documentation for your chosen hypervisor to find the maximum permitted number of VMs per host, then use CloudStack global configuration settings to set this as the default limit. Monitor the VM activity in each cluster and keep the total number of VMs below a safe level that allows for the occasional host failure. For example, if there are N hosts in the cluster, and you want to allow for one host in the cluster to be down at any given time, the total number of VM instances you can permit in the cluster is at most (N-1) \\* (per-host-limit). Once a cluster reaches this number of VMs, use the CloudStack UI to disable allocation to t he cluster." +msgstr "" + +#: ../../choosing_deployment_architecture.rst:323 +# 89ae9c94778c48a2a29f1b11ff95a571 +msgid "The lack of up-do-date hotfixes can lead to data corruption and lost VMs." +msgstr "" + +#: ../../choosing_deployment_architecture.rst:325 +# 28c8fb8da4a24ab4b15726bb4efb7ead +msgid "Be sure all the hotfixes provided by the hypervisor vendor are applied. Track the release of hypervisor patches through your hypervisor vendorâs support channel, and apply patches as soon as possible after they are released. CloudStack will not track or notify you of required hypervisor patches. It is essential that your hosts are completely up to date with the provided hypervisor patches. The hypervisor vendor is likely to refuse to support any system that is not up to date with patches." +msgstr "" +
