Imported Translations from Transifex
For more information about this automatic import see: https://wiki.openstack.org/wiki/Translations/Infrastructure Change-Id: If6c6645e0d82e40c7cd8ea5dd9660a951c139dcd
This commit is contained in:
OpenStack Proposal Bot
parent
1bb8c6347b
commit
ba21a38927
@ -8,7 +8,7 @@ msgid ""
|
||||
msgstr ""
|
||||
"Project-Id-Version: Cloud Administrator Guide 0.9\n"
|
||||
"Report-Msgid-Bugs-To: \n"
|
||||
"POT-Creation-Date: 2015-08-28 06:16+0000\n"
|
||||
"POT-Creation-Date: 2015-08-29 06:14+0000\n"
|
||||
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
|
||||
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
|
||||
"Language-Team: LANGUAGE <LL@li.org>\n"
|
||||
@ -362,7 +362,7 @@ msgstr ""
|
||||
msgid "**Basic security group operations**"
|
||||
msgstr ""
|
||||
|
||||
#: ../compute-node-down.rst:202
|
||||
#: ../compute-node-down.rst:203
|
||||
msgid "**Begin recovery**"
|
||||
msgstr ""
|
||||
|
||||
@ -881,10 +881,6 @@ msgstr ""
|
||||
msgid "**Recommended values for max_lp_per_bridged_ls**"
|
||||
msgstr ""
|
||||
|
||||
#: ../compute-node-down.rst:22
|
||||
msgid "**Recovering from a failed compute node manually**"
|
||||
msgstr ""
|
||||
|
||||
#: ../database.rst:65
|
||||
msgid "**Register image with Image service**"
|
||||
msgstr ""
|
||||
@ -1476,7 +1472,7 @@ msgid ""
|
||||
"where this object should live."
|
||||
msgstr ""
|
||||
|
||||
#: ../compute-node-down.rst:156
|
||||
#: ../compute-node-down.rst:157
|
||||
msgid "A cloud controller (nova-api, nova-objectstore, nova-network)"
|
||||
msgstr ""
|
||||
|
||||
@ -1497,7 +1493,7 @@ msgid ""
|
||||
"Installation Guide."
|
||||
msgstr ""
|
||||
|
||||
#: ../compute-node-down.rst:158
|
||||
#: ../compute-node-down.rst:159
|
||||
msgid "A compute node (nova-compute)"
|
||||
msgstr ""
|
||||
|
||||
@ -1589,7 +1585,7 @@ msgid ""
|
||||
"third party tools may rely on it."
|
||||
msgstr ""
|
||||
|
||||
#: ../compute-node-down.rst:152
|
||||
#: ../compute-node-down.rst:153
|
||||
msgid ""
|
||||
"A disaster could happen to several components of your architecture (for "
|
||||
"example, a disk crash, network loss, or a power failure). In this example, "
|
||||
@ -1915,7 +1911,7 @@ msgstr ""
|
||||
msgid "A statistic selection to aggregate the data."
|
||||
msgstr ""
|
||||
|
||||
#: ../compute-node-down.rst:160
|
||||
#: ../compute-node-down.rst:161
|
||||
msgid ""
|
||||
"A storage area network (SAN) used by OpenStack Block Storage (cinder-volumes)"
|
||||
msgstr ""
|
||||
@ -2340,7 +2336,7 @@ msgid ""
|
||||
"After it validates, save the builder and create a new ``account.builder``:"
|
||||
msgstr ""
|
||||
|
||||
#: ../compute-node-down.rst:183
|
||||
#: ../compute-node-down.rst:184
|
||||
msgid "After power is recovered and all hardware components have restarted:"
|
||||
msgstr ""
|
||||
|
||||
@ -2463,7 +2459,7 @@ msgid ""
|
||||
"All certificate and key files must be in Privacy Enhanced Mail (PEM) format"
|
||||
msgstr ""
|
||||
|
||||
#: ../compute-node-down.rst:316
|
||||
#: ../compute-node-down.rst:317
|
||||
msgid "All instances are restarted with euca2ools."
|
||||
msgstr ""
|
||||
|
||||
@ -2650,7 +2646,7 @@ msgid ""
|
||||
"access resources and perform operations."
|
||||
msgstr ""
|
||||
|
||||
#: ../compute-node-down.rst:320
|
||||
#: ../compute-node-down.rst:321
|
||||
msgid ""
|
||||
"An SSH connection is performed into every instance using Compute credentials."
|
||||
msgstr ""
|
||||
@ -2721,7 +2717,7 @@ msgid ""
|
||||
"checking if that user is a member of the emulation group."
|
||||
msgstr ""
|
||||
|
||||
#: ../compute-node-down.rst:312
|
||||
#: ../compute-node-down.rst:313
|
||||
msgid "An array is created for instances and their attached volumes."
|
||||
msgstr ""
|
||||
|
||||
@ -3856,7 +3852,7 @@ msgstr ""
|
||||
msgid "Certificates for PKI"
|
||||
msgstr ""
|
||||
|
||||
#: ../compute-node-down.rst:125
|
||||
#: ../compute-node-down.rst:126
|
||||
msgid "Change all the files owned by user or group nova. For example:"
|
||||
msgstr ""
|
||||
|
||||
@ -3875,7 +3871,7 @@ msgid ""
|
||||
"IP addresses are not allowed as host names on the 3PAR storage server."
|
||||
msgstr ""
|
||||
|
||||
#: ../compute-node-down.rst:76
|
||||
#: ../compute-node-down.rst:77
|
||||
msgid ""
|
||||
"Change the ``DHCPSERVER`` value to the host IP address of the new compute "
|
||||
"host."
|
||||
@ -3946,7 +3942,7 @@ msgid ""
|
||||
"``nova-network``:"
|
||||
msgstr ""
|
||||
|
||||
#: ../compute-node-down.rst:209
|
||||
#: ../compute-node-down.rst:210
|
||||
msgid ""
|
||||
"Check the current relationship between the volume and its instance, so that "
|
||||
"you can recreate the attachment."
|
||||
@ -4717,13 +4713,13 @@ msgid ""
|
||||
"consistency group id."
|
||||
msgstr ""
|
||||
|
||||
#: ../compute-node-down.rst:166
|
||||
#: ../compute-node-down.rst:167
|
||||
msgid ""
|
||||
"Create an active iSCSI session from the SAN to the cloud controller (used "
|
||||
"for the ``cinder-volumes`` LVM's VG)."
|
||||
msgstr ""
|
||||
|
||||
#: ../compute-node-down.rst:169
|
||||
#: ../compute-node-down.rst:170
|
||||
msgid ""
|
||||
"Create an active iSCSI session from the cloud controller to the compute node "
|
||||
"(managed by cinder-volume)."
|
||||
@ -4734,7 +4730,7 @@ msgid ""
|
||||
"Create an extra specification that links the volume type to a back-end name::"
|
||||
msgstr ""
|
||||
|
||||
#: ../compute-node-down.rst:172
|
||||
#: ../compute-node-down.rst:173
|
||||
msgid ""
|
||||
"Create an iSCSI session for every volume (so 14 EBS volumes requires 14 "
|
||||
"iSCSI sessions)."
|
||||
@ -4762,7 +4758,7 @@ msgstr ""
|
||||
msgid "Create external network and map it to a specific NSX gateway service:"
|
||||
msgstr ""
|
||||
|
||||
#: ../compute-node-down.rst:175
|
||||
#: ../compute-node-down.rst:176
|
||||
msgid ""
|
||||
"Create iptables or ebtables rules from the cloud controller to the compute "
|
||||
"node. This allows access from the cloud controller to the running instance."
|
||||
@ -5238,7 +5234,7 @@ msgstr ""
|
||||
msgid "Debug signing key file errors"
|
||||
msgstr ""
|
||||
|
||||
#: ../compute-node-down.rst:65
|
||||
#: ../compute-node-down.rst:66
|
||||
msgid ""
|
||||
"Decide which compute host the affected VM should be moved to, and run this "
|
||||
"database command to move the VM to the new host:"
|
||||
@ -5595,13 +5591,13 @@ msgstr ""
|
||||
msgid "Displays all ports and IPs allocated on a network."
|
||||
msgstr ""
|
||||
|
||||
#: ../compute-node-down.rst:206
|
||||
#: ../compute-node-down.rst:207
|
||||
msgid ""
|
||||
"Do not add any extra steps to this procedure, or perform the steps out of "
|
||||
"order."
|
||||
msgstr ""
|
||||
|
||||
#: ../compute-node-down.rst:289
|
||||
#: ../compute-node-down.rst:290
|
||||
msgid ""
|
||||
"Do not add the entry for the SAN's disks to the cinder-volume's :file:"
|
||||
"`fstab` file."
|
||||
@ -5626,7 +5622,7 @@ msgid ""
|
||||
"duplicated IPMI sensor samples."
|
||||
msgstr ""
|
||||
|
||||
#: ../compute-node-down.rst:335
|
||||
#: ../compute-node-down.rst:336
|
||||
msgid "Do not forget the ``-r`` flag. Otherwise, you will close all sessions."
|
||||
msgstr ""
|
||||
|
||||
@ -6146,6 +6142,10 @@ msgstr ""
|
||||
msgid "Euca2ools"
|
||||
msgstr ""
|
||||
|
||||
#: ../compute-node-down.rst:12
|
||||
msgid "Evacuate instances"
|
||||
msgstr ""
|
||||
|
||||
#: ../telemetry.rst:7
|
||||
msgid ""
|
||||
"Even in the cloud industry, providers must use a multi-step process for "
|
||||
@ -6783,7 +6783,7 @@ msgid ""
|
||||
"Command-Line Reference <http://docs.openstack.org/cli-reference/content/>`__."
|
||||
msgstr ""
|
||||
|
||||
#: ../compute-node-down.rst:149
|
||||
#: ../compute-node-down.rst:150
|
||||
msgid ""
|
||||
"For a definition of a disaster recovery plan (DRP), see `http://en.wikipedia."
|
||||
"org/wiki/Disaster\\_Recovery\\_Plan <http://en.wikipedia.org/wiki/"
|
||||
@ -7764,7 +7764,7 @@ msgid ""
|
||||
"should map."
|
||||
msgstr ""
|
||||
|
||||
#: ../compute-node-down.rst:24
|
||||
#: ../compute-node-down.rst:25
|
||||
msgid ""
|
||||
"Identify the VMs on the affected hosts. To do this, you can use a "
|
||||
"combination of :command:`nova list` and :command:`nova show` or :command:"
|
||||
@ -7852,6 +7852,14 @@ msgid ""
|
||||
"To enable this boolean, run the following command as the ``root`` user::"
|
||||
msgstr ""
|
||||
|
||||
#: ../compute-node-down.rst:13
|
||||
msgid ""
|
||||
"If a cloud compute node fails due to a hardware malfunction or another "
|
||||
"reason, you can evacuate instances using the :command:`nova evacuate` "
|
||||
"command. See the `Admin User Guide <http://docs.openstack.org/user-guide-"
|
||||
"admin/cli_nova_evacuate.html>`__."
|
||||
msgstr ""
|
||||
|
||||
#: ../telemetry-data-retrieval.rst:432
|
||||
msgid ""
|
||||
"If a file name and location is not specified, this publisher does not log "
|
||||
@ -7953,7 +7961,7 @@ msgid ""
|
||||
"configuration."
|
||||
msgstr ""
|
||||
|
||||
#: ../compute-node-down.rst:269
|
||||
#: ../compute-node-down.rst:270
|
||||
msgid ""
|
||||
"If some services depend on the volume, or if a volume has an entry in fstab, "
|
||||
"you should now be able to restart the instance. Restart directly from the "
|
||||
@ -8189,7 +8197,7 @@ msgid ""
|
||||
"``VlanManager`` and ``FlatDHCPManager`` networking modes."
|
||||
msgstr ""
|
||||
|
||||
#: ../compute-node-down.rst:72
|
||||
#: ../compute-node-down.rst:73
|
||||
msgid ""
|
||||
"If you are using a hypervisor that relies on libvirt (such as KVM), update "
|
||||
"the :file:`libvirt.xml` file (found in :file:`/var/lib/nova/instances/"
|
||||
@ -8382,7 +8390,7 @@ msgid ""
|
||||
"this datastore version, you can list the package names here."
|
||||
msgstr ""
|
||||
|
||||
#: ../compute-node-down.rst:308
|
||||
#: ../compute-node-down.rst:309
|
||||
msgid ""
|
||||
"If you want to script the disaster recovery plan (DRP), a bash script is "
|
||||
"available from `https://github.com/Razique <https://github.com/Razique/"
|
||||
@ -8754,7 +8762,7 @@ msgid ""
|
||||
"compute nodes. This is expected behavior."
|
||||
msgstr ""
|
||||
|
||||
#: ../compute-node-down.rst:98
|
||||
#: ../compute-node-down.rst:99
|
||||
msgid ""
|
||||
"In some cases, files on your compute node can end up using the wrong UID or "
|
||||
"GID. This can happen when running OpenStack Compute, using a shared file "
|
||||
@ -9115,7 +9123,7 @@ msgstr ""
|
||||
msgid "Instance management tools"
|
||||
msgstr ""
|
||||
|
||||
#: ../compute-node-down.rst:237
|
||||
#: ../compute-node-down.rst:238
|
||||
msgid ""
|
||||
"Instance state at this stage depends on whether you added an `/etc/fstab` "
|
||||
"entry for that volume. Images built with the cloud-init package remain in a "
|
||||
@ -9134,7 +9142,7 @@ msgid ""
|
||||
"``http://169.254.169.254/openstack/2012-08-10/user_data``:"
|
||||
msgstr ""
|
||||
|
||||
#: ../compute-node-down.rst:194
|
||||
#: ../compute-node-down.rst:195
|
||||
msgid "Instances are no longer running."
|
||||
msgstr ""
|
||||
|
||||
@ -9161,7 +9169,7 @@ msgid ""
|
||||
"``http://169.254.169.254/2009-04-04/user-data``:"
|
||||
msgstr ""
|
||||
|
||||
#: ../compute-node-down.rst:263
|
||||
#: ../compute-node-down.rst:264
|
||||
msgid ""
|
||||
"Instances that were stopped at the plymouth stage will now automatically "
|
||||
"continue booting and start normally. Instances that previously started "
|
||||
@ -9805,7 +9813,7 @@ msgid ""
|
||||
"DHCP client."
|
||||
msgstr ""
|
||||
|
||||
#: ../compute-node-down.rst:267
|
||||
#: ../compute-node-down.rst:268
|
||||
msgid "Log in to the instances with SSH and reboot them."
|
||||
msgstr ""
|
||||
|
||||
@ -9874,7 +9882,7 @@ msgstr ""
|
||||
msgid "Make sure the certificate directory is only accessible by root."
|
||||
msgstr ""
|
||||
|
||||
#: ../compute-node-down.rst:111
|
||||
#: ../compute-node-down.rst:112
|
||||
msgid ""
|
||||
"Make sure you choose UIDs or GIDs that are not in use for other users or "
|
||||
"groups."
|
||||
@ -9912,7 +9920,7 @@ msgstr ""
|
||||
msgid "Managing the cloud with euca2ools"
|
||||
msgstr ""
|
||||
|
||||
#: ../compute-node-down.rst:16
|
||||
#: ../compute-node-down.rst:22
|
||||
msgid "Manual recovery"
|
||||
msgstr ""
|
||||
|
||||
@ -10434,7 +10442,7 @@ msgid ""
|
||||
"d5217d851862``."
|
||||
msgstr ""
|
||||
|
||||
#: ../compute-node-down.rst:196
|
||||
#: ../compute-node-down.rst:197
|
||||
msgid ""
|
||||
"Note that instances will not be lost, because neither ``destroy`` nor "
|
||||
"``terminate`` was invoked. The files for the instances will remain on the "
|
||||
@ -10897,7 +10905,7 @@ msgid ""
|
||||
"disk faster than they can be migrated."
|
||||
msgstr ""
|
||||
|
||||
#: ../compute-node-down.rst:300
|
||||
#: ../compute-node-down.rst:301
|
||||
msgid ""
|
||||
"On your instances, if you have the whole ``/home/`` directory on the disk, "
|
||||
"leave a user's directory with the user's bash files and the :file:"
|
||||
@ -12057,7 +12065,7 @@ msgstr ""
|
||||
msgid "Query role assignments to groups"
|
||||
msgstr ""
|
||||
|
||||
#: ../compute-node-down.rst:34
|
||||
#: ../compute-node-down.rst:35
|
||||
msgid ""
|
||||
"Query the Compute database to check the status of the host. This example "
|
||||
"converts an EC2 API instance ID into an OpenStack ID. If you use the :"
|
||||
@ -12123,7 +12131,7 @@ msgstr ""
|
||||
msgid "Realtime visibility into client requests"
|
||||
msgstr ""
|
||||
|
||||
#: ../compute-node-down.rst:246
|
||||
#: ../compute-node-down.rst:247
|
||||
msgid ""
|
||||
"Reattach the volumes to their respective instances, if required, using the :"
|
||||
"command:`nova volume-attach` command. This example uses a file of listed "
|
||||
@ -12134,7 +12142,7 @@ msgstr ""
|
||||
msgid "Reboot instances"
|
||||
msgstr ""
|
||||
|
||||
#: ../compute-node-down.rst:81
|
||||
#: ../compute-node-down.rst:82
|
||||
msgid "Reboot the VM:"
|
||||
msgstr ""
|
||||
|
||||
@ -12150,11 +12158,11 @@ msgstr ""
|
||||
msgid "Recommended order of starting services"
|
||||
msgstr ""
|
||||
|
||||
#: ../compute-node-down.rst:143
|
||||
#: ../compute-node-down.rst:144
|
||||
msgid "Recover cloud after disaster"
|
||||
msgstr ""
|
||||
|
||||
#: ../compute-node-down.rst:96
|
||||
#: ../compute-node-down.rst:97
|
||||
msgid "Recover from a UID/GID mismatch"
|
||||
msgstr ""
|
||||
|
||||
@ -12242,7 +12250,7 @@ msgstr ""
|
||||
msgid "Removes the interfaces from the router."
|
||||
msgstr ""
|
||||
|
||||
#: ../compute-node-down.rst:133
|
||||
#: ../compute-node-down.rst:134
|
||||
msgid "Repeat all steps for the :file:`libvirt-qemu` files, if required."
|
||||
msgstr ""
|
||||
|
||||
@ -12410,7 +12418,7 @@ msgstr ""
|
||||
msgid "Restart the ``glusterd`` service::"
|
||||
msgstr ""
|
||||
|
||||
#: ../compute-node-down.rst:229
|
||||
#: ../compute-node-down.rst:230
|
||||
msgid ""
|
||||
"Restart the instances using the :command:`nova reboot INSTANCE` command."
|
||||
msgstr ""
|
||||
@ -12429,7 +12437,7 @@ msgstr ""
|
||||
msgid "Restart the service::"
|
||||
msgstr ""
|
||||
|
||||
#: ../compute-node-down.rst:135
|
||||
#: ../compute-node-down.rst:136
|
||||
msgid "Restart the services."
|
||||
msgstr ""
|
||||
|
||||
@ -12560,7 +12568,7 @@ msgstr ""
|
||||
msgid "Run instances"
|
||||
msgstr ""
|
||||
|
||||
#: ../compute-node-down.rst:137
|
||||
#: ../compute-node-down.rst:138
|
||||
msgid ""
|
||||
"Run the :command:`find` command to verify that all files use the correct "
|
||||
"identifiers."
|
||||
@ -12736,7 +12744,7 @@ msgid ""
|
||||
"iptables service to pick up the changes:"
|
||||
msgstr ""
|
||||
|
||||
#: ../compute-node-down.rst:179
|
||||
#: ../compute-node-down.rst:180
|
||||
msgid ""
|
||||
"Save the current state of the database, the current state of the running "
|
||||
"instances, and the attached volumes (mount point, volume ID, volume status, "
|
||||
@ -12930,19 +12938,19 @@ msgid ""
|
||||
"parameter. The default value for the parameter is ``fd00::/48``."
|
||||
msgstr ""
|
||||
|
||||
#: ../compute-node-down.rst:114
|
||||
#: ../compute-node-down.rst:115
|
||||
msgid ""
|
||||
"Set the ``libvirt-qemu`` UID in :file:`/etc/passwd` to the same number on "
|
||||
"all hosts (for example, 119)."
|
||||
msgstr ""
|
||||
|
||||
#: ../compute-node-down.rst:120
|
||||
#: ../compute-node-down.rst:121
|
||||
msgid ""
|
||||
"Set the ``libvirtd`` group in :file:`/etc/group` file to the same number on "
|
||||
"all hosts (for example, 119)."
|
||||
msgstr ""
|
||||
|
||||
#: ../compute-node-down.rst:117
|
||||
#: ../compute-node-down.rst:118
|
||||
msgid ""
|
||||
"Set the ``nova`` group in :file:`/etc/group` file to the same number on all "
|
||||
"hosts (for example, 120)."
|
||||
@ -12959,7 +12967,7 @@ msgid ""
|
||||
"Set the following options in the :file:`/etc/keystone/keystone.conf` file:"
|
||||
msgstr ""
|
||||
|
||||
#: ../compute-node-down.rst:106
|
||||
#: ../compute-node-down.rst:107
|
||||
msgid ""
|
||||
"Set the nova UID in :file:`/etc/passwd` to the same number on all hosts (for "
|
||||
"example, 112)."
|
||||
@ -13223,7 +13231,7 @@ msgid ""
|
||||
"network storage rather than a local disk."
|
||||
msgstr ""
|
||||
|
||||
#: ../compute-node-down.rst:233
|
||||
#: ../compute-node-down.rst:234
|
||||
msgid ""
|
||||
"Some instances will completely reboot and become reachable, while some might "
|
||||
"stop at the plymouth stage. This is expected behavior, DO NOT reboot a "
|
||||
@ -13246,7 +13254,7 @@ msgid ""
|
||||
"service that needs it."
|
||||
msgstr ""
|
||||
|
||||
#: ../compute-node-down.rst:292
|
||||
#: ../compute-node-down.rst:293
|
||||
msgid ""
|
||||
"Some systems hang on that step, which means you could lose access to your "
|
||||
"cloud-controller. To re-run the session manually, run this command before "
|
||||
@ -13441,7 +13449,7 @@ msgstr ""
|
||||
msgid "Stop the DHCP agent on HostB too."
|
||||
msgstr ""
|
||||
|
||||
#: ../compute-node-down.rst:123
|
||||
#: ../compute-node-down.rst:124
|
||||
msgid "Stop the services on the compute node."
|
||||
msgstr ""
|
||||
|
||||
@ -14090,7 +14098,7 @@ msgid ""
|
||||
"packages."
|
||||
msgstr ""
|
||||
|
||||
#: ../compute-node-down.rst:314
|
||||
#: ../compute-node-down.rst:315
|
||||
msgid "The MySQL database is updated."
|
||||
msgstr ""
|
||||
|
||||
@ -15154,7 +15162,7 @@ msgid ""
|
||||
"alarms` handling can be found in this guide."
|
||||
msgstr ""
|
||||
|
||||
#: ../compute-node-down.rst:62
|
||||
#: ../compute-node-down.rst:63
|
||||
msgid ""
|
||||
"The credentials for your database can be found in :file:`/etc/nova.conf`."
|
||||
msgstr ""
|
||||
@ -15198,11 +15206,11 @@ msgid ""
|
||||
"ServiceGroup abstraction, Compute can treat each type separately."
|
||||
msgstr ""
|
||||
|
||||
#: ../compute-node-down.rst:200
|
||||
#: ../compute-node-down.rst:201
|
||||
msgid "The database has not been updated."
|
||||
msgstr ""
|
||||
|
||||
#: ../compute-node-down.rst:87
|
||||
#: ../compute-node-down.rst:88
|
||||
msgid ""
|
||||
"The database update and :command:`nova reboot` command should be all that is "
|
||||
"required to recover a VM from a failed host. However, if you continue to "
|
||||
@ -15733,11 +15741,11 @@ msgstr ""
|
||||
msgid "The host's name"
|
||||
msgstr ""
|
||||
|
||||
#: ../compute-node-down.rst:185
|
||||
#: ../compute-node-down.rst:186
|
||||
msgid "The iSCSI session from the SAN to the cloud no longer exists."
|
||||
msgstr ""
|
||||
|
||||
#: ../compute-node-down.rst:187
|
||||
#: ../compute-node-down.rst:188
|
||||
msgid ""
|
||||
"The iSCSI session from the cloud controller to the compute node no longer "
|
||||
"exists."
|
||||
@ -15796,7 +15804,7 @@ msgid ""
|
||||
"where samples are produced under the direct control of an agent."
|
||||
msgstr ""
|
||||
|
||||
#: ../compute-node-down.rst:190
|
||||
#: ../compute-node-down.rst:191
|
||||
msgid ""
|
||||
"The iptables and ebtables from the cloud controller to the compute node are "
|
||||
"recreated. This is because nova-network reapplies configurations on boot."
|
||||
@ -16619,7 +16627,7 @@ msgid ""
|
||||
"functionality."
|
||||
msgstr ""
|
||||
|
||||
#: ../compute-node-down.rst:323
|
||||
#: ../compute-node-down.rst:324
|
||||
msgid ""
|
||||
"The script includes a ``test mode``, which allows you to perform that whole "
|
||||
"sequence for only one instance."
|
||||
@ -16965,7 +16973,7 @@ msgstr ""
|
||||
msgid "The volume's user ID"
|
||||
msgstr ""
|
||||
|
||||
#: ../compute-node-down.rst:318
|
||||
#: ../compute-node-down.rst:319
|
||||
msgid "The volumes are reattached."
|
||||
msgstr ""
|
||||
|
||||
@ -16981,7 +16989,7 @@ msgid ""
|
||||
"(ws://) on python versions less than 2.7.4."
|
||||
msgstr ""
|
||||
|
||||
#: ../compute-node-down.rst:163
|
||||
#: ../compute-node-down.rst:164
|
||||
msgid ""
|
||||
"The worst disaster for a cloud is power loss, which applies to all three "
|
||||
"components. Before a power loss:"
|
||||
@ -17300,7 +17308,7 @@ msgid ""
|
||||
"the host machines to locally retrieve this information."
|
||||
msgstr ""
|
||||
|
||||
#: ../compute-node-down.rst:305
|
||||
#: ../compute-node-down.rst:306
|
||||
msgid ""
|
||||
"This allows you to connect to the instance even without the volume attached, "
|
||||
"if you allow only connections through public keys."
|
||||
@ -17581,7 +17589,7 @@ msgid ""
|
||||
"(splitting a string, forcing case)."
|
||||
msgstr ""
|
||||
|
||||
#: ../compute-node-down.rst:212
|
||||
#: ../compute-node-down.rst:213
|
||||
msgid ""
|
||||
"This information can be found using the :command:`nova volume-list` command. "
|
||||
"Note that the ``nova`` client also includes the ability to get volume "
|
||||
@ -17703,7 +17711,7 @@ msgid ""
|
||||
"with the delegated tenant."
|
||||
msgstr ""
|
||||
|
||||
#: ../compute-node-down.rst:283
|
||||
#: ../compute-node-down.rst:284
|
||||
msgid ""
|
||||
"This parameter will cause the system to disable the ability to write to the "
|
||||
"disk if it detects an I/O error. This configuration option should be added "
|
||||
@ -17759,7 +17767,7 @@ msgid ""
|
||||
"to the Compute services."
|
||||
msgstr ""
|
||||
|
||||
#: ../compute-node-down.rst:104
|
||||
#: ../compute-node-down.rst:105
|
||||
msgid "This procedure runs on nova-compute hosts, based on the KVM hypervisor:"
|
||||
msgstr ""
|
||||
|
||||
@ -17811,7 +17819,7 @@ msgid ""
|
||||
"version."
|
||||
msgstr ""
|
||||
|
||||
#: ../compute-node-down.rst:145
|
||||
#: ../compute-node-down.rst:146
|
||||
msgid ""
|
||||
"This section covers procedures for managing your cloud after a disaster, and "
|
||||
"backing up persistent storage volumes. Backups are mandatory, even outside "
|
||||
@ -18484,13 +18492,6 @@ msgid ""
|
||||
"values in :file:`nova.conf`:"
|
||||
msgstr ""
|
||||
|
||||
#: ../compute-node-down.rst:18
|
||||
msgid ""
|
||||
"To recover a KVM or libvirt compute node, see the section called :ref:`nova-"
|
||||
"compute-node-down-manual-recovery`. For all other hypervisors, use this "
|
||||
"procedure:"
|
||||
msgstr ""
|
||||
|
||||
#: ../blockstorage_glusterfs_removal.rst:15
|
||||
msgid ""
|
||||
"To remove a GlusterFS volume from usage as a back end, delete the volume's "
|
||||
@ -18512,7 +18513,7 @@ msgstr ""
|
||||
msgid "To reproduce the issue follow the steps in the following procedure."
|
||||
msgstr ""
|
||||
|
||||
#: ../compute-node-down.rst:326
|
||||
#: ../compute-node-down.rst:327
|
||||
msgid ""
|
||||
"To reproduce the power loss, connect to the compute node which runs that "
|
||||
"instance and close the iSCSI session. Do not detach the volume using the :"
|
||||
@ -19088,7 +19089,7 @@ msgstr ""
|
||||
msgid "Update the DHCP configuration file :file:`/etc/neutron/dhcp_agent.ini`:"
|
||||
msgstr ""
|
||||
|
||||
#: ../compute-node-down.rst:79
|
||||
#: ../compute-node-down.rst:80
|
||||
msgid "Update the VNC IP to `0.0.0.0`"
|
||||
msgstr ""
|
||||
|
||||
@ -19099,7 +19100,7 @@ msgid ""
|
||||
"parameter set to ``False`` or ``True``."
|
||||
msgstr ""
|
||||
|
||||
#: ../compute-node-down.rst:216
|
||||
#: ../compute-node-down.rst:217
|
||||
msgid ""
|
||||
"Update the database to clean the stalled state. Do this for every volume, "
|
||||
"using these queries:"
|
||||
@ -19209,7 +19210,7 @@ msgstr ""
|
||||
msgid "Usage workflow"
|
||||
msgstr ""
|
||||
|
||||
#: ../compute-node-down.rst:227
|
||||
#: ../compute-node-down.rst:228
|
||||
msgid "Use :command:`nova volume-list` commands to list all volumes."
|
||||
msgstr ""
|
||||
|
||||
@ -19384,7 +19385,7 @@ msgid ""
|
||||
"agent``, it should still be added to NSX as a Hypervisor."
|
||||
msgstr ""
|
||||
|
||||
#: ../compute-node-down.rst:280
|
||||
#: ../compute-node-down.rst:281
|
||||
msgid ""
|
||||
"Use the ``errors=remount`` parameter in the :file:`fstab` file to prevent "
|
||||
"data corruption."
|
||||
@ -19437,6 +19438,10 @@ msgstr ""
|
||||
msgid "Use this command to list all volumes"
|
||||
msgstr ""
|
||||
|
||||
#: ../compute-node-down.rst:23
|
||||
msgid "Use this procedure to recover a failed compute node manually:"
|
||||
msgstr ""
|
||||
|
||||
#: ../keystone_use_trusts.rst:3
|
||||
msgid "Use trusts"
|
||||
msgstr ""
|
||||
@ -20105,7 +20110,7 @@ msgid ""
|
||||
"security group APIs are instances based and not port based as Networking."
|
||||
msgstr ""
|
||||
|
||||
#: ../compute-node-down.rst:277
|
||||
#: ../compute-node-down.rst:278
|
||||
msgid ""
|
||||
"When you are planning for and performing a disaster recovery, follow these "
|
||||
"tips:"
|
||||
|
||||
@ -1,7 +1,7 @@
|
||||
msgid ""
|
||||
msgstr ""
|
||||
"Project-Id-Version: PACKAGE VERSION\n"
|
||||
"POT-Creation-Date: 2015-08-28 06:16+0000\n"
|
||||
"POT-Creation-Date: 2015-08-29 06:14+0000\n"
|
||||
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
|
||||
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
|
||||
"Language-Team: LANGUAGE <LL@li.org>\n"
|
||||
@ -134,7 +134,7 @@ msgid "Attack vectors increase further in a public facing OpenStack deployment.
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/ch_legal-security-requirements.xml:64(para)
|
||||
msgid "It's important to understand that user authentication requests encase sensitive information such as user names, passwords, and authentication tokens. For this reason, place the API services behind hardware that performs SSL termination."
|
||||
msgid "It is important to understand that user authentication requests encase sensitive information such as user names, passwords, and authentication tokens. For this reason, place the API services behind hardware that performs SSL termination."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/ch_legal-security-requirements.xml:69(para)
|
||||
@ -158,15 +158,15 @@ msgid "Public security domains"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/ch_legal-security-requirements.xml:89(para)
|
||||
msgid "The public security domain is an untrusted area of the cloud infrastructure. It can refer to the Internet as a whole or simply to networks over which the user has no authority. Always consider this domain untrusted. For example, in a hybrid cloud deployment, any information traversing between and beyond the clouds is in the public domain and untrustworthy."
|
||||
msgid "The public security domain is an untrusted area of the cloud infrastructure. It can refer to the internet as a whole or simply to networks over which the user has no authority. Always consider this domain untrusted. For example, in a hybrid cloud deployment, any information traversing between and beyond the clouds is in the public domain and untrustworthy."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/ch_legal-security-requirements.xml:98(title)
|
||||
msgid "Guest security domains"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/ch_legal-security-requirements.xml:99(para) ./doc/arch-design/generalpurpose/section_tech_considerations_general_purpose.xml:747(para)
|
||||
msgid "Typically used for compute instance-to-instance traffic, the guest security domain handles compute data generated by instances on the cloud but not services that support the operation of the cloud, such as API calls. Public cloud providers and private cloud providers who do not have stringent controls on instance use or who allow unrestricted Internet access to instances should consider this domain to be untrusted. Private cloud providers may want to consider this network as internal and therefore trusted only if they have controls in place to assert that they trust instances and all their tenants."
|
||||
#: ./doc/arch-design/ch_legal-security-requirements.xml:99(para)
|
||||
msgid "Typically used for compute instance-to-instance traffic, the guest security domain handles compute data generated by instances on the cloud but not services that support the operation of the cloud, such as API calls. Public cloud providers and private cloud providers who do not have stringent controls on instance use or who allow unrestricted internet access to instances should consider this domain to be untrusted. Private cloud providers may want to consider this network as internal and therefore trusted only if they have controls in place to assert that they trust instances and all their tenants."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/ch_legal-security-requirements.xml:112(title)
|
||||
@ -190,82 +190,82 @@ msgid "Hypervisor-security"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/ch_legal-security-requirements.xml:131(para)
|
||||
msgid "The hypervisor also requires a security assessment. In a public cloud, organizations typically do not have control over the choice of hypervisor. For example, Amazon uses its own particular version of Xen. Properly securing your hypervisor is important. Attacks made upon the unsecured hypervisor are called a <firstterm>hypervisor breakout</firstterm>. Hypervisor breakout describes the event of a compromised or malicious instance breaking out of the resource controls of the hypervisor and gaining access to the bare metal operating system and hardware resources."
|
||||
msgid "The hypervisor also requires a security assessment. In a public cloud, organizations typically do not have control over the choice of hypervisor. Properly securing your hypervisor is important. Attacks made upon the unsecured hypervisor are called a <firstterm>hypervisor breakout</firstterm>. Hypervisor breakout describes the event of a compromised or malicious instance breaking out of the resource controls of the hypervisor and gaining access to the bare metal operating system and hardware resources."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/ch_legal-security-requirements.xml:142(para)
|
||||
#: ./doc/arch-design/ch_legal-security-requirements.xml:141(para)
|
||||
msgid "There is not an issue if the security of instances is not important. However, enterprises need to avoid vulnerability. The only way to do this is to avoid the situation where the instances are running on a public cloud. That does not mean that there is a need to own all of the infrastructure on which an OpenStack installation operates; it suggests avoiding situations in which sharing hardware with others occurs."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/ch_legal-security-requirements.xml:151(title)
|
||||
#: ./doc/arch-design/ch_legal-security-requirements.xml:150(title)
|
||||
msgid "Baremetal security"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/ch_legal-security-requirements.xml:152(para)
|
||||
msgid "There are other services worth considering that provide a bare metal instance instead of a cloud. In other cases, it is possible to replicate a second private cloud by integrating with a private Cloud-as-a-Service deployment. The organization does not buy the hardware, but also does not share with other tenants. It is also possible to use a provider that hosts a bare-metal \"public\" cloud instance for which the hardware is dedicated only to one customer, or a provider that offers private Cloud-as-a-Service."
|
||||
#: ./doc/arch-design/ch_legal-security-requirements.xml:151(para)
|
||||
msgid "There are other services worth considering that provide a bare metal instance instead of a cloud. In other cases, it is possible to replicate a second private cloud by integrating with a private Cloud-as-a-Service deployment. The organization does not buy the hardware, but also does not share with other tenants. It is also possible to use a provider that hosts a bare-metal public cloud instance for which the hardware is dedicated only to one customer, or a provider that offers private Cloud-as-a-Service."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/ch_legal-security-requirements.xml:161(para)
|
||||
msgid "It is important to realize that each cloud implements services differently. What keeps data secure in one cloud may not do the same in another. Be sure to know the security requirements of every cloud that handles the organization's data or workloads."
|
||||
msgid "Each cloud implements services differently. What keeps data secure in one cloud may not do the same in another. Be sure to know the security requirements of every cloud that handles the organization's data or workloads."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/ch_legal-security-requirements.xml:166(para)
|
||||
#: ./doc/arch-design/ch_legal-security-requirements.xml:167(para)
|
||||
msgid "More information on OpenStack Security can be found in the <link xlink:href=\"http://docs.openstack.org/security-guide\"><citetitle>OpenStack Security Guide</citetitle></link>."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/ch_legal-security-requirements.xml:171(title)
|
||||
#: ./doc/arch-design/ch_legal-security-requirements.xml:172(title)
|
||||
msgid "Networking Security"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/ch_legal-security-requirements.xml:172(para)
|
||||
#: ./doc/arch-design/ch_legal-security-requirements.xml:173(para)
|
||||
msgid "Consider security implications and requirements before designing the physical and logical network topologies. Make sure that the networks are properly segregated and traffic flows are going to the correct destinations without crossing through locations that are undesirable. Consider the following example factors:"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/ch_legal-security-requirements.xml:179(para) ./doc/arch-design/ch_generalpurpose.xml:72(para)
|
||||
#: ./doc/arch-design/ch_legal-security-requirements.xml:180(para) ./doc/arch-design/ch_generalpurpose.xml:72(para)
|
||||
msgid "Firewalls"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/ch_legal-security-requirements.xml:182(para)
|
||||
#: ./doc/arch-design/ch_legal-security-requirements.xml:183(para)
|
||||
msgid "Overlay interconnects for joining separated tenant networks"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/ch_legal-security-requirements.xml:185(para)
|
||||
#: ./doc/arch-design/ch_legal-security-requirements.xml:186(para)
|
||||
msgid "Routing through or avoiding specific networks"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/ch_legal-security-requirements.xml:188(para)
|
||||
#: ./doc/arch-design/ch_legal-security-requirements.xml:189(para)
|
||||
msgid "How networks attach to hypervisors can expose security vulnerabilities. To mitigate against exploiting hypervisor breakouts, separate networks from other systems and schedule instances for the network onto dedicated compute nodes. This prevents attackers from having access to the networks from a compromised instance."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/ch_legal-security-requirements.xml:195(title)
|
||||
#: ./doc/arch-design/ch_legal-security-requirements.xml:196(title)
|
||||
msgid "Multi-site security"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/ch_legal-security-requirements.xml:196(para)
|
||||
#: ./doc/arch-design/ch_legal-security-requirements.xml:197(para)
|
||||
msgid "Securing a multi-site OpenStack installation brings extra challenges. Tenants may expect a tenant-created network to be secure. In a multi-site installation the use of a non-private connection between sites may be required. This may mean that traffic would be visible to third parties and, in cases where an application requires security, this issue requires mitigation. In these instances, install a VPN or encrypted connection between sites to conceal sensitive traffic."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/ch_legal-security-requirements.xml:204(para)
|
||||
#: ./doc/arch-design/ch_legal-security-requirements.xml:205(para)
|
||||
msgid "Another security consideration with regard to multi-site deployments is Identity. Centralize authentication within a multi-site deployment. Centralization provides a single authentication point for users across the deployment, as well as a single point of administration for traditional create, read, update, and delete operations. Centralized authentication is also useful for auditing purposes because all authentication tokens originate from the same source."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/ch_legal-security-requirements.xml:213(para)
|
||||
msgid "Just as tenants in a single-site deployment need isolation from each other, so do tenants in multi-site installations. The extra challenges in multi-site designs revolve around ensuring that tenant networks function across regions. Unfortunately, OpenStack Networking does not presently support a mechanism to provide this functionality, therefore an external system may be necessary to manage these mappings. Tenant networks may contain sensitive information requiring that this mapping be accurate and consistent to ensure that a tenant in one site does not connect to a different tenant in another site."
|
||||
#: ./doc/arch-design/ch_legal-security-requirements.xml:214(para)
|
||||
msgid "Just as tenants in a single-site deployment need isolation from each other, so do tenants in multi-site installations. The extra challenges in multi-site designs revolve around ensuring that tenant networks function across regions. OpenStack Networking (neutron) does not presently support a mechanism to provide this functionality, therefore an external system may be necessary to manage these mappings. Tenant networks may contain sensitive information requiring that this mapping be accurate and consistent to ensure that a tenant in one site does not connect to a different tenant in another site."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/ch_legal-security-requirements.xml:226(title) ./doc/arch-design/storage_focus/section_architecture_storage_focus.xml:361(para) ./doc/arch-design/storage_focus/section_architecture_storage_focus.xml:470(title) ./doc/arch-design/compute_focus/section_tech_considerations_compute_focus.xml:219(title) ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:166(title) ./doc/arch-design/multi_site/section_tech_considerations_multi_site.xml:144(title) ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:560(para) ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:667(title) ./doc/arch-design/generalpurpose/section_tech_considerations_general_purpose.xml:440(title)
|
||||
#: ./doc/arch-design/ch_legal-security-requirements.xml:227(title) ./doc/arch-design/storage_focus/section_architecture_storage_focus.xml:361(para) ./doc/arch-design/storage_focus/section_architecture_storage_focus.xml:470(title) ./doc/arch-design/compute_focus/section_tech_considerations_compute_focus.xml:219(title) ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:166(title) ./doc/arch-design/multi_site/section_tech_considerations_multi_site.xml:144(title) ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:560(para) ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:667(title) ./doc/arch-design/generalpurpose/section_tech_considerations_general_purpose.xml:440(title)
|
||||
msgid "OpenStack components"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/ch_legal-security-requirements.xml:227(para)
|
||||
#: ./doc/arch-design/ch_legal-security-requirements.xml:228(para)
|
||||
msgid "Most OpenStack installations require a bare minimum set of pieces to function. These include OpenStack Identity (keystone) for authentication, OpenStack Compute (nova) for compute, OpenStack Image service (glance) for image storage, OpenStack Networking (neutron) for networking, and potentially an object store in the form of OpenStack Object Storage (swift). Bringing multi-site into play also demands extra components in order to coordinate between regions. Centralized Identity service is necessary to provide the single authentication point. Centralized dashboard is also recommended to provide a single login point and a mapped experience to the API and CLI options available. If needed, use a centralized Object Storage service, installing the required swift proxy service alongside the Object Storage service."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/ch_legal-security-requirements.xml:241(para)
|
||||
#: ./doc/arch-design/ch_legal-security-requirements.xml:242(para)
|
||||
msgid "It may also be helpful to install a few extra options in order to facilitate certain use cases. For instance, installing DNS service may assist in automatically generating DNS domains for each region with an automatically-populated zone full of resource records for each instance. This facilitates using DNS as a mechanism for determining which region would be selected for certain applications."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/ch_legal-security-requirements.xml:248(para)
|
||||
#: ./doc/arch-design/ch_legal-security-requirements.xml:249(para)
|
||||
msgid "Another useful tool for managing a multi-site installation is OpenStack Orchestration (heat). The Orchestration module allows the use of templates to define a set of instances to be launched together or for scaling existing sets. It can set up matching or differentiated groupings based on regions. For instance, if an application requires an equally balanced number of nodes across sites, the same heat template can be used to cover each site with small alterations to only the region name."
|
||||
msgstr ""
|
||||
|
||||
@ -5807,6 +5807,10 @@ msgstr ""
|
||||
msgid "The public security domain is an entirely untrusted area of the cloud infrastructure. It can refer to the Internet as a whole or simply to networks over which you have no authority. This domain should always be considered untrusted."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/generalpurpose/section_tech_considerations_general_purpose.xml:747(para)
|
||||
msgid "Typically used for compute instance-to-instance traffic, the guest security domain handles compute data generated by instances on the cloud but not services that support the operation of the cloud, such as API calls. Public cloud providers and private cloud providers who do not have stringent controls on instance use or who allow unrestricted Internet access to instances should consider this domain to be untrusted. Private cloud providers may want to consider this network as internal and therefore trusted only if they have controls in place to assert that they trust instances and all their tenants."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/generalpurpose/section_tech_considerations_general_purpose.xml:758(para)
|
||||
msgid "The management security domain is where services interact. Sometimes referred to as the \"control plane\", the networks in this domain transport confidential data such as configuration parameters, user names, and passwords. In most deployments this domain is considered trusted."
|
||||
msgstr ""
|
||||
|
||||
@ -9,8 +9,8 @@
|
||||
msgid ""
|
||||
msgstr ""
|
||||
"Project-Id-Version: OpenStack Manuals\n"
|
||||
"POT-Creation-Date: 2015-08-27 05:23+0000\n"
|
||||
"PO-Revision-Date: 2015-08-27 04:55+0000\n"
|
||||
"POT-Creation-Date: 2015-08-28 10:14+0000\n"
|
||||
"PO-Revision-Date: 2015-08-28 07:15+0000\n"
|
||||
"Last-Translator: openstackjenkins <jenkins@openstack.org>\n"
|
||||
"Language-Team: Chinese (China) (http://www.transifex.com/openstack/openstack-"
|
||||
"manuals-i18n/language/zh_CN/)\n"
|
||||
@ -523,17 +523,6 @@ msgstr ""
|
||||
"用。运维花费更高的原因在于相比与其它架构需要更多复杂的编排以及额外的工具。相"
|
||||
"比之下，整体运营成本可能在最具成本效益的平台中使用云运营工具部署负载会降低。"
|
||||
|
||||
msgid ""
|
||||
"A large, monolithic, single-tiered legacy application typically isn't a good "
|
||||
"fit for the cloud. Efficiencies are gained when load can be spread over "
|
||||
"several instances, so that a failure in one part of the system can be "
|
||||
"mitigated without affecting other parts of the system, or so that scaling "
|
||||
"can take place where the app needs it."
|
||||
msgstr ""
|
||||
"那些大型的、单层次的、铁板一块的旧的应用是非常典型的不适合云环境的。将负载分"
|
||||
"割为多个实例会获得高效，所以部分系统失效不会特别影响其他部分的系统，或者说随"
|
||||
"应用的需要而横向扩展。"
|
||||
|
||||
msgid ""
|
||||
"A measure of how many servers can fit into a given measure of physical "
|
||||
"space, such as a rack unit [U]."
|
||||
@ -885,18 +874,6 @@ msgstr "应用增长"
|
||||
msgid "Application readiness"
|
||||
msgstr "应用准备"
|
||||
|
||||
msgid ""
|
||||
"Applications that depend on specific hardwaresuch as a particular chip set "
|
||||
"or an external device such as a fingerprint readermight not be a good fit "
|
||||
"for the cloud, unless those dependencies are specifically addressed. "
|
||||
"Similarly, if an application depends on an operating system or set of "
|
||||
"libraries that cannot be used in the cloud, or cannot be virtualized, that "
|
||||
"is a problem."
|
||||
msgstr ""
|
||||
"如果应用程序依赖特别的硬件，比如特别的芯片或者是类似指纹识别等外设，是不适合"
|
||||
"于云计算的。除非使用特别的方式来实现。同样的，如果应用依赖于操作系统或一组程"
|
||||
"序库不能用于云环境，或者无法在虚拟化环境中运行，这就真的成了问题了。"
|
||||
|
||||
msgid ""
|
||||
"Appropriate <literal>user_data</literal> to populate the central DNS servers "
|
||||
"upon instance launch."
|
||||
@ -996,28 +973,6 @@ msgstr ""
|
||||
msgid "Bare-metal"
|
||||
msgstr "裸金属"
|
||||
|
||||
msgid ""
|
||||
"Be a pessimist: Assume everything fails and design backwards. Love your "
|
||||
"chaos monkey."
|
||||
msgstr ""
|
||||
"做一个悲观主义者：承担一切失败，基于目标选择手段。善待那些将系统搞坏的程序。"
|
||||
|
||||
msgid ""
|
||||
"Be cost aware: Autoscaling, data transmission, virtual software licenses, "
|
||||
"reserved instances, and so on can rapidly increase monthly usage charges. "
|
||||
"Monitor usage closely."
|
||||
msgstr ""
|
||||
"注意开销：自动扩展，数据传输，虚拟软件许可证，保留的实例等等均会快速增加每月"
|
||||
"的使用支出。密切监测使用情况。"
|
||||
|
||||
msgid ""
|
||||
"Be dynamic: Enable dynamic configuration changes such as auto scaling, "
|
||||
"failure recovery and resource discovery to adapt to changing environments, "
|
||||
"faults and workload volumes."
|
||||
msgstr ""
|
||||
"保持动态：激活动态配置变化诸如自动扩展，失效恢复，资源发现等，以适应变化的环"
|
||||
"境，错误的发生以及负载的变化。"
|
||||
|
||||
msgid ""
|
||||
"Be paranoid: Design for defense in depth and zero tolerance by building in "
|
||||
"security at every level and between every component. Trust no one."
|
||||
@ -1109,13 +1064,6 @@ msgstr "从私有云突破负载到公有的非OpenStack云"
|
||||
msgid "Business or technical diversity"
|
||||
msgstr "业务或技术的多样性"
|
||||
|
||||
msgid ""
|
||||
"But not too paranoid: Not every application needs the platinum solution. "
|
||||
"Architect for different SLA's, service tiers and security levels."
|
||||
msgstr ""
|
||||
"但是也不要太偏执：不是所有的应用都需要钻石级的解决方案。为不同的服务水平协"
|
||||
"议、不同的服务层和安全级别等分别设计不同的架构。"
|
||||
|
||||
msgid ""
|
||||
"By definition, a cloud provides end users with the ability to self-provision "
|
||||
"computing power, storage, networks, and software in a simple and flexible "
|
||||
@ -2373,18 +2321,6 @@ msgstr ""
|
||||
"要求有更多的CPU和内存资源，相对存储和网络的性能优先级要低的多。关于设计此类型"
|
||||
"云的指南，请参考 <xref linkend=\"compute_focus\"/>。"
|
||||
|
||||
msgid ""
|
||||
"In cloud environments, on the other hand, servers are more like cattle. "
|
||||
"There are thousands of them, they get names like NY-1138-Q, and if they get "
|
||||
"sick, they get put down and a sysadmin installs another one. Traditional "
|
||||
"applications that are unprepared for this kind of environment, naturally "
|
||||
"will suffer outages, lost data, or worse."
|
||||
msgstr ""
|
||||
"在云的环境中，打个比方，服务器更像是牛群中的某一头牛。它们太多了，成千上万，"
|
||||
"命名的方式可能是类似的编号 NY-1138-Q，如果它们中的一个出问题了，管理员会直接"
|
||||
"抛弃它，再重新安装和启动一个即可。遗留的应用还没有准备好运行在此云环境中，所"
|
||||
"以很自然的会遭遇停运，丢失数据，甚至更加糟糕的。"
|
||||
|
||||
msgid ""
|
||||
"In environments that place extreme demands on Block Storage, we recommend "
|
||||
"using multiple storage pools. In this case, each pool of devices should have "
|
||||
@ -2527,18 +2463,6 @@ msgstr ""
|
||||
"了块级别的存储。Ceph 非常的灵活，并且具有能够降低运营成本的许多特性，比如说自"
|
||||
"动修复以及自动平衡。Ceph 中的 erasure coded 池被用以最大化可用空间的量。"
|
||||
|
||||
msgid ""
|
||||
"In traditional environments, with traditional enterprise applications, the "
|
||||
"applications and the servers that run on them are \"pets\". They're lovingly "
|
||||
"crafted and cared for, the servers have names like Gandalf or Tardis, and if "
|
||||
"they get sick, someone nurses them back to health. All of this is designed "
|
||||
"so that the application does not experience an outage."
|
||||
msgstr ""
|
||||
"在过去的环境中，还有那些过去的企业级应用，服务器和应用的运行都是被当作“宠"
|
||||
"物”看待的，他们被精心的照看和爱护，甚至每台服务器都有自己的名字如“甘道"
|
||||
"夫“或”哆啦唉梦“,一旦他们生病了，则需要人去护理直到恢复健康。所有的这些设计表"
|
||||
"明应用是不可以停止。"
|
||||
|
||||
msgid ""
|
||||
"Inclusion of clustering software, such as Corosync or Pacemaker, is "
|
||||
"determined primarily by the availability requirements. The impact of "
|
||||
@ -2709,33 +2633,9 @@ msgstr ""
|
||||
"理解用户的认证需要一些敏感信息如用户名、密码和认证令牌是非常重要的。基于这个"
|
||||
"原因，强烈建议将认证的API服务隐藏在基于硬件的SSL终端之后。"
|
||||
|
||||
msgid ""
|
||||
"Just as tenants in a single-site deployment need isolation from each other, "
|
||||
"so do tenants in multi-site installations. The extra challenges in multi-"
|
||||
"site designs revolve around ensuring that tenant networks function across "
|
||||
"regions. Unfortunately, OpenStack Networking does not presently support a "
|
||||
"mechanism to provide this functionality, therefore an external system may be "
|
||||
"necessary to manage these mappings. Tenant networks may contain sensitive "
|
||||
"information requiring that this mapping be accurate and consistent to ensure "
|
||||
"that a tenant in one site does not connect to a different tenant in another "
|
||||
"site."
|
||||
msgstr ""
|
||||
"就像在单站点部署的租户需要彼此隔离，在多区域安装中的租户也一样，在多区域设计"
|
||||
"的额外挑战是围绕着如何确保跨region的租户网络功能，不幸的是，OpenStack网络所提"
|
||||
"供的功能还不支持此种机制，因为需要外部的系统来管理这些映射，租户网络包含的敏"
|
||||
"感信息需要这种映射的精准和一致，以确保在一个站点的租户不会联系到另外一个站点"
|
||||
"的不同租户。"
|
||||
|
||||
msgid "KVM (and QEMU)"
|
||||
msgstr "KVM (and QEMU)"
|
||||
|
||||
msgid ""
|
||||
"Keep it loose: Loose coupling, service interfaces, separation of concerns, "
|
||||
"abstraction and well defined API's deliver flexibility."
|
||||
msgstr ""
|
||||
"保持松散：松耦合，服务接口，分离关注度高的点，抽象并定义好的应用程序接口，交"
|
||||
"付灵活。"
|
||||
|
||||
msgid ""
|
||||
"Kenneth Hui (EMC) <link xlink:href=\"http://twitter.com/hui_kenneth"
|
||||
"\">@hui_kenneth</link>"
|
||||
@ -2923,14 +2823,6 @@ msgstr ""
|
||||
"Maish Saidel-Keesing (Cisco) <link xlink:href=\"http://twitter.com/maishsk"
|
||||
"\">@maishsk</link>"
|
||||
|
||||
msgid ""
|
||||
"Manage the data: Data is usually the most inflexible and complex area of a "
|
||||
"cloud and cloud integration architecture. Don't short change the effort in "
|
||||
"analyzing and addressing data needs."
|
||||
msgstr ""
|
||||
"管理数据：数据通常是最为灵活的也最复杂的一块，尤其是在云中或云集成的架构中。"
|
||||
"要在分析和传送数据付出更多的努力。"
|
||||
|
||||
msgid "Management"
|
||||
msgstr "管理"
|
||||
|
||||
@ -4274,15 +4166,6 @@ msgstr "选择OpenStack软件组件"
|
||||
msgid "Selection of supplemental software"
|
||||
msgstr "选择支撑软件"
|
||||
|
||||
msgid ""
|
||||
"Self-contained applications or those that depend on resources that are not "
|
||||
"reachable by the cloud in question, will not run. In some situations, work "
|
||||
"around these issues with custom network setup, but how well this works "
|
||||
"depends on the chosen cloud environment."
|
||||
msgstr ""
|
||||
"自包含的应用或它们所依赖的资源在云的环境无法实现，将无法运行。也许在一些情况"
|
||||
"下，通过自定义网络解决了这些问题，但是运行是否良好还得看选择云的环境。"
|
||||
|
||||
msgid "Separation of duties"
|
||||
msgstr "职责分工"
|
||||
|
||||
@ -5141,21 +5024,6 @@ msgstr ""
|
||||
"型的软件Cumulus Linux即是个例子，Cumulus Linux具有运行多数交换机供应商的硬件"
|
||||
"的能力。"
|
||||
|
||||
msgid ""
|
||||
"There are other reasons to design applications with cloud in mind. Some are "
|
||||
"defensive, such as the fact that applications cannot be certain of exactly "
|
||||
"where or on what hardware they will be launched, they need to be flexible, "
|
||||
"or at least adaptable. Others are proactive. For example, one of the "
|
||||
"advantages of using the cloud is scalability, so applications need to be "
|
||||
"designed in such a way that they can take advantage of those and other "
|
||||
"opportunities."
|
||||
msgstr ""
|
||||
"在为云设计应用还有另外一些原因需要注意。一些是防御性的，例如一些应用并不能准"
|
||||
"确的确定在什么地方或什么样的硬件去启动，所以他们需要灵活性，即使做不到至少应"
|
||||
"该保持适应性更强。另外一些则是主动性的，例如，使用云的一个优点是其有高扩展"
|
||||
"性，所以应用需要被设计的能够使用这些优点，当然云还有更多的优点，也得一并考"
|
||||
"虑。"
|
||||
|
||||
msgid ""
|
||||
"There are several factors to take into consideration when looking at whether "
|
||||
"an application is a good fit for the cloud."
|
||||
|
||||
@ -12,7 +12,7 @@ msgstr ""
|
||||
"Project-Id-Version: OpenStack Manuals\n"
|
||||
"Report-Msgid-Bugs-To: \n"
|
||||
"POT-Creation-Date: 2015-06-19 06:17+0000\n"
|
||||
"PO-Revision-Date: 2015-08-28 05:51+0000\n"
|
||||
"PO-Revision-Date: 2015-08-28 11:26+0000\n"
|
||||
"Last-Translator: Tomoyuki KATO <tomo@dream.daynight.jp>\n"
|
||||
"Language-Team: Japanese (http://www.transifex.com/openstack/openstack-"
|
||||
"manuals-i18n/language/ja/)\n"
|
||||
@ -6101,6 +6101,16 @@ msgid "Runs automated tests against the core OpenStack API; written in Rails."
|
||||
msgstr ""
|
||||
"コア OpenStack API に対して自動テストを実行する。Rails で書かれている。"
|
||||
|
||||
msgid "Runs operating systems and provides scratch space"
|
||||
msgstr "オペレーティングシステムを実行し、新規領域を提供します"
|
||||
|
||||
msgid ""
|
||||
"Runs within the guest instance. Manages and performs operations on the "
|
||||
"database itself."
|
||||
msgstr ""
|
||||
"ゲストインスタンスの中で実行します。データベース自身の処理を管理、実行しま"
|
||||
"す。"
|
||||
|
||||
msgid "S3"
|
||||
msgstr "S3"
|
||||
|
||||
@ -7913,6 +7923,19 @@ msgstr ""
|
||||
"以下を実行して、ホストを一覧表示し、インスタンスを退避するための別のホストを"
|
||||
"探します。"
|
||||
|
||||
msgid ""
|
||||
"To preserve the user disk data on the evacuated server, deploy OpenStack "
|
||||
"Compute with a shared file system. To configure your system, see `Configure "
|
||||
"migrations <http://docs.openstack.org/admin-guide-cloud/compute-configuring-"
|
||||
"migrations.html>`_ in OpenStack Cloud Administrator Guide. In the following "
|
||||
"example, the password remains unchanged::"
|
||||
msgstr ""
|
||||
"退避したサーバーにユーザーディスクのデータを保存する場合、共有ファイルシステ"
|
||||
"ムを持つ OpenStack Compute を配備します。お使いのシステムの設定方法は "
|
||||
"OpenStack Cloud Administrator Guide の `Configure migrations <http://docs."
|
||||
"openstack.org/admin-guide-cloud/compute-configuring-migrations.html>`_ を参照"
|
||||
"してください。以下の例では、パスワードがそのままになります。"
|
||||
|
||||
msgid ""
|
||||
"To preserve the user disk data on the evacuated server, deploy OpenStack "
|
||||
"Compute with a shared file system. To configure your system, see `Configure "
|
||||
|
||||
@ -7,8 +7,8 @@
|
||||
msgid ""
|
||||
msgstr ""
|
||||
"Project-Id-Version: OpenStack Manuals\n"
|
||||
"POT-Creation-Date: 2015-08-28 01:04+0000\n"
|
||||
"PO-Revision-Date: 2015-08-28 05:51+0000\n"
|
||||
"POT-Creation-Date: 2015-08-28 10:14+0000\n"
|
||||
"PO-Revision-Date: 2015-08-28 09:13+0000\n"
|
||||
"Last-Translator: openstackjenkins <jenkins@openstack.org>\n"
|
||||
"Language-Team: Japanese (http://www.transifex.com/openstack/openstack-"
|
||||
"manuals-i18n/language/ja/)\n"
|
||||
@ -2099,6 +2099,16 @@ msgid "Run the following command to discover the version number for a client:"
|
||||
msgstr ""
|
||||
"クライアントのバージョン番号を確認するために、以下のコマンドを実行します。"
|
||||
|
||||
msgid "Runs operating systems and provides scratch space"
|
||||
msgstr "オペレーティングシステムを実行し、新規領域を提供します"
|
||||
|
||||
msgid ""
|
||||
"Runs within the guest instance. Manages and performs operations on the "
|
||||
"database itself."
|
||||
msgstr ""
|
||||
"ゲストインスタンスの中で実行します。データベース自身の処理を管理、実行しま"
|
||||
"す。"
|
||||
|
||||
msgid "SQL database"
|
||||
msgstr "SQL データベース"
|
||||
|
||||
|
||||
@ -11,8 +11,8 @@
|
||||
msgid ""
|
||||
msgstr ""
|
||||
"Project-Id-Version: OpenStack Manuals\n"
|
||||
"POT-Creation-Date: 2015-08-28 01:04+0000\n"
|
||||
"PO-Revision-Date: 2015-08-27 07:31+0000\n"
|
||||
"POT-Creation-Date: 2015-08-28 10:14+0000\n"
|
||||
"PO-Revision-Date: 2015-08-28 12:11+0000\n"
|
||||
"Last-Translator: openstackjenkins <jenkins@openstack.org>\n"
|
||||
"Language-Team: Chinese (China) (http://www.transifex.com/openstack/openstack-"
|
||||
"manuals-i18n/language/zh_CN/)\n"
|
||||
@ -125,6 +125,9 @@ msgstr "(IntOpt)元数据API监控端口"
|
||||
msgid "(IntOpt) VNC starting port"
|
||||
msgstr "(IntOpt)VNC启动端口"
|
||||
|
||||
msgid "(StrOpt) Backend to use for IPv6 generation"
|
||||
msgstr "(StrOpt) IPv6生成器的后台"
|
||||
|
||||
msgid "(StrOpt) Default IPv6 gateway"
|
||||
msgstr "(StrOpt)缺省IPv6网关"
|
||||
|
||||
@ -156,6 +159,28 @@ msgstr ""
|
||||
"(StrOpt) Location of VNC console proxy, in the form \"http://127.0.0.1:6080/"
|
||||
"vnc_auto.html\""
|
||||
|
||||
msgid ""
|
||||
"(StrOpt) Location of nova xvp VNC console proxy, in the form "
|
||||
"\"http://127.0.0.1:6081/console\""
|
||||
msgstr ""
|
||||
"(StrOpt)nova xvp VNC控制台代理的位置，格式为 \"http://127.0.0.1:6081/console"
|
||||
"\""
|
||||
|
||||
msgid "(StrOpt) OpenStack metadata service manager"
|
||||
msgstr "(StrOpt)OpenStack元数据服务管理者"
|
||||
|
||||
msgid "(StrOpt) Run webserver on same port. Serve files from DIR."
|
||||
msgstr "(StrOpt)在在同样地端口运行websever。服务器文件在目录DIR。"
|
||||
|
||||
msgid "(StrOpt) SSL key file (if separate from cert)"
|
||||
msgstr "(StrOpt)SSL键值文件(从证书中隔离)"
|
||||
|
||||
msgid "(StrOpt) The IP address for the metadata API server"
|
||||
msgstr "(StrOpt) 元数据API服务器的IP地址"
|
||||
|
||||
msgid "(StrOpt) The IP address on which the metadata API will listen."
|
||||
msgstr "(StrOpt)元数据API监听的IP地址"
|
||||
|
||||
msgid "--os-auth_url"
|
||||
msgstr "--os-auth_url"
|
||||
|
||||
|
||||
@ -14,8 +14,8 @@ msgid ""
|
||||
msgstr ""
|
||||
"Project-Id-Version: OpenStack Manuals\n"
|
||||
"Report-Msgid-Bugs-To: \n"
|
||||
"POT-Creation-Date: 2015-08-28 01:05+0000\n"
|
||||
"PO-Revision-Date: 2015-08-27 09:56+0000\n"
|
||||
"POT-Creation-Date: 2015-08-28 10:15+0000\n"
|
||||
"PO-Revision-Date: 2015-08-28 11:26+0000\n"
|
||||
"Last-Translator: Tomoyuki KATO <tomo@dream.daynight.jp>\n"
|
||||
"Language-Team: Japanese (http://www.transifex.com/openstack/openstack-"
|
||||
"manuals-i18n/language/ja/)\n"
|
||||
@ -1022,6 +1022,22 @@ msgstr ""
|
||||
"ローカルストレージを提供します。仮想マシンの終了時、一時ディスクにあるすべて"
|
||||
"のデータは失われます。一時ディスクはスナップショットに含められません。"
|
||||
|
||||
msgid "Evacuate instances"
|
||||
msgstr "インスタンスの退避"
|
||||
|
||||
msgid ""
|
||||
"Evacuate the instance. You can pass the instance password to the command by "
|
||||
"using the :option:`--password PWD` option. If you do not specify a password, "
|
||||
"one is generated and printed after the command finishes successfully. The "
|
||||
"following command evacuates a server without shared storage from a host that "
|
||||
"is down to the specified HOST_B::"
|
||||
msgstr ""
|
||||
" インスタンスを退避します。:option:`--password PWD` オプションを使用して、コ"
|
||||
"マンドにインスタンスのパスワードを指定します。パスワードを指定しない場合は、"
|
||||
"コマンドが正常に完了してから、パスワードが生成、出力されます。以下のコマンド"
|
||||
"では、共有ストレージなしで、停止しているホストから指定の host_b に、サーバー"
|
||||
"を退避させます。"
|
||||
|
||||
# #-#-#-#-# cli_manage_flavors.pot (Admin User Guide 1.0.0) #-#-#-#-#
|
||||
# #-#-#-#-# dashboard_manage_flavors.pot (Admin User Guide 1.0.0) #-#-#-#-#
|
||||
msgid "Flavor"
|
||||
@ -1158,6 +1174,17 @@ msgstr ""
|
||||
msgid "How can I administer an OpenStack cloud?"
|
||||
msgstr "OpenStack クラウドをどのように管理できますか?"
|
||||
|
||||
msgid ""
|
||||
"If a cloud compute node fails due to a hardware malfunction or another "
|
||||
"reason, you can evacuate instances to make them available again. You can "
|
||||
"optionally include the target host on the :command:`evacuate` command. If "
|
||||
"you omit the host, the scheduler determines the target host."
|
||||
msgstr ""
|
||||
"コンピュートノードが、ハードウェアの誤動作や他の理由により異常になった場合、"
|
||||
"インスタンスを後から利用できるようにするために、退避しておくことができます。"
|
||||
"オプションとして、:command:`evacuate` コマンドに退避先ホストを指定できます。"
|
||||
"ホストを省略した場合、スケジューラーが退避先ホストを判断します。"
|
||||
|
||||
msgid ""
|
||||
"If an individual user or group of users needs a custom flavor that you do "
|
||||
"not want other tenants to have access to, you can change the flavor's access "
|
||||
@ -2331,6 +2358,14 @@ msgstr ""
|
||||
"イメージがアップロードのためにキューに入れられます。ステータスが ``Queued`` "
|
||||
"から ``Active`` に変更されるまでに少し時間がかかるかもしれません。"
|
||||
|
||||
msgid ""
|
||||
"The instance is booted from a new disk, but preserves its configuration "
|
||||
"including its ID, name, uid, IP address, and so on. The command returns a "
|
||||
"password::"
|
||||
msgstr ""
|
||||
"インスタンスが新しいディスクから起動されます。ただし、ID、名前、IP アドレスな"
|
||||
"どの現在の設定は維持されます。このコマンドはパスワードを返します。"
|
||||
|
||||
msgid ""
|
||||
"The instance is booted from a new host, but preserves its configuration "
|
||||
"including its ID, name, any metadata, IP address, and other properties."
|
||||
@ -2581,6 +2616,12 @@ msgstr ""
|
||||
"全プロジェクトのすべての Floating IP アドレスを一覧表示するために、以下を実行"
|
||||
"します。"
|
||||
|
||||
msgid ""
|
||||
"To list hosts and find a different host for the evacuated instance, run::"
|
||||
msgstr ""
|
||||
"以下を実行して、ホストを一覧表示し、インスタンスを退避するための別のホストを"
|
||||
"探します。"
|
||||
|
||||
msgid "To list the Networking extensions, run this command::"
|
||||
msgstr "Networking 拡張機能を表示するには、以下のコマンドを実行します。 "
|
||||
|
||||
@ -2603,6 +2644,29 @@ msgstr ""
|
||||
"インスタンスを移行し、状態を確認するために、このサンプルスクリプトを使用しま"
|
||||
"す。"
|
||||
|
||||
msgid ""
|
||||
"To preserve the user disk data on the evacuated server, deploy OpenStack "
|
||||
"Compute with a shared file system. To configure your system, see `Configure "
|
||||
"migrations <http://docs.openstack.org/admin-guide-cloud/compute-configuring-"
|
||||
"migrations.html>`_ in OpenStack Cloud Administrator Guide. In the following "
|
||||
"example, the password remains unchanged::"
|
||||
msgstr ""
|
||||
"退避したサーバーにユーザーディスクのデータを保存する場合、共有ファイルシステ"
|
||||
"ムを持つ OpenStack Compute を配備します。お使いのシステムの設定方法は "
|
||||
"OpenStack Cloud Administrator Guide の `Configure migrations <http://docs."
|
||||
"openstack.org/admin-guide-cloud/compute-configuring-migrations.html>`_ を参照"
|
||||
"してください。以下の例では、パスワードがそのままになります。"
|
||||
|
||||
msgid ""
|
||||
"To preserve user data on server disk, you must configure shared storage on "
|
||||
"the target host. Also, you must validate that the current VM host is down; "
|
||||
"otherwise, the evacuation fails with an error."
|
||||
msgstr ""
|
||||
"サーバーディスクのユーザーデータを保持する場合、退避先ホストにおいて共有ファ"
|
||||
"イルシステムを設定する必要があります。また、現在の仮想マシンのホストが停止状"
|
||||
"態であることを確認してください。停止状態でない場合は、エラーが発生して退避に"
|
||||
"失敗します。"
|
||||
|
||||
# #-#-#-#-# cli_set_quotas.pot (Admin User Guide 1.0.0) #-#-#-#-#
|
||||
# #-#-#-#-# dashboard_set_quotas.pot (Admin User Guide 1.0.0) #-#-#-#-#
|
||||
msgid ""
|
||||
|
||||
@ -8,7 +8,7 @@ msgid ""
|
||||
msgstr ""
|
||||
"Project-Id-Version: Admin User Guide 1.0.0\n"
|
||||
"Report-Msgid-Bugs-To: \n"
|
||||
"POT-Creation-Date: 2015-08-28 06:17+0000\n"
|
||||
"POT-Creation-Date: 2015-08-29 06:16+0000\n"
|
||||
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
|
||||
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
|
||||
"Language-Team: LANGUAGE <LL@li.org>\n"
|
||||
@ -1060,6 +1060,19 @@ msgid ""
|
||||
"lost. Ephemeral disks are not included in any snapshots."
|
||||
msgstr ""
|
||||
|
||||
#: ../cli_nova_evacuate.rst:3
|
||||
msgid "Evacuate instances"
|
||||
msgstr ""
|
||||
|
||||
#: ../cli_nova_evacuate.rst:19
|
||||
msgid ""
|
||||
"Evacuate the instance. You can pass the instance password to the command by "
|
||||
"using the :option:`--password PWD` option. If you do not specify a password, "
|
||||
"one is generated and printed after the command finishes successfully. The "
|
||||
"following command evacuates a server without shared storage from a host that "
|
||||
"is down to the specified HOST_B::"
|
||||
msgstr ""
|
||||
|
||||
# #-#-#-#-# cli_manage_flavors.pot (Admin User Guide 1.0.0) #-#-#-#-#
|
||||
# #-#-#-#-# dashboard_manage_flavors.pot (Admin User Guide 1.0.0) #-#-#-#-#
|
||||
#: ../cli_manage_flavors.rst:53 ../dashboard_manage_flavors.rst:12
|
||||
@ -1196,6 +1209,14 @@ msgstr ""
|
||||
msgid "How can I administer an OpenStack cloud?"
|
||||
msgstr ""
|
||||
|
||||
#: ../cli_nova_evacuate.rst:5
|
||||
msgid ""
|
||||
"If a cloud compute node fails due to a hardware malfunction or another "
|
||||
"reason, you can evacuate instances to make them available again. You can "
|
||||
"optionally include the target host on the :command:`evacuate` command. If "
|
||||
"you omit the host, the scheduler determines the target host."
|
||||
msgstr ""
|
||||
|
||||
#: ../cli_manage_flavors.rst:98
|
||||
msgid ""
|
||||
"If an individual user or group of users needs a custom flavor that you do "
|
||||
@ -2352,6 +2373,13 @@ msgid ""
|
||||
"status changes from ``Queued`` to ``Active``."
|
||||
msgstr ""
|
||||
|
||||
#: ../cli_nova_evacuate.rst:28
|
||||
msgid ""
|
||||
"The instance is booted from a new disk, but preserves its configuration "
|
||||
"including its ID, name, uid, IP address, and so on. The command returns a "
|
||||
"password::"
|
||||
msgstr ""
|
||||
|
||||
#: ../cli_nova_migrate.rst:74
|
||||
msgid ""
|
||||
"The instance is booted from a new host, but preserves its configuration "
|
||||
@ -2572,6 +2600,11 @@ msgstr ""
|
||||
msgid "To list all floating IP addresses for all projects, run::"
|
||||
msgstr ""
|
||||
|
||||
#: ../cli_nova_evacuate.rst:15
|
||||
msgid ""
|
||||
"To list hosts and find a different host for the evacuated instance, run::"
|
||||
msgstr ""
|
||||
|
||||
#: ../networking_advanced_quotas.rst:114
|
||||
msgid "To list the Networking extensions, run this command::"
|
||||
msgstr ""
|
||||
@ -2595,6 +2628,22 @@ msgid ""
|
||||
"To migrate of an instance and watch the status, use this example script:"
|
||||
msgstr ""
|
||||
|
||||
#: ../cli_nova_evacuate.rst:38
|
||||
msgid ""
|
||||
"To preserve the user disk data on the evacuated server, deploy OpenStack "
|
||||
"Compute with a shared file system. To configure your system, see `Configure "
|
||||
"migrations <http://docs.openstack.org/admin-guide-cloud/compute-configuring-"
|
||||
"migrations.html>`_ in OpenStack Cloud Administrator Guide. In the following "
|
||||
"example, the password remains unchanged::"
|
||||
msgstr ""
|
||||
|
||||
#: ../cli_nova_evacuate.rst:11
|
||||
msgid ""
|
||||
"To preserve user data on server disk, you must configure shared storage on "
|
||||
"the target host. Also, you must validate that the current VM host is down; "
|
||||
"otherwise, the evacuation fails with an error."
|
||||
msgstr ""
|
||||
|
||||
# #-#-#-#-# cli_set_quotas.pot (Admin User Guide 1.0.0) #-#-#-#-#
|
||||
# #-#-#-#-# dashboard_set_quotas.pot (Admin User Guide 1.0.0) #-#-#-#-#
|
||||
#: ../cli_set_quotas.rst:5 ../dashboard_set_quotas.rst:10
|
||||
|
||||
Loading…
Reference in New Issue
Block a user