You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cloudstack.apache.org by pd...@apache.org on 2017/02/08 01:18:24 UTC
[11/63] [abbrv] cloudstack-docs-admin git commit: 50% des chaines
sont traduites en FR
http://git-wip-us.apache.org/repos/asf/cloudstack-docs-admin/blob/a6b15cb9/source/locale/pot/virtual_machines/user-data.pot
----------------------------------------------------------------------
diff --git a/source/locale/pot/virtual_machines/user-data.pot b/source/locale/pot/virtual_machines/user-data.pot
new file mode 100644
index 0000000..d3f3bb5
--- /dev/null
+++ b/source/locale/pot/virtual_machines/user-data.pot
@@ -0,0 +1,106 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2016, Apache Software Foundation
+# 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.8\n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2016-08-22 13:55+0200\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EM...@ADDRESS>\n"
+"Language-Team: LANGUAGE <LL...@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#: ../../virtual_machines/user-data.rst:18
+msgid "User-Data and Meta-Data"
+msgstr ""
+
+#: ../../virtual_machines/user-data.rst:20
+msgid "CloudStack provides API access to attach up to 2KB of data after base64 encoding to a deployed VM. Using HTTP POST(via POST body), you can send up to 32K of data after base64 encoding. Deployed VMs also have access to instance metadata via the virtual router."
+msgstr ""
+
+#: ../../virtual_machines/user-data.rst:25
+msgid "Create virtual machine thru the API: `deployVirtualMachine <http://cloudstack.apache.org/docs/api/apidocs-4.5/user/deployVirtualMachine.html>`_ using the parameter ``userdata=`` to include user-data formated in `base64 <https://www.base64encode.org/>`_."
+msgstr ""
+
+#: ../../virtual_machines/user-data.rst:29
+msgid "Accessed user-data from VM. Once the IP address of the virtual router is known, use the following steps to retrieve user-data:"
+msgstr ""
+
+#: ../../virtual_machines/user-data.rst:32
+msgid "Run the following command to find the virtual router."
+msgstr ""
+
+#: ../../virtual_machines/user-data.rst:38
+msgid "Access user-data by running the following command using the result of the above command"
+msgstr ""
+
+#: ../../virtual_machines/user-data.rst:45
+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 ""
+
+#: ../../virtual_machines/user-data.rst:50
+msgid "``service-offering``. A description of the VMs service offering"
+msgstr ""
+
+#: ../../virtual_machines/user-data.rst:52
+msgid "``availability-zone``. The Zone name"
+msgstr ""
+
+#: ../../virtual_machines/user-data.rst:54
+msgid "``local-ipv4``. The guest IP of the VM"
+msgstr ""
+
+#: ../../virtual_machines/user-data.rst:56
+msgid "``local-hostname``. The hostname of the VM"
+msgstr ""
+
+#: ../../virtual_machines/user-data.rst:58
+msgid "``public-ipv4``. The first public IP for the router. (E.g. the first IP of eth2)"
+msgstr ""
+
+#: ../../virtual_machines/user-data.rst:61
+msgid "``public-hostname``. This is the same as public-ipv4"
+msgstr ""
+
+#: ../../virtual_machines/user-data.rst:63
+msgid "``instance-id``. The instance name of the VM"
+msgstr ""
+
+#: ../../virtual_machines/user-data.rst:67
+msgid "Using Cloud-Init"
+msgstr ""
+
+#: ../../virtual_machines/user-data.rst:69
+msgid "`Cloud-Init <https://cloudinit.readthedocs.org/en/latest>`_ can be use to access an interpret user-data from virtual machines. Cloud-Init be installed into templates and also require CloudStack password and sshkey scripts (:ref:`adding-password-management-to-templates` and `using ssh keys <virtual_machines.html#using-ssh-keys-for-authentication>`_). User password management and ``resetSSHKeyForVirtualMachine`` API are not yet supported by cloud-init."
+msgstr ""
+
+#: ../../virtual_machines/user-data.rst:74
+msgid "Install cloud-init package into a template:"
+msgstr ""
+
+#: ../../virtual_machines/user-data.rst:82
+msgid "Create datasource configuration file: ``/etc/cloud/cloud.cfg.d/99_cloudstack.cfg``"
+msgstr ""
+
+#: ../../virtual_machines/user-data.rst:94
+msgid "user-data example"
+msgstr ""
+
+#: ../../virtual_machines/user-data.rst:96
+msgid "This example use cloud-init to Upgrade Operating-System of the newly created VM:"
+msgstr ""
+
+#: ../../virtual_machines/user-data.rst:110
+msgid "base64 formated:"
+msgstr ""
+
+#: ../../virtual_machines/user-data.rst:116
+msgid "Refer to `Cloud-Init CloudStack datasource <http://cloudinit.readthedocs.org/en/latest/topics/datasources.html#cloudstack>`_ documentation for latest capabilities. Cloud-Init and Cloud-Init CloudStack datasource are not supported by Apache CloudStack community."
+msgstr ""
+
http://git-wip-us.apache.org/repos/asf/cloudstack-docs-admin/blob/a6b15cb9/source/locale/zh_CN/LC_MESSAGES/accounts.po
----------------------------------------------------------------------
diff --git a/source/locale/zh_CN/LC_MESSAGES/accounts.po b/source/locale/zh_CN/LC_MESSAGES/accounts.po
index 2d96d83..58e1868 100644
--- a/source/locale/zh_CN/LC_MESSAGES/accounts.po
+++ b/source/locale/zh_CN/LC_MESSAGES/accounts.po
@@ -1,265 +1,383 @@
# SOME DESCRIPTIVE TITLE.
# Copyright (C)
-# This file is distributed under the same license as the Apache CloudStack Administration Documentation package.
-#
+# This file is distributed under the same license as the Apache CloudStack
+# Administration Documentation package.
+#
# Translators:
msgid ""
msgstr ""
"Project-Id-Version: Apache CloudStack Administration RTD\n"
"Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2014-06-30 12:52+0200\n"
+"POT-Creation-Date: 2016-08-22 13:55+0200\n"
"PO-Revision-Date: 2014-06-30 12:03+0000\n"
"Last-Translator: FULL NAME <EM...@ADDRESS>\n"
-"Language-Team: Chinese (China) (http://www.transifex.com/projects/p/apache-cloudstack-administration-rtd/language/zh_CN/)\n"
+"Language-Team: Chinese (China) (http://www.transifex.com/projects/p"
+"/apache-cloudstack-administration-rtd/language/zh_CN/)\n"
"MIME-Version: 1.0\n"
-"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Type: text/plain; charset=utf-8\n"
"Content-Transfer-Encoding: 8bit\n"
-"Language: zh_CN\n"
-"Plural-Forms: nplurals=1; plural=0;\n"
+"Generated-By: Babel 2.3.4\n"
-# bdc151e73be141a8ad0b4190c3102939
#: ../../accounts.rst:18
-msgid "Managing Accounts, Users and Domains"
+#, fuzzy
+msgid "Managing Roles, Accounts, Users and Domains"
msgstr "\u7ba1\u7406\u8d26\u6237\uff0c\u7528\u6237\u548c\u57df"
-# a49422e951994e72894009f0fc5cc963
#: ../../accounts.rst:21
-msgid "Accounts, Users, and Domains"
+#, fuzzy
+msgid "Roles, Accounts, Users, and Domains"
msgstr "\u8d26\u6237\uff0c\u7528\u6237\uff0c\u57df"
-# 7316ca3f637249cbbf2f29bd75791600
#: ../../accounts.rst:24
+msgid "Roles"
+msgstr ""
+
+#: ../../accounts.rst:26
+msgid ""
+"A role represents a set of allowed functions. All CloudStack accounts "
+"have a role attached to them that enforce access rules on them to be "
+"allowed or disallowed to make an API request. Typically there are four "
+"default roles: root admin, resource admin, domain admin and user."
+msgstr ""
+
+#: ../../accounts.rst:33
msgid "Accounts"
msgstr "\u8d26\u6237"
-# 7544ce31af194b279c9dcfb7ae37d3cc
-#: ../../accounts.rst:26
+#: ../../accounts.rst:35
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."
+"department in a large organization. Multiple users can exist in an "
+"account."
msgstr "\u4e00\u4e2a\u8d26\u6237\u901a\u5e38\u4ee3\u8868\u4e00\u4e2a\u5ba2\u6237\u7684\u670d\u52a1\u63d0\u4f9b\u8005\u6216\u4e00\u4e2a\u5927\u7ec4\u7ec7\u4e2d\u7684\u4e00\u4e2a\u90e8\u95e8\u3002\u4e00\u4e2a\u8d26\u6237\u53ef\u5b58\u5728\u591a\u4e2a\u7528\u6237\u3002"
-# e758840629a8483ba31892ff437911e1
-#: ../../accounts.rst:32
+#: ../../accounts.rst:41
msgid "Domains"
msgstr "\u57df"
-# 3e28d2a36b0642c08a698f6a4426e72c
-#: ../../accounts.rst:34
+#: ../../accounts.rst:43
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."
+"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 "\u5e10\u6237\u901a\u5e38\u6309\u57df\u8fdb\u884c\u5206\u7ec4\u3002\u57df\u4e2d\u7ecf\u5e38\u5305\u542b\u591a\u4e2a\u8d26\u6237\uff0c\u8fd9\u4e9b\u8d26\u6237\u95f4\u5b58\u5728\u4e00\u4e9b\u903b\u8f91\u4e0a\u5173\u7cfb\u548c\u4e00\u7cfb\u5217\u8be5\u57df\u548c\u5176\u5b50\u57df\u4e0b\u7684\u59d4\u6d3e\u7684\u7ba1\u7406\u5458\uff08\u8fd9\u6bb5\u7684\u610f\u601d\u5c31\u662f\u8bf4\u5728\u903b\u8f91\u4e0a\u57df\u4e0b\u53ef\u4ee5\u6709\u7ba1\u7406\u5458\uff0c\u5b50\u57df\u4e0b\u4e5f\u53ef\u4ee5\u6709\u7ba1\u7406\u5458\uff09\u3002\u6bd4\u5982\uff0c\u4e00\u4e2a\u670d\u52a1\u63d0\u4f9b\u5546\u53ef\u6709\u591a\u4e2a\u5206\u9500\u5546\u8fd9\u6837\u7684\u670d\u52a1\u63d0\u4f9b\u5546\u5c31\u80fd\u4e3a\u6bcf\u4e00\u4e2a\u5206\u9500\u5546\u521b\u5efa\u4e00\u4e2a\u57df"
-# 79060520f2e046868f58925f3f2efc01
-#: ../../accounts.rst:40
+#: ../../accounts.rst:49
msgid ""
"For each account created, the Cloud installation creates three different "
-"types of user accounts: root administrator, domain administrator, and user."
+"types of user accounts: root administrator, domain administrator, and "
+"user."
msgstr "\u5bf9\u4e8e\u6bcf\u4e2a\u8d26\u6237\u7684\u521b\u5efa,Cloud\u7684\u5b89\u88c5\u8fc7\u7a0b\u4e2d\u521b\u5efa\u4e86\u4e09\u79cd\u4e0d\u540c\u7c7b\u578b\u7684\u7528\u6237\u8d26\u6237\uff1a\u6839\u7ba1\u7406\u5458\uff0c\u57df\u7ba1\u7406\u5458\uff0c\u666e\u901a\u7528\u6237\u3002"
-# 341bf7792d884c2d8180600a07351f62
-#: ../../accounts.rst:46
+#: ../../accounts.rst:55
msgid "Users"
msgstr "\u666e\u901a\u7528\u6237"
-# 8efee3ca63e44a4098ff5086e58f1249
-#: ../../accounts.rst:48
+#: ../../accounts.rst:57
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. 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 "\u7528\u6237\u5c31\u50cf\u662f\u8d26\u6237\u7684\u522b\u540d\u3002\u5728\u540c\u4e00\u8d26\u6237\u4e0b\u7684\u7528\u6237\u5f7c\u6b64\u4e4b\u95f4\u5e76\u975e\u9694\u79bb\u7684\u3002\u4f46\u662f\u4ed6\u4eec\u4e0e\u4e0d\u540c\u8d26\u6237\u4e0b\u7684\u7528\u6237\u662f\u76f8\u4e92\u9694\u79bb\u7684\u3002\u5927\u591a\u6570\u5b89\u88c5\u4e0d\u9700\u8981\u7528\u6237\u7684\u8868\u9762\u6982\u5ff5\uff1b\u4ed6\u4eec\u53ea\u662f\u6bcf\u4e00\u4e2a\u5e10\u6237\u7684\u7528\u6237\u3002\u540c\u4e00\u7528\u6237\u4e0d\u80fd\u5c5e\u4e8e\u591a\u4e2a\u5e10\u6237\u3002"
-# 67a573904306470f87a1f3f6ad52a15f
-#: ../../accounts.rst:54
+#: ../../accounts.rst:63
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."
+"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 "\u591a\u4e2a\u8d26\u6237\u4e2d\u7684\u7528\u6237\u540d\u5728\u57df\u4e2d\u5e94\u8be5\u662f\u552f\u4e00\u7684\u3002\u76f8\u540c\u7684\u7528\u6237\u540d\u80fd\u5728\u5176\u4ed6\u7684\u57df\u4e2d\u5b58\u5728\uff0c\u5305\u62ec\u5b50\u57df\u3002\u57df\u540d\u53ea\u6709\u5728\u5168\u8def\u5f84\u540d\u552f\u4e00\u7684\u65f6\u5019\u624d\u80fd\u91cd\u590d\u3002\u6bd4\u5982\uff0c\u4f60\u80fd\u521b\u5efa\u4e00\u4e2aroot/d1\uff0c\u4e5f\u53ef\u4ee5\u521b\u5efaroot/foo/d1\u548croot/sales/d1\u3002"
-# af85977a7aeb4aff9010bde059e08b23
-#: ../../accounts.rst:59
+#: ../../accounts.rst:68
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."
+"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 "\u7ba1\u7406\u5458\u5728\u7cfb\u7edf\u4e2d\u662f\u62e5\u6709\u7279\u6743\u7684\u8d26\u6237\u3002\u53ef\u80fd\u6709\u591a\u4e2a\u7ba1\u7406\u5458\u5728\u7cfb\u7edf\u4e2d\uff0c\u7ba1\u7406\u5458\u80fd\u521b\u5efa\u5220\u9664\u5176\u4ed6\u7ba1\u7406\u5458\uff0c\u5e76\u4e14\u4fee\u6539\u7cfb\u7edf\u4e2d\u4efb\u610f\u7528\u6237\u7684\u5bc6\u7801\u3002"
-# 8613eb42958647fba87ae1b922d58740
-#: ../../accounts.rst:66
+#: ../../accounts.rst:75
msgid "Domain Administrators"
msgstr "\u57df\u7ba1\u7406\u5458"
-# 901efdb2c8554033b865587a48a319f9
-#: ../../accounts.rst:68
+#: ../../accounts.rst:77
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."
+"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 "\u57df\u7ba1\u7406\u5458\u53ef\u4ee5\u5bf9\u5c5e\u4e8e\u8be5\u57df\u7684\u7528\u6237\u8fdb\u884c\u7ba1\u7406\u64cd\u4f5c\u3002\u57df\u7ba1\u7406\u5458\u5728\u7269\u7406\u670d\u52a1\u5668\u6216\u5176\u4ed6\u57df\u4e2d\u4e0d\u53ef\u89c1\u3002"
-# 5922a532b5814e479301a7d697eb8854
-#: ../../accounts.rst:74
+#: ../../accounts.rst:83
msgid "Root Administrator"
msgstr "\u6839\u7ba1\u7406\u5458"
-# 20be104d0a134bab92309e774b538dd4
-#: ../../accounts.rst:76
+#: ../../accounts.rst:85
msgid ""
-"Root administrators have complete access to the system, including managing "
-"templates, service offerings, customer care administrators, and domains"
+"Root administrators have complete access to the system, including "
+"managing templates, service offerings, customer care administrators, and "
+"domains"
msgstr "\u6839\u7ba1\u7406\u5458\u62e5\u6709\u7cfb\u7edf\u5b8c\u5168\u8bbf\u95ee\u6743\u9650\uff0c\u5305\u62ec\u7ba1\u7406\u6a21\u677f\uff0c\u670d\u52a1\u65b9\u6848\uff0c\u5ba2\u6237\u670d\u52a1\u7ba1\u7406\u5458\u548c\u57df\u3002"
-# 7f9e7eaa9c5b4eaba5575b81514d4040
-#: ../../accounts.rst:82
+#: ../../accounts.rst:91
msgid "Resource Ownership"
msgstr "\u8d44\u6e90\u6240\u6709\u6743"
-# 3fad6f5edfb34464b707419ce6b7b4a6
-#: ../../accounts.rst:84
-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 "\u8d44\u6e90\u5c5e\u4e8e\u5e10\u6237\uff0c\u800c\u4e0d\u662f\u5e10\u6237\u4e2d\u7684\u5355\u4e2a\u7528\u6237\u3002\u4f8b\u5982\uff0c\u8d26\u5355\u3001\u8d44\u6e90\u9650\u5236\u7b49\u7531\u5e10\u6237\u7ef4\u62a4\uff0c\u800c\u4e0d\u662f\u7528\u6237\u7ef4\u62a4\u3002\u7528\u6237\u6709\u6743\u9650\u64cd\u4f5c\u4efb\u4f55\u5728\u5e10\u6237\u4e2d\u63d0\u4f9b\u7684\u8d44\u6e90\u3002\u6743\u9650\u6709\u89d2\u8272\u51b3\u5b9a\u3002\u6839\u7ba1\u7406\u5458\u901a\u8fc7\u4f7f\u7528assignVirtualMachine API\u53ef\u4ee5\u5c06\u4efb\u4f55\u865a\u62df\u673a\u7684\u6240\u6709\u6743\u4ece\u4e00\u4e2a\u5e10\u6237\u8c03\u6574\u5230\u53e6\u4e00\u4e2a\u5e10\u6237\u3002\u57df\u6216\u5b50\u57df\u7ba1\u7406\u5458\u53ef\u4ee5\u5bf9\u57df\u4e2d\u7684VMs\u505a\u540c\u6837\u7684\u64cd\u4f5c\uff0c\u5305\u62ec\u5b50\u57df\u3002"
-
-# f25ec45041cd435d83eaf32720407dd4
-#: ../../accounts.rst:96
+#: ../../accounts.rst:93
+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 ""
+"\u8d44\u6e90\u5c5e\u4e8e\u5e10\u6237\uff0c\u800c\u4e0d\u662f\u5e10\u6237\u4e2d\u7684\u5355\u4e2a\u7528\u6237\u3002\u4f8b\u5982\uff0c\u8d26\u5355\u3001\u8d44\u6e90\u9650\u5236\u7b49\u7531\u5e10\u6237\u7ef4\u62a4\uff0c\u800c\u4e0d\u662f\u7528\u6237\u7ef4\u62a4\u3002\u7528\u6237\u6709\u6743\u9650\u64cd\u4f5c\u4efb\u4f55\u5728\u5e10\u6237\u4e2d\u63d0\u4f9b\u7684\u8d44\u6e90\u3002\u6743\u9650\u6709\u89d2\u8272\u51b3\u5b9a\u3002\u6839\u7ba1\u7406\u5458\u901a\u8fc7\u4f7f\u7528assignVirtualMachine"
+" API\u53ef\u4ee5\u5c06\u4efb\u4f55\u865a\u62df\u673a\u7684\u6240\u6709\u6743\u4ece\u4e00\u4e2a\u5e10\u6237\u8c03\u6574\u5230\u53e6\u4e00\u4e2a\u5e10\u6237\u3002\u57df\u6216\u5b50\u57df\u7ba1\u7406\u5458\u53ef\u4ee5\u5bf9\u57df\u4e2d\u7684VMs\u505a\u540c\u6837\u7684\u64cd\u4f5c\uff0c\u5305\u62ec\u5b50\u57df\u3002"
+
+#: ../../accounts.rst:105
+msgid "Using Dynamic Roles"
+msgstr ""
+
+#: ../../accounts.rst:107
+msgid ""
+"In addition to the four default roles, the dynamic role-based API checker"
+" feature allows CloudStack root admins to create new roles with "
+"customized permissions. The allow/deny rules can be configured "
+"dynamically during runtime without restarting the management server(s)."
+msgstr ""
+
+#: ../../accounts.rst:112
+msgid ""
+"For backward compatiblity, all roles resolve to one of the four role "
+"types: admin, resource admin, domain admin and user. A new role can be "
+"created using the roles tab in the UI and specifying a name, a role type "
+"and optionally a description."
+msgstr ""
+
+#: ../../accounts.rst:117
+msgid ""
+"Role specific rules can be configured through the rules tab on role "
+"specific details page. A rule is either an API name or a wildcard string "
+"that are one of allow or deny permission and optionally a description."
+msgstr ""
+
+#: ../../accounts.rst:121
+msgid ""
+"When a user makes an API request, the backend checks the requested API "
+"against configured rules (in the order the rules were configured) for the"
+" caller user-account's role. It will iterate through the rules and would "
+"allow the API request if the API matches an allow rule, else if it "
+"matches a deny rule it would deny the request. Next, if the request API "
+"fails to match any of the configured rules it would allow if the "
+"requested API's default authorized annotaions allow that user role type "
+"and finally deny the user API request if it fails to be explicitly "
+"allowed/denied by the role permission rules or the default API authorize "
+"annotations. Note: to avoid root admin being locked out of the system, "
+"all root admin accounts are allowed all APIs."
+msgstr ""
+
+#: ../../accounts.rst:132
+msgid ""
+"The dynamic-roles feature is enabled by default only for all new "
+"CloudStack installations since version `4.9.x "
+"<https://cwiki.apache.org/confluence/display/CLOUDSTACK/Dynamic+Role+Based+API+Access+Checker+for+CloudStack>`_."
+msgstr ""
+
+#: ../../accounts.rst:135
+msgid ""
+"After an upgrade, existing deployments can be migrated to use this "
+"feature by running a migration tool by the CloudStack admin. The "
+"migration tool is located at ``/usr/share/cloudstack-common/scripts/util"
+"/migrate-dynamicroles.py``."
+msgstr ""
+
+#: ../../accounts.rst:139
+msgid ""
+"During migration, this tool enables an internal flag in the database, "
+"copies existing static role-based rules from provided commands.properties"
+" file (typically at ``/etc/cloudstack/management/commands.properties``) "
+"to the database and renames the commands.properties file (typically to "
+"/etc/cloudstack/management/commands.properties.deprecated). The migration"
+" process does not require restarting the management server(s)."
+msgstr ""
+
+#: ../../accounts.rst:146
+msgid "Usage: ``migrate-dynamicroles.py`` [options] [-h for help]"
+msgstr ""
+
+#: ../../accounts.rst:148
+msgid "Options:"
+msgstr ""
+
+#: ../../accounts.rst:151
+msgid "The name of the database, default: cloud"
+msgstr ""
+
+#: ../../accounts.rst:153
+msgid "User name a MySQL user with privileges on cloud database, default: cloud"
+msgstr ""
+
+#: ../../accounts.rst:155
+msgid "Password of a MySQL user with privileges on cloud database"
+msgstr ""
+
+#: ../../accounts.rst:157
+msgid "Host or IP of the MySQL server"
+msgstr ""
+
+#: ../../accounts.rst:159
+msgid "Host or IP of the MySQL server, default: 3306"
+msgstr ""
+
+#: ../../accounts.rst:161
+msgid ""
+"The commands.properties file, default: "
+"/etc/cloudstack/management/commands.properties"
+msgstr ""
+
+#: ../../accounts.rst:163
+msgid "Dry run and debug operations this tool will perform"
+msgstr ""
+
+#: ../../accounts.rst:166
+msgid "Example:"
+msgstr ""
+
+#: ../../accounts.rst:168
+msgid ""
+"sudo python /usr/share/cloudstack-common/scripts/util/migrate-"
+"dynamicroles.py -u cloud -p cloud -h localhost -p 3006 -f "
+"/etc/cloudstack/management/commands.properties"
+msgstr ""
+
+#: ../../accounts.rst:170
+msgid ""
+"If you've multiple management servers, remove or rename the "
+"commands.properties file on all management servers typically in "
+"/etc/cloudstack/management path, after running the migration tool for the"
+" first management server"
+msgstr ""
+
+#: ../../accounts.rst:176
msgid "Dedicating Resources to Accounts and Domains"
msgstr "\u7ed9\u5e10\u6237\u548c\u57df\u5206\u914d\u4e13\u7528\u8d44\u6e90"
-# 8a6427fc034647e681a14ca03224406c
-#: ../../accounts.rst:98
+#: ../../accounts.rst:178
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."
+"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 "\u6839\u7ba1\u7406\u5458\u53ef\u4ee5\u5c06\u8d44\u6e90\u5206\u914d\u7ed9\u6307\u5b9a\u7684\u57df\u6216\u4e3a\u4e86\u4fdd\u8bc1\u989d\u5916\u7684\u5b89\u5168\u6216\u6027\u80fd\u4ece\u800c\u9700\u8981\u5355\u72ec\u57fa\u7840\u67b6\u6784\u5e10\u6237\u3002\u4e3a\u4e86\u4e00\u4e2a\u6307\u5b9a\u7684\u57df\u6216\u8d26\u53f7\uff0c\u533a\u57df\u3001\u673a\u67b6\u3001\u7fa4\u96c6\u6216\u8005\u4e3b\u673a\u53ef\u4ee5\u88ab\u6839\u7ba1\u7406\u5458\u4fdd\u7559\u3002\u53ea\u6709\u57df\u6216\u5b83\u7684\u5b50\u57df\u4e2d\u7684\u7528\u6237\u53ef\u4ee5\u4f7f\u7528\u8fd9\u4e2a\u57fa\u7840\u67b6\u6784\u3002\u6bd4\u5982\uff0c\u53ea\u6709\u57df\u4e2d\u7684\u7528\u6237\u53ef\u4ee5\u5728\u5176\u4e2d\u7684\u533a\u57df\u4e2d\u521b\u5efa\u6765\u5bbe\u865a\u673a\u3002"
-# 13b20e92d1144d5da1089384a9ce4e59
-#: ../../accounts.rst:106
+#: ../../accounts.rst:186
msgid "There are several types of dedication available:"
msgstr "\u8fd9\u91cc\u6709\u51e0\u79cd\u6709\u6548\u7684\u5206\u914d\u65b9\u5f0f\uff1a"
-# a62e7433baeb444386932b41fe5601fa
-#: ../../accounts.rst:108
+#: ../../accounts.rst:188
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."
+"account or domain by the root administrator during initial deployment and"
+" configuration."
msgstr "\u660e\u786e\u7684\u4e13\u7528\u3002\u6839\u7ba1\u7406\u5458\u5728\u521d\u59cb\u90e8\u7f72\u548c\u914d\u7f6e\u671f\u95f4\u7ed9\u4e00\u4e2a\u5e10\u6237\u6216\u8005\u57df\u5206\u914d\u4e86\u4e00\u4e2a\u533a\u57df\u3001\u673a\u67b6\u3001\u7fa4\u96c6\u6216\u8005\u4e3b\u673a\u3002"
-# 29fbffa86cfd49b4aa29ea7d373eaa03
-#: ../../accounts.rst:112
+#: ../../accounts.rst:192
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."
+"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 "\u4e25\u683c\u7684\u6f5c\u5728\u4e13\u7528\uff1a\u4e00\u4e2a\u4e3b\u673a\u7981\u6b62\u901a\u8fc7\u591a\u4e2a\u8d26\u53f7\u5171\u4eab\u3002\u4f8b\u5982\uff0c\u4e25\u683c\u79c1\u81ea\u5171\u4eab\u5bf9\u4e8e\u90e8\u7f72\u7684\u67d0\u4e9b\u5e94\u7528\u662f\u6709\u7528\u5904\u7684\uff0c\u50cf\u6ca1\u6709\u8f6f\u4ef6\u6388\u6743\u4e3b\u673a\u4e0d\u80fd\u5728\u4e0d\u540c\u8d26\u53f7\u95f4\u8fdb\u884c\u684c\u9762\u5171\u4eab\u3002"
-# a821acd0f71541708e12788d2fbc5d75
-#: ../../accounts.rst:118
+#: ../../accounts.rst:198
msgid ""
"Preferred implicit dedication. The VM will be deployed in dedicated "
"infrastructure if possible. Otherwise, the VM can be deployed in shared "
"infrastructure."
msgstr "\u4f18\u5148\u7684\u6f5c\u5728\u4e13\u7528\u3002\u5982\u679c\u53ef\u4ee5\u7684\u8bdd\uff0cVM\u4f1a\u88ab\u90e8\u7f72\u5728\u4e13\u7528\u7684\u57fa\u7840\u67b6\u6784\u4e2d\u3002\u5426\u5219\uff0cVM\u53ef\u88ab\u90e8\u7f72\u5728\u5171\u4eab\u57fa\u7840\u67b6\u6784\u4e2d\u3002"
-# b498c9fe36a94f2588d7a9e4494a761d
-#: ../../accounts.rst:124
+#: ../../accounts.rst:204
msgid "How to Dedicate a Zone, Cluster, Pod, or Host to an Account or Domain"
msgstr "\u5982\u4f55\u7ed9\u5e10\u6237\u6216\u8005\u57df\u6307\u5b9a\u4e00\u4e2a\u533a\u57df\u3001\u7fa4\u96c6\u3001\u673a\u67b6\u6216\u8005\u4e3b\u673a"
-# 62ce22c4d6f346b79218ff7a937ee3e2
-#: ../../accounts.rst:126
+#: ../../accounts.rst:206
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."
+"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 "\u5bf9\u4e8e\u660e\u786e\u7684\u4e13\u7528\uff1a\u5f53\u90e8\u7f72\u4e00\u4e2a\u65b0\u7684\u533a\u57df\u3001\u673a\u67b6\u3001\u7fa4\u96c6\u6216\u8005\u4e3b\u673a\u7684\u65f6\u5019\uff0c\u6839\u7ba1\u7406\u5458\u53ef\u4ee5\u70b9\u51fbDedicated\u9009\u6846\uff0c\u7136\u540e\u9009\u62e9\u57df\u6216\u8005\u5e10\u6237\u6765\u62e5\u6709\u8fd9\u4e9b\u8d44\u6e90\u3002"
-# 9dfe3b7a9e87411d9694c32c5e4f891e
-#: ../../accounts.rst:130
+#: ../../accounts.rst:210
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 "\u5bf9\u4e8e\u660e\u786e\u7684\u4e13\u7528\u4e00\u4e2a\u5df2\u5b58\u5728\u7684\u533a\u57df\u3001\u673a\u67b6\u3001\u7fa4\u96c6\u6216\u8005\u4e3b\u673a\uff1a\u4f7f\u7528\u6839\u7ba1\u7406\u5458\u767b\u5f55\uff0c\u5728UI\u4e2d\u627e\u5230\u8d44\u6e90\uff0c\u7136\u540e\u70b9\u51fbDedicate\u6309\u94ae\u3002|button to dedicate a zone, pod,cluster, or host|"
+"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 ""
+"\u5bf9\u4e8e\u660e\u786e\u7684\u4e13\u7528\u4e00\u4e2a\u5df2\u5b58\u5728\u7684\u533a\u57df\u3001\u673a\u67b6\u3001\u7fa4\u96c6\u6216\u8005\u4e3b\u673a\uff1a\u4f7f\u7528\u6839\u7ba1\u7406\u5458\u767b\u5f55\uff0c\u5728UI\u4e2d\u627e\u5230\u8d44\u6e90\uff0c\u7136\u540e\u70b9\u51fbDedicate\u6309\u94ae\u3002|button to "
+"dedicate a zone, pod,cluster, or host|"
-# 90707af3ed2b4e6fa7875e9bdd890252
-#: ../../accounts.rst:134
+#: ../../accounts.rst:214
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."
+"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 "\u5bf9\u4e8e\u9690\u5f0f\u7684\u4e13\u7528\uff1a\u7ba1\u7406\u5458\u521b\u5efa\u7684\u8ba1\u7b97\u670d\u52a1\u65b9\u6848\u548c\u5728\u90e8\u7f72\u89c4\u5212\u533a\u57df\u9009\u62e9ImplicitDedicationPlanner\u3002\u7136\u540e\u5728\u89c4\u5212\u6a21\u578b\u4e2d\uff0c\u7ba1\u7406\u5458\u6309\u7167\u662f\u5426\u5141\u8bb8\u4e00\u4e9b\u4eba\u5f53\u6ca1\u6709\u4e13\u7528\u8d44\u6e90\u53ef\u7528\u7684\u65f6\u5019\u4f7f\u7528\u5171\u4eab\u8d44\u6e90\u6765\u9009\u62e9\u4e25\u683c\u7684\u6216\u8005\u4f18\u5148\u7684\u3002\u65e0\u8bba\u4f55\u65f6\uff0c\u7528\u6237\u57fa\u4e8e\u8fd9\u4e2a\u670d\u52a1\u65b9\u6848\u521b\u5efa\u7684VM\u90fd\u4f1a\u4f4d\u4e8e\u4e13\u7528\u4e3b\u673a\u3002"
-# fda3697ce3a4454da72edbe9f02b3564
-#: ../../accounts.rst:144
+#: ../../accounts.rst:224
msgid "How to Use Dedicated Hosts"
msgstr "\u5982\u4f55\u4f7f\u7528\u4e13\u7528\u4e3b\u673a"
-# cfd0e245a5a2498b9fa7c89160957ffe
-#: ../../accounts.rst:146
+#: ../../accounts.rst:226
msgid ""
"To use an explicitly dedicated host, use the explicit-dedicated type of "
"affinity group (see `\u201cAffinity Groups\u201d <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 "\u8981\u4f7f\u7528\u660e\u786e\u4e13\u7528\u4e3b\u673a\uff0c\u5728\u5173\u8054\u7ec4 (\u53c2\u9605 `\u201c\u5173\u8054\u7ec4\u201d <virtual_machines.html#affinity-groups>`_)\u4e2d\u9009\u62e9explicit-dedicated \u7c7b\u578b\u3002\u6bd4\u5982\uff0c\u5f53\u521b\u5efa\u65b0VM\u7684\u65f6\u5019\uff0c\u7ec8\u7aef\u7528\u6237\u53ef\u4ee5\u9009\u62e9\u5c06\u5176\u8fd0\u884c\u5728\u4e13\u7528\u57fa\u7840\u67b6\u6784\u4e0a\u3002\u5982\u679c\u4e00\u4e9b\u57fa\u7840\u67b6\u6784\u5df2\u7ecf\u88ab\u5206\u914d\u7ed9\u4e13\u7528\u7684\u7528\u6237\u5e10\u53f7\u6216\u57df\uff0c\u90a3\u4e48\u8fd9\u4e2a\u64cd\u4f5c\u624d\u80fd\u6210\u529f\u3002"
+"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 ""
+"\u8981\u4f7f\u7528\u660e\u786e\u4e13\u7528\u4e3b\u673a\uff0c\u5728\u5173\u8054\u7ec4 (\u53c2\u9605 `\u201c\u5173\u8054\u7ec4\u201d <virtual_machines.html#affinity-groups>`_"
+")\u4e2d\u9009\u62e9explicit-dedicated "
+"\u7c7b\u578b\u3002\u6bd4\u5982\uff0c\u5f53\u521b\u5efa\u65b0VM\u7684\u65f6\u5019\uff0c\u7ec8\u7aef\u7528\u6237\u53ef\u4ee5\u9009\u62e9\u5c06\u5176\u8fd0\u884c\u5728\u4e13\u7528\u57fa\u7840\u67b6\u6784\u4e0a\u3002\u5982\u679c\u4e00\u4e9b\u57fa\u7840\u67b6\u6784\u5df2\u7ecf\u88ab\u5206\u914d\u7ed9\u4e13\u7528\u7684\u7528\u6237\u5e10\u53f7\u6216\u57df\uff0c\u90a3\u4e48\u8fd9\u4e2a\u64cd\u4f5c\u624d\u80fd\u6210\u529f\u3002"
-# 86abbd3940f34e96a1ad71a01dc6339d
-#: ../../accounts.rst:155
+#: ../../accounts.rst:235
msgid "Behavior of Dedicated Hosts, Clusters, Pods, and Zones"
msgstr "\u4e13\u7528\u4e3b\u673a\u3001\u7fa4\u96c6\u3001\u673a\u67b6\u548c\u533a\u57df\u7684\u884c\u4e3a"
-# a9963e63da4e48f2a2b7b7fdad96ba29
-#: ../../accounts.rst:157
+#: ../../accounts.rst:237
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."
+"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 "\u7ba1\u7406\u5458\u53ef\u4ee5\u5c06VMs\u4ece\u4e13\u7528\u4e3b\u673a\u4e0a\u8fc1\u79fb\u5230\u4efb\u4f55\u60f3\u8981\u7684\u5730\u65b9\uff0c\u4e0d\u7ba1\u76ee\u6807\u4e3b\u673a\u662f\u4e0d\u540c\u5e10\u53f7/\u57df\u4e13\u7528\u7684\u8fd8\u662f\u5171\u4eab\u7684\u4e3b\u673a(\u4e0d\u5bf9\u4efb\u4f55\u7279\u6b8a\u5e10\u53f7\u6216\u57df\u4e13\u7528)\u3002CloudStack\u5c06\u751f\u6210\u4e00\u4e2a\u8b66\u544a\uff0c\u4e0d\u8fc7\u64cd\u4f5c\u8fd8\u662f\u5141\u8bb8\u7684\u3002"
-# a9a8992734b0490aac5bd5e5efa45483
-#: ../../accounts.rst:163
+#: ../../accounts.rst:243
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."
+"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 "\u4e13\u7528\u4e3b\u673a\u53ef\u7528\u4e3b\u673a\u6807\u7b7e\u8fde\u63a5\u3002\u5982\u679c\u540c\u65f6\u9700\u8981\u4e3b\u673a\u6807\u7b7e\u548c\u4e13\u7528\uff0c\u90a3\u4e48VM\u5c06\u53ea\u4f1a\u5728\u5339\u914d\u6240\u6709\u9700\u6c42\u7684\u4e3b\u673a\u4e0a\u8fd0\u884c\u3002\u5982\u679c\u6ca1\u6709\u4e13\u7528\u8d44\u6e90\u53ef\u7528\u4e8e\u8fd9\u7c7b\u7528\u6237\uff0c\u90a3\u4e48VM\u5c31\u4e0d\u4f1a\u88ab\u4e0d\u90e8\u7f72\u3002"
-# 694b1842b07049c094a79e240c2db934
-#: ../../accounts.rst:169
+#: ../../accounts.rst:249
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 "
@@ -267,284 +385,592 @@ msgid ""
"dedicate them to a different account or domain."
msgstr "\u5982\u679c\u4f60\u5220\u9664\u4e86\u4e00\u4e2a\u6307\u5b9a\u4e86\u4e13\u7528\u8d44\u6e90\u7684\u5e10\u53f7\u6216\u8005\u57df\uff0c\u90a3\u4e48\u5176\u4e2d\u7684\u4efb\u4f55\u4e3b\u673a\u3001\u7fa4\u96c6\u3001\u673a\u67b6\u548c\u533a\u57df\u5c31\u4f1a\u88ab\u91ca\u653e\u3002\u5b83\u4eec\u4f1a\u53d8\u6210\u53ef\u88ab\u4efb\u4f55\u5e10\u6237\u6216\u8005\u57df\u5171\u4eab\uff0c\u6216\u8005\u7ba1\u7406\u5458\u53ef\u9009\u62e9\u91cd\u65b0\u628a\u5b83\u4eec\u6307\u5b9a\u7ed9\u4e0d\u540c\u7684\u5e10\u53f7\u6216\u57df\u3002"
-# 9676e7d49a4247c0bd41a3d53e7482a1
-#: ../../accounts.rst:174
+#: ../../accounts.rst:254
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."
+"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 "\u7cfb\u7edfVMs\u548c\u865a\u62df\u8def\u7531\u5668\u5f71\u54cd\u4e13\u7528\u4e3b\u673a\u7684\u884c\u4e3a\u3002\u7cfb\u7edfVMs\u548c\u865a\u62df\u8def\u7531\u5668\u7531CloudStack\u7cfb\u7edf\u8d26\u53f7\u62e5\u6709\uff0c\u5e76\u4e14\u5b83\u4eec\u53ef\u5728\u4efb\u4f55\u4e3b\u673a\u4e0a\u90e8\u7f72\u3002\u5b83\u4eec\u4e0d\u4f1a\u4f34\u968f\u7740\u660e\u786e\u4e13\u7528\u4e3b\u673a\u3002\u4e3b\u673a\u4e0a\u7684\u7cfb\u7edf\u865a\u673a\u548c\u865a\u62df\u8def\u7531\u5668\u4f7f\u5176\u4e0d\u518d\u9002\u5408\u4f5c\u4e3a\u4e25\u683c\u7684\u6f5c\u5728\u4e13\u7528\u4e3b\u673a\u3002\u4e3b\u673a\u4e4b\u6240\u4ee5\u4e0d\u80fd\u7528\u4e8e\u4e25\u683c\u7684\u6f5c\u5728\u4e13\u7528\u4e3b\u673a\uff0c\u662f\u56e0\u4e3a\u4e3b\u673a\u5df2\u7ecf\u6709\u9488\u5bf9\u5e10\u53f7(\u9ed8\u8ba4\u7cfb\u7edf\u8d26\u53f7)\u7684VMs\u3002\u5c3d\u7ba1\u5982\u6b64\uff0c\u8fd0\u884c\u7740\u7cfb\u7edfVMs\u6216\u865a\u62df\u8def\u7531\u5668\u7684\u4e3b\u673a\u53ef\u4ee5\u88ab\u7528\u4e8e\u4f18\u5148\u7684\u6f5c\u5728\u4e13\u7528\u3002"
-# c3ac9b9cb46f4fa7b6ea8d96adc7111e
-#: ../../accounts.rst:186
+#: ../../accounts.rst:266
msgid "Using an LDAP Server for User Authentication"
msgstr "\u4f7f\u7528LDAP\u670d\u52a1\u5668\u7528\u4e8e\u7528\u6237\u9a8c\u8bc1"
-# 4c358cdbd0ef4ea8bae9aa240f1b4e4a
-#: ../../accounts.rst:188
+#: ../../accounts.rst:268
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\u2019s 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 "\u4f60\u53ef\u4ee5\u4f7f\u7528\u4e00\u4e2a\u5916\u90e8LDAP\u670d\u52a1\u5668\uff0c\u4f8b\u5982\u5fae\u8f6f\u6d3b\u52a8\u76ee\u5f55\u6216ApacheDS\u8fdb\u884cCloudStack\u7684\u7ec8\u7aef\u7528\u6237\u9a8c\u8bc1\u3002\u4ec5\u4ec5\u4f7f\u7528\u67e5\u8be2\u8fc7\u6ee4\u5668\u6620\u5c04CloudStack\u8d26\u6237\u4e0e\u5bf9\u5e94\u7684LDAP\u5e10\u6237\u3002\u67e5\u8be2\u8fc7\u6ee4\u5668\u662f\u4f7f\u7528\u67e5\u8be2\u8bed\u6cd5\u5199\u7684\u7279\u522b\u7684LDAP\u670d\u52a1\u5668\uff0c\u53ef\u4ee5\u5305\u62ec\u7528CloudStack\u63d0\u4f9b\u7684\u7279\u6b8a\u901a\u914d\u7b26\u5339\u914d\u901a\u7528\u7684\u50cf\u7528\u6237\u7684\u7535\u5b50\u90ae\u4ef6\u5730\u5740\u548c\u540d\u79f0\u8fd9\u79cd\u503c\u3002CloudStack\u5c06\u5728\u5916\u90e8LDAP\u76ee\u5f55\u6811\u4e2d\u4ece\u4e00\u4e2a\u6307\u5b9a\u7684\u57fa\u76ee\u641c\u7d22\u5f55\u5e76\u8fd4\u56de\u4e13\u6709\u540d\u79f0(DN)\u548c\u5bc6\u7801\u5339\u914d\u7528\u6237\u3002\u8fd9\u4e2a\u4fe1\u606f\u4ee5\u53ca\u7ed9\u5b9a\u7684\u5bc6\u7801\u662f\u7528\u4e8e\u9a8c\u8bc1\u7528\u6237\u3002\u3002"
+"You can use an external LDAP server such as Microsoft Active Directory or"
+" ApacheDS to authenticate CloudStack end-users. CloudStack will search "
+"the external LDAP directory tree starting at a specified base directory "
+"and gets user info such as first name, last name, email and username."
+msgstr ""
-# 14c749c7da61408588c8e8cdaa11796c
-#: ../../accounts.rst:199
+#: ../../accounts.rst:273
+msgid ""
+"To authenticate, username and password entered by the user are used. "
+"Cloudstack does a search for a user with the given username. If it "
+"exists, it does a bind request with DN and password."
+msgstr ""
+
+#: ../../accounts.rst:277
+msgid ""
+"To set up LDAP authentication in CloudStack, call the CloudStack API "
+"command ``addLdapConfiguration`` and provide Hostname or IP address and "
+"listening port of the LDAP server. You could configure multiple servers "
+"as well. These are expected to be replicas. If one fails, the next one is"
+" used."
+msgstr ""
+
+#: ../../accounts.rst:283
msgid ""
-"To set up LDAP authentication in CloudStack, call the CloudStack API command"
-" ldapConfig and provide the following:"
-msgstr "\u5728CloudStack\u4e2d\u8bbe\u7f6eLDAP\u9a8c\u8bc1\uff0c\u8c03\u7528CloudStack API\u6307\u4ee4ldapConfig\uff0c\u5e76\u63d0\u4f9b\u5982\u4e0b\uff1a"
+"The following global configurations should also be configured (the "
+"default values are for openldap)"
+msgstr ""
+
+#: ../../accounts.rst:286
+msgid ""
+"``ldap.basedn``: Sets the basedn for LDAP. Ex: "
+"**OU=APAC,DC=company,DC=com**"
+msgstr ""
+
+#: ../../accounts.rst:288
+msgid ""
+"``ldap.bind.principal``, ``ldap.bind.password``: DN and password for a "
+"user who can list all the users in the above basedn. Ex: "
+"**CN=Administrator, OU=APAC, DC=company, DC=com**"
+msgstr ""
+
+#: ../../accounts.rst:292
+msgid ""
+"``ldap.user.object``: object type of users within LDAP. Defaults value is"
+" **user** for AD and **inetorgperson** for openldap."
+msgstr ""
+
+#: ../../accounts.rst:295
+msgid ""
+"``ldap.email.attribute``: email attribute within ldap for a user. Default"
+" value for AD and openldap is **mail**."
+msgstr ""
+
+#: ../../accounts.rst:298
+msgid ""
+"``ldap.firstname.attribute``: firstname attribute within ldap for a user."
+" Default value for AD and openldap is **givenname**."
+msgstr ""
+
+#: ../../accounts.rst:301
+msgid ""
+"``ldap.lastname.attribute``: lastname attribute within ldap for a user. "
+"Default value for AD and openldap is **sn**."
+msgstr ""
+
+#: ../../accounts.rst:304
+msgid ""
+"``ldap.username.attribute``: username attribute for a user within LDAP. "
+"Default value is **SAMAccountName** for AD and **uid** for openldap."
+msgstr ""
+
+#: ../../accounts.rst:309
+msgid "Restricting LDAP users to a group:"
+msgstr ""
+
+#: ../../accounts.rst:311
+msgid ""
+"``ldap.search.group.principle``: this is optional and if set only users "
+"from this group are listed."
+msgstr ""
+
+#: ../../accounts.rst:316
+msgid "LDAP SSL:"
+msgstr ""
+
+#: ../../accounts.rst:318
+msgid ""
+"If the LDAP server requires SSL, you need to enable the below "
+"configurations. Before enabling SSL for LDAP, 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 ""
+
+#: ../../accounts.rst:322
+msgid "``ldap.truststore`` : truststore path"
+msgstr ""
+
+#: ../../accounts.rst:323
+msgid "``ldap.truststore.password`` : truststore password"
+msgstr ""
+
+#: ../../accounts.rst:327
+msgid "LDAP groups:"
+msgstr ""
+
+#: ../../accounts.rst:329
+msgid ""
+"``ldap.group.object``: object type of groups within LDAP. Default value "
+"is group for AD and **groupOfUniqueNames** for openldap."
+msgstr ""
+
+#: ../../accounts.rst:332
+msgid ""
+"``ldap.group.user.uniquemember``: attribute for uniquemembers within a "
+"group. Default value is **member** for AD and **uniquemember** for "
+"openldap."
+msgstr ""
+
+#: ../../accounts.rst:335
+msgid ""
+"Once configured, on Add Account page, you will see an \"Add LDAP "
+"Account\" button which opens a dialog and the selected users can be "
+"imported."
+msgstr ""
+
+#: ../../accounts.rst:342
+msgid ""
+"You could also use api commands: ``listLdapUsers``, ``ldapCreateAccount``"
+" and ``importLdapUsers``."
+msgstr ""
+
+#: ../../accounts.rst:345
+msgid ""
+"Once LDAP is enabled, the users will not be allowed to changed password "
+"directly in cloudstack."
+msgstr ""
+
+#: ../../accounts.rst:353
+#, fuzzy
+msgid "Using a SAML 2.0 Identity Provider for User Authentication"
+msgstr "\u4f7f\u7528LDAP\u670d\u52a1\u5668\u7528\u4e8e\u7528\u6237\u9a8c\u8bc1"
+
+#: ../../accounts.rst:355
+msgid ""
+"You can use a SAML 2.0 Identity Provider with CloudStack for user "
+"authentication. This will require enabling the SAML 2.0 service provider "
+"plugin in CloudStack. To do that first, enable the SAML plugin by setting"
+" ``saml2.enabled`` to ``true`` and restart management server."
+msgstr ""
+
+#: ../../accounts.rst:360
+msgid ""
+"Starting 4.5.2, the SAML plugin uses an authorization workflow where "
+"users should be authorized by an admin using ``authorizeSamlSso`` API "
+"before those users can use Single Sign On against a specific IDP. This "
+"can be done by ticking the enable SAML Single Sign On checkbox and "
+"selecting a IDP when adding or importing users. For existing users, admin"
+" can go to the user's page and click on configure SAML SSO option to "
+"enable/disable SSO for a user and select a Identity Provider. A user can "
+"be authorized to authenticate against only one IDP."
+msgstr ""
+
+#: ../../accounts.rst:368
+msgid ""
+"The CloudStack service provider metadata is accessible using the "
+"``getSPMetadata`` API command, or from the URL http://acs-"
+"server:8080/client/api?command=getSPMetadata where acs-server is the "
+"domain name or IP address of the management server. The IDP administrator"
+" can get the SP metadata from CloudStack and add it to their IDP server."
+msgstr ""
+
+#: ../../accounts.rst:374
+msgid ""
+"To start a SAML 2.0 Single Sign-On authentication, on the login page "
+"users need to select the Identity Provider or Institution/Department they"
+" can authenticate with and click on Login button. This action call the "
+"``samlsso`` API command which will redirect the user to the Identity "
+"Provider's login page. Upon successful authentication, the IdP will "
+"redirect the user to CloudStack. In case a user has multiple user "
+"accounts with the same username (across domains) for the same authorized "
+"IDP, that user would need to specify domainpath after selecting their IDP"
+" server from the dropdown list. By default, users don't need to specify "
+"any domain path. After a user is successfully authenticated by an IDP "
+"server, the SAML authentication plugin finds user accounts whose username"
+" match the username attribute value returned by the SAML authentication "
+"response; it fails only when it finds that there are multiple user "
+"accounts with the same user name for the specific IDP otherwise the "
+"unique useraccount is allowed to proceed and the user is logged into "
+"their account."
+msgstr ""
+
+#: ../../accounts.rst:389
+msgid "Limitations:"
+msgstr ""
+
+#: ../../accounts.rst:391
+msgid ""
+"The plugin uses a user attribute returned by the IDP server in the SAML "
+"response to find and map the authorized user in CloudStack. The default "
+"attribute is `uid`."
+msgstr ""
+
+#: ../../accounts.rst:394
+msgid ""
+"The SAML authentication plugin supports HTTP-Redirect and HTTP-Post "
+"bindings."
+msgstr ""
+
+#: ../../accounts.rst:396
+msgid ""
+"Tested with Shibboleth 2.4, SSOCircle, Microsoft ADFS, OneLogin, Feide "
+"OpenIDP, PingIdentity."
+msgstr ""
+
+#: ../../accounts.rst:399
+msgid "The following global configuration should be configured:"
+msgstr ""
+
+#: ../../accounts.rst:401
+msgid ""
+"``saml2.enabled``: Indicates whether SAML SSO plugin is enabled or not "
+"true. Default is **false**"
+msgstr ""
+
+#: ../../accounts.rst:403
+msgid "``saml2.sp.id``: SAML2 Service Provider Identifier string"
+msgstr ""
+
+#: ../../accounts.rst:405
+msgid ""
+"``saml2.idp.metadata.url``: SAML2 Identity Provider Metadata XML Url or "
+"Filename. If a URL is not provided, it will look for a file in the config"
+" directory /etc/cloudstack/management"
+msgstr ""
+
+#: ../../accounts.rst:407
+msgid ""
+"``saml2.default.idpid``: The default IdP entity ID to use only in case of"
+" multiple IdPs"
+msgstr ""
+
+#: ../../accounts.rst:409
+msgid ""
+"``saml2.sigalg``: The algorithm to use to when signing a SAML request. "
+"Default is SHA1, allowed algorithms: SHA1, SHA256, SHA384, SHA512."
+msgstr ""
+
+#: ../../accounts.rst:411
+msgid ""
+"``saml2.redirect.url``: The CloudStack UI url the SSO should redirected "
+"to when successful. Default is **http://localhost:8080/client**"
+msgstr ""
+
+#: ../../accounts.rst:413
+msgid "``saml2.sp.org.name``: SAML2 Service Provider Organization Name"
+msgstr ""
+
+#: ../../accounts.rst:415
+msgid "``saml2.sp.org.url``: SAML2 Service Provider Organization URL"
+msgstr ""
+
+#: ../../accounts.rst:417
+msgid "``saml2.sp.contact.email``: SAML2 Service Provider Contact Email Address"
+msgstr ""
+
+#: ../../accounts.rst:419
+msgid "``saml2.sp.contact.person``: SAML2 Service Provider Contact Person Name"
+msgstr ""
+
+#: ../../accounts.rst:421
+msgid "``saml2.sp.slo.url``: SAML2 CloudStack Service Provider Single Log Out URL"
+msgstr ""
+
+#: ../../accounts.rst:423
+msgid "``saml2.sp.sso.url``: SAML2 CloudStack Service Provider Single Sign On URL"
+msgstr ""
+
+#: ../../accounts.rst:425
+msgid ""
+"``saml2.user.attribute``: Attribute name to be looked for in SAML "
+"response that will contain the username. Default is **uid**"
+msgstr ""
+
+#: ../../accounts.rst:427
+msgid ""
+"``saml2.timeout``: SAML2 IDP Metadata refresh interval in seconds, "
+"minimum value is set to 300. Default is 1800"
+msgstr ""
+
+# 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\u2019s 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 "\u4f60\u53ef\u4ee5\u4f7f\u7528\u4e00\u4e2a\u5916\u90e8LDAP\u670d\u52a1\u5668\uff0c\u4f8b\u5982\u5fae\u8f6f\u6d3b\u52a8\u76ee\u5f55\u6216ApacheDS\u8fdb\u884cCloudStack\u7684\u7ec8\u7aef\u7528\u6237\u9a8c\u8bc1\u3002\u4ec5\u4ec5\u4f7f\u7528\u67e5\u8be2\u8fc7\u6ee4\u5668\u6620\u5c04CloudStack\u8d26\u6237\u4e0e\u5bf9\u5e94\u7684LDAP\u5e10\u6237\u3002\u67e5\u8be2\u8fc7\u6ee4\u5668\u662f\u4f7f\u7528\u67e5\u8be2\u8bed\u6cd5\u5199\u7684\u7279\u522b\u7684LDAP\u670d\u52a1\u5668\uff0c\u53ef\u4ee5\u5305\u62ec\u7528CloudStack\u63d0\u4f9b\u7684\u7279\u6b8a\u901a\u914d\u7b26\u5339\u914d\u901a\u7528\u7684\u50cf\u7528\u6237\u7684\u7535\u5b50\u90ae\u4ef6\u5730\u5740\u548c\u540d\u79f0\u8fd9\u79cd\u503c\u3002CloudStack\u5c06\u5728\u5916\u90e8LDAP\u76ee\u5f55\u6811\u4e2d\u4ece\u4e00\u4e2a\u6307\u5b9a\u7684\u57fa\u76ee\u641c\u7d22\u5f55\u5e76\u8fd4\u56de\u4e13\u6709\u540d\u79f0(DN)\u548c\u5bc6\u7801\u5339\u914d\u7528\u6237\u3002\u8fd9\u4e2a\u4fe1\u606f\u4ee5\u53ca\u7ed9\u5b9a\u7684\u5bc6\u7801\u662f\u7528\u4e8e\u9a8c\u8bc1\u7528\u6237\u3002\u3002"
+
+# 14c749c7da61408588c8e8cdaa11796c
+#~ msgid ""
+#~ "To set up LDAP authentication in "
+#~ "CloudStack, call the CloudStack API "
+#~ "command ldapConfig and provide the "
+#~ "following:"
+#~ msgstr "\u5728CloudStack\u4e2d\u8bbe\u7f6eLDAP\u9a8c\u8bc1\uff0c\u8c03\u7528CloudStack API\u6307\u4ee4ldapConfig\uff0c\u5e76\u63d0\u4f9b\u5982\u4e0b\uff1a"
# c4708aa56b75423080f17f84ec2a37a4
-#: ../../accounts.rst:202
-msgid "Hostname or IP address and listening port of the LDAP server"
-msgstr "LDAP\u670d\u52a1\u5668\u7684\u4e3b\u673a\u540d\u6216IP\u5730\u5740\u548c\u76d1\u542c\u7aef\u53e3"
+#~ msgid "Hostname or IP address and listening port of the LDAP server"
+#~ msgstr "LDAP\u670d\u52a1\u5668\u7684\u4e3b\u673a\u540d\u6216IP\u5730\u5740\u548c\u76d1\u542c\u7aef\u53e3"
# ff4d11fcc40f4d5c86ce032c3d6e6a76
-#: ../../accounts.rst:204
-msgid "Base directory and query filter"
-msgstr "\u57fa\u672c\u76ee\u5f55\u548c\u67e5\u8be2\u8fc7\u6ee4\u5668"
+#~ msgid "Base directory and query filter"
+#~ msgstr "\u57fa\u672c\u76ee\u5f55\u548c\u67e5\u8be2\u8fc7\u6ee4\u5668"
# 0b5fce75930e49b19cf1d00062c78539
-#: ../../accounts.rst:206
-msgid ""
-"Search user DN credentials, which give CloudStack permission to search on "
-"the LDAP server"
-msgstr "\u641c\u7d22\u7528\u6237DN \u51ed\u8bc1\uff0c\u8fd9\u4e2a\u51ed\u8bc1\u662f\u6388\u4e88CloudStack\u5141\u8bb8\u641c\u7d22LDAP\u670d\u52a1\u5668\u4e0a\u7684\u51ed\u8bc1"
+#~ msgid ""
+#~ "Search user DN credentials, which give"
+#~ " CloudStack permission to search on "
+#~ "the LDAP server"
+#~ msgstr "\u641c\u7d22\u7528\u6237DN \u51ed\u8bc1\uff0c\u8fd9\u4e2a\u51ed\u8bc1\u662f\u6388\u4e88CloudStack\u5141\u8bb8\u641c\u7d22LDAP\u670d\u52a1\u5668\u4e0a\u7684\u51ed\u8bc1"
# c3d66516470141c3af861a4b24f45150
-#: ../../accounts.rst:209
-msgid "SSL keystore and password, if SSL is used"
-msgstr "SSL\u5bc6\u94a5\u5e93\u548c\u5bc6\u7801\uff0c\u5982\u679c\u4f7f\u7528\u4e86SSL"
+#~ msgid "SSL keystore and password, if SSL is used"
+#~ msgstr "SSL\u5bc6\u94a5\u5e93\u548c\u5bc6\u7801\uff0c\u5982\u679c\u4f7f\u7528\u4e86SSL"
# 6e565fd7b02d4a97b86b380e839f129f
-#: ../../accounts.rst:213
-msgid "Example LDAP Configuration Commands"
-msgstr "LDAP\u914d\u7f6e\u547d\u4ee4\u793a\u4f8b"
+#~ msgid "Example LDAP Configuration Commands"
+#~ msgstr "LDAP\u914d\u7f6e\u547d\u4ee4\u793a\u4f8b"
# ee72e29a6b33456684ebcbfd012c075a
-#: ../../accounts.rst:215
-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\u2019s Guide."
-msgstr "\u4e3a\u4e86\u660e\u767d\u672c\u7ae0\u8282\u7684\u793a\u4f8b\uff0c \u4f60\u9700\u8981\u77e5\u9053\u8c03\u7528CloudStack API\u7684\u57fa\u672c\u6982\u5ff5\uff0c\u8fd9\u5728\u5f00\u53d1\u8005\u6587\u6863\u4e2d\u6709\u8bb2\u89e3\u3002"
+#~ 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\u2019s Guide."
+#~ msgstr "\u4e3a\u4e86\u660e\u767d\u672c\u7ae0\u8282\u7684\u793a\u4f8b\uff0c \u4f60\u9700\u8981\u77e5\u9053\u8c03\u7528CloudStack API\u7684\u57fa\u672c\u6982\u5ff5\uff0c\u8fd9\u5728\u5f00\u53d1\u8005\u6587\u6863\u4e2d\u6709\u8bb2\u89e3\u3002"
# 065e58a0d0f74c8d84670251cf00c487
-#: ../../accounts.rst:219
-msgid ""
-"The following shows an example invocation of ldapConfig with an ApacheDS "
-"LDAP server"
-msgstr "\u4ee5\u4e0b\u5c55\u793a\u4e86\u901a\u8fc7ApacheDS LDAP\u670d\u52a1\u5668\u8c03\u7528 ldapConfig\u547d\u4ee4\u7684\u793a\u4f8b"
+#~ msgid ""
+#~ "The following shows an example "
+#~ "invocation of ldapConfig with an "
+#~ "ApacheDS LDAP server"
+#~ msgstr "\u4ee5\u4e0b\u5c55\u793a\u4e86\u901a\u8fc7ApacheDS LDAP\u670d\u52a1\u5668\u8c03\u7528 ldapConfig\u547d\u4ee4\u7684\u793a\u4f8b"
# 31d88144f8004adf8efd11cf7f9db7bd
-#: ../../accounts.rst:226
-msgid ""
-"The command must be URL-encoded. Here is the same example without the URL "
-"encoding:"
-msgstr "\u547d\u4ee4\u8c03\u7528\u7684URL\u5fc5\u987b\u8fdb\u884c\u7f16\u7801. \u8fd9\u91cc\u662f\u4e00\u4e2a\u6ca1\u6709\u8fdb\u884cURL\u7f16\u7801\u7684\u793a\u4f8b\uff1a"
+#~ msgid ""
+#~ "The command must be URL-encoded. "
+#~ "Here is the same example without "
+#~ "the URL encoding:"
+#~ msgstr "\u547d\u4ee4\u8c03\u7528\u7684URL\u5fc5\u987b\u8fdb\u884c\u7f16\u7801. \u8fd9\u91cc\u662f\u4e00\u4e2a\u6ca1\u6709\u8fdb\u884cURL\u7f16\u7801\u7684\u793a\u4f8b\uff1a"
# 884cde7f5dbd499ba1c28ff09380c692
-#: ../../accounts.rst:244
-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 "\u4ee5\u4e0b\u5c55\u793a\u4e86\u4e0e\u6d3b\u52a8\u76ee\u5f55\u7c7b\u4f3c\u7684\u547d\u4ee4\u3002\u8fd9\u91cc\uff0c\u641c\u7d22\u662f\u57fa\u4e8e\u4e00\u4e2a\u516c\u53f8\u7684\u6d4b\u8bd5\u7ec4\uff0c\u7528\u6237\u662f\u6839\u636e\u90ae\u4ef6\u5730\u5740\u8fdb\u884c\u67e5\u627e\u3002"
+#~ 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 "\u4ee5\u4e0b\u5c55\u793a\u4e86\u4e0e\u6d3b\u52a8\u76ee\u5f55\u7c7b\u4f3c\u7684\u547d\u4ee4\u3002\u8fd9\u91cc\uff0c\u641c\u7d22\u662f\u57fa\u4e8e\u4e00\u4e2a\u516c\u53f8\u7684\u6d4b\u8bd5\u7ec4\uff0c\u7528\u6237\u662f\u6839\u636e\u90ae\u4ef6\u5730\u5740\u8fdb\u884c\u67e5\u627e\u3002"
# d2675a267aa34f4ea3fe2bba2300b61c
-#: ../../accounts.rst:252
-msgid ""
-"The next few sections explain some of the concepts you will need to know "
-"when filling out the ldapConfig parameters."
-msgstr "\u63a5\u4e0b\u6765\u7684\u51e0\u4e2a\u7ae0\u8282\u89e3\u91ca\u4e86\u5f53\u586b\u5199ldapConfig\u53c2\u6570\u65f6\u4f60\u9700\u8981\u77e5\u9053\u7684\u4e00\u4e9b\u6982\u5ff5\u3002"
+#~ msgid ""
+#~ "The next few sections explain some "
+#~ "of the concepts you will need to"
+#~ " know when filling out the ldapConfig"
+#~ " parameters."
+#~ msgstr "\u63a5\u4e0b\u6765\u7684\u51e0\u4e2a\u7ae0\u8282\u89e3\u91ca\u4e86\u5f53\u586b\u5199ldapConfig\u53c2\u6570\u65f6\u4f60\u9700\u8981\u77e5\u9053\u7684\u4e00\u4e9b\u6982\u5ff5\u3002"
# befdce0cfd624549844139c917a82bb4
-#: ../../accounts.rst:257
-msgid "Search Base"
-msgstr "\u641c\u7d22\u57fa\u7840\u76ee\u5f55"
+#~ msgid "Search Base"
+#~ msgstr "\u641c\u7d22\u57fa\u7840\u76ee\u5f55"
# 1522f19d5a2a4e35a8bedc5d147a1af1
-#: ../../accounts.rst:259
-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 "LDAP\u67e5\u8be2\u4e0e\u4e00\u4e2aLDAP\u76ee\u5f55\u6811\u4e2d\u7684\u8282\u70b9\u6709\u5173\uff0c\u79f0\u4e4b\u4e3a\u505a\u641c\u7d22\u57fa\u7840\u76ee\u5f55\u3002\u641c\u7d22\u57fa\u7840\u76ee\u5f55\u662f\u76ee\u5f55\u5e93\u4e2d\u7684\u4e00\u7ea7\u7684distinguished name(DN)\uff0c\u5728\u8fd9\u91cc\u80fd\u627e\u5230\u6240\u6709\u7528\u6237\u3002\u7528\u6237\u53ef\u4ee5\u76f4\u5c5e\u4e8e\u6839\u76ee\u5f55\u6216\u8005\u4e00\u4e9b\u5b50\u76ee\u5f55\u3002\u641c\u7d22\u57fa\u7840\u76ee\u5f55\u53ef\u80fd\u662f\u7ec4\u7ec7\u3001\u7ec4\u6216\u8005\u57df\u7528\u6237\u540d\u3002\u7528\u4e8e\u5199DN\u53d8\u91cf\u7684\u8bed\u6cd5\u53d6\u51b3\u4e8e\u4f60\u6240\u4f7f\u7528\u7684LDAP\u670d\u52a1\u3002\u518d\u6df1\u5165\u5168\u9762\u7684\u8ba8\u8bbadistinguished names\u8d85\u51fa\u4e86\u6211\u4eec\u6587\u6863\u7684\u8303\u56f4\u3002\u4ee5\u4e0b\u8868\u683c\u4e2d\u5c55\u793a\u4e86\u4e00\u4e9b\u5728\u641c\u7d22\u57fa\u7840\u76ee\u5f55\u4e2d\u67e5\u627e\u6d4b\u8bd5\u90e8\u95e8\u4e2d\u7528\u6237\u7684\u793a\u4f8b\u3002"
+#~ 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 ""
+#~ "LDAP\u67e5\u8be2\u4e0e\u4e00\u4e2aLDAP\u76ee\u5f55\u6811\u4e2d\u7684\u8282\u70b9\u6709\u5173\uff0c\u79f0\u4e4b\u4e3a\u505a\u641c\u7d22\u57fa\u7840\u76ee\u5f55\u3002\u641c\u7d22\u57fa\u7840\u76ee\u5f55\u662f\u76ee\u5f55\u5e93\u4e2d\u7684\u4e00\u7ea7\u7684distinguished "
+#~ "name(DN)\uff0c\u5728\u8fd9\u91cc\u80fd\u627e\u5230\u6240\u6709\u7528\u6237\u3002\u7528\u6237\u53ef\u4ee5\u76f4\u5c5e\u4e8e\u6839\u76ee\u5f55\u6216\u8005\u4e00\u4e9b\u5b50\u76ee\u5f55\u3002\u641c\u7d22\u57fa\u7840\u76ee\u5f55\u53ef\u80fd\u662f\u7ec4\u7ec7\u3001\u7ec4\u6216\u8005\u57df\u7528\u6237\u540d\u3002\u7528\u4e8e\u5199DN\u53d8\u91cf\u7684\u8bed\u6cd5\u53d6\u51b3\u4e8e\u4f60\u6240\u4f7f\u7528\u7684LDAP\u670d\u52a1\u3002\u518d\u6df1\u5165\u5168\u9762\u7684\u8ba8\u8bbadistinguished"
+#~ " names\u8d85\u51fa\u4e86\u6211\u4eec\u6587\u6863\u7684\u8303\u56f4\u3002\u4ee5\u4e0b\u8868\u683c\u4e2d\u5c55\u793a\u4e86\u4e00\u4e9b\u5728\u641c\u7d22\u57fa\u7840\u76ee\u5f55\u4e2d\u67e5\u627e\u6d4b\u8bd5\u90e8\u95e8\u4e2d\u7528\u6237\u7684\u793a\u4f8b\u3002"
# 3649e87915d24059beec30463e0abd10
# eb0f32160dd24b21991c2f454df60742
-#: ../../accounts.rst:270 ../../accounts.rst:328
-msgid "LDAP Server"
-msgstr "LDAP\u670d\u52a1\u5668"
+#~ msgid "LDAP Server"
+#~ msgstr "LDAP\u670d\u52a1\u5668"
# d8fb5f498afb4ee1aa6669b39f1e34be
-#: ../../accounts.rst:270
-msgid "Example Search Base DN"
-msgstr "\u641c\u7d22\u57fa\u672cDN\u793a\u4f8b"
+#~ msgid "Example Search Base DN"
+#~ msgstr "\u641c\u7d22\u57fa\u672cDN\u793a\u4f8b"
# 2e421fc0d49d4a819b31999dc3cae2e0
# a0327a00878d45dab6dc0bc777814674
-#: ../../accounts.rst:272 ../../accounts.rst:330
-msgid "ApacheDS"
-msgstr "ApacheDS"
+#~ msgid "ApacheDS"
+#~ msgstr "ApacheDS"
# 6c854d5e6cdd4e3aadda7dd9be769a53
-#: ../../accounts.rst:272
-msgid "OU=testing, O=project"
-msgstr "OU=testing, O=project"
+#~ msgid "OU=testing, O=project"
+#~ msgstr "OU=testing, O=project"
# a1fbaf989c584a248386911c51fd2fba
# c776e850eb3e4d64b262a32a9d302bfb
-#: ../../accounts.rst:273 ../../accounts.rst:331
-msgid "Active Directory"
-msgstr "Active Directory"
+#~ msgid "Active Directory"
+#~ msgstr "Active Directory"
# 5d0095ff2d7044e7b60bc1754210dd3c
-#: ../../accounts.rst:273
-msgid "OU=testing, DC=company"
-msgstr "OU=testing, DC=company"
+#~ msgid "OU=testing, DC=company"
+#~ msgstr "OU=testing, DC=company"
# 8309dae488944f0aae3e84a8e1a97ac3
-#: ../../accounts.rst:278
-msgid "Query Filter"
-msgstr "\u67e5\u8be2\u8fc7\u6ee4"
+#~ msgid "Query Filter"
+#~ msgstr "\u67e5\u8be2\u8fc7\u6ee4"
# c523dbbf5dd94c62a2e3927a8f3123dc
-#: ../../accounts.rst:280
-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 "\u67e5\u8be2\u8fc7\u6ee4\u5668\u7528\u4e8e\u5728\u5916\u90e8LDAP\u670d\u52a1\u5668\u4e2d\u67e5\u627e\u4e00\u4e2a\u6620\u5c04\u7684\u7528\u6237\u3002\u4e3a\u5b9e\u73b0\u6709\u6548\u8ba4\u8bc1\uff0c\u67e5\u8be2\u8fc7\u6ee4\u5668\u5e94\u8be5\u5c06CloudStack\u7684\u7528\u6237\u552f\u4e00\u6620\u5c04\u5230LDAP\u7528\u6237\u3002\u5173\u4e8e\u67e5\u8be2\u8fc7\u6ee4\u5668\u7684\u8bed\u6cd5\uff0c\u8bf7\u53c2\u8003\u60a8\u4f7f\u7528\u7684LDAP\u670d\u52a1\u5668\u6587\u6863\u3002"
+#~ 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 "\u67e5\u8be2\u8fc7\u6ee4\u5668\u7528\u4e8e\u5728\u5916\u90e8LDAP\u670d\u52a1\u5668\u4e2d\u67e5\u627e\u4e00\u4e2a\u6620\u5c04\u7684\u7528\u6237\u3002\u4e3a\u5b9e\u73b0\u6709\u6548\u8ba4\u8bc1\uff0c\u67e5\u8be2\u8fc7\u6ee4\u5668\u5e94\u8be5\u5c06CloudStack\u7684\u7528\u6237\u552f\u4e00\u6620\u5c04\u5230LDAP\u7528\u6237\u3002\u5173\u4e8e\u67e5\u8be2\u8fc7\u6ee4\u5668\u7684\u8bed\u6cd5\uff0c\u8bf7\u53c2\u8003\u60a8\u4f7f\u7528\u7684LDAP\u670d\u52a1\u5668\u6587\u6863\u3002"
# f4f9c13ceefa4163962bd3cfab257852
-#: ../../accounts.rst:285
-msgid "The CloudStack query filter wildcards are:"
-msgstr "CloudStack\u67e5\u8be2\u8fc7\u6ee4\u7684\u901a\u914d\u7b26\u6709:"
+#~ msgid "The CloudStack query filter wildcards are:"
+#~ msgstr "CloudStack\u67e5\u8be2\u8fc7\u6ee4\u7684\u901a\u914d\u7b26\u6709:"
# bab683973b9045339c8df3488bc5dd1c
-#: ../../accounts.rst:288
-msgid "Query Filter Wildcard"
-msgstr "\u67e5\u8be2\u8fc7\u6ee4\u901a\u914d\u7b26"
+#~ msgid "Query Filter Wildcard"
+#~ msgstr "\u67e5\u8be2\u8fc7\u6ee4\u901a\u914d\u7b26"
# a94af335cc864d9a962f1fb9b7b5f72c
-#: ../../accounts.rst:288
-msgid "Description"
-msgstr "\u63cf\u8ff0"
+#~ msgid "Description"
+#~ msgstr "\u63cf\u8ff0"
# 334393ba6786415e91a2ed1a22d26adb
-#: ../../accounts.rst:290
-msgid "%u"
-msgstr "%u"
+#~ msgid "%u"
+#~ msgstr "%u"
# 151cd28e952d4ff98ff9d1544698ccb8
-#: ../../accounts.rst:290
-msgid "User name"
-msgstr "\u7528\u6237\u540d"
+#~ msgid "User name"
+#~ msgstr "\u7528\u6237\u540d"
# f1f86cbcf39e412fb298da7653a123d3
-#: ../../accounts.rst:291
-msgid "%e"
-msgstr "%e"
+#~ msgid "%e"
+#~ msgstr "%e"
# fdf52531788c41fabb814f45f07b178a
-#: ../../accounts.rst:291
-msgid "Email address"
-msgstr "\u90ae\u4ef6\u5730\u5740"
+#~ msgid "Email address"
+#~ msgstr "\u90ae\u4ef6\u5730\u5740"
# 6e5b529e3da248ee85f1e20f81bd8e1c
-#: ../../accounts.rst:292
-msgid "%n"
-msgstr "%n"
+#~ msgid "%n"
+#~ msgstr "%n"
# 4704eb3b3e494ad3bc2105d98a3c84a9
-#: ../../accounts.rst:292
-msgid "First and last name"
-msgstr "\u59d3\u540d"
+#~ msgid "First and last name"
+#~ msgstr "\u59d3\u540d"
# 51612c6475e246f7b7d8a156605a2323
-#: ../../accounts.rst:295
-msgid ""
-"The following examples assume you are using Active Directory, and refer to "
-"user attributes from the Active Directory schema."
-msgstr "\u4e0b\u9762\u7684\u793a\u4f8b\u5047\u8bbe\u4f60\u4f7f\u7528\u6d3b\u52a8\u76ee\u5f55, \u5e76\u4ece\u6d3b\u52a8\u76ee\u5f55\u67b6\u6784\u4e2d\u83b7\u5f97\u7528\u6237\u5c5e\u6027."
+#~ msgid ""
+#~ "The following examples assume you are"
+#~ " using Active Directory, and refer to"
+#~ " user attributes from the Active "
+#~ "Directory schema."
+#~ msgstr "\u4e0b\u9762\u7684\u793a\u4f8b\u5047\u8bbe\u4f60\u4f7f\u7528\u6d3b\u52a8\u76ee\u5f55, \u5e76\u4ece\u6d3b\u52a8\u76ee\u5f55\u67b6\u6784\u4e2d\u83b7\u5f97\u7528\u6237\u5c5e\u6027."
# d853815e3f894dcdbb92be883305dc5b
-#: ../../accounts.rst:298
-msgid "If the CloudStack user name is the same as the LDAP user ID:"
-msgstr "\u5982\u679c CloudStack \u7684\u7528\u6237\u540d\u4e0eLDAP\u4e2d\u7684\u7528\u6237ID\u4e00\u81f4:"
+#~ msgid "If the CloudStack user name is the same as the LDAP user ID:"
+#~ msgstr "\u5982\u679c CloudStack \u7684\u7528\u6237\u540d\u4e0eLDAP\u4e2d\u7684\u7528\u6237ID\u4e00\u81f4:"
# d0bb623240d0410eb8d70ed22ba5a2f8
-#: ../../accounts.rst:304
-msgid "If the CloudStack user name is the LDAP display name:"
-msgstr "\u5982\u679cCloudStack\u7684\u7528\u6237\u540d\u662fLDAP\u4e2d\u7684\u663e\u793a\u540d\u5b57\uff1a"
+#~ msgid "If the CloudStack user name is the LDAP display name:"
+#~ msgstr "\u5982\u679cCloudStack\u7684\u7528\u6237\u540d\u662fLDAP\u4e2d\u7684\u663e\u793a\u540d\u5b57\uff1a"
# 0a96c3c2516946c1b4260fd4d4d6ffb7
-#: ../../accounts.rst:310
-msgid "To find a user by email address:"
-msgstr "\u4f7f\u7528\u90ae\u4ef6\u5730\u5740\u67e5\u627e\u7528\u6237:"
+#~ msgid "To find a user by email address:"
+#~ msgstr "\u4f7f\u7528\u90ae\u4ef6\u5730\u5740\u67e5\u627e\u7528\u6237:"
# 5b63c901fb5a4d208df8e362234d1cba
-#: ../../accounts.rst:318
-msgid "Search User Bind DN"
-msgstr "\u641c\u7d22\u7528\u6237\u7ed1\u5b9a\u7684DN"
+#~ msgid "Search User Bind DN"
+#~ msgstr "\u641c\u7d22\u7528\u6237\u7ed1\u5b9a\u7684DN"
# 92769f4cb5be444cab0bcb685ebe1cc4
-#: ../../accounts.rst:320
-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 "bind DN\u662f\u4f4d\u4e8e\u5916\u90e8\u88ab\u5141\u8bb8\u5728\u5b9a\u4e49\u7684\u641c\u7d22\u57fa\u7840\u76ee\u5f55\u4e2d\u641c\u7d22LDAP\u76ee\u5f55\u7684LDAP\u670d\u52a1\u5668\u4e0a\u7684\u7528\u6237\u3002\u5f53DN\u8fd4\u56de\u503c\u7684\u65f6\u5019\uff0cDN\u548c\u901a\u8fc7\u7684\u5bc6\u7801\u5c31\u4e0eLDAPbind\u4e00\u8d77\u88ab\u7528\u4e8e\u9a8c\u8bc1CloudStack \u7528\u6237\u3002\u518d\u6df1\u5165\u5b8c\u5168\u7684\u8ba8\u8bbabind DNs\u8d85\u51fa\u4e86\u6587\u6863\u7684\u8303\u56f4\u3002\u4e0b\u9762\u7684\u8868\u683c\u5c55\u793a\u4e86\u4e00\u4e9bbind DNs\u7684\u5b9e\u4f8b\u3002"
+#~ 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 ""
+#~ "bind "
+#~ "DN\u662f\u4f4d\u4e8e\u5916\u90e8\u88ab\u5141\u8bb8\u5728\u5b9a\u4e49\u7684\u641c\u7d22\u57fa\u7840\u76ee\u5f55\u4e2d\u641c\u7d22LDAP\u76ee\u5f55\u7684LDAP\u670d\u52a1\u5668\u4e0a\u7684\u7528\u6237\u3002\u5f53DN\u8fd4\u56de\u503c\u7684\u65f6\u5019\uff0cDN\u548c\u901a\u8fc7\u7684\u5bc6\u7801\u5c31\u4e0eLDAPbind\u4e00\u8d77\u88ab\u7528\u4e8e\u9a8c\u8bc1CloudStack"
+#~ " \u7528\u6237\u3002\u518d\u6df1\u5165\u5b8c\u5168\u7684\u8ba8\u8bbabind DNs\u8d85\u51fa\u4e86\u6587\u6863\u7684\u8303\u56f4\u3002\u4e0b\u9762\u7684\u8868\u683c\u5c55\u793a\u4e86\u4e00\u4e9bbind DNs\u7684\u5b9e\u4f8b\u3002"
# 7fcc45a0be9241b09a01d2287541d652
-#: ../../accounts.rst:328
-msgid "Example Bind DN"
-msgstr "\u7ed1\u5b9aDN\u793a\u4f8b"
+#~ msgid "Example Bind DN"
+#~ msgstr "\u7ed1\u5b9aDN\u793a\u4f8b"
# b4c0b2f84be54e32820cac392b6c9c75
-#: ../../accounts.rst:330
-msgid "CN=Administrator,DC=testing,OU=project,OU=org"
-msgstr "CN=Administrator,DC=testing,OU=project,OU=org"
+#~ msgid "CN=Administrator,DC=testing,OU=project,OU=org"
+#~ msgstr "CN=Administrator,DC=testing,OU=project,OU=org"
# 46e145ddbc9f47e08b21fa2631ed9fa7
-#: ../../accounts.rst:331
-msgid "CN=Administrator, OU=testing, DC=company, DC=com"
-msgstr "CN=Administrator, OU=testing, DC=company, DC=com"
+#~ msgid "CN=Administrator, OU=testing, DC=company, DC=com"
+#~ msgstr "CN=Administrator, OU=testing, DC=company, DC=com"
# cbaaf7054abf480eb88b336ba62a097b
-#: ../../accounts.rst:336
-msgid "SSL Keystore Path and Password"
-msgstr "SSL \u5bc6\u94a5\u5e93\u8def\u5f84\u548c\u5bc6\u7801"
+#~ msgid "SSL Keystore Path and Password"
+#~ msgstr "SSL \u5bc6\u94a5\u5e93\u8def\u5f84\u548c\u5bc6\u7801"
# 8a6a84c57cc144edb9a20e63c71ddedc
-#: ../../accounts.rst:338
-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 "\u5982\u679cLDAP \u670d\u52a1\u5668\u8981\u6c42SSL\uff0c \u4f60\u9700\u8981\u5728ldapConfig\u547d\u4ee4\u4e2d\u901a\u8fc7\u8bbe\u7f6e\u53c2\u6570ssl, truststore\u548ctruststorepass\u4f7f\u5176\u751f\u6548\u3002\u5728\u4f7fSSL \u5bf9ldapConfig \u751f\u6548\u4e4b\u524d\uff0c\u4f60\u9700\u8981\u5f97\u5230LDAP\u670d\u52a1\u5668\u5728\u4f7f\u7528\u7684\u8bc1\u4e66\u5e76\u628a\u5b83\u52a0\u5230\u88ab\u4fe1\u4efb\u7684\u5bc6\u94a5\u5e93\u4e2d\u3002\u4f60\u5c06\u9700\u8981\u77e5\u9053\u5230\u5bc6\u94a5\u5e93\u548c\u5bc6\u7801\u7684\u8def\u5f84\u3002"
+#~ 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 ""
+#~ "\u5982\u679cLDAP \u670d\u52a1\u5668\u8981\u6c42SSL\uff0c \u4f60\u9700\u8981\u5728ldapConfig\u547d\u4ee4\u4e2d\u901a\u8fc7\u8bbe\u7f6e\u53c2\u6570ssl, "
+#~ "truststore\u548ctruststorepass\u4f7f\u5176\u751f\u6548\u3002\u5728\u4f7fSSL \u5bf9ldapConfig "
+#~ "\u751f\u6548\u4e4b\u524d\uff0c\u4f60\u9700\u8981\u5f97\u5230LDAP\u670d\u52a1\u5668\u5728\u4f7f\u7528\u7684\u8bc1\u4e66\u5e76\u628a\u5b83\u52a0\u5230\u88ab\u4fe1\u4efb\u7684\u5bc6\u94a5\u5e93\u4e2d\u3002\u4f60\u5c06\u9700\u8981\u77e5\u9053\u5230\u5bc6\u94a5\u5e93\u548c\u5bc6\u7801\u7684\u8def\u5f84\u3002"
+