| 1 |
# SOME DESCRIPTIVE TITLE |
| 2 |
# Copyright (C) YEAR Free Software Foundation, Inc. |
| 3 |
# This file is distributed under the same license as the PACKAGE package. |
| 4 |
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR. |
| 5 |
# |
| 6 |
#, fuzzy |
| 7 |
msgid "" |
| 8 |
msgstr "" |
| 9 |
"Project-Id-Version: PACKAGE VERSION\n" |
| 10 |
"POT-Creation-Date: 2020-03-02 15:09+0000\n" |
| 11 |
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" |
| 12 |
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n" |
| 13 |
"Language-Team: LANGUAGE <[email protected]>\n" |
| 14 |
"Language: \n" |
| 15 |
"MIME-Version: 1.0\n" |
| 16 |
"Content-Type: text/plain; charset=CHARSET\n" |
| 17 |
"Content-Transfer-Encoding: 8bit\n" |
| 18 |
|
| 19 |
#. type: Title == |
| 20 |
#: drbdmanage-more.adoc:2 |
| 21 |
#, no-wrap |
| 22 |
msgid "More Information about DRBD Manage" |
| 23 |
msgstr "有关DRBD Manage的更多信息" |
| 24 |
|
| 25 |
#. type: Plain text |
| 26 |
#: drbdmanage-more.adoc:5 |
| 27 |
msgid "" |
| 28 |
"Here you will find some more information about DRBD Manage internals, " |
| 29 |
"techniques, and strategies." |
| 30 |
msgstr "在这里,您将找到有关DRBD管理内幕、技术和策略的更多信息。" |
| 31 |
|
| 32 |
#. type: Title === |
| 33 |
#: drbdmanage-more.adoc:8 |
| 34 |
#, no-wrap |
| 35 |
msgid "Free Space reporting" |
| 36 |
msgstr "可用空间报告" |
| 37 |
|
| 38 |
#. type: Plain text |
| 39 |
#: drbdmanage-more.adoc:11 |
| 40 |
msgid "DRBD Manage can report free space in two ways:" |
| 41 |
msgstr "DRBD Manage可以通过两种方式报告可用空间:" |
| 42 |
|
| 43 |
#. type: Plain text |
| 44 |
#: drbdmanage-more.adoc:15 |
| 45 |
msgid "" |
| 46 |
"indexterm:[free space]Per node, via `drbdmanage nodes`; this will tell the " |
| 47 |
"\"physical\" space available, which might not mean much if using Thin LVs " |
| 48 |
"for storing data." |
| 49 |
msgstr "" |
| 50 |
"indexterm:[free space]在每个节点上,可通过 `drbdmanage " |
| 51 |
"nodes` 查看可用空间;这将列出 `物理` 可用空间,如果使用精简LVs存储数据,这可能没有多大意义。" |
| 52 |
|
| 53 |
#. type: Plain text |
| 54 |
#: drbdmanage-more.adoc:19 |
| 55 |
msgid "" |
| 56 |
"indexterm:[free space]Via `drbdmanage list-free-space`; this will return the" |
| 57 |
" size for the single largest volume that can be created with the defined " |
| 58 |
"replication count." |
| 59 |
msgstr "" |
| 60 |
"indexterm:[free space]通过 `drbdmanage list-free-space`;这将返回可使用定义的复制计数创建的单个最大卷的大小。" |
| 61 |
|
| 62 |
#. type: Plain text |
| 63 |
#: drbdmanage-more.adoc:23 |
| 64 |
msgid "" |
| 65 |
"So, with 10 storage nodes each having 1TiB free space, the value returned " |
| 66 |
"will be 1TiB, and allocating such a volume will not change the free space " |
| 67 |
"value." |
| 68 |
msgstr "因此,如果10个存储节点每个都有1TiB可用空间,则返回的值将为1TiB,并且分配这样的卷不会更改可用空间值。" |
| 69 |
|
| 70 |
#. type: Plain text |
| 71 |
#: drbdmanage-more.adoc:26 |
| 72 |
msgid "" |
| 73 |
"For storage nodes with 20GiB, 15GiB, 10GiB, and 5GiB, the free space for " |
| 74 |
"3-way-redundancy will be 10GiB, and 15GiB for 2-way." |
| 75 |
msgstr "对于具有20GiB、15GiB、10GiB和5GiB的存储节点,3路冗余的可用空间为10GiB,2路冗余的可用空间为15GiB。" |
| 76 |
|
| 77 |
#. type: Plain text |
| 78 |
#: drbdmanage-more.adoc:31 |
| 79 |
msgid "" |
| 80 |
"The free space issue is further muddled quite a bit by thin LVM pools (one " |
| 81 |
"or multiple, depending on storage backend in DRBD Manage - please see " |
| 82 |
"<<s-drbdmanage-storage-plugins>> for more details), and DRBD Manage " |
| 83 |
"snapshots." |
| 84 |
msgstr "" |
| 85 |
"精简LVM池(一个或多个,取决于DRBD Manage中的存储后端-请参见<<s-drbdmanage-storage-" |
| 86 |
"plugins>>了解更多详细信息)和DRBD Manage快照进一步混淆了可用空间问题。" |
| 87 |
|
| 88 |
#. type: Title === |
| 89 |
#: drbdmanage-more.adoc:34 |
| 90 |
#, no-wrap |
| 91 |
msgid "Policy plugin, waiting for deployment" |
| 92 |
msgstr "策略插件,正在等待部署" |
| 93 |
|
| 94 |
#. type: Plain text |
| 95 |
#: drbdmanage-more.adoc:38 |
| 96 |
msgid "" |
| 97 |
"When deploying a resource (resp. volume), a snapshot, or when resizing a " |
| 98 |
"volume, you might need to trade between performance and availability." |
| 99 |
msgstr "当部署资源(resp. 卷)、快照或调整卷大小时,可能需要在性能和可用性之间进行权衡。" |
| 100 |
|
| 101 |
#. type: Plain text |
| 102 |
#: drbdmanage-more.adoc:42 |
| 103 |
msgid "" |
| 104 |
"For a small example, if you have 3 storage servers, but one is down because " |
| 105 |
"of a hardware or software upgrade, and you choose to create a new resource " |
| 106 |
"that should keep three copies - what should happen?" |
| 107 |
msgstr "举个小例子,如果您有3台存储服务器,但其中一台由于硬件或软件升级而停机,并且您选择创建一个新的资源,该资源应保留三个副本—会发生什么情况?" |
| 108 |
|
| 109 |
#. type: Plain text |
| 110 |
#: drbdmanage-more.adoc:44 |
| 111 |
msgid "" |
| 112 |
"Should volume creation block until the third node is available again (hours," |
| 113 |
" days, weeks)?" |
| 114 |
msgstr "在第三个节点再次可用(小时、天、周)之前是否应该阻止卷创建?" |
| 115 |
|
| 116 |
#. type: Plain text |
| 117 |
#: drbdmanage-more.adoc:46 |
| 118 |
msgid "" |
| 119 |
"Should volume creation just continue? Should it continue even if only one " |
| 120 |
"storage server is available, even if 3-way redundancy was requested?" |
| 121 |
msgstr "是否应该继续创建卷?即使只有一个存储服务器可用,即使请求了3路冗余,它是否应该继续?" |
| 122 |
|
| 123 |
#. type: Plain text |
| 124 |
#: drbdmanage-more.adoc:47 |
| 125 |
msgid "" |
| 126 |
"Should snapshot creation wait, or continue if at least one server was able " |
| 127 |
"to create the snapshot?" |
| 128 |
msgstr "快照创建应该等待,还是在至少有一台服务器能够创建快照时继续?" |
| 129 |
|
| 130 |
#. type: Plain text |
| 131 |
#: drbdmanage-more.adoc:51 |
| 132 |
msgid "" |
| 133 |
"The more server you have, the more likely it is that at least one of them is" |
| 134 |
" non-operating at any given time; so you need to decide on your policies, " |
| 135 |
"and configure them." |
| 136 |
msgstr "服务器越多,它们中的至少一个在任何给定时间都不运行的可能性就越大;因此,您需要决定策略并对其进行配置。" |
| 137 |
|
| 138 |
#. type: Plain text |
| 139 |
#: drbdmanage-more.adoc:58 |
| 140 |
msgid "" |
| 141 |
"To avoid having to make such decisions in each driver accessing DRBD " |
| 142 |
"Managefootnote:[Like OpenAttic, OpenNebula, <<ch-openstack,Openstack>>, " |
| 143 |
"ProxMox, etc.] individually (duplicating quite a lot of code), we provide " |
| 144 |
"one DRBD Manage pluginfootnote:[\"Plugin\" might not be the best term here; " |
| 145 |
"the code is in the standard DRBD Manage distribution, but it gets called via" |
| 146 |
" the `run_external_plugin` API.] that aims to provide these functionality." |
| 147 |
msgstr "" |
| 148 |
"为了避免在访问DRBD Manage的每个驱动程序中做出这样的决定 footnote:[Like OpenAttic,OpenNebula,<<ch-" |
| 149 |
"openstack,Openstack>>,ProxMox,etc.]单独地(复制相当多的代码),我们提供了一个DRBD Manage " |
| 150 |
"pluginfootnote:[ \"Plugin\" 可能不是最好的术语;代码在标准的DRBD " |
| 151 |
"Manage发行版中,但是它通过旨在提供这些功能的 `run_external_plugin` API.]用于提供这些功能调用。" |
| 152 |
|
| 153 |
#. type: Plain text |
| 154 |
#: drbdmanage-more.adoc:63 |
| 155 |
msgid "" |
| 156 |
"The exact configuration depends on the specific service using DRBD Manage, " |
| 157 |
"of course; but the basic approach is to allow the admin to specify the " |
| 158 |
"waiting behaviour via a JSON blob, which might be given in the configuration" |
| 159 |
" via simple text string (see e.g. <<s-openstack-addtl-conf,Policy " |
| 160 |
"configuration for OpenStack>>)." |
| 161 |
msgstr "" |
| 162 |
"当然,确切的配置取决于使用DRBD Manage的特定服务;但基本方法是允许管理员通过JSON " |
| 163 |
"blob指定等待行为,该blob可以在配置中通过简单的文本字符串给出(请参见<<s-openstack-addtl-conf,Policy " |
| 164 |
"configuration for OpenStack>>)。" |
| 165 |
|
| 166 |
#. type: Plain text |
| 167 |
#: drbdmanage-more.adoc:66 |
| 168 |
msgid "" |
| 169 |
"The available policies for `WaitForResource` and `WaitForSnapshot` are:" |
| 170 |
msgstr "`WaitForResource` 和 `WaitForSnapshot` 的可用策略是:" |
| 171 |
|
| 172 |
#. type: Plain text |
| 173 |
#: drbdmanage-more.adoc:72 |
| 174 |
msgid "" |
| 175 |
"(((Policy,count)))`count` will wait for an absolute number of deployments; " |
| 176 |
"note that these don't have to be in syncfootnote:[On thick LVM a 1TiB " |
| 177 |
"deployment would take some time for the initial sync, and you most probably " |
| 178 |
"don't plan to wait for that, right?] but just *deployed*." |
| 179 |
msgstr "" |
| 180 |
"(((Policy,count)))`count` 将等待绝对数量的部署;请注意,这些部署不必全部同步footnote:[在厚LVM上,1TiB部署需要一些时间进行初始同步,您很可能不打算等待,对吧?], 但仅仅只是 *部署* 了。" |
| 181 |
|
| 182 |
#. type: Plain text |
| 183 |
#: drbdmanage-more.adoc:76 |
| 184 |
msgid "" |
| 185 |
"(((Policy,ratio)))`ratio` is similar, but uses a value from `0.0` to `1.0`, " |
| 186 |
"which gets multiplied with the number of _planned_ deployments. So, for a " |
| 187 |
"resource that has (diskful) assignments on 5 servers, and 3 of them are " |
| 188 |
"available, a ratio of `0.6` would work." |
| 189 |
msgstr "" |
| 190 |
"(((Policy,ratio)))`ratio` 类似,但使用从 `0.0` 到 `1.0` 的值,该值与计划的部署数相乘。因此,对于一个在5台服务器上有(磁盘)分配,并且其中3台服务器可用的资源,`0.6` 的比率将起作用。" |
| 191 |
|
| 192 |
#. type: Block title |
| 193 |
#: drbdmanage-more.adoc:77 |
| 194 |
#, no-wrap |
| 195 |
msgid "NOTE" |
| 196 |
msgstr "注意" |
| 197 |
|
| 198 |
#. type: Plain text |
| 199 |
#: drbdmanage-more.adoc:81 |
| 200 |
msgid "" |
| 201 |
"The given _``ratio``_ will be compared using \"greater-or-equal\"; so " |
| 202 |
"passing `0.5` in does *not* mean \"wait for majority\", as one-of-two " |
| 203 |
"deployments available would already be sufficient! Use `0.51` to get the " |
| 204 |
"intended meaning." |
| 205 |
msgstr "" |
| 206 |
"给定的 _``ratio``_ 将使用 `大于或等于` 进行比较;因此,传入 `0.5` 并不意味着 \"等待多数\" ,因为两个可用的部署之一已经足够了!使用 `0.51` 获得预期含义。" |
| 207 |
|
| 208 |
#. type: Plain text |
| 209 |
#: drbdmanage-more.adoc:84 |
| 210 |
msgid "" |
| 211 |
"If you pass in more than one policy, _any_ of them is sufficient; so, for " |
| 212 |
"`count=3` and `ratio=0.75`, 3-out-of-5 servers would return `result=true`." |
| 213 |
msgstr "" |
| 214 |
"如果传入多个策略,其中任何一个都足够;因此,对于 `count=3` 和 `ratio=0.75` ,五分之三的服务器将返回 `result=true`。" |
| 215 |
|
| 216 |
#. type: Title ==== |
| 217 |
#: drbdmanage-more.adoc:87 |
| 218 |
#, no-wrap |
| 219 |
msgid "More detailed information for driver-writers" |
| 220 |
msgstr "驱动程序编写器的更详细信息" |
| 221 |
|
| 222 |
#. type: Plain text |
| 223 |
#: drbdmanage-more.adoc:91 |
| 224 |
msgid "" |
| 225 |
"For people implementing software that accesses DRBDmanage via the DBus API, " |
| 226 |
"here's an example usage (in mostly Python syntax):" |
| 227 |
msgstr "对于实现通过DBus API访问DRBDmanage的软件的人,下面是一个使用示例(主要使用Python语法):" |
| 228 |
|
| 229 |
#. type: Plain text |
| 230 |
#: drbdmanage-more.adoc:98 |
| 231 |
#, no-wrap |
| 232 |
msgid "" |
| 233 |
" result, data = run_external_plugin(\n" |
| 234 |
" \"drbdmanage.plugins.plugins.wait_for.WaitForResource\",\n" |
| 235 |
" { \"resource\": \"foo\",\n" |
| 236 |
" \"starttime\": <unix-timestamp, i.e. time(NULL), of first call>\n" |
| 237 |
" \"count\": \"3\",\n" |
| 238 |
" \"timeout\": \"15\"})\n" |
| 239 |
msgstr "" |
| 240 |
" result, data = run_external_plugin(\n" |
| 241 |
" \"drbdmanage.plugins.plugins.wait_for.WaitForResource\",\n" |
| 242 |
" { \"resource\": \"foo\",\n" |
| 243 |
" \"starttime\": <unix-timestamp, i.e. time(NULL), of first call>\n" |
| 244 |
" \"count\": \"3\",\n" |
| 245 |
" \"timeout\": \"15\"})\n" |
| 246 |
|
| 247 |
#. type: Plain text |
| 248 |
#: drbdmanage-more.adoc:103 |
| 249 |
msgid "" |
| 250 |
"would return the normal array of success/error datafootnote:[Which will " |
| 251 |
"always mean some calling/internal error; \"Policy not satisfied\" or " |
| 252 |
"\"timeout\" will be reported _on this level_ as \"completed succesfully\"!]," |
| 253 |
" and an additional dict with detailed status data:" |
| 254 |
msgstr "" |
| 255 |
"将返回正常的成功/错误数据数组footnote:[这始终意味着某些调用/内部错误; \"策略未满足\" 或 \"超时\" 将被报告为 \"已成功完成\"!],以及带有详细状态数据的附加dict:" |
| 256 |
|
| 257 |
#. type: Plain text |
| 258 |
#: drbdmanage-more.adoc:109 |
| 259 |
#, no-wrap |
| 260 |
msgid "" |
| 261 |
" {\n" |
| 262 |
" \"policy\": \"count\",\n" |
| 263 |
" \"result\": \"true\",\n" |
| 264 |
" \"timeout\": \"false\"\n" |
| 265 |
" }\n" |
| 266 |
msgstr "" |
| 267 |
" {\n" |
| 268 |
" \"policy\": \"count\",\n" |
| 269 |
" \"result\": \"true\",\n" |
| 270 |
" \"timeout\": \"false\"\n" |
| 271 |
" }\n" |
| 272 |
|
| 273 |
#. type: Plain text |
| 274 |
#: drbdmanage-more.adoc:112 |
| 275 |
msgid "" |
| 276 |
"If at least 3 servers had the given resource deployed (at the time of the " |
| 277 |
"call), `result` got `\"true\"` because the `count` policy was satisfied." |
| 278 |
msgstr "如果至少有3个服务器部署了给定的资源(在调用时),`result` 会为 `true` ,因为满足 `count` 策略。" |
| 279 |
|
| 280 |
#. type: Plain text |
| 281 |
#: drbdmanage-more.adoc:115 |
| 282 |
msgid "You can wait with/for these plugins/events:" |
| 283 |
msgstr "您可以使用/等待这些插件/事件:" |
| 284 |
|
| 285 |
#. type: Plain text |
| 286 |
#: drbdmanage-more.adoc:118 |
| 287 |
msgid "" |
| 288 |
"(((Policy,resource " |
| 289 |
"creation)))`drbdmanage.plugins.plugins.wait_for.WaitForResource` needs a " |
| 290 |
"`resource` key as input data;" |
| 291 |
msgstr "" |
| 292 |
"(((Policy,resource creation)))`drbdmanage.plugins.plugins.wait_for.WaitForResource` " |
| 293 |
"需要一个 `resource` 键作为输入数据;" |
| 294 |
|
| 295 |
#. type: Plain text |
| 296 |
#: drbdmanage-more.adoc:120 |
| 297 |
msgid "" |
| 298 |
"(((Policy,snapshot " |
| 299 |
"creation)))`drbdmanage.plugins.plugins.wait_for.WaitForSnapshot` needs a " |
| 300 |
"`resource` and a `snapshot` key as input data;" |
| 301 |
msgstr "" |
| 302 |
"(((Policy,snapshot creation)))`drbdmanage.plugins.plugins.wait_for.WaitForSnapshot` " |
| 303 |
"需要一个 `resource` 和一个 `snapshot` 键作为输入数据;" |
| 304 |
|
| 305 |
#. type: Plain text |
| 306 |
#: drbdmanage-more.adoc:122 |
| 307 |
msgid "" |
| 308 |
"(((Policy,resizing " |
| 309 |
"volumes)))`drbdmanage.plugins.plugins.wait_for.WaitForVolumeSize` requires " |
| 310 |
"`resource`, `volnr`, and `req_size` (net size, in KiB) input arguments." |
| 311 |
msgstr "" |
| 312 |
"(((Policy.resizing volumes)))`drbdmanage.plugins.plugins.wait_for.WaitForVolumeSize` " |
| 313 |
"需要 `resource`、`volnr` 和 `req-size` (网络大小,以KiB为单位)输入参数。" |
| 314 |
|
| 315 |
#. type: Plain text |
| 316 |
#: drbdmanage-more.adoc:129 |
| 317 |
msgid "" |
| 318 |
"Please note that because of DBus timeouts this API function does *not* " |
| 319 |
"block; it will return immediately. That's the reason for the `starttime` and" |
| 320 |
" `timeout` values in the input dictionary; if the plugin sees that the " |
| 321 |
"current time is after `starttime` plus `timeout`, it will set the `timeout` " |
| 322 |
"result to `\"true\"`, so that the driver knows to abort and return an error." |
| 323 |
msgstr "" |
| 324 |
"请注意,由于DBus超时,此API函数 *不会* 阻塞;它将立即返回。这就是输入字典中 `starttime` 和 `timeout` 值的原因;如果插件看到当前时间在 `starttime` 加上 `timeout` 之后,它会将 `timeout` 结果设置为 `true` ,以便驱动程序知道中止并返回错误。" |