You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cloudstack.apache.org by se...@apache.org on 2014/03/31 20:14:57 UTC
[8/8] git commit: setup i18n with transifex and sphinx-intl
setup i18n with transifex and sphinx-intl
Project: http://git-wip-us.apache.org/repos/asf/cloudstack-docs-admin/repo
Commit: http://git-wip-us.apache.org/repos/asf/cloudstack-docs-admin/commit/65303ea3
Tree: http://git-wip-us.apache.org/repos/asf/cloudstack-docs-admin/tree/65303ea3
Diff: http://git-wip-us.apache.org/repos/asf/cloudstack-docs-admin/diff/65303ea3
Branch: refs/heads/master
Commit: 65303ea3b0d943b17c70bbe71ee06d1c0c6a310e
Parents: 41c0b33
Author: Sebastien Goasguen <ru...@gmail.com>
Authored: Mon Mar 31 14:14:39 2014 -0400
Committer: Sebastien Goasguen <ru...@gmail.com>
Committed: Mon Mar 31 14:14:39 2014 -0400
----------------------------------------------------------------------
.gitignore | 1 +
.tx/config | 104 +
Makefile | 4 +-
README.rst | 34 +
source/locale/pot/accounts.pot | 409 ++
source/locale/pot/administration.pot | 63 +
source/locale/pot/api.pot | 123 +
source/locale/pot/events.pot | 332 ++
source/locale/pot/hosts.pot | 828 ++++
source/locale/pot/index.pot | 103 +
source/locale/pot/management.pot | 458 ++
source/locale/pot/networking.pot | 765 +++
source/locale/pot/networking2.pot | 6796 ++++++++++++++++++++++++++
source/locale/pot/projects.pot | 600 +++
source/locale/pot/reliability.pot | 368 ++
source/locale/pot/service_offerings.pot | 809 +++
source/locale/pot/storage.pot | 1106 +++++
source/locale/pot/systemvm.pot | 740 +++
source/locale/pot/templates.pot | 1215 +++++
source/locale/pot/troubleshooting.pot | 383 ++
source/locale/pot/tuning.pot | 123 +
source/locale/pot/ui.pot | 345 ++
source/locale/pot/usage.pot | 1497 ++++++
source/locale/pot/virtual_machines.pot | 1456 ++++++
24 files changed, 18660 insertions(+), 2 deletions(-)
----------------------------------------------------------------------
http://git-wip-us.apache.org/repos/asf/cloudstack-docs-admin/blob/65303ea3/.gitignore
----------------------------------------------------------------------
diff --git a/.gitignore b/.gitignore
index a5819d9..e955aad 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-admin/blob/65303ea3/.tx/config
----------------------------------------------------------------------
diff --git a/.tx/config b/.tx/config
new file mode 100644
index 0000000..4bc5a06
--- /dev/null
+++ b/.tx/config
@@ -0,0 +1,104 @@
+[main]
+host = https://www.transifex.com
+type = PO
+
+[apache-cloudstack-administration-rtd.accounts]
+file_filter = source/locale/<lang>/LC_MESSAGES/accounts.po
+source_file = source/locale/pot/accounts.pot
+source_lang = en
+
+[apache-cloudstack-administration-rtd.administration]
+file_filter = source/locale/<lang>/LC_MESSAGES/administration.po
+source_file = source/locale/pot/administration.pot
+source_lang = en
+
+[apache-cloudstack-administration-rtd.api]
+file_filter = source/locale/<lang>/LC_MESSAGES/api.po
+source_file = source/locale/pot/api.pot
+source_lang = en
+
+[apache-cloudstack-administration-rtd.events]
+file_filter = source/locale/<lang>/LC_MESSAGES/events.po
+source_file = source/locale/pot/events.pot
+source_lang = en
+
+[apache-cloudstack-administration-rtd.hosts]
+file_filter = source/locale/<lang>/LC_MESSAGES/hosts.po
+source_file = source/locale/pot/hosts.pot
+source_lang = en
+
+[apache-cloudstack-administration-rtd.index]
+file_filter = source/locale/<lang>/LC_MESSAGES/index.po
+source_file = source/locale/pot/index.pot
+source_lang = en
+
+[apache-cloudstack-administration-rtd.management]
+file_filter = source/locale/<lang>/LC_MESSAGES/management.po
+source_file = source/locale/pot/management.pot
+source_lang = en
+
+[apache-cloudstack-administration-rtd.networking]
+file_filter = source/locale/<lang>/LC_MESSAGES/networking.po
+source_file = source/locale/pot/networking.pot
+source_lang = en
+
+[apache-cloudstack-administration-rtd.networking2]
+file_filter = source/locale/<lang>/LC_MESSAGES/networking2.po
+source_file = source/locale/pot/networking2.pot
+source_lang = en
+
+[apache-cloudstack-administration-rtd.projects]
+file_filter = source/locale/<lang>/LC_MESSAGES/projects.po
+source_file = source/locale/pot/projects.pot
+source_lang = en
+
+[apache-cloudstack-administration-rtd.reliability]
+file_filter = source/locale/<lang>/LC_MESSAGES/reliability.po
+source_file = source/locale/pot/reliability.pot
+source_lang = en
+
+[apache-cloudstack-administration-rtd.service_offerings]
+file_filter = source/locale/<lang>/LC_MESSAGES/service_offerings.po
+source_file = source/locale/pot/service_offerings.pot
+source_lang = en
+
+[apache-cloudstack-administration-rtd.storage]
+file_filter = source/locale/<lang>/LC_MESSAGES/storage.po
+source_file = source/locale/pot/storage.pot
+source_lang = en
+
+[apache-cloudstack-administration-rtd.systemvm]
+file_filter = source/locale/<lang>/LC_MESSAGES/systemvm.po
+source_file = source/locale/pot/systemvm.pot
+source_lang = en
+
+[apache-cloudstack-administration-rtd.templates]
+file_filter = source/locale/<lang>/LC_MESSAGES/templates.po
+source_file = source/locale/pot/templates.pot
+source_lang = en
+
+[apache-cloudstack-administration-rtd.troubleshooting]
+file_filter = source/locale/<lang>/LC_MESSAGES/troubleshooting.po
+source_file = source/locale/pot/troubleshooting.pot
+source_lang = en
+
+[apache-cloudstack-administration-rtd.tuning]
+file_filter = source/locale/<lang>/LC_MESSAGES/tuning.po
+source_file = source/locale/pot/tuning.pot
+source_lang = en
+
+[apache-cloudstack-administration-rtd.ui]
+file_filter = source/locale/<lang>/LC_MESSAGES/ui.po
+source_file = source/locale/pot/ui.pot
+source_lang = en
+
+[apache-cloudstack-administration-rtd.usage]
+file_filter = source/locale/<lang>/LC_MESSAGES/usage.po
+source_file = source/locale/pot/usage.pot
+source_lang = en
+
+[apache-cloudstack-administration-rtd.virtual_machines]
+file_filter = source/locale/<lang>/LC_MESSAGES/virtual_machines.po
+source_file = source/locale/pot/virtual_machines.pot
+source_lang = en
+
http://git-wip-us.apache.org/repos/asf/cloudstack-docs-admin/blob/65303ea3/Makefile
----------------------------------------------------------------------
diff --git a/Makefile b/Makefile
index 6253ea3..749816b 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-admin/blob/65303ea3/README.rst
----------------------------------------------------------------------
diff --git a/README.rst b/README.rst
index ef84521..227a6c8 100644
--- a/README.rst
+++ b/README.rst
@@ -24,6 +24,40 @@ Website
This administration guide is on-line at <http://cloudstack-administration.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-administration-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-admin/blob/65303ea3/source/locale/pot/accounts.pot
----------------------------------------------------------------------
diff --git a/source/locale/pot/accounts.pot b/source/locale/pot/accounts.pot
new file mode 100644
index 0000000..c7ed8fb
--- /dev/null
+++ b/source/locale/pot/accounts.pot
@@ -0,0 +1,409 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C)
+# This file is distributed under the same license as the Apache CloudStack Administration Documentation package.
+# FIRST AUTHOR <EM...@ADDRESS>, YEAR.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: Apache CloudStack Administration Documentation 4\n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2014-03-31 14:08-0400\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EM...@ADDRESS>\n"
+"Language-Team: LANGUAGE <LL...@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#: ../../accounts.rst:18
+# 90951daa147540dab10f9d0c78d8c73b
+msgid "Managing Accounts, Users and Domains"
+msgstr ""
+
+#: ../../accounts.rst:21
+# 661635f04f94452db5ca9e4dd563cef7
+msgid "Accounts, Users, and Domains"
+msgstr ""
+
+#: ../../accounts.rst:24
+# a7494e04f72d469a86f3c67e958ed65f
+msgid "Accounts"
+msgstr ""
+
+#: ../../accounts.rst:26
+# 457dea8dff534d9aa75e2270c1e1ac6d
+msgid "An account typically represents a customer of the service provider or a department in a large organization. Multiple users can exist in an account."
+msgstr ""
+
+#: ../../accounts.rst:31
+# b45cd9ee7d3e478cbb3c129943ce53d5
+msgid "Domains"
+msgstr ""
+
+#: ../../accounts.rst:33
+# 10ebf41c7dbf4e65b1be24934d043965
+msgid "Accounts are grouped by domains. Domains usually contain multiple accounts that have some logical relationship to each other and a set of delegated administrators with some authority over the domain and its subdomains. For example, a service provider with several resellers could create a domain for each reseller."
+msgstr ""
+
+#: ../../accounts.rst:39
+# 403c3bff584f41c6b9ee1d4ba5bc6241
+msgid "For each account created, the Cloud installation creates three different types of user accounts: root administrator, domain administrator, and user."
+msgstr ""
+
+#: ../../accounts.rst:44
+# 65e0965c3efe4beb825b48109a593375
+msgid "Users"
+msgstr ""
+
+#: ../../accounts.rst:46
+# 34892ebe1c424238b2d30be07cfbef77
+msgid "Users are like aliases in the account. Users in the same account are not isolated from each other, but they are isolated from users in other accounts. Most installations need not surface the notion of users; they just have one user per account. The same user cannot belong to multiple accounts."
+msgstr ""
+
+#: ../../accounts.rst:52
+# 31c0da272edb4413bba06570446855e5
+msgid "Username is unique in a domain across accounts in that domain. The same username can exist in other domains, including sub-domains. Domain name can repeat only if the full pathname from root is unique. For example, you can create root/d1, as well as root/foo/d1, and root/sales/d1."
+msgstr ""
+
+#: ../../accounts.rst:57
+# 1754108df51d4b9aa2bfcab98e1b9bf0
+msgid "Administrators are accounts with special privileges in the system. There may be multiple administrators in the system. Administrators can create or delete other administrators, and change the password for any user in the system."
+msgstr ""
+
+#: ../../accounts.rst:63
+# 12ec03346ad2491195e691d8d6e3139b
+msgid "Domain Administrators"
+msgstr ""
+
+#: ../../accounts.rst:65
+# 14a1bb86d2624ad3b4c82731fa8dd170
+msgid "Domain administrators can perform administrative operations for users who belong to that domain. Domain administrators do not have visibility into physical servers or other domains."
+msgstr ""
+
+#: ../../accounts.rst:70
+# 39f193590cb5492691994021f7591f2e
+msgid "Root Administrator"
+msgstr ""
+
+#: ../../accounts.rst:72
+# 97d51f9ba69843b5af3c3770b5e6a41d
+msgid "Root administrators have complete access to the system, including managing templates, service offerings, customer care administrators, and domains"
+msgstr ""
+
+#: ../../accounts.rst:77
+# 0231216736c74923a934181f66c7be6d
+msgid "Resource Ownership"
+msgstr ""
+
+#: ../../accounts.rst:79
+# 72eb8676abfd416cb9bbb177a3de84f6
+msgid "Resources belong to the account, not individual users in that account. For example, billing, resource limits, and so on are maintained by the account, not the users. A user can operate on any resource in the account provided the user has privileges for that operation. The privileges are determined by the role. A root administrator can change the ownership of any virtual machine from one account to any other account by using the assignVirtualMachine API. A domain or sub-domain administrator can do the same for VMs within the domain from one account to any other account in the domain or any of its sub-domains."
+msgstr ""
+
+#: ../../accounts.rst:90
+# ff5d0b1e1c574c599f7af2c724e6fed1
+msgid "Dedicating Resources to Accounts and Domains"
+msgstr ""
+
+#: ../../accounts.rst:92
+# 0a4bdfeefcbc4e6b90e29d85882276e5
+msgid "The root administrator can dedicate resources to a specific domain or account that needs private infrastructure for additional security or performance guarantees. A zone, pod, cluster, or host can be reserved by the root administrator for a specific domain or account. Only users in that domain or its subdomain may use the infrastructure. For example, only users in a given domain can create guests in a zone dedicated to that domain."
+msgstr ""
+
+#: ../../accounts.rst:100
+# d6b26e49ebc04db7bc3a577de66cada3
+msgid "There are several types of dedication available:"
+msgstr ""
+
+#: ../../accounts.rst:104
+# dac518c9d097412c8fc411ea7ed6a9e7
+msgid "Explicit dedication. A zone, pod, cluster, or host is dedicated to an account or domain by the root administrator during initial deployment and configuration."
+msgstr ""
+
+#: ../../accounts.rst:110
+# 574012d1f1984a9a8d7a720f9ea1c4d6
+msgid "Strict implicit dedication. A host will not be shared across multiple accounts. For example, strict implicit dedication is useful for deployment of certain types of applications, such as desktops, where no host can be shared between different accounts without violating the desktop software's terms of license."
+msgstr ""
+
+#: ../../accounts.rst:118
+# a5988bb1ccf4413394ead18a5bf8d2b4
+msgid "Preferred implicit dedication. The VM will be deployed in dedicated infrastructure if possible. Otherwise, the VM can be deployed in shared infrastructure."
+msgstr ""
+
+#: ../../accounts.rst:123
+# 599bcac969ab4007b46f4a44e3aab507
+msgid "How to Dedicate a Zone, Cluster, Pod, or Host to an Account or Domain"
+msgstr ""
+
+#: ../../accounts.rst:125
+# 235f58f9b9bd48eab66c66dc94d93e40
+msgid "For explicit dedication: When deploying a new zone, pod, cluster, or host, the root administrator can click the Dedicated checkbox, then choose a domain or account to own the resource."
+msgstr ""
+
+#: ../../accounts.rst:129
+# 99189fbc5d704126a534a43918bd1cc9
+msgid "To explicitly dedicate an existing zone, pod, cluster, or host: log in as the root admin, find the resource in the UI, and click the Dedicate button. |button to dedicate a zone, pod,cluster, or host|"
+msgstr ""
+
+#: ../../accounts.rst:133
+# e7ebf6fbd7d048bf822061139e2b5a4c
+msgid "For implicit dedication: The administrator creates a compute service offering and in the Deployment Planner field, chooses ImplicitDedicationPlanner. Then in Planner Mode, the administrator specifies either Strict or Preferred, depending on whether it is permissible to allow some use of shared resources when dedicated resources are not available. Whenever a user creates a VM based on this service offering, it is allocated on one of the dedicated hosts."
+msgstr ""
+
+#: ../../accounts.rst:142
+# 57e1c25d97df4d22b88b35dc599e45f7
+msgid "How to Use Dedicated Hosts"
+msgstr ""
+
+#: ../../accounts.rst:144
+# b227acf3ae06498d99b21119713e2238
+msgid "To use an explicitly dedicated host, use the explicit-dedicated type of affinity group (see `“Affinity Groups” <virtual_machines.html#affinity-groups>`_). For example, when creating a new VM, an end user can choose to place it on dedicated infrastructure. This operation will succeed only if some infrastructure has already been assigned as dedicated to the user's account or domain."
+msgstr ""
+
+#: ../../accounts.rst:152
+# f9c5cb26d6904347ad48d4ceba1481a6
+msgid "Behavior of Dedicated Hosts, Clusters, Pods, and Zones"
+msgstr ""
+
+#: ../../accounts.rst:154
+# 05b28e9607634f78abda79633a1403cf
+msgid "The administrator can live migrate VMs away from dedicated hosts if desired, whether the destination is a host reserved for a different account/domain or a host that is shared (not dedicated to any particular account or domain). CloudStack will generate an alert, but the operation is allowed."
+msgstr ""
+
+#: ../../accounts.rst:160
+# ce25fc9a198a4cbeaabd2e2405325e9c
+msgid "Dedicated hosts can be used in conjunction with host tags. If both a host tag and dedication are requested, the VM will be placed only on a host that meets both requirements. If there is no dedicated resource available to that user that also has the host tag requested by the user, then the VM will not deploy."
+msgstr ""
+
+#: ../../accounts.rst:166
+# aeb33b23037c45be909c3768cc8966b6
+msgid "If you delete an account or domain, any hosts, clusters, pods, and zones that were dedicated to it are freed up. They will now be available to be shared by any account or domain, or the administrator may choose to re-dedicate them to a different account or domain."
+msgstr ""
+
+#: ../../accounts.rst:171
+# 1ce4e0516a79477a817eb0619fbfb51e
+msgid "System VMs and virtual routers affect the behavior of host dedication. System VMs and virtual routers are owned by the CloudStack system account, and they can be deployed on any host. They do not adhere to explicit dedication. The presence of system vms and virtual routers on a host makes it unsuitable for strict implicit dedication. The host can not be used for strict implicit dedication, because the host already has VMs of a specific account (the default system account). However, a host with system VMs or virtual routers can be used for preferred implicit dedication."
+msgstr ""
+
+#: ../../accounts.rst:182
+# ad8c17e1de7c4cb4af2c8b55ee0a851c
+msgid "Using an LDAP Server for User Authentication"
+msgstr ""
+
+#: ../../accounts.rst:184
+# d3eb07c14a05493ba2ff39ea53010821
+msgid "You can use an external LDAP server such as Microsoft Active Directory or ApacheDS to authenticate CloudStack end-users. Just map CloudStack accounts to the corresponding LDAP accounts using a query filter. The query filter is written using the query syntax of the particular LDAP server, and can include special wildcard characters provided by CloudStack for matching common values such as the user’s email address and name. CloudStack will search the external LDAP directory tree starting at a specified base directory and return the distinguished name (DN) and password of the matching user. This information along with the given password is used to authenticate the user.."
+msgstr ""
+
+#: ../../accounts.rst:195
+# efbc795d47b644b592c065f9221a5ecc
+msgid "To set up LDAP authentication in CloudStack, call the CloudStack API command ldapConfig and provide the following:"
+msgstr ""
+
+#: ../../accounts.rst:200
+# 7826c9574e864a3fa3927d2452d6f247
+msgid "Hostname or IP address and listening port of the LDAP server"
+msgstr ""
+
+#: ../../accounts.rst:204
+# 70b92e095a0749628ec280152921d951
+msgid "Base directory and query filter"
+msgstr ""
+
+#: ../../accounts.rst:208
+# 4fe250c5d3ac44ab883b8c10af24f1fe
+msgid "Search user DN credentials, which give CloudStack permission to search on the LDAP server"
+msgstr ""
+
+#: ../../accounts.rst:213
+# 2ceaa9828892484ebd391520d745991d
+msgid "SSL keystore and password, if SSL is used"
+msgstr ""
+
+#: ../../accounts.rst:216
+# 26d8fb1d67a74f8387452da5b3cce675
+msgid "Example LDAP Configuration Commands"
+msgstr ""
+
+#: ../../accounts.rst:218
+# 1c19000335be4f7ebdab1d79a7c4658c
+msgid "To understand the examples in this section, you need to know the basic concepts behind calling the CloudStack API, which are explained in the Developer’s Guide."
+msgstr ""
+
+#: ../../accounts.rst:222
+# d7aafed8ded6431d8129d3bbe41769aa
+msgid "The following shows an example invocation of ldapConfig with an ApacheDS LDAP server"
+msgstr ""
+
+#: ../../accounts.rst:229
+# 7214405299e94877a1c09f6c6287ee10
+msgid "The command must be URL-encoded. Here is the same example without the URL encoding:"
+msgstr ""
+
+#: ../../accounts.rst:247
+# 74c45748c7614774911829b534605cc1
+msgid "The following shows a similar command for Active Directory. Here, the search base is the testing group within a company, and the users are matched up based on email address."
+msgstr ""
+
+#: ../../accounts.rst:255
+# e42d0dbce6674c9ba00d73998fb30e71
+msgid "The next few sections explain some of the concepts you will need to know when filling out the ldapConfig parameters."
+msgstr ""
+
+#: ../../accounts.rst:259
+# a47324fc43df41cdbcae97f676f2536f
+msgid "Search Base"
+msgstr ""
+
+#: ../../accounts.rst:261
+# f44d14b0d741402087e0cc706bbb068e
+msgid "An LDAP query is relative to a given node of the LDAP directory tree, called the search base. The search base is the distinguished name (DN) of a level of the directory tree below which all users can be found. The users can be in the immediate base directory or in some subdirectory. The search base may be equivalent to the organization, group, or domain name. The syntax for writing a DN varies depending on which LDAP server you are using. A full discussion of distinguished names is outside the scope of our documentation. The following table shows some examples of search bases to find users in the testing department.."
+msgstr ""
+
+#: ../../accounts.rst:272
+#: ../../accounts.rst:328
+# c824c6d3616243eaa848cc45808ec373
+# 46c8c55831674fd3a12caa7352108fa4
+msgid "LDAP Server"
+msgstr ""
+
+#: ../../accounts.rst:272
+# bf34c451c0994186b556742324006c30
+msgid "Example Search Base DN"
+msgstr ""
+
+#: ../../accounts.rst:274
+#: ../../accounts.rst:330
+# c6940ea324fb4c99895c4d2152bfd32e
+# 359bafef7f4044e380b30643767ad285
+msgid "ApacheDS"
+msgstr ""
+
+#: ../../accounts.rst:274
+# 2253d38b2ae84eeab805635117cf368c
+msgid "OU=testing, O=project"
+msgstr ""
+
+#: ../../accounts.rst:275
+#: ../../accounts.rst:331
+# ddf11f35901948058a34dff9cbca8c3d
+# 6d6eab10b7674a65aedf6c1f41312bf8
+msgid "Active Directory"
+msgstr ""
+
+#: ../../accounts.rst:275
+# 0fdc037b3c2746e0b455bd0594bf0bee
+msgid "OU=testing, DC=company"
+msgstr ""
+
+#: ../../accounts.rst:279
+# 03d46aff89114039bebeeea32fbcda86
+msgid "Query Filter"
+msgstr ""
+
+#: ../../accounts.rst:281
+# 93b867a441bc4cddad5a72d6b9e51abf
+msgid "The query filter is used to find a mapped user in the external LDAP server. The query filter should uniquely map the CloudStack user to LDAP user for a meaningful authentication. For more information about query filter syntax, consult the documentation for your LDAP server."
+msgstr ""
+
+#: ../../accounts.rst:286
+# 94920970089b494395b1e5410ad30bb1
+msgid "The CloudStack query filter wildcards are:"
+msgstr ""
+
+#: ../../accounts.rst:289
+# f7c82cdd777a4284b5adc6a920065f32
+msgid "Query Filter Wildcard"
+msgstr ""
+
+#: ../../accounts.rst:289
+# 2e1c45a30d2648c6878074583a6a4c7b
+msgid "Description"
+msgstr ""
+
+#: ../../accounts.rst:291
+# b636b6a26b4942d390e3083bb99636ec
+msgid "%u"
+msgstr ""
+
+#: ../../accounts.rst:291
+# b85fa10a6f7c473f9579fbee87abc7dc
+msgid "User name"
+msgstr ""
+
+#: ../../accounts.rst:292
+# aaca04ef47ce4a6d957d7f999021beec
+msgid "%e"
+msgstr ""
+
+#: ../../accounts.rst:292
+# 04104fb07bb94de38b10667d6fdadf04
+msgid "Email address"
+msgstr ""
+
+#: ../../accounts.rst:293
+# ae0690d61f774148a22980a6ed2d4c98
+msgid "%n"
+msgstr ""
+
+#: ../../accounts.rst:293
+# 5c8df2d1e58b4c88b7f6f76691f54e32
+msgid "First and last name"
+msgstr ""
+
+#: ../../accounts.rst:296
+# fb24e5d77b0b4a369c988a18859c27b5
+msgid "The following examples assume you are using Active Directory, and refer to user attributes from the Active Directory schema."
+msgstr ""
+
+#: ../../accounts.rst:299
+# 53d9ff57793f490ea016d5c0dd2235e1
+msgid "If the CloudStack user name is the same as the LDAP user ID:"
+msgstr ""
+
+#: ../../accounts.rst:305
+# fe9b3901fa4c442dbba0966d900dc335
+msgid "If the CloudStack user name is the LDAP display name:"
+msgstr ""
+
+#: ../../accounts.rst:311
+# 67bfee8945324987bfa2debd1cbd0f29
+msgid "To find a user by email address:"
+msgstr ""
+
+#: ../../accounts.rst:318
+# 0a2a4f3d28a447ccafdcade93acec26e
+msgid "Search User Bind DN"
+msgstr ""
+
+#: ../../accounts.rst:320
+# 9d07ca9ffe4d45e1a14848570aad2f64
+msgid "The bind DN is the user on the external LDAP server permitted to search the LDAP directory within the defined search base. When the DN is returned, the DN and passed password are used to authenticate the CloudStack user with an LDAP bind. A full discussion of bind DNs is outside the scope of our documentation. The following table shows some examples of bind DNs."
+msgstr ""
+
+#: ../../accounts.rst:328
+# 3b0b6b5b036945e6bb5442cb94a46fcd
+msgid "Example Bind DN"
+msgstr ""
+
+#: ../../accounts.rst:330
+# 1cd4f20b644c4fd68eb8a37ef35f7b47
+msgid "CN=Administrator,DC=testing,OU=project,OU=org"
+msgstr ""
+
+#: ../../accounts.rst:331
+# 2e60a99cfddd494c9de480a48304dfe3
+msgid "CN=Administrator, OU=testing, DC=company, DC=com"
+msgstr ""
+
+#: ../../accounts.rst:336
+# 16cd1707b0594271ae8a6ae3884ec80e
+msgid "SSL Keystore Path and Password"
+msgstr ""
+
+#: ../../accounts.rst:338
+# 074f3d04369241be9e56096bb7dded79
+msgid "If the LDAP server requires SSL, you need to enable it in the ldapConfig command by setting the parameters ssl, truststore, and truststorepass. Before enabling SSL for ldapConfig, you need to get the certificate which the LDAP server is using and add it to a trusted keystore. You will need to know the path to the keystore and the password."
+msgstr ""
+
http://git-wip-us.apache.org/repos/asf/cloudstack-docs-admin/blob/65303ea3/source/locale/pot/administration.pot
----------------------------------------------------------------------
diff --git a/source/locale/pot/administration.pot b/source/locale/pot/administration.pot
new file mode 100644
index 0000000..a70fd94
--- /dev/null
+++ b/source/locale/pot/administration.pot
@@ -0,0 +1,63 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C)
+# This file is distributed under the same license as the Apache CloudStack Administration Documentation package.
+# FIRST AUTHOR <EM...@ADDRESS>, YEAR.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: Apache CloudStack Administration Documentation 4\n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2014-03-31 14:08-0400\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EM...@ADDRESS>\n"
+"Language-Team: LANGUAGE <LL...@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#: ../../administration.rst:19
+# 5782522e7a564a9caa1ecc02e0977696
+msgid "User Services"
+msgstr ""
+
+#: ../../administration.rst:21
+# 06114f8c3f954e45b8add1ef10ed3f6e
+msgid "In addition to the physical and logical infrastructure of your cloud and the CloudStack software and servers, you also need a layer of user services so that people can actually make use of the cloud. This means not just a user UI, but a set of options and resources that users can choose from, such as templates for creating virtual machines, disk storage, and more. If you are running a commercial service, you will be keeping track of what services and resources users are consuming and charging them for that usage. Even if you do not charge anything for people to use your cloud – say, if the users are strictly internal to your organization, or just friends who are sharing your cloud – you can still keep track of what services they use and how much of them."
+msgstr ""
+
+#: ../../administration.rst:34
+# 08b7862dbeb64d2d8c3e46cacc0a995d
+msgid "Service Offerings, Disk Offerings, Network Offerings, and Templates"
+msgstr ""
+
+#: ../../administration.rst:36
+# f761dfbfdddc4df58bc4fb22ad4c4ada
+msgid "A user creating a new instance can make a variety of choices about its characteristics and capabilities. CloudStack provides several ways to present users with choices when creating a new instance:"
+msgstr ""
+
+#: ../../administration.rst:42
+# 46491c0220454387a6a1eaf3e9c62f68
+msgid "Service Offerings, defined by the CloudStack administrator, provide a choice of CPU speed, number of CPUs, RAM size, tags on the root disk, and other choices. See Creating a New Compute Offering."
+msgstr ""
+
+#: ../../administration.rst:48
+# 2739214a038842799d6315fc83f2d7b9
+msgid "Disk Offerings, defined by the CloudStack administrator, provide a choice of disk size and IOPS (Quality of Service) for primary data storage. See Creating a New Disk Offering."
+msgstr ""
+
+#: ../../administration.rst:54
+# 7b90ec0921524642a75fc2610c86c276
+msgid "Network Offerings, defined by the CloudStack administrator, describe the feature set that is available to end users from the virtual router or external networking devices on a given guest network. See Network Offerings."
+msgstr ""
+
+#: ../../administration.rst:61
+# b5a2bc83e71142d2b6133c4d6266cab9
+msgid "Templates, defined by the CloudStack administrator or by any CloudStack user, are the base OS images that the user can choose from when creating a new instance. For example, CloudStack includes CentOS as a template. See Working with Templates."
+msgstr ""
+
+#: ../../administration.rst:66
+# 2e2f04a2e3e449698ca4be2d9d1215fb
+msgid "In addition to these choices that are provided for users, there is another type of service offering which is available only to the CloudStack root administrator, and is used for configuring virtual infrastructure resources. For more information, see Upgrading a Virtual Router with System Service Offerings."
+msgstr ""
+
http://git-wip-us.apache.org/repos/asf/cloudstack-docs-admin/blob/65303ea3/source/locale/pot/api.pot
----------------------------------------------------------------------
diff --git a/source/locale/pot/api.pot b/source/locale/pot/api.pot
new file mode 100644
index 0000000..efa4adf
--- /dev/null
+++ b/source/locale/pot/api.pot
@@ -0,0 +1,123 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C)
+# This file is distributed under the same license as the Apache CloudStack Administration Documentation package.
+# FIRST AUTHOR <EM...@ADDRESS>, YEAR.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: Apache CloudStack Administration Documentation 4\n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2014-03-31 14:08-0400\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EM...@ADDRESS>\n"
+"Language-Team: LANGUAGE <LL...@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#: ../../api.rst:18
+# c9f373cc299e447998a4b0c51d6b30e1
+msgid "CloudStack API"
+msgstr ""
+
+#: ../../api.rst:20
+# 4f31f79497784c4eb83f19285c8fc8d4
+msgid "The CloudStack API is a low level API that has been used to implement the CloudStack web UIs. It is also a good basis for implementing other popular APIs such as EC2/S3 and emerging DMTF standards."
+msgstr ""
+
+#: ../../api.rst:24
+# 0484938f098f467e94ea20aa2d3de1f0
+msgid "Many CloudStack API calls are asynchronous. These will return a Job ID immediately when called. This Job ID can be used to query the status of the job later. Also, status calls on impacted resources will provide some indication of their state."
+msgstr ""
+
+#: ../../api.rst:29
+# 59bb256e7c6841a89ab8fd907a34f08a
+msgid "The API has a REST-like query basis and returns results in XML or JSON."
+msgstr ""
+
+#: ../../api.rst:31
+# 3f40f7f90a3b4dd2a8b4ddbb30340800
+msgid "See `the Developer’s Guide <https://cwiki.apache.org/confluence/display/CLOUDSTACK/Development+101>`_ and `the API Reference <http://cloudstack.apache.org/docs/api/>`_."
+msgstr ""
+
+#: ../../api.rst:35
+# 850a1709dc05430b81c947813bf2c387
+msgid "Provisioning and Authentication API"
+msgstr ""
+
+#: ../../api.rst:37
+# 4b899aee7aa147bbb8cbe8cc3fdd3436
+msgid "CloudStack expects that a customer will have their own user provisioning infrastructure. It provides APIs to integrate with these existing systems where the systems call out to CloudStack to add/remove users.."
+msgstr ""
+
+#: ../../api.rst:41
+# d1809ac4f63b4171bd2bf7449f9af520
+msgid "CloudStack supports pluggable authenticators. By default, CloudStack assumes it is provisioned with the user’s password, and as a result authentication is done locally. However, external authentication is possible as well. For example, see Using an LDAP Server for User Authentication."
+msgstr ""
+
+#: ../../api.rst:48
+# e0f1a61ca7404d2fbe4cfa7a466e23a6
+msgid "User Data and Meta Data"
+msgstr ""
+
+#: ../../api.rst:50
+# 4921f2bf02984bc0a308cc391af4cabf
+msgid "CloudStack provides API access to attach up to 32KB of user data to a deployed VM. Deployed VMs also have access to instance metadata via the virtual router."
+msgstr ""
+
+#: ../../api.rst:54
+# 076533995e0345db90168c6278c3460b
+msgid "User data can be accessed once the IP address of the virtual router is known. Once the IP address is known, use the following steps to access the user data:"
+msgstr ""
+
+#: ../../api.rst:58
+# cf43f38848f845f4a34393092ae8b81e
+msgid "Run the following command to find the virtual router."
+msgstr ""
+
+#: ../../api.rst:64
+# 6fff13e87cff49809caebf13b8fa61cb
+msgid "Access user data by running the following command using the result of the above command"
+msgstr ""
+
+#: ../../api.rst:71
+# cd37cb5d158343c29780503c5bca4540
+msgid "Meta Data can be accessed similarly, using a URL of the form http://10.1.1.1/latest/meta-data/{metadata type}. (For backwards compatibility, the previous URL http://10.1.1.1/latest/{metadata type} is also supported.) For metadata type, use one of the following:"
+msgstr ""
+
+#: ../../api.rst:78
+# e84e13e6d81f41fda2e53325bcf8196b
+msgid "service-offering. A description of the VMs service offering"
+msgstr ""
+
+#: ../../api.rst:82
+# 62048249f8d2494db34980c3b1862e5b
+msgid "availability-zone. The Zone name"
+msgstr ""
+
+#: ../../api.rst:86
+# 7463be88f12e49e8aac8925ca6a5884f
+msgid "local-ipv4. The guest IP of the VM"
+msgstr ""
+
+#: ../../api.rst:90
+# ba16b21040764726a1202dde1d4e83d6
+msgid "local-hostname. The hostname of the VM"
+msgstr ""
+
+#: ../../api.rst:94
+# 363adc60e20b4bfcb51004281919f11e
+msgid "public-ipv4. The first public IP for the router. (E.g. the first IP of eth2)"
+msgstr ""
+
+#: ../../api.rst:99
+# 352781028d6f46f1b95f08adccbb1ff2
+msgid "public-hostname. This is the same as public-ipv4"
+msgstr ""
+
+#: ../../api.rst:103
+# dc787ff8567442788d44cf46ab9a6462
+msgid "instance-id. The instance name of the VM"
+msgstr ""
+
http://git-wip-us.apache.org/repos/asf/cloudstack-docs-admin/blob/65303ea3/source/locale/pot/events.pot
----------------------------------------------------------------------
diff --git a/source/locale/pot/events.pot b/source/locale/pot/events.pot
new file mode 100644
index 0000000..57799bc
--- /dev/null
+++ b/source/locale/pot/events.pot
@@ -0,0 +1,332 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C)
+# This file is distributed under the same license as the Apache CloudStack Administration Documentation package.
+# FIRST AUTHOR <EM...@ADDRESS>, YEAR.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: Apache CloudStack Administration Documentation 4\n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2014-03-31 14:08-0400\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EM...@ADDRESS>\n"
+"Language-Team: LANGUAGE <LL...@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#: ../../events.rst:18
+# 102ed2ffb3fb4c3bb6029d0c7eb905de
+msgid "Event Notification"
+msgstr ""
+
+#: ../../events.rst:20
+# afc241a8b0d0496a8744768e3563fbe8
+msgid "An event is essentially a significant or meaningful change in the state of both virtual and physical resources associated with a cloud environment. Events are used by monitoring systems, usage and billing systems, or any other event-driven workflow systems to discern a pattern and make the right business decision. In CloudStack an event could be a state change of virtual or physical resources, an action performed by an user (action events), or policy based events (alerts)."
+msgstr ""
+
+#: ../../events.rst:29
+# 0fca00203fea49669148771eeedf55c3
+msgid "Event Logs"
+msgstr ""
+
+#: ../../events.rst:31
+# 1d21fa8ae81748baa8e52f31043facf7
+msgid "There are two types of events logged in the CloudStack Event Log. Standard events log the success or failure of an event and can be used to identify jobs or processes that have failed. There are also long running job events. Events for asynchronous jobs log when a job is scheduled, when it starts, and when it completes. Other long running synchronous jobs log when a job starts, and when it completes. Long running synchronous and asynchronous event logs can be used to gain more information on the status of a pending job or can be used to identify a job that is hanging or has not started. The following sections provide more information on these events.."
+msgstr ""
+
+#: ../../events.rst:43
+# 8a0c6176934d4aec840789a07a73084b
+msgid "Notification"
+msgstr ""
+
+#: ../../events.rst:45
+# 64816315eaa145ab8ad138648b2589e3
+msgid "Event notification framework provides a means for the Management Server components to publish and subscribe to CloudStack events. Event notification is achieved by implementing the concept of event bus abstraction in the Management Server. An event bus is introduced in the Management Server that allows the CloudStack components and extension plug-ins to subscribe to the events by using the Advanced Message Queuing Protocol (AMQP) client. In CloudStack, a default implementation of event bus is provided as a plug-in that uses the RabbitMQ AMQP client. The AMQP client pushes the published events to a compatible AMQP server. Therefore all the CloudStack events are published to an exchange in the AMQP server."
+msgstr ""
+
+#: ../../events.rst:57
+# 69559e28bd3c4833a65e235470bd7ae9
+msgid "A new event for state change, resource state change, is introduced as part of Event notification framework. Every resource, such as user VM, volume, NIC, network, public IP, snapshot, and template, is associated with a state machine and generates events as part of the state change. That implies that a change in the state of a resource results in a state change event, and the event is published in the corresponding state machine on the event bus. All the CloudStack events (alerts, action events, usage events) and the additional category of resource state change events, are published on to the events bus."
+msgstr ""
+
+#: ../../events.rst:68
+# c7c4a9021bb94d0d8c8806bdc797abc7
+msgid "Use Cases"
+msgstr ""
+
+#: ../../events.rst:70
+# 2b32e72970d74bd3b50d67a5c2b25913
+msgid "The following are some of the use cases:"
+msgstr ""
+
+#: ../../events.rst:74
+# 785e64cd20c945e39b1fcd1248e29463
+msgid "Usage or Billing Engines: A third-party cloud usage solution can implement a plug-in that can connects to CloudStack to subscribe to CloudStack events and generate usage data. The usage data is consumed by their usage software."
+msgstr ""
+
+#: ../../events.rst:81
+# 697fd51abda3475fbec2bfb2cf48eeee
+msgid "AMQP plug-in can place all the events on the a message queue, then a AMQP message broker can provide topic-based notification to the subscribers."
+msgstr ""
+
+#: ../../events.rst:87
+# 13d4c3bf275446aca6afcc5f13b12aa3
+msgid "Publish and Subscribe notification service can be implemented as a pluggable service in CloudStack that can provide rich set of APIs for event notification, such as topics-based subscription and notification. Additionally, the pluggable service can deal with multi-tenancy, authentication, and authorization issues."
+msgstr ""
+
+#: ../../events.rst:94
+# 1aedf09c5c0b4effa9dd9117fcf5a102
+msgid "Configuration"
+msgstr ""
+
+#: ../../events.rst:96
+# 1520275479c3459fb8bb45890eae9935
+msgid "As a CloudStack administrator, perform the following one-time configuration to enable event notification framework. At run time no changes can control the behaviour."
+msgstr ""
+
+#: ../../events.rst:102
+# e80abe3d28594327a0464339d8818c44
+msgid "Open ``'componentContext.xml``."
+msgstr ""
+
+#: ../../events.rst:106
+# 9df0be28f95041d19f82142547b7265b
+msgid "Define a bean named ``eventNotificationBus`` as follows:"
+msgstr ""
+
+#: ../../events.rst:110
+# e46a3a197cc74df2a9eb8e5bd57ebf52
+msgid "name : Specify a name for the bean."
+msgstr ""
+
+#: ../../events.rst:114
+# b203c95bc9f44afc81fbb8980802291e
+msgid "server : The name or the IP address of the RabbitMQ AMQP server."
+msgstr ""
+
+#: ../../events.rst:118
+# 6e8c151c2dd847f1a2a160d97c119e86
+msgid "port : The port on which RabbitMQ server is running."
+msgstr ""
+
+#: ../../events.rst:122
+# 42911e580f7a4f6fa5b5be87551390cb
+msgid "username : The username associated with the account to access the RabbitMQ server."
+msgstr ""
+
+#: ../../events.rst:127
+# 887fd9bc57b548f382e1c635c3dbb8a0
+msgid "password : The password associated with the username of the account to access the RabbitMQ server."
+msgstr ""
+
+#: ../../events.rst:132
+# 4c518b7b80a941638553284affb8603e
+msgid "exchange : The exchange name on the RabbitMQ server where CloudStack events are published."
+msgstr ""
+
+#: ../../events.rst:135
+# f881113c3c1540c9a568b4bb01f37ff2
+msgid "A sample bean is given below:"
+msgstr ""
+
+#: ../../events.rst:148
+# c88f66382e86471fa752a96e8c286e51
+msgid "The ``eventNotificationBus`` bean represents the ``org.apache.cloudstack.mom.rabbitmq.RabbitMQEventBus`` class."
+msgstr ""
+
+#: ../../events.rst:153
+# 3c84696f04ae4ad58c0edfe8eee24a49
+msgid "Restart the Management Server."
+msgstr ""
+
+#: ../../events.rst:156
+# 34f2df7b30c8489690de80ca02292b43
+msgid "Standard Events"
+msgstr ""
+
+#: ../../events.rst:158
+#: ../../events.rst:191
+# 658ab70617ca480387c4446d2df3f783
+# e43e53282a8743bc94e7a3f26dacfeed
+msgid "The events log records three types of standard events."
+msgstr ""
+
+#: ../../events.rst:162
+#: ../../events.rst:195
+# 9400dae867ab48dfb95e9a05e8949fdb
+# cb299fcbd64849a7a47486675d1f6477
+msgid "INFO. This event is generated when an operation has been successfully performed."
+msgstr ""
+
+#: ../../events.rst:167
+#: ../../events.rst:200
+# 294607854e004c4fa685bb9760e11d2f
+# 26f912bd36f4415c9f6349109dbc880a
+msgid "WARN. This event is generated in the following circumstances."
+msgstr ""
+
+#: ../../events.rst:171
+#: ../../events.rst:204
+# 8f26ab07f1da41c5a67f35568dee82ae
+# a962175d5c794f9e88b25a995aa3fe1a
+msgid "When a network is disconnected while monitoring a template download."
+msgstr ""
+
+#: ../../events.rst:176
+#: ../../events.rst:209
+# 41d6341dfbc74296aebd0eff9602f59a
+# 9bdea7d661d140718fea5fda4ae30615
+msgid "When a template download is abandoned."
+msgstr ""
+
+#: ../../events.rst:180
+#: ../../events.rst:213
+# d2d6ebc19c2f42138e8698f89ee29c6f
+# 93031d47c5704fb383a9e8149b602855
+msgid "When an issue on the storage server causes the volumes to fail over to the mirror storage server."
+msgstr ""
+
+#: ../../events.rst:185
+#: ../../events.rst:218
+# 583a50a8c403401093490e43cbd95dfd
+# 52ea4911fdfe42a5af3cc9a97e48a987
+msgid "ERROR. This event is generated when an operation has not been successfully performed"
+msgstr ""
+
+#: ../../events.rst:189
+# 5b8500630feb40f4afb3b8f9e29a53a3
+msgid "Long Running Job Events"
+msgstr ""
+
+#: ../../events.rst:222
+# c379b57670384b0b9da909afafca7292
+msgid "Event Log Queries"
+msgstr ""
+
+#: ../../events.rst:224
+# 88a9f85fb3da4603bee07701eabb7806
+msgid "Database logs can be queried from the user interface. The list of events captured by the system includes:"
+msgstr ""
+
+#: ../../events.rst:229
+# cd15e4ae2eca4d55b7510293e7fd2bbd
+msgid "Virtual machine creation, deletion, and on-going management operations"
+msgstr ""
+
+#: ../../events.rst:234
+# 2df022a424dc41b699e1367171be2d50
+msgid "Virtual router creation, deletion, and on-going management operations"
+msgstr ""
+
+#: ../../events.rst:238
+# d36f900c99fb40fa94804d5e52af7822
+msgid "Template creation and deletion"
+msgstr ""
+
+#: ../../events.rst:242
+# 2e97521ac7be4b15b4892a30073bc966
+msgid "Network/load balancer rules creation and deletion"
+msgstr ""
+
+#: ../../events.rst:246
+# f59bcdcfa249464a800cad1cd97cfc0f
+msgid "Storage volume creation and deletion"
+msgstr ""
+
+#: ../../events.rst:250
+# 8bd53c90bb38449fbbadd472c0930466
+msgid "User login and logout"
+msgstr ""
+
+#: ../../events.rst:253
+# 1e928be3f4e54e8f8b6532879b4e5f7e
+msgid "Deleting and Archiving Events and Alerts"
+msgstr ""
+
+#: ../../events.rst:255
+# 13275df9c48f45ccba383ca172df3874
+msgid "CloudStack provides you the ability to delete or archive the existing alerts and events that you no longer want to implement. You can regularly delete or archive any alerts or events that you cannot, or do not want to resolve from the database."
+msgstr ""
+
+#: ../../events.rst:260
+# 1371e435af2d4271b9db506b9e5c40aa
+msgid "You can delete or archive individual alerts or events either directly by using the Quickview or by using the Details page. If you want to delete multiple alerts or events at the same time, you can use the respective context menu. You can delete alerts or events by category for a time period. For example, you can select categories such as **USER.LOGOUT**, **VM.DESTROY**, **VM.AG.UPDATE**, **CONFIGURATION.VALUE.EDI**, and so on. You can also view the number of events or alerts archived or deleted."
+msgstr ""
+
+#: ../../events.rst:269
+# c8695ccfaf37456c9fe6e0ec4d207a62
+msgid "In order to support the delete or archive alerts, the following global parameters have been added:"
+msgstr ""
+
+#: ../../events.rst:274
+# d437d10a6c5c4d4fac98d68635980067
+msgid "**alert.purge.delay**: The alerts older than specified number of days are purged. Set the value to 0 to never purge alerts automatically."
+msgstr ""
+
+#: ../../events.rst:279
+# 368c17d62d6043429befbae6871a04c0
+msgid "**alert.purge.interval**: The interval in seconds to wait before running the alert purge thread. The default is 86400 seconds (one day)."
+msgstr ""
+
+#: ../../events.rst:283
+# 57dd9b95bbcf4bfd87ebf5cbaef78931
+msgid "Archived alerts or events cannot be viewed in the UI or by using the API. They are maintained in the database for auditing or compliance purposes."
+msgstr ""
+
+#: ../../events.rst:288
+# ec3e8f0b43514403afc0a9e47f381c0c
+msgid "Permissions"
+msgstr ""
+
+#: ../../events.rst:290
+# 7db5396af5d24382a51e418ced931fff
+msgid "Consider the following:"
+msgstr ""
+
+#: ../../events.rst:294
+# 2814ee39c91e4c2e832d73a1a39839b5
+msgid "The root admin can delete or archive one or multiple alerts or events."
+msgstr ""
+
+#: ../../events.rst:299
+# 01be1c88e97f4e9eae1e310e28045ae2
+msgid "The domain admin or end user can delete or archive one or multiple events."
+msgstr ""
+
+#: ../../events.rst:303
+# 8d806f13fadd4080bae10069ad330bbc
+msgid "Procedure"
+msgstr ""
+
+#: ../../events.rst:307
+# 0670181e1983452ab571f7ae6ce4d594
+msgid "Log in as administrator to the CloudStack UI."
+msgstr ""
+
+#: ../../events.rst:311
+# 3ab15d176fec4a14a47ed28c4e81a0bc
+msgid "In the left navigation, click Events."
+msgstr ""
+
+#: ../../events.rst:315
+# 3dfc816afe4744f1a2b5aa030c3be966
+msgid "Perform either of the following:"
+msgstr ""
+
+#: ../../events.rst:319
+# 3308c260b9c8454bb6109c2b36420617
+msgid "To archive events, click Archive Events, and specify event type and date."
+msgstr ""
+
+#: ../../events.rst:324
+# 3563bec70a3f40aa9bfd26494bda8c93
+msgid "To archive events, click Delete Events, and specify event type and date."
+msgstr ""
+
+#: ../../events.rst:329
+# f0ab5197a41b478684c629f86f95fc12
+msgid "Click OK."
+msgstr ""
+
http://git-wip-us.apache.org/repos/asf/cloudstack-docs-admin/blob/65303ea3/source/locale/pot/hosts.pot
----------------------------------------------------------------------
diff --git a/source/locale/pot/hosts.pot b/source/locale/pot/hosts.pot
new file mode 100644
index 0000000..da72b99
--- /dev/null
+++ b/source/locale/pot/hosts.pot
@@ -0,0 +1,828 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C)
+# This file is distributed under the same license as the Apache CloudStack Administration Documentation package.
+# FIRST AUTHOR <EM...@ADDRESS>, YEAR.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: Apache CloudStack Administration Documentation 4\n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2014-03-31 14:08-0400\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EM...@ADDRESS>\n"
+"Language-Team: LANGUAGE <LL...@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#: ../../hosts.rst:18
+# 592d97db5d074967b8037886828bbbf7
+msgid "Working with Hosts"
+msgstr ""
+
+#: ../../hosts.rst:21
+# eb6157eff5a24266a1934dce1cc5c38e
+msgid "Adding Hosts"
+msgstr ""
+
+#: ../../hosts.rst:23
+# 8278623233e349e2bbe063bea7e23268
+msgid "Additional hosts can be added at any time to provide more capacity for guest VMs. For requirements and instructions, see `“Adding a Host” <http://docs.cloudstack.apache.org/projects/cloudstack-installation/en/latest/configuration.html#adding-a-host>`_."
+msgstr ""
+
+#: ../../hosts.rst:28
+# d13936e89f4e4d9ea480d52a5c693cab
+msgid "Scheduled Maintenance and Maintenance Mode for Hosts"
+msgstr ""
+
+#: ../../hosts.rst:30
+# c80faa4e959d4bf6a547b8898e582f71
+msgid "You can place a host into maintenance mode. When maintenance mode is activated, the host becomes unavailable to receive new guest VMs, and the guest VMs already running on the host are seamlessly migrated to another host not in maintenance mode. This migration uses live migration technology and does not interrupt the execution of the guest."
+msgstr ""
+
+#: ../../hosts.rst:37
+# 050155d6fe2d4fe9bfb03ae737991f51
+msgid "vCenter and Maintenance Mode"
+msgstr ""
+
+#: ../../hosts.rst:39
+# 6e6dd514ac534a609dbba7282dd7d14e
+msgid "To enter maintenance mode on a vCenter host, both vCenter and CloudStack must be used in concert. CloudStack and vCenter have separate maintenance modes that work closely together."
+msgstr ""
+
+#: ../../hosts.rst:45
+# 1e1a327f506545d588b5c2dac6a6be66
+msgid "Place the host into CloudStack's \"scheduled maintenance\" mode. This does not invoke the vCenter maintenance mode, but only causes VMs to be migrated off the host"
+msgstr ""
+
+#: ../../hosts.rst:49
+# 10b6ab6a7f494f5e8df3db13ccfd3af8
+msgid "When the CloudStack maintenance mode is requested, the host first moves into the Prepare for Maintenance state. In this state it cannot be the target of new guest VM starts. Then all VMs will be migrated off the server. Live migration will be used to move VMs off the host. This allows the guests to be migrated to other hosts with no disruption to the guests. After this migration is completed, the host will enter the Ready for Maintenance mode."
+msgstr ""
+
+#: ../../hosts.rst:59
+# 1628c924f80a4f4e9f5becf74ad3f0ee
+msgid "Wait for the \"Ready for Maintenance\" indicator to appear in the UI."
+msgstr ""
+
+#: ../../hosts.rst:63
+# 4adef7c4df77454e8bd00237cd21e93c
+msgid "Now use vCenter to perform whatever actions are necessary to maintain the host. During this time, the host cannot be the target of new VM allocations."
+msgstr ""
+
+#: ../../hosts.rst:69
+# 7d67902696d54dba85c98361d7218cc4
+msgid "When the maintenance tasks are complete, take the host out of maintenance mode as follows:"
+msgstr ""
+
+#: ../../hosts.rst:74
+# a3f38b02fdc24e5e9b3c51227bb08fd7
+msgid "First use vCenter to exit the vCenter maintenance mode."
+msgstr ""
+
+#: ../../hosts.rst:76
+# d4f34ccb4d9b4a1bb09958fa5cf4de5e
+msgid "This makes the host ready for CloudStack to reactivate it."
+msgstr ""
+
+#: ../../hosts.rst:80
+# fc22d153282549d19896184eb37b2090
+msgid "Then use CloudStack's administrator UI to cancel the CloudStack maintenance mode"
+msgstr ""
+
+#: ../../hosts.rst:83
+# ce24285fd2e84a2d8e071223d9f7aa23
+msgid "When the host comes back online, the VMs that were migrated off of it may be migrated back to it manually and new VMs can be added."
+msgstr ""
+
+#: ../../hosts.rst:87
+# 1be609d82bc7437ab1f435f587dee885
+msgid "XenServer and Maintenance Mode"
+msgstr ""
+
+#: ../../hosts.rst:89
+# 4801359e1b504036a523926cb3083fcf
+msgid "For XenServer, you can take a server offline temporarily by using the Maintenance Mode feature in XenCenter. When you place a server into Maintenance Mode, all running VMs are automatically migrated from it to another host in the same pool. If the server is the pool master, a new master will also be selected for the pool. While a server is Maintenance Mode, you cannot create or start any VMs on it."
+msgstr ""
+
+#: ../../hosts.rst:96
+# 4a08aa70600a434a8cf5feeb551dd509
+msgid "**To place a server in Maintenance Mode:**"
+msgstr ""
+
+#: ../../hosts.rst:100
+#: ../../hosts.rst:123
+# f29fecea7fd547a4ac456396de215514
+# e5801557c9ac4721b34dd0390e57621f
+msgid "In the Resources pane, select the server, then do one of the following:"
+msgstr ""
+
+#: ../../hosts.rst:105
+# 1c753ac55dcb457ca6a65e85506faea1
+msgid "Right-click, then click Enter Maintenance Mode on the shortcut menu."
+msgstr ""
+
+#: ../../hosts.rst:110
+# 457c53ac36f14ed5a1f83bc59f41713a
+msgid "On the Server menu, click Enter Maintenance Mode."
+msgstr ""
+
+#: ../../hosts.rst:114
+# 8870ed34b2dc4486ac8f411a890d72c4
+msgid "Click Enter Maintenance Mode."
+msgstr ""
+
+#: ../../hosts.rst:116
+# 2433c930578741a1909765bc2bade385
+msgid "The server's status in the Resources pane shows when all running VMs have been successfully migrated off the server."
+msgstr ""
+
+#: ../../hosts.rst:119
+# 42be08f037604e5a9f47001de252d369
+msgid "**To take a server out of Maintenance Mode:**"
+msgstr ""
+
+#: ../../hosts.rst:128
+# f57ec4b8d883455d81686a1fd40f6160
+msgid "Right-click, then click Exit Maintenance Mode on the shortcut menu."
+msgstr ""
+
+#: ../../hosts.rst:133
+# 7d8e71c7ffbc4d71a75266dfba6b84df
+msgid "On the Server menu, click Exit Maintenance Mode."
+msgstr ""
+
+#: ../../hosts.rst:137
+# 8d0f538994db4767b7f9417b1cb41871
+msgid "Click Exit Maintenance Mode."
+msgstr ""
+
+#: ../../hosts.rst:140
+# bd837a82be2c48858847657c7b3cfdaa
+msgid "Disabling and Enabling Zones, Pods, and Clusters"
+msgstr ""
+
+#: ../../hosts.rst:142
+# 3aea5f5c94fc4404a3d7c5f194da767d
+msgid "You can enable or disable a zone, pod, or cluster without permanently removing it from the cloud. This is useful for maintenance or when there are problems that make a portion of the cloud infrastructure unreliable. No new allocations will be made to a disabled zone, pod, or cluster until its state is returned to Enabled. When a zone, pod, or cluster is first added to the cloud, it is Disabled by default."
+msgstr ""
+
+#: ../../hosts.rst:149
+# a9c8925bb2d04ecc9962de6fd0fbc1fd
+msgid "To disable and enable a zone, pod, or cluster:"
+msgstr ""
+
+#: ../../hosts.rst:153
+# 32c0489f474c4fecb77b83336097e9db
+msgid "Log in to the CloudStack UI as administrator"
+msgstr ""
+
+#: ../../hosts.rst:157
+#: ../../hosts.rst:447
+# 6b89d161130140ffbf2ccaee055008a3
+# 2f4cd598e62c47168a2ed22c6bec7674
+msgid "In the left navigation bar, click Infrastructure."
+msgstr ""
+
+#: ../../hosts.rst:161
+# 5ce0a640f1954756b46305873f389ad9
+msgid "In Zones, click View More."
+msgstr ""
+
+#: ../../hosts.rst:165
+# 3d333ceeab284ce5ad02f60c1fa67471
+msgid "If you are disabling or enabling a zone, find the name of the zone in the list, and click the Enable/Disable button. |enable-disable.png|"
+msgstr ""
+
+#: ../../hosts.rst:170
+# 0a4cfd78743b4e2c83066e46ce8464f8
+msgid "If you are disabling or enabling a pod or cluster, click the name of the zone that contains the pod or cluster."
+msgstr ""
+
+#: ../../hosts.rst:175
+# 0dc7b10cd00b48c1a2c77859a0cd940a
+msgid "Click the Compute tab."
+msgstr ""
+
+#: ../../hosts.rst:179
+# c7daddfdce6e4da6bb743f31b20c08df
+msgid "In the Pods or Clusters node of the diagram, click View All."
+msgstr ""
+
+#: ../../hosts.rst:183
+# 35005e277f71455ca42dd6d65bf92a77
+msgid "Click the pod or cluster name in the list."
+msgstr ""
+
+#: ../../hosts.rst:187
+# e96437e7b142420f990a2c0717d1e472
+msgid "Click the Enable/Disable button. |enable-disable.png|"
+msgstr ""
+
+#: ../../hosts.rst:190
+# 5ab36fe8716644fa8a74b1315198f7d3
+msgid "Removing Hosts"
+msgstr ""
+
+#: ../../hosts.rst:192
+# 2915247620714f17b21f9124f39d894e
+msgid "Hosts can be removed from the cloud as needed. The procedure to remove a host depends on the hypervisor type."
+msgstr ""
+
+#: ../../hosts.rst:196
+# 04254d2838064c639d5331ae3ffc4753
+msgid "Removing XenServer and KVM Hosts"
+msgstr ""
+
+#: ../../hosts.rst:198
+# eccc01ddbac946f9800dccea47e31ba9
+msgid "A node cannot be removed from a cluster until it has been placed in maintenance mode. This will ensure that all of the VMs on it have been migrated to other Hosts. To remove a Host from the cloud:"
+msgstr ""
+
+#: ../../hosts.rst:204
+# 82565e09d51041738069677fb128372d
+msgid "Place the node in maintenance mode."
+msgstr ""
+
+#: ../../hosts.rst:206
+# dd04ef23348a42fc815ff0a376123868
+msgid "See `“Scheduled Maintenance and Maintenance Mode for Hosts” <#scheduled-maintenance-and-maintenance-mode-for-hosts>`_."
+msgstr ""
+
+#: ../../hosts.rst:211
+# fed544dd8c474c2581684a87c9dae984
+msgid "For KVM, stop the cloud-agent service."
+msgstr ""
+
+#: ../../hosts.rst:215
+# 1f7547325d9a4881a6768dd009061aae
+msgid "Use the UI option to remove the node."
+msgstr ""
+
+#: ../../hosts.rst:217
+# f00eeb5fdaae4a9cbd1e36d610e270ac
+msgid "Then you may power down the Host, re-use its IP address, re-install it, etc"
+msgstr ""
+
+#: ../../hosts.rst:221
+# ae67d2137019437192ee7fbe0d451012
+msgid "Removing vSphere Hosts"
+msgstr ""
+
+#: ../../hosts.rst:223
+# b5b44fe095f645ed89753427c54c129e
+msgid "To remove this type of host, first place it in maintenance mode, as described in `“Scheduled Maintenance and Maintenance Mode for Hosts” <#scheduled-maintenance-and-maintenance-mode-for-hosts>`_. Then use CloudStack to remove the host. CloudStack will not direct commands to a host that has been removed using CloudStack. However, the host may still exist in the vCenter cluster."
+msgstr ""
+
+#: ../../hosts.rst:231
+# 2634c1aab86c49d6847a1cb6b9ca885d
+msgid "Re-Installing Hosts"
+msgstr ""
+
+#: ../../hosts.rst:233
+# 4a42ccaecda646bca2ac6ac89016ca33
+msgid "You can re-install a host after placing it in maintenance mode and then removing it. If a host is down and cannot be placed in maintenance mode, it should still be removed before the re-install."
+msgstr ""
+
+#: ../../hosts.rst:238
+# 65deb360368a4ef6aeac7a84cfe5c1ab
+msgid "Maintaining Hypervisors on Hosts"
+msgstr ""
+
+#: ../../hosts.rst:240
+# b927785c512c4eb79d94c141907bf453
+msgid "When running hypervisor software on hosts, 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 ""
+
+#: ../../hosts.rst:250
+# 6e001d3995a4461a98eb2c84399f8040
+msgid "The lack of up-do-date hotfixes can lead to data corruption and lost VMs."
+msgstr ""
+
+#: ../../hosts.rst:252
+# 24e34948fedb4eebaaa0b332c6b3ea55
+msgid "(XenServer) For more information, see `Highly Recommended Hotfixes for XenServer in the CloudStack Knowledge Base <http://docs.cloudstack.org/Knowledge_Base/Possible_VM_corruption_if_XenServer_Hotfix_is_not_Applied/Highly_Recommended_Hotfixes_for_XenServer_5.6_SP2>`_."
+msgstr ""
+
+#: ../../hosts.rst:255
+# e291026e0bcb4fc19c5f5ec67fb27962
+msgid "Changing Host Password"
+msgstr ""
+
+#: ../../hosts.rst:257
+# a2ecdc3bf4ea4777a754dbf829ae95cf
+msgid "The password for a XenServer Node, KVM Node, or vSphere Node may be changed in the database. Note that all Nodes in a Cluster must have the same password."
+msgstr ""
+
+#: ../../hosts.rst:261
+# 932a8d5023a3408bb325bb9976e78c9f
+msgid "To change a Node's password:"
+msgstr ""
+
+#: ../../hosts.rst:265
+# 02c81a7d530c40cfa1a6acfbdd7d7db5
+msgid "Identify all hosts in the cluster."
+msgstr ""
+
+#: ../../hosts.rst:269
+# 5493aaf270c04495a774d707812f6b71
+msgid "Change the password on all hosts in the cluster. Now the password for the host and the password known to CloudStack will not match. Operations on the cluster will fail until the two passwords match."
+msgstr ""
+
+#: ../../hosts.rst:275
+# 5a61d0b0dad244d5943f0f9a28393c34
+msgid "Get the list of host IDs for the host in the cluster where you are changing the password. You will need to access the database to determine these host IDs. For each hostname \"h\" (or vSphere cluster) that you are changing the password for, execute:"
+msgstr ""
+
+#: ../../hosts.rst:286
+# 6581ccaebb344383ac2fc40ddd20df3a
+msgid "This should return a single ID. Record the set of such IDs for these hosts."
+msgstr ""
+
+#: ../../hosts.rst:291
+# 081546910b424a93a45df2dee1cc04ca
+msgid "Update the passwords for the host in the database. In this example, we change the passwords for hosts with IDs 5, 10, and 12 to \"password\"."
+msgstr ""
+
+#: ../../hosts.rst:300
+# 08354d3af75c417c8f3bb81415fabd09
+msgid "Over-Provisioning and Service Offering Limits"
+msgstr ""
+
+#: ../../hosts.rst:302
+# a3bafa57323548dd9a6431f678eee017
+msgid "(Supported for XenServer, KVM, and VMware)"
+msgstr ""
+
+#: ../../hosts.rst:304
+# 0b69ea7e552248b1be401f196dfbb5d3
+msgid "CPU and memory (RAM) over-provisioning factors can be set for each cluster to change the number of VMs that can run on each host in the cluster. This helps optimize the use of resources. By increasing the over-provisioning ratio, more resource capacity will be used. If the ratio is set to 1, no over-provisioning is done."
+msgstr ""
+
+#: ../../hosts.rst:310
+# e80bfc39f5a24aec99fa634cef445579
+msgid "The administrator can also set global default over-provisioning ratios in the cpu.overprovisioning.factor and mem.overprovisioning.factor global configuration variables. The default value of these variables is 1: over-provisioning is turned off by default."
+msgstr ""
+
+#: ../../hosts.rst:315
+# 22e46dfef84e43f088ea1c9ba56b012b
+msgid "Over-provisioning ratios are dynamically substituted in CloudStack's capacity calculations. For example:"
+msgstr ""
+
+#: ../../hosts.rst:318
+# aeb35836bd204db3878f47e711625690
+msgid "Capacity = 2 GB Over-provisioning factor = 2 Capacity after over-provisioning = 4 GB"
+msgstr ""
+
+#: ../../hosts.rst:322
+# fb3b9278bc9d46c7a2c77e1f574c1151
+msgid "With this configuration, suppose you deploy 3 VMs of 1 GB each:"
+msgstr ""
+
+#: ../../hosts.rst:324
+# 9feabccde7a04110b98c75d65bdfb257
+msgid "Used = 3 GB Free = 1 GB"
+msgstr ""
+
+#: ../../hosts.rst:327
+# 5fb90dd3e25942db89cf99b12028bc9f
+msgid "The administrator can specify a memory over-provisioning ratio, and can specify both CPU and memory over-provisioning ratios on a per-cluster basis."
+msgstr ""
+
+#: ../../hosts.rst:331
+# 116d6bee32f044cbbd7e4da1d643e5b7
+msgid "In any given cloud, the optimum number of VMs for each host is affected by such things as the hypervisor, storage, and hardware configuration. These may be different for each cluster in the same cloud. A single global over-provisioning setting can not provide the best utilization for all the different clusters in the cloud. It has to be set for the lowest common denominator. The per-cluster setting provides a finer granularity for better utilization of resources, no matter where the CloudStack placement algorithm decides to place a VM."
+msgstr ""
+
+#: ../../hosts.rst:340
+# 52d81b5edf1e4675934e117fe3f7e39b
+msgid "The overprovisioning settings can be used along with dedicated resources (assigning a specific cluster to an account) to effectively offer different levels of service to different accounts. For example, an account paying for a more expensive level of service could be assigned to a dedicated cluster with an over-provisioning ratio of 1, and a lower-paying account to a cluster with a ratio of 2."
+msgstr ""
+
+#: ../../hosts.rst:347
+# c36163afa88548cfba86a4569c955329
+msgid "When a new host is added to a cluster, CloudStack will assume the host has the capability to perform the CPU and RAM over-provisioning which is configured for that cluster. It is up to the administrator to be sure the host is actually suitable for the level of over-provisioning which has been set."
+msgstr ""
+
+#: ../../hosts.rst:354
+# edc95af891bf48bf9348b06cd982309c
+msgid "Limitations on Over-Provisioning in XenServer and KVM"
+msgstr ""
+
+#: ../../hosts.rst:358
+#: ../../hosts.rst:465
+# cc00f5f645f64e0697ca6ebdd96d0def
+# fa75f18b499847fd8e2399cb4259df55
+msgid "In XenServer, due to a constraint of this hypervisor, you can not use an over-provisioning factor greater than 4."
+msgstr ""
+
+#: ../../hosts.rst:363
+# 0a8e4b3712eb41eb98132d75c64a88a7
+msgid "The KVM hypervisor can not manage memory allocation to VMs dynamically. CloudStack sets the minimum and maximum amount of memory that a VM can use. The hypervisor adjusts the memory within the set limits based on the memory contention."
+msgstr ""
+
+#: ../../hosts.rst:369
+# f2fe7c9bf6004d17af2fc11f9e60bcb5
+msgid "Requirements for Over-Provisioning"
+msgstr ""
+
+#: ../../hosts.rst:371
+# bee683fe8af6414ba2ce5829f1cce894
+msgid "Several prerequisites are required in order for over-provisioning to function properly. The feature is dependent on the OS type, hypervisor capabilities, and certain scripts. It is the administrator's responsibility to ensure that these requirements are met."
+msgstr ""
+
+#: ../../hosts.rst:377
+# ac320e5915bc4d5e92bae95824019630
+msgid "Balloon Driver"
+msgstr ""
+
+#: ../../hosts.rst:379
+# 90096ecdf9dd4377bedd8eacc44a5805
+msgid "All VMs should have a balloon driver installed in them. The hypervisor communicates with the balloon driver to free up and make the memory available to a VM."
+msgstr ""
+
+#: ../../hosts.rst:384
+#: ../../hosts.rst:410
+# 3a85924afec74d44a1d3d84552e06e8f
+# 8cce762b3d4c48b5aaa49bca9049a7b8
+msgid "XenServer"
+msgstr ""
+
+#: ../../hosts.rst:386
+# 2bce40c454304c82b26a1b0275e7d257
+msgid "The balloon driver can be found as a part of xen pv or PVHVM drivers. The xen pvhvm drivers are included in upstream linux kernels 2.6.36+."
+msgstr ""
+
+#: ../../hosts.rst:390
+# 9514bde1f9244064beacff1f13d21855
+msgid "VMware"
+msgstr ""
+
+#: ../../hosts.rst:392
+# 1721067bf51441578864874e46fb712f
+msgid "The balloon driver can be found as a part of the VMware tools. All the VMs that are deployed in a over-provisioned cluster should have the VMware tools installed."
+msgstr ""
+
+#: ../../hosts.rst:397
+# fdfc3291197e40cbb6918abad409e86f
+msgid "KVM"
+msgstr ""
+
+#: ../../hosts.rst:399
+# 393102255c6a4f449aa9100faef98786
+msgid "All VMs are required to support the virtio drivers. These drivers are installed in all Linux kernel versions 2.6.25 and greater. The administrator must set CONFIG\\_VIRTIO\\_BALLOON=y in the virtio configuration."
+msgstr ""
+
+#: ../../hosts.rst:405
+# 02e47b485a7e4c9792ff13a65325ff98
+msgid "Hypervisor capabilities"
+msgstr ""
+
+#: ../../hosts.rst:407
+# 24056966cd1e43f4b55061b3d1952313
+msgid "The hypervisor must be capable of using the memory ballooning."
+msgstr ""
+
+#: ../../hosts.rst:412
+# cbb4ca754be34de8ac7f1de22df461b5
+msgid "The DMC (Dynamic Memory Control) capability of the hypervisor should be enabled. Only XenServer Advanced and above versions have this feature."
+msgstr ""
+
+#: ../../hosts.rst:416
+# 134f00ef1ff74950a8dff3d90e185df3
+msgid "VMware, KVM"
+msgstr ""
+
+#: ../../hosts.rst:418
+# cbf853d94adb42db8f9447bcc6c094b4
+msgid "Memory ballooning is supported by default."
+msgstr ""
+
+#: ../../hosts.rst:421
+# fe751eb8be7f47c4ac053e41b99a0c3f
+msgid "Setting Over-Provisioning Ratios"
+msgstr ""
+
+#: ../../hosts.rst:423
+# 362d1a967cde49bd8c050e25ce11a418
+msgid "There are two ways the root admin can set CPU and RAM over-provisioning ratios. First, the global configuration settings cpu.overprovisioning.factor and mem.overprovisioning.factor will be applied when a new cluster is created. Later, the ratios can be modified for an existing cluster."
+msgstr ""
+
+#: ../../hosts.rst:429
+# 1f116a42dfc04347bf2fbc30976a7fe1
+msgid "Only VMs deployed after the change are affected by the new setting. If you want VMs deployed before the change to adopt the new over-provisioning ratio, you must stop and restart the VMs. When this is done, CloudStack recalculates or scales the used and reserved capacities based on the new over-provisioning ratios, to ensure that CloudStack is correctly tracking the amount of free capacity."
+msgstr ""
+
+#: ../../hosts.rst:437
+# 93a9d4a11ea3467bab17fb3f4cd0dad6
+msgid "It is safer not to deploy additional new VMs while the capacity recalculation is underway, in case the new values for available capacity are not high enough to accommodate the new VMs. Just wait for the new used/available values to become available, to be sure there is room for all the new VMs you want."
+msgstr ""
+
+#: ../../hosts.rst:439
+# e0366b1e2fa54380bcd721e1a380fc53
+msgid "To change the over-provisioning ratios for an existing cluster:"
+msgstr ""
+
+#: ../../hosts.rst:443
+# 7ffed21dabe7462b8e09848f5725cc96
+msgid "Log in as administrator to the CloudStack UI."
+msgstr ""
+
+#: ../../hosts.rst:451
+# 4d7c773d04964e5b9f50c9425f2787da
+msgid "Under Clusters, click View All."
+msgstr ""
+
+#: ../../hosts.rst:455
+# 84bddff125d543f283dd83cce8892998
+msgid "Select the cluster you want to work with, and click the Edit button."
+msgstr ""
+
+#: ../../hosts.rst:459
+# 519a8079ef6b4d2eb83eb8537dfed6e8
+msgid "Fill in your desired over-provisioning multipliers in the fields CPU overcommit ratio and RAM overcommit ratio. The value which is intially shown in these fields is the default value inherited from the global configuration settings."
+msgstr ""
+
+#: ../../hosts.rst:468
+# 8e7465fb587642f5aac407e899b0ad64
+msgid "Service Offering Limits and Over-Provisioning"
+msgstr ""
+
+#: ../../hosts.rst:470
+# 0d6a4122110b4dee8cff81972c293a1f
+msgid "Service offering limits (e.g. 1 GHz, 1 core) are strictly enforced for core count. For example, a guest with a service offering of one core will have only one core available to it regardless of other activity on the Host."
+msgstr ""
+
+#: ../../hosts.rst:475
+# 480c139ad92a490a8cf4bf6004be1bf8
+msgid "Service offering limits for gigahertz are enforced only in the presence of contention for CPU resources. For example, suppose that a guest was created with a service offering of 1 GHz on a Host that has 2 GHz cores, and that guest is the only guest running on the Host. The guest will have the full 2 GHz available to it. When multiple guests are attempting to use the CPU a weighting factor is used to schedule CPU resources. The weight is based on the clock speed in the service offering. Guests receive a CPU allocation that is proportionate to the GHz in the service offering. For example, a guest created from a 2 GHz service offering will receive twice the CPU allocation as a guest created from a 1 GHz service offering. CloudStack does not perform memory over-provisioning."
+msgstr ""
+
+#: ../../hosts.rst:488
+# 6973ca6704974a47964898e5e0e218dc
+msgid "VLAN Provisioning"
+msgstr ""
+
+#: ../../hosts.rst:490
+# 5b73126100d24f48a0f831790b6172db
+msgid "CloudStack automatically creates and destroys interfaces bridged to VLANs on the hosts. In general the administrator does not need to manage this process."
+msgstr ""
+
+#: ../../hosts.rst:494
+# 4e2359bef8e1410d98f92288a2f72a96
+msgid "CloudStack manages VLANs differently based on hypervisor type. For XenServer or KVM, the VLANs are created on only the hosts where they will be used and then they are destroyed when all guests that require them have been terminated or moved to another host."
+msgstr ""
+
+#: ../../hosts.rst:499
+# cfd189a826f9412e8b54976947f52b54
+msgid "For vSphere the VLANs are provisioned on all hosts in the cluster even if there is no guest running on a particular Host that requires the VLAN. This allows the administrator to perform live migration and other functions in vCenter without having to create the VLAN on the destination Host. Additionally, the VLANs are not removed from the Hosts when they are no longer needed."
+msgstr ""
+
+#: ../../hosts.rst:506
+# fc44fd764b804474b12d380d2b22dc04
+msgid "You can use the same VLANs on different physical networks provided that each physical network has its own underlying layer-2 infrastructure, such as switches. For example, you can specify VLAN range 500 to 1000 while deploying physical networks A and B in an Advanced zone setup. This capability allows you to set up an additional layer-2 physical infrastructure on a different physical NIC and use the same set of VLANs if you run out of VLANs. Another advantage is that you can use the same set of IPs for different customers, each one with their own routers and the guest networks on different physical NICs."
+msgstr ""
+
+#: ../../hosts.rst:517
+# 06f9c538941f4e3ca83477adfe036a8b
+msgid "VLAN Allocation Example"
+msgstr ""
+
+#: ../../hosts.rst:519
+# 7a8e238fd6a447e9803e0fcd39957760
+msgid "VLANs are required for public and guest traffic. The following is an example of a VLAN allocation scheme:"
+msgstr ""
+
+#: ../../hosts.rst:523
+# 97aaca38941d42f183baf9eb2c560eec
+msgid "VLAN IDs"
+msgstr ""
+
+#: ../../hosts.rst:523
+# d6cbed5a64fc49fda68543d1a54823ec
+msgid "Traffic type"
+msgstr ""
+
+#: ../../hosts.rst:523
+# c6a593644e2848398fdf1b4c86458434
+msgid "Scope"
+msgstr ""
+
+#: ../../hosts.rst:525
+# df3262b199df4244a2cb492f3134ee68
+msgid "less than 500"
+msgstr ""
+
+#: ../../hosts.rst:525
+# 5fc5eed1fae7464bb9bd0cd832cb9901
+msgid "Management traffic."
+msgstr ""
+
+#: ../../hosts.rst:525
+# d7ca9d9a93904c57808e9baf286d1374
+msgid "Reserved for administrative purposes. CloudStack software can access this, hypervisors, system VMs."
+msgstr ""
+
+#: ../../hosts.rst:526
+# 816d6141016845e68cc5cfbb70a5ca4a
+msgid "500-599"
+msgstr ""
+
+#: ../../hosts.rst:526
+# 4c6772a236b949c6a827887e55f468dc
+msgid "VLAN carrying public traffic."
+msgstr ""
+
+#: ../../hosts.rst:526
+# 9788f1148534421f8b3e69b0a2291d4c
+msgid "CloudStack accounts."
+msgstr ""
+
+#: ../../hosts.rst:527
+# faa736af78474fec844134eb7ee8f8e8
+msgid "600-799"
+msgstr ""
+
+#: ../../hosts.rst:527
+#: ../../hosts.rst:528
+# 00cdf19f243d48eda62692e050cca578
+# 968535793b2646eda10843e74d06390c
+msgid "VLANs carrying guest traffic."
+msgstr ""
+
+#: ../../hosts.rst:527
+# 4c9c92a88e4240c8a3eb4021856220ab
+msgid "CloudStack accounts. Account-specific VLAN is chosen from this pool."
+msgstr ""
+
+#: ../../hosts.rst:528
+# 821a9f34a9dd4ccbbcb7099bc2e120ff
+msgid "800-899"
+msgstr ""
+
+#: ../../hosts.rst:528
+# a0b968ec993843e7b61e267dcffdc110
+msgid "CloudStack accounts. Account-specific VLAN chosen by CloudStack admin to assign to that account."
+msgstr ""
+
+#: ../../hosts.rst:529
+# eebf870170034248bf44689d980f22fd
+msgid "900-999"
+msgstr ""
+
+#: ../../hosts.rst:529
+# fcaefad65c864f0aa12decdbc8ea1a9f
+msgid "VLAN carrying guest traffic"
+msgstr ""
+
+#: ../../hosts.rst:529
+# dbc8efd08bdb47939963f1e1ade787c4
+msgid "CloudStack accounts. Can be scoped by project, domain, or all accounts."
+msgstr ""
+
+#: ../../hosts.rst:530
+# b91c7c3931aa46dbaddfffb5b3497d75
+msgid "greater than 1000"
+msgstr ""
+
+#: ../../hosts.rst:530
+# 11b667ae6cb04cc68d5a10a133cee37b
+msgid "Reserved for future use"
+msgstr ""
+
+#: ../../hosts.rst:534
+# 10b73559efa5445caf021d488a10c300
+msgid "Adding Non Contiguous VLAN Ranges"
+msgstr ""
+
+#: ../../hosts.rst:536
+# 632b0960356d40aabb5f7262a942d317
+msgid "CloudStack provides you with the flexibility to add non contiguous VLAN ranges to your network. The administrator can either update an existing VLAN range or add multiple non contiguous VLAN ranges while creating a zone. You can also use the UpdatephysicalNetwork API to extend the VLAN range."
+msgstr ""
+
+#: ../../hosts.rst:544
+# 22166092fd8e4f749f83b22e91ed0a19
+msgid "Log in to the CloudStack UI as an administrator or end user."
+msgstr ""
+
+#: ../../hosts.rst:548
+# c3cc468f1166400fbf2d5bbccec17632
+msgid "Ensure that the VLAN range does not already exist."
+msgstr ""
+
+#: ../../hosts.rst:552
+# 0cca254c9b6c4adab9fca2d53a8d2a99
+msgid "In the left navigation, choose Infrastructure."
+msgstr ""
+
+#: ../../hosts.rst:556
+# 501e52d3dc124b9b81b1a94a93af9f28
+msgid "On Zones, click View More, then click the zone to which you want to work with."
+msgstr ""
+
+#: ../../hosts.rst:561
+# 6a6640c67ea34b0b9a0ca859696174c0
+msgid "Click Physical Network."
+msgstr ""
+
+#: ../../hosts.rst:565
+# 9df7f0d650ab4fa8868898684c3025ba
+msgid "In the Guest node of the diagram, click Configure."
+msgstr ""
+
+#: ../../hosts.rst:569
+# 81b5cc6e8b5e4cffada11d5628cf542b
+msgid "Click Edit |edit-icon.png|."
+msgstr ""
+
+#: ../../hosts.rst:571
+# 128ddb2b1a0b403eaa01728b573229e2
+msgid "The VLAN Ranges field now is editable."
+msgstr ""
+
+#: ../../hosts.rst:575
+# ecf3f3c2e0a24b78aed1b4ed3eb44f3c
+msgid "Specify the start and end of the VLAN range in comma-separated list."
+msgstr ""
+
+#: ../../hosts.rst:577
+# 16e7961826d14270960e64272b17457a
+msgid "Specify all the VLANs you want to use, VLANs not specified will be removed if you are adding new ranges to the existing list."
+msgstr ""
+
+#: ../../hosts.rst:582
+# d6cbf61222844716888f5f8f862bfd82
+msgid "Click Apply."
+msgstr ""
+
+#: ../../hosts.rst:585
+# 87d75c37a1ca4312b9d73ae90c39dacf
+msgid "Assigning VLANs to Isolated Networks"
+msgstr ""
+
+#: ../../hosts.rst:587
+# 329c29ef5c0640298b62d8621919a04e
+msgid "CloudStack provides you the ability to control VLAN assignment to Isolated networks. As a Root admin, you can assign a VLAN ID when a network is created, just the way it's done for Shared networks."
+msgstr ""
+
+#: ../../hosts.rst:591
+# d463cc2b2e6b45efbc688fae2f8c844e
+msgid "The former behaviour also is supported — VLAN is randomly allocated to a network from the VNET range of the physical network when the network turns to Implemented state. The VLAN is released back to the VNET pool when the network shuts down as a part of the Network Garbage Collection. The VLAN can be re-used either by the same network when it is implemented again, or by any other network. On each subsequent implementation of a network, a new VLAN can be assigned."
+msgstr ""
+
+#: ../../hosts.rst:599
+# 67f26f616c1d468f9f43fbad3a96d653
+msgid "Only the Root admin can assign VLANs because the regular users or domain admin are not aware of the physical network topology. They cannot even view what VLAN is assigned to a network."
+msgstr ""
+
+#: ../../hosts.rst:603
+# 8cb6b5c237b24db2a036745c714fd0c1
+msgid "To enable you to assign VLANs to Isolated networks,"
+msgstr ""
+
+#: ../../hosts.rst:607
+# aa68c2b731f44e8ca5e7b12992e491e4
+msgid "Create a network offering by specifying the following:"
+msgstr ""
+
+#: ../../hosts.rst:611
+# 6ac8335147a0424ea30c996690f508f6
+msgid "**Guest Type**: Select Isolated."
+msgstr ""
+
+#: ../../hosts.rst:615
+# a4d3756da9654670af81f81ef51f5bea
+msgid "**Specify VLAN**: Select the option."
+msgstr ""
+
+#: ../../hosts.rst:617
+# 418a868357c54463be949ae219831e3f
+msgid "For more information, see the CloudStack Installation Guide."
+msgstr ""
+
+#: ../../hosts.rst:621
+# c7ae08cd2c954f069c402e2f29bd6498
+msgid "Using this network offering, create a network."
+msgstr ""
+
+#: ../../hosts.rst:623
+# b76ebd2ac4ec4be88b31ead41a0ffa76
+msgid "You can create a VPC tier or an Isolated network."
+msgstr ""
+
+#: ../../hosts.rst:627
+# c827ff2cdfaa40c0a2f5dcefd4637b6f
+msgid "Specify the VLAN when you create the network."
+msgstr ""
+
+#: ../../hosts.rst:629
+# 8e3918b569284ecc9204e3c58114c951
+msgid "When VLAN is specified, a CIDR and gateway are assigned to this network and the state is changed to Setup. In this state, the network will not be garbage collected."
+msgstr ""
+
+#: ../../hosts.rst:634
+# 710699c1ce8949f781a434db64439614
+msgid "You cannot change a VLAN once it's assigned to the network. The VLAN remains with the network for its entire life cycle."
+msgstr ""
+
http://git-wip-us.apache.org/repos/asf/cloudstack-docs-admin/blob/65303ea3/source/locale/pot/index.pot
----------------------------------------------------------------------
diff --git a/source/locale/pot/index.pot b/source/locale/pot/index.pot
new file mode 100644
index 0000000..0f29df7
--- /dev/null
+++ b/source/locale/pot/index.pot
@@ -0,0 +1,103 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C)
+# This file is distributed under the same license as the Apache CloudStack Administration Documentation package.
+# FIRST AUTHOR <EM...@ADDRESS>, YEAR.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: Apache CloudStack Administration Documentation 4\n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2014-03-31 14:08-0400\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EM...@ADDRESS>\n"
+"Language-Team: LANGUAGE <LL...@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#: ../../index.rst:22
+# d7684c4811fb465d8e5523136e60776b
+msgid "Welcome to CloudStack Administration Documentation"
+msgstr ""
+
+#: ../../index.rst:25
+# 89ba74160fc34ab384dce20831bba66f
+msgid "User Interface"
+msgstr ""
+
+#: ../../index.rst:33
+# 0b869c712c0549f794b04850fc92bbf0
+msgid "Managing Accounts, Users and Domains"
+msgstr ""
+
+#: ../../index.rst:41
+# ade0aa6c65934d08b9439c9b55d76991
+msgid "Using Projects to Organize User Resources"
+msgstr ""
+
+#: ../../index.rst:48
+# a4efa62c4fe0431e97cf1e8a8afa3c4c
+msgid "Service Offerings"
+msgstr ""
+
+#: ../../index.rst:56
+# 784d8d28e28c49e588607297adc80f3b
+msgid "Setting up Networking for Users"
+msgstr ""
+
+#: ../../index.rst:64
+# 99a275b31677470fb19d20cc2cfb3a66
+msgid "Working with Virtual Machines"
+msgstr ""
+
+#: ../../index.rst:72
+# 8f3d1a01a82d4daca2072ce17e85191b
+msgid "Working with Templates"
+msgstr ""
+
+#: ../../index.rst:80
+# b618e01117be4bc8917aab2189ec3be4
+msgid "Working with Hosts"
+msgstr ""
+
+#: ../../index.rst:88
+# 1d07b6cc6bd74b689edf5f3f6305e11f
+msgid "Working with Storage"
+msgstr ""
+
+#: ../../index.rst:96
+# 538bdb71f1c34206a75745c0c45b8669
+msgid "Working with System Virtual Machines"
+msgstr ""
+
+#: ../../index.rst:104
+# da80feddb6be416fb7a724951d7f6049
+msgid "Working with Usage"
+msgstr ""
+
+#: ../../index.rst:112
+# 89016757f86c44379eb90b8ea75b6d40
+msgid "Managing Networks and Traffic"
+msgstr ""
+
+#: ../../index.rst:120
+# 4c1cbbb4d99f4c8bace30f6c0edbdd98
+msgid "Managing the Cloud"
+msgstr ""
+
+#: ../../index.rst:128
+# 769cb32397e246beb100d0a77e9bf7ab
+msgid "System Reliability and Availability"
+msgstr ""
+
+#: ../../index.rst:136
+# 2256c3b81c7b49e18235f85ab474184f
+msgid "Tuning"
+msgstr ""
+
+#: ../../index.rst:144
+# 1577c7120b3648449625d8806030fe2b
+msgid "Events and Troubleshooting"
+msgstr ""
+