Imported Translations from Transifex
For more information about this automatic import see: https://wiki.openstack.org/wiki/Translations/Infrastructure Change-Id: Icb299cbed12583f8bffc42f7ced906770a66c4df
This commit is contained in:
OpenStack Proposal Bot
parent
d7b823e88f
commit
07e7c99e5c
@ -1,7 +1,7 @@
|
||||
msgid ""
|
||||
msgstr ""
|
||||
"Project-Id-Version: PACKAGE VERSION\n"
|
||||
"POT-Creation-Date: 2014-11-16 06:12+0000\n"
|
||||
"POT-Creation-Date: 2014-11-19 06:10+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"
|
||||
@ -1326,7 +1326,7 @@ msgstr ""
|
||||
msgid "The displayed image attributes are:"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/admin-guide-cloud/ch_compute.xml:340(literal) ./doc/admin-guide-cloud/compute/section_compute-instance-building-blocks.xml:27(literal) ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:518(replaceable)
|
||||
#: ./doc/admin-guide-cloud/ch_compute.xml:340(literal) ./doc/admin-guide-cloud/compute/section_compute-instance-building-blocks.xml:27(literal) ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:520(replaceable)
|
||||
msgid "ID"
|
||||
msgstr ""
|
||||
|
||||
@ -2702,7 +2702,7 @@ msgstr ""
|
||||
msgid "NETWORK_NAME"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/admin-guide-cloud/networking/section_networking-use.xml:375(para) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1725(para) ./doc/admin-guide-cloud/networking/section_networking-adv-config.xml:199(para) ./doc/admin-guide-cloud/networking/section_networking-adv-config.xml:263(para) ./doc/admin-guide-cloud/networking/section_networking-config-identity.xml:48(para) ./doc/admin-guide-cloud/networking/section_networking-config-identity.xml:62(para) ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:236(para) ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:257(para) ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:265(para) ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:280(para) ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:309(para) ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:314(para) ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:471(para)
|
||||
#: ./doc/admin-guide-cloud/networking/section_networking-use.xml:375(para) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1725(para) ./doc/admin-guide-cloud/networking/section_networking-adv-config.xml:199(para) ./doc/admin-guide-cloud/networking/section_networking-adv-config.xml:263(para) ./doc/admin-guide-cloud/networking/section_networking-config-identity.xml:48(para) ./doc/admin-guide-cloud/networking/section_networking-config-identity.xml:62(para) ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:238(para) ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:259(para) ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:267(para) ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:282(para) ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:311(para) ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:316(para) ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:473(para)
|
||||
msgid "For example:"
|
||||
msgstr ""
|
||||
|
||||
@ -3588,7 +3588,7 @@ msgstr ""
|
||||
msgid "Identifies the <replaceable>PORT_ID</replaceable> that represents the VM NIC to which the floating IP should map."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:470(replaceable) ./doc/admin-guide-cloud/telemetry/section_telemetry-alarms.xml:90(replaceable)
|
||||
#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:470(replaceable) ./doc/admin-guide-cloud/telemetry/section_telemetry-alarms.xml:108(replaceable)
|
||||
msgid "INSTANCE_ID"
|
||||
msgstr ""
|
||||
|
||||
@ -3684,7 +3684,7 @@ msgstr ""
|
||||
msgid "Human-readable name for the security group. Might not be unique. Cannot be named default as that is automatically created for a tenant."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:632(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:893(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1015(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1083(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1601(td) ./doc/admin-guide-cloud/telemetry/section_telemetry-alarms.xml:111(term)
|
||||
#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:632(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:893(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1015(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1083(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1601(td) ./doc/admin-guide-cloud/telemetry/section_telemetry-alarms.xml:129(term)
|
||||
msgid "description"
|
||||
msgstr ""
|
||||
|
||||
@ -4028,7 +4028,7 @@ msgstr ""
|
||||
msgid "Action to be performed on the traffic matching the rule (allow, deny)."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:971(td) ./doc/admin-guide-cloud/telemetry/section_telemetry-alarms.xml:117(term)
|
||||
#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:971(td) ./doc/admin-guide-cloud/telemetry/section_telemetry-alarms.xml:135(term)
|
||||
msgid "enabled"
|
||||
msgstr ""
|
||||
|
||||
@ -4724,7 +4724,7 @@ msgstr ""
|
||||
msgid "Creates a metering rule."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1724(replaceable) ./doc/admin-guide-cloud/networking/section_networking-adv-config.xml:262(replaceable) ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:481(replaceable) ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:486(replaceable)
|
||||
#: ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1724(replaceable) ./doc/admin-guide-cloud/networking/section_networking-adv-config.xml:262(replaceable) ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:483(replaceable) ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:488(replaceable)
|
||||
msgid "CIDR"
|
||||
msgstr ""
|
||||
|
||||
@ -6978,199 +6978,211 @@ msgstr ""
|
||||
msgid "These are a lightweight alternative to webhooks, whereby the state transition is simply logged by the <systemitem class=\"service\">alarm-notifier</systemitem>, and are intended primarily for testing purposes."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-alarms.xml:79(title)
|
||||
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-alarms.xml:78(title)
|
||||
msgid "Workload partitioning"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-alarms.xml:79(para)
|
||||
msgid "The alarm evaluation process uses the same mechanism for workload partitioning as the central and compute agents. The <link href=\"https://pypi.python.org/pypi/tooz\"> Tooz</link> library provides the coordination within the groups of service instances. For further information about this approach see <xref linkend=\"section_telemetry-cetral-compute-agent-ha\"/>."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-alarms.xml:87(para)
|
||||
msgid "To use this workload partitioning solution set the <option>evaluation_service</option> option to <literal> default</literal>. For more information, see the alarm section in the <link href=\"http://docs.openstack.org/trunk/config-reference/content/ch_configuring-openstack-telemetry.html\"><citetitle>OpenStack Configuration Reference</citetitle></link>."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-alarms.xml:97(title)
|
||||
msgid "Using alarms"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-alarms.xml:80(para)
|
||||
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-alarms.xml:98(para)
|
||||
msgid "The <placeholder-1/> CLI provides simple verbs for creating and manipulating alarms."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-alarms.xml:82(title)
|
||||
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-alarms.xml:100(title)
|
||||
msgid "Alarm creation"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-alarms.xml:83(para)
|
||||
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-alarms.xml:101(para)
|
||||
msgid "An example of creating a threshold-oriented alarm, based on an upper bound on the CPU utilization for a particular instance:"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-alarms.xml:91(para)
|
||||
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-alarms.xml:109(para)
|
||||
msgid "This creates an alarm that will fire when the average CPU utilization for an individual instance exceeds 70% for three consecutive 10 minute periods. The notification in this case is simply a log message, though it could alternatively be a webhook URL."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-alarms.xml:93(para)
|
||||
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-alarms.xml:111(para)
|
||||
msgid "Alarm names must be unique for the alarms associated with an individual project."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-alarms.xml:95(para)
|
||||
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-alarms.xml:113(para)
|
||||
msgid "The sliding time window over which the alarm is evaluated is 30 minutes in this example. This window is not clamped to wall-clock time boundaries, rather it's anchored on the current time for each evaluation cycle, and continually creeps forward as each evaluation cycle rolls around (by default, this occurs every minute)."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-alarms.xml:96(para)
|
||||
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-alarms.xml:114(para)
|
||||
msgid "The period length is set to 600s in this case to reflect the out-of-the-box default cadence for collection of the associated metric. This period matching illustrates an important general principal to keep in mind for alarms:"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-alarms.xml:98(para)
|
||||
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-alarms.xml:116(para)
|
||||
msgid "The alarm period should be a whole number multiple (1 or more) of the interval configured in the pipeline corresponding to the target meter."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-alarms.xml:100(para)
|
||||
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-alarms.xml:118(para)
|
||||
msgid "Otherwise the alarm will tend to flit in and out of the <literal>insufficient data</literal> state due to the mismatch between the actual frequency of datapoints in the metering store and the statistics queries used to compare against the alarm threshold. If a shorter alarm period is needed, then the corresponding interval should be adjusted in the <filename>pipeline.yaml</filename> file."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-alarms.xml:101(para)
|
||||
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-alarms.xml:119(para)
|
||||
msgid "Other notable alarm attributes that may be set on creation, or via a subsequent update, include:"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-alarms.xml:105(term)
|
||||
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-alarms.xml:123(term)
|
||||
msgid "state"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-alarms.xml:107(para)
|
||||
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-alarms.xml:125(para)
|
||||
msgid "The initial alarm state (defaults to <literal>insufficient data</literal>)."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-alarms.xml:113(para)
|
||||
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-alarms.xml:131(para)
|
||||
msgid "A free-text description of the alarm (defaults to a synopsis of the alarm rule)."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-alarms.xml:119(para)
|
||||
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-alarms.xml:137(para)
|
||||
msgid "True if evaluation and actioning is to be enabled for this alarm (defaults to True)."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-alarms.xml:123(term)
|
||||
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-alarms.xml:141(term)
|
||||
msgid "repeat-actions"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-alarms.xml:125(para)
|
||||
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-alarms.xml:143(para)
|
||||
msgid "True if actions should be repeatedly notified while the alarm remains in the target state (defaults to False)."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-alarms.xml:129(term)
|
||||
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-alarms.xml:147(term)
|
||||
msgid "ok-action"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-alarms.xml:131(para)
|
||||
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-alarms.xml:149(para)
|
||||
msgid "An action to invoke when the alarm state transitions to <literal>ok</literal>."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-alarms.xml:135(term)
|
||||
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-alarms.xml:153(term)
|
||||
msgid "insufficient-data-action"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-alarms.xml:137(para)
|
||||
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-alarms.xml:155(para)
|
||||
msgid "An action to invoke when the alarm state transitions to <literal>insufficient data</literal>."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-alarms.xml:141(term)
|
||||
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-alarms.xml:159(term)
|
||||
msgid "time-constraint"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-alarms.xml:143(para)
|
||||
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-alarms.xml:161(para)
|
||||
msgid "Used to restrict evaluation of the alarm to certain times of the day or days of the week (expressed as <literal>cron</literal> expression with an optional timezone)."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-alarms.xml:148(para)
|
||||
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-alarms.xml:166(para)
|
||||
msgid "An example of creating a combination alarm, based on the combined state of two underlying alarms:"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-alarms.xml:150(replaceable)
|
||||
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-alarms.xml:168(replaceable)
|
||||
msgid "ALARM_ID1"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-alarms.xml:151(replaceable)
|
||||
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-alarms.xml:169(replaceable)
|
||||
msgid "ALARM_ID2"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-alarms.xml:154(para)
|
||||
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-alarms.xml:172(para)
|
||||
msgid "This creates an alarm that will fire when ether one of two underlying alarms transition into the alarm state. The notification in this case is a webhook call. Any number of underlying alarms can be combined in this way, using either <literal>and</literal> or <literal>or</literal>."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-alarms.xml:157(title)
|
||||
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-alarms.xml:175(title)
|
||||
msgid "Alarm retrieval"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-alarms.xml:158(para)
|
||||
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-alarms.xml:176(para)
|
||||
msgid "You can display all your alarms via (some attributes are omitted for brevity):"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-alarms.xml:163(replaceable) ./doc/admin-guide-cloud/telemetry/section_telemetry-alarms.xml:192(replaceable) ./doc/admin-guide-cloud/telemetry/section_telemetry-alarms.xml:195(replaceable) ./doc/admin-guide-cloud/telemetry/section_telemetry-alarms.xml:196(replaceable) ./doc/admin-guide-cloud/telemetry/section_telemetry-alarms.xml:198(replaceable) ./doc/admin-guide-cloud/telemetry/section_telemetry-alarms.xml:213(replaceable) ./doc/admin-guide-cloud/telemetry/section_telemetry-alarms.xml:215(replaceable)
|
||||
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-alarms.xml:181(replaceable) ./doc/admin-guide-cloud/telemetry/section_telemetry-alarms.xml:210(replaceable) ./doc/admin-guide-cloud/telemetry/section_telemetry-alarms.xml:213(replaceable) ./doc/admin-guide-cloud/telemetry/section_telemetry-alarms.xml:214(replaceable) ./doc/admin-guide-cloud/telemetry/section_telemetry-alarms.xml:216(replaceable) ./doc/admin-guide-cloud/telemetry/section_telemetry-alarms.xml:231(replaceable) ./doc/admin-guide-cloud/telemetry/section_telemetry-alarms.xml:233(replaceable)
|
||||
msgid "ALARM_ID"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-alarms.xml:165(para)
|
||||
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-alarms.xml:183(para)
|
||||
msgid "In this case, the state is reported as <literal>insufficient data</literal> which could indicate that:"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-alarms.xml:168(para)
|
||||
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-alarms.xml:186(para)
|
||||
msgid "metrics have not yet been gathered about this instance over the evaluation window into the recent past (for example a brand-new instance)"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-alarms.xml:171(para)
|
||||
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-alarms.xml:189(para)
|
||||
msgid "<emphasis>or</emphasis>, that the identified instance is not visible to the user/tenant owning the alarm"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-alarms.xml:174(para)
|
||||
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-alarms.xml:192(para)
|
||||
msgid "<emphasis>or</emphasis>, simply that an alarm evaluation cycle hasn't kicked off since the alarm was created (by default, alarms are evaluated once per minute)."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-alarms.xml:178(para)
|
||||
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-alarms.xml:196(para)
|
||||
msgid "The visibility of alarms depends on the role and project associated with the user issuing the query:"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-alarms.xml:181(para)
|
||||
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-alarms.xml:199(para)
|
||||
msgid "admin users see <emphasis>all</emphasis> alarms, regardless of the owner"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-alarms.xml:184(para)
|
||||
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-alarms.xml:202(para)
|
||||
msgid "non-admin users see only the alarms associated with their project (as per the normal tenant segregation in OpenStack)"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-alarms.xml:190(title)
|
||||
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-alarms.xml:208(title)
|
||||
msgid "Alarm update"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-alarms.xml:191(para)
|
||||
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-alarms.xml:209(para)
|
||||
msgid "Once the state of the alarm has settled down, we might decide that we set that bar too low with 70%, in which case the threshold (or most any other alarm attribute) can be updated thusly:"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-alarms.xml:193(para)
|
||||
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-alarms.xml:211(para)
|
||||
msgid "The change will take effect from the next evaluation cycle, which by default occurs every minute."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-alarms.xml:194(para)
|
||||
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-alarms.xml:212(para)
|
||||
msgid "Most alarm attributes can be changed in this way, but there is also a convenient short-cut for getting and setting the alarm state:"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-alarms.xml:197(para)
|
||||
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-alarms.xml:215(para)
|
||||
msgid "Over time the state of the alarm may change often, especially if the threshold is chosen to be close to the trending value of the statistic. You can follow the history of an alarm over its lifecycle via the audit API:"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-alarms.xml:202(replaceable)
|
||||
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-alarms.xml:220(replaceable)
|
||||
msgid "time0"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-alarms.xml:206(replaceable)
|
||||
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-alarms.xml:224(replaceable)
|
||||
msgid "time1"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-alarms.xml:207(replaceable)
|
||||
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-alarms.xml:225(replaceable)
|
||||
msgid "time2"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-alarms.xml:211(title)
|
||||
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-alarms.xml:229(title)
|
||||
msgid "Alarm deletion"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-alarms.xml:212(para)
|
||||
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-alarms.xml:230(para)
|
||||
msgid "An alarm that's no longer required can be disabled so that it is no longer actively evaluated:"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-alarms.xml:214(para)
|
||||
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-alarms.xml:232(para)
|
||||
msgid "or even deleted permanently (an irreversible step):"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-alarms.xml:217(para)
|
||||
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-alarms.xml:235(para)
|
||||
msgid "By default, alarm history is retained for deleted alarms."
|
||||
msgstr ""
|
||||
|
||||
@ -7779,7 +7791,7 @@ msgid "As the name of this agent shows, it is a central component in the Telemet
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:205(para)
|
||||
msgid "The follwoing services can be polled with this agent:"
|
||||
msgid "The following services can be polled with this agent:"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:212(para)
|
||||
@ -7963,7 +7975,7 @@ msgid "The required fields for sending a sample using the command line client ar
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:399(para)
|
||||
msgid "The <literal>memory.usage</literal> meter is not supported when Libvirt is used in an Openstack deployment. There is still a possibility to provide samples for this meter based on any custom measurements. To send samples to Telemetry using the command line client, the follwoing command should be invoked: <placeholder-1/>"
|
||||
msgid "The <literal>memory.usage</literal> meter is not supported when Libvirt is used in an Openstack deployment. There is still a possibility to provide samples for this meter based on any custom measurements. To send samples to Telemetry using the command line client, the following command should be invoked: <placeholder-1/>"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:423(title)
|
||||
@ -10624,19 +10636,19 @@ 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/compute/section_compute-networking-nova.xml:547(None)
|
||||
#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:549(None)
|
||||
msgid "@@image: '../../common/figures/SCH_5007_V00_NUAC-multi_nic_OpenStack-Flat-manager.jpg'; md5=31f7e15a45d042bd9d6499631e2f3ccc"
|
||||
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/compute/section_compute-networking-nova.xml:557(None)
|
||||
#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:559(None)
|
||||
msgid "@@image: '../../common/figures/SCH_5007_V00_NUAC-multi_nic_OpenStack-Flat-DHCP-manager.jpg'; md5=0f33a228f1dec4a4e4424dd5ee81bde8"
|
||||
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/compute/section_compute-networking-nova.xml:567(None)
|
||||
#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:569(None)
|
||||
msgid "@@image: '../../common/figures/SCH_5007_V00_NUAC-multi_nic_OpenStack-VLAN-manager.jpg'; md5=0acaf3e2041f941d8fee2d111f37e7ac"
|
||||
msgstr ""
|
||||
|
||||
@ -10796,411 +10808,411 @@ msgstr ""
|
||||
msgid "To retrieve a list of supported versions for the OpenStack metadata API, make a GET request to <literal>http://169.254.169.254/openstack</literal> For example:"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:234(para)
|
||||
#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:236(para)
|
||||
msgid "To list supported versions for the EC2-compatible metadata API, make a GET request to <literal>http://169.254.169.254</literal>."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:248(para)
|
||||
#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:250(para)
|
||||
msgid "If you write a consumer for one of these APIs, always attempt to access the most recent API version supported by your consumer first, then fall back to an earlier version if the most recent one is not available."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:253(title)
|
||||
#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:255(title)
|
||||
msgid "OpenStack metadata API"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:254(para)
|
||||
#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:256(para)
|
||||
msgid "Metadata from the OpenStack API is distributed in JSON format. To retrieve the metadata, make a GET request to <literal>http://169.254.169.254/openstack/2012-08-10/meta_data.json</literal>."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:260(para)
|
||||
#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:262(para)
|
||||
msgid "Instances also retrieve user data (passed as the <literal>user_data</literal> parameter in the API call or by the <literal>--user_data</literal> flag in the <placeholder-1/> command) through the metadata service, by making a GET request to <literal>http://169.254.169.254/openstack/2012-08-10/user_data</literal>."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:271(title)
|
||||
#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:273(title)
|
||||
msgid "EC2 metadata API"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:272(para)
|
||||
#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:274(para)
|
||||
msgid "The metadata service has an API that is compatible with version 2009-04-04 of the <link href=\"http://docs.amazonwebservices.com/AWSEC2/2009-04-04/UserGuide/AESDG-chapter-instancedata.html\">Amazon EC2 metadata service</link>; virtual machine images that are designed for EC2 work properly with OpenStack."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:277(para)
|
||||
#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:279(para)
|
||||
msgid "The EC2 API exposes a separate URL for each metadata. You can retrieve a listing of these elements by making a GET query to <literal>http://169.254.169.254/2009-04-04/meta-data/</literal>"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:306(para)
|
||||
#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:308(para)
|
||||
msgid "Instances can retrieve the public SSH key (identified by keypair name when a user requests a new instance) by making a GET request to <literal>http://169.254.169.254/2009-04-04/meta-data/public-keys/0/openssh-key</literal>."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:312(para)
|
||||
#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:314(para)
|
||||
msgid "Instances can retrieve user data by making a GET request to <literal>http://169.254.169.254/2009-04-04/user-data</literal>."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:320(title)
|
||||
#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:322(title)
|
||||
msgid "Run the metadata service"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:321(para)
|
||||
#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:323(para)
|
||||
msgid "The metadata service is implemented by either the <systemitem class=\"service\">nova-api</systemitem> service or the <systemitem class=\"service\">nova-api-metadata</systemitem> service. (The <systemitem class=\"service\">nova-api-metadata</systemitem> service is generally only used when running in multi-host mode, it retrieves instance-specific metadata). If you are running the <systemitem class=\"service\">nova-api</systemitem> service, you must have <literal>metadata</literal> as one of the elements of the list of the <literal>enabled_apis</literal> configuration option in <filename>/etc/nova/nova.conf</filename>. The default <literal>enabled_apis</literal> configuration setting includes the metadata service, so you should not need to modify it."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:332(para)
|
||||
#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:334(para)
|
||||
msgid "Hosts access the service at <literal>169.254.169.254:80</literal>, and this is translated to <literal>metadata_host:metadata_port</literal> by an iptables rule established by the <systemitem class=\"service\">nova-network</systemitem> service. In multi-host mode, you can set <option>metadata_host</option> to <literal>127.0.0.1</literal>."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:337(para)
|
||||
#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:339(para)
|
||||
msgid "To enable instances to reach the metadata service, the <systemitem class=\"service\">nova-network</systemitem> service configures iptables to NAT port <literal>80</literal> of the <literal>169.254.169.254</literal> address to the IP address specified in <option>metadata_host</option> (default <literal>$my_ip</literal>, which is the IP address of the <systemitem class=\"service\">nova-network</systemitem> service) and port specified in <option>metadata_port</option> (default <literal>8775</literal>) in <filename>/etc/nova/nova.conf</filename>."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:346(para)
|
||||
#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:348(para)
|
||||
msgid "The <literal>metadata_host</literal> configuration option must be an IP address, not a host name."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:350(para)
|
||||
#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:352(para)
|
||||
msgid "The default Compute service settings assume that the <systemitem class=\"service\">nova-network</systemitem> service and the <systemitem class=\"service\">nova-api</systemitem> service are running on the same host. If this is not the case, you must make this change in the <filename>/etc/nova/nova.conf</filename> file on the host running the <systemitem class=\"service\">nova-network</systemitem> service:"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:356(para)
|
||||
#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:358(para)
|
||||
msgid "Set the <literal>metadata_host</literal> configuration option to the IP address of the host where the <systemitem class=\"service\">nova-api</systemitem> service runs."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:364(title)
|
||||
#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:366(title)
|
||||
msgid "Enable ping and SSH on VMs"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:365(para)
|
||||
#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:367(para)
|
||||
msgid "Be sure you enable access to your VMs by using the <placeholder-1/> or <placeholder-2/> command. These commands enable you to <placeholder-3/> and <placeholder-4/> to your VMs:"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:369(para)
|
||||
#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:371(para)
|
||||
msgid "You must run these commands as root only if the credentials used to interact with <systemitem class=\"service\">nova-api</systemitem> are in <filename>/root/.bashrc</filename>. If the EC2 credentials are the <filename>.bashrc</filename> file for another user, you must run these commands as the user."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:375(para)
|
||||
#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:377(para)
|
||||
msgid "Run <placeholder-1/> commands:"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:378(para)
|
||||
#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:380(para)
|
||||
msgid "Using euca2ools:"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:381(para)
|
||||
#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:383(para)
|
||||
msgid "If you still cannot ping or SSH your instances after issuing the <placeholder-1/> commands, look at the number of <literal>dnsmasq</literal> processes that are running. If you have a running instance, check to see that TWO <literal>dnsmasq</literal> processes are running. If not, perform the following commands as root:"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:390(title)
|
||||
#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:392(title)
|
||||
msgid "Configure public (floating) IP addresses"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:392(para)
|
||||
#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:394(para)
|
||||
msgid "If you are using Compute's <systemitem class=\"service\">nova-network</systemitem> instead of OpenStack Networking (neutron) for networking in OpenStack, use procedures in this section to configure floating IP addresses. For instructions on how to configure OpenStack Networking (neutron) to provide access to instances through floating IP addresses, see <xref linkend=\"section_l3_router_and_nat\"/>."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:398(title)
|
||||
#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:400(title)
|
||||
msgid "Private and public IP addresses"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:399(para)
|
||||
#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:401(para)
|
||||
msgid "Every virtual instance is automatically assigned a private IP address. You can optionally assign public IP addresses to instances. The term <glossterm baseform=\"floating IP address\">floating IP</glossterm> refers to an IP address, typically public, that you can dynamically add to a running virtual instance. OpenStack Compute uses Network Address Translation (NAT) to assign floating IPs to virtual instances."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:405(para)
|
||||
#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:407(para)
|
||||
msgid "If you plan to use this feature, you must add edit the <filename>/etc/nova/nova.conf</filename> file to specify to which interface the <systemitem class=\"service\">nova-network</systemitem> service binds public IP addresses, as follows:"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:409(replaceable)
|
||||
#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:411(replaceable)
|
||||
msgid "VLAN100"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:410(para)
|
||||
#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:412(para)
|
||||
msgid "If you make changes to the <filename>/etc/nova/nova.conf</filename> file while the <systemitem class=\"service\">nova-network</systemitem> service is running, you must restart the service."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:414(title)
|
||||
#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:416(title)
|
||||
msgid "Traffic between VMs using floating IPs"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:415(para)
|
||||
#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:417(para)
|
||||
msgid "Because floating IPs are implemented by using a source NAT (SNAT rule in iptables), security groups can display inconsistent behavior if VMs use their floating IP to communicate with other VMs, particularly on the same physical host. Traffic from VM to VM across the fixed network does not have this issue, and so this is the recommended path. To ensure that traffic does not get SNATed to the floating range, explicitly set:"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:422(para)
|
||||
#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:424(para)
|
||||
msgid "The <literal>x.x.x.x/y</literal> value specifies the range of floating IPs for each pool of floating IPs that you define. If the VMs in the source group have floating IPs, this configuration is also required."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:428(title)
|
||||
#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:430(title)
|
||||
msgid "Enable IP forwarding"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:429(para)
|
||||
#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:431(para)
|
||||
msgid "By default, IP forwarding is disabled on most Linux distributions. To use the floating IP feature, you must enable IP forwarding."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:432(para)
|
||||
#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:434(para)
|
||||
msgid "You must enable IP forwarding only on the nodes that run the <systemitem class=\"service\">nova-network</systemitem> service. If you use <literal>multi_host</literal> mode, ensure that you enable it on all compute nodes. Otherwise, enable it on only the node that runs the <systemitem class=\"service\">nova-network</systemitem> service."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:438(para)
|
||||
#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:440(para)
|
||||
msgid "To check whether forwarding is enabled, run:"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:441(para)
|
||||
#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:443(para)
|
||||
msgid "Alternatively, you can run:"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:444(para)
|
||||
#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:446(para)
|
||||
msgid "In the previous example, IP forwarding is <emphasis role=\"bold\">disabled</emphasis>. To enable it dynamically, run:"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:447(para)
|
||||
#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:449(para)
|
||||
msgid "Or:"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:449(para)
|
||||
#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:451(para)
|
||||
msgid "To make the changes permanent, edit the <filename>/etc/sysctl.conf</filename> file and update the IP forwarding setting:"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:452(para)
|
||||
#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:454(para)
|
||||
msgid "Save the file and run the following command to apply the changes:"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:454(para)
|
||||
#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:456(para)
|
||||
msgid "You can also update the setting by restarting the network service:"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:457(para)
|
||||
#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:459(para)
|
||||
msgid "On Ubuntu, run:"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:461(para)
|
||||
#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:463(para)
|
||||
msgid "On RHEL/Fedora/CentOS, run:"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:467(title)
|
||||
#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:469(title)
|
||||
msgid "Create a list of available floating IP addresses"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:468(para)
|
||||
#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:470(para)
|
||||
msgid "Compute maintains a list of floating IP addresses that you can assign to instances. Use the <placeholder-1/> command to add entries to this list."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:473(para)
|
||||
#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:475(para)
|
||||
msgid "You can use the following <placeholder-1/> commands to perform floating IP operations:"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:478(para)
|
||||
#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:480(para)
|
||||
msgid "Lists the floating IP addresses in the pool."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:481(replaceable) ./doc/admin-guide-cloud/compute/section_compute-configure-migrations.xml:281(replaceable)
|
||||
#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:483(replaceable) ./doc/admin-guide-cloud/compute/section_compute-configure-migrations.xml:281(replaceable)
|
||||
msgid "POOL_NAME"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:482(para)
|
||||
#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:484(para)
|
||||
msgid "Creates specific floating IPs for either a single address or a subnet."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:487(para)
|
||||
#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:489(para)
|
||||
msgid "Removes floating IP addresses using the same parameters as the create command."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:491(para)
|
||||
#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:493(para)
|
||||
msgid "For information about how administrators can associate floating IPs with instances, see <link href=\"http://docs.openstack.org/user-guide-admin/content/manage_ip_addresses.html\">Manage IP addresses</link> in the <citetitle>OpenStack Admin User Guide</citetitle>."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:498(title)
|
||||
#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:500(title)
|
||||
msgid "Automatically add floating IPs"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:499(para)
|
||||
#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:501(para)
|
||||
msgid "You can configure the <systemitem class=\"service\">nova-network</systemitem> service to automatically allocate and assign a floating IP address to virtual instances when they are launched. Add the following line to the <filename>/etc/nova/nova.conf</filename> file and restart the <systemitem class=\"service\">nova-network</systemitem> service:"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:506(para)
|
||||
#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:508(para)
|
||||
msgid "If you enable this option and all floating IP addresses have already been allocated, the <placeholder-1/> command fails."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:512(title)
|
||||
#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:514(title)
|
||||
msgid "Remove a network from a project"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:513(para)
|
||||
#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:515(para)
|
||||
msgid "You cannot remove a network that has already been associated to a project by simply deleting it."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:515(para)
|
||||
#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:517(para)
|
||||
msgid "To determine the project ID, you must have administrative rights. You can disassociate the project from the network with a scrub command and the project ID as the final parameter:"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:521(title)
|
||||
#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:523(title)
|
||||
msgid "Multiple interfaces for your instances (multinic)"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:523(para)
|
||||
#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:525(para)
|
||||
msgid "The multinic feature allows you to plug more than one interface to your instances, making it possible to make several use cases available:"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:527(para)
|
||||
#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:529(para)
|
||||
msgid "SSL Configurations (VIPs)"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:530(para)
|
||||
#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:532(para)
|
||||
msgid "Services failover/ HA"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:533(para)
|
||||
#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:535(para)
|
||||
msgid "Bandwidth Allocation"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:536(para)
|
||||
#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:538(para)
|
||||
msgid "Administrative/ Public access to your instances"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:539(para)
|
||||
#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:541(para)
|
||||
msgid "Each VIF is representative of a separate network with its own IP block. Every network mode introduces its own set of changes regarding the multinic usage:"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:542(title)
|
||||
#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:544(title)
|
||||
msgid "multinic flat manager"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:552(title)
|
||||
#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:554(title)
|
||||
msgid "multinic flatdhcp manager"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:562(title)
|
||||
#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:564(title)
|
||||
msgid "multinic VLAN manager"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:572(title)
|
||||
#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:574(title)
|
||||
msgid "Use the multinic feature"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:573(para)
|
||||
#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:575(para)
|
||||
msgid "In order to use the multinic feature, first create two networks, and attach them to your tenant (still named 'project' on the command line): <placeholder-1/> Now every time you spawn a new instance, it gets two IP addresses from the respective DHCP servers:"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:586(para)
|
||||
#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:588(para)
|
||||
msgid "Make sure to power up the second interface on the instance, otherwise that last won't be reachable through its second IP. Here is an example of how to setup the interfaces within the instance (this is the configuration that needs to be applied inside the image):"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:590(filename)
|
||||
#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:592(filename)
|
||||
msgid "/etc/network/interfaces"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:602(para)
|
||||
#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:604(para)
|
||||
msgid "If the Virtual Network Service Neutron is installed, it is possible to specify the networks to attach to the respective interfaces by using the <literal>--nic</literal> flag when invoking the <literal>nova</literal> command:"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:606(replaceable)
|
||||
#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:608(replaceable)
|
||||
msgid "NETWORK1_ID"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:606(replaceable)
|
||||
#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:608(replaceable)
|
||||
msgid "NETWORK2_ID"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:611(title)
|
||||
#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:613(title)
|
||||
msgid "Troubleshoot Networking"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:613(title)
|
||||
#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:615(title)
|
||||
msgid "Cannot reach floating IPs"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:614(para)
|
||||
#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:616(para)
|
||||
msgid "If you cannot reach your instances through the floating IP address, check the following:"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:618(para)
|
||||
#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:620(para)
|
||||
msgid "Ensure the default security group allows ICMP (ping) and SSH (port 22), so that you can reach the instances:"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:629(para)
|
||||
#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:631(para)
|
||||
msgid "Ensure the NAT rules have been added to <systemitem>iptables</systemitem> on the node that <systemitem>nova-network</systemitem> is running on, as root:"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:637(para)
|
||||
#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:639(para)
|
||||
msgid "Check that the public address, in this example \"68.99.26.170\", has been added to your public interface. You should see the address in the listing when you enter \"ip addr\" at the command prompt."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:648(para)
|
||||
#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:650(para)
|
||||
msgid "You cannot <placeholder-1/> to an instance with a public IP from within the same server because the routing configuration does not allow it."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:654(para)
|
||||
#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:656(para)
|
||||
msgid "You can use <placeholder-1/> to identify if packets are being routed to the inbound interface on the compute host. If the packets are reaching the compute hosts but the connection is failing, the issue may be that the packet is being dropped by reverse path filtering. Try disabling reverse-path filtering on the inbound interface. For example, if the inbound interface is <literal>eth2</literal>, as root, run:"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:660(replaceable)
|
||||
#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:662(replaceable)
|
||||
msgid "ETH2"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:661(para)
|
||||
#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:663(para)
|
||||
msgid "If this solves your issue, add the following line to <filename>/etc/sysctl.conf</filename> so that the reverse-path filter is disabled the next time the compute host reboots:"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:669(title)
|
||||
#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:671(title)
|
||||
msgid "Disable firewall"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:670(para)
|
||||
#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:672(para)
|
||||
msgid "To help debug networking issues with reaching VMs, you can disable the firewall by setting the following option in <filename>/etc/nova/nova.conf</filename>:"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:673(para)
|
||||
#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:675(para)
|
||||
msgid "We strongly recommend you remove this line to re-enable the firewall once your networking issues have been resolved."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:677(title)
|
||||
#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:679(title)
|
||||
msgid "Packet loss from instances to nova-network server (VLANManager mode)"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:678(para)
|
||||
#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:680(para)
|
||||
msgid "If you can SSH to your instances but you find that the network interactions to your instance is slow, or if you find that running certain operations are slower than they should be (for example, <placeholder-1/>), then there may be packet loss occurring on the connection to the instance."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:682(para)
|
||||
#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:684(para)
|
||||
msgid "Packet loss can be caused by Linux networking configuration settings related to bridges. Certain settings can cause packets to be dropped between the VLAN interface (for example, <literal>vlan100</literal>) and the associated bridge interface (for example, <literal>br100</literal>) on the host running the <systemitem class=\"service\">nova-network</systemitem> service."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:687(para)
|
||||
#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:689(para)
|
||||
msgid "One way to check whether this is the issue in your setup, is to open up three terminals and run the following commands:"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:691(para)
|
||||
#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:693(para)
|
||||
msgid "In the first terminal, on the host running nova-network, use <placeholder-1/> on the VLAN interface to monitor DNS-related traffic (UDP, port 53). As root, run:"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:697(para)
|
||||
#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:699(para)
|
||||
msgid "In the second terminal, also on the host running nova-network, use <placeholder-1/> to monitor DNS-related traffic on the bridge interface. As root, run:"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:703(para)
|
||||
#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:705(para)
|
||||
msgid "In the third terminal, SSH inside of the instance and generate DNS requests by using the <placeholder-1/> command:"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:706(para)
|
||||
#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:708(para)
|
||||
msgid "The symptoms may be intermittent, so try running <placeholder-1/> multiple times. If the network configuration is correct, the command should return immediately each time. If it is not functioning properly, the command hangs for several seconds."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:712(para)
|
||||
#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:714(para)
|
||||
msgid "If the <placeholder-1/> command sometimes hangs, and there are packets that appear in the first terminal but not the second, then the problem may be due to filtering done on the bridges. Try to disable filtering, run the following commands as root:"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:719(para)
|
||||
#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:721(para)
|
||||
msgid "If this solves your issue, add the following line to <filename>/etc/sysctl.conf</filename> so that these changes take effect the next time the host reboots:"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:729(title)
|
||||
#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:731(title)
|
||||
msgid "KVM: Network connectivity works initially, then fails"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:730(para)
|
||||
#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:732(para)
|
||||
msgid "Some administrators have observed an issue with the KVM hypervisor where instances running Ubuntu 12.04 sometimes loses network connectivity after functioning properly for a period of time. Some users have reported success with loading the vhost_net kernel module as a workaround for this issue (see <link href=\"https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/997978/\">bug #997978</link>) . This kernel module may also <link href=\"http://www.linux-kvm.org/page/VhostNet\">improve network performance on KVM</link>. To load the kernel module, as root:"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:740(para)
|
||||
#: ./doc/admin-guide-cloud/compute/section_compute-networking-nova.xml:742(para)
|
||||
msgid "Loading the module has no effect on running instances."
|
||||
msgstr ""
|
||||
|
||||
|
||||
@ -1,7 +1,7 @@
|
||||
msgid ""
|
||||
msgstr ""
|
||||
"Project-Id-Version: PACKAGE VERSION\n"
|
||||
"POT-Creation-Date: 2014-11-11 06:13+0000\n"
|
||||
"POT-Creation-Date: 2014-11-19 06:10+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"
|
||||
@ -2367,23 +2367,23 @@ msgstr ""
|
||||
msgid "Now, start copying the data we have in the ring into the builder."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/common/section_objectstorage-troubleshoot.xml:85(para)
|
||||
#: ./doc/common/section_objectstorage-troubleshoot.xml:86(para)
|
||||
msgid "This is the extent of the recoverable fields. For <literal>min_part_hours</literal> you'll either have to remember what the value you used was, or just make up a new one."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/common/section_objectstorage-troubleshoot.xml:90(para)
|
||||
msgid "Try some validation: if this doesn't raise an exception, you may feel some hope. Not too much, though."
|
||||
#: ./doc/common/section_objectstorage-troubleshoot.xml:91(para)
|
||||
msgid "Next, validate the builder. If this raises an exception, check your previous code. When it validates, you're ready to save the builder and create a new account.builder."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/common/section_objectstorage-troubleshoot.xml:93(para)
|
||||
#: ./doc/common/section_objectstorage-troubleshoot.xml:95(para)
|
||||
msgid "Save the builder."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/common/section_objectstorage-troubleshoot.xml:97(para)
|
||||
#: ./doc/common/section_objectstorage-troubleshoot.xml:100(para)
|
||||
msgid "You should now have a file called 'account.builder' in the current working directory. Next, run <literal>swift-ring-builder account.builder write_ring</literal> and compare the new account.ring.gz to the account.ring.gz that you started from. They probably won't be byte-for-byte identical, but if you load them up in a REPL and their <literal>_replica2part2dev_id</literal> and <literal>devs</literal> attributes are the same (or nearly so), then you're in good shape."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/common/section_objectstorage-troubleshoot.xml:104(para)
|
||||
#: ./doc/common/section_objectstorage-troubleshoot.xml:107(para)
|
||||
msgid "Next, repeat the procedure for <filename>container.ring.gz</filename> and <filename>object.ring.gz</filename>, and you might get usable builder files."
|
||||
msgstr ""
|
||||
|
||||
|
||||
@ -19,8 +19,8 @@
|
||||
msgid ""
|
||||
msgstr ""
|
||||
"Project-Id-Version: OpenStack Manuals\n"
|
||||
"POT-Creation-Date: 2014-11-11 02:33+0000\n"
|
||||
"PO-Revision-Date: 2014-11-11 02:31+0000\n"
|
||||
"POT-Creation-Date: 2014-11-18 18:58+0000\n"
|
||||
"PO-Revision-Date: 2014-11-18 12:23+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"
|
||||
@ -3844,24 +3844,25 @@ msgstr ""
|
||||
msgid "Now, start copying the data we have in the ring into the builder."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/common/section_objectstorage-troubleshoot.xml85(para)
|
||||
#: ./doc/common/section_objectstorage-troubleshoot.xml86(para)
|
||||
msgid ""
|
||||
"This is the extent of the recoverable fields. For "
|
||||
"<literal>min_part_hours</literal> you'll either have to remember what the "
|
||||
"value you used was, or just make up a new one."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/common/section_objectstorage-troubleshoot.xml90(para)
|
||||
#: ./doc/common/section_objectstorage-troubleshoot.xml91(para)
|
||||
msgid ""
|
||||
"Try some validation: if this doesn't raise an exception, you may feel some "
|
||||
"hope. Not too much, though."
|
||||
"Next, validate the builder. If this raises an exception, check your previous"
|
||||
" code. When it validates, you're ready to save the builder and create a new "
|
||||
"account.builder."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/common/section_objectstorage-troubleshoot.xml93(para)
|
||||
#: ./doc/common/section_objectstorage-troubleshoot.xml95(para)
|
||||
msgid "Save the builder."
|
||||
msgstr "Enregistrer le générateur."
|
||||
|
||||
#: ./doc/common/section_objectstorage-troubleshoot.xml97(para)
|
||||
#: ./doc/common/section_objectstorage-troubleshoot.xml100(para)
|
||||
msgid ""
|
||||
"You should now have a file called 'account.builder' in the current working "
|
||||
"directory. Next, run <literal>swift-ring-builder account.builder "
|
||||
@ -3872,7 +3873,7 @@ msgid ""
|
||||
"attributes are the same (or nearly so), then you're in good shape."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/common/section_objectstorage-troubleshoot.xml104(para)
|
||||
#: ./doc/common/section_objectstorage-troubleshoot.xml107(para)
|
||||
msgid ""
|
||||
"Next, repeat the procedure for <filename>container.ring.gz</filename> and "
|
||||
"<filename>object.ring.gz</filename>, and you might get usable builder files."
|
||||
|
||||
@ -7,8 +7,8 @@
|
||||
msgid ""
|
||||
msgstr ""
|
||||
"Project-Id-Version: OpenStack Manuals\n"
|
||||
"POT-Creation-Date: 2014-11-11 02:33+0000\n"
|
||||
"PO-Revision-Date: 2014-11-11 02:31+0000\n"
|
||||
"POT-Creation-Date: 2014-11-18 18:58+0000\n"
|
||||
"PO-Revision-Date: 2014-11-18 12:23+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"
|
||||
@ -3832,24 +3832,25 @@ msgstr ""
|
||||
msgid "Now, start copying the data we have in the ring into the builder."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/common/section_objectstorage-troubleshoot.xml85(para)
|
||||
#: ./doc/common/section_objectstorage-troubleshoot.xml86(para)
|
||||
msgid ""
|
||||
"This is the extent of the recoverable fields. For "
|
||||
"<literal>min_part_hours</literal> you'll either have to remember what the "
|
||||
"value you used was, or just make up a new one."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/common/section_objectstorage-troubleshoot.xml90(para)
|
||||
#: ./doc/common/section_objectstorage-troubleshoot.xml91(para)
|
||||
msgid ""
|
||||
"Try some validation: if this doesn't raise an exception, you may feel some "
|
||||
"hope. Not too much, though."
|
||||
"Next, validate the builder. If this raises an exception, check your previous"
|
||||
" code. When it validates, you're ready to save the builder and create a new "
|
||||
"account.builder."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/common/section_objectstorage-troubleshoot.xml93(para)
|
||||
#: ./doc/common/section_objectstorage-troubleshoot.xml95(para)
|
||||
msgid "Save the builder."
|
||||
msgstr "ビルダーを保存します。"
|
||||
|
||||
#: ./doc/common/section_objectstorage-troubleshoot.xml97(para)
|
||||
#: ./doc/common/section_objectstorage-troubleshoot.xml100(para)
|
||||
msgid ""
|
||||
"You should now have a file called 'account.builder' in the current working "
|
||||
"directory. Next, run <literal>swift-ring-builder account.builder "
|
||||
@ -3860,7 +3861,7 @@ msgid ""
|
||||
"attributes are the same (or nearly so), then you're in good shape."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/common/section_objectstorage-troubleshoot.xml104(para)
|
||||
#: ./doc/common/section_objectstorage-troubleshoot.xml107(para)
|
||||
msgid ""
|
||||
"Next, repeat the procedure for <filename>container.ring.gz</filename> and "
|
||||
"<filename>object.ring.gz</filename>, and you might get usable builder files."
|
||||
|
||||
@ -6,8 +6,8 @@
|
||||
msgid ""
|
||||
msgstr ""
|
||||
"Project-Id-Version: OpenStack Manuals\n"
|
||||
"POT-Creation-Date: 2014-11-17 23:24+0000\n"
|
||||
"PO-Revision-Date: 2014-11-18 04:00+0000\n"
|
||||
"POT-Creation-Date: 2014-11-18 18:58+0000\n"
|
||||
"PO-Revision-Date: 2014-11-18 12:04+0000\n"
|
||||
"Last-Translator: Tomoyuki KATO <tomo@dream.daynight.jp>\n"
|
||||
"Language-Team: Japanese (http://www.transifex.com/projects/p/openstack-manuals-i18n/language/ja/)\n"
|
||||
"MIME-Version: 1.0\n"
|
||||
@ -254,7 +254,7 @@ msgid ""
|
||||
"In a high-availability setup with an active/passive configuration, systems "
|
||||
"are set up to bring additional resources online to replace those that have "
|
||||
"failed."
|
||||
msgstr ""
|
||||
msgstr "アクティブ/パッシブ設定を用いた高可用性セットアップでは、故障したシステムを置き換えるために、システムが追加リソースをオンラインにするようセットアップされる。"
|
||||
|
||||
#: ./doc/glossary/glossary-terms.xml245(glossterm)
|
||||
#: ./doc/glossary/glossary-terms.xml247(primary)
|
||||
@ -684,11 +684,11 @@ msgstr "論理ポートへのインターフェースIDの紐付け。インタ
|
||||
#: ./doc/glossary/glossary-terms.xml678(glossterm)
|
||||
#: ./doc/glossary/glossary-terms.xml680(primary)
|
||||
msgid "auditing"
|
||||
msgstr ""
|
||||
msgstr "監査"
|
||||
|
||||
#: ./doc/glossary/glossary-terms.xml684(para)
|
||||
msgid "Provided in Compute through the system usage data facility."
|
||||
msgstr ""
|
||||
msgstr "システム使用状況データ機能経由で Compute において提供される。"
|
||||
|
||||
#: ./doc/glossary/glossary-terms.xml690(glossterm)
|
||||
#: ./doc/glossary/glossary-terms.xml692(primary)
|
||||
@ -924,7 +924,7 @@ msgstr "bare, 定義"
|
||||
msgid ""
|
||||
"An Image Service container format that indicates that no container exists "
|
||||
"for the VM image."
|
||||
msgstr ""
|
||||
msgstr "仮想マシンイメージ用のコンテナーが存在しないことを意味する、Image Service のコンテナー形式。"
|
||||
|
||||
#: ./doc/glossary/glossary-terms.xml947(glossterm)
|
||||
#: ./doc/glossary/glossary-terms.xml949(primary)
|
||||
@ -991,7 +991,7 @@ msgstr "ビット, 定義"
|
||||
msgid ""
|
||||
"A bit is a single digit number that is in base of 2 (either a zero or one). "
|
||||
"Bandwidth usage is measured in bits per second."
|
||||
msgstr ""
|
||||
msgstr "ビットは、2 を基数とする単一のデジタル数値 (0 または 1)。帯域使用量は、ビット毎秒 (bps) で測定される。"
|
||||
|
||||
#: ./doc/glossary/glossary-terms.xml1016(glossterm)
|
||||
#: ./doc/glossary/glossary-terms.xml1018(primary)
|
||||
@ -2482,7 +2482,7 @@ msgstr "分散仮想ルーター (DVR)"
|
||||
msgid ""
|
||||
"Mechanism for highly-available multi-host routing when using OpenStack "
|
||||
"Networking (neutron)."
|
||||
msgstr ""
|
||||
msgstr "OpenStack Networking (neutron) の使用時、高可用なマルチホストルーティングのための機構。"
|
||||
|
||||
#: ./doc/glossary/glossary-terms.xml2597(glossterm)
|
||||
#: ./doc/glossary/glossary-terms.xml2599(primary)
|
||||
@ -5626,7 +5626,7 @@ msgstr "orphan"
|
||||
msgid ""
|
||||
"In the context of Object Storage, this is a process that is not terminated "
|
||||
"after an upgrade, restart, or reload of the service."
|
||||
msgstr ""
|
||||
msgstr "Object Storage の文脈において、サービスの更新、再起動、再読み込みの後に終了しないプロセス。"
|
||||
|
||||
#: ./doc/glossary/glossary-terms.xml6072(title)
|
||||
msgid "P"
|
||||
@ -5662,7 +5662,7 @@ msgstr "パーティション"
|
||||
msgid ""
|
||||
"A unit of storage within Object Storage used to store objects. It exists on "
|
||||
"top of devices and is replicated for fault tolerance."
|
||||
msgstr ""
|
||||
msgstr "オブジェクトを保存するために使用される、Object Storage 内の保存単位。デバイスの上位に存在し、耐障害のために複製される。"
|
||||
|
||||
#: ./doc/glossary/glossary-terms.xml6108(glossterm)
|
||||
#: ./doc/glossary/glossary-terms.xml6112(secondary)
|
||||
@ -5672,7 +5672,7 @@ msgstr "パーティションインデックス"
|
||||
#: ./doc/glossary/glossary-terms.xml6116(para)
|
||||
msgid ""
|
||||
"Contains the locations of all Object Storage partitions within the ring."
|
||||
msgstr ""
|
||||
msgstr "リング内にあるすべての Object Storage のパーティションの場所を含む。"
|
||||
|
||||
#: ./doc/glossary/glossary-terms.xml6122(glossterm)
|
||||
msgid "partition shift value"
|
||||
@ -5701,13 +5701,13 @@ msgstr "エンド間の MTU を検出し、パケットサイズを適切に調
|
||||
#: ./doc/glossary/glossary-terms.xml6148(glossterm)
|
||||
#: ./doc/glossary/glossary-terms.xml6150(primary)
|
||||
msgid "pause"
|
||||
msgstr "ポーズ"
|
||||
msgstr "一時停止"
|
||||
|
||||
#: ./doc/glossary/glossary-terms.xml6154(para)
|
||||
msgid ""
|
||||
"A VM state where no changes occur (no changes in memory, network "
|
||||
"communications stop, etc); the VM is frozen but not shut down."
|
||||
msgstr ""
|
||||
msgstr "変更が発生しない (メモリーの変更なし、ネットワーク通信の停止など)、仮想マシンの状態。仮想マシンは停止するが、シャットダウンしない。"
|
||||
|
||||
#: ./doc/glossary/glossary-terms.xml6160(glossterm)
|
||||
#: ./doc/glossary/glossary-terms.xml6162(primary)
|
||||
@ -5718,7 +5718,7 @@ msgstr "PCI パススルー"
|
||||
msgid ""
|
||||
"Gives guest VMs exclusive access to a PCI device. Currently supported in "
|
||||
"OpenStack Havana and later releases."
|
||||
msgstr ""
|
||||
msgstr "ゲスト仮想マシンが PCI デバイスに排他的にアクセスされる。OpenStack Havana 以降でサポートされる。"
|
||||
|
||||
#: ./doc/glossary/glossary-terms.xml6172(glossterm)
|
||||
msgid "persistent message"
|
||||
@ -6273,7 +6273,7 @@ msgstr "リビルド"
|
||||
|
||||
#: ./doc/glossary/glossary-terms.xml6796(primary)
|
||||
msgid "rebuilding"
|
||||
msgstr ""
|
||||
msgstr "リビルド"
|
||||
|
||||
#: ./doc/glossary/glossary-terms.xml6800(para)
|
||||
msgid ""
|
||||
@ -6597,7 +6597,7 @@ msgstr "ラウンドロビン"
|
||||
msgid ""
|
||||
"Type of Compute scheduler that evenly distributes instances among available "
|
||||
"hosts."
|
||||
msgstr ""
|
||||
msgstr "利用可能なホスト間でインスタンスを平等に分散させる、Compute のスケジューラーの一種。"
|
||||
|
||||
#: ./doc/glossary/glossary-terms.xml7145(glossterm)
|
||||
#: ./doc/glossary/glossary-terms.xml7147(primary)
|
||||
|
||||
Loading…
Reference in New Issue
Block a user