Imported Translations from Transifex
For more information about this automatic import see: https://wiki.openstack.org/wiki/Translations/Infrastructure Change-Id: Ic370387f33b085684d856c27b68968be6f352263
This commit is contained in:
OpenStack Proposal Bot
parent
a407886259
commit
ca44132108
@ -1,7 +1,7 @@
|
||||
msgid ""
|
||||
msgstr ""
|
||||
"Project-Id-Version: PACKAGE VERSION\n"
|
||||
"POT-Creation-Date: 2015-01-27 06:11+0000\n"
|
||||
"POT-Creation-Date: 2015-01-31 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"
|
||||
@ -1138,7 +1138,7 @@ msgstr ""
|
||||
msgid "Docker"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/admin-guide-cloud/ch_compute.xml:91(link) ./doc/admin-guide-cloud/networking/section_networking_introduction.xml:538(th) ./doc/admin-guide-cloud/telemetry/section_telemetry-system-architecture.xml:158(link)
|
||||
#: ./doc/admin-guide-cloud/ch_compute.xml:91(link) ./doc/admin-guide-cloud/networking/section_networking_introduction.xml:532(th) ./doc/admin-guide-cloud/telemetry/section_telemetry-system-architecture.xml:158(link)
|
||||
msgid "Hyper-V"
|
||||
msgstr ""
|
||||
|
||||
@ -1828,7 +1828,7 @@ msgstr ""
|
||||
msgid "Available networking plug-ins"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/admin-guide-cloud/networking/section_networking_introduction.xml:404(th) ./doc/admin-guide-cloud/networking/section_networking_introduction.xml:534(th) ./doc/admin-guide-cloud/networking/section_networking_pagination_and_sorting_support.xml:13(th)
|
||||
#: ./doc/admin-guide-cloud/networking/section_networking_introduction.xml:404(th) ./doc/admin-guide-cloud/networking/section_networking_introduction.xml:528(th) ./doc/admin-guide-cloud/networking/section_networking_pagination_and_sorting_support.xml:13(th)
|
||||
msgid "Plug-in"
|
||||
msgstr ""
|
||||
|
||||
@ -1836,7 +1836,7 @@ msgstr ""
|
||||
msgid "Documentation"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/admin-guide-cloud/networking/section_networking_introduction.xml:410(emphasis) ./doc/admin-guide-cloud/networking/section_networking_introduction.xml:544(td)
|
||||
#: ./doc/admin-guide-cloud/networking/section_networking_introduction.xml:410(emphasis) ./doc/admin-guide-cloud/networking/section_networking_introduction.xml:538(td)
|
||||
msgid "Big Switch (Floodlight REST Proxy)"
|
||||
msgstr ""
|
||||
|
||||
@ -1848,7 +1848,7 @@ msgstr ""
|
||||
msgid "This guide and <placeholder-1/>"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/admin-guide-cloud/networking/section_networking_introduction.xml:416(emphasis) ./doc/admin-guide-cloud/networking/section_networking_introduction.xml:552(td)
|
||||
#: ./doc/admin-guide-cloud/networking/section_networking_introduction.xml:416(emphasis) ./doc/admin-guide-cloud/networking/section_networking_introduction.xml:546(td)
|
||||
msgid "Brocade"
|
||||
msgstr ""
|
||||
|
||||
@ -1856,7 +1856,7 @@ msgstr ""
|
||||
msgid "https://wiki.openstack.org/wiki/Brocade-neutron-plugin"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/admin-guide-cloud/networking/section_networking_introduction.xml:422(emphasis) ./doc/admin-guide-cloud/networking/section_networking_introduction.xml:560(td)
|
||||
#: ./doc/admin-guide-cloud/networking/section_networking_introduction.xml:422(emphasis) ./doc/admin-guide-cloud/networking/section_networking_introduction.xml:554(td)
|
||||
msgid "Cisco"
|
||||
msgstr ""
|
||||
|
||||
@ -1864,7 +1864,7 @@ msgstr ""
|
||||
msgid "http://wiki.openstack.org/cisco-neutron"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/admin-guide-cloud/networking/section_networking_introduction.xml:428(emphasis) ./doc/admin-guide-cloud/networking/section_networking_introduction.xml:568(td)
|
||||
#: ./doc/admin-guide-cloud/networking/section_networking_introduction.xml:428(emphasis) ./doc/admin-guide-cloud/networking/section_networking_introduction.xml:562(td)
|
||||
msgid "Cloudbase Hyper-V"
|
||||
msgstr ""
|
||||
|
||||
@ -1872,7 +1872,7 @@ msgstr ""
|
||||
msgid "http://www.cloudbase.it/quantum-hyper-v-plugin/"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/admin-guide-cloud/networking/section_networking_introduction.xml:434(emphasis) ./doc/admin-guide-cloud/networking/section_networking_introduction.xml:576(td)
|
||||
#: ./doc/admin-guide-cloud/networking/section_networking_introduction.xml:434(emphasis) ./doc/admin-guide-cloud/networking/section_networking_introduction.xml:570(td)
|
||||
msgid "IBM SDN-VE"
|
||||
msgstr ""
|
||||
|
||||
@ -1880,7 +1880,7 @@ msgstr ""
|
||||
msgid "https://wiki.openstack.org/wiki/IBM-Neutron"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/admin-guide-cloud/networking/section_networking_introduction.xml:440(emphasis) ./doc/admin-guide-cloud/networking/section_networking_introduction.xml:584(td) ./doc/admin-guide-cloud/networking/section_networking_pagination_and_sorting_support.xml:30(td) ./doc/admin-guide-cloud/networking/section_networking-adv-config.xml:81(emphasis) ./doc/admin-guide-cloud/networking/section_networking-adv-config.xml:131(emphasis) ./doc/admin-guide-cloud/networking/section_networking-adv-config.xml:180(emphasis) ./doc/admin-guide-cloud/networking/section_networking-adv-config.xml:311(emphasis) ./doc/admin-guide-cloud/networking/section_networking-scenarios.xml:453(title)
|
||||
#: ./doc/admin-guide-cloud/networking/section_networking_introduction.xml:440(emphasis) ./doc/admin-guide-cloud/networking/section_networking_introduction.xml:578(td) ./doc/admin-guide-cloud/networking/section_networking_pagination_and_sorting_support.xml:30(td) ./doc/admin-guide-cloud/networking/section_networking-adv-config.xml:81(emphasis) ./doc/admin-guide-cloud/networking/section_networking-adv-config.xml:131(emphasis) ./doc/admin-guide-cloud/networking/section_networking-adv-config.xml:180(emphasis) ./doc/admin-guide-cloud/networking/section_networking-adv-config.xml:311(emphasis) ./doc/admin-guide-cloud/networking/section_networking-scenarios.xml:453(title)
|
||||
msgid "Linux Bridge"
|
||||
msgstr ""
|
||||
|
||||
@ -1888,7 +1888,7 @@ msgstr ""
|
||||
msgid "http://wiki.openstack.org/Neutron-Linux-Bridge-Plugin"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/admin-guide-cloud/networking/section_networking_introduction.xml:446(emphasis) ./doc/admin-guide-cloud/networking/section_networking_introduction.xml:592(td)
|
||||
#: ./doc/admin-guide-cloud/networking/section_networking_introduction.xml:446(emphasis) ./doc/admin-guide-cloud/networking/section_networking_introduction.xml:586(td)
|
||||
msgid "Midonet"
|
||||
msgstr ""
|
||||
|
||||
@ -1896,7 +1896,7 @@ msgstr ""
|
||||
msgid "http://www.midokura.com/"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/admin-guide-cloud/networking/section_networking_introduction.xml:451(emphasis) ./doc/admin-guide-cloud/networking/section_networking_introduction.xml:600(td)
|
||||
#: ./doc/admin-guide-cloud/networking/section_networking_introduction.xml:451(emphasis) ./doc/admin-guide-cloud/networking/section_networking_introduction.xml:594(td)
|
||||
msgid "ML2 (Modular Layer 2)"
|
||||
msgstr ""
|
||||
|
||||
@ -1904,7 +1904,7 @@ msgstr ""
|
||||
msgid "https://wiki.openstack.org/wiki/Neutron/ML2"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/admin-guide-cloud/networking/section_networking_introduction.xml:457(emphasis) ./doc/admin-guide-cloud/networking/section_networking_introduction.xml:608(td)
|
||||
#: ./doc/admin-guide-cloud/networking/section_networking_introduction.xml:457(emphasis) ./doc/admin-guide-cloud/networking/section_networking_introduction.xml:602(td)
|
||||
msgid "NEC OpenFlow"
|
||||
msgstr ""
|
||||
|
||||
@ -1912,7 +1912,7 @@ msgstr ""
|
||||
msgid "https://wiki.openstack.org/wiki/Neutron/NEC_OpenFlow_Plugin"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/admin-guide-cloud/networking/section_networking_introduction.xml:463(emphasis) ./doc/admin-guide-cloud/networking/section_networking_introduction.xml:616(td) ./doc/admin-guide-cloud/networking/section_networking_pagination_and_sorting_support.xml:25(td) ./doc/admin-guide-cloud/networking/section_networking-adv-config.xml:60(emphasis) ./doc/admin-guide-cloud/networking/section_networking-adv-config.xml:123(emphasis) ./doc/admin-guide-cloud/networking/section_networking-adv-config.xml:168(emphasis) ./doc/admin-guide-cloud/networking/section_networking-adv-config.xml:303(emphasis) ./doc/admin-guide-cloud/networking/section_networking-scenarios.xml:9(title)
|
||||
#: ./doc/admin-guide-cloud/networking/section_networking_introduction.xml:463(emphasis) ./doc/admin-guide-cloud/networking/section_networking_introduction.xml:610(td) ./doc/admin-guide-cloud/networking/section_networking_pagination_and_sorting_support.xml:25(td) ./doc/admin-guide-cloud/networking/section_networking-adv-config.xml:60(emphasis) ./doc/admin-guide-cloud/networking/section_networking-adv-config.xml:123(emphasis) ./doc/admin-guide-cloud/networking/section_networking-adv-config.xml:168(emphasis) ./doc/admin-guide-cloud/networking/section_networking-adv-config.xml:303(emphasis) ./doc/admin-guide-cloud/networking/section_networking-scenarios.xml:9(title)
|
||||
msgid "Open vSwitch"
|
||||
msgstr ""
|
||||
|
||||
@ -1936,7 +1936,7 @@ msgstr ""
|
||||
msgid "<placeholder-1/> and <placeholder-2/>"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/admin-guide-cloud/networking/section_networking_introduction.xml:476(emphasis) ./doc/admin-guide-cloud/networking/section_networking_introduction.xml:624(td)
|
||||
#: ./doc/admin-guide-cloud/networking/section_networking_introduction.xml:476(emphasis) ./doc/admin-guide-cloud/networking/section_networking_introduction.xml:618(td)
|
||||
msgid "PLUMgrid"
|
||||
msgstr ""
|
||||
|
||||
@ -1944,7 +1944,7 @@ msgstr ""
|
||||
msgid "https://https://wiki.openstack.org/wiki/PLUMgrid-Neutron"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/admin-guide-cloud/networking/section_networking_introduction.xml:483(emphasis) ./doc/admin-guide-cloud/networking/section_networking_introduction.xml:632(td)
|
||||
#: ./doc/admin-guide-cloud/networking/section_networking_introduction.xml:483(emphasis) ./doc/admin-guide-cloud/networking/section_networking_introduction.xml:626(td)
|
||||
msgid "VMware NSX"
|
||||
msgstr ""
|
||||
|
||||
@ -1969,58 +1969,58 @@ msgid "The <glossterm baseform=\"Modular Layer 2 (ML2) neutron plug-in\">Modular
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/admin-guide-cloud/networking/section_networking_introduction.xml:503(para)
|
||||
msgid "The ML2 framework contains two types of drivers, Type Drivers which maintain any needed type-specific network state, perform provider network validation and tenant network allocation; and Mechanism Drivers which ensure the information established by the TypeDriver is properly applied. Multiple Mechanism Drivers can simultaneously access the same network, which address complex requirements in large heterogeneous environments."
|
||||
msgid "The ML2 framework contains two types of drivers, type drivers and mechanism drivers. Type drivers maintain any needed type-specific network states, perform provider network validation and tenant network allocation. Mechanism drivers ensure the information established by the type driver is properly applied. Multiple mechanism drivers can access the same network simultaneously, which addresses complex requirements in large heterogeneous environments."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/admin-guide-cloud/networking/section_networking_introduction.xml:510(para)
|
||||
#: ./doc/admin-guide-cloud/networking/section_networking_introduction.xml:504(para)
|
||||
msgid "You can enable the ML2 plug-in by editing the <literal>core-plugin</literal> parameter in the <filename>/etc/neutron/neutron.conf</filename> file:"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/admin-guide-cloud/networking/section_networking_introduction.xml:513(replaceable)
|
||||
#: ./doc/admin-guide-cloud/networking/section_networking_introduction.xml:507(replaceable)
|
||||
msgid "neutron.plugins.ml2.plugin.Ml2Plugin"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/admin-guide-cloud/networking/section_networking_introduction.xml:515(title)
|
||||
#: ./doc/admin-guide-cloud/networking/section_networking_introduction.xml:509(title)
|
||||
msgid "Plug-in deprecation notice"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/admin-guide-cloud/networking/section_networking_introduction.xml:516(para)
|
||||
#: ./doc/admin-guide-cloud/networking/section_networking_introduction.xml:510(para)
|
||||
msgid "The Open vSwitch and Linux Bridge plug-ins are deprecated in the Havana release and will be removed in the Icehouse release. The features in these plug-ins are now part of the ML2 plug-in in the form of mechanism drivers."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/admin-guide-cloud/networking/section_networking_introduction.xml:523(title)
|
||||
#: ./doc/admin-guide-cloud/networking/section_networking_introduction.xml:517(title)
|
||||
msgid "Plug-in removal notice"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/admin-guide-cloud/networking/section_networking_introduction.xml:524(para)
|
||||
#: ./doc/admin-guide-cloud/networking/section_networking_introduction.xml:518(para)
|
||||
msgid "The Mellanox plug-in has been removed in the Kilo release."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/admin-guide-cloud/networking/section_networking_introduction.xml:527(para)
|
||||
#: ./doc/admin-guide-cloud/networking/section_networking_introduction.xml:521(para)
|
||||
msgid "Not all Networking plug-ins are compatible with all possible Compute drivers:"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/admin-guide-cloud/networking/section_networking_introduction.xml:530(caption)
|
||||
#: ./doc/admin-guide-cloud/networking/section_networking_introduction.xml:524(caption)
|
||||
msgid "Plug-in compatibility with Compute drivers"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/admin-guide-cloud/networking/section_networking_introduction.xml:535(th)
|
||||
#: ./doc/admin-guide-cloud/networking/section_networking_introduction.xml:529(th)
|
||||
msgid "Libvirt (KVM/QEMU)"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/admin-guide-cloud/networking/section_networking_introduction.xml:536(th) ./doc/admin-guide-cloud/compute/section_compute-configure-migrations.xml:292(title)
|
||||
#: ./doc/admin-guide-cloud/networking/section_networking_introduction.xml:530(th) ./doc/admin-guide-cloud/compute/section_compute-configure-migrations.xml:292(title)
|
||||
msgid "XenServer"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/admin-guide-cloud/networking/section_networking_introduction.xml:537(th)
|
||||
#: ./doc/admin-guide-cloud/networking/section_networking_introduction.xml:531(th)
|
||||
msgid "VMware"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/admin-guide-cloud/networking/section_networking_introduction.xml:539(th)
|
||||
#: ./doc/admin-guide-cloud/networking/section_networking_introduction.xml:533(th)
|
||||
msgid "Bare-metal"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/admin-guide-cloud/networking/section_networking_introduction.xml:545(td) ./doc/admin-guide-cloud/networking/section_networking_introduction.xml:553(td) ./doc/admin-guide-cloud/networking/section_networking_introduction.xml:561(td) ./doc/admin-guide-cloud/networking/section_networking_introduction.xml:572(td) ./doc/admin-guide-cloud/networking/section_networking_introduction.xml:577(td) ./doc/admin-guide-cloud/networking/section_networking_introduction.xml:585(td) ./doc/admin-guide-cloud/networking/section_networking_introduction.xml:593(td) ./doc/admin-guide-cloud/networking/section_networking_introduction.xml:601(td) ./doc/admin-guide-cloud/networking/section_networking_introduction.xml:604(td) ./doc/admin-guide-cloud/networking/section_networking_introduction.xml:609(td) ./doc/admin-guide-cloud/networking/section_networking_introduction.xml:617(td) ./doc/admin-guide-cloud/networking/section_networking_introduction.xml:625(td) ./doc/admin-guide-cloud/networking/section_networking_introduction.xml:627(td) ./doc/admin-guide-cloud/networking/section_networking_introduction.xml:633(td) ./doc/admin-guide-cloud/networking/section_networking_introduction.xml:634(td) ./doc/admin-guide-cloud/networking/section_networking_introduction.xml:635(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1501(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1508(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1515(td)
|
||||
#: ./doc/admin-guide-cloud/networking/section_networking_introduction.xml:539(td) ./doc/admin-guide-cloud/networking/section_networking_introduction.xml:547(td) ./doc/admin-guide-cloud/networking/section_networking_introduction.xml:555(td) ./doc/admin-guide-cloud/networking/section_networking_introduction.xml:566(td) ./doc/admin-guide-cloud/networking/section_networking_introduction.xml:571(td) ./doc/admin-guide-cloud/networking/section_networking_introduction.xml:579(td) ./doc/admin-guide-cloud/networking/section_networking_introduction.xml:587(td) ./doc/admin-guide-cloud/networking/section_networking_introduction.xml:595(td) ./doc/admin-guide-cloud/networking/section_networking_introduction.xml:598(td) ./doc/admin-guide-cloud/networking/section_networking_introduction.xml:603(td) ./doc/admin-guide-cloud/networking/section_networking_introduction.xml:611(td) ./doc/admin-guide-cloud/networking/section_networking_introduction.xml:619(td) ./doc/admin-guide-cloud/networking/section_networking_introduction.xml:621(td) ./doc/admin-guide-cloud/networking/section_networking_introduction.xml:627(td) ./doc/admin-guide-cloud/networking/section_networking_introduction.xml:628(td) ./doc/admin-guide-cloud/networking/section_networking_introduction.xml:629(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1501(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1508(td) ./doc/admin-guide-cloud/networking/section_networking_adv_features.xml:1515(td)
|
||||
msgid "Yes"
|
||||
msgstr ""
|
||||
|
||||
@ -11681,7 +11681,7 @@ msgid "In this example, vm1 is running on HostB."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/admin-guide-cloud/compute/section_compute-system-admin.xml:387(para)
|
||||
msgid "Select the server to which instances will be migrated:"
|
||||
msgid "Select the compute node to which instances will be migrated to:"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/admin-guide-cloud/compute/section_compute-system-admin.xml:399(para)
|
||||
@ -11733,7 +11733,7 @@ msgid "Use the <placeholder-1/> command to migrate the instances:<placeholder-2/
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/admin-guide-cloud/compute/section_compute-system-admin.xml:447(para)
|
||||
msgid "Where <replaceable>SERVER</replaceable> can be the ID or name of the server. For example:"
|
||||
msgid "Where <replaceable>SERVER</replaceable> can be the ID or name of the instance. For example:"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/admin-guide-cloud/compute/section_compute-system-admin.xml:451(para)
|
||||
@ -11741,7 +11741,7 @@ msgid "Ensure instances are migrated successfully with <placeholder-1/>. If inst
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/admin-guide-cloud/compute/section_compute-system-admin.xml:456(para)
|
||||
msgid "Although the <placeholder-1/> command is called <placeholder-2/>, under the default Compute configuration options the instances are suspended before migration."
|
||||
msgid "Although the <placeholder-1/> command is called <placeholder-2/>, under the default Compute configuration options, the instances are suspended before migration."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/admin-guide-cloud/compute/section_compute-system-admin.xml:459(para)
|
||||
|
||||
@ -1,7 +1,7 @@
|
||||
msgid ""
|
||||
msgstr ""
|
||||
"Project-Id-Version: PACKAGE VERSION\n"
|
||||
"POT-Creation-Date: 2015-01-30 06:27+0000\n"
|
||||
"POT-Creation-Date: 2015-01-31 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"
|
||||
@ -887,7 +887,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: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:56(term) ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:169(term) ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:391(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:99(term) ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:259(term) ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:583(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:56(term) ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:169(term) ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:391(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 ""
|
||||
|
||||
@ -1161,7 +1161,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: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:177(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:387(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:177(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 ""
|
||||
|
||||
@ -1177,7 +1177,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: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:435(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:630(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:435(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 ""
|
||||
|
||||
@ -1193,7 +1193,7 @@ msgstr ""
|
||||
msgid "Just as tenants in a single-site deployment need isolation from each other, so do tenants in multi-site installations. The extra challenges in multi-site designs revolve around ensuring that tenant networks function across regions. Unfortunately, OpenStack Networking does not presently support a mechanism to provide this functionality, therefore an external system may be necessary to manage these mappings. Tenant networks may contain sensitive information requiring that this mapping be accurate and consistent to ensure that a tenant in one site does not connect to a different tenant in another site."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/multi_site/section_tech_considerations_multi_site.xml:169(title) ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:564(para) ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:671(title) ./doc/arch-design/generalpurpose/section_tech_considerations_general_purpose.xml:414(title) ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:366(para) ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:472(title) ./doc/arch-design/compute_focus/section_tech_considerations_compute_focus.xml:360(title) ./doc/arch-design/storage_focus/section_architecture_storage_focus.xml:394(para) ./doc/arch-design/storage_focus/section_architecture_storage_focus.xml:512(title)
|
||||
#: ./doc/arch-design/multi_site/section_tech_considerations_multi_site.xml:169(title) ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:560(para) ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:667(title) ./doc/arch-design/generalpurpose/section_tech_considerations_general_purpose.xml:414(title) ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:366(para) ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:472(title) ./doc/arch-design/compute_focus/section_tech_considerations_compute_focus.xml:360(title) ./doc/arch-design/storage_focus/section_architecture_storage_focus.xml:394(para) ./doc/arch-design/storage_focus/section_architecture_storage_focus.xml:512(title)
|
||||
msgid "OpenStack components"
|
||||
msgstr ""
|
||||
|
||||
@ -1965,467 +1965,467 @@ msgstr ""
|
||||
msgid "Storage capacity (gigabytes or terabytes as well as Input/Output Operations Per Second (<glossterm>IOPS</glossterm>)"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:75(para)
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:71(para)
|
||||
msgid "Server hardware is evaluated around four conflicting dimensions."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:79(term) ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:35(term) ./doc/arch-design/storage_focus/section_architecture_storage_focus.xml:160(term)
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:75(term) ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:35(term) ./doc/arch-design/storage_focus/section_architecture_storage_focus.xml:160(term)
|
||||
msgid "Server density"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:81(para) ./doc/arch-design/storage_focus/section_architecture_storage_focus.xml:162(para)
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:77(para) ./doc/arch-design/storage_focus/section_architecture_storage_focus.xml:162(para)
|
||||
msgid "A measure of how many servers can fit into a given measure of physical space, such as a rack unit [U]."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:87(term) ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:42(term) ./doc/arch-design/storage_focus/section_architecture_storage_focus.xml:168(term)
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:83(term) ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:42(term) ./doc/arch-design/storage_focus/section_architecture_storage_focus.xml:168(term)
|
||||
msgid "Resource capacity"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:89(para) ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:44(para) ./doc/arch-design/storage_focus/section_architecture_storage_focus.xml:170(para)
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:85(para) ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:44(para) ./doc/arch-design/storage_focus/section_architecture_storage_focus.xml:170(para)
|
||||
msgid "The number of CPU cores, how much RAM, or how much storage a given server will deliver."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:95(term) ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:289(term) ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:49(term) ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:201(term) ./doc/arch-design/storage_focus/section_architecture_storage_focus.xml:76(term) ./doc/arch-design/storage_focus/section_architecture_storage_focus.xml:176(term)
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:91(term) ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:285(term) ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:49(term) ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:201(term) ./doc/arch-design/storage_focus/section_architecture_storage_focus.xml:76(term) ./doc/arch-design/storage_focus/section_architecture_storage_focus.xml:176(term)
|
||||
msgid "Expandability"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:97(para) ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:51(para) ./doc/arch-design/storage_focus/section_architecture_storage_focus.xml:178(para)
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:93(para) ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:51(para) ./doc/arch-design/storage_focus/section_architecture_storage_focus.xml:178(para)
|
||||
msgid "The number of additional resources that can be added to a server before it has reached its limit."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:105(para) ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:58(para)
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:101(para) ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:58(para)
|
||||
msgid "The relative purchase price of the hardware weighted against the level of design effort needed to build the system."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:111(para)
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:107(para)
|
||||
msgid "Increasing server density means sacrificing resource capacity or expandability, however, increasing resource capacity and expandability increases cost and decreases server density. As a result, determining the best server hardware for a general purpose OpenStack architecture means understanding how choice of form factor will impact the rest of the design. The following list outlines the form factors to choose from:"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:121(para)
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:117(para)
|
||||
msgid "Blade servers typically support dual-socket multi-core CPUs, which is the configuration generally considered to be the \"sweet spot\" for a general purpose cloud deployment. Blades also offer outstanding density. As an example, both HP BladeSystem and Dell PowerEdge M1000e support up to 16 servers in only 10 rack units. However, the blade servers themselves often have limited storage and networking capacity. Additionally, the expandability of many blade servers can be limited."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:133(para)
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:129(para)
|
||||
msgid "1U rack-mounted servers occupy only a single rack unit. Their benefits include high density, support for dual-socket multi-core CPUs, and support for reasonable RAM amounts. This form factor offers limited storage capacity, limited network capacity, and limited expandability."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:141(para)
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:137(para)
|
||||
msgid "2U rack-mounted servers offer the expanded storage and networking capacity that 1U servers tend to lack, but with a corresponding decrease in server density (half the density offered by 1U rack-mounted servers)."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:148(para)
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:144(para)
|
||||
msgid "Larger rack-mounted servers, such as 4U servers, will tend to offer even greater CPU capacity, often supporting four or even eight CPU sockets. These servers often have much greater expandability so will provide the best option for upgradability. This means, however, that the servers have a much lower server density and a much greater hardware cost."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:157(para)
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:153(para)
|
||||
msgid "\"Sled servers\" are rack-mounted servers that support multiple independent servers in a single 2U or 3U enclosure. This form factor offers increased density over typical 1U-2U rack-mounted servers but tends to suffer from limitations in the amount of storage or network capacity each individual server supports."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:166(para)
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:162(para)
|
||||
msgid "The best form factor for server hardware supporting a general purpose OpenStack cloud is driven by outside business and cost factors. No single reference architecture will apply to all implementations; the decision must flow from user requirements, technical considerations, and operational considerations. Here are some of the key factors that influence the selection of server hardware:"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:176(term) ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:124(term) ./doc/arch-design/storage_focus/section_architecture_storage_focus.xml:274(term)
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:172(term) ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:124(term) ./doc/arch-design/storage_focus/section_architecture_storage_focus.xml:274(term)
|
||||
msgid "Instance density"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:178(para)
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:174(para)
|
||||
msgid "Sizing is an important consideration for a general purpose OpenStack cloud. The expected or anticipated number of instances that each hypervisor can host is a common metric used in sizing the deployment. The selected server hardware needs to support the expected or anticipated instance density."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:188(term) ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:134(term) ./doc/arch-design/storage_focus/section_architecture_storage_focus.xml:284(term)
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:184(term) ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:134(term) ./doc/arch-design/storage_focus/section_architecture_storage_focus.xml:284(term)
|
||||
msgid "Host density"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:190(para)
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:186(para)
|
||||
msgid "Physical data centers have limited physical space, power, and cooling. The number of hosts (or hypervisors) that can be fitted into a given metric (rack, rack unit, or floor tile) is another important method of sizing. Floor weight is an often overlooked consideration. The data center floor must be able to support the weight of the proposed number of hosts within a rack or set of racks. These factors need to be applied as part of the host density calculation and server hardware selection."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:203(term)
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:199(term)
|
||||
msgid "Power density"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:205(para)
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:201(para)
|
||||
msgid "Data centers have a specified amount of power fed to a given rack or set of racks. Older data centers may have a power density as power as low as 20 AMPs per rack, while more recent data centers can be architected to support power densities as high as 120 AMP per rack. The selected server hardware must take power density into account."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:215(term)
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:211(term)
|
||||
msgid "Network connectivity"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:217(para)
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:213(para)
|
||||
msgid "The selected server hardware must have the appropriate number of network connections, as well as the right type of network connections, in order to support the proposed architecture. Ensure that, at a minimum, there are at least two diverse network connections coming into each rack. For architectures requiring even more redundancy, it might be necessary to confirm that the network connections are from diverse telecom providers. Many data centers have that capacity available."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:231(para)
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:227(para)
|
||||
msgid "The selection of form factors or architectures affects the selection of server hardware. For example, if the design is a scale-out storage architecture, then the server hardware selection will require careful consideration when matching the requirements set to the commercial solution."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:235(para)
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:231(para)
|
||||
msgid "Ensure that the selected server hardware is configured to support enough storage capacity (or storage expandability) to match the requirements of selected scale-out storage solution. For example, if a centralized storage solution is required, such as a centralized storage array from a storage vendor that has InfiniBand or FDDI connections, the server hardware will need to have appropriate network adapters installed to be compatible with the storage array vendor's specifications."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:244(para)
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:240(para)
|
||||
msgid "Similarly, the network architecture will have an impact on the server hardware selection and vice versa. For example, make sure that the server is configured with enough additional network ports and expansion cards to support all of the networks required. There is variability in network expansion cards, so it is important to be aware of potential impacts or interoperability issues with other components in the architecture."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:253(title)
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:249(title)
|
||||
msgid "Selecting storage hardware"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:254(para)
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:250(para)
|
||||
msgid "Storage hardware architecture is largely determined by the selected storage architecture. The selection of storage architecture, as well as the corresponding storage hardware, is determined by evaluating possible solutions against the critical factors, the user requirements, technical considerations, and operational considerations. Factors that need to be incorporated into the storage architecture include:"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:265(para)
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:261(para)
|
||||
msgid "Storage can be a significant portion of the overall system cost. For an organization that is concerned with vendor support, a commercial storage solution is advisable, although it comes with a higher price tag. If initial capital expenditure requires minimization, designing a system based on commodity hardware would apply. The trade-off is potentially higher support costs and a greater risk of incompatibility and interoperability issues."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:277(term) ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:525(term) ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:189(term) ./doc/arch-design/storage_focus/section_architecture_storage_focus.xml:62(term)
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:273(term) ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:521(term) ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:189(term) ./doc/arch-design/storage_focus/section_architecture_storage_focus.xml:62(term)
|
||||
msgid "Scalability"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:279(para)
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:275(para)
|
||||
msgid "Scalability, along with expandability, is a major consideration in a general purpose OpenStack cloud. It might be difficult to predict the final intended size of the implementation as there are no established usage patterns for a general purpose cloud. It might become necessary to expand the initial deployment in order to accommodate growth and user demand."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:291(para)
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:287(para)
|
||||
msgid "Expandability is a major architecture factor for storage solutions with general purpose OpenStack cloud. A storage solution that expands to 50PB is considered more expandable than a solution that only scales to 10PB. This metric is related to, but different, from scalability, which is a measure of the solution's performance as it expands. For example, the storage architecture for a cloud that is intended for a development platform may not have the same expandability and scalability requirements as a cloud that is intended for a commercial product."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:305(para)
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:301(para)
|
||||
msgid "Using a scale-out storage solution with direct-attached storage (DAS) in the servers is well suited for a general purpose OpenStack cloud. For example, it is possible to populate storage in either the compute hosts similar to a grid computing solution, or into hosts dedicated to providing block storage exclusively. When deploying storage in the compute hosts appropriate hardware, that can support both the storage and compute services on the same hardware, will be required."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:313(para)
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:309(para)
|
||||
msgid "Understanding the requirements of cloud services will help determine what scale-out solution should be used. Determining if a single, highly expandable and highly vertical, scalable, centralized storage array should be included in the design. Once an approach has been determined, the storage hardware needs to be selected based on this criteria."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:319(para)
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:315(para)
|
||||
msgid "This list expands upon the potential impacts for including a particular storage architecture (and corresponding storage hardware) into the design for a general purpose OpenStack cloud:"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:325(term) ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:512(term) ./doc/arch-design/introduction/section_methodology.xml:182(term) ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:237(term) ./doc/arch-design/storage_focus/section_architecture_storage_focus.xml:116(term)
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:321(term) ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:508(term) ./doc/arch-design/introduction/section_methodology.xml:182(term) ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:237(term) ./doc/arch-design/storage_focus/section_architecture_storage_focus.xml:116(term)
|
||||
msgid "Connectivity"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:327(para)
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:323(para)
|
||||
msgid "Ensure that, if storage protocols other than Ethernet are part of the storage solution, the appropriate hardware has been selected. If a centralized storage array is selected, ensure that the hypervisor will be able to connect to that storage array for image storage."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:336(term)
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:332(term)
|
||||
msgid "Usage"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:338(para)
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:334(para)
|
||||
msgid "How the particular storage architecture will be used is critical for determining the architecture. Some of the configurations that will influence the architecture include whether it will be used by the hypervisors for ephemeral instance storage or if OpenStack Object Storage will use it for object storage."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:347(term)
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:343(term)
|
||||
msgid "Instance and image locations"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:349(para)
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:345(para)
|
||||
msgid "Where instances and images will be stored will influence the architecture."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:355(term) ./doc/arch-design/storage_focus/section_architecture_storage_focus.xml:145(term)
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:351(term) ./doc/arch-design/storage_focus/section_architecture_storage_focus.xml:145(term)
|
||||
msgid "Server hardware"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:357(para)
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:353(para)
|
||||
msgid "If the solution is a scale-out storage architecture that includes DAS, it will affect the server hardware selection. This could ripple into the decisions that affect host density, instance density, power density, OS-hypervisor, management tools and others."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:366(para)
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:362(para)
|
||||
msgid "General purpose OpenStack cloud has multiple options. The key factors that will have an influence on selection of storage hardware for a general purpose OpenStack cloud are as follows:"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:372(term)
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:368(term)
|
||||
msgid "Capacity"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:374(para)
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:370(para)
|
||||
msgid "Hardware resources selected for the resource nodes should be capable of supporting enough storage for the cloud services. Defining the initial requirements and ensuring the design can support adding capacity is important. Hardware nodes selected for object storage should be capable of support a large number of inexpensive disks with no reliance on RAID controller cards. Hardware nodes selected for block storage should be capable of supporting high speed storage solutions and RAID controller cards to provide performance and redundancy to storage at a hardware level. Selecting hardware RAID controllers that automatically repair damaged arrays will assist with the replacement and repair of degraded or destroyed storage devices."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:393(para)
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:389(para)
|
||||
msgid "Disks selected for object storage services do not need to be fast performing disks. We recommend that object storage nodes take advantage of the best cost per terabyte available for storage. Contrastingly, disks chosen for block storage services should take advantage of performance boosting features that may entail the use of SSDs or flash storage to provide high performance block storage pools. Storage performance of ephemeral disks used for instances should also be taken into consideration. If compute pools are expected to have a high utilization of ephemeral storage, or requires very high performance, it would be advantageous to deploy similar hardware solutions to block storage."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:408(term)
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:404(term)
|
||||
msgid "Fault tolerance"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:410(para)
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:406(para)
|
||||
msgid "Object storage resource nodes have no requirements for hardware fault tolerance or RAID controllers. It is not necessary to plan for fault tolerance within the object storage hardware because the object storage service provides replication between zones as a feature of the service. Block storage nodes, compute nodes and cloud controllers should all have fault tolerance built in at the hardware level by making use of hardware RAID controllers and varying levels of RAID configuration. The level of RAID chosen should be consistent with the performance and availability requirements of the cloud."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:428(title) ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:281(title)
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:424(title) ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:281(title)
|
||||
msgid "Selecting networking hardware"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:429(para)
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:425(para)
|
||||
msgid "Selecting network architecture determines which network hardware will be used. Networking software is determined by the selected networking hardware. For example, selecting networking hardware that only supports Gigabit Ethernet (GbE) will impact the overall design. Similarly, deciding to use 10 Gigabit Ethernet (10GbE) will have a number of impacts on various areas of the overall design."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:436(para)
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:432(para)
|
||||
msgid "There are more subtle design impacts that need to be considered. The selection of certain networking hardware (and the networking software) affects the management tools that can be used. There are exceptions to this; the rise of \"open\" networking software that supports a range of networking hardware means that there are instances where the relationship between networking hardware and networking software are not as tightly defined. An example of this type of software is Cumulus Linux, which is capable of running on a number of switch vendor's hardware solutions."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:446(para) ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:282(para) ./doc/arch-design/storage_focus/section_architecture_storage_focus.xml:315(para)
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:442(para) ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:282(para) ./doc/arch-design/storage_focus/section_architecture_storage_focus.xml:315(para)
|
||||
msgid "Some of the key considerations that should be included in the selection of networking hardware include:"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:450(term) ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:286(term) ./doc/arch-design/storage_focus/section_architecture_storage_focus.xml:319(term)
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:446(term) ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:286(term) ./doc/arch-design/storage_focus/section_architecture_storage_focus.xml:319(term)
|
||||
msgid "Port count"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:452(para) ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:288(para)
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:448(para) ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:288(para)
|
||||
msgid "The design will require networking hardware that has the requisite port count."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:457(term) ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:293(term) ./doc/arch-design/storage_focus/section_architecture_storage_focus.xml:326(term)
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:453(term) ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:293(term) ./doc/arch-design/storage_focus/section_architecture_storage_focus.xml:326(term)
|
||||
msgid "Port density"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:459(para)
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:455(para)
|
||||
msgid "The network design will be affected by the physical space that is required to provide the requisite port count. A higher port density is preferred, as it leaves more rack space for compute or storage components that may be required by the design. This can also lead into concerns about fault domains and power density that should be considered. Higher density switches are more expensive and should also be considered, as it is important not to over design the network if it is not required."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:472(term) ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:308(term) ./doc/arch-design/storage_focus/section_architecture_storage_focus.xml:342(term)
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:468(term) ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:308(term) ./doc/arch-design/storage_focus/section_architecture_storage_focus.xml:342(term)
|
||||
msgid "Port speed"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:474(para) ./doc/arch-design/storage_focus/section_architecture_storage_focus.xml:344(para)
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:470(para) ./doc/arch-design/storage_focus/section_architecture_storage_focus.xml:344(para)
|
||||
msgid "The networking hardware must support the proposed network speed, for example: 1GbE, 10GbE, or 40GbE (or even 100GbE)."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:481(term) ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:316(term) ./doc/arch-design/storage_focus/section_architecture_storage_focus.xml:350(term)
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:477(term) ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:316(term) ./doc/arch-design/storage_focus/section_architecture_storage_focus.xml:350(term)
|
||||
msgid "Redundancy"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:483(para)
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:479(para)
|
||||
msgid "The level of network hardware redundancy required is influenced by the user requirements for high availability and cost considerations. Network redundancy can be achieved by adding redundant power supplies or paired switches. If this is a requirement, the hardware will need to support this configuration."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:492(term) ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:328(term) ./doc/arch-design/storage_focus/section_architecture_storage_focus.xml:363(term)
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:488(term) ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:328(term) ./doc/arch-design/storage_focus/section_architecture_storage_focus.xml:363(term)
|
||||
msgid "Power requirements"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:494(para)
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:490(para)
|
||||
msgid "Ensure that the physical data center provides the necessary power for the selected network hardware."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:498(para)
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:494(para)
|
||||
msgid "This may be an issue for spine switches in a leaf and spine fabric, or end of row (EoR) switches."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:505(para)
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:501(para)
|
||||
msgid "There is no single best practice architecture for the networking hardware supporting a general purpose OpenStack cloud that will apply to all implementations. Some of the key factors that will have a strong influence on selection of networking hardware include:"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:514(para)
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:510(para)
|
||||
msgid "All nodes within an OpenStack cloud require network connectivity. In some cases, nodes require access to more than one network segment. The design must encompass sufficient network capacity and bandwidth to ensure that all communications within the cloud, both north-south and east-west traffic have sufficient resources available."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:527(para)
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:523(para)
|
||||
msgid "The network design should encompass a physical and logical network design that can be easily expanded upon. Network hardware should offer the appropriate types of interfaces and speeds that are required by the hardware nodes."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:535(term) ./doc/arch-design/generalpurpose/section_tech_considerations_general_purpose.xml:588(title) ./doc/arch-design/storage_focus/section_user_requirements_storage_focus.xml:113(term)
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:531(term) ./doc/arch-design/generalpurpose/section_tech_considerations_general_purpose.xml:588(title) ./doc/arch-design/storage_focus/section_user_requirements_storage_focus.xml:113(term)
|
||||
msgid "Availability"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:537(para)
|
||||
msgid "To ensure that access to nodes within the cloud is not interrupted, we recommend that the network architecture identify any single points of failure and provide some level of redundancy or fault tolerance. With regard to the network infrastructure itself, this often involves use of networking protocols such as LACP, VRRP or others to achieve a highly available network connection. In addition, it is important to consider the networking implications on API availability. In order to ensure that the APIs, and potentially other services in the cloud are highly available, we recommend you design load balancing solution within the network architecture to accommodate for these requirements."
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:533(para)
|
||||
msgid "To ensure that access to nodes within the cloud is not interrupted, we recommend that the network architecture identify any single points of failure and provide some level of redundancy or fault tolerance. With regard to the network infrastructure itself, this often involves use of networking protocols such as LACP, VRRP or others to achieve a highly available network connection. In addition, it is important to consider the networking implications on API availability. In order to ensure that the APIs, and potentially other services in the cloud are highly available, we recommend you design a load balancing solution within the network architecture to accommodate for these requirements."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:556(title) ./doc/arch-design/generalpurpose/section_tech_considerations_general_purpose.xml:294(title) ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:358(title) ./doc/arch-design/storage_focus/section_architecture_storage_focus.xml:386(title)
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:552(title) ./doc/arch-design/generalpurpose/section_tech_considerations_general_purpose.xml:294(title) ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:358(title) ./doc/arch-design/storage_focus/section_architecture_storage_focus.xml:386(title)
|
||||
msgid "Software selection"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:557(para)
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:553(para)
|
||||
msgid "Software selection for a general purpose OpenStack architecture design needs to include these three areas:"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:561(para) ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:363(para) ./doc/arch-design/storage_focus/section_architecture_storage_focus.xml:391(para)
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:557(para) ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:363(para) ./doc/arch-design/storage_focus/section_architecture_storage_focus.xml:391(para)
|
||||
msgid "Operating system (OS) and hypervisor"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:567(para) ./doc/arch-design/generalpurpose/section_tech_considerations_general_purpose.xml:454(title) ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:369(para) ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:524(title) ./doc/arch-design/storage_focus/section_architecture_storage_focus.xml:397(para) ./doc/arch-design/storage_focus/section_architecture_storage_focus.xml:562(title)
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:563(para) ./doc/arch-design/generalpurpose/section_tech_considerations_general_purpose.xml:454(title) ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:369(para) ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:524(title) ./doc/arch-design/storage_focus/section_architecture_storage_focus.xml:397(para) ./doc/arch-design/storage_focus/section_architecture_storage_focus.xml:562(title)
|
||||
msgid "Supplemental software"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:572(title) ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:376(title) ./doc/arch-design/storage_focus/section_architecture_storage_focus.xml:403(title)
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:568(title) ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:376(title) ./doc/arch-design/storage_focus/section_architecture_storage_focus.xml:403(title)
|
||||
msgid "Operating system and hypervisor"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:573(para)
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:569(para)
|
||||
msgid "The operating system (OS) and hypervisor have a significant impact on the overall design. Selecting a particular operating system and hypervisor can directly affect server hardware selection. Make sure the storage hardware and topology support the selected operating system and hypervisor combination. Also ensure the networking hardware selection and topology will work with the chosen operating system and hypervisor combination. For example, if the design uses Link Aggregation Control Protocol (LACP), the OS and hypervisor both need to support it."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:583(para) ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:387(para) ./doc/arch-design/storage_focus/section_architecture_storage_focus.xml:413(para)
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:579(para) ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:387(para) ./doc/arch-design/storage_focus/section_architecture_storage_focus.xml:413(para)
|
||||
msgid "Some areas that could be impacted by the selection of OS and hypervisor include:"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:589(para)
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:585(para)
|
||||
msgid "Selecting a commercially supported hypervisor, such as Microsoft Hyper-V, will result in a different cost model rather than community-supported open source hypervisors including <glossterm baseform=\"kernel-based VM (KVM)\">KVM</glossterm>, Kinstance or <glossterm>Xen</glossterm>. When comparing open source OS solutions, choosing Ubuntu over Red Hat (or vice versa) will have an impact on cost due to support contracts."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:601(term) ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:404(term) ./doc/arch-design/storage_focus/section_architecture_storage_focus.xml:431(term)
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:597(term) ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:404(term) ./doc/arch-design/storage_focus/section_architecture_storage_focus.xml:431(term)
|
||||
msgid "Supportability"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:603(para)
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:599(para)
|
||||
msgid "Depending on the selected hypervisor, staff should have the appropriate training and knowledge to support the selected OS and hypervisor combination. If they do not, training will need to be provided which could have a cost impact on the design."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:612(term) ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:414(term) ./doc/arch-design/storage_focus/section_architecture_storage_focus.xml:448(term)
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:608(term) ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:414(term) ./doc/arch-design/storage_focus/section_architecture_storage_focus.xml:448(term)
|
||||
msgid "Management tools"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:614(para) ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:416(para)
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:610(para) ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:416(para)
|
||||
msgid "The management tools used for Ubuntu and Kinstance differ from the management tools for VMware vSphere. Although both OS and hypervisor combinations are supported by OpenStack, there will be very different impacts to the rest of the design as a result of the selection of one combination versus the other."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:624(term) ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:425(term) ./doc/arch-design/storage_focus/section_architecture_storage_focus.xml:460(term)
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:620(term) ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:425(term) ./doc/arch-design/storage_focus/section_architecture_storage_focus.xml:460(term)
|
||||
msgid "Scale and performance"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:626(para)
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:622(para)
|
||||
msgid "Ensure that selected OS and hypervisor combinations meet the appropriate scale and performance requirements. The chosen architecture will need to meet the targeted instance-host ratios with the selected OS-hypervisor combinations."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:636(para)
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:632(para)
|
||||
msgid "Ensure that the design can accommodate regular periodic installations of application security patches while maintaining required workloads. The frequency of security patches for the proposed OS-hypervisor combination will have an impact on performance and the patch installation process could affect maintenance windows."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:646(term) ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:446(term) ./doc/arch-design/storage_focus/section_architecture_storage_focus.xml:483(term)
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:642(term) ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:446(term) ./doc/arch-design/storage_focus/section_architecture_storage_focus.xml:483(term)
|
||||
msgid "Supported features"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:648(para)
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:644(para)
|
||||
msgid "Determine which features of OpenStack are required. This will often determine the selection of the OS-hypervisor combination. Some features are only available with specific OSs or hypervisors. For example, if certain features are not available, the design might need to be modified to meet the user requirements."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:657(term) ./doc/arch-design/generalpurpose/section_tech_considerations_general_purpose.xml:343(term) ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:457(term) ./doc/arch-design/storage_focus/section_architecture_storage_focus.xml:495(term)
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:653(term) ./doc/arch-design/generalpurpose/section_tech_considerations_general_purpose.xml:343(term) ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:457(term) ./doc/arch-design/storage_focus/section_architecture_storage_focus.xml:495(term)
|
||||
msgid "Interoperability"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:659(para)
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:655(para)
|
||||
msgid "You will need to consider how the OS and hypervisor combination interactions with other operating systems and hypervisors, including other software solutions. Operational troubleshooting tools for one OS-hypervisor combination may differ from the tools used for another OS-hypervisor combination and, as a result, the design will need to address if the two sets of tools need to interoperate."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:672(para)
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:668(para)
|
||||
msgid "Selecting which OpenStack components are included in the overall design can have a significant impact. Some OpenStack components, like compute and Image Service, are required in every architecture. Other components, like Orchestration, are not always required."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:676(para)
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:672(para)
|
||||
msgid "Excluding certain OpenStack components can limit or constrain the functionality of other components. For example, if the architecture includes Orchestration but excludes Telemetry, then the design will not be able to take advantage of Orchestrations' auto scaling functionality. It is important to research the component interdependencies in conjunction with the technical requirements before deciding on the final architecture."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:684(title)
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:680(title)
|
||||
msgid "Supplemental components"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:685(para)
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:681(para)
|
||||
msgid "While OpenStack is a fairly complete collection of software projects for building a platform for cloud services, there are invariably additional pieces of software that need to be considered in any given OpenStack design."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:692(title) ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:530(title) ./doc/arch-design/storage_focus/section_architecture_storage_focus.xml:568(title)
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:688(title) ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:530(title) ./doc/arch-design/storage_focus/section_architecture_storage_focus.xml:568(title)
|
||||
msgid "Networking software"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:693(para)
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:689(para)
|
||||
msgid "OpenStack Networking provides a wide variety of networking services for instances. There are many additional networking software packages that can be useful when managing OpenStack components. Some examples include:"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:699(para)
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:695(para)
|
||||
msgid "Software to provide load balancing"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:704(para)
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:700(para)
|
||||
msgid "Network redundancy protocols"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:709(para)
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:705(para)
|
||||
msgid "Routing daemons"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:714(para)
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:710(para)
|
||||
msgid "Some of these software packages are described in more detail in the <citetitle>OpenStack High Availability Guide</citetitle> (refer to the <link href=\"http://docs.openstack.org/high-availability-guide/content/ch-network.html\">Network controller cluster stack chapter</link> of the OpenStack High Availability Guide)."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:720(para)
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:716(para)
|
||||
msgid "For a general purpose OpenStack cloud, the OpenStack infrastructure components need to be highly available. If the design does not include hardware load balancing, networking software packages like HAProxy will need to be included."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:727(title) ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:546(title) ./doc/arch-design/storage_focus/section_architecture_storage_focus.xml:585(title)
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:723(title) ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:546(title) ./doc/arch-design/storage_focus/section_architecture_storage_focus.xml:585(title)
|
||||
msgid "Management software"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:728(para)
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:724(para)
|
||||
msgid "Selected supplemental software solution impacts and affects the overall OpenStack cloud design. This includes software for providing clustering, logging, monitoring and alerting."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:732(para)
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:728(para)
|
||||
msgid "Inclusion of clustering software, such as Corosync or Pacemaker, is determined primarily by the availability requirements. The impact of including (or not including) these software packages is primarily determined by the availability of the cloud infrastructure and the complexity of supporting the configuration after it is deployed. The <link href=\"http://docs.openstack.org/high-availability-guide/\"><citetitle>OpenStack High Availability Guide</citetitle></link> provides more details on the installation and configuration of Corosync and Pacemaker, should these packages need to be included in the design."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:743(para)
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:739(para)
|
||||
msgid "Requirements for logging, monitoring, and alerting are determined by operational considerations. Each of these sub-categories includes a number of various options. For example, in the logging sub-category one might consider Logstash, Splunk, instanceware Log Insight, or some other log aggregation-consolidation tool. Logs should be stored in a centralized location to make it easier to perform analytics against the data. Log data analytics engines can also provide automation and issue notification by providing a mechanism to both alert and automatically attempt to remediate some of the more commonly known issues."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:753(para)
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:749(para)
|
||||
msgid "If these software packages are required, the design must account for the additional resource consumption (CPU, RAM, storage, and network bandwidth). Some other potential design impacts include:"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:759(para) ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:573(para)
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:755(para) ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:573(para)
|
||||
msgid "OS-hypervisor combination: Ensure that the selected logging, monitoring, or alerting tools support the proposed OS-hypervisor combination."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:764(para) ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:578(para) ./doc/arch-design/storage_focus/section_architecture_storage_focus.xml:625(para)
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:760(para) ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:578(para) ./doc/arch-design/storage_focus/section_architecture_storage_focus.xml:625(para)
|
||||
msgid "Network hardware: The network hardware selection needs to be supported by the logging, monitoring, and alerting software."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:771(title) ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:584(title) ./doc/arch-design/storage_focus/section_architecture_storage_focus.xml:631(title)
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:767(title) ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:584(title) ./doc/arch-design/storage_focus/section_architecture_storage_focus.xml:631(title)
|
||||
msgid "Database software"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:772(para)
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:768(para)
|
||||
msgid "OpenStack components often require access to back-end database services to store state and configuration information. Selecting an appropriate back-end database that satisfies the availability and fault tolerance requirements of the OpenStack services is required. OpenStack services supports connecting to a database that is supported by the SQLAlchemy python drivers, however, most common database deployments make use of MySQL or variations of it. We recommend that the database, which provides back-end service within a general purpose cloud, be made highly available when using an available technology which can accomplish that goal."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:786(title)
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:782(title)
|
||||
msgid "Addressing performance-sensitive workloads"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:787(para)
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:783(para)
|
||||
msgid "Although one of the key defining factors for a general purpose OpenStack cloud is that performance is not a determining factor, there may still be some performance-sensitive workloads deployed on the general purpose OpenStack cloud. For design guidance on performance-sensitive workloads, we recommend that you refer to the focused scenarios later in this guide. The resource-focused guides can be used as a supplement to this guide to help with decisions regarding performance-sensitive workloads."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:799(title)
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:795(title)
|
||||
msgid "Compute-focused workloads"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:800(para)
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:796(para)
|
||||
msgid "In an OpenStack cloud that is compute-focused, there are some design choices that can help accommodate those workloads. Compute-focused workloads demand more CPU and memory resources with lower priority given to storage and network performance. For guidance on designing for this type of cloud, please refer to <xref linkend=\"compute_focus\"/>."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:808(title)
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:804(title)
|
||||
msgid "Network-focused workloads"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:809(para)
|
||||
msgid "In a network-focused OpenStack cloud some design choices can improve the performance of these types of workloads. Network-focused workloads have extreme demands on network bandwidth and services that require specialized consideration and planning. For guidance on designing for this type of cloud, please refer to <xref linkend=\"network_focus\"/>."
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:805(para)
|
||||
msgid "In a network-focused OpenStack cloud, some design choices can improve the performance of these types of workloads. Network-focused workloads have extreme demands on network bandwidth and services that require specialized consideration and planning. For guidance on designing for this type of cloud, please refer to <xref linkend=\"network_focus\"/>."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:817(title)
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:813(title)
|
||||
msgid "Storage-focused workloads"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:818(para)
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:814(para)
|
||||
msgid "Storage focused OpenStack clouds need to be designed to accommodate workloads that have extreme demands on either object or block storage services. For guidance on designing for this type of cloud, please refer to <xref linkend=\"storage_focus\"/>."
|
||||
msgstr ""
|
||||
|
||||
@ -2526,7 +2526,7 @@ msgid "Security should be implemented according to asset, threat, and vulnerabil
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/generalpurpose/section_operational_considerations_general_purpose.xml:9(para)
|
||||
msgid "In the planning and design phases of the build out, it is important to include the operation's function. Operational factors affect the design choices for general purpose cloud, and operations staff are often tasked with the maintenance of cloud environments for larger installations."
|
||||
msgid "In the planning and design phases of the build out, it is important to include the operation's function. Operational factors affect the design choices for a general purpose cloud, and operations staff are often tasked with the maintenance of cloud environments for larger installations."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/generalpurpose/section_operational_considerations_general_purpose.xml:14(para)
|
||||
@ -2546,7 +2546,7 @@ msgid "Network uptime guarantees affecting switch design, which might require re
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/generalpurpose/section_operational_considerations_general_purpose.xml:33(para)
|
||||
msgid "Network security policies requirements needing to be factored in to deployments."
|
||||
msgid "Network security policies requirements need to be factored in to deployments."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/generalpurpose/section_operational_considerations_general_purpose.xml:38(title) ./doc/arch-design/compute_focus/section_operational_considerations_compute_focus.xml:36(title)
|
||||
@ -2554,7 +2554,7 @@ msgid "Support and maintainability"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/generalpurpose/section_operational_considerations_general_purpose.xml:39(para)
|
||||
msgid "To be able to support and maintain an installation, OpenStack cloud management requires operations staff to understand and comprehend design architecture content. The operations and engineering staff skill level, and level of separation, are dependent on size and purpose of the installation. Large cloud service providers, or a telecom provider, are more likely to be managed by specially trained, dedicated operations organization. Smaller implementations are more likely to rely on support staff that need to take on combined engineering, design and operations functions."
|
||||
msgid "To be able to support and maintain an installation, OpenStack cloud management requires operations staff to understand and comprehend design architecture content. The operations and engineering staff skill level, and level of separation, are dependent on size and purpose of the installation. Large cloud service providers, or telecom providers, are more likely to be managed by a specially trained, dedicated operations organization. Smaller implementations are more likely to rely on support staff that need to take on combined engineering, design and operations functions."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/generalpurpose/section_operational_considerations_general_purpose.xml:48(para)
|
||||
@ -2630,7 +2630,7 @@ msgid "Compute nodes automatically attach to OpenStack clouds, resulting in a ho
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/generalpurpose/section_operational_considerations_general_purpose.xml:137(para)
|
||||
msgid "Assessing the average workloads and increasing the number of instances that can run within the compute environment by adjusting the overcommit ratio is another option. It is important to remember changing the CPU overcommit ratio can have a detrimental effect and cause potential increase in noisy neighbor. The additional risk of increasing the overcommit ratio is more instances failing when a compute host fails."
|
||||
msgid "Assessing the average workloads and increasing the number of instances that can run within the compute environment by adjusting the overcommit ratio is another option. It is important to remember that changing the CPU overcommit ratio can have a detrimental effect and cause a potential increase in a noisy neighbor. The additional risk of increasing the overcommit ratio is more instances failing when a compute host fails."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/generalpurpose/section_operational_considerations_general_purpose.xml:143(para)
|
||||
@ -2732,7 +2732,7 @@ msgid "We recommend you design compute resources as pools of resources which wil
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/generalpurpose/section_tech_considerations_general_purpose.xml:43(para)
|
||||
msgid "To design for the best use of available resources by applications running in the cloud, we recommend you design more than one compute resource pool. Each independent resource pool should be designed to provide service for specific flavors of instances or groupings of flavors. For the purpose of this book, \"instance\" refers to a virtual machines and the operating system running on the virtual machine. Designing multiple resource pools helps to ensure that, as instances are scheduled onto compute hypervisors, each independent node's resources will be allocated in a way that makes the most efficient use of available hardware. This is commonly referred to as bin packing."
|
||||
msgid "To design for the best use of available resources by applications running in the cloud, we recommend you design more than one compute resource pool. Each independent resource pool should be designed to provide service for specific flavors of instances or groupings of flavors. For the purpose of this book, \"instance\" refers to a virtual machine and the operating system running on the virtual machine. Designing multiple resource pools helps to ensure that, as instances are scheduled onto compute hypervisors, each independent node's resources will be allocated in a way that makes the most efficient use of available hardware. This is commonly referred to as bin packing."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/generalpurpose/section_tech_considerations_general_purpose.xml:55(para)
|
||||
@ -2752,7 +2752,7 @@ msgid "Processor selection is an extremely important consideration in hardware d
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/generalpurpose/section_tech_considerations_general_purpose.xml:93(para)
|
||||
msgid "In addition to the impact on actual compute services, it is also important to consider the compute requirements of resource nodes within the cloud. Resource nodes refers to non-hypervisor nodes providing controller, object storage, block storage, or networking services in the cloud. The number of processor cores and threads has a direct correlation to the number of worker threads which can be run on a resource node. It is important to ensure sufficient compute capacity and memory is planned on resource nodes."
|
||||
msgid "In addition to the impact on actual compute services, it is also important to consider the compute requirements of resource nodes within the cloud. Resource nodes refer to non-hypervisor nodes providing controller, object storage, block storage, or networking services in the cloud. The number of processor cores and threads has a direct correlation to the number of worker threads which can be run on a resource node. It is important to ensure sufficient compute capacity and memory is planned on resource nodes."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/generalpurpose/section_tech_considerations_general_purpose.xml:102(para)
|
||||
@ -2768,7 +2768,7 @@ msgid "An OpenStack cloud traditionally has multiple network segments, each of w
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/generalpurpose/section_tech_considerations_general_purpose.xml:130(para)
|
||||
msgid "Based on the requirements of instances being serviced in the cloud, the next design choice which will affect your design is the choice of network service which will be used to service instances in the cloud. The choice between legacy networking (nova-network), as a part of OpenStack Compute, and OpenStack Networking (neutron), has tremendous implications and will have a huge impact on the architecture and design of the cloud network infrastructure."
|
||||
msgid "Based on the requirements of instances being serviced in the cloud, the next design choice, which will affect your design is the choice of network service which will be used to service instances in the cloud. The choice between legacy networking (nova-network), as a part of OpenStack Compute, and OpenStack Networking (neutron), has tremendous implications and will have a huge impact on the architecture and design of the cloud network infrastructure."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/generalpurpose/section_tech_considerations_general_purpose.xml:138(para)
|
||||
@ -3016,7 +3016,7 @@ msgid "Storage performance"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/generalpurpose/section_tech_considerations_general_purpose.xml:568(para)
|
||||
msgid "When considering performance of OpenStack Block Storage, hardware and architecture choice is important. Block Storage can use enterprise back-end systems such as NetApp or EMC, use scale out storage such as GlusterFS and Ceph, or simply use the capabilities of directly attached storage in the nodes themselves. Block Storage may be deployed so that traffic traverses the host network, which could affect, and be adversely affected by, the front-side API traffic performance. As such, consider using a dedicated data storage network with dedicated interfaces on the Controller and Compute hosts."
|
||||
msgid "When considering the performance of OpenStack Block Storage, hardware and architecture choices are important. Block Storage can use enterprise back-end systems such as NetApp or EMC, use scale out storage such as GlusterFS and Ceph, or simply use the capabilities of directly attached storage in the nodes themselves. Block Storage may be deployed so that traffic traverses the host network, which could affect, and be adversely affected by, the front-side API traffic performance. As such, consider using a dedicated data storage network with dedicated interfaces on the Controller and Compute hosts."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/generalpurpose/section_tech_considerations_general_purpose.xml:579(para)
|
||||
@ -3112,7 +3112,7 @@ msgid "It's important to understand that user authentication requests include se
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/generalpurpose/section_tech_considerations_general_purpose.xml:753(para)
|
||||
msgid "For more information OpenStack Security, see the <link href=\"http://docs.openstack.org/security-guide/\"><citetitle>OpenStack Security Guide</citetitle></link>"
|
||||
msgid "For more information on OpenStack Security, see the <link href=\"http://docs.openstack.org/security-guide/\"><citetitle>OpenStack Security Guide</citetitle></link>"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/introduction/section_intended_audience.xml:7(title)
|
||||
@ -3482,7 +3482,7 @@ msgid "Operationally, there are a number of considerations that affect the desig
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/compute_focus/section_operational_considerations_compute_focus.xml:13(para)
|
||||
msgid "Service-level agreements (SLAs) are a contractual obligation that gives assurances around availability of a provided service. As such, factoring in promises of availability implies a certain level of redundancy and resiliency when designing an OpenStack cloud."
|
||||
msgid "Service-level agreements (SLAs) are a contractual obligation that gives assurances around the availability of a provided service. As such, factoring in promises of availability implies a certain level of redundancy and resiliency when designing an OpenStack cloud."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/compute_focus/section_operational_considerations_compute_focus.xml:19(para)
|
||||
@ -3498,11 +3498,11 @@ msgid "Network security policy requirements need to be factored in to deployment
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/compute_focus/section_operational_considerations_compute_focus.xml:32(para)
|
||||
msgid "Knowing when and where to implement redundancy and high availability (HA) is directly affected by terms contained in any associated SLA, if one is present."
|
||||
msgid "Knowing when and where to implement redundancy and high availability (HA) is directly affected by the terms contained in any associated SLA, if one is present."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/compute_focus/section_operational_considerations_compute_focus.xml:37(para)
|
||||
msgid "OpenStack cloud management requires operations staff to be able to understand and comprehend design architecture content on some level. The level of skills and the level of separation of the operations and engineering staff is dependent on the size and purpose of the installation. A large cloud service provider or a telecom provider is more inclined to be managed by specially trained dedicated operations organization. A smaller implementation is more inclined to rely on a smaller support staff that might need to take on the combined engineering, design and operations functions."
|
||||
msgid "OpenStack cloud management requires operations staff to be able to understand and comprehend design architecture content on some level. The level of skills and the level of separation of the operations and engineering staff is dependent on the size and purpose of the installation. A large cloud service provider or a telecom provider is more inclined to be managed by a specially trained dedicated operations organization. A smaller implementation is more inclined to rely on a smaller support staff that might need to take on the combined engineering, design and operations functions."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/compute_focus/section_operational_considerations_compute_focus.xml:47(para)
|
||||
@ -3538,7 +3538,7 @@ msgid "Compute hosts can also have internal components changed to account for in
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/compute_focus/section_operational_considerations_compute_focus.xml:109(para)
|
||||
msgid "Another option is to assess the average workloads and increase the number of instances that can run within the compute environment by adjusting the overcommit ratio. While only appropriate in some environments, it's important to remember that changing the CPU overcommit ratio can have a detrimental effect and cause a potential increase in noisy neighbor. The added risk of increasing the overcommit ratio is more instances will fail when a compute host fails. In a compute-focused OpenStack design architecture, increasing the CPU overcommit ratio increases the potential for noisy neighbor issues and is not recommended."
|
||||
msgid "Another option is to assess the average workloads and increase the number of instances that can run within the compute environment by adjusting the overcommit ratio. While only appropriate in some environments, it's important to remember that changing the CPU overcommit ratio can have a detrimental effect and cause a potential increase in a noisy neighbor. The added risk of increasing the overcommit ratio is that more instances will fail when a compute host fails. In a compute-focused OpenStack design architecture, increasing the CPU overcommit ratio increases the potential for noisy neighbor issues and is not recommended."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/compute_focus/section_user_requirements_compute_focus.xml:13(para)
|
||||
@ -3774,7 +3774,7 @@ msgid "The selection of operating system (OS) and hypervisor has a significant i
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:393(para)
|
||||
msgid "Selecting a commercially supported hypervisor such as Microsoft Hyper-V will result in a different cost model rather than chosen a community-supported open source hypervisor like Kinstance or Xen. Even within the ranks of open source solutions, choosing Ubuntu over Red Hat (or vice versa) will have an impact on cost due to support contracts. On the other hand, business or application requirements might dictate a specific or commercially supported hypervisor."
|
||||
msgid "Selecting a commercially supported hypervisor such as Microsoft Hyper-V will result in a different cost model rather than choosing a community-supported open source hypervisor like Kinstance or Xen. Even within the ranks of open source solutions, choosing Ubuntu over Red Hat (or vice versa) will have an impact on cost due to support contracts. On the other hand, business or application requirements might dictate a specific or commercially supported hypervisor."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:406(para)
|
||||
@ -3838,7 +3838,7 @@ msgid "OpenStack Block Storage would potentially not be incorporated into a comp
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:513(para)
|
||||
msgid "The exclusion of certain OpenStack components might also limit or constrain the functionality of other components. If a design opts to include the Orchestration module but exclude the Telemetry module, then the design will not be able to take advantage of Orchestration's auto scaling functionality (which relies on information from Telemetry). Due to the fact that you can use Orchestration to spin up a large number of instances to perform the compute-intensive processing, including Orchestration in a compute-focused architecture design is strongly recommended."
|
||||
msgid "The exclusion of certain OpenStack components might also limit or constrain the functionality of other components. If a design opts to include the Orchestration module but excludes the Telemetry module, then the design will not be able to take advantage of Orchestration's auto scaling functionality (which relies on information from Telemetry). Due to the fact that you can use Orchestration to spin up a large number of instances to perform the compute-intensive processing, including Orchestration in a compute-focused architecture design is strongly recommended."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:525(para)
|
||||
|
||||
File diff suppressed because it is too large
Load Diff
@ -7,8 +7,8 @@
|
||||
msgid ""
|
||||
msgstr ""
|
||||
"Project-Id-Version: OpenStack Manuals\n"
|
||||
"POT-Creation-Date: 2015-01-28 21:14+0000\n"
|
||||
"PO-Revision-Date: 2015-01-28 19:06+0000\n"
|
||||
"POT-Creation-Date: 2015-01-31 02:01+0000\n"
|
||||
"PO-Revision-Date: 2015-01-30 08:00+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"
|
||||
@ -2267,15 +2267,26 @@ msgstr ""
|
||||
|
||||
#: ./doc/image-guide/ch_obtaining_images.xml93(para)
|
||||
msgid ""
|
||||
"Debian does not (yet) provide images for direct download. Instead, a package"
|
||||
" named <package>openstack-debian-images</package> provides a simple script "
|
||||
"for building them. This package is available in Debian Unstable, Debian "
|
||||
"Jessie, and through the wheezy-backports repositories. To produce a Wheezy "
|
||||
"image, simply run: <placeholder-1/>"
|
||||
"Since January 2015, <link "
|
||||
"href=\"http://cdimage.debian.org/cdimage/openstack/\">Debian provides images"
|
||||
" for direct download</link>. They are now made at the same time as the CD "
|
||||
"and DVD images of Debian. However, until Debian 8.0 (aka Jessie) is out, "
|
||||
"these images are the weekly built images of the testing distribution."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/image-guide/ch_obtaining_images.xml99(para)
|
||||
msgid ""
|
||||
"If you wish to build your own images of Debian 7.0 (aka Wheezy, the current "
|
||||
"stable release of Debian), you can use the package which is used to build "
|
||||
"the official Debian images. It is named <package>openstack-debian-"
|
||||
"images</package>, and it provides a simple script for building them. This "
|
||||
"package is available in Debian Unstable, Debian Jessie, and through the "
|
||||
"wheezy-backports repositories. To produce a Wheezy image, simply run: "
|
||||
"<placeholder-1/>"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/image-guide/ch_obtaining_images.xml107(para)
|
||||
msgid ""
|
||||
"If building the image for Wheezy, packages like <package>cloud-"
|
||||
"init</package>, <package>cloud-utils</package> or <package>cloud-initramfs-"
|
||||
"growroot</package> will be pulled from wheezy-backports. Also, the current "
|
||||
@ -2290,21 +2301,21 @@ msgid ""
|
||||
"parameter: <placeholder-4/>"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/image-guide/ch_obtaining_images.xml120(title)
|
||||
#: ./doc/image-guide/ch_obtaining_images.xml128(title)
|
||||
msgid "Official images from other Linux distributions"
|
||||
msgstr "Images officielles pour d'autres distributions de Linux"
|
||||
|
||||
#: ./doc/image-guide/ch_obtaining_images.xml121(para)
|
||||
#: ./doc/image-guide/ch_obtaining_images.xml129(para)
|
||||
msgid ""
|
||||
"As of this writing, we are not aware of other distributions that provide "
|
||||
"images for download."
|
||||
msgstr "Au moment où nous écrivons ces lignes, nous n'avons pas connaissance d'autres distributions qui fourniraient des images en téléchargement."
|
||||
|
||||
#: ./doc/image-guide/ch_obtaining_images.xml124(title)
|
||||
#: ./doc/image-guide/ch_obtaining_images.xml132(title)
|
||||
msgid "Rackspace Cloud Builders (multiple distros) images"
|
||||
msgstr "Images Rackspace Cloud Builders (distributions multiples)"
|
||||
|
||||
#: ./doc/image-guide/ch_obtaining_images.xml126(para)
|
||||
#: ./doc/image-guide/ch_obtaining_images.xml134(para)
|
||||
msgid ""
|
||||
"Rackspace Cloud Builders maintains a list of pre-built images from various "
|
||||
"distributions (Red Hat, CentOS, Fedora, Ubuntu). Links to these images can "
|
||||
@ -2312,11 +2323,11 @@ msgid ""
|
||||
"build\">rackerjoe/oz-image-build on GitHub</link>."
|
||||
msgstr "Rackspace Cloud Builders maintient une liste d'images pré-générées issues de diverses distributions (Red Hat, CentOS, Fedora, Ubuntu). Les liens vers ces images peuvent être trouvés à <link href=\"https://github.com/rackerjoe/oz-image-build\">rackerjoe/oz-image-build on GitHub</link>."
|
||||
|
||||
#: ./doc/image-guide/ch_obtaining_images.xml132(title)
|
||||
#: ./doc/image-guide/ch_obtaining_images.xml140(title)
|
||||
msgid "Microsoft Windows images"
|
||||
msgstr "Images Microsoft Windows"
|
||||
|
||||
#: ./doc/image-guide/ch_obtaining_images.xml133(para)
|
||||
#: ./doc/image-guide/ch_obtaining_images.xml141(para)
|
||||
msgid ""
|
||||
"Cloudbase Solutions hosts an <link "
|
||||
"href=\"http://www.cloudbase.it/ws2012r2/\">OpenStack Windows Server 2012 "
|
||||
|
||||
@ -1,7 +1,7 @@
|
||||
msgid ""
|
||||
msgstr ""
|
||||
"Project-Id-Version: PACKAGE VERSION\n"
|
||||
"POT-Creation-Date: 2015-01-29 06:29+0000\n"
|
||||
"POT-Creation-Date: 2015-01-31 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"
|
||||
@ -1554,34 +1554,38 @@ msgid "Official Debian images"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/image-guide/ch_obtaining_images.xml:93(para)
|
||||
msgid "Debian does not (yet) provide images for direct download. Instead, a package named <package>openstack-debian-images</package> provides a simple script for building them. This package is available in Debian Unstable, Debian Jessie, and through the wheezy-backports repositories. To produce a Wheezy image, simply run: <placeholder-1/>"
|
||||
msgid "Since January 2015, <link href=\"http://cdimage.debian.org/cdimage/openstack/\">Debian provides images for direct download</link>. They are now made at the same time as the CD and DVD images of Debian. However, until Debian 8.0 (aka Jessie) is out, these images are the weekly built images of the testing distribution."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/image-guide/ch_obtaining_images.xml:99(para)
|
||||
msgid "If you wish to build your own images of Debian 7.0 (aka Wheezy, the current stable release of Debian), you can use the package which is used to build the official Debian images. It is named <package>openstack-debian-images</package>, and it provides a simple script for building them. This package is available in Debian Unstable, Debian Jessie, and through the wheezy-backports repositories. To produce a Wheezy image, simply run: <placeholder-1/>"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/image-guide/ch_obtaining_images.xml:107(para)
|
||||
msgid "If building the image for Wheezy, packages like <package>cloud-init</package>, <package>cloud-utils</package> or <package>cloud-initramfs-growroot</package> will be pulled from wheezy-backports. Also, the current version of <package>bootlogd</package> in Wheezy doesn't support logging to multiple consoles, which is needed so that both the OpenStack Dashboard console and the <placeholder-1/> console works. However, a <link href=\"http://archive.gplhost.com/debian/pool/juno-backports/main/s/sysvinit/bootlogd_2.88dsf-41+deb7u2_amd64.deb\"> fixed version is available from the non-official GPLHost repository</link>. To install it on top of the image, it is possible to use the <placeholder-2/> option of the <placeholder-3/> script, with this kind of script as parameter: <placeholder-4/>"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/image-guide/ch_obtaining_images.xml:120(title)
|
||||
#: ./doc/image-guide/ch_obtaining_images.xml:128(title)
|
||||
msgid "Official images from other Linux distributions"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/image-guide/ch_obtaining_images.xml:121(para)
|
||||
#: ./doc/image-guide/ch_obtaining_images.xml:129(para)
|
||||
msgid "As of this writing, we are not aware of other distributions that provide images for download."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/image-guide/ch_obtaining_images.xml:124(title)
|
||||
#: ./doc/image-guide/ch_obtaining_images.xml:132(title)
|
||||
msgid "Rackspace Cloud Builders (multiple distros) images"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/image-guide/ch_obtaining_images.xml:126(para)
|
||||
#: ./doc/image-guide/ch_obtaining_images.xml:134(para)
|
||||
msgid "Rackspace Cloud Builders maintains a list of pre-built images from various distributions (Red Hat, CentOS, Fedora, Ubuntu). Links to these images can be found at <link href=\"https://github.com/rackerjoe/oz-image-build\">rackerjoe/oz-image-build on GitHub</link>."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/image-guide/ch_obtaining_images.xml:132(title)
|
||||
#: ./doc/image-guide/ch_obtaining_images.xml:140(title)
|
||||
msgid "Microsoft Windows images"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/image-guide/ch_obtaining_images.xml:133(para)
|
||||
#: ./doc/image-guide/ch_obtaining_images.xml:141(para)
|
||||
msgid "Cloudbase Solutions hosts an <link href=\"http://www.cloudbase.it/ws2012r2/\">OpenStack Windows Server 2012 Standard Evaluation image</link> that runs on Hyper-V, KVM, and XenServer/XCP."
|
||||
msgstr ""
|
||||
|
||||
|
||||
@ -6,8 +6,8 @@
|
||||
msgid ""
|
||||
msgstr ""
|
||||
"Project-Id-Version: OpenStack Manuals\n"
|
||||
"POT-Creation-Date: 2015-01-28 21:14+0000\n"
|
||||
"PO-Revision-Date: 2015-01-28 19:06+0000\n"
|
||||
"POT-Creation-Date: 2015-01-31 02:01+0000\n"
|
||||
"PO-Revision-Date: 2015-01-30 08:00+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"
|
||||
@ -2266,15 +2266,26 @@ msgstr "公式 Debian イメージ"
|
||||
|
||||
#: ./doc/image-guide/ch_obtaining_images.xml93(para)
|
||||
msgid ""
|
||||
"Debian does not (yet) provide images for direct download. Instead, a package"
|
||||
" named <package>openstack-debian-images</package> provides a simple script "
|
||||
"for building them. This package is available in Debian Unstable, Debian "
|
||||
"Jessie, and through the wheezy-backports repositories. To produce a Wheezy "
|
||||
"image, simply run: <placeholder-1/>"
|
||||
msgstr "Debian は、直接ダウンロードするイメージをまだ提供していません。代わりに、<package>openstack-debian-images</package> という名前のパッケージが、イメージを構築するためのシンプルなスクリプトを提供します。このパッケージは、Debian Unstable、Debian Jessie、wheezy バックポートリポジトリー経由で利用可能です。以下を実行して、Wheezy イメージを作成します。<placeholder-1/>"
|
||||
"Since January 2015, <link "
|
||||
"href=\"http://cdimage.debian.org/cdimage/openstack/\">Debian provides images"
|
||||
" for direct download</link>. They are now made at the same time as the CD "
|
||||
"and DVD images of Debian. However, until Debian 8.0 (aka Jessie) is out, "
|
||||
"these images are the weekly built images of the testing distribution."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/image-guide/ch_obtaining_images.xml99(para)
|
||||
msgid ""
|
||||
"If you wish to build your own images of Debian 7.0 (aka Wheezy, the current "
|
||||
"stable release of Debian), you can use the package which is used to build "
|
||||
"the official Debian images. It is named <package>openstack-debian-"
|
||||
"images</package>, and it provides a simple script for building them. This "
|
||||
"package is available in Debian Unstable, Debian Jessie, and through the "
|
||||
"wheezy-backports repositories. To produce a Wheezy image, simply run: "
|
||||
"<placeholder-1/>"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/image-guide/ch_obtaining_images.xml107(para)
|
||||
msgid ""
|
||||
"If building the image for Wheezy, packages like <package>cloud-"
|
||||
"init</package>, <package>cloud-utils</package> or <package>cloud-initramfs-"
|
||||
"growroot</package> will be pulled from wheezy-backports. Also, the current "
|
||||
@ -2289,21 +2300,21 @@ msgid ""
|
||||
"parameter: <placeholder-4/>"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/image-guide/ch_obtaining_images.xml120(title)
|
||||
#: ./doc/image-guide/ch_obtaining_images.xml128(title)
|
||||
msgid "Official images from other Linux distributions"
|
||||
msgstr "他の Linux ディストリビューションの公式イメージ"
|
||||
|
||||
#: ./doc/image-guide/ch_obtaining_images.xml121(para)
|
||||
#: ./doc/image-guide/ch_obtaining_images.xml129(para)
|
||||
msgid ""
|
||||
"As of this writing, we are not aware of other distributions that provide "
|
||||
"images for download."
|
||||
msgstr "執筆時点では、ダウンロード用のイメージを提供している他のディストリビューションを把握していません。"
|
||||
|
||||
#: ./doc/image-guide/ch_obtaining_images.xml124(title)
|
||||
#: ./doc/image-guide/ch_obtaining_images.xml132(title)
|
||||
msgid "Rackspace Cloud Builders (multiple distros) images"
|
||||
msgstr "Rackspace Cloud Builders (複数ディストリビューション) イメージ"
|
||||
|
||||
#: ./doc/image-guide/ch_obtaining_images.xml126(para)
|
||||
#: ./doc/image-guide/ch_obtaining_images.xml134(para)
|
||||
msgid ""
|
||||
"Rackspace Cloud Builders maintains a list of pre-built images from various "
|
||||
"distributions (Red Hat, CentOS, Fedora, Ubuntu). Links to these images can "
|
||||
@ -2311,11 +2322,11 @@ msgid ""
|
||||
"build\">rackerjoe/oz-image-build on GitHub</link>."
|
||||
msgstr "Rackspace Cloud Builders は、さまざまなディストリビューション (Red Hat, CentOS, Fedora, Ubuntu) の事前構築済みイメージを維持しています。これらのイメージへのリンクは、<link href=\"https://github.com/rackerjoe/oz-image-build\">GitHub の rackerjoe/oz-image-build</link> にあります。"
|
||||
|
||||
#: ./doc/image-guide/ch_obtaining_images.xml132(title)
|
||||
#: ./doc/image-guide/ch_obtaining_images.xml140(title)
|
||||
msgid "Microsoft Windows images"
|
||||
msgstr "Microsoft Windows イメージ"
|
||||
|
||||
#: ./doc/image-guide/ch_obtaining_images.xml133(para)
|
||||
#: ./doc/image-guide/ch_obtaining_images.xml141(para)
|
||||
msgid ""
|
||||
"Cloudbase Solutions hosts an <link "
|
||||
"href=\"http://www.cloudbase.it/ws2012r2/\">OpenStack Windows Server 2012 "
|
||||
|
||||
@ -4,8 +4,8 @@
|
||||
msgid ""
|
||||
msgstr ""
|
||||
"Project-Id-Version: OpenStack Manuals\n"
|
||||
"POT-Creation-Date: 2015-01-28 21:14+0000\n"
|
||||
"PO-Revision-Date: 2015-01-28 19:06+0000\n"
|
||||
"POT-Creation-Date: 2015-01-31 02:01+0000\n"
|
||||
"PO-Revision-Date: 2015-01-30 08:00+0000\n"
|
||||
"Last-Translator: openstackjenkins <jenkins@openstack.org>\n"
|
||||
"Language-Team: Chinese (China) (http://www.transifex.com/projects/p/openstack-manuals-i18n/language/zh_CN/)\n"
|
||||
"MIME-Version: 1.0\n"
|
||||
@ -2264,15 +2264,26 @@ msgstr "官方 Debian 镜像"
|
||||
|
||||
#: ./doc/image-guide/ch_obtaining_images.xml93(para)
|
||||
msgid ""
|
||||
"Debian does not (yet) provide images for direct download. Instead, a package"
|
||||
" named <package>openstack-debian-images</package> provides a simple script "
|
||||
"for building them. This package is available in Debian Unstable, Debian "
|
||||
"Jessie, and through the wheezy-backports repositories. To produce a Wheezy "
|
||||
"image, simply run: <placeholder-1/>"
|
||||
msgstr "Debian 还没有提供镜像直接下载，作为替代的是，他们提供一个简单的脚本 <package>openstack-debian-images</package> 包用于创建镜像，这个包在 Debian 未稳定分支 Debian Jessie 内，通过使用 wheezy-backports 源。要生成 Wheezy 镜像，仅需如下命令：<placeholder-1/>"
|
||||
"Since January 2015, <link "
|
||||
"href=\"http://cdimage.debian.org/cdimage/openstack/\">Debian provides images"
|
||||
" for direct download</link>. They are now made at the same time as the CD "
|
||||
"and DVD images of Debian. However, until Debian 8.0 (aka Jessie) is out, "
|
||||
"these images are the weekly built images of the testing distribution."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/image-guide/ch_obtaining_images.xml99(para)
|
||||
msgid ""
|
||||
"If you wish to build your own images of Debian 7.0 (aka Wheezy, the current "
|
||||
"stable release of Debian), you can use the package which is used to build "
|
||||
"the official Debian images. It is named <package>openstack-debian-"
|
||||
"images</package>, and it provides a simple script for building them. This "
|
||||
"package is available in Debian Unstable, Debian Jessie, and through the "
|
||||
"wheezy-backports repositories. To produce a Wheezy image, simply run: "
|
||||
"<placeholder-1/>"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/image-guide/ch_obtaining_images.xml107(para)
|
||||
msgid ""
|
||||
"If building the image for Wheezy, packages like <package>cloud-"
|
||||
"init</package>, <package>cloud-utils</package> or <package>cloud-initramfs-"
|
||||
"growroot</package> will be pulled from wheezy-backports. Also, the current "
|
||||
@ -2287,21 +2298,21 @@ msgid ""
|
||||
"parameter: <placeholder-4/>"
|
||||
msgstr "如果你创建 Wheezy 镜像，诸如 <package>cloud-init</package>, <package>cloud-utils</package> 或 <package>cloud-initramfs-growroot</package> 安装包将从 wheezy-backports 获取。并且，当前版本的 Wheezy 的 <package>bootlogd</package>包不支持记录日志到多个控制台，但OpenStack Dashboard 控制台和 <placeholder-1/> 需要记录日志到多控制台才能工作。因此。<link href=\"http://archive.gplhost.com/debian/pool/juno-backports/main/s/sysvinit/bootlogd_2.88dsf-41+deb7u2_amd64.deb\"> GPLHost 软件库的修正的非官方版本</link>。要在镜像上安装它，可能需要使用 <placeholder-3/> 脚本的 <placeholder-2/> 选项，使用下面的脚本作为参数：<placeholder-4/>"
|
||||
|
||||
#: ./doc/image-guide/ch_obtaining_images.xml120(title)
|
||||
#: ./doc/image-guide/ch_obtaining_images.xml128(title)
|
||||
msgid "Official images from other Linux distributions"
|
||||
msgstr "其他Linux发行版的官方镜像"
|
||||
|
||||
#: ./doc/image-guide/ch_obtaining_images.xml121(para)
|
||||
#: ./doc/image-guide/ch_obtaining_images.xml129(para)
|
||||
msgid ""
|
||||
"As of this writing, we are not aware of other distributions that provide "
|
||||
"images for download."
|
||||
msgstr "在本文档便携式，我们并未发现其他Linux发行版提供镜像下载。"
|
||||
|
||||
#: ./doc/image-guide/ch_obtaining_images.xml124(title)
|
||||
#: ./doc/image-guide/ch_obtaining_images.xml132(title)
|
||||
msgid "Rackspace Cloud Builders (multiple distros) images"
|
||||
msgstr "Rackspace 云计算镜像（多个发行版）"
|
||||
|
||||
#: ./doc/image-guide/ch_obtaining_images.xml126(para)
|
||||
#: ./doc/image-guide/ch_obtaining_images.xml134(para)
|
||||
msgid ""
|
||||
"Rackspace Cloud Builders maintains a list of pre-built images from various "
|
||||
"distributions (Red Hat, CentOS, Fedora, Ubuntu). Links to these images can "
|
||||
@ -2309,11 +2320,11 @@ msgid ""
|
||||
"build\">rackerjoe/oz-image-build on GitHub</link>."
|
||||
msgstr "Rackspace 云运行商维护了多个发行版（Red Hat, CentOS, Fedora, Ubuntu）预先创建的镜像列表。列表的链接为<link href=\"https://github.com/rackerjoe/oz-image-build\">rackerjoe/oz-image-build on GitHub</link>。"
|
||||
|
||||
#: ./doc/image-guide/ch_obtaining_images.xml132(title)
|
||||
#: ./doc/image-guide/ch_obtaining_images.xml140(title)
|
||||
msgid "Microsoft Windows images"
|
||||
msgstr "微软 Windows 镜像"
|
||||
|
||||
#: ./doc/image-guide/ch_obtaining_images.xml133(para)
|
||||
#: ./doc/image-guide/ch_obtaining_images.xml141(para)
|
||||
msgid ""
|
||||
"Cloudbase Solutions hosts an <link "
|
||||
"href=\"http://www.cloudbase.it/ws2012r2/\">OpenStack Windows Server 2012 "
|
||||
|
||||
@ -1,7 +1,7 @@
|
||||
msgid ""
|
||||
msgstr ""
|
||||
"Project-Id-Version: PACKAGE VERSION\n"
|
||||
"POT-Creation-Date: 2015-01-21 06:13+0000\n"
|
||||
"POT-Creation-Date: 2015-01-31 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"
|
||||
@ -11,43 +11,43 @@ 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/install-guide/section_keystone-install.xml:133(None)
|
||||
#: ./doc/install-guide/section_keystone-install.xml:140(None)
|
||||
msgid "@@image: 'figures/debconf-screenshots/keystone_1_admin_token.png'; md5=29a51caaf09c3d6e3f0fda73c256a17a"
|
||||
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/install-guide/section_keystone-install.xml:147(None)
|
||||
#: ./doc/install-guide/section_keystone-install.xml:154(None)
|
||||
msgid "@@image: 'figures/debconf-screenshots/keystone_2_register_admin_tenant_yes_no.png'; md5=25c9a90b1df2d979aae6ce9975c7285b"
|
||||
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/install-guide/section_keystone-install.xml:156(None)
|
||||
#: ./doc/install-guide/section_keystone-install.xml:163(None)
|
||||
msgid "@@image: 'figures/debconf-screenshots/keystone_3_admin_user_name.png'; md5=173cf7ed13252df1425109be588b2ad6"
|
||||
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/install-guide/section_keystone-install.xml:165(None)
|
||||
#: ./doc/install-guide/section_keystone-install.xml:172(None)
|
||||
msgid "@@image: 'figures/debconf-screenshots/keystone_4_admin_user_email.png'; md5=b7f0d34350ccc0aa9ae4e766b7ac80c1"
|
||||
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/install-guide/section_keystone-install.xml:174(None)
|
||||
#: ./doc/install-guide/section_keystone-install.xml:181(None)
|
||||
msgid "@@image: 'figures/debconf-screenshots/keystone_5_admin_user_pass.png'; md5=e6b32d8d80af90f07a66abc8fb256c84"
|
||||
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/install-guide/section_keystone-install.xml:183(None)
|
||||
#: ./doc/install-guide/section_keystone-install.xml:190(None)
|
||||
msgid "@@image: 'figures/debconf-screenshots/keystone_6_admin_user_pass_confirm.png'; md5=1fbf9223e4923c93030d53278d1771cc"
|
||||
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/install-guide/section_keystone-install.xml:194(None)
|
||||
#: ./doc/install-guide/section_keystone-install.xml:201(None)
|
||||
msgid "@@image: 'figures/debconf-screenshots/keystone_7_register_endpoint.png'; md5=d24d84133bfee936267e79631a2666e6"
|
||||
msgstr ""
|
||||
|
||||
@ -99,11 +99,11 @@ msgstr ""
|
||||
msgid "Generate a random value to use as the administration token during initial configuration:"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/install-guide/section_keystone-install.xml:60(title) ./doc/install-guide/section_keystone-install.xml:120(title)
|
||||
#: ./doc/install-guide/section_keystone-install.xml:60(title) ./doc/install-guide/section_keystone-install.xml:127(title)
|
||||
msgid "To install and configure the components"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/install-guide/section_keystone-install.xml:62(para) ./doc/install-guide/section_keystone-install.xml:122(para)
|
||||
#: ./doc/install-guide/section_keystone-install.xml:62(para) ./doc/install-guide/section_keystone-install.xml:129(para)
|
||||
msgid "Run the following command to install the packages:"
|
||||
msgstr ""
|
||||
|
||||
@ -139,71 +139,75 @@ msgstr ""
|
||||
msgid "In the <literal>[token]</literal> section, configure the UUID token provider and SQL driver:"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/install-guide/section_keystone-install.xml:98(para) ./doc/install-guide/section_cinder-storage-node.xml:217(para) ./doc/install-guide/section_cinder-controller-node.xml:212(para) ./doc/install-guide/section_nova-controller-install.xml:200(para) ./doc/install-guide/section_glance-install.xml:170(para) ./doc/install-guide/section_glance-install.xml:218(para) ./doc/install-guide/section_neutron-compute-node.xml:135(para) ./doc/install-guide/section_neutron-controller-node.xml:255(para) ./doc/install-guide/section_neutron-network-node.xml:139(para) ./doc/install-guide/section_neutron-network-node.xml:244(para) ./doc/install-guide/section_neutron-network-node.xml:273(para) ./doc/install-guide/section_neutron-network-node.xml:387(para) ./doc/install-guide/section_nova-compute-install.xml:137(para) ./doc/install-guide/section_heat-install.xml:230(para)
|
||||
#: ./doc/install-guide/section_keystone-install.xml:98(para)
|
||||
msgid "In the <literal>[revoke]</literal> section, configure the SQL revocation driver:"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/install-guide/section_keystone-install.xml:105(para) ./doc/install-guide/section_cinder-storage-node.xml:217(para) ./doc/install-guide/section_cinder-controller-node.xml:212(para) ./doc/install-guide/section_nova-controller-install.xml:200(para) ./doc/install-guide/section_glance-install.xml:170(para) ./doc/install-guide/section_glance-install.xml:218(para) ./doc/install-guide/section_neutron-compute-node.xml:135(para) ./doc/install-guide/section_neutron-controller-node.xml:255(para) ./doc/install-guide/section_neutron-network-node.xml:139(para) ./doc/install-guide/section_neutron-network-node.xml:244(para) ./doc/install-guide/section_neutron-network-node.xml:273(para) ./doc/install-guide/section_neutron-network-node.xml:387(para) ./doc/install-guide/section_nova-compute-install.xml:137(para) ./doc/install-guide/section_heat-install.xml:230(para)
|
||||
msgid "(Optional) To assist with troubleshooting, enable verbose logging in the <literal>[DEFAULT]</literal> section:"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/install-guide/section_keystone-install.xml:107(para)
|
||||
#: ./doc/install-guide/section_keystone-install.xml:114(para)
|
||||
msgid "Create generic certificates and keys and restrict access to the associated files:"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/install-guide/section_keystone-install.xml:115(para)
|
||||
#: ./doc/install-guide/section_keystone-install.xml:122(para)
|
||||
msgid "Populate the Identity service database:"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/install-guide/section_keystone-install.xml:126(para)
|
||||
#: ./doc/install-guide/section_keystone-install.xml:133(para)
|
||||
msgid "Respond to prompts for <xref linkend=\"debconf-dbconfig-common\"/>."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/install-guide/section_keystone-install.xml:129(para)
|
||||
#: ./doc/install-guide/section_keystone-install.xml:136(para)
|
||||
msgid "Configure the initial administration token:"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/install-guide/section_keystone-install.xml:137(para)
|
||||
#: ./doc/install-guide/section_keystone-install.xml:144(para)
|
||||
msgid "Use the random value that you generated in a previous step. If you install using non-interactive mode or you do not specify this token, the configuration tool generates a random value."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/install-guide/section_keystone-install.xml:142(para)
|
||||
#: ./doc/install-guide/section_keystone-install.xml:149(para)
|
||||
msgid "Create the <literal>admin</literal> tenant and user:"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/install-guide/section_keystone-install.xml:189(para)
|
||||
#: ./doc/install-guide/section_keystone-install.xml:196(para)
|
||||
msgid "Create the Identity service endpoints:"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/install-guide/section_keystone-install.xml:201(title) ./doc/install-guide/section_basics-database.xml:66(title) ./doc/install-guide/section_basics-packages.xml:138(title) ./doc/install-guide/section_cinder-storage-node.xml:252(title) ./doc/install-guide/section_cinder-controller-node.xml:244(title) ./doc/install-guide/section_nova-controller-install.xml:247(title) ./doc/install-guide/section_glance-install.xml:261(title) ./doc/install-guide/section_dashboard-install.xml:109(title) ./doc/install-guide/section_neutron-controller-node.xml:360(title) ./doc/install-guide/section_nova-compute-install.xml:181(title) ./doc/install-guide/section_heat-install.xml:274(title) ./doc/install-guide/section_ceilometer-controller.xml:341(title)
|
||||
#: ./doc/install-guide/section_keystone-install.xml:208(title) ./doc/install-guide/section_basics-database.xml:66(title) ./doc/install-guide/section_basics-packages.xml:138(title) ./doc/install-guide/section_cinder-storage-node.xml:252(title) ./doc/install-guide/section_cinder-controller-node.xml:244(title) ./doc/install-guide/section_nova-controller-install.xml:247(title) ./doc/install-guide/section_glance-install.xml:261(title) ./doc/install-guide/section_dashboard-install.xml:109(title) ./doc/install-guide/section_neutron-controller-node.xml:360(title) ./doc/install-guide/section_nova-compute-install.xml:181(title) ./doc/install-guide/section_heat-install.xml:274(title) ./doc/install-guide/section_ceilometer-controller.xml:341(title)
|
||||
msgid "To finalize installation"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/install-guide/section_keystone-install.xml:203(para)
|
||||
#: ./doc/install-guide/section_keystone-install.xml:210(para)
|
||||
msgid "Restart the Identity service:"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/install-guide/section_keystone-install.xml:207(para)
|
||||
#: ./doc/install-guide/section_keystone-install.xml:214(para)
|
||||
msgid "Start the Identity service and configure it to start when the system boots:"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/install-guide/section_keystone-install.xml:211(para) ./doc/install-guide/section_basics-database.xml:27(para) ./doc/install-guide/section_basics-database.xml:76(para) ./doc/install-guide/section_ceilometer-swift.xml:63(para) ./doc/install-guide/section_ceilometer-nova.xml:36(para) ./doc/install-guide/section_ceilometer-nova.xml:112(para) ./doc/install-guide/section_ceilometer-cinder.xml:26(para) ./doc/install-guide/section_ceilometer-cinder.xml:34(para) ./doc/install-guide/section_cinder-storage-node.xml:264(para) ./doc/install-guide/section_cinder-controller-node.xml:255(para) ./doc/install-guide/section_basics-ntp.xml:60(para) ./doc/install-guide/section_basics-ntp.xml:102(para) ./doc/install-guide/section_nova-controller-install.xml:266(para) ./doc/install-guide/section_nova-networking-compute-node.xml:61(para) ./doc/install-guide/section_glance-install.xml:272(para) ./doc/install-guide/section_dashboard-install.xml:133(para) ./doc/install-guide/section_neutron-compute-node.xml:215(para) ./doc/install-guide/section_neutron-compute-node.xml:304(para) ./doc/install-guide/section_neutron-compute-node.xml:315(para) ./doc/install-guide/section_neutron-controller-node.xml:393(para) ./doc/install-guide/section_neutron-controller-node.xml:409(para) ./doc/install-guide/section_neutron-network-node.xml:417(para) ./doc/install-guide/section_neutron-network-node.xml:440(para) ./doc/install-guide/section_neutron-network-node.xml:516(para) ./doc/install-guide/section_trove-install.xml:236(para) ./doc/install-guide/section_nova-networking-controller-node.xml:31(para) ./doc/install-guide/section_nova-compute-install.xml:215(para) ./doc/install-guide/section_heat-install.xml:288(para) ./doc/install-guide/section_ceilometer-glance.xml:26(para) ./doc/install-guide/section_basics-queue.xml:49(para) ./doc/install-guide/section_ceilometer-controller.xml:26(para) ./doc/install-guide/section_ceilometer-controller.xml:78(para) ./doc/install-guide/section_ceilometer-controller.xml:360(para) ./doc/install-guide/object-storage/section_swift-finalize-installation.xml:68(para) ./doc/install-guide/object-storage/section_swift-finalize-installation.xml:106(para) ./doc/install-guide/object-storage/section_swift-storage-node.xml:169(para) ./doc/install-guide/object-storage/section_start-storage-node-services.xml:22(para)
|
||||
#: ./doc/install-guide/section_keystone-install.xml:218(para) ./doc/install-guide/section_basics-database.xml:27(para) ./doc/install-guide/section_basics-database.xml:76(para) ./doc/install-guide/section_ceilometer-swift.xml:63(para) ./doc/install-guide/section_ceilometer-nova.xml:36(para) ./doc/install-guide/section_ceilometer-nova.xml:112(para) ./doc/install-guide/section_ceilometer-cinder.xml:26(para) ./doc/install-guide/section_ceilometer-cinder.xml:34(para) ./doc/install-guide/section_cinder-storage-node.xml:264(para) ./doc/install-guide/section_cinder-controller-node.xml:255(para) ./doc/install-guide/section_basics-ntp.xml:60(para) ./doc/install-guide/section_basics-ntp.xml:102(para) ./doc/install-guide/section_nova-controller-install.xml:266(para) ./doc/install-guide/section_nova-networking-compute-node.xml:61(para) ./doc/install-guide/section_glance-install.xml:272(para) ./doc/install-guide/section_dashboard-install.xml:133(para) ./doc/install-guide/section_neutron-compute-node.xml:215(para) ./doc/install-guide/section_neutron-compute-node.xml:304(para) ./doc/install-guide/section_neutron-compute-node.xml:315(para) ./doc/install-guide/section_neutron-controller-node.xml:393(para) ./doc/install-guide/section_neutron-controller-node.xml:409(para) ./doc/install-guide/section_neutron-network-node.xml:417(para) ./doc/install-guide/section_neutron-network-node.xml:440(para) ./doc/install-guide/section_neutron-network-node.xml:516(para) ./doc/install-guide/section_trove-install.xml:236(para) ./doc/install-guide/section_nova-networking-controller-node.xml:31(para) ./doc/install-guide/section_nova-compute-install.xml:215(para) ./doc/install-guide/section_heat-install.xml:288(para) ./doc/install-guide/section_ceilometer-glance.xml:26(para) ./doc/install-guide/section_basics-queue.xml:49(para) ./doc/install-guide/section_ceilometer-controller.xml:26(para) ./doc/install-guide/section_ceilometer-controller.xml:78(para) ./doc/install-guide/section_ceilometer-controller.xml:360(para) ./doc/install-guide/object-storage/section_swift-finalize-installation.xml:68(para) ./doc/install-guide/object-storage/section_swift-finalize-installation.xml:106(para) ./doc/install-guide/object-storage/section_swift-storage-node.xml:169(para) ./doc/install-guide/object-storage/section_start-storage-node-services.xml:22(para)
|
||||
msgid "On SLES:"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/install-guide/section_keystone-install.xml:214(para) ./doc/install-guide/section_basics-database.xml:25(para) ./doc/install-guide/section_basics-database.xml:79(para) ./doc/install-guide/section_ceilometer-swift.xml:65(para) ./doc/install-guide/section_ceilometer-nova.xml:38(para) ./doc/install-guide/section_ceilometer-nova.xml:115(para) ./doc/install-guide/section_ceilometer-cinder.xml:29(para) ./doc/install-guide/section_ceilometer-cinder.xml:36(para) ./doc/install-guide/section_cinder-storage-node.xml:269(para) ./doc/install-guide/section_cinder-controller-node.xml:260(para) ./doc/install-guide/section_basics-ntp.xml:63(para) ./doc/install-guide/section_basics-ntp.xml:105(para) ./doc/install-guide/section_nova-controller-install.xml:279(para) ./doc/install-guide/section_nova-networking-compute-node.xml:66(para) ./doc/install-guide/section_glance-install.xml:277(para) ./doc/install-guide/section_dashboard-install.xml:138(para) ./doc/install-guide/section_neutron-compute-node.xml:218(para) ./doc/install-guide/section_neutron-compute-node.xml:306(para) ./doc/install-guide/section_neutron-compute-node.xml:318(para) ./doc/install-guide/section_neutron-controller-node.xml:397(para) ./doc/install-guide/section_neutron-controller-node.xml:412(para) ./doc/install-guide/section_neutron-network-node.xml:419(para) ./doc/install-guide/section_neutron-network-node.xml:443(para) ./doc/install-guide/section_neutron-network-node.xml:526(para) ./doc/install-guide/section_trove-install.xml:243(para) ./doc/install-guide/section_nova-networking-controller-node.xml:35(para) ./doc/install-guide/section_nova-compute-install.xml:220(para) ./doc/install-guide/section_heat-install.xml:295(para) ./doc/install-guide/section_ceilometer-glance.xml:29(para) ./doc/install-guide/section_basics-queue.xml:52(para) ./doc/install-guide/section_ceilometer-controller.xml:24(para) ./doc/install-guide/section_ceilometer-controller.xml:81(para) ./doc/install-guide/section_ceilometer-controller.xml:373(para) ./doc/install-guide/object-storage/section_swift-finalize-installation.xml:73(para) ./doc/install-guide/object-storage/section_swift-finalize-installation.xml:119(para) ./doc/install-guide/object-storage/section_swift-storage-node.xml:172(para) ./doc/install-guide/object-storage/section_start-storage-node-services.xml:28(para)
|
||||
#: ./doc/install-guide/section_keystone-install.xml:221(para) ./doc/install-guide/section_basics-database.xml:25(para) ./doc/install-guide/section_basics-database.xml:79(para) ./doc/install-guide/section_ceilometer-swift.xml:65(para) ./doc/install-guide/section_ceilometer-nova.xml:38(para) ./doc/install-guide/section_ceilometer-nova.xml:115(para) ./doc/install-guide/section_ceilometer-cinder.xml:29(para) ./doc/install-guide/section_ceilometer-cinder.xml:36(para) ./doc/install-guide/section_cinder-storage-node.xml:269(para) ./doc/install-guide/section_cinder-controller-node.xml:260(para) ./doc/install-guide/section_basics-ntp.xml:63(para) ./doc/install-guide/section_basics-ntp.xml:105(para) ./doc/install-guide/section_nova-controller-install.xml:279(para) ./doc/install-guide/section_nova-networking-compute-node.xml:66(para) ./doc/install-guide/section_glance-install.xml:277(para) ./doc/install-guide/section_dashboard-install.xml:138(para) ./doc/install-guide/section_neutron-compute-node.xml:218(para) ./doc/install-guide/section_neutron-compute-node.xml:306(para) ./doc/install-guide/section_neutron-compute-node.xml:318(para) ./doc/install-guide/section_neutron-controller-node.xml:397(para) ./doc/install-guide/section_neutron-controller-node.xml:412(para) ./doc/install-guide/section_neutron-network-node.xml:419(para) ./doc/install-guide/section_neutron-network-node.xml:443(para) ./doc/install-guide/section_neutron-network-node.xml:526(para) ./doc/install-guide/section_trove-install.xml:243(para) ./doc/install-guide/section_nova-networking-controller-node.xml:35(para) ./doc/install-guide/section_nova-compute-install.xml:220(para) ./doc/install-guide/section_heat-install.xml:295(para) ./doc/install-guide/section_ceilometer-glance.xml:29(para) ./doc/install-guide/section_basics-queue.xml:52(para) ./doc/install-guide/section_ceilometer-controller.xml:24(para) ./doc/install-guide/section_ceilometer-controller.xml:81(para) ./doc/install-guide/section_ceilometer-controller.xml:373(para) ./doc/install-guide/object-storage/section_swift-finalize-installation.xml:73(para) ./doc/install-guide/object-storage/section_swift-finalize-installation.xml:119(para) ./doc/install-guide/object-storage/section_swift-storage-node.xml:172(para) ./doc/install-guide/object-storage/section_start-storage-node-services.xml:28(para)
|
||||
msgid "On openSUSE:"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/install-guide/section_keystone-install.xml:219(para) ./doc/install-guide/section_heat-install.xml:302(para)
|
||||
#: ./doc/install-guide/section_keystone-install.xml:226(para) ./doc/install-guide/section_heat-install.xml:302(para)
|
||||
msgid "By default, the Ubuntu packages create a SQLite database."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/install-guide/section_keystone-install.xml:220(para) ./doc/install-guide/section_cinder-controller-node.xml:266(para) ./doc/install-guide/section_nova-controller-install.xml:289(para) ./doc/install-guide/section_glance-install.xml:283(para) ./doc/install-guide/section_nova-compute-install.xml:226(para) ./doc/install-guide/section_heat-install.xml:303(para)
|
||||
#: ./doc/install-guide/section_keystone-install.xml:227(para) ./doc/install-guide/section_cinder-controller-node.xml:266(para) ./doc/install-guide/section_nova-controller-install.xml:289(para) ./doc/install-guide/section_glance-install.xml:283(para) ./doc/install-guide/section_nova-compute-install.xml:226(para) ./doc/install-guide/section_heat-install.xml:303(para)
|
||||
msgid "Because this configuration uses a SQL database server, you can remove the SQLite database file:"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/install-guide/section_keystone-install.xml:225(para)
|
||||
#: ./doc/install-guide/section_keystone-install.xml:232(para)
|
||||
msgid "By default, the Identity service stores expired tokens in the database indefinitely. The accumulation of expired tokens considerably increases the database size and might degrade service performance, particularly in environments with limited resources."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/install-guide/section_keystone-install.xml:229(para)
|
||||
#: ./doc/install-guide/section_keystone-install.xml:236(para)
|
||||
msgid "We recommend that you use <systemitem class=\"service\">cron</systemitem> to configure a periodic task that purges expired tokens hourly:"
|
||||
msgstr ""
|
||||
|
||||
|
||||
@ -5,8 +5,8 @@
|
||||
msgid ""
|
||||
msgstr ""
|
||||
"Project-Id-Version: OpenStack Manuals\n"
|
||||
"POT-Creation-Date: 2015-01-20 20:43+0000\n"
|
||||
"PO-Revision-Date: 2015-01-20 18:33+0000\n"
|
||||
"POT-Creation-Date: 2015-01-31 02:01+0000\n"
|
||||
"PO-Revision-Date: 2015-01-31 02:02+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"
|
||||
@ -18,7 +18,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/install-guide/section_keystone-install.xml133(None)
|
||||
#: ./doc/install-guide/section_keystone-install.xml140(None)
|
||||
msgid ""
|
||||
"@@image: 'figures/debconf-screenshots/keystone_1_admin_token.png'; "
|
||||
"md5=29a51caaf09c3d6e3f0fda73c256a17a"
|
||||
@ -27,7 +27,7 @@ msgstr "@@image: 'figures/debconf-screenshots/keystone_1_admin_token.png'; md5=2
|
||||
#. 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/install-guide/section_keystone-install.xml147(None)
|
||||
#: ./doc/install-guide/section_keystone-install.xml154(None)
|
||||
msgid ""
|
||||
"@@image: 'figures/debconf-"
|
||||
"screenshots/keystone_2_register_admin_tenant_yes_no.png'; "
|
||||
@ -37,7 +37,7 @@ msgstr "@@image: 'figures/debconf-screenshots/keystone_2_register_admin_tenant_y
|
||||
#. 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/install-guide/section_keystone-install.xml156(None)
|
||||
#: ./doc/install-guide/section_keystone-install.xml163(None)
|
||||
msgid ""
|
||||
"@@image: 'figures/debconf-screenshots/keystone_3_admin_user_name.png'; "
|
||||
"md5=173cf7ed13252df1425109be588b2ad6"
|
||||
@ -46,7 +46,7 @@ msgstr "@@image: 'figures/debconf-screenshots/keystone_3_admin_user_name.png'; m
|
||||
#. 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/install-guide/section_keystone-install.xml165(None)
|
||||
#: ./doc/install-guide/section_keystone-install.xml172(None)
|
||||
msgid ""
|
||||
"@@image: 'figures/debconf-screenshots/keystone_4_admin_user_email.png'; "
|
||||
"md5=b7f0d34350ccc0aa9ae4e766b7ac80c1"
|
||||
@ -55,7 +55,7 @@ msgstr "@@image: 'figures/debconf-screenshots/keystone_4_admin_user_email.png';
|
||||
#. 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/install-guide/section_keystone-install.xml174(None)
|
||||
#: ./doc/install-guide/section_keystone-install.xml181(None)
|
||||
msgid ""
|
||||
"@@image: 'figures/debconf-screenshots/keystone_5_admin_user_pass.png'; "
|
||||
"md5=e6b32d8d80af90f07a66abc8fb256c84"
|
||||
@ -64,7 +64,7 @@ msgstr "@@image: 'figures/debconf-screenshots/keystone_5_admin_user_pass.png'; m
|
||||
#. 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/install-guide/section_keystone-install.xml183(None)
|
||||
#: ./doc/install-guide/section_keystone-install.xml190(None)
|
||||
msgid ""
|
||||
"@@image: 'figures/debconf-"
|
||||
"screenshots/keystone_6_admin_user_pass_confirm.png'; "
|
||||
@ -74,7 +74,7 @@ msgstr "@@image: 'figures/debconf-screenshots/keystone_6_admin_user_pass_confirm
|
||||
#. 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/install-guide/section_keystone-install.xml194(None)
|
||||
#: ./doc/install-guide/section_keystone-install.xml201(None)
|
||||
msgid ""
|
||||
"@@image: 'figures/debconf-screenshots/keystone_7_register_endpoint.png'; "
|
||||
"md5=d24d84133bfee936267e79631a2666e6"
|
||||
@ -175,12 +175,12 @@ msgid ""
|
||||
msgstr "初期設定中に管理トークンとして使用するために、ランダム値を生成します。"
|
||||
|
||||
#: ./doc/install-guide/section_keystone-install.xml60(title)
|
||||
#: ./doc/install-guide/section_keystone-install.xml120(title)
|
||||
#: ./doc/install-guide/section_keystone-install.xml127(title)
|
||||
msgid "To install and configure the components"
|
||||
msgstr "コンポーネントをインストールし、設定する方法"
|
||||
|
||||
#: ./doc/install-guide/section_keystone-install.xml62(para)
|
||||
#: ./doc/install-guide/section_keystone-install.xml122(para)
|
||||
#: ./doc/install-guide/section_keystone-install.xml129(para)
|
||||
msgid "Run the following command to install the packages:"
|
||||
msgstr "パッケージをインストールするために、以下のコマンドを実行します。"
|
||||
|
||||
@ -360,6 +360,12 @@ msgid ""
|
||||
msgstr "<literal>[token]</literal> セクションに、UUID トークンプロバイダーと SQL ドライバーを設定します。"
|
||||
|
||||
#: ./doc/install-guide/section_keystone-install.xml98(para)
|
||||
msgid ""
|
||||
"In the <literal>[revoke]</literal> section, configure the SQL revocation "
|
||||
"driver:"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/install-guide/section_keystone-install.xml105(para)
|
||||
#: ./doc/install-guide/section_cinder-storage-node.xml217(para)
|
||||
#: ./doc/install-guide/section_cinder-controller-node.xml212(para)
|
||||
#: ./doc/install-guide/section_nova-controller-install.xml200(para)
|
||||
@ -378,40 +384,40 @@ msgid ""
|
||||
"<literal>[DEFAULT]</literal> section:"
|
||||
msgstr "(オプション) トラブルシューティングしやすくするために、冗長ロギングを <literal>[DEFAULT]</literal> セクションで有効化します。"
|
||||
|
||||
#: ./doc/install-guide/section_keystone-install.xml107(para)
|
||||
#: ./doc/install-guide/section_keystone-install.xml114(para)
|
||||
msgid ""
|
||||
"Create generic certificates and keys and restrict access to the associated "
|
||||
"files:"
|
||||
msgstr "汎用的な証明書および暗号鍵を作成し、関連するファイルのアクセス権を制限します。"
|
||||
|
||||
#: ./doc/install-guide/section_keystone-install.xml115(para)
|
||||
#: ./doc/install-guide/section_keystone-install.xml122(para)
|
||||
msgid "Populate the Identity service database:"
|
||||
msgstr "Identity のデータベースに初期データを登録します。"
|
||||
|
||||
#: ./doc/install-guide/section_keystone-install.xml126(para)
|
||||
#: ./doc/install-guide/section_keystone-install.xml133(para)
|
||||
msgid "Respond to prompts for <xref linkend=\"debconf-dbconfig-common\"/>."
|
||||
msgstr "<xref linkend=\"debconf-dbconfig-common\"/> のプロンプトに入力します。"
|
||||
|
||||
#: ./doc/install-guide/section_keystone-install.xml129(para)
|
||||
#: ./doc/install-guide/section_keystone-install.xml136(para)
|
||||
msgid "Configure the initial administration token:"
|
||||
msgstr "初期管理トークンを設定します。"
|
||||
|
||||
#: ./doc/install-guide/section_keystone-install.xml137(para)
|
||||
#: ./doc/install-guide/section_keystone-install.xml144(para)
|
||||
msgid ""
|
||||
"Use the random value that you generated in a previous step. If you install "
|
||||
"using non-interactive mode or you do not specify this token, the "
|
||||
"configuration tool generates a random value."
|
||||
msgstr "前の手順で生成したランダムな値を使用します。非対話モードを使用してインストールした場合、このトークンを指定しなかった場合は、設定ツールがランダムな値を生成します。"
|
||||
|
||||
#: ./doc/install-guide/section_keystone-install.xml142(para)
|
||||
#: ./doc/install-guide/section_keystone-install.xml149(para)
|
||||
msgid "Create the <literal>admin</literal> tenant and user:"
|
||||
msgstr "<literal>admin</literal> プロジェクトとユーザーを作成します。"
|
||||
|
||||
#: ./doc/install-guide/section_keystone-install.xml189(para)
|
||||
#: ./doc/install-guide/section_keystone-install.xml196(para)
|
||||
msgid "Create the Identity service endpoints:"
|
||||
msgstr "Identity のエンドポイントを作成します。"
|
||||
|
||||
#: ./doc/install-guide/section_keystone-install.xml201(title)
|
||||
#: ./doc/install-guide/section_keystone-install.xml208(title)
|
||||
#: ./doc/install-guide/section_basics-database.xml66(title)
|
||||
#: ./doc/install-guide/section_basics-packages.xml138(title)
|
||||
#: ./doc/install-guide/section_cinder-storage-node.xml252(title)
|
||||
@ -426,16 +432,16 @@ msgstr "Identity のエンドポイントを作成します。"
|
||||
msgid "To finalize installation"
|
||||
msgstr "インストールの最終手順"
|
||||
|
||||
#: ./doc/install-guide/section_keystone-install.xml203(para)
|
||||
#: ./doc/install-guide/section_keystone-install.xml210(para)
|
||||
msgid "Restart the Identity service:"
|
||||
msgstr "Identity のサービスを再起動します。"
|
||||
|
||||
#: ./doc/install-guide/section_keystone-install.xml207(para)
|
||||
#: ./doc/install-guide/section_keystone-install.xml214(para)
|
||||
msgid ""
|
||||
"Start the Identity service and configure it to start when the system boots:"
|
||||
msgstr "Identity のサービスを起動し、システム起動時に起動するよう設定します。"
|
||||
|
||||
#: ./doc/install-guide/section_keystone-install.xml211(para)
|
||||
#: ./doc/install-guide/section_keystone-install.xml218(para)
|
||||
#: ./doc/install-guide/section_basics-database.xml27(para)
|
||||
#: ./doc/install-guide/section_basics-database.xml76(para)
|
||||
#: ./doc/install-guide/section_ceilometer-swift.xml63(para)
|
||||
@ -475,7 +481,7 @@ msgstr "Identity のサービスを起動し、システム起動時に起動す
|
||||
msgid "On SLES:"
|
||||
msgstr "SLES の場合:"
|
||||
|
||||
#: ./doc/install-guide/section_keystone-install.xml214(para)
|
||||
#: ./doc/install-guide/section_keystone-install.xml221(para)
|
||||
#: ./doc/install-guide/section_basics-database.xml25(para)
|
||||
#: ./doc/install-guide/section_basics-database.xml79(para)
|
||||
#: ./doc/install-guide/section_ceilometer-swift.xml65(para)
|
||||
@ -515,12 +521,12 @@ msgstr "SLES の場合:"
|
||||
msgid "On openSUSE:"
|
||||
msgstr "openSUSE の場合:"
|
||||
|
||||
#: ./doc/install-guide/section_keystone-install.xml219(para)
|
||||
#: ./doc/install-guide/section_keystone-install.xml226(para)
|
||||
#: ./doc/install-guide/section_heat-install.xml302(para)
|
||||
msgid "By default, the Ubuntu packages create a SQLite database."
|
||||
msgstr "Ubuntu パッケージは、デフォルトで SQLite データベースを作成します。"
|
||||
|
||||
#: ./doc/install-guide/section_keystone-install.xml220(para)
|
||||
#: ./doc/install-guide/section_keystone-install.xml227(para)
|
||||
#: ./doc/install-guide/section_cinder-controller-node.xml266(para)
|
||||
#: ./doc/install-guide/section_nova-controller-install.xml289(para)
|
||||
#: ./doc/install-guide/section_glance-install.xml283(para)
|
||||
@ -531,7 +537,7 @@ msgid ""
|
||||
"SQLite database file:"
|
||||
msgstr "この設定は SQL データベースサーバーを使用するため、SQLite データベースファイルを削除できます。"
|
||||
|
||||
#: ./doc/install-guide/section_keystone-install.xml225(para)
|
||||
#: ./doc/install-guide/section_keystone-install.xml232(para)
|
||||
msgid ""
|
||||
"By default, the Identity service stores expired tokens in the database "
|
||||
"indefinitely. The accumulation of expired tokens considerably increases the "
|
||||
@ -539,7 +545,7 @@ msgid ""
|
||||
"environments with limited resources."
|
||||
msgstr "Identity は、デフォルトで期限切れのトークンをデータベースに永続的に保持します。期限切れトークンの蓄積により、データベースの容量が大きくなり、サービスの性能が劣化する可能性があります。とくにリソースが限られている場合に顕著でしょう。"
|
||||
|
||||
#: ./doc/install-guide/section_keystone-install.xml229(para)
|
||||
#: ./doc/install-guide/section_keystone-install.xml236(para)
|
||||
msgid ""
|
||||
"We recommend that you use <systemitem class=\"service\">cron</systemitem> to"
|
||||
" configure a periodic task that purges expired tokens hourly:"
|
||||
|
||||
@ -17,9 +17,9 @@
|
||||
msgid ""
|
||||
msgstr ""
|
||||
"Project-Id-Version: OpenStack Manuals\n"
|
||||
"POT-Creation-Date: 2015-01-23 18:22+0000\n"
|
||||
"PO-Revision-Date: 2015-01-23 16:32+0000\n"
|
||||
"Last-Translator: Hak-Geon, Lee <withteas@gmail.com>\n"
|
||||
"POT-Creation-Date: 2015-01-31 02:01+0000\n"
|
||||
"PO-Revision-Date: 2015-01-31 02:02+0000\n"
|
||||
"Last-Translator: openstackjenkins <jenkins@openstack.org>\n"
|
||||
"Language-Team: Korean (Korea) (http://www.transifex.com/projects/p/openstack-manuals-i18n/language/ko_KR/)\n"
|
||||
"MIME-Version: 1.0\n"
|
||||
"Content-Type: text/plain; charset=UTF-8\n"
|
||||
@ -30,7 +30,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/install-guide/section_keystone-install.xml133(None)
|
||||
#: ./doc/install-guide/section_keystone-install.xml140(None)
|
||||
msgid ""
|
||||
"@@image: 'figures/debconf-screenshots/keystone_1_admin_token.png'; "
|
||||
"md5=29a51caaf09c3d6e3f0fda73c256a17a"
|
||||
@ -39,7 +39,7 @@ msgstr "@@image: 'figures/debconf-screenshots/keystone_1_admin_token.png'; md5=2
|
||||
#. 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/install-guide/section_keystone-install.xml147(None)
|
||||
#: ./doc/install-guide/section_keystone-install.xml154(None)
|
||||
msgid ""
|
||||
"@@image: 'figures/debconf-"
|
||||
"screenshots/keystone_2_register_admin_tenant_yes_no.png'; "
|
||||
@ -49,7 +49,7 @@ msgstr "@@image: 'figures/debconf-screenshots/keystone_2_register_admin_tenant_y
|
||||
#. 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/install-guide/section_keystone-install.xml156(None)
|
||||
#: ./doc/install-guide/section_keystone-install.xml163(None)
|
||||
msgid ""
|
||||
"@@image: 'figures/debconf-screenshots/keystone_3_admin_user_name.png'; "
|
||||
"md5=173cf7ed13252df1425109be588b2ad6"
|
||||
@ -58,7 +58,7 @@ msgstr "@@image: 'figures/debconf-screenshots/keystone_3_admin_user_name.png'; m
|
||||
#. 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/install-guide/section_keystone-install.xml165(None)
|
||||
#: ./doc/install-guide/section_keystone-install.xml172(None)
|
||||
msgid ""
|
||||
"@@image: 'figures/debconf-screenshots/keystone_4_admin_user_email.png'; "
|
||||
"md5=b7f0d34350ccc0aa9ae4e766b7ac80c1"
|
||||
@ -67,7 +67,7 @@ msgstr "@@image: 'figures/debconf-screenshots/keystone_4_admin_user_email.png';
|
||||
#. 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/install-guide/section_keystone-install.xml174(None)
|
||||
#: ./doc/install-guide/section_keystone-install.xml181(None)
|
||||
msgid ""
|
||||
"@@image: 'figures/debconf-screenshots/keystone_5_admin_user_pass.png'; "
|
||||
"md5=e6b32d8d80af90f07a66abc8fb256c84"
|
||||
@ -76,7 +76,7 @@ msgstr "@@image: 'figures/debconf-screenshots/keystone_5_admin_user_pass.png'; m
|
||||
#. 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/install-guide/section_keystone-install.xml183(None)
|
||||
#: ./doc/install-guide/section_keystone-install.xml190(None)
|
||||
msgid ""
|
||||
"@@image: 'figures/debconf-"
|
||||
"screenshots/keystone_6_admin_user_pass_confirm.png'; "
|
||||
@ -86,7 +86,7 @@ msgstr "@@image: 'figures/debconf-screenshots/keystone_6_admin_user_pass_confirm
|
||||
#. 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/install-guide/section_keystone-install.xml194(None)
|
||||
#: ./doc/install-guide/section_keystone-install.xml201(None)
|
||||
msgid ""
|
||||
"@@image: 'figures/debconf-screenshots/keystone_7_register_endpoint.png'; "
|
||||
"md5=d24d84133bfee936267e79631a2666e6"
|
||||
@ -187,12 +187,12 @@ msgid ""
|
||||
msgstr "초기설정동안 관리 토큰으로 사용할 무작위 값을 생성합니다:"
|
||||
|
||||
#: ./doc/install-guide/section_keystone-install.xml60(title)
|
||||
#: ./doc/install-guide/section_keystone-install.xml120(title)
|
||||
#: ./doc/install-guide/section_keystone-install.xml127(title)
|
||||
msgid "To install and configure the components"
|
||||
msgstr "컴포넌트들의 설치와 설정"
|
||||
|
||||
#: ./doc/install-guide/section_keystone-install.xml62(para)
|
||||
#: ./doc/install-guide/section_keystone-install.xml122(para)
|
||||
#: ./doc/install-guide/section_keystone-install.xml129(para)
|
||||
msgid "Run the following command to install the packages:"
|
||||
msgstr "패키지들을 설치하기 위해 다음 커맨드를 실행합니다:"
|
||||
|
||||
@ -372,6 +372,12 @@ msgid ""
|
||||
msgstr "<literal>[token]</literal> 섹션에서, UUID 토큰 provider와 SQL 드라이버를 설정하십시오:"
|
||||
|
||||
#: ./doc/install-guide/section_keystone-install.xml98(para)
|
||||
msgid ""
|
||||
"In the <literal>[revoke]</literal> section, configure the SQL revocation "
|
||||
"driver:"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/install-guide/section_keystone-install.xml105(para)
|
||||
#: ./doc/install-guide/section_cinder-storage-node.xml217(para)
|
||||
#: ./doc/install-guide/section_cinder-controller-node.xml212(para)
|
||||
#: ./doc/install-guide/section_nova-controller-install.xml200(para)
|
||||
@ -390,40 +396,40 @@ msgid ""
|
||||
"<literal>[DEFAULT]</literal> section:"
|
||||
msgstr "(선택사항) troubleshooting을 돕기 위해서, <literal>[DEFAULT]</literal> 섹션의 verbose logging을 활성화하십시오."
|
||||
|
||||
#: ./doc/install-guide/section_keystone-install.xml107(para)
|
||||
#: ./doc/install-guide/section_keystone-install.xml114(para)
|
||||
msgid ""
|
||||
"Create generic certificates and keys and restrict access to the associated "
|
||||
"files:"
|
||||
msgstr "인증서와 키들을 생성하고 관련파일의 접근을 제한합니다:"
|
||||
|
||||
#: ./doc/install-guide/section_keystone-install.xml115(para)
|
||||
#: ./doc/install-guide/section_keystone-install.xml122(para)
|
||||
msgid "Populate the Identity service database:"
|
||||
msgstr "Identity 서비스 데이터베이스를 넣어줍니다:"
|
||||
|
||||
#: ./doc/install-guide/section_keystone-install.xml126(para)
|
||||
#: ./doc/install-guide/section_keystone-install.xml133(para)
|
||||
msgid "Respond to prompts for <xref linkend=\"debconf-dbconfig-common\"/>."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/install-guide/section_keystone-install.xml129(para)
|
||||
#: ./doc/install-guide/section_keystone-install.xml136(para)
|
||||
msgid "Configure the initial administration token:"
|
||||
msgstr "초기 관리 토큰을 설정합니다:"
|
||||
|
||||
#: ./doc/install-guide/section_keystone-install.xml137(para)
|
||||
#: ./doc/install-guide/section_keystone-install.xml144(para)
|
||||
msgid ""
|
||||
"Use the random value that you generated in a previous step. If you install "
|
||||
"using non-interactive mode or you do not specify this token, the "
|
||||
"configuration tool generates a random value."
|
||||
msgstr "전단계에서 생성한 무작위값을 사용합니다. 만약 non-interactive mode로 설치했거나 토큰을 지정하지 않으면, 설정 툴이 무작위값을 생성합니다."
|
||||
|
||||
#: ./doc/install-guide/section_keystone-install.xml142(para)
|
||||
#: ./doc/install-guide/section_keystone-install.xml149(para)
|
||||
msgid "Create the <literal>admin</literal> tenant and user:"
|
||||
msgstr "<literal>admin</literal> tenant와 사용자를 생성합니다:"
|
||||
|
||||
#: ./doc/install-guide/section_keystone-install.xml189(para)
|
||||
#: ./doc/install-guide/section_keystone-install.xml196(para)
|
||||
msgid "Create the Identity service endpoints:"
|
||||
msgstr "Identity 서비스 엔드 포인트를 생성합니다:"
|
||||
|
||||
#: ./doc/install-guide/section_keystone-install.xml201(title)
|
||||
#: ./doc/install-guide/section_keystone-install.xml208(title)
|
||||
#: ./doc/install-guide/section_basics-database.xml66(title)
|
||||
#: ./doc/install-guide/section_basics-packages.xml138(title)
|
||||
#: ./doc/install-guide/section_cinder-storage-node.xml252(title)
|
||||
@ -438,16 +444,16 @@ msgstr "Identity 서비스 엔드 포인트를 생성합니다:"
|
||||
msgid "To finalize installation"
|
||||
msgstr "설치 후"
|
||||
|
||||
#: ./doc/install-guide/section_keystone-install.xml203(para)
|
||||
#: ./doc/install-guide/section_keystone-install.xml210(para)
|
||||
msgid "Restart the Identity service:"
|
||||
msgstr "인증 서비스 다시 시작:"
|
||||
|
||||
#: ./doc/install-guide/section_keystone-install.xml207(para)
|
||||
#: ./doc/install-guide/section_keystone-install.xml214(para)
|
||||
msgid ""
|
||||
"Start the Identity service and configure it to start when the system boots:"
|
||||
msgstr "Identity 서비스를 시작하고 시스템 부팅시 시작하도록 설정합니다:"
|
||||
|
||||
#: ./doc/install-guide/section_keystone-install.xml211(para)
|
||||
#: ./doc/install-guide/section_keystone-install.xml218(para)
|
||||
#: ./doc/install-guide/section_basics-database.xml27(para)
|
||||
#: ./doc/install-guide/section_basics-database.xml76(para)
|
||||
#: ./doc/install-guide/section_ceilometer-swift.xml63(para)
|
||||
@ -487,7 +493,7 @@ msgstr "Identity 서비스를 시작하고 시스템 부팅시 시작하도록
|
||||
msgid "On SLES:"
|
||||
msgstr "SLES 상에서:"
|
||||
|
||||
#: ./doc/install-guide/section_keystone-install.xml214(para)
|
||||
#: ./doc/install-guide/section_keystone-install.xml221(para)
|
||||
#: ./doc/install-guide/section_basics-database.xml25(para)
|
||||
#: ./doc/install-guide/section_basics-database.xml79(para)
|
||||
#: ./doc/install-guide/section_ceilometer-swift.xml65(para)
|
||||
@ -527,12 +533,12 @@ msgstr "SLES 상에서:"
|
||||
msgid "On openSUSE:"
|
||||
msgstr "openSUSE 상에서:"
|
||||
|
||||
#: ./doc/install-guide/section_keystone-install.xml219(para)
|
||||
#: ./doc/install-guide/section_keystone-install.xml226(para)
|
||||
#: ./doc/install-guide/section_heat-install.xml302(para)
|
||||
msgid "By default, the Ubuntu packages create a SQLite database."
|
||||
msgstr "디폴트로, Ubuntu 패키지는 SQLite 데이터베이스를 생성합니다."
|
||||
|
||||
#: ./doc/install-guide/section_keystone-install.xml220(para)
|
||||
#: ./doc/install-guide/section_keystone-install.xml227(para)
|
||||
#: ./doc/install-guide/section_cinder-controller-node.xml266(para)
|
||||
#: ./doc/install-guide/section_nova-controller-install.xml289(para)
|
||||
#: ./doc/install-guide/section_glance-install.xml283(para)
|
||||
@ -543,7 +549,7 @@ msgid ""
|
||||
"SQLite database file:"
|
||||
msgstr "이 설정에서는 SQL 데이터베이스 서버를 이용하기 때문에, SQLite 데이터베이스 파일을 제거할 수 있습니다:"
|
||||
|
||||
#: ./doc/install-guide/section_keystone-install.xml225(para)
|
||||
#: ./doc/install-guide/section_keystone-install.xml232(para)
|
||||
msgid ""
|
||||
"By default, the Identity service stores expired tokens in the database "
|
||||
"indefinitely. The accumulation of expired tokens considerably increases the "
|
||||
@ -551,7 +557,7 @@ msgid ""
|
||||
"environments with limited resources."
|
||||
msgstr "기본설정으로 Identity 서비스는 만료된 토큰들을 데이터베이스에 무기한으로 저장합니다. 만료된 토큰들을 축적하는 것은 제한된 리소스의 특정 환경에서는 데이터베이스의 크기를 매우 커지게하고 서비스 성능을 떨어트릴 수 있습니다."
|
||||
|
||||
#: ./doc/install-guide/section_keystone-install.xml229(para)
|
||||
#: ./doc/install-guide/section_keystone-install.xml236(para)
|
||||
msgid ""
|
||||
"We recommend that you use <systemitem class=\"service\">cron</systemitem> to"
|
||||
" configure a periodic task that purges expired tokens hourly:"
|
||||
|
||||
@ -12,9 +12,9 @@
|
||||
msgid ""
|
||||
msgstr ""
|
||||
"Project-Id-Version: OpenStack Manuals\n"
|
||||
"POT-Creation-Date: 2015-01-20 20:43+0000\n"
|
||||
"PO-Revision-Date: 2015-01-21 00:31+0000\n"
|
||||
"Last-Translator: Fernando Pimenta <fernando.c.pimenta@gmail.com>\n"
|
||||
"POT-Creation-Date: 2015-01-31 02:01+0000\n"
|
||||
"PO-Revision-Date: 2015-01-31 02:02+0000\n"
|
||||
"Last-Translator: openstackjenkins <jenkins@openstack.org>\n"
|
||||
"Language-Team: Portuguese (Brazil) (http://www.transifex.com/projects/p/openstack-manuals-i18n/language/pt_BR/)\n"
|
||||
"MIME-Version: 1.0\n"
|
||||
"Content-Type: text/plain; charset=UTF-8\n"
|
||||
@ -25,7 +25,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/install-guide/section_keystone-install.xml133(None)
|
||||
#: ./doc/install-guide/section_keystone-install.xml140(None)
|
||||
msgid ""
|
||||
"@@image: 'figures/debconf-screenshots/keystone_1_admin_token.png'; "
|
||||
"md5=29a51caaf09c3d6e3f0fda73c256a17a"
|
||||
@ -34,7 +34,7 @@ msgstr "@@image: 'figures/debconf-screenshots/keystone_1_admin_token.png'; md5=2
|
||||
#. 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/install-guide/section_keystone-install.xml147(None)
|
||||
#: ./doc/install-guide/section_keystone-install.xml154(None)
|
||||
msgid ""
|
||||
"@@image: 'figures/debconf-"
|
||||
"screenshots/keystone_2_register_admin_tenant_yes_no.png'; "
|
||||
@ -44,7 +44,7 @@ msgstr "@@image: 'figures/debconf-screenshots/keystone_2_register_admin_tenant_y
|
||||
#. 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/install-guide/section_keystone-install.xml156(None)
|
||||
#: ./doc/install-guide/section_keystone-install.xml163(None)
|
||||
msgid ""
|
||||
"@@image: 'figures/debconf-screenshots/keystone_3_admin_user_name.png'; "
|
||||
"md5=173cf7ed13252df1425109be588b2ad6"
|
||||
@ -53,7 +53,7 @@ msgstr "@@image: 'figures/debconf-screenshots/keystone_3_admin_user_name.png'; m
|
||||
#. 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/install-guide/section_keystone-install.xml165(None)
|
||||
#: ./doc/install-guide/section_keystone-install.xml172(None)
|
||||
msgid ""
|
||||
"@@image: 'figures/debconf-screenshots/keystone_4_admin_user_email.png'; "
|
||||
"md5=b7f0d34350ccc0aa9ae4e766b7ac80c1"
|
||||
@ -62,7 +62,7 @@ msgstr "@@image: 'figures/debconf-screenshots/keystone_4_admin_user_email.png';
|
||||
#. 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/install-guide/section_keystone-install.xml174(None)
|
||||
#: ./doc/install-guide/section_keystone-install.xml181(None)
|
||||
msgid ""
|
||||
"@@image: 'figures/debconf-screenshots/keystone_5_admin_user_pass.png'; "
|
||||
"md5=e6b32d8d80af90f07a66abc8fb256c84"
|
||||
@ -71,7 +71,7 @@ msgstr "@@image: 'figures/debconf-screenshots/keystone_5_admin_user_pass.png'; m
|
||||
#. 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/install-guide/section_keystone-install.xml183(None)
|
||||
#: ./doc/install-guide/section_keystone-install.xml190(None)
|
||||
msgid ""
|
||||
"@@image: 'figures/debconf-"
|
||||
"screenshots/keystone_6_admin_user_pass_confirm.png'; "
|
||||
@ -81,7 +81,7 @@ msgstr "@@image: 'figures/debconf-screenshots/keystone_6_admin_user_pass_confirm
|
||||
#. 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/install-guide/section_keystone-install.xml194(None)
|
||||
#: ./doc/install-guide/section_keystone-install.xml201(None)
|
||||
msgid ""
|
||||
"@@image: 'figures/debconf-screenshots/keystone_7_register_endpoint.png'; "
|
||||
"md5=d24d84133bfee936267e79631a2666e6"
|
||||
@ -182,12 +182,12 @@ msgid ""
|
||||
msgstr "Gere um valor aleatório para utilizar como token de administração durante a configuração inicial:"
|
||||
|
||||
#: ./doc/install-guide/section_keystone-install.xml60(title)
|
||||
#: ./doc/install-guide/section_keystone-install.xml120(title)
|
||||
#: ./doc/install-guide/section_keystone-install.xml127(title)
|
||||
msgid "To install and configure the components"
|
||||
msgstr "Para instalar e configurar os componentes"
|
||||
|
||||
#: ./doc/install-guide/section_keystone-install.xml62(para)
|
||||
#: ./doc/install-guide/section_keystone-install.xml122(para)
|
||||
#: ./doc/install-guide/section_keystone-install.xml129(para)
|
||||
msgid "Run the following command to install the packages:"
|
||||
msgstr "Execute os seguintes comandos para instalar os pacotes:"
|
||||
|
||||
@ -367,6 +367,12 @@ msgid ""
|
||||
msgstr "Na seção <literal>[token]</literal>, configure o provedor do token UUID e o driver SQL:"
|
||||
|
||||
#: ./doc/install-guide/section_keystone-install.xml98(para)
|
||||
msgid ""
|
||||
"In the <literal>[revoke]</literal> section, configure the SQL revocation "
|
||||
"driver:"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/install-guide/section_keystone-install.xml105(para)
|
||||
#: ./doc/install-guide/section_cinder-storage-node.xml217(para)
|
||||
#: ./doc/install-guide/section_cinder-controller-node.xml212(para)
|
||||
#: ./doc/install-guide/section_nova-controller-install.xml200(para)
|
||||
@ -385,40 +391,40 @@ msgid ""
|
||||
"<literal>[DEFAULT]</literal> section:"
|
||||
msgstr "(Opcional) Para auxiliar com a solução de problemas, habilite o log detalhado na seção <literal>[DEFAULT]</literal> :"
|
||||
|
||||
#: ./doc/install-guide/section_keystone-install.xml107(para)
|
||||
#: ./doc/install-guide/section_keystone-install.xml114(para)
|
||||
msgid ""
|
||||
"Create generic certificates and keys and restrict access to the associated "
|
||||
"files:"
|
||||
msgstr "Crie certificados e chaves genéricos e restrinja o acesso aos arquivos associados:"
|
||||
|
||||
#: ./doc/install-guide/section_keystone-install.xml115(para)
|
||||
#: ./doc/install-guide/section_keystone-install.xml122(para)
|
||||
msgid "Populate the Identity service database:"
|
||||
msgstr "Popule a base de dados do Serviço de Identidade:"
|
||||
|
||||
#: ./doc/install-guide/section_keystone-install.xml126(para)
|
||||
#: ./doc/install-guide/section_keystone-install.xml133(para)
|
||||
msgid "Respond to prompts for <xref linkend=\"debconf-dbconfig-common\"/>."
|
||||
msgstr "Responda às questões para <xref linkend=\"debconf-dbconfig-common\"/>."
|
||||
|
||||
#: ./doc/install-guide/section_keystone-install.xml129(para)
|
||||
#: ./doc/install-guide/section_keystone-install.xml136(para)
|
||||
msgid "Configure the initial administration token:"
|
||||
msgstr "Configure o token de administração inicial:"
|
||||
|
||||
#: ./doc/install-guide/section_keystone-install.xml137(para)
|
||||
#: ./doc/install-guide/section_keystone-install.xml144(para)
|
||||
msgid ""
|
||||
"Use the random value that you generated in a previous step. If you install "
|
||||
"using non-interactive mode or you do not specify this token, the "
|
||||
"configuration tool generates a random value."
|
||||
msgstr "Utilize o valor aleatório que você gerou no passo anterior. Se você instalar usando o modo não interativo ou você não especificar este token, a ferramenta de configuração gera um valor aleatório."
|
||||
|
||||
#: ./doc/install-guide/section_keystone-install.xml142(para)
|
||||
#: ./doc/install-guide/section_keystone-install.xml149(para)
|
||||
msgid "Create the <literal>admin</literal> tenant and user:"
|
||||
msgstr "Crie o tenant e o usuário <literal>admin</literal>:"
|
||||
|
||||
#: ./doc/install-guide/section_keystone-install.xml189(para)
|
||||
#: ./doc/install-guide/section_keystone-install.xml196(para)
|
||||
msgid "Create the Identity service endpoints:"
|
||||
msgstr "Crie os endpoints do Serviço de Identidade:"
|
||||
|
||||
#: ./doc/install-guide/section_keystone-install.xml201(title)
|
||||
#: ./doc/install-guide/section_keystone-install.xml208(title)
|
||||
#: ./doc/install-guide/section_basics-database.xml66(title)
|
||||
#: ./doc/install-guide/section_basics-packages.xml138(title)
|
||||
#: ./doc/install-guide/section_cinder-storage-node.xml252(title)
|
||||
@ -433,16 +439,16 @@ msgstr "Crie os endpoints do Serviço de Identidade:"
|
||||
msgid "To finalize installation"
|
||||
msgstr "Para finalizar a instalação"
|
||||
|
||||
#: ./doc/install-guide/section_keystone-install.xml203(para)
|
||||
#: ./doc/install-guide/section_keystone-install.xml210(para)
|
||||
msgid "Restart the Identity service:"
|
||||
msgstr "Reinicie o serviço de Identidade:"
|
||||
|
||||
#: ./doc/install-guide/section_keystone-install.xml207(para)
|
||||
#: ./doc/install-guide/section_keystone-install.xml214(para)
|
||||
msgid ""
|
||||
"Start the Identity service and configure it to start when the system boots:"
|
||||
msgstr "Inicie o serviço de Identidade e configure-o para iniciar quando o sistema inicializar:"
|
||||
|
||||
#: ./doc/install-guide/section_keystone-install.xml211(para)
|
||||
#: ./doc/install-guide/section_keystone-install.xml218(para)
|
||||
#: ./doc/install-guide/section_basics-database.xml27(para)
|
||||
#: ./doc/install-guide/section_basics-database.xml76(para)
|
||||
#: ./doc/install-guide/section_ceilometer-swift.xml63(para)
|
||||
@ -482,7 +488,7 @@ msgstr "Inicie o serviço de Identidade e configure-o para iniciar quando o sist
|
||||
msgid "On SLES:"
|
||||
msgstr "No SLES:"
|
||||
|
||||
#: ./doc/install-guide/section_keystone-install.xml214(para)
|
||||
#: ./doc/install-guide/section_keystone-install.xml221(para)
|
||||
#: ./doc/install-guide/section_basics-database.xml25(para)
|
||||
#: ./doc/install-guide/section_basics-database.xml79(para)
|
||||
#: ./doc/install-guide/section_ceilometer-swift.xml65(para)
|
||||
@ -522,12 +528,12 @@ msgstr "No SLES:"
|
||||
msgid "On openSUSE:"
|
||||
msgstr "No OpenSUSE:"
|
||||
|
||||
#: ./doc/install-guide/section_keystone-install.xml219(para)
|
||||
#: ./doc/install-guide/section_keystone-install.xml226(para)
|
||||
#: ./doc/install-guide/section_heat-install.xml302(para)
|
||||
msgid "By default, the Ubuntu packages create a SQLite database."
|
||||
msgstr "Por padrão, os pacotes do Ubuntu criam um banco de dados SQLite."
|
||||
|
||||
#: ./doc/install-guide/section_keystone-install.xml220(para)
|
||||
#: ./doc/install-guide/section_keystone-install.xml227(para)
|
||||
#: ./doc/install-guide/section_cinder-controller-node.xml266(para)
|
||||
#: ./doc/install-guide/section_nova-controller-install.xml289(para)
|
||||
#: ./doc/install-guide/section_glance-install.xml283(para)
|
||||
@ -538,7 +544,7 @@ msgid ""
|
||||
"SQLite database file:"
|
||||
msgstr "Devido esta configuração utilizar um servidor de banco de dados SQL, você pode remover o arquivo de banco de dados SQLite:"
|
||||
|
||||
#: ./doc/install-guide/section_keystone-install.xml225(para)
|
||||
#: ./doc/install-guide/section_keystone-install.xml232(para)
|
||||
msgid ""
|
||||
"By default, the Identity service stores expired tokens in the database "
|
||||
"indefinitely. The accumulation of expired tokens considerably increases the "
|
||||
@ -546,7 +552,7 @@ msgid ""
|
||||
"environments with limited resources."
|
||||
msgstr "Por padrão, o serviço de Identidade armazena os tokens expirados na base de dados indefinidamente. A acumulação de tokens expirados aumenta consideravelmente o tamanho da base de dados e pode degradar o desempenho do sistema, particularmente em ambientes com recursos limitados."
|
||||
|
||||
#: ./doc/install-guide/section_keystone-install.xml229(para)
|
||||
#: ./doc/install-guide/section_keystone-install.xml236(para)
|
||||
msgid ""
|
||||
"We recommend that you use <systemitem class=\"service\">cron</systemitem> to"
|
||||
" configure a periodic task that purges expired tokens hourly:"
|
||||
|
||||
Loading…
x
Reference in New Issue
Block a user