Imported Translations from Transifex
For more information about this automatic import see: https://wiki.openstack.org/wiki/Translations/Infrastructure Change-Id: Ic21802bff439b5e6dc4eba0bc7ead588e1a0f8e5
This commit is contained in:
OpenStack Proposal Bot
parent
49a5d96756
commit
38b31b34a8
@ -1,7 +1,7 @@
|
||||
msgid ""
|
||||
msgstr ""
|
||||
"Project-Id-Version: PACKAGE VERSION\n"
|
||||
"POT-Creation-Date: 2015-01-17 06:12+0000\n"
|
||||
"POT-Creation-Date: 2015-01-20 06:12+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"
|
||||
@ -5544,7 +5544,7 @@ msgstr ""
|
||||
msgid "Support Native Sorting"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/admin-guide-cloud/networking/section_networking_pagination_and_sorting_support.xml:20(td) ./doc/admin-guide-cloud/networking/section_networking-scenarios.xml:679(title)
|
||||
#: ./doc/admin-guide-cloud/networking/section_networking_pagination_and_sorting_support.xml:20(td) ./doc/admin-guide-cloud/networking/section_networking-scenarios.xml:684(title)
|
||||
msgid "ML2"
|
||||
msgstr ""
|
||||
|
||||
@ -6206,7 +6206,7 @@ msgstr ""
|
||||
|
||||
#. When image changes, this message will be marked fuzzy or untranslated for you.
|
||||
#. It doesn't matter what you translate it to: it's not used at all.
|
||||
#: ./doc/admin-guide-cloud/networking/section_networking-scenarios.xml:36(None) ./doc/admin-guide-cloud/networking/section_networking-scenarios.xml:483(None)
|
||||
#: ./doc/admin-guide-cloud/networking/section_networking-scenarios.xml:36(None) ./doc/admin-guide-cloud/networking/section_networking-scenarios.xml:488(None)
|
||||
msgid "@@image: '../../common/figures/under-the-hood-scenario-1.png'; md5=6c8c80ff7e23cc2c7c7e1aa66e1fd8c0"
|
||||
msgstr ""
|
||||
|
||||
@ -6230,7 +6230,7 @@ msgstr ""
|
||||
|
||||
#. When image changes, this message will be marked fuzzy or untranslated for you.
|
||||
#. It doesn't matter what you translate it to: it's not used at all.
|
||||
#: ./doc/admin-guide-cloud/networking/section_networking-scenarios.xml:317(None) ./doc/admin-guide-cloud/networking/section_networking-scenarios.xml:593(None)
|
||||
#: ./doc/admin-guide-cloud/networking/section_networking-scenarios.xml:317(None) ./doc/admin-guide-cloud/networking/section_networking-scenarios.xml:598(None)
|
||||
msgid "@@image: '../../common/figures/under-the-hood-scenario-2.png'; md5=148feb87744e7b04da21ec4f17503c75"
|
||||
msgstr ""
|
||||
|
||||
@ -6260,49 +6260,49 @@ msgstr ""
|
||||
|
||||
#. When image changes, this message will be marked fuzzy or untranslated for you.
|
||||
#. It doesn't matter what you translate it to: it's not used at all.
|
||||
#: ./doc/admin-guide-cloud/networking/section_networking-scenarios.xml:524(None)
|
||||
#: ./doc/admin-guide-cloud/networking/section_networking-scenarios.xml:529(None)
|
||||
msgid "@@image: '../../common/figures/under-the-hood-scenario-1-linuxbridge-compute.png'; md5=8270a65d291a628c7091997414046167"
|
||||
msgstr ""
|
||||
|
||||
#. When image changes, this message will be marked fuzzy or untranslated for you.
|
||||
#. It doesn't matter what you translate it to: it's not used at all.
|
||||
#: ./doc/admin-guide-cloud/networking/section_networking-scenarios.xml:568(None)
|
||||
#: ./doc/admin-guide-cloud/networking/section_networking-scenarios.xml:573(None)
|
||||
msgid "@@image: '../../common/figures/under-the-hood-scenario-1-linuxbridge-network.png'; md5=bd78453eb11ffebddf55484ca2cd125e"
|
||||
msgstr ""
|
||||
|
||||
#. When image changes, this message will be marked fuzzy or untranslated for you.
|
||||
#. It doesn't matter what you translate it to: it's not used at all.
|
||||
#: ./doc/admin-guide-cloud/networking/section_networking-scenarios.xml:581(None)
|
||||
#: ./doc/admin-guide-cloud/networking/section_networking-scenarios.xml:586(None)
|
||||
msgid "@@image: '../../common/figures/under-the-hood-scenario-1-linuxbridge-netns.png'; md5=915d10e90cbb18e887b4d5eb5ea15e58"
|
||||
msgstr ""
|
||||
|
||||
#. When image changes, this message will be marked fuzzy or untranslated for you.
|
||||
#. It doesn't matter what you translate it to: it's not used at all.
|
||||
#: ./doc/admin-guide-cloud/networking/section_networking-scenarios.xml:637(None)
|
||||
#: ./doc/admin-guide-cloud/networking/section_networking-scenarios.xml:642(None)
|
||||
msgid "@@image: '../../common/figures/under-the-hood-scenario-2-linuxbridge-compute.png'; md5=f68f0baeba932b219574e55853bd2300"
|
||||
msgstr ""
|
||||
|
||||
#. When image changes, this message will be marked fuzzy or untranslated for you.
|
||||
#. It doesn't matter what you translate it to: it's not used at all.
|
||||
#: ./doc/admin-guide-cloud/networking/section_networking-scenarios.xml:655(None)
|
||||
#: ./doc/admin-guide-cloud/networking/section_networking-scenarios.xml:660(None)
|
||||
msgid "@@image: '../../common/figures/under-the-hood-scenario-2-linuxbridge-network.png'; md5=25f818f7f9148152e5a8dbf6d530dcf6"
|
||||
msgstr ""
|
||||
|
||||
#. When image changes, this message will be marked fuzzy or untranslated for you.
|
||||
#. It doesn't matter what you translate it to: it's not used at all.
|
||||
#: ./doc/admin-guide-cloud/networking/section_networking-scenarios.xml:665(None)
|
||||
#: ./doc/admin-guide-cloud/networking/section_networking-scenarios.xml:670(None)
|
||||
msgid "@@image: '../../common/figures/under-the-hood-scenario-2-linuxbridge-netns.png'; md5=cdc0bd4b3e7988f7fedffefae4dae9d0"
|
||||
msgstr ""
|
||||
|
||||
#. When image changes, this message will be marked fuzzy or untranslated for you.
|
||||
#. It doesn't matter what you translate it to: it's not used at all.
|
||||
#: ./doc/admin-guide-cloud/networking/section_networking-scenarios.xml:708(None)
|
||||
#: ./doc/admin-guide-cloud/networking/section_networking-scenarios.xml:713(None)
|
||||
msgid "@@image: '../../common/figures/ml2_without_l2pop_full_mesh.png'; md5=881485c0686f20b82967d5b817932952"
|
||||
msgstr ""
|
||||
|
||||
#. When image changes, this message will be marked fuzzy or untranslated for you.
|
||||
#. It doesn't matter what you translate it to: it's not used at all.
|
||||
#: ./doc/admin-guide-cloud/networking/section_networking-scenarios.xml:720(None)
|
||||
#: ./doc/admin-guide-cloud/networking/section_networking-scenarios.xml:725(None)
|
||||
msgid "@@image: '../../common/figures/ml2_without_l2pop_partial_mesh.png'; md5=66fe83560a3e1880ffe3a85d80538f83"
|
||||
msgstr ""
|
||||
|
||||
@ -6322,27 +6322,27 @@ msgstr ""
|
||||
msgid "This example uses VLAN segmentation on the switches to isolate tenant networks. This configuration labels the physical network associated with the public network as <literal>physnet1</literal>, and the physical network associated with the data network as <literal>physnet2</literal>, which leads to the following configuration options in <filename>ovs_neutron_plugin.ini</filename>:"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/admin-guide-cloud/networking/section_networking-scenarios.xml:26(title) ./doc/admin-guide-cloud/networking/section_networking-scenarios.xml:472(title)
|
||||
#: ./doc/admin-guide-cloud/networking/section_networking-scenarios.xml:26(title) ./doc/admin-guide-cloud/networking/section_networking-scenarios.xml:477(title)
|
||||
msgid "Scenario 1: one tenant, two networks, one router"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/admin-guide-cloud/networking/section_networking-scenarios.xml:27(para) ./doc/admin-guide-cloud/networking/section_networking-scenarios.xml:473(para)
|
||||
#: ./doc/admin-guide-cloud/networking/section_networking-scenarios.xml:27(para) ./doc/admin-guide-cloud/networking/section_networking-scenarios.xml:478(para)
|
||||
msgid "The first scenario has two private networks (<literal>net01</literal>, and <literal>net02</literal>), each with one subnet (<literal>net01_subnet01</literal>: 192.168.101.0/24, <literal>net02_subnet01</literal>, 192.168.102.0/24). Both private networks are attached to a router that connects them to the public network (10.64.201.0/24)."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/admin-guide-cloud/networking/section_networking-scenarios.xml:39(para) ./doc/admin-guide-cloud/networking/section_networking-scenarios.xml:486(para)
|
||||
#: ./doc/admin-guide-cloud/networking/section_networking-scenarios.xml:39(para) ./doc/admin-guide-cloud/networking/section_networking-scenarios.xml:491(para)
|
||||
msgid "Under the <literal>service</literal> tenant, create the shared router, define the public network, and set it as the default gateway of the router<placeholder-1/>"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/admin-guide-cloud/networking/section_networking-scenarios.xml:50(para) ./doc/admin-guide-cloud/networking/section_networking-scenarios.xml:497(para)
|
||||
#: ./doc/admin-guide-cloud/networking/section_networking-scenarios.xml:50(para) ./doc/admin-guide-cloud/networking/section_networking-scenarios.xml:502(para)
|
||||
msgid "Under the <literal>demo</literal> user tenant, create the private network <literal>net01</literal> and corresponding subnet, and connect it to the <literal>router01</literal> router. Configure it to use VLAN ID 101 on the physical switch.<placeholder-1/>"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/admin-guide-cloud/networking/section_networking-scenarios.xml:61(para) ./doc/admin-guide-cloud/networking/section_networking-scenarios.xml:508(para)
|
||||
#: ./doc/admin-guide-cloud/networking/section_networking-scenarios.xml:61(para) ./doc/admin-guide-cloud/networking/section_networking-scenarios.xml:513(para)
|
||||
msgid "Similarly, for <literal>net02</literal>, using VLAN ID 102 on the physical switch:<placeholder-1/>"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/admin-guide-cloud/networking/section_networking-scenarios.xml:69(title) ./doc/admin-guide-cloud/networking/section_networking-scenarios.xml:517(title)
|
||||
#: ./doc/admin-guide-cloud/networking/section_networking-scenarios.xml:69(title) ./doc/admin-guide-cloud/networking/section_networking-scenarios.xml:522(title)
|
||||
msgid "Scenario 1: Compute host config"
|
||||
msgstr ""
|
||||
|
||||
@ -6350,7 +6350,7 @@ msgstr ""
|
||||
msgid "The following figure shows how to configure various Linux networking devices on the compute host:"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/admin-guide-cloud/networking/section_networking-scenarios.xml:80(title) ./doc/admin-guide-cloud/networking/section_networking-scenarios.xml:529(title)
|
||||
#: ./doc/admin-guide-cloud/networking/section_networking-scenarios.xml:80(title) ./doc/admin-guide-cloud/networking/section_networking-scenarios.xml:534(title)
|
||||
msgid "Types of network devices"
|
||||
msgstr ""
|
||||
|
||||
@ -6358,7 +6358,7 @@ msgstr ""
|
||||
msgid "There are four distinct type of virtual networking devices: TAP devices, veth pairs, Linux bridges, and Open vSwitch bridges. For an Ethernet frame to travel from <literal>eth0</literal> of virtual machine <literal>vm01</literal> to the physical network, it must pass through nine devices inside of the host: TAP <literal>vnet0</literal>, Linux bridge <literal>qbr<replaceable>NNN</replaceable></literal>, veth pair <literal>(qvb<replaceable>NNN</replaceable>, qvo<replaceable>NNN</replaceable>)</literal>, Open vSwitch bridge <literal>br-int</literal>, veth pair <literal>(int-br-eth1, phy-br-eth1)</literal>, and, finally, the physical network interface card <literal>eth1</literal>."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/admin-guide-cloud/networking/section_networking-scenarios.xml:94(para) ./doc/admin-guide-cloud/networking/section_networking-scenarios.xml:540(para)
|
||||
#: ./doc/admin-guide-cloud/networking/section_networking-scenarios.xml:94(para) ./doc/admin-guide-cloud/networking/section_networking-scenarios.xml:545(para)
|
||||
msgid "A <emphasis role=\"italic\">TAP device</emphasis>, such as <literal>vnet0</literal> is how hypervisors such as KVM and Xen implement a virtual network interface card (typically called a VIF or vNIC). An Ethernet frame sent to a TAP device is received by the guest operating system."
|
||||
msgstr ""
|
||||
|
||||
@ -6410,7 +6410,7 @@ msgstr ""
|
||||
msgid "Networking uses an extra Linux bridge and a veth pair as a workaround for this issue. Instead of connecting <literal>vnet0</literal> to an Open vSwitch bridge, it is connected to a Linux bridge, <literal>qbr<replaceable>XXX</replaceable></literal>. This bridge is connected to the integration bridge, <literal>br-int</literal>, through the <literal>(qvb<replaceable>XXX</replaceable>, qvo<replaceable>XXX</replaceable>)</literal> veth pair."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/admin-guide-cloud/networking/section_networking-scenarios.xml:167(title) ./doc/admin-guide-cloud/networking/section_networking-scenarios.xml:562(title)
|
||||
#: ./doc/admin-guide-cloud/networking/section_networking-scenarios.xml:167(title) ./doc/admin-guide-cloud/networking/section_networking-scenarios.xml:567(title)
|
||||
msgid "Scenario 1: Network host config"
|
||||
msgstr ""
|
||||
|
||||
@ -6498,7 +6498,7 @@ msgstr ""
|
||||
msgid "In this example, there are three network namespaces, as shown in the figure above:<placeholder-1/>"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/admin-guide-cloud/networking/section_networking-scenarios.xml:311(title) ./doc/admin-guide-cloud/networking/section_networking-scenarios.xml:587(title)
|
||||
#: ./doc/admin-guide-cloud/networking/section_networking-scenarios.xml:311(title) ./doc/admin-guide-cloud/networking/section_networking-scenarios.xml:592(title)
|
||||
msgid "Scenario 2: two tenants, two networks, two routers"
|
||||
msgstr ""
|
||||
|
||||
@ -6506,7 +6506,7 @@ msgstr ""
|
||||
msgid "In this scenario, tenant A and tenant B each have a network with one subnet and one router that connects the tenants to the public Internet."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/admin-guide-cloud/networking/section_networking-scenarios.xml:320(para) ./doc/admin-guide-cloud/networking/section_networking-scenarios.xml:596(para)
|
||||
#: ./doc/admin-guide-cloud/networking/section_networking-scenarios.xml:320(para) ./doc/admin-guide-cloud/networking/section_networking-scenarios.xml:601(para)
|
||||
msgid "Under the <literal>service</literal> tenant, define the public network:<placeholder-1/>"
|
||||
msgstr ""
|
||||
|
||||
@ -6514,11 +6514,11 @@ msgstr ""
|
||||
msgid "Under the <literal>tenantA</literal> user tenant, create the tenant router and set its gateway for the public network.<placeholder-1/> Then, define private network <literal>net01</literal> using VLAN ID 101 on the physical switch, along with its subnet, and connect it to the router. <placeholder-2/>"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/admin-guide-cloud/networking/section_networking-scenarios.xml:341(para) ./doc/admin-guide-cloud/networking/section_networking-scenarios.xml:617(para)
|
||||
#: ./doc/admin-guide-cloud/networking/section_networking-scenarios.xml:341(para) ./doc/admin-guide-cloud/networking/section_networking-scenarios.xml:622(para)
|
||||
msgid "Similarly, for <literal>tenantB</literal>, create a router and another network, using VLAN ID 102 on the physical switch:<placeholder-1/>"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/admin-guide-cloud/networking/section_networking-scenarios.xml:353(title) ./doc/admin-guide-cloud/networking/section_networking-scenarios.xml:630(title)
|
||||
#: ./doc/admin-guide-cloud/networking/section_networking-scenarios.xml:353(title) ./doc/admin-guide-cloud/networking/section_networking-scenarios.xml:635(title)
|
||||
msgid "Scenario 2: Compute host config"
|
||||
msgstr ""
|
||||
|
||||
@ -6530,11 +6530,11 @@ msgstr ""
|
||||
msgid "The compute host configuration resembles the configuration in scenario 1. However, in scenario 1, a guest connects to two subnets while in this scenario, the subnets belong to different tenants."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/admin-guide-cloud/networking/section_networking-scenarios.xml:370(title) ./doc/admin-guide-cloud/networking/section_networking-scenarios.xml:648(title)
|
||||
#: ./doc/admin-guide-cloud/networking/section_networking-scenarios.xml:370(title) ./doc/admin-guide-cloud/networking/section_networking-scenarios.xml:653(title)
|
||||
msgid "Scenario 2: Network host config"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/admin-guide-cloud/networking/section_networking-scenarios.xml:371(para) ./doc/admin-guide-cloud/networking/section_networking-scenarios.xml:649(para)
|
||||
#: ./doc/admin-guide-cloud/networking/section_networking-scenarios.xml:371(para) ./doc/admin-guide-cloud/networking/section_networking-scenarios.xml:654(para)
|
||||
msgid "The following figure shows the network devices on the network host for the second scenario."
|
||||
msgstr ""
|
||||
|
||||
@ -6598,127 +6598,131 @@ msgstr ""
|
||||
msgid "This example uses VLAN isolation on the switches to isolate tenant networks. This configuration labels the physical network associated with the public network as <literal>physnet1</literal>, and the physical network associated with the data network as <literal>physnet2</literal>, which leads to the following configuration options in <filename>linuxbridge_conf.ini</filename>:"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/admin-guide-cloud/networking/section_networking-scenarios.xml:518(para)
|
||||
#: ./doc/admin-guide-cloud/networking/section_networking-scenarios.xml:471(para)
|
||||
msgid "In this configuration there isn't a bridge mapping for <literal>physnet1</literal> as it is only needed on the network host, which maps it to the Open vSwitch bridge <literal>br-ex</literal> connected to the external network as seen below."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/admin-guide-cloud/networking/section_networking-scenarios.xml:523(para)
|
||||
msgid "The following figure shows how to configure the various Linux networking devices on the compute host."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/admin-guide-cloud/networking/section_networking-scenarios.xml:531(para)
|
||||
#: ./doc/admin-guide-cloud/networking/section_networking-scenarios.xml:536(para)
|
||||
msgid "There are three distinct type of virtual networking devices: TAP devices, VLAN devices, and Linux bridges. For an Ethernet frame to travel from <literal>eth0</literal> of virtual machine <literal>vm01</literal>, to the physical network, it must pass through four devices inside of the host: TAP <literal>vnet0</literal>, Linux bridge <literal>brq<replaceable>XXX</replaceable></literal>, VLAN <literal>eth1.101)</literal>, and, finally, the physical network interface card <literal>eth1</literal>."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/admin-guide-cloud/networking/section_networking-scenarios.xml:545(para)
|
||||
#: ./doc/admin-guide-cloud/networking/section_networking-scenarios.xml:550(para)
|
||||
msgid "A <emphasis role=\"italic\">VLAN device</emphasis> is associated with a VLAN tag attaches to an existing interface device and adds or removes VLAN tags. In the preceding example, VLAN device <literal>eth1.101</literal> is associated with VLAN ID 101 and is attached to interface <literal>eth1</literal>. Packets received from the outside by <literal>eth1</literal> with VLAN tag 101 will be passed to device <literal>eth1.101</literal>, which will then strip the tag. In the other direction, any Ethernet frame sent directly to eth1.101 will have VLAN tag 101 added and will be forward to <literal>eth1</literal> for sending out to the network."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/admin-guide-cloud/networking/section_networking-scenarios.xml:555(para)
|
||||
#: ./doc/admin-guide-cloud/networking/section_networking-scenarios.xml:560(para)
|
||||
msgid "A <emphasis role=\"italic\">Linux bridge</emphasis> behaves like a hub: you can connect multiple (physical or virtual) network interfaces devices to a Linux bridge. Any Ethernet frames that come in from one interface attached to the bridge is transmitted to all of the other devices."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/admin-guide-cloud/networking/section_networking-scenarios.xml:563(para)
|
||||
#: ./doc/admin-guide-cloud/networking/section_networking-scenarios.xml:568(para)
|
||||
msgid "The following figure shows the network devices on the network host."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/admin-guide-cloud/networking/section_networking-scenarios.xml:571(para)
|
||||
#: ./doc/admin-guide-cloud/networking/section_networking-scenarios.xml:576(para)
|
||||
msgid "The following figure shows how the Linux Bridge plug-in uses network namespaces to provide isolation."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/admin-guide-cloud/networking/section_networking-scenarios.xml:574(para)
|
||||
#: ./doc/admin-guide-cloud/networking/section_networking-scenarios.xml:579(para)
|
||||
msgid "veth pairs form connections between the Linux bridges and the network namespaces."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/admin-guide-cloud/networking/section_networking-scenarios.xml:588(para)
|
||||
#: ./doc/admin-guide-cloud/networking/section_networking-scenarios.xml:593(para)
|
||||
msgid "The second scenario has two tenants (A, B). Each tenant has a network with one subnet, and each one has a router that connects them to the public Internet."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/admin-guide-cloud/networking/section_networking-scenarios.xml:604(para)
|
||||
#: ./doc/admin-guide-cloud/networking/section_networking-scenarios.xml:609(para)
|
||||
msgid "Under the <literal>tenantA</literal> user tenant, create the tenant router and set its gateway for the public network.<placeholder-1/> Then, define private network <literal>net01</literal> using VLAN ID 102 on the physical switch, along with its subnet, and connect it to the router. <placeholder-2/>"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/admin-guide-cloud/networking/section_networking-scenarios.xml:631(para)
|
||||
#: ./doc/admin-guide-cloud/networking/section_networking-scenarios.xml:636(para)
|
||||
msgid "The following figure shows how the various Linux networking devices would be configured on the compute host under this scenario."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/admin-guide-cloud/networking/section_networking-scenarios.xml:641(para)
|
||||
#: ./doc/admin-guide-cloud/networking/section_networking-scenarios.xml:646(para)
|
||||
msgid "The configuration on the compute host is very similar to the configuration in scenario 1. The only real difference is that scenario 1 had a guest connected to two subnets, and in this scenario the subnets belong to different tenants."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/admin-guide-cloud/networking/section_networking-scenarios.xml:658(para)
|
||||
#: ./doc/admin-guide-cloud/networking/section_networking-scenarios.xml:663(para)
|
||||
msgid "The main difference between the configuration in this scenario and the previous one is the organization of the network namespaces, in order to provide isolation across the two subnets, as shown in the following figure."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/admin-guide-cloud/networking/section_networking-scenarios.xml:668(para)
|
||||
#: ./doc/admin-guide-cloud/networking/section_networking-scenarios.xml:673(para)
|
||||
msgid "In this scenario, there are four network namespaces (<literal>qhdcp-<replaceable>AAA</replaceable></literal>, <literal>qrouter-<replaceable>BBBB</replaceable></literal>, <literal>qrouter-<replaceable>CCCC</replaceable></literal>, and <literal>qhdcp-<replaceable>DDDD</replaceable></literal>), instead of three. Each router is implemented by a separate namespace, since there is no connectivity between the two networks."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/admin-guide-cloud/networking/section_networking-scenarios.xml:680(para)
|
||||
#: ./doc/admin-guide-cloud/networking/section_networking-scenarios.xml:685(para)
|
||||
msgid "The Modular Layer 2 plug-in allows OpenStack Networking to simultaneously utilize the variety of layer 2 networking technologies found in complex real-world data centers. It currently includes drivers for the local, flat, VLAN, GRE and VXLAN network types and works with the existing <emphasis>Open vSwitch</emphasis>, <emphasis>Linux Bridge </emphasis>, and <emphasis>HyperV</emphasis> L2 agents. The <emphasis>ML2</emphasis> plug-in can be extended through mechanism drivers, allowing multiple mechanisms to be used simultaneously. This section describes different <emphasis>ML2</emphasis> plug-in and agent configurations with different type drivers and mechanism drivers."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/admin-guide-cloud/networking/section_networking-scenarios.xml:688(para)
|
||||
#: ./doc/admin-guide-cloud/networking/section_networking-scenarios.xml:693(para)
|
||||
msgid "Previously, Networking deployments were only able to use the plug-in that had been selected at implementation time. For example, a deployment running the Open vSwitch plug-in was only able to use Open vSwitch exclusively; it wasn't possible to simultaneously run another plug-in such as Linux Bridge. This was found to be a limitation in environments with heterogeneous requirements."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/admin-guide-cloud/networking/section_networking-scenarios.xml:694(para)
|
||||
#: ./doc/admin-guide-cloud/networking/section_networking-scenarios.xml:699(para)
|
||||
msgid "Disabling a ML2 type driver and re-enabling it later may lead to database inconsistencies if ML2 is reconfigured without support for that type."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/admin-guide-cloud/networking/section_networking-scenarios.xml:698(title)
|
||||
#: ./doc/admin-guide-cloud/networking/section_networking-scenarios.xml:703(title)
|
||||
msgid "ML2 with L2 population mechanism driver"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/admin-guide-cloud/networking/section_networking-scenarios.xml:699(para)
|
||||
#: ./doc/admin-guide-cloud/networking/section_networking-scenarios.xml:704(para)
|
||||
msgid "The L2 Population driver enables broadcast, multicast, and unicast traffic to scale out on large overlay networks. This traffic is sent to the relevant agent via encapsulation as a targeted unicast."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/admin-guide-cloud/networking/section_networking-scenarios.xml:702(para)
|
||||
#: ./doc/admin-guide-cloud/networking/section_networking-scenarios.xml:707(para)
|
||||
msgid "Current <emphasis>Open vSwitch</emphasis> and <emphasis>Linux Bridge</emphasis> tunneling implementations broadcast to every agent, even if they don't host the corresponding network as illustrated below."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/admin-guide-cloud/networking/section_networking-scenarios.xml:711(para)
|
||||
#: ./doc/admin-guide-cloud/networking/section_networking-scenarios.xml:716(para)
|
||||
msgid "As broadcast emulation on overlay is costly, it may be better to avoid its use for MAC learning and ARP resolution. This supposes the use of proxy ARP on the agent to answer VM requests, and to populate forwarding table. Currently only the <emphasis>Linux Bridge</emphasis> Agent implements an ARP proxy. The pre-population limits L2 broadcasts in overlay, however it may anyway be necessary to provide broadcast emulation. This is achieved by broadcasting packets via unicast only to the relevant agents as illustrated below.<placeholder-1/>The partial-mesh is available with the <emphasis>Open vSwitch</emphasis> and <emphasis>Linux Bridge</emphasis> agents. The following scenarios will use the L2 population mechanism driver with an <emphasis>Open vSwitch</emphasis> agent and a <emphasis>Linux Bridge</emphasis> agent. Enable the l2 population driver by adding it to the list of mechanism drivers. In addition, a tunneling driver must be selected. Supported options are GRE, VXLAN, or a combination of both. Configuration settings are enabled in <filename>ml2_conf.ini</filename>:"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/admin-guide-cloud/networking/section_networking-scenarios.xml:735(title)
|
||||
#: ./doc/admin-guide-cloud/networking/section_networking-scenarios.xml:740(title)
|
||||
msgid "Scenario 1: L2 population with Open vSwitch agent"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/admin-guide-cloud/networking/section_networking-scenarios.xml:736(para)
|
||||
#: ./doc/admin-guide-cloud/networking/section_networking-scenarios.xml:741(para)
|
||||
msgid "Enable the l2 population extension in the <emphasis>Open vSwitch</emphasis> agent, and configure the <placeholder-1/> and <placeholder-2/> parameters in the <filename>ml2_conf.ini</filename> file:"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/admin-guide-cloud/networking/section_networking-scenarios.xml:740(replaceable) ./doc/admin-guide-cloud/networking/section_networking-scenarios.xml:753(replaceable)
|
||||
#: ./doc/admin-guide-cloud/networking/section_networking-scenarios.xml:745(replaceable) ./doc/admin-guide-cloud/networking/section_networking-scenarios.xml:758(replaceable)
|
||||
msgid "192.168.1.10"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/admin-guide-cloud/networking/section_networking-scenarios.xml:743(replaceable)
|
||||
#: ./doc/admin-guide-cloud/networking/section_networking-scenarios.xml:748(replaceable)
|
||||
msgid "GRE"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/admin-guide-cloud/networking/section_networking-scenarios.xml:743(replaceable)
|
||||
#: ./doc/admin-guide-cloud/networking/section_networking-scenarios.xml:748(replaceable)
|
||||
msgid "VXLAN"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/admin-guide-cloud/networking/section_networking-scenarios.xml:747(title)
|
||||
#: ./doc/admin-guide-cloud/networking/section_networking-scenarios.xml:752(title)
|
||||
msgid "Scenario 2: L2 population with <emphasis>Linux Bridge</emphasis> agent"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/admin-guide-cloud/networking/section_networking-scenarios.xml:748(para)
|
||||
#: ./doc/admin-guide-cloud/networking/section_networking-scenarios.xml:753(para)
|
||||
msgid "Enable the l2 population extension on the <emphasis>Linux Bridge</emphasis> agent. Enable VXLAN and configure the local_ip parameter in <filename>ml2_conf.ini</filename>."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/admin-guide-cloud/networking/section_networking-scenarios.xml:757(title)
|
||||
#: ./doc/admin-guide-cloud/networking/section_networking-scenarios.xml:762(title)
|
||||
msgid "Enable security group API"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/admin-guide-cloud/networking/section_networking-scenarios.xml:758(para)
|
||||
#: ./doc/admin-guide-cloud/networking/section_networking-scenarios.xml:763(para)
|
||||
msgid "The ML2 plug-in can concurrently support different L2 agents (or other mechanisms) with different configuration files, so each L2 agent configuration file (such as <filename>ovs_neutron_plugin.ini</filename> or <filename>linuxbridge_conf.ini</filename>) should contain the appropriate <placeholder-1/> value for that agent in addition to setting <placeholder-2/> to <literal>True</literal> (which is the default)."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/admin-guide-cloud/networking/section_networking-scenarios.xml:767(para)
|
||||
#: ./doc/admin-guide-cloud/networking/section_networking-scenarios.xml:772(para)
|
||||
msgid "The <placeholder-1/> value in the API server's <filename>ml2_conf.ini</filename> file does not matter."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/admin-guide-cloud/networking/section_networking-scenarios.xml:770(para)
|
||||
#: ./doc/admin-guide-cloud/networking/section_networking-scenarios.xml:775(para)
|
||||
msgid "To disable the securitygroup API, edit the <filename>ml2_conf.ini</filename> file on the API server, and <filename>ovs_neutron_plugin.ini</filename>, <filename>linuxbridge_conf.ini</filename> or other L2 agent configuration files on the agent servers :"
|
||||
msgstr ""
|
||||
|
||||
|
||||
@ -1,7 +1,7 @@
|
||||
msgid ""
|
||||
msgstr ""
|
||||
"Project-Id-Version: PACKAGE VERSION\n"
|
||||
"POT-Creation-Date: 2015-01-09 06:12+0000\n"
|
||||
"POT-Creation-Date: 2015-01-20 06:12+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"
|
||||
@ -7439,7 +7439,7 @@ msgid "Bare metal command-line client"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/cli-reference/generated/ch_cli_ironic_commands.xml:14(para)
|
||||
msgid "The <placeholder-1/> client is the command-line interface (CLI) for the Bare metal and its extensions. This chapter documents <placeholder-2/> version <literal>0.3.2</literal>."
|
||||
msgid "The <placeholder-1/> client is the command-line interface (CLI) for the Bare metal and its extensions. This chapter documents <placeholder-2/> version <literal>0.3.3</literal>."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/cli-reference/generated/ch_cli_ironic_commands.xml:27(title)
|
||||
|
||||
@ -1,7 +1,7 @@
|
||||
msgid ""
|
||||
msgstr ""
|
||||
"Project-Id-Version: PACKAGE VERSION\n"
|
||||
"POT-Creation-Date: 2015-01-16 06:13+0000\n"
|
||||
"POT-Creation-Date: 2015-01-20 06:12+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"
|
||||
@ -2262,7 +2262,7 @@ msgstr ""
|
||||
msgid "Dashboard/httpd log files"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/dashboard/section_dashboard-log-files.xml:22(td) ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:211(th) ./doc/config-reference/block-storage/drivers/ibm-gpfs-volume-driver.xml:80(th) ./doc/config-reference/block-storage/drivers/hds-hus-driver.xml:309(td) ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:206(th) ./doc/config-reference/block-storage/drivers/coraid-driver.xml:371(th) ./doc/config-reference/block-storage/drivers/hds-hnas-driver.xml:378(td) ./doc/config-reference/compute/section_compute-scheduler.xml:771(th) ./doc/config-reference/compute/section_compute-scheduler.xml:875(th)
|
||||
#: ./doc/config-reference/dashboard/section_dashboard-log-files.xml:22(td) ./doc/config-reference/block-storage/drivers/huawei-storage-driver.xml:211(th) ./doc/config-reference/block-storage/drivers/ibm-gpfs-volume-driver.xml:80(th) ./doc/config-reference/block-storage/drivers/hds-hus-driver.xml:309(td) ./doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml:206(th) ./doc/config-reference/block-storage/drivers/coraid-driver.xml:371(th) ./doc/config-reference/block-storage/drivers/hds-hnas-driver.xml:378(td) ./doc/config-reference/compute/section_compute-scheduler.xml:792(th) ./doc/config-reference/compute/section_compute-scheduler.xml:896(th)
|
||||
msgid "Description"
|
||||
msgstr ""
|
||||
|
||||
@ -3556,7 +3556,7 @@ msgstr ""
|
||||
msgid "Typically a OpenStack Block Storage volume instance has only one such service label. For example, any <literal>svc_0</literal>, <literal>svc_1</literal>, <literal>svc_2</literal>, or <literal>svc_3</literal> can be associated with it. But any mix of these service labels can be used in the same instance <placeholder-1/>."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/block-storage/drivers/hds-hus-driver.xml:306(td) ./doc/config-reference/block-storage/drivers/hds-hnas-driver.xml:375(td) ./doc/config-reference/compute/section_compute-scheduler.xml:770(th) ./doc/config-reference/compute/section_compute-scheduler.xml:874(th)
|
||||
#: ./doc/config-reference/block-storage/drivers/hds-hus-driver.xml:306(td) ./doc/config-reference/block-storage/drivers/hds-hnas-driver.xml:375(td) ./doc/config-reference/compute/section_compute-scheduler.xml:791(th) ./doc/config-reference/compute/section_compute-scheduler.xml:895(th)
|
||||
msgid "Option"
|
||||
msgstr ""
|
||||
|
||||
@ -8942,7 +8942,7 @@ msgstr ""
|
||||
msgid "Sections"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/compute/section_nova-conf.xml:32(literal) ./doc/config-reference/compute/section_compute-scheduler.xml:776(td) ./doc/config-reference/compute/section_compute-scheduler.xml:786(td) ./doc/config-reference/compute/section_compute-scheduler.xml:798(td)
|
||||
#: ./doc/config-reference/compute/section_nova-conf.xml:32(literal) ./doc/config-reference/compute/section_compute-scheduler.xml:797(td) ./doc/config-reference/compute/section_compute-scheduler.xml:807(td) ./doc/config-reference/compute/section_compute-scheduler.xml:819(td)
|
||||
msgid "[DEFAULT]"
|
||||
msgstr ""
|
||||
|
||||
@ -8958,7 +8958,7 @@ msgstr ""
|
||||
msgid "Configures the baremetal hypervisor driver."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/compute/section_nova-conf.xml:49(literal) ./doc/config-reference/compute/section_compute-scheduler.xml:880(td) ./doc/config-reference/compute/section_compute-scheduler.xml:888(td) ./doc/config-reference/compute/section_compute-scheduler.xml:895(td) ./doc/config-reference/compute/section_compute-scheduler.xml:902(td) ./doc/config-reference/compute/section_compute-scheduler.xml:912(td)
|
||||
#: ./doc/config-reference/compute/section_nova-conf.xml:49(literal) ./doc/config-reference/compute/section_compute-scheduler.xml:901(td) ./doc/config-reference/compute/section_compute-scheduler.xml:909(td) ./doc/config-reference/compute/section_compute-scheduler.xml:916(td) ./doc/config-reference/compute/section_compute-scheduler.xml:923(td) ./doc/config-reference/compute/section_compute-scheduler.xml:933(td)
|
||||
msgid "[cells]"
|
||||
msgstr ""
|
||||
|
||||
@ -9046,7 +9046,7 @@ msgstr ""
|
||||
msgid "Configures a matchmaker ring."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/compute/section_nova-conf.xml:142(literal) ./doc/config-reference/compute/section_compute-scheduler.xml:807(td) ./doc/config-reference/compute/section_compute-scheduler.xml:813(td) ./doc/config-reference/compute/section_compute-scheduler.xml:823(td) ./doc/config-reference/compute/section_compute-scheduler.xml:845(td)
|
||||
#: ./doc/config-reference/compute/section_nova-conf.xml:142(literal) ./doc/config-reference/compute/section_compute-scheduler.xml:828(td) ./doc/config-reference/compute/section_compute-scheduler.xml:834(td) ./doc/config-reference/compute/section_compute-scheduler.xml:844(td) ./doc/config-reference/compute/section_compute-scheduler.xml:866(td)
|
||||
msgid "[metrics]"
|
||||
msgstr ""
|
||||
|
||||
@ -10806,7 +10806,7 @@ msgstr ""
|
||||
msgid "When using the VMwareVCDriver (vCenter) with OpenStack Compute with vSphere version 5.0 or earlier, <filename>nova.conf</filename> must include the following extra config option:"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/compute/section_hypervisor_vmware.xml:1017(title) ./doc/config-reference/compute/section_compute-scheduler.xml:943(title)
|
||||
#: ./doc/config-reference/compute/section_hypervisor_vmware.xml:1017(title) ./doc/config-reference/compute/section_compute-scheduler.xml:964(title)
|
||||
msgid "Configuration reference"
|
||||
msgstr ""
|
||||
|
||||
@ -11086,7 +11086,7 @@ msgstr ""
|
||||
|
||||
#. When image changes, this message will be marked fuzzy or untranslated for you.
|
||||
#. It doesn't matter what you translate it to: it's not used at all.
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:753(None)
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:774(None)
|
||||
msgid "@@image: '../../common/figures/nova-weighting-hosts.png'; md5=000eab4cf0deb1da2e692e023065a6ae"
|
||||
msgstr ""
|
||||
|
||||
@ -11351,462 +11351,474 @@ msgid "The Compute API always returns the actual number of CPU cores available o
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:374(title)
|
||||
msgid "DifferentHostFilter"
|
||||
msgid "NUMATopologyFilter"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:375(para)
|
||||
msgid "Schedules the instance on a different host from a set of instances. To take advantage of this filter, the requester must pass a scheduler hint, using <literal>different_host</literal> as the key and a list of instance UUIDs as the value. This filter is the opposite of the <literal>SameHostFilter</literal>. Using the <placeholder-1/> command-line tool, use the <literal>--hint</literal> flag. For example:"
|
||||
msgid "Filters hosts based on the NUMA topology that was specified for the instance through the use of flavor <literal>extra_specs</literal>in combination with the image properties, as described in detail in the related nova-spec document: <placeholder-1/> Filter will try to match the exact NUMA cells of the instance to those of the host. It will consider the standard over-subscription limits each cell, and provide limits to the compute host accordingly."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:387(para)
|
||||
msgid "If instance has no topology defined, it will be considered for any host. If instance has a topology defined, it will be considered only for NUMA capable hosts."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:395(title)
|
||||
msgid "DifferentHostFilter"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:396(para)
|
||||
msgid "Schedules the instance on a different host from a set of instances. To take advantage of this filter, the requester must pass a scheduler hint, using <literal>different_host</literal> as the key and a list of instance UUIDs as the value. This filter is the opposite of the <literal>SameHostFilter</literal>. Using the <placeholder-1/> command-line tool, use the <literal>--hint</literal> flag. For example:"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:408(para)
|
||||
msgid "With the API, use the <literal>os:scheduler_hints</literal> key. For example:"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:393(title)
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:414(title)
|
||||
msgid "DiskFilter"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:394(para)
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:415(para)
|
||||
msgid "Only schedules instances on hosts if there is sufficient disk space available for root and ephemeral storage."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:397(para)
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:418(para)
|
||||
msgid "You can configure this filter to enable a fixed amount of disk overcommitment by using the <literal>disk_allocation_ratio</literal> configuration option in <filename>nova.conf</filename>. The default setting is:"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:404(para)
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:425(para)
|
||||
msgid "Adjusting this value to greater than 1.0 enables scheduling instances while over committing disk resources on the node. This might be desirable if you use an image format that is sparse or copy on write so that each virtual instance does not require a 1:1 allocation of virtual disk to physical storage."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:412(title)
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:433(title)
|
||||
msgid "GroupAffinityFilter"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:414(para)
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:435(para)
|
||||
msgid "This filter is deprecated in favor of <link linkend=\"servergroupantiaffinityfilter\">ServerGroupAffinityFilter</link>."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:418(para)
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:439(para)
|
||||
msgid "The GroupAffinityFilter ensures that an instance is scheduled on to a host from a set of group hosts. To take advantage of this filter, the requester must pass a scheduler hint, using <literal>group</literal> as the key and an arbitrary name as the value. Using the <placeholder-1/> command-line tool, use the <literal>--hint</literal> flag. For example:"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:426(replaceable) ./doc/config-reference/compute/section_compute-scheduler.xml:447(replaceable) ./doc/config-reference/compute/section_compute-scheduler.xml:665(replaceable) ./doc/config-reference/compute/section_compute-scheduler.xml:680(replaceable)
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:447(replaceable) ./doc/config-reference/compute/section_compute-scheduler.xml:468(replaceable) ./doc/config-reference/compute/section_compute-scheduler.xml:686(replaceable) ./doc/config-reference/compute/section_compute-scheduler.xml:701(replaceable)
|
||||
msgid "IMAGE_ID"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:427(para)
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:448(para)
|
||||
msgid "This filter should not be enabled at the same time as <link linkend=\"groupantiaffinityfilter\">GroupAntiAffinityFilter</link> or neither filter will work properly."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:433(title)
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:454(title)
|
||||
msgid "GroupAntiAffinityFilter"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:435(para)
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:456(para)
|
||||
msgid "This filter is deprecated in favor of <link linkend=\"servergroupantiaffinityfilter\">ServerGroupAntiAffinityFilter</link>."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:439(para)
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:460(para)
|
||||
msgid "The GroupAntiAffinityFilter ensures that each instance in a group is on a different host. To take advantage of this filter, the requester must pass a scheduler hint, using <literal>group</literal> as the key and an arbitrary name as the value. Using the <placeholder-1/> command-line tool, use the <literal>--hint</literal> flag. For example:"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:448(para)
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:469(para)
|
||||
msgid "This filter should not be enabled at the same time as <link linkend=\"groupaffinityfilter\">GroupAffinityFilter</link> or neither filter will work properly."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:454(title)
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:475(title)
|
||||
msgid "ImagePropertiesFilter"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:455(para)
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:476(para)
|
||||
msgid "Filters hosts based on properties defined on the instance's image. It passes hosts that can support the specified image properties contained in the instance. Properties include the architecture, hypervisor type, and virtual machine mode. for example, an instance might require a host that runs an ARM-based processor and QEMU as the hypervisor. An image can be decorated with these properties by using:"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:464(para)
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:485(para)
|
||||
msgid "The image properties that the filter checks for are:"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:468(para)
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:489(para)
|
||||
msgid "<literal>architecture</literal>: Architecture describes the machine architecture required by the image. Examples are i686, x86_64, arm, and ppc64."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:474(para)
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:495(para)
|
||||
msgid "<literal>hypervisor_type</literal>: Hypervisor type describes the hypervisor required by the image. Examples are xen, qemu, and xenapi. Note that qemu is used for both QEMU and KVM hypervisor types."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:481(para)
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:502(para)
|
||||
msgid "<literal>vm_mode</literal>: Virtual machine mode describes the hypervisor application binary interface (ABI) required by the image. Examples are 'xen' for Xen 3.0 paravirtual ABI, 'hvm' for native ABI, 'uml' for User Mode Linux paravirtual ABI, exe for container virt executable ABI."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:492(title)
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:513(title)
|
||||
msgid "IsolatedHostsFilter"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:493(para)
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:514(para)
|
||||
msgid "Allows the admin to define a special (isolated) set of images and a special (isolated) set of hosts, such that the isolated images can only run on the isolated hosts, and the isolated hosts can only run isolated images. The flag <literal>restrict_isolated_hosts_to_isolated_images</literal> can be used to force isolated hosts to only run isolated images."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:501(para)
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:522(para)
|
||||
msgid "The admin must specify the isolated set of images and hosts in the <filename>nova.conf</filename> file using the <literal>isolated_hosts</literal> and <literal>isolated_images</literal> configuration options. For example:"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:510(title)
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:531(title)
|
||||
msgid "IoOpsFilter"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:511(para)
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:532(para)
|
||||
msgid "The IoOpsFilter filters hosts by concurrent I/O operations on it. Hosts with too many concurrent I/O operations will be filtered out. The <placeholder-1/> option specifies the maximum number of I/O intensive instances allowed to run on a host. A host will be ignored by the scheduler if more than <placeholder-2/> instances in build, resize, snapshot, migrate, rescue or unshelve task states are running on it."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:524(title)
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:545(title)
|
||||
msgid "JsonFilter"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:529(para)
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:550(para)
|
||||
msgid "="
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:532(para)
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:553(para)
|
||||
msgid "<"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:535(para)
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:556(para)
|
||||
msgid ">"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:538(para)
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:559(para)
|
||||
msgid "in"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:541(para)
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:562(para)
|
||||
msgid "<="
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:544(para)
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:565(para)
|
||||
msgid ">="
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:547(para)
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:568(para)
|
||||
msgid "not"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:550(para)
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:571(para)
|
||||
msgid "or"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:553(para)
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:574(para)
|
||||
msgid "and"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:557(code)
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:578(code)
|
||||
msgid "$free_ram_mb"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:560(code)
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:581(code)
|
||||
msgid "$free_disk_mb"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:563(code)
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:584(code)
|
||||
msgid "$total_usable_ram_mb"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:566(code)
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:587(code)
|
||||
msgid "$vcpus_total"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:569(code)
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:590(code)
|
||||
msgid "$vcpus_used"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:525(para)
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:546(para)
|
||||
msgid "The JsonFilter allows a user to construct a custom filter by passing a scheduler hint in JSON format. The following operators are supported:<placeholder-1/>The filter supports the following variables:<placeholder-2/>Using the <placeholder-3/> command-line tool, use the <literal>--hint</literal> flag:"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:576(para) ./doc/config-reference/compute/section_compute-scheduler.xml:648(para) ./doc/config-reference/compute/section_compute-scheduler.xml:712(para)
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:597(para) ./doc/config-reference/compute/section_compute-scheduler.xml:669(para) ./doc/config-reference/compute/section_compute-scheduler.xml:733(para)
|
||||
msgid "With the API, use the <literal>os:scheduler_hints</literal> key:"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:581(title)
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:602(title)
|
||||
msgid "MetricsFilter"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:582(para)
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:603(para)
|
||||
msgid "Filters hosts based on metrics <literal>weight_setting</literal>. Only hosts with the available metrics are passed so that the metrics weigher will not fail due to these hosts."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:589(title)
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:610(title)
|
||||
msgid "NumInstancesFilter"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:590(para)
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:611(para)
|
||||
msgid "Hosts that have more instances running than specified by the <placeholder-1/> option are filtered out when this filter is in place."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:597(title)
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:618(title)
|
||||
msgid "PciPassthroughFilter"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:598(para)
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:619(para)
|
||||
msgid "The filter schedules instances on a host if the host has devices that meet the device requests in the <literal>extra_specs</literal> attribute for the flavor."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:605(title)
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:626(title)
|
||||
msgid "RamFilter"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:606(para)
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:627(para)
|
||||
msgid "Only schedules instances on hosts that have sufficient RAM available. If this filter is not set, the scheduler may over provision a host based on RAM (for example, the RAM allocated by virtual machine instances may exceed the physical RAM)."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:611(para)
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:632(para)
|
||||
msgid "You can configure this filter to enable a fixed amount of RAM overcommitment by using the <literal>ram_allocation_ratio</literal> configuration option in <filename>nova.conf</filename>. The default setting is:"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:618(para)
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:639(para)
|
||||
msgid "This setting enables 1.5GB instances to run on any compute node with 1GB of free RAM."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:622(title)
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:643(title)
|
||||
msgid "RetryFilter"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:623(para)
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:644(para)
|
||||
msgid "Filters out hosts that have already been attempted for scheduling purposes. If the scheduler selects a host to respond to a service request, and the host fails to respond to the request, this filter prevents the scheduler from retrying that host for the service request."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:629(para)
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:650(para)
|
||||
msgid "This filter is only useful if the <literal>scheduler_max_attempts</literal> configuration option is set to a value greater than zero."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:635(title)
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:656(title)
|
||||
msgid "SameHostFilter"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:636(para)
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:657(para)
|
||||
msgid "Schedules the instance on the same host as another instance in a set of instances. To take advantage of this filter, the requester must pass a scheduler hint, using <literal>same_host</literal> as the key and a list of instance UUIDs as the value. This filter is the opposite of the <literal>DifferentHostFilter</literal>. Using the <placeholder-1/> command-line tool, use the <literal>--hint</literal> flag:"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:653(title)
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:674(title)
|
||||
msgid "ServerGroupAffinityFilter"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:654(para)
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:675(para)
|
||||
msgid "The ServerGroupAffinityFilter ensures that an instance is scheduled on to a host from a set of group hosts. To take advantage of this filter, the requester must create a server group with an <literal>affinity</literal> policy, and pass a scheduler hint, using <literal>group</literal> as the key and the server group UUID as the value. Using the <placeholder-1/> command-line tool, use the <literal>--hint</literal> flag. For example:"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:665(replaceable) ./doc/config-reference/compute/section_compute-scheduler.xml:680(replaceable)
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:686(replaceable) ./doc/config-reference/compute/section_compute-scheduler.xml:701(replaceable)
|
||||
msgid "SERVER_GROUP_UUID"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:668(title)
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:689(title)
|
||||
msgid "ServerGroupAntiAffinityFilter"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:669(para)
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:690(para)
|
||||
msgid "The ServerGroupAntiAffinityFilter ensures that each instance in a group is on a different host. To take advantage of this filter, the requester must create a server group with an <literal>anti-affinity</literal> policy, and pass a scheduler hint, using <literal>group</literal> as the key and the server group UUID as the value. Using the <placeholder-1/> command-line tool, use the <literal>--hint</literal> flag. For example:"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:683(title)
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:704(title)
|
||||
msgid "SimpleCIDRAffinityFilter"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:684(para)
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:705(para)
|
||||
msgid "Schedules the instance based on host IP subnet range. To take advantage of this filter, the requester must specify a range of valid IP address in CIDR format, by passing two scheduler hints:"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:690(literal)
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:711(literal)
|
||||
msgid "build_near_host_ip"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:692(para)
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:713(para)
|
||||
msgid "The first IP address in the subnet (for example, <literal>192.168.1.1</literal>)"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:698(literal)
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:719(literal)
|
||||
msgid "cidr"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:700(para)
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:721(para)
|
||||
msgid "The CIDR that corresponds to the subnet (for example, <literal>/24</literal>)"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:706(para)
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:727(para)
|
||||
msgid "Using the <placeholder-1/> command-line tool, use the <literal>--hint</literal> flag. For example, to specify the IP subnet <literal>192.168.1.1/24</literal>"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:717(title)
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:738(title)
|
||||
msgid "TrustedFilter"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:718(para)
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:739(para)
|
||||
msgid "Filters hosts based on their trust. Only passes hosts that meet the trust requirements specified in the instance properties."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:725(title)
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:746(title)
|
||||
msgid "TypeAffinityFilter"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:726(para)
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:747(para)
|
||||
msgid "Dynamically limits hosts to one instance type. An instance can only be launched on a host, if no instance with different instances types are running on it, or if the host has no running instances at all."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:735(title)
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:756(title)
|
||||
msgid "Weights"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:737(para)
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:758(para)
|
||||
msgid "When resourcing instances, the filter scheduler filters and weights each host in the list of acceptable hosts. Each time the scheduler selects a host, it virtually consumes resources on it, and subsequent selections are adjusted accordingly. This process is useful when the customer asks for the same large amount of instances, because weight is computed for each requested instance."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:744(para)
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:765(para)
|
||||
msgid "All weights are normalized before being summed up; the host with the largest weight is given the highest priority."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:748(title)
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:769(title)
|
||||
msgid "Weighting hosts"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:757(para)
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:778(para)
|
||||
msgid "If cells are used, cells are weighted by the scheduler in the same manner as hosts."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:759(para)
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:780(para)
|
||||
msgid "Hosts and cells are weighted based on the following options in the <filename>/etc/nova/nova.conf</filename> file:"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:763(caption)
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:784(caption)
|
||||
msgid "Host weighting options"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:769(th) ./doc/config-reference/compute/section_compute-scheduler.xml:873(th)
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:790(th) ./doc/config-reference/compute/section_compute-scheduler.xml:894(th)
|
||||
msgid "Section"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:777(literal) ./doc/config-reference/compute/section_compute-scheduler.xml:903(literal)
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:798(literal) ./doc/config-reference/compute/section_compute-scheduler.xml:924(literal)
|
||||
msgid "ram_weight_multiplier"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:778(td)
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:799(td)
|
||||
msgid "By default, the scheduler spreads instances across all hosts evenly. Set the <placeholder-1/> option to a negative number if you prefer stacking instead of spreading. Use a floating-point value."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:787(literal)
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:808(literal)
|
||||
msgid "scheduler_host_subset_size"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:788(td)
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:809(td)
|
||||
msgid "New instances are scheduled on a host that is chosen randomly from a subset of the N best hosts. This property defines the subset size from which a host is chosen. A value of 1 chooses the first host returned by the weighting functions. This value must be at least 1. A value less than 1 is ignored, and 1 is used instead. Use an integer value."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:799(literal) ./doc/config-reference/compute/section_compute-scheduler.xml:913(literal)
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:820(literal) ./doc/config-reference/compute/section_compute-scheduler.xml:934(literal)
|
||||
msgid "scheduler_weight_classes"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:801(literal)
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:822(literal)
|
||||
msgid "nova.scheduler.weights.all_weighers"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:800(td)
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:821(td)
|
||||
msgid "Defaults to <placeholder-1/>, which selects the RamWeigher. Hosts are then weighted and sorted with the largest weight winning."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:808(literal)
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:829(literal)
|
||||
msgid "weight_multiplier"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:809(td)
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:830(td)
|
||||
msgid "Multiplier for weighting metrics. Use a floating-point value."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:814(literal)
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:835(literal)
|
||||
msgid "weight_setting"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:818(literal)
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:839(literal)
|
||||
msgid "name1.value * 1.0 + name2.value * -1.0"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:815(td)
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:836(td)
|
||||
msgid "Determines how metrics are weighted. Use a comma-separated list of metricName=ratio. For example: \"name1=1.0, name2=-1.0\" results in: <placeholder-1/>"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:824(literal)
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:845(literal)
|
||||
msgid "required"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:827(para)
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:848(para)
|
||||
msgid "TrueRaises an exception. To avoid the raised exception, you should use the scheduler filter MetricFilter to filter out hosts with unavailable metrics."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:836(para)
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:857(para)
|
||||
msgid "FalseTreated as a negative factor in the weighting process (uses the option)."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:825(para)
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:846(para)
|
||||
msgid "Specifies how to treat unavailable metrics:<placeholder-1/>"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:846(literal)
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:867(literal)
|
||||
msgid "weight_of_unavailable"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:847(td)
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:868(td)
|
||||
msgid "If <placeholder-1/> is set to False, and any one of the metrics set by <placeholder-2/> is unavailable, the <placeholder-3/> value is returned to the scheduler."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:856(para) ./doc/config-reference/compute/section_compute-scheduler.xml:922(para)
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:877(para) ./doc/config-reference/compute/section_compute-scheduler.xml:943(para)
|
||||
msgid "For example:"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:867(caption)
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:888(caption)
|
||||
msgid "Cell weighting options"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:881(literal)
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:902(literal)
|
||||
msgid "mute_weight_multiplier"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:882(td)
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:903(td)
|
||||
msgid "Multiplier to weight mute children (hosts which have not sent capacity or capacity updates for some time). Use a negative, floating-point value."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:889(literal)
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:910(literal)
|
||||
msgid "mute_weight_value"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:890(td)
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:911(td)
|
||||
msgid "Weight value assigned to mute children. Use a positive, floating-point value with a maximum of '1.0'."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:896(literal)
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:917(literal)
|
||||
msgid "offset_weight_multiplier"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:897(td)
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:918(td)
|
||||
msgid "Multiplier to weight cells, so you can specify a preferred cell. Use a floating point value."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:904(td)
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:925(td)
|
||||
msgid "By default, the scheduler spreads instances across all cells evenly. Set the <placeholder-1/> option to a negative number if you prefer stacking instead of spreading. Use a floating-point value."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:915(literal)
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:936(literal)
|
||||
msgid "nova.cells.weights.all_weighers"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:914(td)
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:935(td)
|
||||
msgid "Defaults to <placeholder-1/>, which maps to all cell weighers included with Compute. Cells are then weighted and sorted with the largest weight winning."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:931(title)
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:952(title)
|
||||
msgid "Chance scheduler"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:933(para)
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:954(para)
|
||||
msgid "As an administrator, you work with the filter scheduler. However, the Compute service also uses the Chance Scheduler, <literal>nova.scheduler.chance.ChanceScheduler</literal>, which randomly selects from lists of filtered hosts."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:944(para)
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:965(para)
|
||||
msgid "To customize the Compute scheduler, use the configuration option settings documented in <xref linkend=\"config_table_nova_scheduler\"/>."
|
||||
msgstr ""
|
||||
|
||||
|
||||
@ -7,8 +7,8 @@
|
||||
msgid ""
|
||||
msgstr ""
|
||||
"Project-Id-Version: OpenStack Manuals\n"
|
||||
"POT-Creation-Date: 2015-01-16 17:58+0000\n"
|
||||
"PO-Revision-Date: 2015-01-16 09:11+0000\n"
|
||||
"POT-Creation-Date: 2015-01-20 04:54+0000\n"
|
||||
"PO-Revision-Date: 2015-01-19 19:54+0000\n"
|
||||
"Last-Translator: openstackjenkins <jenkins@openstack.org>\n"
|
||||
"Language-Team: French (http://www.transifex.com/projects/p/openstack-manuals-i18n/language/fr/)\n"
|
||||
"MIME-Version: 1.0\n"
|
||||
@ -2261,19 +2261,11 @@ msgid ""
|
||||
"openSUSE and SLES images."
|
||||
msgstr "SUSE ne fournit pas d'images openSUSE ou SUSE Linux Enterprise Server (SLES) en téléchargement direct. A la place, ils fournissent un outil basé sur le web dénommé <link href=\"http://susestudio.com\">SUSE Studio</link> que vous pouvez utiliser pour construire des images openSUSE et SLES."
|
||||
|
||||
#: ./doc/image-guide/ch_obtaining_images.xml91(para)
|
||||
msgid ""
|
||||
"For example, Christian Berendt used <link "
|
||||
"href=\"http://www.opensuse.org\">openSUSE</link> to create <link "
|
||||
"href=\"http://susestudio.com/a/YRUrwO/testing-instance-for-openstack-"
|
||||
"opensuse-12-3\"> a test openSUSE 12.3 image</link>."
|
||||
msgstr "Par exemple, Christian Berendt à utilisé <link href=\"http://www.opensuse.org\">openSUSE</link> pour créer <link href=\"http://susestudio.com/a/YRUrwO/testing-instance-for-openstack-opensuse-12-3\"> une image de test openSUSE 12.3</link>."
|
||||
|
||||
#: ./doc/image-guide/ch_obtaining_images.xml96(title)
|
||||
#: ./doc/image-guide/ch_obtaining_images.xml92(title)
|
||||
msgid "Official Debian images"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/image-guide/ch_obtaining_images.xml97(para)
|
||||
#: ./doc/image-guide/ch_obtaining_images.xml93(para)
|
||||
msgid ""
|
||||
"Debian does not (yet) provide images for direct download. Instead, a package"
|
||||
" named <package>openstack-debian-images</package> provides a simple script "
|
||||
@ -2282,7 +2274,7 @@ msgid ""
|
||||
"image, simply run: <placeholder-1/>"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/image-guide/ch_obtaining_images.xml103(para)
|
||||
#: ./doc/image-guide/ch_obtaining_images.xml99(para)
|
||||
msgid ""
|
||||
"If building the image for Wheezy, packages like <package>cloud-"
|
||||
"init</package>, <package>cloud-utils</package> or <package>cloud-initramfs-"
|
||||
@ -2298,21 +2290,21 @@ msgid ""
|
||||
"parameter: <placeholder-4/>"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/image-guide/ch_obtaining_images.xml124(title)
|
||||
#: ./doc/image-guide/ch_obtaining_images.xml120(title)
|
||||
msgid "Official images from other Linux distributions"
|
||||
msgstr "Images officielles pour d'autres distributions de Linux"
|
||||
|
||||
#: ./doc/image-guide/ch_obtaining_images.xml125(para)
|
||||
#: ./doc/image-guide/ch_obtaining_images.xml121(para)
|
||||
msgid ""
|
||||
"As of this writing, we are not aware of other distributions that provide "
|
||||
"images for download."
|
||||
msgstr "Au moment où nous écrivons ces lignes, nous n'avons pas connaissance d'autres distributions qui fourniraient des images en téléchargement."
|
||||
|
||||
#: ./doc/image-guide/ch_obtaining_images.xml128(title)
|
||||
#: ./doc/image-guide/ch_obtaining_images.xml124(title)
|
||||
msgid "Rackspace Cloud Builders (multiple distros) images"
|
||||
msgstr "Images Rackspace Cloud Builders (distributions multiples)"
|
||||
|
||||
#: ./doc/image-guide/ch_obtaining_images.xml130(para)
|
||||
#: ./doc/image-guide/ch_obtaining_images.xml126(para)
|
||||
msgid ""
|
||||
"Rackspace Cloud Builders maintains a list of pre-built images from various "
|
||||
"distributions (Red Hat, CentOS, Fedora, Ubuntu). Links to these images can "
|
||||
@ -2320,11 +2312,11 @@ msgid ""
|
||||
"build\">rackerjoe/oz-image-build on GitHub</link>."
|
||||
msgstr "Rackspace Cloud Builders maintient une liste d'images pré-générées issues de diverses distributions (Red Hat, CentOS, Fedora, Ubuntu). Les liens vers ces images peuvent être trouvés à <link href=\"https://github.com/rackerjoe/oz-image-build\">rackerjoe/oz-image-build on GitHub</link>."
|
||||
|
||||
#: ./doc/image-guide/ch_obtaining_images.xml136(title)
|
||||
#: ./doc/image-guide/ch_obtaining_images.xml132(title)
|
||||
msgid "Microsoft Windows images"
|
||||
msgstr "Images Microsoft Windows"
|
||||
|
||||
#: ./doc/image-guide/ch_obtaining_images.xml137(para)
|
||||
#: ./doc/image-guide/ch_obtaining_images.xml133(para)
|
||||
msgid ""
|
||||
"Cloudbase Solutions hosts an <link "
|
||||
"href=\"http://www.cloudbase.it/ws2012r2/\">OpenStack Windows Server 2012 "
|
||||
|
||||
@ -1,7 +1,7 @@
|
||||
msgid ""
|
||||
msgstr ""
|
||||
"Project-Id-Version: PACKAGE VERSION\n"
|
||||
"POT-Creation-Date: 2015-01-17 06:12+0000\n"
|
||||
"POT-Creation-Date: 2015-01-20 06:13+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"
|
||||
@ -1549,43 +1549,39 @@ msgstr ""
|
||||
msgid "SUSE does not provide openSUSE or SUSE Linux Enterprise Server (SLES) images for direct download. Instead, they provide a web-based tool called <link href=\"http://susestudio.com\">SUSE Studio</link> that you can use to build openSUSE and SLES images."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/image-guide/ch_obtaining_images.xml:91(para)
|
||||
msgid "For example, Christian Berendt used <link href=\"http://www.opensuse.org\">openSUSE</link> to create <link href=\"http://susestudio.com/a/YRUrwO/testing-instance-for-openstack-opensuse-12-3\"> a test openSUSE 12.3 image</link>."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/image-guide/ch_obtaining_images.xml:96(title)
|
||||
#: ./doc/image-guide/ch_obtaining_images.xml:92(title)
|
||||
msgid "Official Debian images"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/image-guide/ch_obtaining_images.xml:97(para)
|
||||
#: ./doc/image-guide/ch_obtaining_images.xml:93(para)
|
||||
msgid "Debian does not (yet) provide images for direct download. Instead, a package named <package>openstack-debian-images</package> provides a simple script for building them. This package is available in Debian Unstable, Debian Jessie, and through the wheezy-backports repositories. To produce a Wheezy image, simply run: <placeholder-1/>"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/image-guide/ch_obtaining_images.xml:103(para)
|
||||
#: ./doc/image-guide/ch_obtaining_images.xml:99(para)
|
||||
msgid "If building the image for Wheezy, packages like <package>cloud-init</package>, <package>cloud-utils</package> or <package>cloud-initramfs-growroot</package> will be pulled from wheezy-backports. Also, the current version of <package>bootlogd</package> in Wheezy doesn't support logging to multiple consoles, which is needed so that both the OpenStack Dashboard console and the <placeholder-1/> console works. However, a <link href=\"http://archive.gplhost.com/debian/pool/juno-backports/main/s/sysvinit/bootlogd_2.88dsf-41+deb7u2_amd64.deb\"> fixed version is available from the non-official GPLHost repository</link>. To install it on top of the image, it is possible to use the <placeholder-2/> option of the <placeholder-3/> script, with this kind of script as parameter: <placeholder-4/>"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/image-guide/ch_obtaining_images.xml:124(title)
|
||||
#: ./doc/image-guide/ch_obtaining_images.xml:120(title)
|
||||
msgid "Official images from other Linux distributions"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/image-guide/ch_obtaining_images.xml:125(para)
|
||||
#: ./doc/image-guide/ch_obtaining_images.xml:121(para)
|
||||
msgid "As of this writing, we are not aware of other distributions that provide images for download."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/image-guide/ch_obtaining_images.xml:128(title)
|
||||
#: ./doc/image-guide/ch_obtaining_images.xml:124(title)
|
||||
msgid "Rackspace Cloud Builders (multiple distros) images"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/image-guide/ch_obtaining_images.xml:130(para)
|
||||
#: ./doc/image-guide/ch_obtaining_images.xml:126(para)
|
||||
msgid "Rackspace Cloud Builders maintains a list of pre-built images from various distributions (Red Hat, CentOS, Fedora, Ubuntu). Links to these images can be found at <link href=\"https://github.com/rackerjoe/oz-image-build\">rackerjoe/oz-image-build on GitHub</link>."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/image-guide/ch_obtaining_images.xml:136(title)
|
||||
#: ./doc/image-guide/ch_obtaining_images.xml:132(title)
|
||||
msgid "Microsoft Windows images"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/image-guide/ch_obtaining_images.xml:137(para)
|
||||
#: ./doc/image-guide/ch_obtaining_images.xml:133(para)
|
||||
msgid "Cloudbase Solutions hosts an <link href=\"http://www.cloudbase.it/ws2012r2/\">OpenStack Windows Server 2012 Standard Evaluation image</link> that runs on Hyper-V, KVM, and XenServer/XCP."
|
||||
msgstr ""
|
||||
|
||||
|
||||
@ -6,8 +6,8 @@
|
||||
msgid ""
|
||||
msgstr ""
|
||||
"Project-Id-Version: OpenStack Manuals\n"
|
||||
"POT-Creation-Date: 2015-01-16 17:58+0000\n"
|
||||
"PO-Revision-Date: 2015-01-16 09:11+0000\n"
|
||||
"POT-Creation-Date: 2015-01-20 04:54+0000\n"
|
||||
"PO-Revision-Date: 2015-01-19 19:54+0000\n"
|
||||
"Last-Translator: openstackjenkins <jenkins@openstack.org>\n"
|
||||
"Language-Team: Japanese (http://www.transifex.com/projects/p/openstack-manuals-i18n/language/ja/)\n"
|
||||
"MIME-Version: 1.0\n"
|
||||
@ -2260,19 +2260,11 @@ msgid ""
|
||||
"openSUSE and SLES images."
|
||||
msgstr "SUSE は、直接ダウンロードするための、openSUSE や SUSE Linux Enterprise Server (SLES) のイメージを提供していません。代わりに、openSUSE や SLES のイメージを作成するために使用できる、<link href=\"http://susestudio.com\">SUSE Studio</link> という Web ベースのツールを提供しています。"
|
||||
|
||||
#: ./doc/image-guide/ch_obtaining_images.xml91(para)
|
||||
msgid ""
|
||||
"For example, Christian Berendt used <link "
|
||||
"href=\"http://www.opensuse.org\">openSUSE</link> to create <link "
|
||||
"href=\"http://susestudio.com/a/YRUrwO/testing-instance-for-openstack-"
|
||||
"opensuse-12-3\"> a test openSUSE 12.3 image</link>."
|
||||
msgstr "例えば、Christian Berendt は、<link href=\"http://susestudio.com/a/YRUrwO/testing-instance-for-openstack-opensuse-12-3\">openSUSE 12.3 テストイメージ</link>を作成するために、<link href=\"http://www.opensuse.org\">openSUSE</link> を使用しました。"
|
||||
|
||||
#: ./doc/image-guide/ch_obtaining_images.xml96(title)
|
||||
#: ./doc/image-guide/ch_obtaining_images.xml92(title)
|
||||
msgid "Official Debian images"
|
||||
msgstr "公式 Debian イメージ"
|
||||
|
||||
#: ./doc/image-guide/ch_obtaining_images.xml97(para)
|
||||
#: ./doc/image-guide/ch_obtaining_images.xml93(para)
|
||||
msgid ""
|
||||
"Debian does not (yet) provide images for direct download. Instead, a package"
|
||||
" named <package>openstack-debian-images</package> provides a simple script "
|
||||
@ -2281,7 +2273,7 @@ msgid ""
|
||||
"image, simply run: <placeholder-1/>"
|
||||
msgstr "Debian は、直接ダウンロードするイメージをまだ提供していません。代わりに、<package>openstack-debian-images</package> という名前のパッケージが、イメージを構築するためのシンプルなスクリプトを提供します。このパッケージは、Debian Unstable、Debian Jessie、wheezy バックポートリポジトリー経由で利用可能です。以下を実行して、Wheezy イメージを作成します。<placeholder-1/>"
|
||||
|
||||
#: ./doc/image-guide/ch_obtaining_images.xml103(para)
|
||||
#: ./doc/image-guide/ch_obtaining_images.xml99(para)
|
||||
msgid ""
|
||||
"If building the image for Wheezy, packages like <package>cloud-"
|
||||
"init</package>, <package>cloud-utils</package> or <package>cloud-initramfs-"
|
||||
@ -2297,21 +2289,21 @@ msgid ""
|
||||
"parameter: <placeholder-4/>"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/image-guide/ch_obtaining_images.xml124(title)
|
||||
#: ./doc/image-guide/ch_obtaining_images.xml120(title)
|
||||
msgid "Official images from other Linux distributions"
|
||||
msgstr "他の Linux ディストリビューションの公式イメージ"
|
||||
|
||||
#: ./doc/image-guide/ch_obtaining_images.xml125(para)
|
||||
#: ./doc/image-guide/ch_obtaining_images.xml121(para)
|
||||
msgid ""
|
||||
"As of this writing, we are not aware of other distributions that provide "
|
||||
"images for download."
|
||||
msgstr "執筆時点では、ダウンロード用のイメージを提供している他のディストリビューションを把握していません。"
|
||||
|
||||
#: ./doc/image-guide/ch_obtaining_images.xml128(title)
|
||||
#: ./doc/image-guide/ch_obtaining_images.xml124(title)
|
||||
msgid "Rackspace Cloud Builders (multiple distros) images"
|
||||
msgstr "Rackspace Cloud Builders (複数ディストリビューション) イメージ"
|
||||
|
||||
#: ./doc/image-guide/ch_obtaining_images.xml130(para)
|
||||
#: ./doc/image-guide/ch_obtaining_images.xml126(para)
|
||||
msgid ""
|
||||
"Rackspace Cloud Builders maintains a list of pre-built images from various "
|
||||
"distributions (Red Hat, CentOS, Fedora, Ubuntu). Links to these images can "
|
||||
@ -2319,11 +2311,11 @@ msgid ""
|
||||
"build\">rackerjoe/oz-image-build on GitHub</link>."
|
||||
msgstr "Rackspace Cloud Builders は、さまざまなディストリビューション (Red Hat, CentOS, Fedora, Ubuntu) の事前構築済みイメージを維持しています。これらのイメージへのリンクは、<link href=\"https://github.com/rackerjoe/oz-image-build\">GitHub の rackerjoe/oz-image-build</link> にあります。"
|
||||
|
||||
#: ./doc/image-guide/ch_obtaining_images.xml136(title)
|
||||
#: ./doc/image-guide/ch_obtaining_images.xml132(title)
|
||||
msgid "Microsoft Windows images"
|
||||
msgstr "Microsoft Windows イメージ"
|
||||
|
||||
#: ./doc/image-guide/ch_obtaining_images.xml137(para)
|
||||
#: ./doc/image-guide/ch_obtaining_images.xml133(para)
|
||||
msgid ""
|
||||
"Cloudbase Solutions hosts an <link "
|
||||
"href=\"http://www.cloudbase.it/ws2012r2/\">OpenStack Windows Server 2012 "
|
||||
|
||||
File diff suppressed because it is too large
Load Diff
@ -12,9 +12,9 @@
|
||||
msgid ""
|
||||
msgstr ""
|
||||
"Project-Id-Version: OpenStack Manuals\n"
|
||||
"POT-Creation-Date: 2015-01-18 23:01+0000\n"
|
||||
"PO-Revision-Date: 2015-01-18 23:02+0000\n"
|
||||
"Last-Translator: openstackjenkins <jenkins@openstack.org>\n"
|
||||
"POT-Creation-Date: 2015-01-20 04:54+0000\n"
|
||||
"PO-Revision-Date: 2015-01-20 01:21+0000\n"
|
||||
"Last-Translator: Fernando Pimenta <fernando.c.pimenta@gmail.com>\n"
|
||||
"Language-Team: Portuguese (Brazil) (http://www.transifex.com/projects/p/openstack-manuals-i18n/language/pt_BR/)\n"
|
||||
"MIME-Version: 1.0\n"
|
||||
"Content-Type: text/plain; charset=UTF-8\n"
|
||||
@ -1136,7 +1136,7 @@ msgstr "Edite o arquivo <filename>/etc/ceilometer/ceilometer.conf</filename> e c
|
||||
msgid ""
|
||||
"In the <literal>[publisher]</literal> section, set the metering secret for "
|
||||
"Telemetry service nodes:"
|
||||
msgstr ""
|
||||
msgstr "Na seção <literal>[publisher]</literal>, defina o segredo de medição para os nodos do serviço de Telemetria:"
|
||||
|
||||
#: ./doc/install-guide/section_ceilometer-nova.xml51(replaceable)
|
||||
#: ./doc/install-guide/section_ceilometer-controller.xml266(replaceable)
|
||||
@ -1148,7 +1148,7 @@ msgstr "METERING_SECRET"
|
||||
msgid ""
|
||||
"Replace <replaceable>METERING_SECRET</replaceable> with the metering secret "
|
||||
"that you created previously."
|
||||
msgstr ""
|
||||
msgstr "Substitua <replaceable>METERING_SECRET</replaceable> com o segredo de medição que você criou anteriormente."
|
||||
|
||||
#: ./doc/install-guide/section_ceilometer-nova.xml56(para)
|
||||
msgid ""
|
||||
@ -6635,7 +6635,7 @@ msgstr "OpenStack Foundation"
|
||||
|
||||
#: ./doc/install-guide/bk-openstack-install-guide.xml41(releaseinfo)
|
||||
msgid "kilo"
|
||||
msgstr ""
|
||||
msgstr "kilo"
|
||||
|
||||
#: ./doc/install-guide/bk-openstack-install-guide.xml42(productname)
|
||||
msgid "OpenStack Installation Guide"
|
||||
@ -6664,7 +6664,7 @@ msgid ""
|
||||
"Enterprise Server 11 SP3 through the Open Build Service Cloud "
|
||||
"repository.</phrase> Explanations of configuration options and sample "
|
||||
"configuration files are included."
|
||||
msgstr ""
|
||||
msgstr "O sistema OpenStack consiste de vários projetos principais que você instala separadamente. Estes projetos trabalham juntos dependendo de suas necessidades de nuvem. Este projetos incluem Computação, Serviço de Identidade, Rede, Serviço de Imagem, Block Storage, Object Storage, Telemetria, Orquestração, e Banco de Dados. Você pode instalar quaisquer destes projetos separadamente e configurá-los autonomamente ou como entidades conectadas.\n<phrase os=\"debian\">Este guia caminha através de uma instalação usando os pacotes disponíveis no Debian 7 (codinome: Wheezy).</phrase><phrase os=\"ubuntu\">Este guia caminha através de uma instalação usando os pacotes disponíveis no Ubuntu 14.04.</phrase><phrase os=\"rhel;centos;fedora\">Este guia mostra a você como instalar o OpenStack utilizando pacotes disponíveis através do Fedora 20 bem como no Red Hat Enterprise Linux 7 e seus derivados através do repositório EPEL.</phrase><phrase os=\"opensuse;sles\">Este guia mostra a você como instalar o OpenStack utilizando pacotes disponíveis no openSUSE 13.1 e SUSE Linux Enterprise Server 11 SP3 através do repositório Open Build Service Cloud.</phrase>"
|
||||
|
||||
#: ./doc/install-guide/bk-openstack-install-guide.xml80(date)
|
||||
msgid "2014-10-15"
|
||||
@ -7037,7 +7037,7 @@ msgstr "Na seção <literal>[publisher]</literal>, configure o secret de mediç
|
||||
msgid ""
|
||||
"Replace <replaceable>METERING_SECRET</replaceable> with the metering secret "
|
||||
"that you generated in a previous step."
|
||||
msgstr ""
|
||||
msgstr "Substitua <replaceable>METERING_SECRET</replaceable> com o segredo de medição que você gerou no passo anterior."
|
||||
|
||||
#: ./doc/install-guide/section_ceilometer-controller.xml278(para)
|
||||
msgid ""
|
||||
|
||||
@ -1,7 +1,7 @@
|
||||
msgid ""
|
||||
msgstr ""
|
||||
"Project-Id-Version: PACKAGE VERSION\n"
|
||||
"POT-Creation-Date: 2015-01-15 06:13+0000\n"
|
||||
"POT-Creation-Date: 2015-01-20 06:13+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"
|
||||
@ -2352,7 +2352,7 @@ msgid "Networking layers"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/networking-guide/section_intro-layers.xml:13(para)
|
||||
msgid "Network communications is commonly described in terms of the OSI model, a seven-layer model that describes how various protocols and mechanisms fit together. Each layer depends on the protocols in the layer beneath it."
|
||||
msgid "Network communication is commonly described in terms of the OSI model. The OSI model is a seven-layer model that describes how various protocols and mechanisms fit together. Each layer depends on the protocols in the layer beneath it."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/networking-guide/section_intro-layers.xml:19(term)
|
||||
@ -2392,7 +2392,7 @@ msgid "3 Network"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/networking-guide/section_intro-layers.xml:56(para)
|
||||
msgid "This layer handles transmission for data from node to node. The network layer handles routing, forwarding, addressing, internetworking, and error handling. Usually this is the IP portion of TCP/IP."
|
||||
msgid "This layer handles transmission for data from node to node. The network layer handles routing, forwarding, addressing, inter-networking, and error handling. Usually this is the IP portion of TCP/IP."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/networking-guide/section_intro-layers.xml:63(term)
|
||||
@ -2400,7 +2400,7 @@ msgid "2 Data link"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/networking-guide/section_intro-layers.xml:65(para)
|
||||
msgid "The data link layer where most LAN technologies like Ethernet live. The layer is divided into two sublayers: <emphasis role=\"bold\">MAC (Media Access Control):</emphasis> Handles access to data and permissions to translate it. <emphasis role=\"bold\">LLC (Logical Link Control):</emphasis> Manages traffic across the physical layer."
|
||||
msgid "The data link layer is where most LAN technologies such as Ethernet live. This layer is divided into two sub layers: <emphasis role=\"bold\">MAC (Media Access Control):</emphasis> Handles access to data and permissions to translate it. <emphasis role=\"bold\">LLC (Logical Link Control):</emphasis> Manages traffic across the physical layer."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/networking-guide/section_intro-layers.xml:74(term)
|
||||
|
||||
Loading…
Reference in New Issue
Block a user