Imported Translations from Transifex

For more information about this automatic import see:
https://wiki.openstack.org/wiki/Translations/Infrastructure

Change-Id: Id20981589ddd96b22fe55eed50952465ec94da02
This commit is contained in:
OpenStack Proposal Bot 2014-12-17 06:13:02 +00:00
parent 4f34cb1276
commit daba800aa9
8 changed files with 1080 additions and 1174 deletions

View File

@ -1,7 +1,7 @@
msgid ""
msgstr ""
"Project-Id-Version: PACKAGE VERSION\n"
"POT-Creation-Date: 2014-12-13 06:12+0000\n"
"POT-Creation-Date: 2014-12-17 06:11+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"
@ -334,7 +334,7 @@ msgstr ""
msgid "You can retrieve the collected samples three different ways: with the REST API, with the command line interface, or with the Metering tab on an OpenStack dashboard."
msgstr ""
#: ./doc/admin-guide-cloud/ch_database.xml:7(title) ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:783(td)
#: ./doc/admin-guide-cloud/ch_database.xml:7(title) ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:786(td)
msgid "Database"
msgstr ""
@ -442,7 +442,7 @@ msgstr ""
msgid "--config-file=/etc/trove/trove.conf"
msgstr ""
#: ./doc/admin-guide-cloud/ch_database.xml:88(para) ./doc/admin-guide-cloud/networking/section_networking-use.xml:106(option) ./doc/admin-guide-cloud/networking/section_networking-use.xml:210(option) ./doc/admin-guide-cloud/networking/section_networking-use.xml:286(option) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:267(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:625(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:887(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1009(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1077(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1199(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1595(td) ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:570(term)
#: ./doc/admin-guide-cloud/ch_database.xml:88(para) ./doc/admin-guide-cloud/networking/section_networking-use.xml:106(option) ./doc/admin-guide-cloud/networking/section_networking-use.xml:210(option) ./doc/admin-guide-cloud/networking/section_networking-use.xml:286(option) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:267(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:625(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:887(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1009(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1077(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1199(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1595(td) ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:573(term)
msgid "name"
msgstr ""
@ -7210,7 +7210,7 @@ msgstr ""
msgid "The list of supported database back ends:"
msgstr ""
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-system-architecture.xml:91(link) ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:791(td)
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-system-architecture.xml:91(link) ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:794(td)
msgid "MongoDB"
msgstr ""
@ -7222,11 +7222,11 @@ msgstr ""
msgid "PostgreSQL"
msgstr ""
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-system-architecture.xml:100(link) ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:810(td)
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-system-architecture.xml:100(link) ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:813(td)
msgid "HBase"
msgstr ""
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-system-architecture.xml:103(link) ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:818(td)
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-system-architecture.xml:103(link) ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:821(td)
msgid "DB2"
msgstr ""
@ -7422,7 +7422,7 @@ msgstr ""
msgid "Processing notifications from other OpenStack services, by consuming messages from the configured message queue system."
msgstr ""
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:30(term) ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:184(title)
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:30(term) ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:187(title)
msgid "Polling"
msgstr ""
@ -7522,7 +7522,7 @@ msgstr ""
msgid "Configure the Image Service for Telemetry section"
msgstr ""
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:99(citetitle) ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:144(citetitle)
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:99(citetitle) ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:147(citetitle)
msgid "OpenStack Installation Guide"
msgstr ""
@ -7530,7 +7530,7 @@ msgstr ""
msgid "The required configuration for Image service can be found in the <placeholder-1/> section in the <placeholder-2/>."
msgstr ""
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:102(td) ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:209(para)
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:102(td) ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:212(para)
msgid "OpenStack Networking"
msgstr ""
@ -7622,7 +7622,7 @@ msgstr ""
msgid "orchestration.stack.suspend.end"
msgstr ""
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:131(td) ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:215(para)
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:131(td) ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:218(para)
msgid "OpenStack Block Storage"
msgstr ""
@ -7639,638 +7639,650 @@ msgid "volume.delete.*"
msgstr ""
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:135(para)
msgid "volume.resize.*"
msgid "volume.update.*"
msgstr ""
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:136(para)
msgid "snapshot.exists"
msgid "volume.resize.*"
msgstr ""
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:137(para)
msgid "snapshot.create.*"
msgid "volume.attach.*"
msgstr ""
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:138(para)
msgid "snapshot.delete.*"
msgid "volume.detach.*"
msgstr ""
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:139(para)
msgid "snapshot.resize.*"
msgid "snapshot.exists"
msgstr ""
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:142(link)
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:140(para)
msgid "snapshot.create.*"
msgstr ""
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:141(para)
msgid "snapshot.delete.*"
msgstr ""
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:142(para)
msgid "snapshot.update.*"
msgstr ""
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:145(link)
msgid "Add the Block Storage service agent for Telemetry section"
msgstr ""
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:140(td)
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:143(td)
msgid "The required configuration for Block Storage service can be found in the <placeholder-1/> section in the <placeholder-2/>."
msgstr ""
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:149(para)
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:152(para)
msgid "Some services require additional configuration to emit the notifications using the correct control exchange on the message queue and so forth. These configuration needs are referred in the above table for each OpenStack service that needs it."
msgstr ""
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:155(para)
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:158(para)
msgid "When the <literal>store_events</literal> option is set to True in <filename>ceilometer.conf</filename>, the notification agent needs database access in order to work properly."
msgstr ""
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:160(title)
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:163(title)
msgid "Middleware for OpenStack Object Storage service"
msgstr ""
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:161(para)
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:164(para)
msgid "A subset of Object Store statistics requires an additional middleware to be installed behind the proxy of Object Store. This additional component emits notifications containing the data-flow-oriented meters, namely the storage.objects.(incoming|outgoing).bytes values. The list of these meters are listed in the <link href=\"http://docs.openstack.org/developer/ceilometer/measurements.html#object-storage-swift\"> Swift</link> table section in the <citetitle>Telemetry Measurements Reference</citetitle>, marked with <literal>notification</literal> as origin."
msgstr ""
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:168(para)
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:171(para)
msgid "The instructions on how to install this middleware can be found in <link href=\"http://docs.openstack.org/trunk/install-guide/install/apt/content/ceilometer-install-swift.html\"> Configure the Object Storage service for Telemetry</link> section in the <citetitle>OpenStack Installation Guide</citetitle>."
msgstr ""
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:175(title)
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:178(title)
msgid "Telemetry middleware"
msgstr ""
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:176(para)
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:179(para)
msgid "Telemetry provides the capability of counting the HTTP requests and responses for each API endpoint in OpenStack. This is achieved by storing a sample for each event marked as <literal>http.request</literal> or <literal>http.response</literal>."
msgstr ""
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:179(para)
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:182(para)
msgid "Telemetry can consume these events if the services are configured to emit notifications with these two event types."
msgstr ""
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:185(para)
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:188(para)
msgid "The Telemetry module is intended to store a complex picture of the infrastructure. This goal requires additional information than what is provided by the events and notifications published by each service. Some information is not emitted directly, like resource usage of the VM instances."
msgstr ""
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:190(para)
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:193(para)
msgid "Therefore Telemetry uses another method to gather this data by polling the infrastructure including the APIs of the different OpenStack services and other assets, like hypervisors. The latter case requires closer interaction with the compute hosts. To solve this issue, Telemetry uses an agent based architecture to fulfill the requirements against the data collection."
msgstr ""
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:195(para)
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:198(para)
msgid "There are two agents supporting the polling mechanism, namely the compute agent and the central agent. The following subsections give further information regarding to the architectural and configuration details of these components."
msgstr ""
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:200(title)
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:203(title)
msgid "Central agent"
msgstr ""
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:201(para)
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:204(para)
msgid "As the name of this agent shows, it is a central component in the Telemetry architecture. This agent is responsible for polling public REST APIs to retrieve additional information on OpenStack resources not already surfaced via notifications, and also for polling hardware resources over SNMP."
msgstr ""
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:205(para)
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:208(para)
msgid "The following services can be polled with this agent:"
msgstr ""
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:212(para)
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:215(para)
msgid "OpenStack Object Storage"
msgstr ""
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:218(para)
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:221(para)
msgid "Hardware resources via SNMP"
msgstr ""
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:221(para)
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:224(para)
msgid "Energy consumption metrics via <link href=\"https://launchpad.net/kwapi\"> Kwapi</link> framework"
msgstr ""
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:225(para)
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:228(para)
msgid "To install and configure this service use the <link href=\"http://docs.openstack.org/trunk/install-guide/install/apt/content/ceilometer-install.html\"> Install the Telemetry module</link> section in the <citetitle>OpenStack Installation Guide</citetitle>."
msgstr ""
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:229(para)
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:232(para)
msgid "The central agent does not need direct database connection. The samples collected by this agent are sent via message queue to the collector service, which is responsible for persisting the data into the configured database back end."
msgstr ""
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:235(title)
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:238(title)
msgid "Compute agent"
msgstr ""
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:236(para)
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:239(para)
msgid "This agent is responsible for collecting resource usage data of VM instances on individual compute nodes within an OpenStack deployment. This mechanism requires a closer interaction with the hypervisor, therefore a separate agent type fulfills the collection of the related meters, which placed on the host machines to locally retrieve this information."
msgstr ""
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:241(para)
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:244(para)
msgid "A compute agent instance has to be installed on each and every compute node, installation instructions can be found in the <link href=\"http://docs.openstack.org/trunk/install-guide/install/apt/content/ceilometer-install-nova.html\"> Install the Compute agent for Telemetry</link> section in the <citetitle>OpenStack Installation Guide</citetitle>."
msgstr ""
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:247(para) ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:340(para)
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:250(para) ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:343(para)
msgid "Just like the central agent, this component also does not need a direct database access. The samples are sent via AMQP to the collector."
msgstr ""
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:250(para)
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:253(para)
msgid "The list of supported hypervisors can be found in <xref linkend=\"section_telemetry-supported-hypervisors\"/>. The compute agent uses the API of the hypervisor installed on the compute hosts. Therefore the supported meters can be different in case of each virtualization back end, as these tools provide different set of metrics."
msgstr ""
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:255(para)
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:258(para)
msgid "The list of collected meters can be found in the <link href=\"http://docs.openstack.org/developer/ceilometer/measurements.html#compute-nova\"> Compute section</link> in the <citetitle>Telemetry Measurements Reference</citetitle>. The support column provides the information that which meter is available for each hypervisor supported by the Telemetry module."
msgstr ""
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:261(para)
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:264(para)
msgid "Telemetry supports Libvirt, which hides the hypervisor under it."
msgstr ""
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:265(title)
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:268(title)
msgid "Support for HA deployment of the central and compute agent services"
msgstr ""
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:266(para)
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:269(para)
msgid "Both the central and the compute agent can run in an HA deployment, which means that multiple instances of these services can run in parallel with workload partitioning among these running instances."
msgstr ""
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:269(para)
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:272(para)
msgid "The <link href=\"https://pypi.python.org/pypi/tooz\">Tooz</link> library provides the coordination within the groups of service instances. It provides an API above several back ends that can be used for building distributed applications."
msgstr ""
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:276(para)
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:279(para)
msgid "<link href=\"http://zookeeper.apache.org/\">Zookeeper</link>. Recommended solution by the Tooz project."
msgstr ""
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:280(link)
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:283(link)
msgid "Memcached"
msgstr ""
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:273(para)
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:276(para)
msgid "Tooz supports the following back-end solutions: <placeholder-1/> You must configure these back ends to use either of them for the HA deployment of the Telemetry services."
msgstr ""
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:285(para)
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:288(para)
msgid "For information about the required configuration options that have to be set in the <filename>ceilometer.conf</filename> configuration file for both the central and compute agents, see the <link href=\"http://docs.openstack.org/trunk/config-reference/content/ch_configuring-openstack-telemetry.html\"><literal>coordination</literal> section</link> in the <citetitle>OpenStack Configuration Reference</citetitle>."
msgstr ""
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:292(para)
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:295(para)
msgid "Without the <option>backend_url</option> option being set only one instance of both the central and compute agent service is able to run and function correctly."
msgstr ""
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:296(para)
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:299(para)
msgid "The availability check of the instances is provided by heartbeat messages. When the connection with an instance is lost, the workload will be reassigned within the remained instances in the next polling cycle."
msgstr ""
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:300(para)
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:303(para)
msgid "<literal>Memcached</literal> uses a <option>timeout</option> value, which should always be set to a value that is higher than the <option>heartbeat</option> value set for Telemetry."
msgstr ""
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:304(para)
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:307(para)
msgid "For backward compatibility and supporting existing deployments, the central agent configuration also supports using different configuration files for groups of service instances of this type that are running in parallel. For enabling this configuration set a value for the <option>partitioning_group_prefix</option> option in the <link href=\"http://docs.openstack.org/trunk/config-reference/content/ch_configuring-openstack-telemetry.html\"><literal>central</literal> section</link> in the <citetitle>OpenStack Configuration Reference</citetitle>."
msgstr ""
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:312(para)
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:315(para)
msgid "For each sub-group of the central agent pool with the same <option>partitioning_group_prefix</option> a disjoint subset of meters must be polled, otherwise samples may be missing or duplicated. The list of meters to poll can be set in the <filename>/etc/ceilometer/pipeline.yaml</filename> configuration file. For more information about pipelines see <xref linkend=\"section_telemetry-data-collection-processing\"/>."
msgstr ""
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:319(para)
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:322(para)
msgid "To enable the compute agent to run multiple instances simultaneously with workload partitioning, the <option>workload_partitioning</option> option has to be set to <literal>True</literal> under the <link href=\"http://docs.openstack.org/trunk/config-reference/content/ch_configuring-openstack-telemetry.html\"> compute section</link> in the <filename>ceilometer.conf</filename> configuration file."
msgstr ""
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:327(title)
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:330(title)
msgid "IPMI agent"
msgstr ""
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:328(para)
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:331(para)
msgid "This agent is responsible for collecting IPMI sensor data and Intel Node Manager data on individual compute nodes within an OpenStack deployment. This agent requires IPMI capable node with <application>ipmitool</application> installed, which is a common utility for IPMI control on various Linux distributions."
msgstr ""
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:332(para)
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:335(para)
msgid "An IPMI agent instance could be installed on each and every compute node with IPMI support, except that the node is managed by Bare metal module for OpenStack and the <option>conductor.send_sensor_data</option> option is set to <literal>true</literal> in the Bare metal module for OpenStack. It is no harm to install this agent on compute node without IPMI or Intel Node Manager support, as the agent checks for the hardware and if none is available, returns empty data. But it is suggested that you install IPMI agent only on IPMI capable node for performance reason."
msgstr ""
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:343(para)
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:346(para)
msgid "The list of collected meters can be found in the <link href=\"http://docs.openstack.org/developer/ceilometer/measurements.html#ironic-hardware-ipmi-sensor-data\"> Ironic Hardware IPMI Sensor Data section</link> in the <citetitle>Telemetry Measurements Reference</citetitle>."
msgstr ""
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:347(para)
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:350(para)
msgid "Do not deploy both IPMI agent and Bare metal module for OpenStack on one compute node. If <option>conductor.send_sensor_data</option> set, this misconfiguration causes duplicated IPMI sensor samples."
msgstr ""
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:355(title)
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:358(title)
msgid "Send samples to Telemetry"
msgstr ""
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:356(para)
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:359(para)
msgid "Most parts of the data collections in the Telemetry module are automated. Telemetry provides the possibility to submit samples via the REST API to allow users to send custom samples into this module."
msgstr ""
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:359(para)
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:362(para)
msgid "This option makes it possible to send any kind of samples without the need of writing extra code lines or making configuration changes."
msgstr ""
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:361(para)
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:364(para)
msgid "The samples that can be sent to Telemetry are not limited to the actual existing meters. There is a possibility to provide data for any new, customer defined counter by filling out all the required fields of the POST request."
msgstr ""
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:365(para)
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:368(para)
msgid "If the sample corresponds to an existing meter, then the fields like <literal>meter-type</literal> and meter name should be matched accordingly."
msgstr ""
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:371(para)
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:374(para)
msgid "ID of the corresponding resource. (<parameter>--resource-id</parameter>)"
msgstr ""
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:374(para)
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:377(para)
msgid "Name of meter. (<parameter>--meter-name</parameter>)"
msgstr ""
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:377(para)
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:380(para)
msgid "Type of meter. (<parameter>--meter-type</parameter>)"
msgstr ""
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:378(para)
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:381(para)
msgid "Predefined meter types:"
msgstr ""
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:381(para)
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:384(para)
msgid "Gauge"
msgstr ""
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:384(para)
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:387(para)
msgid "Delta"
msgstr ""
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:387(para)
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:390(para)
msgid "Cumulative"
msgstr ""
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:392(para)
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:395(para)
msgid "Unit of meter. (<parameter>--meter-unit</parameter>)"
msgstr ""
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:395(para)
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:398(para)
msgid "Volume of sample. (<parameter>--sample-volume</parameter>)"
msgstr ""
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:367(para)
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:370(para)
msgid "The required fields for sending a sample using the command line client are: <placeholder-1/>"
msgstr ""
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:399(para)
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:402(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 following command should be invoked: <placeholder-1/>"
msgstr ""
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:423(title)
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:426(title)
msgid "Data collection and processing"
msgstr ""
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:424(para)
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:427(para)
msgid "The mechanism via the data is collected and processed and is called pipeline. Pipelines, at the configuration level, describe a coupling between sources of samples and the corresponding sinks for transformation and publication of data."
msgstr ""
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:428(para)
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:431(para)
msgid "A source is a producer of samples, in effect, a set of pollsters and/or notification handlers emitting samples for a set of matching meters."
msgstr ""
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:431(para)
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:434(para)
msgid "Each source configuration encapsulates meter name matching, polling interval determination, optional resource enumeration or discovery, and mapping to one or more sinks for publication."
msgstr ""
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:434(para)
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:437(para)
msgid "A sink on the other hand is a consumer of samples, providing logic for the transformation and publication of samples emitted from related sources. Each sink configuration is concerned only with the transformation rules and publication conduits for samples."
msgstr ""
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:438(para)
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:441(para)
msgid "In effect, a sink describes a chain of handlers. The chain starts with zero or more transformers and ends with one or more publishers. The first transformer in the chain is passed samples from the corresponding source, takes some action such as deriving rate of change, performing unit conversion, or aggregating, before passing the modified sample to the next step that is described in <xref linkend=\"section_telemetry-publishers\"/>."
msgstr ""
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:446(title)
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:449(title)
msgid "Pipeline configuration"
msgstr ""
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:447(para)
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:450(para)
msgid "Pipeline configuration by default, is stored in a separate configuration file, called <filename>pipeline.yaml</filename>, next to the <filename>ceilometer.conf</filename> file. The pipeline configuration file can be set in the <parameter>pipeline_cfg_file</parameter> parameter listed in the <link href=\"http://docs.openstack.org/trunk/config-reference/content/ch_configuring-openstack-telemetry.html\">Description of configuration options for api table</link> section in the <citetitle>OpenStack Configuration Reference</citetitle>. Multiple chains can be defined in one pipeline configuration file."
msgstr ""
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:456(para)
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:459(para)
msgid "The chain definition looks like the following:"
msgstr ""
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:472(para)
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:475(para)
msgid "The interval parameter in the sources section should be defined in seconds. It determines the cadence of sample injection into the pipeline, where samples are produced under the direct control of an agent, for instance via a polling cycle as opposed to incoming notifications."
msgstr ""
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:476(para)
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:479(para)
msgid "There are several ways to define the list of meters for a pipeline source. The list of valid meters can be found in the <link href=\"http://docs.openstack.org/developer/ceilometer/measurements.html\"> Telemetry Measurements Reference</link> document. There is a possibility to define all the meters, or just included or excluded meters, with which a source should operate:"
msgstr ""
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:484(para)
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:487(para)
msgid "To include all meters, use the <literal>*</literal> wildcard symbol."
msgstr ""
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:487(para)
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:490(para)
msgid "To define the list of meters, use either of the following:"
msgstr ""
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:490(para)
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:493(para)
msgid "To define the list of included meters, use the <literal>meter_name</literal> syntax."
msgstr ""
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:494(para)
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:497(para)
msgid "To define the list of excluded meters, use the <literal>!meter_name</literal> syntax."
msgstr ""
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:498(para)
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:501(para)
msgid "For meters, which have variants identified by a complex name field, use the wildcard symbol to select all, e.g. for “instance:m1.tiny”, use “instance:*”."
msgstr ""
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:505(para)
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:508(para)
msgid "The above definition methods can be used in the following combinations:"
msgstr ""
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:508(para)
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:511(para)
msgid "Use only the wildcard symbol."
msgstr ""
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:511(para)
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:514(para)
msgid "Use the list of included meters."
msgstr ""
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:514(para)
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:517(para)
msgid "Use the list of excluded meters."
msgstr ""
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:517(para)
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:520(para)
msgid "Use wildcard symbol with the list of excluded meters."
msgstr ""
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:521(para)
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:524(para)
msgid "At least one of the above variations should be included in the meters section. Included and excluded meters cannot co-exist in the same pipeline. Wildcard and included meters cannot co-exist in the same pipeline definition section."
msgstr ""
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:525(para)
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:528(para)
msgid "The optional resources section of a pipeline source allows a static list of resource URLs to be configured for polling."
msgstr ""
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:527(para)
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:530(para)
msgid "The transformers section of a pipeline sink provides the possibility to add a list of transformer definitions. The available transformers are:"
msgstr ""
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:530(caption)
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:533(caption)
msgid "List of available transformers"
msgstr ""
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:535(td)
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:538(td)
msgid "Name of transformer"
msgstr ""
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:536(td)
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:539(td)
msgid "Reference name for configuration"
msgstr ""
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:541(td)
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:544(td)
msgid "Accumulator"
msgstr ""
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:542(td)
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:545(td)
msgid "accumulator"
msgstr ""
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:545(td)
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:548(td)
msgid "Aggregator"
msgstr ""
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:546(td)
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:549(td)
msgid "aggregator"
msgstr ""
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:549(td)
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:552(td)
msgid "Arithmetic"
msgstr ""
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:550(td)
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:553(td)
msgid "arithmetic"
msgstr ""
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:553(td)
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:556(td)
msgid "Rate of change"
msgstr ""
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:554(td)
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:557(td)
msgid "rate_of_change"
msgstr ""
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:557(td)
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:560(td)
msgid "Unit conversion"
msgstr ""
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:558(td)
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:561(td)
msgid "unit_conversion"
msgstr ""
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:562(para)
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:565(para)
msgid "The publishers section contains the list of publishers, where the samples data should be sent after the possible transformations."
msgstr ""
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:565(title)
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:568(title)
msgid "Transformers"
msgstr ""
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:566(para)
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:569(para)
msgid "The definition of transformers can contain the following fields:"
msgstr ""
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:572(para)
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:575(para)
msgid "Name of the transformer."
msgstr ""
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:576(term)
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:579(term)
msgid "parameters"
msgstr ""
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:578(para)
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:581(para)
msgid "Parameters of the transformer."
msgstr ""
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:583(para)
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:586(para)
msgid "The parameters section can contain transformer specific fields, like source and target fields with different subfields in case of the rate of change, which depends on the implementation of the transformer."
msgstr ""
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:587(title)
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:590(title)
msgid "Rate of change transformer"
msgstr ""
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:588(para)
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:591(para)
msgid "In the case of the transformer that creates the <literal>cpu_util</literal> meter, the definition looks like the following:"
msgstr ""
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:598(para)
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:601(para)
msgid "The rate of change the transformer generates is the <literal>cpu_util</literal>meter from the sample values of the <literal>cpu</literal> counter, which represents cumulative CPU time in nanoseconds. The transformer definition above defines a scale factor (for nanoseconds, multiple CPUs, etc.), which is applied before the transformation derives a sequence of gauge samples with unit %, from sequential values of the <literal>cpu</literal> meter."
msgstr ""
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:604(para)
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:607(para)
msgid "The definition for the disk I/O rate, which is also generated by the rate of change transformer:"
msgstr ""
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:620(title)
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:623(title)
msgid "Unit conversion transformer"
msgstr ""
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:621(para)
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:624(para)
msgid "Transformer to apply a unit conversion. It takes the volume of the meter and multiplies it with the given scale expression. Also supports <literal>map_from </literal> and <literal>map_to</literal> like the rate of change transformer."
msgstr ""
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:624(para)
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:627(para)
msgid "Sample configuration:"
msgstr ""
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:632(para)
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:635(para)
msgid "With the <parameter>map_from</parameter> and <parameter>map_to</parameter> :"
msgstr ""
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:647(title)
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:650(title)
msgid "Aggregator transformer"
msgstr ""
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:648(para)
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:651(para)
msgid "A transformer that sums up the incoming samples until enough samples have come in or a timeout has been reached."
msgstr ""
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:650(para)
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:653(para)
msgid "Timeout can be specified with the <parameter>retention_time</parameter> parameter. If we want to flush the aggregation after a set number of samples have been aggregated, we can specify the size parameter."
msgstr ""
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:653(para)
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:656(para)
msgid "The volume of the created sample is the sum of the volumes of samples that came into the transformer. Samples can be aggregated by the attributes <parameter>project_id </parameter>, <parameter>user_id</parameter> and <parameter>resource_metadata</parameter>. To aggregate by the chosen attributes, specify them in the configuration and set which value of the attribute to take for the new sample (first to take the first samples attribute, last to take the last samples attribute, and drop to discard the attribute)."
msgstr ""
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:660(para)
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:663(para)
msgid "To aggregate 60s worth of samples by <parameter>resource_metadata</parameter> and keep the <parameter>resource_metadata</parameter> of the latest received sample:"
msgstr ""
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:668(para)
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:671(para)
msgid "To aggregate each 15 samples by <parameter>user_id</parameter> and <parameter>resource_metadata </parameter> and keep the <parameter>user_id</parameter> of the first received sample and drop the <parameter>resource_metadata</parameter>:"
msgstr ""
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:679(title)
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:682(title)
msgid "Accumulator transformer"
msgstr ""
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:680(para)
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:683(para)
msgid "This transformer simply caches the samples until enough samples have arrived and then flushes them all down the pipeline at once."
msgstr ""
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:688(title)
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:691(title)
msgid "Multi meter arithmetic transformer"
msgstr ""
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:689(para)
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:692(para)
msgid "This transformer enables us to perform arithmetic calculations over one or more meters and/or their metadata, for example:"
msgstr ""
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:692(para)
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:695(para)
msgid "A new sample is created with the properties described in the <literal>target </literal> section of the transformers configuration. The samples volume is the result of the provided expression. The calculation is performed on samples from the same resource."
msgstr ""
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:697(para)
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:700(para)
msgid "The calculation is limited to meters with the same interval."
msgstr ""
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:699(para)
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:702(para)
msgid "Example configuration:"
msgstr ""
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:708(para)
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:711(para)
msgid "To demonstrate the use of metadata, here is the implementation of a silly metric that shows average CPU time per core:"
msgstr ""
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:719(para)
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:722(para)
msgid "Expression evaluation gracefully handles NaNs and exceptions. In such a case it does not create a new sample but only logs a warning."
msgstr ""
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:727(title)
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:730(title)
msgid "Block Storage audit script setup to get notifications"
msgstr ""
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:728(para)
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:731(para)
msgid "If you want to collect OpenStack Block Storage notification on demand, you can use <placeholder-1/> from OpenStack Block Storage. This script becomes available when you install OpenStack Block Storage, so you can use it without any specific settings and you don't need to authenticate to access the data. To use it, you must run this command in the following format:"
msgstr ""
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:735(para)
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:738(para)
msgid "This script outputs what volumes or snapshots were created or deleted or existed in a given period of time and some information about these volumes or snapshots. Information about the existence and size of volumes and snapshots is store in the Telemetry module."
msgstr ""
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:740(para)
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:743(para)
msgid "Using this script via cron you can get notifications periodically, for example, every 5 minutes."
msgstr ""
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:745(title)
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:748(title)
msgid "Storing samples"
msgstr ""
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:746(para)
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:749(para)
msgid "The Telemetry module has a separate service that is responsible for persisting the data that is coming from the pollsters or received as notifications. The data is stored in a database back end, the list of supported databases can be found in <xref linkend=\"section_telemetry-supported-dbs\"/>."
msgstr ""
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:751(para)
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:754(para)
msgid "The <systemitem class=\"service\">ceilometer-collector</systemitem> service receives the samples as metering messages from the message bus of the configured AMQP service. It stores these samples without any modification in the configured back end. The service has to run on a host machine from which it has access to the database."
msgstr ""
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:755(para)
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:758(para)
msgid "Multiple <systemitem class=\"service\">ceilometer-collector</systemitem> process can be run at a time. It is also supported to start multiple worker threads per collector process. The <parameter>collector_workers</parameter> configuration option has to be modified in the <link href=\"http://docs.openstack.org/trunk/config-reference/content/ch_configuring-openstack-telemetry.html\"> collector section</link> of the <filename>ceilometer.conf</filename> configuration file."
msgstr ""
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:762(para)
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:765(para)
msgid "Using multiple workers per collector process is not recommended to be used with PostgreSQL as database back end."
msgstr ""
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:765(para)
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:768(para)
msgid "By default the time to live value (ttl) for samples is set to -1, which means that they are kept in the database forever. This can be changed by modifying the <parameter>time_to_live </parameter> parameter in <filename>ceilometer.conf</filename>. The value has to be specified in seconds and it means that every sample that based on its timestamp is older, than the specified value will be deleted from the database."
msgstr ""
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:770(para)
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:773(para)
msgid "When the samples are deleted, there are cases, when users and resources remain in the database without any corresponding sample. There is a command line script, that deletes these useless entries, which is called <systemitem class=\"service\">ceilometer-expirer</systemitem>. This script should be run periodically, for instance in a cron job, to ensure that the database is cleaned up properly."
msgstr ""
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:775(para)
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:778(para)
msgid "The level of support differs in case of the configured back end:"
msgstr ""
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:777(caption)
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:780(caption)
msgid "Time-to-live support for database back ends"
msgstr ""
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:784(td)
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:787(td)
msgid "ttl value support"
msgstr ""
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:785(systemitem) ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:796(systemitem) ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:803(systemitem) ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:814(systemitem)
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:788(systemitem) ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:799(systemitem) ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:806(systemitem) ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:817(systemitem)
msgid "ceilometer-expirer"
msgstr ""
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:785(td)
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:788(td)
msgid "<placeholder-1/> capabilities"
msgstr ""
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:792(td)
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:795(td)
msgid "MongoDB has a built-in mechanism for deleting samples that are older than the configured ttl value."
msgstr ""
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:794(td)
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:797(td)
msgid "In case of this database, only the lingering dead resource, user and project entries will be deleted by <placeholder-1/>."
msgstr ""
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:800(td)
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:803(td)
msgid "SQL-based back ends"
msgstr ""
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:801(td)
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:804(td)
msgid "The library (SQLAlchemy) that is used for accessing SQL-based back ends does not support using the ttl value."
msgstr ""
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:806(parameter)
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:809(parameter)
msgid "time_to_live"
msgstr ""
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:803(td)
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:806(td)
msgid "<placeholder-1/> has to be used for deleting both the samples and the remaining entires in other database tables. The script will delete samples based on the <placeholder-2/> value that is set in the configuration file."
msgstr ""
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:811(td)
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:814(td)
msgid "HBase does not support this functionality currently, therefore the ttl value in the configuration file is ignored."
msgstr ""
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:813(td)
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:816(td)
msgid "The samples are not deleted by using <placeholder-1/>, this functionality is not supported."
msgstr ""
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:819(td) ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:820(td)
#: ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:822(td) ./doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml:823(td)
msgid "Same case as MongoDB."
msgstr ""

View File

@ -1,7 +1,7 @@
msgid ""
msgstr ""
"Project-Id-Version: PACKAGE VERSION\n"
"POT-Creation-Date: 2014-12-15 06:10+0000\n"
"POT-Creation-Date: 2014-12-17 06:11+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"
@ -795,19 +795,19 @@ msgstr ""
msgid "A multi-site architecture is complex and has its own risks and considerations, therefore it is important to make sure when contemplating the design such an architecture that it meets the user and business requirements."
msgstr ""
#: ./doc/arch-design/multi_site/section_user_requirements_multi_site.xml:13(para) ./doc/arch-design/network_focus/section_user_requirements_network_focus.xml:42(para) ./doc/arch-design/generalpurpose/section_user_requirements_general_purpose.xml:89(para) ./doc/arch-design/compute_focus/section_user_requirements_compute_focus.xml:55(para) ./doc/arch-design/hybrid/section_user_requirements_hybrid.xml:83(para) ./doc/arch-design/massively_scalable/section_user_requirements_massively_scalable.xml:17(para) ./doc/arch-design/storage_focus/section_user_requirements_storage_focus.xml:42(para)
#: ./doc/arch-design/multi_site/section_user_requirements_multi_site.xml:13(para) ./doc/arch-design/network_focus/section_user_requirements_network_focus.xml:42(para) ./doc/arch-design/generalpurpose/section_user_requirements_general_purpose.xml:78(para) ./doc/arch-design/compute_focus/section_user_requirements_compute_focus.xml:55(para) ./doc/arch-design/hybrid/section_user_requirements_hybrid.xml:83(para) ./doc/arch-design/massively_scalable/section_user_requirements_massively_scalable.xml:17(para) ./doc/arch-design/storage_focus/section_user_requirements_storage_focus.xml:42(para)
msgid "Many jurisdictions have legislative and regulatory requirements governing the storage and management of data in cloud environments. Common areas of regulation include:"
msgstr ""
#: ./doc/arch-design/multi_site/section_user_requirements_multi_site.xml:18(para) ./doc/arch-design/network_focus/section_user_requirements_network_focus.xml:47(para) ./doc/arch-design/generalpurpose/section_user_requirements_general_purpose.xml:94(para) ./doc/arch-design/compute_focus/section_user_requirements_compute_focus.xml:60(para) ./doc/arch-design/hybrid/section_user_requirements_hybrid.xml:88(para) ./doc/arch-design/massively_scalable/section_user_requirements_massively_scalable.xml:22(para)
#: ./doc/arch-design/multi_site/section_user_requirements_multi_site.xml:18(para) ./doc/arch-design/network_focus/section_user_requirements_network_focus.xml:47(para) ./doc/arch-design/generalpurpose/section_user_requirements_general_purpose.xml:83(para) ./doc/arch-design/compute_focus/section_user_requirements_compute_focus.xml:60(para) ./doc/arch-design/hybrid/section_user_requirements_hybrid.xml:88(para) ./doc/arch-design/massively_scalable/section_user_requirements_massively_scalable.xml:22(para)
msgid "Data retention policies ensuring storage of persistent data and records management to meet data archival requirements."
msgstr ""
#: ./doc/arch-design/multi_site/section_user_requirements_multi_site.xml:23(para) ./doc/arch-design/network_focus/section_user_requirements_network_focus.xml:52(para) ./doc/arch-design/generalpurpose/section_user_requirements_general_purpose.xml:99(para) ./doc/arch-design/compute_focus/section_user_requirements_compute_focus.xml:65(para) ./doc/arch-design/hybrid/section_user_requirements_hybrid.xml:93(para) ./doc/arch-design/massively_scalable/section_user_requirements_massively_scalable.xml:27(para)
#: ./doc/arch-design/multi_site/section_user_requirements_multi_site.xml:23(para) ./doc/arch-design/network_focus/section_user_requirements_network_focus.xml:52(para) ./doc/arch-design/generalpurpose/section_user_requirements_general_purpose.xml:88(para) ./doc/arch-design/compute_focus/section_user_requirements_compute_focus.xml:65(para) ./doc/arch-design/hybrid/section_user_requirements_hybrid.xml:93(para) ./doc/arch-design/massively_scalable/section_user_requirements_massively_scalable.xml:27(para)
msgid "Data ownership policies governing the possession and responsibility for data."
msgstr ""
#: ./doc/arch-design/multi_site/section_user_requirements_multi_site.xml:27(para) ./doc/arch-design/network_focus/section_user_requirements_network_focus.xml:56(para) ./doc/arch-design/generalpurpose/section_user_requirements_general_purpose.xml:103(para) ./doc/arch-design/compute_focus/section_user_requirements_compute_focus.xml:69(para) ./doc/arch-design/hybrid/section_user_requirements_hybrid.xml:97(para) ./doc/arch-design/massively_scalable/section_user_requirements_massively_scalable.xml:31(para)
#: ./doc/arch-design/multi_site/section_user_requirements_multi_site.xml:27(para) ./doc/arch-design/network_focus/section_user_requirements_network_focus.xml:56(para) ./doc/arch-design/generalpurpose/section_user_requirements_general_purpose.xml:92(para) ./doc/arch-design/compute_focus/section_user_requirements_compute_focus.xml:69(para) ./doc/arch-design/hybrid/section_user_requirements_hybrid.xml:97(para) ./doc/arch-design/massively_scalable/section_user_requirements_massively_scalable.xml:31(para)
msgid "Data sovereignty policies governing the storage of data in foreign countries or otherwise separate jurisdictions."
msgstr ""
@ -883,7 +883,7 @@ msgstr ""
msgid "Some applications are tolerant of the lack of synchronized object storage, while others may need those objects to be replicated and available across regions. Understanding of how the cloud implementation impacts new and existing applications is important for risk mitigation and the overall success of a cloud project. Applications may have to be written to expect an infrastructure with little to no redundancy. Existing applications not developed with the cloud in mind may need to be rewritten."
msgstr ""
#: ./doc/arch-design/multi_site/section_user_requirements_multi_site.xml:139(title) ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:103(term) ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:263(term) ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:587(term) ./doc/arch-design/generalpurpose/section_user_requirements_general_purpose.xml:25(term) ./doc/arch-design/compute_focus/section_user_requirements_compute_focus.xml:20(term) ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:55(term) ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:174(term) ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:396(term) ./doc/arch-design/hybrid/section_user_requirements_hybrid.xml:19(term) ./doc/arch-design/storage_focus/section_architecture_storage_focus.xml:16(para) ./doc/arch-design/storage_focus/section_architecture_storage_focus.xml:40(term) ./doc/arch-design/storage_focus/section_architecture_storage_focus.xml:184(term) ./doc/arch-design/storage_focus/section_architecture_storage_focus.xml:417(term) ./doc/arch-design/storage_focus/section_user_requirements_storage_focus.xml:16(term)
#: ./doc/arch-design/multi_site/section_user_requirements_multi_site.xml:139(title) ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:103(term) ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:263(term) ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:587(term) ./doc/arch-design/generalpurpose/section_user_requirements_general_purpose.xml:24(term) ./doc/arch-design/compute_focus/section_user_requirements_compute_focus.xml:20(term) ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:55(term) ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:174(term) ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:396(term) ./doc/arch-design/hybrid/section_user_requirements_hybrid.xml:19(term) ./doc/arch-design/storage_focus/section_architecture_storage_focus.xml:16(para) ./doc/arch-design/storage_focus/section_architecture_storage_focus.xml:40(term) ./doc/arch-design/storage_focus/section_architecture_storage_focus.xml:184(term) ./doc/arch-design/storage_focus/section_architecture_storage_focus.xml:417(term) ./doc/arch-design/storage_focus/section_user_requirements_storage_focus.xml:16(term)
msgid "Cost"
msgstr ""
@ -1025,11 +1025,11 @@ msgstr ""
msgid "As of late there has been several outages in number of major public cloud providersusually due to the fact these applications were running out of a single geographical location. The design therefore should mitigate the chance of a single site causing an outage for their business."
msgstr ""
#: ./doc/arch-design/multi_site/section_prescriptive_examples_multi_site.xml:102(para) ./doc/arch-design/generalpurpose/section_prescriptive_example_general_purpose.xml:32(para)
#: ./doc/arch-design/multi_site/section_prescriptive_examples_multi_site.xml:102(para) ./doc/arch-design/generalpurpose/section_prescriptive_example_general_purpose.xml:30(para)
msgid "The solution would consist of the following OpenStack components:"
msgstr ""
#: ./doc/arch-design/multi_site/section_prescriptive_examples_multi_site.xml:106(para) ./doc/arch-design/generalpurpose/section_prescriptive_example_general_purpose.xml:36(para)
#: ./doc/arch-design/multi_site/section_prescriptive_examples_multi_site.xml:106(para) ./doc/arch-design/generalpurpose/section_prescriptive_example_general_purpose.xml:34(para)
msgid "A firewall, switches and load balancers on the public facing network connections."
msgstr ""
@ -1037,7 +1037,7 @@ msgstr ""
msgid "OpenStack Controller services running, Networking, dashboard, Block Storage and Compute running locally in each of the three regions. The other services, Identity, Orchestration, Telemetry, Image Service and Object Storage will be installed centrallywith nodes in each of the region providing a redundant OpenStack Controller plane throughout the globe."
msgstr ""
#: ./doc/arch-design/multi_site/section_prescriptive_examples_multi_site.xml:120(para) ./doc/arch-design/generalpurpose/section_prescriptive_example_general_purpose.xml:47(para)
#: ./doc/arch-design/multi_site/section_prescriptive_examples_multi_site.xml:120(para) ./doc/arch-design/generalpurpose/section_prescriptive_example_general_purpose.xml:44(para)
msgid "OpenStack Compute nodes running the KVM hypervisor."
msgstr ""
@ -1157,7 +1157,7 @@ msgstr ""
msgid "Depending on the storage model chosen during site design, storage replication and availability will also be a concern for end-users. If an application is capable of understanding regions, then it is possible to keep the object storage system separated by region. In this case, users who want to have an object available to more than one region will need to do the cross-site replication themselves. With a centralized swift proxy, however, the user may need to benchmark the replication timing of the Object Storage back end. Benchmarking allows the operational staff to provide users with an understanding of the amount of time required for a stored or modified object to become available to the entire environment."
msgstr ""
#: ./doc/arch-design/multi_site/section_tech_considerations_multi_site.xml:114(title) ./doc/arch-design/network_focus/section_tech_considerations_network_focus.xml:432(title) ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:391(term) ./doc/arch-design/generalpurpose/section_user_requirements_general_purpose.xml:131(term) ./doc/arch-design/generalpurpose/section_tech_considerations_general_purpose.xml:493(title) ./doc/arch-design/compute_focus/section_user_requirements_compute_focus.xml:96(term) ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:182(term) ./doc/arch-design/compute_focus/section_tech_considerations_compute_focus.xml:257(title) ./doc/arch-design/hybrid/section_tech_considerations_hybrid.xml:253(title) ./doc/arch-design/storage_focus/section_architecture_storage_focus.xml:19(para) ./doc/arch-design/storage_focus/section_architecture_storage_focus.xml:48(term) ./doc/arch-design/storage_focus/section_user_requirements_storage_focus.xml:105(term)
#: ./doc/arch-design/multi_site/section_tech_considerations_multi_site.xml:114(title) ./doc/arch-design/network_focus/section_tech_considerations_network_focus.xml:432(title) ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:391(term) ./doc/arch-design/generalpurpose/section_user_requirements_general_purpose.xml:120(term) ./doc/arch-design/generalpurpose/section_tech_considerations_general_purpose.xml:493(title) ./doc/arch-design/compute_focus/section_user_requirements_compute_focus.xml:96(term) ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:182(term) ./doc/arch-design/compute_focus/section_tech_considerations_compute_focus.xml:257(title) ./doc/arch-design/hybrid/section_tech_considerations_hybrid.xml:253(title) ./doc/arch-design/storage_focus/section_architecture_storage_focus.xml:19(para) ./doc/arch-design/storage_focus/section_architecture_storage_focus.xml:48(term) ./doc/arch-design/storage_focus/section_user_requirements_storage_focus.xml:105(term)
msgid "Performance"
msgstr ""
@ -1173,7 +1173,7 @@ msgstr ""
msgid "Storage availability can also be impacted by the architecture of a multi-site deployment. A centralized Object Storage service requires more time for an object to be available to instances locally in regions where the object was not created. Some applications may need to be tuned to account for this effect. Block Storage does not currently have a method for replicating data across multiple regions, so applications that depend on available block storage will need to manually cope with this limitation by creating duplicate block storage entries in each region."
msgstr ""
#: ./doc/arch-design/multi_site/section_tech_considerations_multi_site.xml:139(title) ./doc/arch-design/network_focus/section_user_requirements_network_focus.xml:163(title) ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:634(term) ./doc/arch-design/generalpurpose/section_user_requirements_general_purpose.xml:200(term) ./doc/arch-design/generalpurpose/section_tech_considerations_general_purpose.xml:671(title) ./doc/arch-design/compute_focus/section_user_requirements_compute_focus.xml:160(term) ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:440(term) ./doc/arch-design/compute_focus/section_tech_considerations_compute_focus.xml:268(title) ./doc/arch-design/hybrid/section_tech_considerations_hybrid.xml:107(title) ./doc/arch-design/storage_focus/section_tech_considerations_storage_focus.xml:50(term) ./doc/arch-design/storage_focus/section_architecture_storage_focus.xml:471(term) ./doc/arch-design/storage_focus/section_user_requirements_storage_focus.xml:123(term)
#: ./doc/arch-design/multi_site/section_tech_considerations_multi_site.xml:139(title) ./doc/arch-design/network_focus/section_user_requirements_network_focus.xml:163(title) ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:634(term) ./doc/arch-design/generalpurpose/section_user_requirements_general_purpose.xml:191(term) ./doc/arch-design/generalpurpose/section_tech_considerations_general_purpose.xml:671(title) ./doc/arch-design/compute_focus/section_user_requirements_compute_focus.xml:160(term) ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:440(term) ./doc/arch-design/compute_focus/section_tech_considerations_compute_focus.xml:268(title) ./doc/arch-design/hybrid/section_tech_considerations_hybrid.xml:107(title) ./doc/arch-design/storage_focus/section_tech_considerations_storage_focus.xml:50(term) ./doc/arch-design/storage_focus/section_architecture_storage_focus.xml:471(term) ./doc/arch-design/storage_focus/section_user_requirements_storage_focus.xml:123(term)
msgid "Security"
msgstr ""
@ -2426,90 +2426,98 @@ msgid "Storage focused OpenStack clouds need to be designed to accommodate workl
msgstr ""
#: ./doc/arch-design/generalpurpose/section_user_requirements_general_purpose.xml:9(para)
msgid "The general purpose cloud is built following the <glossterm baseform=\"IaaS\">Infrastructure-as-a-Service (IaaS)</glossterm> model; as a platform best suited for use cases with simple requirements. The general purpose cloud user requirements themselves are typically not complex. However, it is still important to capture them even if the project has minimum business and technical requirements such as a proof of concept (PoC) or a small lab platform."
msgid "When building a general purpose cloud, you should follow the <glossterm baseform=\"IaaS\">Infrastructure-as-a-Service (IaaS)</glossterm> model; a platform best suited for use cases with simple requirements. General purpose cloud user requirements are not complex. However, it is important to capture them even if the project has minimum business and technical requirements, such as a proof of concept (PoC), or a small lab platform."
msgstr ""
#: ./doc/arch-design/generalpurpose/section_user_requirements_general_purpose.xml:18(para)
msgid "These user considerations are written from the perspective of the organization that is building the cloud, not from the perspective of the end-users who will consume cloud services provided by this design."
#: ./doc/arch-design/generalpurpose/section_user_requirements_general_purpose.xml:17(para)
msgid "The following user considerations are written from the perspective of the cloud builder, not from the perspective of the end user."
msgstr ""
#: ./doc/arch-design/generalpurpose/section_user_requirements_general_purpose.xml:27(para)
msgid "Financial factors are a primary concern for any organization. Since general purpose clouds are considered the baseline from which all other cloud architecture environments derive, cost will commonly be an important criteria. This type of cloud, however, does not always provide the most cost-effective environment for a specialized application or situation. Unless razor-thin margins and costs have been mandated as a critical factor, cost should not be the sole consideration when choosing or designing a general purpose architecture."
#: ./doc/arch-design/generalpurpose/section_user_requirements_general_purpose.xml:26(para)
msgid "Financial factors are a primary concern for any organization. Cost is an important criterion as general purpose clouds are considered the baseline from which all other cloud architecture environments derive. General purpose cloud do not always provide the most cost-effective environment for specialized applications or situations. Unless razor-thin margins and costs have been mandated as a critical factor, cost should not be the sole consideration when choosing or designing a general purpose architecture."
msgstr ""
#: ./doc/arch-design/generalpurpose/section_user_requirements_general_purpose.xml:41(term) ./doc/arch-design/compute_focus/section_user_requirements_compute_focus.xml:31(term) ./doc/arch-design/hybrid/section_user_requirements_hybrid.xml:46(term)
#: ./doc/arch-design/generalpurpose/section_user_requirements_general_purpose.xml:39(term) ./doc/arch-design/compute_focus/section_user_requirements_compute_focus.xml:31(term) ./doc/arch-design/hybrid/section_user_requirements_hybrid.xml:46(term)
msgid "Time to market"
msgstr ""
#: ./doc/arch-design/generalpurpose/section_user_requirements_general_purpose.xml:43(para)
msgid "Another common business factor in building a general purpose cloud is the ability to deliver a service or product more quickly and flexibly. In the modern hyper-fast business world, being able to deliver a product in six months instead of two years is often a major driving force behind the decision to build a general purpose cloud. General purpose clouds allow users to self-provision and gain access to compute, network, and storage resources on-demand thus decreasing time to market. It may potentially make more sense to build a general purpose PoC as opposed to waiting to finalize the ultimate use case for the system. The tradeoff with taking this approach is the risk that the general purpose cloud is not optimized for the actual final workloads. The final decision on which approach to take will be dependent on the specifics of the business objectives and time frame for the project."
#: ./doc/arch-design/generalpurpose/section_user_requirements_general_purpose.xml:41(para)
msgid "The ability to deliver services or products within a flexible time frame is a common business factor when building a general purpose cloud. In today's high-speed business world, the ability to deliver a product in six months instead of two years is a driving force behind the decision to build general purpose clouds. General purpose clouds allow users to self-provision and gain access to compute, network, and storage resources on-demand thus decreasing time to market."
msgstr ""
#: ./doc/arch-design/generalpurpose/section_user_requirements_general_purpose.xml:64(term) ./doc/arch-design/compute_focus/section_user_requirements_compute_focus.xml:40(term) ./doc/arch-design/hybrid/section_user_requirements_hybrid.xml:33(term)
#: ./doc/arch-design/generalpurpose/section_user_requirements_general_purpose.xml:53(term) ./doc/arch-design/compute_focus/section_user_requirements_compute_focus.xml:40(term) ./doc/arch-design/hybrid/section_user_requirements_hybrid.xml:33(term)
msgid "Revenue opportunity"
msgstr ""
#: ./doc/arch-design/generalpurpose/section_user_requirements_general_purpose.xml:66(para)
msgid "The revenue opportunity for a given cloud will vary greatly based on the intended use case of that particular cloud. Some general purpose clouds are built for commercial customer facing products, but there are plenty of other reasons that might make the general purpose cloud the right choice. A small cloud service provider (CSP) might want to build a general purpose cloud rather than a massively scalable cloud because they do not have the deep financial resources needed, or because they do not or will not know in advance the purposes for which their customers are going to use the cloud. For some users, the advantages cloud itself offers mean an enhancement of revenue opportunity. For others, the fact that a general purpose cloud provides only baseline functionality will be a disincentive for use, leading to a potential stagnation of potential revenue opportunities."
#: ./doc/arch-design/generalpurpose/section_user_requirements_general_purpose.xml:55(para)
msgid "Revenue opportunities for a cloud will vary greatly based on the intended use case of that particular cloud. Some general purpose clouds are built for commercial customer facing products, but there are alternatives that might make the general purpose cloud the right choice. For example, a small cloud service provider (CSP) might want to build a general purpose cloud rather than a massively scalable cloud because they do not have the deep financial resources needed, or because they do not, or will not, know in advance the purposes for which their customers are going to use the cloud. For some users, the advantages cloud itself offers mean an enhancement of revenue opportunity. For others, the fact that a general purpose cloud provides only baseline functionality will be a disincentive for use, leading to a potential stagnation of potential revenue opportunities."
msgstr ""
#: ./doc/arch-design/generalpurpose/section_user_requirements_general_purpose.xml:88(title) ./doc/arch-design/compute_focus/section_user_requirements_compute_focus.xml:54(title) ./doc/arch-design/hybrid/section_user_requirements_hybrid.xml:82(title) ./doc/arch-design/storage_focus/section_user_requirements_storage_focus.xml:30(term) ./doc/arch-design/storage_focus/section_user_requirements_storage_focus.xml:41(title)
#: ./doc/arch-design/generalpurpose/section_user_requirements_general_purpose.xml:77(title) ./doc/arch-design/compute_focus/section_user_requirements_compute_focus.xml:54(title) ./doc/arch-design/hybrid/section_user_requirements_hybrid.xml:82(title) ./doc/arch-design/storage_focus/section_user_requirements_storage_focus.xml:30(term) ./doc/arch-design/storage_focus/section_user_requirements_storage_focus.xml:41(title)
msgid "Legal requirements"
msgstr ""
#: ./doc/arch-design/generalpurpose/section_user_requirements_general_purpose.xml:108(para)
msgid "Data compliance policies governing certain types of information need to reside in certain locations due to regular issues - and more important cannot reside in other locations for the same reason."
#: ./doc/arch-design/generalpurpose/section_user_requirements_general_purpose.xml:97(para)
msgid "Data compliance policies governing certain types of information needing to reside in certain locations due to regular issues - and more importantly, cannot reside in other locations for the same reason."
msgstr ""
#: ./doc/arch-design/generalpurpose/section_user_requirements_general_purpose.xml:114(para) ./doc/arch-design/compute_focus/section_user_requirements_compute_focus.xml:80(para) ./doc/arch-design/massively_scalable/section_user_requirements_massively_scalable.xml:42(para) ./doc/arch-design/storage_focus/section_user_requirements_storage_focus.xml:79(para)
#: ./doc/arch-design/generalpurpose/section_user_requirements_general_purpose.xml:103(para) ./doc/arch-design/compute_focus/section_user_requirements_compute_focus.xml:80(para) ./doc/arch-design/massively_scalable/section_user_requirements_massively_scalable.xml:42(para) ./doc/arch-design/storage_focus/section_user_requirements_storage_focus.xml:79(para)
msgid "Examples of such legal frameworks include the <link href=\"http://ec.europa.eu/justice/data-protection/\">data protection framework</link> of the European Union and the requirements of the <link href=\"http://www.finra.org/Industry/Regulation/FINRARules/\">Financial Industry Regulatory Authority</link> in the United States. Consult a local regulatory body for more information."
msgstr ""
#: ./doc/arch-design/generalpurpose/section_user_requirements_general_purpose.xml:125(title) ./doc/arch-design/storage_focus/section_user_requirements_storage_focus.xml:90(title)
#: ./doc/arch-design/generalpurpose/section_user_requirements_general_purpose.xml:114(title) ./doc/arch-design/storage_focus/section_user_requirements_storage_focus.xml:90(title)
msgid "Technical requirements"
msgstr ""
#: ./doc/arch-design/generalpurpose/section_user_requirements_general_purpose.xml:126(para)
#: ./doc/arch-design/generalpurpose/section_user_requirements_general_purpose.xml:115(para)
msgid "Technical cloud architecture requirements should be weighted against the business requirements."
msgstr ""
#: ./doc/arch-design/generalpurpose/section_user_requirements_general_purpose.xml:133(para)
#: ./doc/arch-design/generalpurpose/section_user_requirements_general_purpose.xml:122(para)
msgid "As a baseline product, general purpose clouds do not provide optimized performance for any particular function. While a general purpose cloud should provide enough performance to satisfy average user considerations, performance is not a general purpose cloud customer driver."
msgstr ""
#: ./doc/arch-design/generalpurpose/section_user_requirements_general_purpose.xml:142(term)
#: ./doc/arch-design/generalpurpose/section_user_requirements_general_purpose.xml:131(term)
msgid "No predefined usage model"
msgstr ""
#: ./doc/arch-design/generalpurpose/section_user_requirements_general_purpose.xml:144(para)
#: ./doc/arch-design/generalpurpose/section_user_requirements_general_purpose.xml:133(para)
msgid "The lack of a pre-defined usage model enables the user to run a wide variety of applications without having to know the application requirements in advance. This provides a degree of independence and flexibility that no other cloud scenarios are able to provide."
msgstr ""
#: ./doc/arch-design/generalpurpose/section_user_requirements_general_purpose.xml:153(term)
#: ./doc/arch-design/generalpurpose/section_user_requirements_general_purpose.xml:142(term)
msgid "On-demand and self-service application"
msgstr ""
#: ./doc/arch-design/generalpurpose/section_user_requirements_general_purpose.xml:155(para)
#: ./doc/arch-design/generalpurpose/section_user_requirements_general_purpose.xml:144(para)
msgid "By definition, a cloud provides end users with the ability to self-provision computing power, storage, networks, and software in a simple and flexible way. The user must be able to scale their resources up to a substantial level without disrupting the underlying host operations. One of the benefits of using a general purpose cloud architecture is the ability to start with limited resources and increase them over time as the user demand grows."
msgstr ""
#: ./doc/arch-design/generalpurpose/section_user_requirements_general_purpose.xml:168(term)
#: ./doc/arch-design/generalpurpose/section_user_requirements_general_purpose.xml:157(term)
msgid "Public cloud"
msgstr ""
#: ./doc/arch-design/generalpurpose/section_user_requirements_general_purpose.xml:170(para)
msgid "For a company interested in building a commercial public cloud offering based on OpenStack, the general purpose architecture model might be the best choice because the designers are not going to know the purposes or workloads for which the end users will use the cloud."
#: ./doc/arch-design/generalpurpose/section_user_requirements_general_purpose.xml:159(para)
msgid "For a company interested in building a commercial public cloud offering based on OpenStack, the general purpose architecture model might be the best choice. Designers are not always going to know the purposes or workloads for which the end users will use the cloud."
msgstr ""
#: ./doc/arch-design/generalpurpose/section_user_requirements_general_purpose.xml:179(term)
#: ./doc/arch-design/generalpurpose/section_user_requirements_general_purpose.xml:168(term)
msgid "Internal consumption (private) cloud"
msgstr ""
#: ./doc/arch-design/generalpurpose/section_user_requirements_general_purpose.xml:181(para)
msgid "Organizations need to determine if it makes the most sense to create their own clouds internally. The main advantage of a private cloud is that it allows the organization to maintain complete control over all the architecture and the cloud components. One caution is to think about the possibility that users will want to combine using the internal cloud with access to an external cloud. If that case is likely, it might be worth exploring the possibility of taking a multi-cloud approach with regard to at least some of the architectural elements. Designs that incorporate the use of multiple clouds, such as a private cloud and a public cloud offering, are described in the \"Multi-Cloud\" scenario, see <xref linkend=\"multi_site\"/>."
#: ./doc/arch-design/generalpurpose/section_user_requirements_general_purpose.xml:170(para)
msgid "Organizations need to determine if it is logical to create their own clouds internally. Using private cloud, organizations are able to maintain complete control over the architectural and cloud components."
msgstr ""
#: ./doc/arch-design/generalpurpose/section_user_requirements_general_purpose.xml:202(para)
#: ./doc/arch-design/generalpurpose/section_user_requirements_general_purpose.xml:175(para)
msgid "Users will want to combine using the internal cloud with access to an external cloud. If that case is likely, it might be worth exploring the possibility of taking a multi-cloud approach with regard to at least some of the architectural elements."
msgstr ""
#: ./doc/arch-design/generalpurpose/section_user_requirements_general_purpose.xml:183(para)
msgid "Designs that incorporate the use of multiple clouds, such as a private cloud and a public cloud offering, are described in the \"Multi-Cloud\" scenario, see <xref linkend=\"multi_site\"/>."
msgstr ""
#: ./doc/arch-design/generalpurpose/section_user_requirements_general_purpose.xml:193(para)
msgid "Security should be implemented according to asset, threat, and vulnerability risk assessment matrices. For cloud domains that require increased computer security, network security, or information security, general purpose cloud is not considered an appropriate choice."
msgstr ""
@ -2635,7 +2643,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/arch-design/generalpurpose/section_prescriptive_example_general_purpose.xml:62(None)
#: ./doc/arch-design/generalpurpose/section_prescriptive_example_general_purpose.xml:59(None)
msgid "@@image: '../images/General_Architecture3.png'; md5=278d469e1d026634b3682209c454bff1"
msgstr ""
@ -2644,59 +2652,63 @@ msgid "Prescriptive example"
msgstr ""
#: ./doc/arch-design/generalpurpose/section_prescriptive_example_general_purpose.xml:9(para)
msgid "An online classified advertising company wants to run web applications consisting of Tomcat, Nginx and MariaDB in a private cloud. In order to meet policy requirements, the cloud infrastructure will run in their own data center. They have predictable load requirements but require an element of scaling to cope with nightly increases in demand. Their current environment is not flexible enough to align with their goal of running an open source API driven environment. Their current environment consists of the following:"
msgid "An online classified advertising company wants to run web applications consisting of Tomcat, Nginx and MariaDB in a private cloud. To be able to meet policy requirements, the cloud infrastructure will run in their own data center. The company has predictable load requirements, but requires scaling to cope with nightly increases in demand. Their current environment does not have the flexibility to align with their goal of running an open source API environment. The current environment consists of the following:"
msgstr ""
#: ./doc/arch-design/generalpurpose/section_prescriptive_example_general_purpose.xml:19(para)
#: ./doc/arch-design/generalpurpose/section_prescriptive_example_general_purpose.xml:18(para)
msgid "Between 120 and 140 installations of Nginx and Tomcat, each with 2 vCPUs and 4 GB of RAM"
msgstr ""
#: ./doc/arch-design/generalpurpose/section_prescriptive_example_general_purpose.xml:23(para)
#: ./doc/arch-design/generalpurpose/section_prescriptive_example_general_purpose.xml:22(para)
msgid "A three-node MariaDB and Galera cluster, each with 4 vCPUs and 8 GB RAM"
msgstr ""
#: ./doc/arch-design/generalpurpose/section_prescriptive_example_general_purpose.xml:27(para)
msgid "The company runs hardware load balancers and multiple web applications serving the sites. The company orchestrates their environment using a combination of scripts and Puppet. The websites generate a large amount of log data each day that needs to be archived."
#: ./doc/arch-design/generalpurpose/section_prescriptive_example_general_purpose.xml:26(para)
msgid "The company runs hardware load balancers and multiple web applications serving their websites, and orchestrates environments using combinations of scripts and Puppet. The website generates large amounts of log data daily that requires archiving."
msgstr ""
#: ./doc/arch-design/generalpurpose/section_prescriptive_example_general_purpose.xml:40(para)
msgid "OpenStack Controller services running Image, Identity, Networking and supporting services such as MariaDB and RabbitMQ. The controllers will run in a highly available configuration on at least three controller nodes."
#: ./doc/arch-design/generalpurpose/section_prescriptive_example_general_purpose.xml:38(para)
msgid "OpenStack Controller service running Image, Identity, Networking, combined with support services such as MariaDB and RabbitMQ, configured for high availability on at least three controller nodes."
msgstr ""
#: ./doc/arch-design/generalpurpose/section_prescriptive_example_general_purpose.xml:51(para)
msgid "OpenStack Block Storage for use by compute instances that require persistent storage such as databases for dynamic sites."
#: ./doc/arch-design/generalpurpose/section_prescriptive_example_general_purpose.xml:48(para)
msgid "OpenStack Block Storage for use by compute instances, requiring persistent storage (such as databases for dynamic sites)."
msgstr ""
#: ./doc/arch-design/generalpurpose/section_prescriptive_example_general_purpose.xml:56(para)
msgid "OpenStack Object Storage for serving static objects such as images."
#: ./doc/arch-design/generalpurpose/section_prescriptive_example_general_purpose.xml:53(para)
msgid "OpenStack Object Storage for serving static objects (such as images)."
msgstr ""
#: ./doc/arch-design/generalpurpose/section_prescriptive_example_general_purpose.xml:63(para)
#: ./doc/arch-design/generalpurpose/section_prescriptive_example_general_purpose.xml:60(para)
msgid "Running up to 140 web instances and the small number of MariaDB instances requires 292 vCPUs available, as well as 584 GB RAM. On a typical 1U server using dual-socket hex-core Intel CPUs with Hyperthreading, and assuming 2:1 CPU overcommit ratio, this would require 8 OpenStack Compute nodes."
msgstr ""
#: ./doc/arch-design/generalpurpose/section_prescriptive_example_general_purpose.xml:69(para)
#: ./doc/arch-design/generalpurpose/section_prescriptive_example_general_purpose.xml:66(para)
msgid "The web application instances run from local storage on each of the OpenStack Compute nodes. The web application instances are stateless, meaning that any of the instances can fail and the application will continue to function."
msgstr ""
#: ./doc/arch-design/generalpurpose/section_prescriptive_example_general_purpose.xml:73(para)
#: ./doc/arch-design/generalpurpose/section_prescriptive_example_general_purpose.xml:70(para)
msgid "MariaDB server instances store their data on shared enterprise storage, such as NetApp or Solidfire devices. If a MariaDB instance fails, storage would be expected to be re-attached to another instance and rejoined to the Galera cluster."
msgstr ""
#: ./doc/arch-design/generalpurpose/section_prescriptive_example_general_purpose.xml:75(para)
msgid "Logs from the web application servers are shipped to OpenStack Object Storage for processing and archiving."
msgstr ""
#: ./doc/arch-design/generalpurpose/section_prescriptive_example_general_purpose.xml:78(para)
msgid "Logs from the web application servers are shipped to OpenStack Object Storage for later processing and archiving."
msgid "Additional capabilities can be realized by moving static web content to be served from OpenStack Object Storage containers, and backing the OpenStack Image Service with OpenStack Object Storage."
msgstr ""
#: ./doc/arch-design/generalpurpose/section_prescriptive_example_general_purpose.xml:81(para)
msgid "In this scenario, additional capabilities can be realized by moving static web content to be served from OpenStack Object Storage containers, and backing the OpenStack Image Service with OpenStack Object Storage. Note that an increase in OpenStack Object Storage means that network bandwidth needs to be taken in to consideration. It is best to run OpenStack Object Storage with network connections offering 10 GbE or better connectivity."
#: ./doc/arch-design/generalpurpose/section_prescriptive_example_general_purpose.xml:83(para)
msgid "Increasing OpenStack Object Storage means network bandwidth needs to be taken into consideration. Running OpenStack Object Storage with network connections offering 10 GbE or better connectivity is advised."
msgstr ""
#: ./doc/arch-design/generalpurpose/section_prescriptive_example_general_purpose.xml:89(para)
msgid "There is also a potential to leverage the Orchestration and Telemetry modules to provide an auto-scaling, orchestrated web application environment. Defining the web applications in <glossterm baseform=\"Heat Orchestration Template (HOT)\">Heat Orchestration Templates (HOT)</glossterm> would negate the reliance on the scripted Puppet solution currently employed."
#: ./doc/arch-design/generalpurpose/section_prescriptive_example_general_purpose.xml:90(para)
msgid "Leveraging Orchestration and Telemetry modules is also a potential issue when providing auto-scaling, orchestrated web application environments. Defining the web applications in <glossterm baseform=\"Heat Orchestration Template (HOT)\">Heat Orchestration Templates (HOT)</glossterm> negates the reliance on the current scripted Puppet solution."
msgstr ""
#: ./doc/arch-design/generalpurpose/section_prescriptive_example_general_purpose.xml:97(para)
msgid "OpenStack Networking can be used to control hardware load balancers through the use of plug-ins and the Networking API. This would allow a user to control hardware load balance pools and instances as members in these pools, but their use in production environments must be carefully weighed against current stability."
#: ./doc/arch-design/generalpurpose/section_prescriptive_example_general_purpose.xml:95(para)
msgid "OpenStack Networking can be used to control hardware load balancers through the use of plug-ins and the Networking API. This allows users to control hardware load balance pools and instances as members in these pools, but their use in production environments must be carefully weighed against current stability."
msgstr ""
#: ./doc/arch-design/generalpurpose/section_tech_considerations_general_purpose.xml:13(para)

File diff suppressed because one or more lines are too long

View File

@ -1,7 +1,7 @@
msgid ""
msgstr ""
"Project-Id-Version: PACKAGE VERSION\n"
"POT-Creation-Date: 2014-12-15 06:10+0000\n"
"POT-Creation-Date: 2014-12-17 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"
@ -9415,7 +9415,7 @@ msgstr ""
msgid "(StrOpt) Policy backend driver."
msgstr ""
#: ./doc/common/tables/keystone-policy.xml:36(td) ./doc/common/tables/keystone-api.xml:49(td) ./doc/common/tables/keystone-identity.xml:37(td) ./doc/common/tables/keystone-catalog.xml:37(td) ./doc/common/tables/keystone-assignment.xml:33(td)
#: ./doc/common/tables/keystone-policy.xml:36(td) ./doc/common/tables/keystone-api.xml:49(td) ./doc/common/tables/keystone-identity.xml:37(td) ./doc/common/tables/keystone-catalog.xml:33(td) ./doc/common/tables/keystone-assignment.xml:33(td)
msgid "list_limit = None"
msgstr ""
@ -13663,23 +13663,15 @@ msgstr ""
msgid "(StrOpt) Catalog backend driver."
msgstr ""
#: ./doc/common/tables/keystone-catalog.xml:33(td)
msgid "endpoint_substitution_whitelist = tenant_id, user_id, public_bind_host, admin_bind_host, compute_host, compute_port, admin_port, public_port, public_endpoint, admin_endpoint"
msgstr ""
#: ./doc/common/tables/keystone-catalog.xml:34(td)
msgid "(ListOpt) (Deprecated) List of possible substitutions for use in formatting endpoints. Use caution when modifying this list. It will give users with permission to create endpoints the ability to see those values in your configuration file. This option will be removed in Juno."
msgstr ""
#: ./doc/common/tables/keystone-catalog.xml:38(td)
msgid "(IntOpt) Maximum number of entities that will be returned in a catalog collection."
msgstr ""
#: ./doc/common/tables/keystone-catalog.xml:41(td)
#: ./doc/common/tables/keystone-catalog.xml:37(td)
msgid "template_file = default_catalog.templates"
msgstr ""
#: ./doc/common/tables/keystone-catalog.xml:42(td)
#: ./doc/common/tables/keystone-catalog.xml:38(td)
msgid "(StrOpt) Catalog template file name for use with the template catalog backend."
msgstr ""

View File

@ -19,8 +19,8 @@
msgid ""
msgstr ""
"Project-Id-Version: OpenStack Manuals\n"
"POT-Creation-Date: 2014-12-15 00:16+0000\n"
"PO-Revision-Date: 2014-12-15 00:30+0000\n"
"POT-Creation-Date: 2014-12-17 04:36+0000\n"
"PO-Revision-Date: 2014-12-17 04:37+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"
@ -15026,7 +15026,7 @@ msgstr ""
#: ./doc/common/tables/keystone-policy.xml36(td)
#: ./doc/common/tables/keystone-api.xml49(td)
#: ./doc/common/tables/keystone-identity.xml37(td)
#: ./doc/common/tables/keystone-catalog.xml37(td)
#: ./doc/common/tables/keystone-catalog.xml33(td)
#: ./doc/common/tables/keystone-assignment.xml33(td)
msgid "list_limit = None"
msgstr ""
@ -22656,32 +22656,17 @@ msgstr ""
msgid "(StrOpt) Catalog backend driver."
msgstr ""
#: ./doc/common/tables/keystone-catalog.xml33(td)
msgid ""
"endpoint_substitution_whitelist = tenant_id, user_id, public_bind_host, "
"admin_bind_host, compute_host, compute_port, admin_port, public_port, "
"public_endpoint, admin_endpoint"
msgstr ""
#: ./doc/common/tables/keystone-catalog.xml34(td)
msgid ""
"(ListOpt) (Deprecated) List of possible substitutions for use in formatting "
"endpoints. Use caution when modifying this list. It will give users with "
"permission to create endpoints the ability to see those values in your "
"configuration file. This option will be removed in Juno."
msgstr ""
#: ./doc/common/tables/keystone-catalog.xml38(td)
msgid ""
"(IntOpt) Maximum number of entities that will be returned in a catalog "
"collection."
msgstr ""
#: ./doc/common/tables/keystone-catalog.xml41(td)
#: ./doc/common/tables/keystone-catalog.xml37(td)
msgid "template_file = default_catalog.templates"
msgstr ""
#: ./doc/common/tables/keystone-catalog.xml42(td)
#: ./doc/common/tables/keystone-catalog.xml38(td)
msgid ""
"(StrOpt) Catalog template file name for use with the template catalog "
"backend."

View File

@ -7,8 +7,8 @@
msgid ""
msgstr ""
"Project-Id-Version: OpenStack Manuals\n"
"POT-Creation-Date: 2014-12-15 00:16+0000\n"
"PO-Revision-Date: 2014-12-15 00:30+0000\n"
"POT-Creation-Date: 2014-12-17 04:36+0000\n"
"PO-Revision-Date: 2014-12-17 04:37+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"
@ -15014,7 +15014,7 @@ msgstr ""
#: ./doc/common/tables/keystone-policy.xml36(td)
#: ./doc/common/tables/keystone-api.xml49(td)
#: ./doc/common/tables/keystone-identity.xml37(td)
#: ./doc/common/tables/keystone-catalog.xml37(td)
#: ./doc/common/tables/keystone-catalog.xml33(td)
#: ./doc/common/tables/keystone-assignment.xml33(td)
msgid "list_limit = None"
msgstr ""
@ -22644,32 +22644,17 @@ msgstr ""
msgid "(StrOpt) Catalog backend driver."
msgstr ""
#: ./doc/common/tables/keystone-catalog.xml33(td)
msgid ""
"endpoint_substitution_whitelist = tenant_id, user_id, public_bind_host, "
"admin_bind_host, compute_host, compute_port, admin_port, public_port, "
"public_endpoint, admin_endpoint"
msgstr ""
#: ./doc/common/tables/keystone-catalog.xml34(td)
msgid ""
"(ListOpt) (Deprecated) List of possible substitutions for use in formatting "
"endpoints. Use caution when modifying this list. It will give users with "
"permission to create endpoints the ability to see those values in your "
"configuration file. This option will be removed in Juno."
msgstr ""
#: ./doc/common/tables/keystone-catalog.xml38(td)
msgid ""
"(IntOpt) Maximum number of entities that will be returned in a catalog "
"collection."
msgstr ""
#: ./doc/common/tables/keystone-catalog.xml41(td)
#: ./doc/common/tables/keystone-catalog.xml37(td)
msgid "template_file = default_catalog.templates"
msgstr ""
#: ./doc/common/tables/keystone-catalog.xml42(td)
#: ./doc/common/tables/keystone-catalog.xml38(td)
msgid ""
"(StrOpt) Catalog template file name for use with the template catalog "
"backend."

View File

@ -1,7 +1,7 @@
msgid ""
msgstr ""
"Project-Id-Version: PACKAGE VERSION\n"
"POT-Creation-Date: 2014-12-16 06:17+0000\n"
"POT-Creation-Date: 2014-12-17 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"
@ -801,7 +801,7 @@ msgstr ""
msgid "Cloud end users can find out how to resize a server by reading the <link href=\"http://docs.openstack.org/user-guide/content/nova_cli_resize.html\">OpenStack End User Guide</link>."
msgstr ""
#: ./doc/config-reference/ch_computeconfigure.xml:77(title) ./doc/config-reference/compute/section_introduction-to-xen.xml:58(title)
#: ./doc/config-reference/ch_computeconfigure.xml:77(title) ./doc/config-reference/compute/section_introduction-to-xen.xml:59(title)
msgid "XenServer"
msgstr ""
@ -869,7 +869,7 @@ msgstr ""
msgid "The options and descriptions listed in this introduction are auto generated from the code in the Networking service project, which provides software-defined networking between VMs run in Compute. The list contains common options, while the subsections list the options for the various networking plug-ins."
msgstr ""
#: ./doc/config-reference/networking/section_networking-options-reference.xml:20(title) ./doc/config-reference/compute/section_compute-configure-xen.xml:38(title)
#: ./doc/config-reference/networking/section_networking-options-reference.xml:20(title) ./doc/config-reference/compute/section_compute-configure-xen.xml:36(title)
msgid "Agent"
msgstr ""
@ -7258,7 +7258,7 @@ msgstr ""
msgid "This document describes how to configure the OpenStack Block Storage service for use with Coraid storage appliances."
msgstr ""
#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:42(title) ./doc/config-reference/compute/section_introduction-to-xen.xml:21(title)
#: ./doc/config-reference/block-storage/drivers/coraid-driver.xml:42(title) ./doc/config-reference/compute/section_introduction-to-xen.xml:14(title)
msgid "Terminology"
msgstr ""
@ -8891,15 +8891,15 @@ msgid "Prepare for AMI type images"
msgstr ""
#: ./doc/config-reference/compute/section_xapi-ami-setup.xml:9(para)
msgid "To support AMI type images in your OpenStack installation, you must create a <filename>/boot/guest</filename> directory inside Dom0. The OpenStack VM extracts the kernel and ramdisk from the AKI and ARI images puts them in this location."
msgid "To support AMI type images in your OpenStack installation, you must create the <filename>/boot/guest</filename> directory on dom0. One of the OpenStack XAPI plugins will extract the kernel and ramdisk from AKI and ARI images and put them to that directory."
msgstr ""
#: ./doc/config-reference/compute/section_xapi-ami-setup.xml:13(para)
msgid "OpenStack maintains the contents of this directory and its size should not increase during normal operation. However, in case of power failures or accidental shutdowns, some files might be left over. To prevent these files from filling the Dom0 disk, set up this directory as a symlink that points to a subdirectory of the local SR."
#: ./doc/config-reference/compute/section_xapi-ami-setup.xml:15(para)
msgid "OpenStack maintains the contents of this directory and its size should not increase during normal operation. However, in case of power failures or accidental shutdowns, some files might be left over. To prevent these files from filling up dom0's filesystem, set up this directory as a symlink that points to a subdirectory of the local SR."
msgstr ""
#: ./doc/config-reference/compute/section_xapi-ami-setup.xml:19(para)
msgid "Run these commands in Dom0 to achieve this setup:"
#: ./doc/config-reference/compute/section_xapi-ami-setup.xml:22(para)
msgid "Run these commands in dom0 to achieve this setup:"
msgstr ""
#: ./doc/config-reference/compute/section_rpc.xml:9(para)
@ -9708,163 +9708,155 @@ 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_introduction-to-xen.xml:118(None)
msgid "@@image: '../../common/figures/xenserver_architecture.png'; md5=8eb25be1693aa7865967ac7b07d3e563"
#: ./doc/config-reference/compute/section_introduction-to-xen.xml:122(None)
msgid "@@image: '../../common/figures/xenserver_architecture.png'; md5=99792432daf7f0302672fb8f03cb63bb"
msgstr ""
#: ./doc/config-reference/compute/section_introduction-to-xen.xml:8(title)
msgid "Xen, XenAPI, XenServer"
msgid "Xen, XAPI, XenServer"
msgstr ""
#: ./doc/config-reference/compute/section_introduction-to-xen.xml:9(title)
msgid "This section needs help"
#: ./doc/config-reference/compute/section_introduction-to-xen.xml:9(para)
msgid "This section describes XAPI managed hypervisors, and how to use them with OpenStack."
msgstr ""
#: ./doc/config-reference/compute/section_introduction-to-xen.xml:10(para)
msgid "This section is low quality, and contains out of date information. The Documentation Team is currently looking for individuals with experience with the hypervisor to <link href=\"https://blueprints.launchpad.net/openstack-manuals/+spec/redocument-xen\">Re-document Xen integration with OpenStack</link>."
msgstr ""
#: ./doc/config-reference/compute/section_introduction-to-xen.xml:16(para)
msgid "This section describes XenAPI managed hypervisors, and how to use them with OpenStack."
msgstr ""
#: ./doc/config-reference/compute/section_introduction-to-xen.xml:23(title)
#: ./doc/config-reference/compute/section_introduction-to-xen.xml:16(title)
msgid "Xen"
msgstr ""
#: ./doc/config-reference/compute/section_introduction-to-xen.xml:24(para)
msgid "A hypervisor that provides the fundamental isolation between virtual machines. Xen is open source (GPLv2) and is managed by Xen.org, an cross-industry organization and a Linux Foundation Collaborative project."
#: ./doc/config-reference/compute/section_introduction-to-xen.xml:17(para)
msgid "A hypervisor that provides the fundamental isolation between virtual machines. Xen is open source (GPLv2) and is managed by Xen.org, a cross-industry organization and a Linux Foundation Collaborative project."
msgstr ""
#: ./doc/config-reference/compute/section_introduction-to-xen.xml:30(para)
#: ./doc/config-reference/compute/section_introduction-to-xen.xml:23(para)
msgid "Xen is a component of many different products and projects. The hypervisor itself is very similar across all these projects, but the way that it is managed can be different, which can cause confusion if you're not clear which toolstack you are using. Make sure you know what toolstack you want before you get started."
msgstr ""
#: ./doc/config-reference/compute/section_introduction-to-xen.xml:40(title)
#: ./doc/config-reference/compute/section_introduction-to-xen.xml:33(title)
msgid "XAPI"
msgstr ""
#: ./doc/config-reference/compute/section_introduction-to-xen.xml:34(para)
msgid "XAPI is one of the toolstacks that could control a Xen based hypervisor. XAPI's role is similar to libvirt's in the KVM world. The API provided by XAPI is called XenAPI. To learn more about the provided interface, look at <link href=\"http://docs.vmd.citrix.com/XenServer/6.2.0/1.0/en_gb/sdk.html#object_model_overview\"> XenAPI Object Model Overview </link> for definitions of XAPI specific terms such as SR, VDI, VIF and PIF."
msgstr ""
#: ./doc/config-reference/compute/section_introduction-to-xen.xml:46(para)
msgid "OpenStack has a compute driver which talks to XAPI, therefore all XAPI managed servers could be used with OpenStack."
msgstr ""
#: ./doc/config-reference/compute/section_introduction-to-xen.xml:52(title)
msgid "XenAPI"
msgstr ""
#: ./doc/config-reference/compute/section_introduction-to-xen.xml:41(para)
msgid "XenAPI is one of the toolstacks that could control a Xen based hypervisor. XenAPI's role is similar to libvirt's in the KVM world. To learn more about XenAPI, visit the <link href=\"http://docs.vmd.citrix.com/XenServer/6.2.0/1.0/en_gb/sdk.html#object_model_overview\"> XenAPI Object Model Overview </link> for definitions of XenAPI specific terms such as SR, VDI, VIF and PIF."
#: ./doc/config-reference/compute/section_introduction-to-xen.xml:53(para)
msgid "XenAPI is the API provided by XAPI. This name is also used by the python library that is a client for XAPI."
msgstr ""
#: ./doc/config-reference/compute/section_introduction-to-xen.xml:52(para)
msgid "OpenStack has a compute driver which talks to XenAPI, therefore all XenAPI managed servers could be used with OpenStack."
#: ./doc/config-reference/compute/section_introduction-to-xen.xml:60(para)
msgid "An Open Source virtualization software which includes the Xen hypervisor and XAPI for the management. For more information and product downloads, visit <link href=\"http://xenserver.org/\"> xenserver.org </link>."
msgstr ""
#: ./doc/config-reference/compute/section_introduction-to-xen.xml:59(para)
msgid "An Open Source virtualization software which includes the Xen hypervisor and XenAPI for the management. For more information and product downloads, visit <link href=\"http://xenserver.org/\"> xenserver.org </link>."
msgstr ""
#: ./doc/config-reference/compute/section_introduction-to-xen.xml:70(title)
#: ./doc/config-reference/compute/section_introduction-to-xen.xml:71(title)
msgid "Privileged and unprivileged domains"
msgstr ""
#: ./doc/config-reference/compute/section_introduction-to-xen.xml:71(para)
msgid "A Xen host runs a number of virtual machines, VMs, or domains (the terms are synonymous on Xen). One of these is in charge of running the rest of the system, and is known as domain 0, or dom0. It is the first domain to boot after Xen, and owns the storage and networking hardware, the device drivers, and the primary control software. Any other VM is unprivileged, and are known as a domU or guest. All customer VMs are unprivileged, but you should note that on Xen, the OpenStack Compute service (<systemitem class=\"service\">nova-compute</systemitem>) also runs in a domU. This gives a level of security isolation between the privileged system software and the OpenStack software (much of which is customer-facing). This architecture is described in more detail later."
#: ./doc/config-reference/compute/section_introduction-to-xen.xml:72(para)
msgid "A Xen host runs a number of virtual machines, VMs, or domains (the terms are synonymous on Xen). One of these is in charge of running the rest of the system, and is known as domain 0, or dom0. It is the first domain to boot after Xen, and owns the storage and networking hardware, the device drivers, and the primary control software. Any other VM is unprivileged, and is known as a domU or guest. All customer VMs are unprivileged, but you should note that on Xen, the OpenStack Compute service (<systemitem class=\"service\">nova-compute</systemitem>) also runs in a domU. This gives a level of security isolation between the privileged system software and the OpenStack software (much of which is customer-facing). This architecture is described in more detail later."
msgstr ""
#: ./doc/config-reference/compute/section_introduction-to-xen.xml:88(title)
#: ./doc/config-reference/compute/section_introduction-to-xen.xml:89(title)
msgid "Paravirtualized versus hardware virtualized domains"
msgstr ""
#: ./doc/config-reference/compute/section_introduction-to-xen.xml:89(para)
#: ./doc/config-reference/compute/section_introduction-to-xen.xml:90(para)
msgid "A Xen virtual machine can be paravirtualized (PV) or hardware virtualized (HVM). This refers to the interaction between Xen, domain 0, and the guest VM's kernel. PV guests are aware of the fact that they are virtualized and will co-operate with Xen and domain 0; this gives them better performance characteristics. HVM guests are not aware of their environment, and the hardware has to pretend that they are running on an unvirtualized machine. HVM guests do not need to modify the guest operating system, which is essential when running Windows."
msgstr ""
#: ./doc/config-reference/compute/section_introduction-to-xen.xml:101(para)
#: ./doc/config-reference/compute/section_introduction-to-xen.xml:102(para)
msgid "In OpenStack, customer VMs may run in either PV or HVM mode. However, the OpenStack domU (that's the one running <systemitem class=\"service\">nova-compute</systemitem>) must be running in PV mode."
msgstr ""
#: ./doc/config-reference/compute/section_introduction-to-xen.xml:110(title)
msgid "XenAPI Deployment Architecture"
#: ./doc/config-reference/compute/section_introduction-to-xen.xml:111(title)
msgid "XenAPI deployment architecture"
msgstr ""
#: ./doc/config-reference/compute/section_introduction-to-xen.xml:112(para)
msgid "When you deploy OpenStack on XCP or XenServer, you get something similar to this: <placeholder-1/>"
#: ./doc/config-reference/compute/section_introduction-to-xen.xml:114(para)
msgid "A basic OpenStack deployment on a XAPI-managed server, assuming that the network provider is nova-network, looks like this: <placeholder-1/>"
msgstr ""
#: ./doc/config-reference/compute/section_introduction-to-xen.xml:124(para)
#: ./doc/config-reference/compute/section_introduction-to-xen.xml:131(para)
msgid "The hypervisor: Xen"
msgstr ""
#: ./doc/config-reference/compute/section_introduction-to-xen.xml:136(para)
msgid "Domain 0: runs XAPI and some small pieces from OpenStack, the XAPI plug-ins."
msgstr ""
#: ./doc/config-reference/compute/section_introduction-to-xen.xml:142(para)
msgid "OpenStack VM: The <systemitem class=\"service\">Compute</systemitem> service runs in a paravirtualized virtual machine, on the host under management. Each host runs a local instance of <systemitem class=\"service\">Compute</systemitem>. It is also running an instance of nova-network."
msgstr ""
#: ./doc/config-reference/compute/section_introduction-to-xen.xml:153(para)
msgid "OpenStack Compute uses the XenAPI Python library to talk to XAPI, and it uses the Management Network to reach from the OpenStack VM to Domain 0."
msgstr ""
#: ./doc/config-reference/compute/section_introduction-to-xen.xml:127(para)
msgid "Domain 0: runs xapi and some small pieces from OpenStack (some xapi plug-ins and network isolation rules). The majority of this is provided by XenServer or XCP (or yourself using Kronos)."
msgstr ""
#: ./doc/config-reference/compute/section_introduction-to-xen.xml:134(para)
msgid "OpenStack VM: The <systemitem class=\"service\">nova-compute</systemitem> code runs in a paravirtualized virtual machine, running on the host under management. Each host runs a local instance of <systemitem class=\"service\">nova-compute</systemitem>. It will often also be running nova-network (depending on your network mode). In this case, nova-network is managing the addresses given to the tenant VMs through DHCP."
msgstr ""
#: ./doc/config-reference/compute/section_introduction-to-xen.xml:146(para)
msgid "Nova uses the XenAPI Python library to talk to xapi, and it uses the Management Network to reach from the domU to dom0 without leaving the host."
msgstr ""
#: ./doc/config-reference/compute/section_introduction-to-xen.xml:122(para)
msgid "Key things to note: <placeholder-1/>"
msgstr ""
#: ./doc/config-reference/compute/section_introduction-to-xen.xml:154(para)
msgid "The above diagram assumes FlatDHCP networking (the DevStack default)."
#: ./doc/config-reference/compute/section_introduction-to-xen.xml:165(para)
msgid "The above diagram assumes FlatDHCP networking."
msgstr ""
#: ./doc/config-reference/compute/section_introduction-to-xen.xml:160(para)
msgid "Management network - RabbitMQ, MySQL, and other services. Please note that the VM images are downloaded by the XenAPI plug-ins, so make sure that the images can be downloaded through the management network. It usually means binding those services to the management interface."
#: ./doc/config-reference/compute/section_introduction-to-xen.xml:174(para)
msgid "Management network: RabbitMQ, MySQL, inter-host communication, and compute-XAPI communication. Please note that the VM images are downloaded by the XenAPI plug-ins, so make sure that the OpenStack Image Service is accessible through this network. It usually means binding those services to the management interface."
msgstr ""
#: ./doc/config-reference/compute/section_introduction-to-xen.xml:186(para)
msgid "Tenant network: controlled by nova-network, this is used for tenant traffic."
msgstr ""
#: ./doc/config-reference/compute/section_introduction-to-xen.xml:193(para)
msgid "Public network: floating IPs, public API endpoints."
msgstr ""
#: ./doc/config-reference/compute/section_introduction-to-xen.xml:170(para)
msgid "Tenant network - controlled by nova-network. The parameters of this network depend on the networking model selected (Flat, Flat DHCP, VLAN)."
msgid "There are three main OpenStack networks: <placeholder-1/>"
msgstr ""
#: ./doc/config-reference/compute/section_introduction-to-xen.xml:177(para)
msgid "Public network - floating IPs, public API endpoints."
msgstr ""
#: ./doc/config-reference/compute/section_introduction-to-xen.xml:158(para)
msgid "There are three main OpenStack Networks:<placeholder-1/>"
msgstr ""
#: ./doc/config-reference/compute/section_introduction-to-xen.xml:183(para)
#: ./doc/config-reference/compute/section_introduction-to-xen.xml:202(para)
msgid "The networks shown here must be connected to the corresponding physical networks within the data center. In the simplest case, three individual physical network cards could be used. It is also possible to use VLANs to separate these networks. Please note, that the selected configuration must be in line with the networking model selected for the cloud. (In case of VLAN networking, the physical channels have to be able to forward the tagged traffic.)"
msgstr ""
#: ./doc/config-reference/compute/section_introduction-to-xen.xml:152(para)
#: ./doc/config-reference/compute/section_introduction-to-xen.xml:161(para)
msgid "Some notes on the networking: <placeholder-1/>"
msgstr ""
#: ./doc/config-reference/compute/section_introduction-to-xen.xml:198(title)
msgid "XenAPI pools"
msgstr ""
#: ./doc/config-reference/compute/section_introduction-to-xen.xml:199(para)
msgid "The host-aggregates feature enables you to create pools of XenServer hosts to enable live migration when using shared storage. However, you cannot configure shared storage."
msgstr ""
#: ./doc/config-reference/compute/section_introduction-to-xen.xml:205(title)
#: ./doc/config-reference/compute/section_introduction-to-xen.xml:218(title)
msgid "Further reading"
msgstr ""
#: ./doc/config-reference/compute/section_introduction-to-xen.xml:209(para)
msgid "Citrix XenServer official documentation:<link href=\"http://docs.vmd.citrix.com/XenServer/6.0.0/1.0/en_gb/\"> http://docs.vmd.citrix.com/XenServer</link>."
#: ./doc/config-reference/compute/section_introduction-to-xen.xml:224(para)
msgid "Citrix XenServer official documentation: <link href=\"http://docs.vmd.citrix.com/XenServer/6.2.0/1.0/en_gb/\"> http://docs.vmd.citrix.com/XenServer </link>"
msgstr ""
#: ./doc/config-reference/compute/section_introduction-to-xen.xml:216(para)
msgid "What is Xen? by Xen.org: <link href=\"http://xen.org/files/Marketing/WhatisXen.pdf\"> http://xen.org/files/Marketing/WhatisXen.pdf</link>."
#: ./doc/config-reference/compute/section_introduction-to-xen.xml:233(para)
msgid "What is Xen? by Xen.org: <link href=\"http://xen.org/files/Marketing/WhatisXen.pdf\"> http://xen.org/files/Marketing/WhatisXen.pdf </link>"
msgstr ""
#: ./doc/config-reference/compute/section_introduction-to-xen.xml:222(para)
msgid "Xen Hypervisor project: <link href=\"http://xen.org/products/xenhyp.html\"> http://xen.org/products/xenhyp.html</link>."
#: ./doc/config-reference/compute/section_introduction-to-xen.xml:242(para)
msgid "Xen Hypervisor project: <link href=\"http://www.xenproject.org/developers/teams/hypervisor.html\"> http://www.xenproject.org/developers/teams/hypervisor.html </link>"
msgstr ""
#: ./doc/config-reference/compute/section_introduction-to-xen.xml:228(para)
msgid "XCP project: <link href=\"http://xen.org/products/cloudxen.html\"> http://xen.org/products/cloudxen.html</link>."
#: ./doc/config-reference/compute/section_introduction-to-xen.xml:251(para)
msgid "Xapi project: <link href=\"http://www.xenproject.org/developers/teams/xapi.html\"> http://www.xenproject.org/developers/teams/xapi.html </link>"
msgstr ""
#: ./doc/config-reference/compute/section_introduction-to-xen.xml:234(para)
msgid "Further XenServer and OpenStack information: <link href=\"http://wiki.openstack.org/XenServer\"> http://wiki.openstack.org/XenServer</link>."
#: ./doc/config-reference/compute/section_introduction-to-xen.xml:260(para)
msgid "Further XenServer and OpenStack information: <link href=\"http://wiki.openstack.org/XenServer\"> http://wiki.openstack.org/XenServer </link>"
msgstr ""
#: ./doc/config-reference/compute/section_introduction-to-xen.xml:206(para)
#: ./doc/config-reference/compute/section_introduction-to-xen.xml:219(para)
msgid "Here are some of the resources available to learn more about Xen: <placeholder-1/>"
msgstr ""
@ -10157,27 +10149,27 @@ msgid "The second command, <placeholder-1/>, may take a while."
msgstr ""
#: ./doc/config-reference/compute/section_xapi-resize-setup.xml:8(title)
msgid "Modify Dom0 for resize/migration support"
msgid "Modify dom0 for resize/migration support"
msgstr ""
#: ./doc/config-reference/compute/section_xapi-resize-setup.xml:9(para)
msgid "To resize servers with XenServer and XCP, you must:"
msgid "To resize servers with XenServer you must:"
msgstr ""
#: ./doc/config-reference/compute/section_xapi-resize-setup.xml:12(para)
msgid "Establish a root trust between all hypervisor nodes of your deployment:"
msgstr ""
#: ./doc/config-reference/compute/section_xapi-resize-setup.xml:14(para)
#: ./doc/config-reference/compute/section_xapi-resize-setup.xml:16(para)
msgid "To do so, generate an ssh key-pair with the <placeholder-1/> command. Ensure that each of your dom0's <filename>authorized_keys</filename> file (located in <filename>/root/.ssh/authorized_keys</filename>) contains the public key fingerprint (located in <filename>/root/.ssh/id_rsa.pub</filename>)."
msgstr ""
#: ./doc/config-reference/compute/section_xapi-resize-setup.xml:23(para)
msgid "Provide an <filename>/images</filename> mount point to the dom0 for your hypervisor:"
#: ./doc/config-reference/compute/section_xapi-resize-setup.xml:26(para)
msgid "Provide a <filename>/images</filename> mount point to the dom0 for your hypervisor:"
msgstr ""
#: ./doc/config-reference/compute/section_xapi-resize-setup.xml:25(para)
msgid "Dom0 space is at a premium so creating a directory in dom0 is potentially dangerous and likely to fail especially when you resize large servers. The least you can do is to symlink <filename>/images</filename> to your local storage SR. The following instructions work for an English-based installation of XenServer (and XCP) and in the case of ext3-based SR (with which the resize functionality is known to work correctly)."
#: ./doc/config-reference/compute/section_xapi-resize-setup.xml:30(para)
msgid "dom0 space is at a premium so creating a directory in dom0 is potentially dangerous and likely to fail especially when you resize large servers. The least you can do is to symlink <filename>/images</filename> to your local storage SR. The following instructions work for an English-based installation of XenServer and in the case of ext3-based SR (with which the resize functionality is known to work correctly)."
msgstr ""
#. When image changes, this message will be marked fuzzy or untranslated for you.
@ -11911,175 +11903,95 @@ msgid "The <filename>rootwrap.conf</filename> file defines configuration values
msgstr ""
#: ./doc/config-reference/compute/section_xen-install.xml:7(title)
msgid "Install XenServer and XCP"
msgid "Install XenServer"
msgstr ""
#: ./doc/config-reference/compute/section_xen-install.xml:9(para)
msgid "Before you can run OpenStack with XCP or XenServer, you must install the software on <link href=\"http://docs.vmd.citrix.com/XenServer/6.0.0/1.0/en_gb/installation.html#sys_requirements\">an appropriate server</link>."
#: ./doc/config-reference/compute/section_xen-install.xml:8(para)
msgid "Before you can run OpenStack with XenServer, you must install the hypervisor on <link href=\"http://docs.vmd.citrix.com/XenServer/6.2.0/1.0/en_gb/installation.html#sys_requirements\"> an appropriate server </link> ."
msgstr ""
#: ./doc/config-reference/compute/section_xen-install.xml:14(para)
msgid "Xen is a type 1 hypervisor: When your server starts, Xen is the first software that runs. Consequently, you must install XenServer or XCP before you install the operating system where you want to run OpenStack code. The OpenStack services then run in a virtual machine that you install on top of XenServer."
#: ./doc/config-reference/compute/section_xen-install.xml:18(para)
msgid "Xen is a type 1 hypervisor: When your server starts, Xen is the first software that runs. Consequently, you must install XenServer before you install the operating system where you want to run OpenStack code. You then install <systemitem class=\"service\">nova-compute</systemitem> into a dedicated virtual machine on the host."
msgstr ""
#: ./doc/config-reference/compute/section_xen-install.xml:21(para)
msgid "Before you can install your system, decide whether to install a free or paid edition of Citrix XenServer or Xen Cloud Platform from Xen.org. Download the software from these locations:"
#: ./doc/config-reference/compute/section_xen-install.xml:33(link)
msgid "http://xenserver.org/open-source-virtualization-download.html"
msgstr ""
#: ./doc/config-reference/compute/section_xen-install.xml:29(link)
msgid "http://www.citrix.com/XenServer/download"
#: ./doc/config-reference/compute/section_xen-install.xml:27(para)
msgid "Use the following link to download XenServer's installation media: <placeholder-1/>"
msgstr ""
#: ./doc/config-reference/compute/section_xen-install.xml:34(link)
msgid "http://www.xen.org/download/xcp/index.html"
#: ./doc/config-reference/compute/section_xen-install.xml:40(para)
msgid "When you install many servers, you might find it easier to perform <link href=\"http://docs.vmd.citrix.com/XenServer/6.2.0/1.0/en_gb/installation.html#pxe_boot_install\"> PXE boot installations </link> . You can also package any post-installation changes that you want to make to your XenServer by following the instructions of <link href=\"http://docs.vmd.citrix.com/XenServer/6.2.0/1.0/en_gb/supplemental_pack_ddk.html\"> creating your own XenServer supplemental pack </link> ."
msgstr ""
#: ./doc/config-reference/compute/section_xen-install.xml:37(para)
msgid "When you install many servers, you might find it easier to perform <link href=\"http://docs.vmd.citrix.com/XenServer/6.0.0/1.0/en_gb/installation.html#pxe_boot_install\">PXE boot installations of XenServer or XCP</link>. You can also package any post-installation changes that you want to make to your XenServer by <link href=\"http://docs.vmd.citrix.com/XenServer/6.0.0/1.0/en_gb/supplemental_pack_ddk.html\">creating your own XenServer supplemental pack</link>."
msgstr ""
#: ./doc/config-reference/compute/section_xen-install.xml:47(para)
msgid "You can also install the <package>xcp-xenapi</package> package on Debian-based distributions to get XCP. However, this is not as mature or feature complete as above distributions. This modifies your boot loader to first boot Xen and boot your existing OS on top of Xen as Dom0. The xapi daemon runs in Dom0. Find more details at <link href=\"http://wiki.xen.org/wiki/Project_Kronos\">http://wiki.xen.org/wiki/Project_Kronos</link>."
msgstr ""
#: ./doc/config-reference/compute/section_xen-install.xml:56(para)
msgid "Make sure you use the EXT type of storage repository (SR). Features that require access to VHD files (such as copy on write, snapshot and migration) do not work when you use the LVM SR. Storage repository (SR) is a XenAPI-specific term relating to the physical storage where virtual disks are stored."
#: ./doc/config-reference/compute/section_xen-install.xml:55(para)
msgid "Make sure you use the EXT type of storage repository (SR). Features that require access to VHD files (such as copy on write, snapshot and migration) do not work when you use the LVM SR. Storage repository (SR) is a XAPI-specific term relating to the physical storage where virtual disks are stored."
msgstr ""
#: ./doc/config-reference/compute/section_xen-install.xml:62(para)
msgid "On the XenServer/XCP installation screen, choose the <guilabel>XenDesktop Optimized</guilabel> option. If you use an answer file, make sure you use <literal>srtype=\"ext\"</literal> in the <option>installation</option> tag of the answer file."
msgid "On the XenServer installation screen, choose the <guilabel>XenDesktop Optimized</guilabel> option. If you use an answer file, make sure you use <literal>srtype=\"ext\"</literal> in the <literal>installation</literal> tag of the answer file."
msgstr ""
#: ./doc/config-reference/compute/section_xen-install.xml:70(title)
#: ./doc/config-reference/compute/section_xen-install.xml:73(title)
msgid "Post-installation steps"
msgstr ""
#: ./doc/config-reference/compute/section_xen-install.xml:71(para)
msgid "Complete these steps to install OpenStack in your XenServer system:"
#: ./doc/config-reference/compute/section_xen-install.xml:74(para)
msgid "The following steps need to be completed after the hypervisor's installation:"
msgstr ""
#: ./doc/config-reference/compute/section_xen-install.xml:75(para)
msgid "For resize and migrate functionality, complete the changes described in the <citetitle>Configure resize</citetitle> section in the <link href=\"http://docs.openstack.org/trunk/config-reference/content/\"><citetitle>OpenStack Configuration Reference</citetitle></link>."
#: ./doc/config-reference/compute/section_xen-install.xml:80(para)
msgid "For resize and migrate functionality, enable password-less SSH authentication and set up the <literal>/images</literal> directory on dom0."
msgstr ""
#: ./doc/config-reference/compute/section_xen-install.xml:83(para)
msgid "Install the VIF isolation rules to help prevent mac and IP address spoofing."
#: ./doc/config-reference/compute/section_xen-install.xml:88(para)
msgid "Install the XAPI plug-ins."
msgstr ""
#: ./doc/config-reference/compute/section_xen-install.xml:87(para)
msgid "Install the XenAPI plug-ins. See the following section."
#: ./doc/config-reference/compute/section_xen-install.xml:93(para)
msgid "To support AMI type images, you must set up <literal>/boot/guest</literal> symlink/directory in dom0."
msgstr ""
#: ./doc/config-reference/compute/section_xen-install.xml:91(para)
msgid "To support AMI type images, you must set up <literal>/boot/guest</literal> symlink/directory in Dom0. For detailed instructions, see next section."
#: ./doc/config-reference/compute/section_xen-install.xml:100(para)
msgid "Create a Paravirtualized virtual machine that can run <systemitem class=\"service\">nova-compute</systemitem>."
msgstr ""
#: ./doc/config-reference/compute/section_xen-install.xml:97(para)
msgid "To support resize/migration, set up an ssh trust relation between your XenServer hosts, and ensure <literal>/images</literal> is properly set up. See next section for more details."
msgstr ""
#: ./doc/config-reference/compute/section_xen-install.xml:103(para)
msgid "Create a Paravirtualized virtual machine that can run the OpenStack compute code."
msgstr ""
#: ./doc/config-reference/compute/section_xen-install.xml:107(para)
msgid "Install and configure the <systemitem class=\"service\">nova-compute</systemitem> in the above virtual machine."
msgstr ""
#: ./doc/config-reference/compute/section_xen-install.xml:112(para)
msgid "For more information, see how DevStack performs the last three steps for developer deployments. For more information about DevStack, see <citetitle>Getting Started With XenServer and Devstack</citetitle> (<link href=\"https://github.com/openstack-dev/devstack/blob/master/tools/xen/README.md\">https://github.com/openstack-dev/devstack/blob/master/tools/xen/README.md</link>). Find more information about the first step, see <citetitle>Multi Tenancy Networking Protections in XenServer</citetitle> (<link href=\"https://github.com/openstack/nova/blob/master/plugins/xenserver/doc/networking.rst\">https://github.com/openstack/nova/blob/master/plugins/xenserver/doc/networking.rst</link>). For information about how to install the XenAPI plug-ins, see <citetitle>XenAPI README</citetitle> (<link href=\"https://github.com/openstack/nova/blob/master/plugins/xenserver/xenapi/README\">https://github.com/openstack/nova/blob/master/plugins/xenserver/xenapi/README</link>)."
msgstr ""
#: ./doc/config-reference/compute/section_xen-install.xml:132(title)
msgid "Xen boot from ISO"
msgstr ""
#: ./doc/config-reference/compute/section_xen-install.xml:133(para)
msgid "XenServer, through the XenAPI integration with OpenStack, provides a feature to boot instances from an ISO file. To activate the Boot From ISO feature, you must configure the SR elements on XenServer host, as follows:"
msgstr ""
#: ./doc/config-reference/compute/section_xen-install.xml:140(para)
msgid "Create an ISO-typed SR, such as an NFS ISO library, for instance. For this, using XenCenter is a simple method. You must export an NFS volume from a remote NFS server. Make sure it is exported in read-write mode."
msgstr ""
#: ./doc/config-reference/compute/section_xen-install.xml:147(para)
msgid "On the compute host, find and record the UUID of this ISO SR:"
msgstr ""
#: ./doc/config-reference/compute/section_xen-install.xml:152(para)
msgid "Locate the UUID of the NFS ISO library:"
msgstr ""
#: ./doc/config-reference/compute/section_xen-install.xml:156(para)
msgid "Set the UUID and configuration. Even if an NFS mount point is not local, you must specify <literal>local-storage-iso</literal>."
msgstr ""
#: ./doc/config-reference/compute/section_xen-install.xml:162(para)
msgid "Make sure the host-UUID from <literal>xe pbd-list</literal> equals the UUID of the host you found previously:"
msgstr ""
#: ./doc/config-reference/compute/section_xen-install.xml:168(para)
msgid "You can now add images through the OpenStack Image Service with <literal>disk-format=iso</literal>, and boot them in OpenStack Compute:"
#: ./doc/config-reference/compute/section_xen-install.xml:106(para)
msgid "Install and configure <systemitem class=\"service\">nova-compute</systemitem> in the above virtual machine."
msgstr ""
#: ./doc/config-reference/compute/section_xapi-install-plugins.xml:8(title)
msgid "Install the XenAPI plug-ins"
msgid "Install XAPI plug-ins"
msgstr ""
#: ./doc/config-reference/compute/section_xapi-install-plugins.xml:9(para)
msgid "When you use Xen as the hypervisor for OpenStack Compute, you can install a Python script (or any executable) on the host side, and call that through the XenAPI. These scripts are called plug-ins. The XenAPI plug-ins live in the nova code repository. These plug-ins have to be copied to the Dom0 for the hypervisor, to the appropriate directory, where xapi can find them. There are several options for the installation. The important thing is to ensure that the version of the plug-ins are in line with the nova installation by only installing plug-ins from a matching nova repository."
msgid "When you use a XAPI managed hypervisor, you can install a Python script (or any executable) on the host side, and execute that through XenAPI. These scripts are called plug-ins. The OpenStack related XAPI plug-ins live in OpenStack Compute's code repository. These plug-ins have to be copied to dom0's filesystem, to the appropriate directory, where XAPI can find them. It is important to ensure that the version of the plug-ins are in line with the OpenStack Compute installation you are using."
msgstr ""
#: ./doc/config-reference/compute/section_xapi-install-plugins.xml:20(title)
msgid "Manually install the plug-in"
#: ./doc/config-reference/compute/section_xapi-install-plugins.xml:19(para)
msgid "The plugins should typically be copied from the Nova installation running in the Compute's DomU, but if you want to download the latest version the following procedure can be used."
msgstr ""
#: ./doc/config-reference/compute/section_xapi-install-plugins.xml:23(para)
msgid "Create temporary files/directories:"
#: ./doc/config-reference/compute/section_xapi-install-plugins.xml:25(title)
msgid "Manually installing the plug-ins"
msgstr ""
#: ./doc/config-reference/compute/section_xapi-install-plugins.xml:28(para)
msgid "Get the source from GitHub. The example assumes the master branch is used. Amend the URL to match the version being used:"
msgid "Create temporary files/directories:"
msgstr ""
#: ./doc/config-reference/compute/section_xapi-install-plugins.xml:33(para)
msgid "(Alternatively) To use the official Ubuntu packages, use the following commands to get the nova code base:"
msgid "Get the source from GitHub. The example assumes the master branch is used, and the XenServer host is accessible as xenserver. Match those parameters to your setup."
msgstr ""
#: ./doc/config-reference/compute/section_xapi-install-plugins.xml:40(para)
#: ./doc/config-reference/compute/section_xapi-install-plugins.xml:43(para)
msgid "Copy the plug-ins to the hypervisor:"
msgstr ""
#: ./doc/config-reference/compute/section_xapi-install-plugins.xml:45(para)
msgid "Remove the temporary files/directories:"
msgstr ""
#: ./doc/config-reference/compute/section_xapi-install-plugins.xml:52(title)
msgid "Package a XenServer supplemental pack"
msgstr ""
#: ./doc/config-reference/compute/section_xapi-install-plugins.xml:53(para)
msgid "Follow these steps to produce a supplemental pack from the nova sources, and package it as a XenServer supplemental pack."
msgstr ""
#: ./doc/config-reference/compute/section_xapi-install-plugins.xml:58(para)
msgid "Create RPM packages. Given you have the nova sources. Use one of the methods in <xref linkend=\"manual_install\"/>:"
msgstr ""
#: ./doc/config-reference/compute/section_xapi-install-plugins.xml:63(para)
msgid "These commands leave an <filename>.rpm</filename> file in the <filename>rpmbuild/RPMS/noarch/</filename> directory."
msgstr ""
#: ./doc/config-reference/compute/section_xapi-install-plugins.xml:69(para)
msgid "Pack the RPM packages to a Supplemental Pack, using the XenServer DDK (the following command should be issued on the XenServer DDK virtual appliance, after the produced rpm file has been copied over):"
msgstr ""
#: ./doc/config-reference/compute/section_xapi-install-plugins.xml:82(para)
msgid "This command produces an <filename>.iso</filename> file in the output directory specified. Copy that file to the hypervisor."
msgstr ""
#: ./doc/config-reference/compute/section_xapi-install-plugins.xml:88(para)
msgid "Install the Supplemental Pack. Log in to the hypervisor, and issue:"
#: ./doc/config-reference/compute/section_xapi-install-plugins.xml:49(para)
msgid "Remove temporary files/directories:"
msgstr ""
#: ./doc/config-reference/compute/section_compute-hypervisors.xml:6(title)
@ -12162,64 +12074,64 @@ msgstr ""
msgid "To customize the Conductor, use the configuration option settings documented in <xref linkend=\"config_table_nova_conductor\"/>."
msgstr ""
#: ./doc/config-reference/compute/section_compute-configure-xen.xml:6(title) ./doc/config-reference/compute/section_compute-configure-xen.xml:70(title)
#: ./doc/config-reference/compute/section_compute-configure-xen.xml:6(title)
msgid "Xen configuration reference"
msgstr ""
#: ./doc/config-reference/compute/section_compute-configure-xen.xml:7(para)
msgid "The following section discusses some commonly changed options in XenServer. The table below provides a complete reference of all configuration options available for configuring Xen with OpenStack."
msgid "The following section discusses some commonly changed options when using the XenAPI driver. The table below provides a complete reference of all configuration options available for configuring XAPI with OpenStack."
msgstr ""
#: ./doc/config-reference/compute/section_compute-configure-xen.xml:11(para)
msgid "The recommended way to use Xen with OpenStack is through the XenAPI driver. To enable the XenAPI driver, add the following configuration options <filename>/etc/nova/nova.conf</filename> and restart the <systemitem class=\"service\">nova-compute</systemitem> service:"
#: ./doc/config-reference/compute/section_compute-configure-xen.xml:13(para)
msgid "The recommended way to use XAPI with OpenStack is through the XenAPI driver. To enable the XenAPI driver, add the following configuration options to <filename>/etc/nova/nova.conf</filename> and restart <systemitem class=\"service\">OpenStack Compute</systemitem>:"
msgstr ""
#: ./doc/config-reference/compute/section_compute-configure-xen.xml:19(para)
msgid "These connection details are used by the OpenStack Compute service to contact your hypervisor and are the same details you use to connect XenCenter, the XenServer management console, to your XenServer or XCP box."
#: ./doc/config-reference/compute/section_compute-configure-xen.xml:21(replaceable)
msgid "your_xenapi_management_ip_address"
msgstr ""
#: ./doc/config-reference/compute/section_compute-configure-xen.xml:23(para)
msgid "The <literal>xenapi_connection_url</literal> is generally the management network IP address of the XenServer. Though it is possible to use the internal network IP Address (169.250.0.1) to contact XenAPI, this does not allow live migration between hosts. Other functionalities such as host aggregates, do not work."
#: ./doc/config-reference/compute/section_compute-configure-xen.xml:23(replaceable)
msgid "your_password"
msgstr ""
#: ./doc/config-reference/compute/section_compute-configure-xen.xml:24(para)
msgid "These connection details are used by OpenStack Compute service to contact your hypervisor and are the same details you use to connect XenCenter, the XenServer management console, to your XenServer node."
msgstr ""
#: ./doc/config-reference/compute/section_compute-configure-xen.xml:30(para)
msgid "It is possible to manage Xen using libvirt, though this is not well-tested or supported. To experiment using Xen through libvirt add the following configuration options <filename>/etc/nova/nova.conf</filename>: <placeholder-1/>"
msgid "The <literal>connection_url</literal> is generally the management network IP address of the XenServer."
msgstr ""
#: ./doc/config-reference/compute/section_compute-configure-xen.xml:39(para)
msgid "If you don't have the guest agent on your VMs, it takes a long time for nova to decide the VM has successfully started. Generally a large timeout is required for Windows instances, but you may want to tweak <literal>agent_version_timeout</literal>."
#: ./doc/config-reference/compute/section_compute-configure-xen.xml:37(para)
msgid "The agent is a piece of software that runs on the instances, and communicates with OpenStack. In case of the XenAPI driver, the agent communicates with OpenStack through XenStore (see <link href=\"http://wiki.xen.org/wiki/XenStore\">the Xen Wiki</link> for more information on XenStore)."
msgstr ""
#: ./doc/config-reference/compute/section_compute-configure-xen.xml:44(title)
msgid "Firewall"
#: ./doc/config-reference/compute/section_compute-configure-xen.xml:44(para)
msgid "If you don't have the guest agent on your VMs, it takes a long time for OpenStack Compute to detect that the VM has successfully started. Generally a large timeout is required for Windows instances, but you may want to adjust: <literal>agent_version_timeout</literal> within the <literal>[xenserver]</literal> section."
msgstr ""
#: ./doc/config-reference/compute/section_compute-configure-xen.xml:45(para)
msgid "If using nova-network, iptables is supported: <placeholder-1/> Alternately, doing the isolation in Dom0: <placeholder-2/>"
msgstr ""
#: ./doc/config-reference/compute/section_compute-configure-xen.xml:51(title)
#: ./doc/config-reference/compute/section_compute-configure-xen.xml:54(title)
msgid "VNC proxy address"
msgstr ""
#: ./doc/config-reference/compute/section_compute-configure-xen.xml:52(para)
msgid "Assuming you are talking to XenAPI through the host local management network, and XenServer is on the address: 169.254.0.1, you can use the following: <literal>vncserver_proxyclient_address=169.254.0.1</literal>"
#: ./doc/config-reference/compute/section_compute-configure-xen.xml:55(para)
msgid "Assuming you are talking to XAPI through a management network, and XenServer is on the address: 10.10.1.34 specify the same address for the vnc proxy address: <literal>vncserver_proxyclient_address=<replaceable>10.10.1.34</replaceable></literal>"
msgstr ""
#: ./doc/config-reference/compute/section_compute-configure-xen.xml:58(title)
#: ./doc/config-reference/compute/section_compute-configure-xen.xml:63(title)
msgid "Storage"
msgstr ""
#: ./doc/config-reference/compute/section_compute-configure-xen.xml:65(para)
msgid "To use a XenServer pool, you must create the pool by using the Host Aggregates feature."
#: ./doc/config-reference/compute/section_compute-configure-xen.xml:64(para)
msgid "You can specify which Storage Repository to use with nova by editing the following flag. To use the local-storage setup by the default installer: <placeholder-1/> Another alternative is to use the \"default\" storage (for example if you have attached NFS or any other shared storage): <placeholder-2/>"
msgstr ""
#: ./doc/config-reference/compute/section_compute-configure-xen.xml:59(para)
msgid "You can specify which Storage Repository to use with nova by looking at the following flag. The default is to use the local-storage setup by the default installer: <placeholder-1/> Another good alternative is to use the \"default\" storage (for example if you have attached NFS or any other shared storage): <placeholder-2/><placeholder-3/>"
#: ./doc/config-reference/compute/section_compute-configure-xen.xml:75(title)
msgid "XenAPI configuration reference"
msgstr ""
#: ./doc/config-reference/compute/section_compute-configure-xen.xml:71(para)
msgid "To customize the Xen driver, use the configuration option settings documented in <xref linkend=\"config_table_nova_xen\"/>."
#: ./doc/config-reference/compute/section_compute-configure-xen.xml:76(para)
msgid "To customize the XenAPI driver, use the configuration option settings documented in <xref linkend=\"config_table_nova_xen\"/>."
msgstr ""
#. Put one translator per line, in the form of NAME <EMAIL>, YEAR1, YEAR2

View File

@ -7,8 +7,8 @@
msgid ""
msgstr ""
"Project-Id-Version: OpenStack Manuals\n"
"POT-Creation-Date: 2014-12-15 18:58+0000\n"
"PO-Revision-Date: 2014-12-15 19:11+0000\n"
"POT-Creation-Date: 2014-12-17 04:36+0000\n"
"PO-Revision-Date: 2014-12-16 11:31+0000\n"
"Last-Translator: Sungjin Kang <potopro@gmail.com>\n"
"Language-Team: Korean (Korea) (http://www.transifex.com/projects/p/openstack-manuals-i18n/language/ko_KR/)\n"
"MIME-Version: 1.0\n"
@ -741,7 +741,7 @@ msgstr "인증 토큰"
#: ./doc/glossary/glossary-terms.xml744(primary)
msgid "authentication tokens"
msgstr ""
msgstr "인증 토큰"
#: ./doc/glossary/glossary-terms.xml748(para)
msgid ""
@ -828,7 +828,7 @@ msgstr "AWS"
#: ./doc/glossary/glossary-terms.xml842(primary)
msgid "AWS (Amazon Web Services)"
msgstr ""
msgstr "AWS (Amazon Web Services)"
#: ./doc/glossary/glossary-terms.xml846(para)
msgid "Amazon Web Services."
@ -837,7 +837,7 @@ msgstr "Amazon 웹 서비스."
#: ./doc/glossary/glossary-terms.xml851(glossterm)
#: ./doc/glossary/glossary-terms.xml853(primary)
msgid "AWS CloudFormation template"
msgstr ""
msgstr "AWS CloudFormation 템플릿"
#: ./doc/glossary/glossary-terms.xml857(para)
msgid ""
@ -852,13 +852,13 @@ msgstr "B"
#: ./doc/glossary/glossary-terms.xml872(glossterm)
msgid "back end"
msgstr ""
msgstr "백엔드"
#: ./doc/glossary/glossary-terms.xml874(primary)
#: ./doc/glossary/glossary-terms.xml889(primary)
#: ./doc/glossary/glossary-terms.xml905(primary)
msgid "back-end interactions"
msgstr ""
msgstr "백엔드 상호 작용"
#: ./doc/glossary/glossary-terms.xml880(para)
msgid ""
@ -890,7 +890,7 @@ msgstr "백엔드 저장소"
#: ./doc/glossary/glossary-terms.xml907(secondary)
msgid "store"
msgstr ""
msgstr "저장소"
#: ./doc/glossary/glossary-terms.xml911(para)
msgid ""
@ -925,7 +925,7 @@ msgstr ""
msgid ""
"An Image Service container format that indicates that no container exists "
"for the VM image."
msgstr ""
msgstr "이미지 서비스 컨테이너 포멧. 어떤 컨테이너가 VM 이미지가 없음을 의미합니다."
#: ./doc/glossary/glossary-terms.xml947(glossterm)
#: ./doc/glossary/glossary-terms.xml949(primary)
@ -939,7 +939,7 @@ msgstr "OpenStack에서 제공하는 이미지."
#: ./doc/glossary/glossary-terms.xml958(glossterm)
#: ./doc/glossary/glossary-terms.xml960(primary)
msgid "Bell-LaPadula model"
msgstr ""
msgstr "Bell-LaPadula 모델"
#: ./doc/glossary/glossary-terms.xml964(para)
msgid ""
@ -986,7 +986,7 @@ msgstr "비트"
#: ./doc/glossary/glossary-terms.xml1006(primary)
msgid "bits, definition of"
msgstr ""
msgstr "비트의 정의는"
#: ./doc/glossary/glossary-terms.xml1010(para)
msgid ""
@ -997,7 +997,7 @@ msgstr ""
#: ./doc/glossary/glossary-terms.xml1016(glossterm)
#: ./doc/glossary/glossary-terms.xml1018(primary)
msgid "bits per second (BPS)"
msgstr ""
msgstr "초당 비트 (BPS)"
#: ./doc/glossary/glossary-terms.xml1022(para)
msgid ""
@ -1020,7 +1020,7 @@ msgstr ""
#: ./doc/glossary/glossary-terms.xml1041(glossterm)
#: ./doc/glossary/glossary-terms.xml1043(primary)
msgid "block migration"
msgstr ""
msgstr "블록 마이그레이션"
#: ./doc/glossary/glossary-terms.xml1047(para)
msgid ""
@ -1032,7 +1032,7 @@ msgstr ""
#: ./doc/glossary/glossary-terms.xml1055(glossterm)
#: ./doc/glossary/glossary-terms.xml1057(primary)
msgid "Block Storage"
msgstr ""
msgstr "블록 스토리지"
#: ./doc/glossary/glossary-terms.xml1061(para)
msgid ""
@ -1043,7 +1043,7 @@ msgstr ""
#: ./doc/glossary/glossary-terms.xml1068(glossterm)
#: ./doc/glossary/glossary-terms.xml1070(primary)
msgid "Block Storage API"
msgstr ""
msgstr "블록 스토리지 API"
#: ./doc/glossary/glossary-terms.xml1074(para)
msgid ""
@ -1091,7 +1091,7 @@ msgstr ""
#: ./doc/glossary/glossary-terms.xml1122(glossterm)
#: ./doc/glossary/glossary-terms.xml1124(primary)
msgid "Border Gateway Protocol (BGP)"
msgstr ""
msgstr "경계 경로 프로토콜 (BGP)"
#: ./doc/glossary/glossary-terms.xml1127(para)
msgid ""
@ -1120,7 +1120,7 @@ msgstr "빌더 파일"
#: ./doc/glossary/glossary-terms.xml1150(primary)
msgid "builder files"
msgstr ""
msgstr "빌더 파일들"
#: ./doc/glossary/glossary-terms.xml1154(para)
msgid ""
@ -1145,7 +1145,7 @@ msgstr "버튼 클래스"
#: ./doc/glossary/glossary-terms.xml1178(primary)
msgid "button classes"
msgstr ""
msgstr "버튼 클래스들"
#: ./doc/glossary/glossary-terms.xml1182(para)
msgid ""
@ -1229,7 +1229,7 @@ msgstr ""
#: ./doc/glossary/glossary-terms.xml1257(glossterm)
msgid "CADF"
msgstr ""
msgstr "CADF"
#: ./doc/glossary/glossary-terms.xml1259(para)
msgid ""
@ -1251,7 +1251,7 @@ msgstr ""
#: ./doc/glossary/glossary-terms.xml1280(glossterm)
#: ./doc/glossary/glossary-terms.xml1282(primary)
msgid "capability"
msgstr ""
msgstr "용량"
#: ./doc/glossary/glossary-terms.xml1288(para)
msgid ""
@ -1288,7 +1288,7 @@ msgstr "CAST"
#: ./doc/glossary/glossary-terms.xml1322(primary)
msgid "CAST (RPC primitive)"
msgstr ""
msgstr "CAST (RPC 기반)"
#: ./doc/glossary/glossary-terms.xml1326(para)
msgid ""