cloudstack-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From seb...@apache.org
Subject [12/12] git commit: New pot files and tx/config
Date Tue, 27 May 2014 08:51:08 GMT
New pot files and tx/config


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/d63a3776
Tree: http://git-wip-us.apache.org/repos/asf/cloudstack-docs-admin/tree/d63a3776
Diff: http://git-wip-us.apache.org/repos/asf/cloudstack-docs-admin/diff/d63a3776

Branch: refs/heads/master
Commit: d63a377626380a8239e9e8b453b567cab446c65c
Parents: 1089c13
Author: Sebastien Goasguen <runseb@gmail.com>
Authored: Tue May 27 10:50:45 2014 +0200
Committer: Sebastien Goasguen <runseb@gmail.com>
Committed: Tue May 27 10:50:45 2014 +0200

----------------------------------------------------------------------
 .tx/config                                   |    5 +
 source/locale/pot/accounts.pot               |  290 +-
 source/locale/pot/administration.pot         |   34 +-
 source/locale/pot/api.pot                    |   74 +-
 source/locale/pot/events.pot                 |  266 +-
 source/locale/pot/hosts.pot                  |  652 +-
 source/locale/pot/index.pot                  |   95 +-
 source/locale/pot/management.pot             |  340 +-
 source/locale/pot/networking.pot             | 8241 ++++++++++++++++++++-
 source/locale/pot/networking_and_traffic.pot | 7535 +++++++++++++++++++
 source/locale/pot/projects.pot               |  504 +-
 source/locale/pot/reliability.pot            |  272 +-
 source/locale/pot/service_offerings.pot      |  672 +-
 source/locale/pot/storage.pot                |  862 +--
 source/locale/pot/systemvm.pot               |  584 +-
 source/locale/pot/templates.pot              |  984 +--
 source/locale/pot/troubleshooting.pot        |  330 +-
 source/locale/pot/tuning.pot                 |   80 +-
 source/locale/pot/ui.pot                     |  295 +-
 source/locale/pot/usage.pot                  | 1386 ++--
 source/locale/pot/virtual_machines.pot       | 1391 ++--
 21 files changed, 19964 insertions(+), 4928 deletions(-)
----------------------------------------------------------------------


http://git-wip-us.apache.org/repos/asf/cloudstack-docs-admin/blob/d63a3776/.tx/config
----------------------------------------------------------------------
diff --git a/.tx/config b/.tx/config
index 4bc5a06..087e1e7 100644
--- a/.tx/config
+++ b/.tx/config
@@ -102,3 +102,8 @@ file_filter = source/locale/<lang>/LC_MESSAGES/virtual_machines.po
 source_file = source/locale/pot/virtual_machines.pot
 source_lang = en
 
+[apache-cloudstack-administration-rtd.networking_and_traffic]
+file_filter = source/locale/<lang>/LC_MESSAGES/networking_and_traffic.po
+source_file = source/locale/pot/networking_and_traffic.pot
+source_lang = en
+

http://git-wip-us.apache.org/repos/asf/cloudstack-docs-admin/blob/d63a3776/source/locale/pot/accounts.pot
----------------------------------------------------------------------
diff --git a/source/locale/pot/accounts.pot b/source/locale/pot/accounts.pot
index c7ed8fb..c6b8291 100644
--- a/source/locale/pot/accounts.pot
+++ b/source/locale/pot/accounts.pot
@@ -8,7 +8,7 @@ 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"
+"POT-Creation-Date: 2014-05-27 10:34+0200\n"
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
 "Language-Team: LANGUAGE <LL@li.org>\n"
@@ -17,393 +17,393 @@ msgstr ""
 "Content-Transfer-Encoding: 8bit\n"
 
 #: ../../accounts.rst:18
-# 90951daa147540dab10f9d0c78d8c73b
+# bdc151e73be141a8ad0b4190c3102939
 msgid "Managing Accounts, Users and Domains"
 msgstr ""
 
 #: ../../accounts.rst:21
-# 661635f04f94452db5ca9e4dd563cef7
+# a49422e951994e72894009f0fc5cc963
 msgid "Accounts, Users, and Domains"
 msgstr ""
 
 #: ../../accounts.rst:24
-# a7494e04f72d469a86f3c67e958ed65f
+# 7316ca3f637249cbbf2f29bd75791600
 msgid "Accounts"
 msgstr ""
 
 #: ../../accounts.rst:26
-# 457dea8dff534d9aa75e2270c1e1ac6d
+# 7544ce31af194b279c9dcfb7ae37d3cc
 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
+#: ../../accounts.rst:32
+# e758840629a8483ba31892ff437911e1
 msgid "Domains"
 msgstr ""
 
-#: ../../accounts.rst:33
-# 10ebf41c7dbf4e65b1be24934d043965
+#: ../../accounts.rst:34
+# 3e28d2a36b0642c08a698f6a4426e72c
 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
+#: ../../accounts.rst:40
+# 79060520f2e046868f58925f3f2efc01
 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
+#: ../../accounts.rst:46
+# 341bf7792d884c2d8180600a07351f62
 msgid "Users"
 msgstr ""
 
-#: ../../accounts.rst:46
-# 34892ebe1c424238b2d30be07cfbef77
+#: ../../accounts.rst:48
+# 8efee3ca63e44a4098ff5086e58f1249
 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
+#: ../../accounts.rst:54
+# 67a573904306470f87a1f3f6ad52a15f
 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
+#: ../../accounts.rst:59
+# af85977a7aeb4aff9010bde059e08b23
 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
+#: ../../accounts.rst:66
+# 8613eb42958647fba87ae1b922d58740
 msgid "Domain Administrators"
 msgstr ""
 
-#: ../../accounts.rst:65
-# 14a1bb86d2624ad3b4c82731fa8dd170
+#: ../../accounts.rst:68
+# 901efdb2c8554033b865587a48a319f9
 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
+#: ../../accounts.rst:74
+# 5922a532b5814e479301a7d697eb8854
 msgid "Root Administrator"
 msgstr ""
 
-#: ../../accounts.rst:72
-# 97d51f9ba69843b5af3c3770b5e6a41d
+#: ../../accounts.rst:76
+# 20be104d0a134bab92309e774b538dd4
 msgid "Root administrators have complete access to the system, including managing templates, service offerings, customer care administrators, and domains"
 msgstr ""
 
-#: ../../accounts.rst:77
-# 0231216736c74923a934181f66c7be6d
+#: ../../accounts.rst:82
+# 7f9e7eaa9c5b4eaba5575b81514d4040
 msgid "Resource Ownership"
 msgstr ""
 
-#: ../../accounts.rst:79
-# 72eb8676abfd416cb9bbb177a3de84f6
+#: ../../accounts.rst:84
+# 3fad6f5edfb34464b707419ce6b7b4a6
 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
+#: ../../accounts.rst:96
+# f25ec45041cd435d83eaf32720407dd4
 msgid "Dedicating Resources to Accounts and Domains"
 msgstr ""
 
-#: ../../accounts.rst:92
-# 0a4bdfeefcbc4e6b90e29d85882276e5
+#: ../../accounts.rst:98
+# 8a6427fc034647e681a14ca03224406c
 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
+#: ../../accounts.rst:106
+# 13b20e92d1144d5da1089384a9ce4e59
 msgid "There are several types of dedication available:"
 msgstr ""
 
-#: ../../accounts.rst:104
-# dac518c9d097412c8fc411ea7ed6a9e7
+#: ../../accounts.rst:108
+# a62e7433baeb444386932b41fe5601fa
 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
+#: ../../accounts.rst:112
+# 29fbffa86cfd49b4aa29ea7d373eaa03
 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
+# a821acd0f71541708e12788d2fbc5d75
 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
+#: ../../accounts.rst:124
+# b498c9fe36a94f2588d7a9e4494a761d
 msgid "How to Dedicate a Zone, Cluster, Pod, or Host to an Account or Domain"
 msgstr ""
 
-#: ../../accounts.rst:125
-# 235f58f9b9bd48eab66c66dc94d93e40
+#: ../../accounts.rst:126
+# 62ce22c4d6f346b79218ff7a937ee3e2
 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
+#: ../../accounts.rst:130
+# 9dfe3b7a9e87411d9694c32c5e4f891e
 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
+#: ../../accounts.rst:134
+# 90707af3ed2b4e6fa7875e9bdd890252
 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
+#: ../../accounts.rst:144
+# fda3697ce3a4454da72edbe9f02b3564
 msgid "How to Use Dedicated Hosts"
 msgstr ""
 
-#: ../../accounts.rst:144
-# b227acf3ae06498d99b21119713e2238
+#: ../../accounts.rst:146
+# cfd0e245a5a2498b9fa7c89160957ffe
 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
+#: ../../accounts.rst:155
+# 86abbd3940f34e96a1ad71a01dc6339d
 msgid "Behavior of Dedicated Hosts, Clusters, Pods, and Zones"
 msgstr ""
 
-#: ../../accounts.rst:154
-# 05b28e9607634f78abda79633a1403cf
+#: ../../accounts.rst:157
+# a9963e63da4e48f2a2b7b7fdad96ba29
 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
+#: ../../accounts.rst:163
+# a9a8992734b0490aac5bd5e5efa45483
 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
+#: ../../accounts.rst:169
+# 694b1842b07049c094a79e240c2db934
 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
+#: ../../accounts.rst:174
+# 9676e7d49a4247c0bd41a3d53e7482a1
 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
+#: ../../accounts.rst:186
+# c3ac9b9cb46f4fa7b6ea8d96adc7111e
 msgid "Using an LDAP Server for User Authentication"
 msgstr ""
 
-#: ../../accounts.rst:184
-# d3eb07c14a05493ba2ff39ea53010821
+#: ../../accounts.rst:188
+# 4c358cdbd0ef4ea8bae9aa240f1b4e4a
 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
+#: ../../accounts.rst:199
+# 14c749c7da61408588c8e8cdaa11796c
 msgid "To set up LDAP authentication in CloudStack, call the CloudStack API command ldapConfig and provide the following:"
 msgstr ""
 
-#: ../../accounts.rst:200
-# 7826c9574e864a3fa3927d2452d6f247
+#: ../../accounts.rst:202
+# c4708aa56b75423080f17f84ec2a37a4
 msgid "Hostname or IP address and listening port of the LDAP server"
 msgstr ""
 
 #: ../../accounts.rst:204
-# 70b92e095a0749628ec280152921d951
+# ff4d11fcc40f4d5c86ce032c3d6e6a76
 msgid "Base directory and query filter"
 msgstr ""
 
-#: ../../accounts.rst:208
-# 4fe250c5d3ac44ab883b8c10af24f1fe
+#: ../../accounts.rst:206
+# 0b5fce75930e49b19cf1d00062c78539
 msgid "Search user DN credentials, which give CloudStack permission to search on the LDAP server"
 msgstr ""
 
-#: ../../accounts.rst:213
-# 2ceaa9828892484ebd391520d745991d
+#: ../../accounts.rst:209
+# c3d66516470141c3af861a4b24f45150
 msgid "SSL keystore and password, if SSL is used"
 msgstr ""
 
-#: ../../accounts.rst:216
-# 26d8fb1d67a74f8387452da5b3cce675
+#: ../../accounts.rst:213
+# 6e565fd7b02d4a97b86b380e839f129f
 msgid "Example LDAP Configuration Commands"
 msgstr ""
 
-#: ../../accounts.rst:218
-# 1c19000335be4f7ebdab1d79a7c4658c
+#: ../../accounts.rst:215
+# ee72e29a6b33456684ebcbfd012c075a
 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
+#: ../../accounts.rst:219
+# 065e58a0d0f74c8d84670251cf00c487
 msgid "The following shows an example invocation of ldapConfig with an ApacheDS LDAP server"
 msgstr ""
 
-#: ../../accounts.rst:229
-# 7214405299e94877a1c09f6c6287ee10
+#: ../../accounts.rst:226
+# 31d88144f8004adf8efd11cf7f9db7bd
 msgid "The command must be URL-encoded. Here is the same example without the URL encoding:"
 msgstr ""
 
-#: ../../accounts.rst:247
-# 74c45748c7614774911829b534605cc1
+#: ../../accounts.rst:244
+# 884cde7f5dbd499ba1c28ff09380c692
 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
+#: ../../accounts.rst:252
+# d2675a267aa34f4ea3fe2bba2300b61c
 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
+#: ../../accounts.rst:257
+# befdce0cfd624549844139c917a82bb4
 msgid "Search Base"
 msgstr ""
 
-#: ../../accounts.rst:261
-# f44d14b0d741402087e0cc706bbb068e
+#: ../../accounts.rst:259
+# 1522f19d5a2a4e35a8bedc5d147a1af1
 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:270
 #: ../../accounts.rst:328
-# c824c6d3616243eaa848cc45808ec373
-# 46c8c55831674fd3a12caa7352108fa4
+# 3649e87915d24059beec30463e0abd10
+# eb0f32160dd24b21991c2f454df60742
 msgid "LDAP Server"
 msgstr ""
 
-#: ../../accounts.rst:272
-# bf34c451c0994186b556742324006c30
+#: ../../accounts.rst:270
+# d8fb5f498afb4ee1aa6669b39f1e34be
 msgid "Example Search Base DN"
 msgstr ""
 
-#: ../../accounts.rst:274
+#: ../../accounts.rst:272
 #: ../../accounts.rst:330
-# c6940ea324fb4c99895c4d2152bfd32e
-# 359bafef7f4044e380b30643767ad285
+# 2e421fc0d49d4a819b31999dc3cae2e0
+# a0327a00878d45dab6dc0bc777814674
 msgid "ApacheDS"
 msgstr ""
 
-#: ../../accounts.rst:274
-# 2253d38b2ae84eeab805635117cf368c
+#: ../../accounts.rst:272
+# 6c854d5e6cdd4e3aadda7dd9be769a53
 msgid "OU=testing, O=project"
 msgstr ""
 
-#: ../../accounts.rst:275
+#: ../../accounts.rst:273
 #: ../../accounts.rst:331
-# ddf11f35901948058a34dff9cbca8c3d
-# 6d6eab10b7674a65aedf6c1f41312bf8
+# a1fbaf989c584a248386911c51fd2fba
+# c776e850eb3e4d64b262a32a9d302bfb
 msgid "Active Directory"
 msgstr ""
 
-#: ../../accounts.rst:275
-# 0fdc037b3c2746e0b455bd0594bf0bee
+#: ../../accounts.rst:273
+# 5d0095ff2d7044e7b60bc1754210dd3c
 msgid "OU=testing, DC=company"
 msgstr ""
 
-#: ../../accounts.rst:279
-# 03d46aff89114039bebeeea32fbcda86
+#: ../../accounts.rst:278
+# 8309dae488944f0aae3e84a8e1a97ac3
 msgid "Query Filter"
 msgstr ""
 
-#: ../../accounts.rst:281
-# 93b867a441bc4cddad5a72d6b9e51abf
+#: ../../accounts.rst:280
+# c523dbbf5dd94c62a2e3927a8f3123dc
 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
+#: ../../accounts.rst:285
+# f4f9c13ceefa4163962bd3cfab257852
 msgid "The CloudStack query filter wildcards are:"
 msgstr ""
 
-#: ../../accounts.rst:289
-# f7c82cdd777a4284b5adc6a920065f32
+#: ../../accounts.rst:288
+# bab683973b9045339c8df3488bc5dd1c
 msgid "Query Filter Wildcard"
 msgstr ""
 
-#: ../../accounts.rst:289
-# 2e1c45a30d2648c6878074583a6a4c7b
+#: ../../accounts.rst:288
+# a94af335cc864d9a962f1fb9b7b5f72c
 msgid "Description"
 msgstr ""
 
-#: ../../accounts.rst:291
-# b636b6a26b4942d390e3083bb99636ec
+#: ../../accounts.rst:290
+# 334393ba6786415e91a2ed1a22d26adb
 msgid "%u"
 msgstr ""
 
-#: ../../accounts.rst:291
-# b85fa10a6f7c473f9579fbee87abc7dc
+#: ../../accounts.rst:290
+# 151cd28e952d4ff98ff9d1544698ccb8
 msgid "User name"
 msgstr ""
 
-#: ../../accounts.rst:292
-# aaca04ef47ce4a6d957d7f999021beec
+#: ../../accounts.rst:291
+# f1f86cbcf39e412fb298da7653a123d3
 msgid "%e"
 msgstr ""
 
-#: ../../accounts.rst:292
-# 04104fb07bb94de38b10667d6fdadf04
+#: ../../accounts.rst:291
+# fdf52531788c41fabb814f45f07b178a
 msgid "Email address"
 msgstr ""
 
-#: ../../accounts.rst:293
-# ae0690d61f774148a22980a6ed2d4c98
+#: ../../accounts.rst:292
+# 6e5b529e3da248ee85f1e20f81bd8e1c
 msgid "%n"
 msgstr ""
 
-#: ../../accounts.rst:293
-# 5c8df2d1e58b4c88b7f6f76691f54e32
+#: ../../accounts.rst:292
+# 4704eb3b3e494ad3bc2105d98a3c84a9
 msgid "First and last name"
 msgstr ""
 
-#: ../../accounts.rst:296
-# fb24e5d77b0b4a369c988a18859c27b5
+#: ../../accounts.rst:295
+# 51612c6475e246f7b7d8a156605a2323
 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
+#: ../../accounts.rst:298
+# d853815e3f894dcdbb92be883305dc5b
 msgid "If the CloudStack user name is the same as the LDAP user ID:"
 msgstr ""
 
-#: ../../accounts.rst:305
-# fe9b3901fa4c442dbba0966d900dc335
+#: ../../accounts.rst:304
+# d0bb623240d0410eb8d70ed22ba5a2f8
 msgid "If the CloudStack user name is the LDAP display name:"
 msgstr ""
 
-#: ../../accounts.rst:311
-# 67bfee8945324987bfa2debd1cbd0f29
+#: ../../accounts.rst:310
+# 0a96c3c2516946c1b4260fd4d4d6ffb7
 msgid "To find a user by email address:"
 msgstr ""
 
 #: ../../accounts.rst:318
-# 0a2a4f3d28a447ccafdcade93acec26e
+# 5b63c901fb5a4d208df8e362234d1cba
 msgid "Search User Bind DN"
 msgstr ""
 
 #: ../../accounts.rst:320
-# 9d07ca9ffe4d45e1a14848570aad2f64
+# 92769f4cb5be444cab0bcb685ebe1cc4
 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
+# 7fcc45a0be9241b09a01d2287541d652
 msgid "Example Bind DN"
 msgstr ""
 
 #: ../../accounts.rst:330
-# 1cd4f20b644c4fd68eb8a37ef35f7b47
+# b4c0b2f84be54e32820cac392b6c9c75
 msgid "CN=Administrator,DC=testing,OU=project,OU=org"
 msgstr ""
 
 #: ../../accounts.rst:331
-# 2e60a99cfddd494c9de480a48304dfe3
+# 46e145ddbc9f47e08b21fa2631ed9fa7
 msgid "CN=Administrator, OU=testing, DC=company, DC=com"
 msgstr ""
 
 #: ../../accounts.rst:336
-# 16cd1707b0594271ae8a6ae3884ec80e
+# cbaaf7054abf480eb88b336ba62a097b
 msgid "SSL Keystore Path and Password"
 msgstr ""
 
 #: ../../accounts.rst:338
-# 074f3d04369241be9e56096bb7dded79
+# 8a6a84c57cc144edb9a20e63c71ddedc
 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/d63a3776/source/locale/pot/administration.pot
----------------------------------------------------------------------
diff --git a/source/locale/pot/administration.pot b/source/locale/pot/administration.pot
index a70fd94..9bbb1db 100644
--- a/source/locale/pot/administration.pot
+++ b/source/locale/pot/administration.pot
@@ -8,7 +8,7 @@ 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"
+"POT-Creation-Date: 2014-05-27 10:34+0200\n"
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
 "Language-Team: LANGUAGE <LL@li.org>\n"
@@ -16,48 +16,48 @@ msgstr ""
 "Content-Type: text/plain; charset=UTF-8\n"
 "Content-Transfer-Encoding: 8bit\n"
 
-#: ../../administration.rst:19
-# 5782522e7a564a9caa1ecc02e0977696
+#: ../../administration.rst:18
+# 29cfff43a2514946ad4c3499ebefbed6
 msgid "User Services"
 msgstr ""
 
-#: ../../administration.rst:21
-# 06114f8c3f954e45b8add1ef10ed3f6e
+#: ../../administration.rst:20
+# d7001feee3bd4b298a4c17869c0c45dc
 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
+# 8691c3078d2741dabb85f469a7b58373
 msgid "Service Offerings, Disk Offerings, Network Offerings, and Templates"
 msgstr ""
 
 #: ../../administration.rst:36
-# f761dfbfdddc4df58bc4fb22ad4c4ada
+# 82a1a03c5a234653b024700134d18169
 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
+#: ../../administration.rst:40
+# 5b79acf1c4034cf09e56634938cbfd33
 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
+#: ../../administration.rst:44
+# d71f7d3d0dda4061838347d6fc7e35fc
 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
+#: ../../administration.rst:48
+# c00720676a8a4c4a9d423dd5f5743f4c
 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
+#: ../../administration.rst:53
+# 169ad751a60e44929103a91c102ac2a2
 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
+#: ../../administration.rst:58
+# 81b027ebc2094409b6f28288660792c7
 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/d63a3776/source/locale/pot/api.pot
----------------------------------------------------------------------
diff --git a/source/locale/pot/api.pot b/source/locale/pot/api.pot
index efa4adf..220a3f8 100644
--- a/source/locale/pot/api.pot
+++ b/source/locale/pot/api.pot
@@ -8,7 +8,7 @@ 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"
+"POT-Creation-Date: 2014-05-27 10:34+0200\n"
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
 "Language-Team: LANGUAGE <LL@li.org>\n"
@@ -17,107 +17,107 @@ msgstr ""
 "Content-Transfer-Encoding: 8bit\n"
 
 #: ../../api.rst:18
-# c9f373cc299e447998a4b0c51d6b30e1
+# 7499b008b97e41b59d4cdc3835758f36
 msgid "CloudStack API"
 msgstr ""
 
 #: ../../api.rst:20
-# 4f31f79497784c4eb83f19285c8fc8d4
+# 7a40beffc6484f108ad5202cb2a4e7c3
 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
+# 0e4247f81b8a4a83afa84f323d2697b9
 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
+# dc0b3fef72b74085a24d7e0c15cb227d
 msgid "The API has a REST-like query basis and returns results in XML or JSON."
 msgstr ""
 
 #: ../../api.rst:31
-# 3f40f7f90a3b4dd2a8b4ddbb30340800
+# 1f57015e966c480795b141ba3f87b86a
 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
+#: ../../api.rst:36
+# de3d35bb699f45f495251ceb69a2c238
 msgid "Provisioning and Authentication API"
 msgstr ""
 
-#: ../../api.rst:37
-# 4b899aee7aa147bbb8cbe8cc3fdd3436
+#: ../../api.rst:38
+# c8eb593d2c654d8db8d5ce7791bedd07
 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
+#: ../../api.rst:42
+# f37cbbabb4af4c76977b51277f5cefa3
 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
+#: ../../api.rst:50
+# a1cd31f63e9a4fe6869e80cdd8f2274f
 msgid "User Data and Meta Data"
 msgstr ""
 
-#: ../../api.rst:50
-# 4921f2bf02984bc0a308cc391af4cabf
+#: ../../api.rst:52
+# 8adea5c3508040cfb6f8475bc1f2f96c
 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
+#: ../../api.rst:56
+# 11a9a59d3f23401d8c639b7767af0a94
 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
+#: ../../api.rst:60
+# 0b14bfd2cf6c41a98f39a406fdb83868
 msgid "Run the following command to find the virtual router."
 msgstr ""
 
-#: ../../api.rst:64
-# 6fff13e87cff49809caebf13b8fa61cb
+#: ../../api.rst:66
+# e0144a29051543d1aba1d5b18d18e033
 msgid "Access user data by running the following command using the result of the above command"
 msgstr ""
 
-#: ../../api.rst:71
-# cd37cb5d158343c29780503c5bca4540
+#: ../../api.rst:73
+# 8ebc1946ef8840c4b4c99d6194576997
 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
+# bed0120874a643b1b9d59bd6a4e9e404
 msgid "service-offering. A description of the VMs service offering"
 msgstr ""
 
-#: ../../api.rst:82
-# 62048249f8d2494db34980c3b1862e5b
+#: ../../api.rst:80
+# 71b8d766955140c3b512c2a9318fa115
 msgid "availability-zone. The Zone name"
 msgstr ""
 
-#: ../../api.rst:86
-# 7463be88f12e49e8aac8925ca6a5884f
+#: ../../api.rst:82
+# 2a80730691bb49e0b69de28d14feea03
 msgid "local-ipv4. The guest IP of the VM"
 msgstr ""
 
-#: ../../api.rst:90
-# ba16b21040764726a1202dde1d4e83d6
+#: ../../api.rst:84
+# 6f5c73e35f714f0f83b7c799a46c499f
 msgid "local-hostname. The hostname of the VM"
 msgstr ""
 
-#: ../../api.rst:94
-# 363adc60e20b4bfcb51004281919f11e
+#: ../../api.rst:86
+# ad4c5b53b2844aa9b7518ea0165e3c5a
 msgid "public-ipv4. The first public IP for the router. (E.g. the first IP of eth2)"
 msgstr ""
 
-#: ../../api.rst:99
-# 352781028d6f46f1b95f08adccbb1ff2
+#: ../../api.rst:89
+# 53db659838e1499c86e3674db658bbdb
 msgid "public-hostname. This is the same as public-ipv4"
 msgstr ""
 
-#: ../../api.rst:103
-# dc787ff8567442788d44cf46ab9a6462
+#: ../../api.rst:91
+# 760946f739514ea5be9f4c114716b1ba
 msgid "instance-id. The instance name of the VM"
 msgstr ""
 

http://git-wip-us.apache.org/repos/asf/cloudstack-docs-admin/blob/d63a3776/source/locale/pot/events.pot
----------------------------------------------------------------------
diff --git a/source/locale/pot/events.pot b/source/locale/pot/events.pot
index 57799bc..5af6887 100644
--- a/source/locale/pot/events.pot
+++ b/source/locale/pot/events.pot
@@ -8,7 +8,7 @@ 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"
+"POT-Creation-Date: 2014-05-27 10:34+0200\n"
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
 "Language-Team: LANGUAGE <LL@li.org>\n"
@@ -17,316 +17,316 @@ msgstr ""
 "Content-Transfer-Encoding: 8bit\n"
 
 #: ../../events.rst:18
-# 102ed2ffb3fb4c3bb6029d0c7eb905de
+# 0defb3a9608c4824b34ed35d916fd0c4
 msgid "Event Notification"
 msgstr ""
 
 #: ../../events.rst:20
-# afc241a8b0d0496a8744768e3563fbe8
+# 37ebc4e9b0b148daaab42c65d71cc834
 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
+#: ../../events.rst:30
+# 82bc7c30085140f89344da554ad386a3
 msgid "Event Logs"
 msgstr ""
 
-#: ../../events.rst:31
-# 1d21fa8ae81748baa8e52f31043facf7
+#: ../../events.rst:32
+# c1d54e6d1a2d4cd6888ad99bf943ed83
 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
+#: ../../events.rst:45
+# 127295678f0c4cf084cf737444f11087
 msgid "Notification"
 msgstr ""
 
-#: ../../events.rst:45
-# 64816315eaa145ab8ad138648b2589e3
+#: ../../events.rst:47
+# a669e3079b7e41d1a82dd149bf00b011
 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
+#: ../../events.rst:59
+# e41f3e4f6450467da27fc6dc4ebb2788
 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
+#: ../../events.rst:71
+# 4aaf02080d184ab387923b45f39d5762
 msgid "Use Cases"
 msgstr ""
 
-#: ../../events.rst:70
-# 2b32e72970d74bd3b50d67a5c2b25913
+#: ../../events.rst:73
+# f7b5a1de0f014d2eabfe925d0c5c4e95
 msgid "The following are some of the use cases:"
 msgstr ""
 
-#: ../../events.rst:74
-# 785e64cd20c945e39b1fcd1248e29463
+#: ../../events.rst:75
+# 9be82bc2fe244fef9851d9adb481fdaf
 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
+#: ../../events.rst:80
+# 2585685666874f3f8795c70fe2671356
 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
+#: ../../events.rst:84
+# ff10e0227bc04e2f86f15c3c534b7c47
 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
+#: ../../events.rst:92
+# bdc9ac2f935c456fbd3778ddef6c91cf
 msgid "Configuration"
 msgstr ""
 
-#: ../../events.rst:96
-# 1520275479c3459fb8bb45890eae9935
+#: ../../events.rst:94
+# c2514aa04f964044bd2bd630f31b4d3f
 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
+#: ../../events.rst:98
+# e94d4200515d4f15adbc52ca3bbf8c54
 msgid "Open ``'componentContext.xml``."
 msgstr ""
 
-#: ../../events.rst:106
-# 9df0be28f95041d19f82142547b7265b
+#: ../../events.rst:100
+# e2bbf37abe854d6cb8384bdd3c9d72b9
 msgid "Define a bean named ``eventNotificationBus`` as follows:"
 msgstr ""
 
-#: ../../events.rst:110
-# e46a3a197cc74df2a9eb8e5bd57ebf52
+#: ../../events.rst:102
+# 47bce54d52714df7bafac2b6d04dd816
 msgid "name : Specify a name for the bean."
 msgstr ""
 
-#: ../../events.rst:114
-# b203c95bc9f44afc81fbb8980802291e
+#: ../../events.rst:104
+# 4317cb3aa0fd4c7fa3f0e637f6cfea48
 msgid "server : The name or the IP address of the RabbitMQ AMQP server."
 msgstr ""
 
-#: ../../events.rst:118
-# 6e8c151c2dd847f1a2a160d97c119e86
+#: ../../events.rst:106
+# 0f6561172d38446db99181316f50e667
 msgid "port : The port on which RabbitMQ server is running."
 msgstr ""
 
-#: ../../events.rst:122
-# 42911e580f7a4f6fa5b5be87551390cb
+#: ../../events.rst:108
+# 7ff0aa3ff7af48fbbf4651a2d8e5f34d
 msgid "username : The username associated with the account to access the RabbitMQ server."
 msgstr ""
 
-#: ../../events.rst:127
-# 887fd9bc57b548f382e1c635c3dbb8a0
+#: ../../events.rst:111
+# 7193c434eaab44eda2d7d9b2b86c675d
 msgid "password : The password associated with the username of the account to access the RabbitMQ server."
 msgstr ""
 
-#: ../../events.rst:132
-# 4c518b7b80a941638553284affb8603e
+#: ../../events.rst:114
+# f765ea7d69504610a98a95fdb802fe32
 msgid "exchange : The exchange name on the RabbitMQ server where CloudStack events are published."
 msgstr ""
 
-#: ../../events.rst:135
-# f881113c3c1540c9a568b4bb01f37ff2
+#: ../../events.rst:117
+# 7ba933b1d4ec41c1a20f2cdca4275405
 msgid "A sample bean is given below:"
 msgstr ""
 
-#: ../../events.rst:148
-# c88f66382e86471fa752a96e8c286e51
+#: ../../events.rst:130
+# 07a04a0f79804e938092a93f3180770a
 msgid "The ``eventNotificationBus`` bean represents the ``org.apache.cloudstack.mom.rabbitmq.RabbitMQEventBus`` class."
 msgstr ""
 
-#: ../../events.rst:153
-# 3c84696f04ae4ad58c0edfe8eee24a49
+#: ../../events.rst:133
+# 83cdf82ae8c34a238d181c5bbaef30dd
 msgid "Restart the Management Server."
 msgstr ""
 
-#: ../../events.rst:156
-# 34f2df7b30c8489690de80ca02292b43
+#: ../../events.rst:137
+# 573b41c4def247f6981e828da7f54f82
 msgid "Standard Events"
 msgstr ""
 
-#: ../../events.rst:158
-#: ../../events.rst:191
-# 658ab70617ca480387c4446d2df3f783
-# e43e53282a8743bc94e7a3f26dacfeed
+#: ../../events.rst:139
+#: ../../events.rst:161
+# f503981d0a764de49d4acc01c70d6126
+# 9212f9cd71b542899ac8256d4a51026d
 msgid "The events log records three types of standard events."
 msgstr ""
 
-#: ../../events.rst:162
-#: ../../events.rst:195
-# 9400dae867ab48dfb95e9a05e8949fdb
-# cb299fcbd64849a7a47486675d1f6477
+#: ../../events.rst:141
+#: ../../events.rst:163
+# fab87560ba674752808dacaf3abfc44a
+# 94b40a1c0c98456399293f6a38102385
 msgid "INFO. This event is generated when an operation has been successfully performed."
 msgstr ""
 
-#: ../../events.rst:167
-#: ../../events.rst:200
-# 294607854e004c4fa685bb9760e11d2f
-# 26f912bd36f4415c9f6349109dbc880a
+#: ../../events.rst:144
+#: ../../events.rst:166
+# 49450fc963104f569e80611ac7179829
+# 13438410decf4526b0381dc44062ba76
 msgid "WARN. This event is generated in the following circumstances."
 msgstr ""
 
-#: ../../events.rst:171
-#: ../../events.rst:204
-# 8f26ab07f1da41c5a67f35568dee82ae
-# a962175d5c794f9e88b25a995aa3fe1a
+#: ../../events.rst:146
+#: ../../events.rst:168
+# c6197efc809f4a67baf05aa139cb10f5
+# a16599807269441f8f1799ae29968e11
 msgid "When a network is disconnected while monitoring a template download."
 msgstr ""
 
-#: ../../events.rst:176
-#: ../../events.rst:209
-# 41d6341dfbc74296aebd0eff9602f59a
-# 9bdea7d661d140718fea5fda4ae30615
+#: ../../events.rst:149
+#: ../../events.rst:171
+# 0e060afef9e84640b3c2da38436691e2
+# 019e604962174d4492cca7be02ad2647
 msgid "When a template download is abandoned."
 msgstr ""
 
-#: ../../events.rst:180
-#: ../../events.rst:213
-# d2d6ebc19c2f42138e8698f89ee29c6f
-# 93031d47c5704fb383a9e8149b602855
+#: ../../events.rst:151
+#: ../../events.rst:173
+# 8b3eabd5fcc0406bb83abe3863261df9
+# 19ccb6eebbc1446a8cb47056d2ad0274
 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
+#: ../../events.rst:154
+#: ../../events.rst:176
+# 96793fba6d294c98bd8dcde72d0d9f49
+# 0b487b0c814145438366a847c93c52d8
 msgid "ERROR. This event is generated when an operation has not been successfully performed"
 msgstr ""
 
-#: ../../events.rst:189
-# 5b8500630feb40f4afb3b8f9e29a53a3
+#: ../../events.rst:159
+# b1c1824ddd304288bd0803e80d482bb9
 msgid "Long Running Job Events"
 msgstr ""
 
-#: ../../events.rst:222
-# c379b57670384b0b9da909afafca7292
+#: ../../events.rst:181
+# ffb5ee0896674a62a567e634fc725510
 msgid "Event Log Queries"
 msgstr ""
 
-#: ../../events.rst:224
-# 88a9f85fb3da4603bee07701eabb7806
+#: ../../events.rst:183
+# 0c75a642e72943e0bb28642902590c9b
 msgid "Database logs can be queried from the user interface. The list of events captured by the system includes:"
 msgstr ""
 
-#: ../../events.rst:229
-# cd15e4ae2eca4d55b7510293e7fd2bbd
+#: ../../events.rst:186
+# fe735d1b0444472aa47e381cd00eec61
 msgid "Virtual machine creation, deletion, and on-going management operations"
 msgstr ""
 
-#: ../../events.rst:234
-# 2df022a424dc41b699e1367171be2d50
+#: ../../events.rst:189
+# e331126149b64023bf0e7655bbcb2991
 msgid "Virtual router creation, deletion, and on-going management operations"
 msgstr ""
 
-#: ../../events.rst:238
-# d36f900c99fb40fa94804d5e52af7822
+#: ../../events.rst:191
+# 33b99484fca246c48ceff95aac8b52d2
 msgid "Template creation and deletion"
 msgstr ""
 
-#: ../../events.rst:242
-# 2e97521ac7be4b15b4892a30073bc966
+#: ../../events.rst:193
+# 7969071933104816945f05e9f3a597e3
 msgid "Network/load balancer rules creation and deletion"
 msgstr ""
 
-#: ../../events.rst:246
-# f59bcdcfa249464a800cad1cd97cfc0f
+#: ../../events.rst:195
+# 91ecfa5192134ffeafe5043cff29432a
 msgid "Storage volume creation and deletion"
 msgstr ""
 
-#: ../../events.rst:250
-# 8bd53c90bb38449fbbadd472c0930466
+#: ../../events.rst:197
+# b0c0672f35af4003870943a16b461337
 msgid "User login and logout"
 msgstr ""
 
-#: ../../events.rst:253
-# 1e928be3f4e54e8f8b6532879b4e5f7e
+#: ../../events.rst:201
+# 57cfb09e85c842b581f3a0f38609a9c4
 msgid "Deleting and Archiving Events and Alerts"
 msgstr ""
 
-#: ../../events.rst:255
-# 13275df9c48f45ccba383ca172df3874
+#: ../../events.rst:203
+# b4160055fbd946979df299cf40a75777
 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
+#: ../../events.rst:208
+# 7bdab572982c4739808182e94b589c7e
 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
+#: ../../events.rst:217
+# cf46cdd4536a4a93912df2f4e88af8a1
 msgid "In order to support the delete or archive alerts, the following global parameters have been added:"
 msgstr ""
 
-#: ../../events.rst:274
-# d437d10a6c5c4d4fac98d68635980067
+#: ../../events.rst:220
+# 19ff2e090cf24d30aeacde33ec972af1
 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
+#: ../../events.rst:223
+# e3ccfdc51da14488bc9e44623c64d707
 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
+#: ../../events.rst:228
+# a6eda71ad15940c2b58724ff74f97e26
 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
+#: ../../events.rst:234
+# 7c40293965f24130896768ea8223a152
 msgid "Permissions"
 msgstr ""
 
-#: ../../events.rst:290
-# 7db5396af5d24382a51e418ced931fff
+#: ../../events.rst:236
+# e43e679e6a304ae1b78e11f56bed12b2
 msgid "Consider the following:"
 msgstr ""
 
-#: ../../events.rst:294
-# 2814ee39c91e4c2e832d73a1a39839b5
+#: ../../events.rst:238
+# c5bd820d9a5e487b9440609da1e22551
 msgid "The root admin can delete or archive one or multiple alerts or events."
 msgstr ""
 
-#: ../../events.rst:299
-# 01be1c88e97f4e9eae1e310e28045ae2
+#: ../../events.rst:241
+# 51b4fa6e53064c7088052c69d7a1b4fe
 msgid "The domain admin or end user can delete or archive one or multiple events."
 msgstr ""
 
-#: ../../events.rst:303
-# 8d806f13fadd4080bae10069ad330bbc
+#: ../../events.rst:246
+# bea2b3dcb4bb41468a31793133ffeb06
 msgid "Procedure"
 msgstr ""
 
-#: ../../events.rst:307
-# 0670181e1983452ab571f7ae6ce4d594
+#: ../../events.rst:248
+# aa16543921984837a7f59142ad2df67d
 msgid "Log in as administrator to the CloudStack UI."
 msgstr ""
 
-#: ../../events.rst:311
-# 3ab15d176fec4a14a47ed28c4e81a0bc
+#: ../../events.rst:250
+# f8b2ec5bdbf749d2bf704ff20c063c89
 msgid "In the left navigation, click Events."
 msgstr ""
 
-#: ../../events.rst:315
-# 3dfc816afe4744f1a2b5aa030c3be966
+#: ../../events.rst:252
+# 5519a86ae5b04a68b972ee88e37deffe
 msgid "Perform either of the following:"
 msgstr ""
 
-#: ../../events.rst:319
-# 3308c260b9c8454bb6109c2b36420617
+#: ../../events.rst:254
+# fd1193e3ff83466aa226d4834dea269d
 msgid "To archive events, click Archive Events, and specify event type and date."
 msgstr ""
 
-#: ../../events.rst:324
-# 3563bec70a3f40aa9bfd26494bda8c93
+#: ../../events.rst:257
+# abfda9e22c7f42f3a4ff488ff755e59e
 msgid "To archive events, click Delete Events, and specify event type and date."
 msgstr ""
 
-#: ../../events.rst:329
-# f0ab5197a41b478684c629f86f95fc12
+#: ../../events.rst:260
+# 58b630d17160410ab6757d134aa17a62
 msgid "Click OK."
 msgstr ""
 


Mime
View raw message