Translations by Cristina Xu
Cristina Xu has submitted the following strings to this translation. Contributions are visually coded: currently used translations, unreviewed suggestions, rejected suggestions.
13. |
old style configuration can use only dictionary or memcached backends
|
|
2016-03-25 |
舊樣式配置只能使用字典或 Memcached 後端
|
|
24. |
Connection to glance host %(server)s failed: %(reason)s
|
|
2016-03-25 |
與 Glance 主機 %(server)s 的連線失敗:%(reason)s
|
|
36. |
Block Device Mapping is Invalid: %(auth_method)s is unsupported.
|
|
2016-03-25 |
「區塊裝置對映」無效:%(auth_method)s 不受支援。
|
|
46. |
Volume %(volume_id)s could not be attached. Reason: %(reason)s
|
|
2016-03-25 |
無法連接磁區 %(volume_id)s。原因:%(reason)s
|
|
72. |
An invalid 'name' value was provided. The name must be: %(reason)s
|
|
2016-04-07 |
所提供的「名稱」值無效。名稱必須是:%(reason)s
|
|
93. |
This compute node's hypervisor is older than the minimum supported version: %(version)s.
|
|
2016-03-25 |
這部電腦節點的 Hypervisor 版本低於所支援的版本下限:%(version)s。
|
|
95. |
This service is older (v%(thisver)i) than the minimum (v%(minver)i) version of the rest of the deployment. Unable to continue.
|
|
2016-03-25 |
此服務的版本 (v%(thisver)i) 低於其餘部署的版本下限 (v%(minver)i)。無法繼續。
|
|
108. |
Request of image %(image_id)s got BadRequest response: %(response)s
|
|
2016-03-25 |
映像檔 %(image_id)s 的要求取得 BadRequest 回應:%(response)s
|
|
118. |
Undefined Block Device Mapping root: BlockDeviceMappingList contains Block Device Mappings from multiple instances.
|
|
2016-03-25 |
未定義的「區塊裝置對映」根:BlockDeviceMappingList 包含來自多個實例的「區塊裝置對映」。
|
|
121. |
Block Device Mapping %(volume_id)s is a multi-attach volume and is not valid for this operation.
|
|
2016-03-25 |
「區塊裝置對映」%(volume_id)s 是一個多重連接磁區,且不適用於此作業。
|
|
123. |
Device detach failed for %(device)s: %(reason)s)
|
|
2016-03-25 |
分離裝置 %(device)s 失敗:%(reason)s
|
|
124. |
Device '%(device)s' not found.
|
|
2016-03-25 |
找不到裝置 '%(device)s'。
|
|
143. |
%(cidr)s is not a valid IP network.
|
|
2016-03-25 |
%(cidr)s 不是有效的 IP 網路。
|
|
144. |
%(address)s is not a valid IP address.
|
|
2016-03-25 |
%(address)s 不是有效的 IP 位址。
|
|
164. |
OVS configuration failed with: %(inner_exception)s.
|
|
2016-04-07 |
OVS 配置失敗,發生 %(inner_exception)s。
|
|
169. |
Port %(port_id)s not usable for instance %(instance)s. Value %(value)s assigned to dns_name attribute does not match instance's hostname %(hostname)s
|
|
2016-03-25 |
實例 %(instance)s 無法使用埠 %(port_id)s。指派給 dns_name 屬性的值 %(value)s 與實例的主機名 %(hostname)s 不符
|
|
172. |
Fixed IP %(address)s already exists.
|
|
2016-03-25 |
固定 IP %(address)s 已經存在。
|
|
174. |
Fixed IP not found for address %(address)s.
|
|
2016-03-25 |
找不到位址 %(address)s 的固定 IP。
|
|
175. |
Instance %(instance_uuid)s has zero fixed IPs.
|
|
2016-03-25 |
實例 %(instance_uuid)s 具有 0 個固定 IP。
|
|
176. |
Network host %(host)s has zero fixed IPs in network %(network_id)s.
|
|
2016-03-25 |
網路主機 %(host)s 在網路 %(network_id)s 中具有 0 個固定 IP。
|
|
177. |
Instance %(instance_uuid)s doesn't have fixed IP '%(ip)s'.
|
|
2016-03-25 |
實例 %(instance_uuid)s 沒有固定 IP '%(ip)s'。
|
|
181. |
More than one instance is associated with fixed IP address '%(address)s'.
|
|
2016-03-25 |
有多個實例與固定 IP 位址 '%(address)s' 相關聯。
|
|
184. |
Zero fixed IPs could be found.
|
|
2016-03-25 |
可以找到 0 個固定 IP。
|
|
185. |
Floating IP %(address)s already exists.
|
|
2016-03-25 |
浮動 IP %(address)s 已經存在。
|
|
186. |
Floating IP not found for ID %(id)s.
|
|
2016-03-25 |
找不到 ID %(id)s 的浮動 IP。
|
|
188. |
Floating IP not found for address %(address)s.
|
|
2016-03-25 |
找不到位址 %(address)s 的浮動 IP。
|
|
189. |
Floating IP not found for host %(host)s.
|
|
2016-03-25 |
找不到主機 %(host)s 的浮動 IP。
|
|
190. |
Multiple floating IPs are found for address %(address)s.
|
|
2016-03-25 |
找到位址 %(address)s 的多個浮動 IP。
|
|
191. |
Floating IP pool not found.
|
|
2016-03-25 |
找不到浮動 IP 儲存區。
|
|
192. |
Zero floating IPs available.
|
|
2016-03-25 |
有 0 個浮動 IP 可供使用。
|
|
193. |
Floating IP %(address)s is associated.
|
|
2016-03-25 |
已與浮動 IP %(address)s 產生關聯。
|
|
194. |
Floating IP %(address)s is not associated.
|
|
2016-03-25 |
未與浮動 IP %(address)s 產生關聯。
|
|
195. |
Zero floating IPs exist.
|
|
2016-03-25 |
存在 0 個浮動 IP。
|
|
200. |
Cannot disassociate auto assigned floating IP
|
|
2016-03-25 |
無法斷開與自動指派之浮動 IP 的關聯
|
|
233. |
Migration %(migration_id)s not found for instance %(instance_id)s
|
|
2016-03-25 |
找不到實例 %(instance_id)s 的移轉 %(migration_id)s
|
|
234. |
Migration %(migration_id)s state of instance %(instance_uuid)s is %(state)s. Cannot %(method)s while the migration is in this state.
|
|
2016-03-25 |
實例 %(instance_uuid)s 的移轉 %(migration_id)s 狀態為 %(state)s。當移轉處於這種狀態時,無法執行 %(method)s。
|
|
235. |
Console log output could not be retrieved for instance %(instance_id)s. Reason: %(reason)s
|
|
2016-03-25 |
無法擷取實例 %(instance_id)s 的主控台日誌輸出。原因:%(reason)s
|
|
241. |
Guest does not have a console available.
|
|
2016-04-07 |
訪客沒有主控台可用。
|
|
249. |
Flavor %(id)s extra spec cannot be updated or created after %(retries)d retries.
|
|
2016-03-25 |
在嘗試 %(retries)d 次之後,無法更新或建立特性 %(id)s 額外規格。
|
|
278. |
Migration select destinations error: %(reason)s
|
|
2016-03-25 |
移轉選取目的地錯誤:%(reason)s
|
|
295. |
Maximum number of floating IPs exceeded
|
|
2016-03-25 |
超過了浮動 IP 數目上限
|
|
296. |
Maximum number of fixed IPs exceeded
|
|
2016-03-25 |
超過了固定 IP 數目上限
|
|
324. |
Config drive format '%(format)s' is not supported.
|
|
2016-03-25 |
不支援配置磁碟機格式 '%(format)s'。
|
|
327. |
Instance %(instance_uuid)s requires config drive, but it does not exist.
|
|
2016-03-25 |
實例 %(instance_uuid)s 需要配置磁碟機,但該磁碟機不存在。
|
|
329. |
No specific network was requested and none are available for project '%(project_id)s'.
|
|
2016-03-25 |
未要求任何特定網路,且專案 '%(project_id)s' 無法使用任何網路。
|
|
364. |
Signature verification for the image failed: %(reason)s.
|
|
2016-03-25 |
映像檔的簽章驗證失敗:%(reason)s。
|
|
372. |
Not all Virtual Functions of PF %(compute_node_id)s:%(address)s are free.
|
|
2016-03-25 |
並非 PF %(compute_node_id)s:%(address)s 的所有虛擬函數都可用。
|
|
373. |
Physical Function %(compute_node_id)s:%(address)s, related to VF %(compute_node_id)s:%(vf_address)s is %(status)s instead of %(hopestatus)s
|
|
2016-03-25 |
與 VF %(compute_node_id)s:%(vf_address)s 相關的實體函數 %(compute_node_id)s:%(address)s 處於 %(status)s 狀態,而不是 %(hopestatus)s 狀態
|
|
375. |
PCI device request %(requests)s failed
|
|
2016-03-25 |
PCI 裝置要求 %(requests)s 失敗
|
|
391. |
Live migration with API v2.25 requires all the Mitaka upgrade to be complete before it is available.
|
|
2016-03-25 |
使用 API V2.25 進行的即時移轉需要先完成所有 Mitaka 升級,然後才可供使用。
|