Imported Translations from Transifex
For more information about this automatic import see: https://wiki.openstack.org/wiki/Translations/Infrastructure Change-Id: Icde63a99dec3d65bd65fb6d0b94e42844de4facb
This commit is contained in:
OpenStack Proposal Bot
parent
88cc776a5c
commit
cda8e87785
@ -8,7 +8,7 @@ msgid ""
|
||||
msgstr ""
|
||||
"Project-Id-Version: Cloud Administrator Guide 0.9\n"
|
||||
"Report-Msgid-Bugs-To: \n"
|
||||
"POT-Creation-Date: 2015-09-02 06:15+0000\n"
|
||||
"POT-Creation-Date: 2015-09-03 06:14+0000\n"
|
||||
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
|
||||
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
|
||||
"Language-Team: LANGUAGE <LL@li.org>\n"
|
||||
@ -16,6 +16,11 @@ msgstr ""
|
||||
"Content-Type: text/plain; charset=UTF-8\n"
|
||||
"Content-Transfer-Encoding: 8bit\n"
|
||||
|
||||
#: ../objectstorage_auditors.rst:14
|
||||
msgid ""
|
||||
"\"-z\" means to only check for zero-byte files at 1000 files per second."
|
||||
msgstr ""
|
||||
|
||||
#: ../telemetry-measurements.rst:122 ../telemetry-measurements.rst:216
|
||||
#: ../telemetry-measurements.rst:443 ../telemetry-measurements.rst:446
|
||||
#: ../telemetry-measurements.rst:449 ../telemetry-measurements.rst:452
|
||||
@ -9378,6 +9383,12 @@ msgid ""
|
||||
"following:"
|
||||
msgstr ""
|
||||
|
||||
#: ../objectstorage_auditors.rst:16
|
||||
msgid ""
|
||||
"It is useful to run the object auditor on a specific device or set of "
|
||||
"devices. You can run the object-auditor once as follows::"
|
||||
msgstr ""
|
||||
|
||||
#: ../blockstorage-driver-filter-weighing.rst:63
|
||||
msgid ""
|
||||
"It is useful to use the other filters and weighers available in OpenStack in "
|
||||
@ -10773,6 +10784,10 @@ msgstr ""
|
||||
msgid "OS-EXT-SRV-ATTR:host"
|
||||
msgstr ""
|
||||
|
||||
#: ../objectstorage_auditors.rst:3
|
||||
msgid "Object Auditor"
|
||||
msgstr ""
|
||||
|
||||
# #-#-#-#-# compute-images-instances.pot (Cloud Administrator Guide 0.9) #-#-#-#-#
|
||||
# #-#-#-#-# objectstorage.pot (Cloud Administrator Guide 0.9) #-#-#-#-#
|
||||
#: ../compute-images-instances.rst:127 ../objectstorage.rst:3
|
||||
@ -10929,6 +10944,15 @@ msgstr ""
|
||||
msgid "On openSUSE::"
|
||||
msgstr ""
|
||||
|
||||
#: ../objectstorage_auditors.rst:5
|
||||
msgid ""
|
||||
"On system failures, the XFS file system can sometimes truncate files it is "
|
||||
"trying to write and produce zero-byte files. The object-auditor will catch "
|
||||
"these problems but in the case of a system crash it is advisable to run an "
|
||||
"extra, less rate limited sweep, to check for these specific files. You can "
|
||||
"run this command as follows::"
|
||||
msgstr ""
|
||||
|
||||
#: ../ts_no_emulator_x86_64.rst:14
|
||||
msgid ""
|
||||
"On the KVM host, run ``cat /proc/cpuinfo``. Make sure the ``vmx`` or ``svm`` "
|
||||
@ -18052,6 +18076,12 @@ msgid ""
|
||||
"package installed on the compute node::"
|
||||
msgstr ""
|
||||
|
||||
#: ../objectstorage_auditors.rst:23
|
||||
msgid ""
|
||||
"This will run the object auditor on only the sda and sdb devices. This "
|
||||
"parameter accepts a comma separated list of values."
|
||||
msgstr ""
|
||||
|
||||
#: ../telemetry-alarms.rst:33
|
||||
msgid "Threshold rule alarms"
|
||||
msgstr ""
|
||||
|
||||
@ -1,7 +1,7 @@
|
||||
msgid ""
|
||||
msgstr ""
|
||||
"Project-Id-Version: PACKAGE VERSION\n"
|
||||
"POT-Creation-Date: 2015-08-29 06:14+0000\n"
|
||||
"POT-Creation-Date: 2015-09-03 06:14+0000\n"
|
||||
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
|
||||
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
|
||||
"Language-Team: LANGUAGE <LL@li.org>\n"
|
||||
@ -121,7 +121,7 @@ msgstr ""
|
||||
msgid "Examples of such legal frameworks include the <link xlink:href=\"http://ec.europa.eu/justice/data-protection/\">data protection framework</link> of the European Union and the requirements of the <link xlink:href=\"http://www.finra.org/Industry/Regulation/FINRARules/\"> Financial Industry Regulatory Authority</link> in the United States. Consult a local regulatory body for more information."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/ch_legal-security-requirements.xml:48(title) ./doc/arch-design/storage_focus/section_tech_considerations_storage_focus.xml:47(term) ./doc/arch-design/storage_focus/section_architecture_storage_focus.xml:432(term) ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:154(para) ./doc/arch-design/hybrid/section_architecture_hybrid.xml:112(para) ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:630(term) ./doc/arch-design/generalpurpose/section_tech_considerations_general_purpose.xml:713(title) ./doc/arch-design/generalpurpose/section_user_requirements_general_purpose.xml:154(term)
|
||||
#: ./doc/arch-design/ch_legal-security-requirements.xml:48(title) ./doc/arch-design/storage_focus/section_tech_considerations_storage_focus.xml:47(term) ./doc/arch-design/storage_focus/section_architecture_storage_focus.xml:432(term) ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:154(para) ./doc/arch-design/hybrid/section_architecture_hybrid.xml:112(para) ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:581(term) ./doc/arch-design/generalpurpose/section_tech_considerations_general_purpose.xml:713(title) ./doc/arch-design/generalpurpose/section_user_requirements_general_purpose.xml:154(term)
|
||||
msgid "Security"
|
||||
msgstr ""
|
||||
|
||||
@ -253,7 +253,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. OpenStack Networking (neutron) does not presently support a mechanism to provide this functionality, therefore an external system may be necessary to manage these mappings. Tenant networks may contain sensitive information requiring that this mapping be accurate and consistent to ensure that a tenant in one site does not connect to a different tenant in another site."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/ch_legal-security-requirements.xml:227(title) ./doc/arch-design/storage_focus/section_architecture_storage_focus.xml:361(para) ./doc/arch-design/storage_focus/section_architecture_storage_focus.xml:470(title) ./doc/arch-design/compute_focus/section_tech_considerations_compute_focus.xml:219(title) ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:166(title) ./doc/arch-design/multi_site/section_tech_considerations_multi_site.xml:144(title) ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:560(para) ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:667(title) ./doc/arch-design/generalpurpose/section_tech_considerations_general_purpose.xml:440(title)
|
||||
#: ./doc/arch-design/ch_legal-security-requirements.xml:227(title) ./doc/arch-design/storage_focus/section_architecture_storage_focus.xml:361(para) ./doc/arch-design/storage_focus/section_architecture_storage_focus.xml:470(title) ./doc/arch-design/compute_focus/section_tech_considerations_compute_focus.xml:219(title) ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:166(title) ./doc/arch-design/multi_site/section_tech_considerations_multi_site.xml:144(title) ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:512(para) ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:617(title) ./doc/arch-design/generalpurpose/section_tech_considerations_general_purpose.xml:440(title)
|
||||
msgid "OpenStack components"
|
||||
msgstr ""
|
||||
|
||||
@ -1373,7 +1373,7 @@ msgstr ""
|
||||
msgid "When designing a network architecture, the traffic patterns of an application heavily influence the allocation of total bandwidth and the number of links that you use to send and receive traffic. Applications that provide file storage for customers allocate bandwidth and links to favor incoming traffic, whereas video streaming applications allocate bandwidth and links to favor outgoing traffic."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/network_focus/section_tech_considerations_network_focus.xml:415(title) ./doc/arch-design/storage_focus/section_architecture_storage_focus.xml:18(para) ./doc/arch-design/storage_focus/section_architecture_storage_focus.xml:42(term) ./doc/arch-design/multi_site/section_tech_considerations_multi_site.xml:118(title) ./doc/arch-design/hybrid/section_tech_considerations_hybrid.xml:108(title) ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:387(term) ./doc/arch-design/generalpurpose/section_tech_considerations_general_purpose.xml:525(title) ./doc/arch-design/generalpurpose/section_user_requirements_general_purpose.xml:83(term)
|
||||
#: ./doc/arch-design/network_focus/section_tech_considerations_network_focus.xml:415(title) ./doc/arch-design/storage_focus/section_architecture_storage_focus.xml:18(para) ./doc/arch-design/storage_focus/section_architecture_storage_focus.xml:42(term) ./doc/arch-design/multi_site/section_tech_considerations_multi_site.xml:118(title) ./doc/arch-design/hybrid/section_tech_considerations_hybrid.xml:108(title) ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:347(term) ./doc/arch-design/generalpurpose/section_tech_considerations_general_purpose.xml:525(title) ./doc/arch-design/generalpurpose/section_user_requirements_general_purpose.xml:83(term)
|
||||
msgid "Performance"
|
||||
msgstr ""
|
||||
|
||||
@ -1907,7 +1907,7 @@ msgstr ""
|
||||
msgid "Consider the following factors when selecting storage hardware:"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/storage_focus/section_architecture_storage_focus.xml:15(para) ./doc/arch-design/storage_focus/section_architecture_storage_focus.xml:35(term) ./doc/arch-design/storage_focus/section_architecture_storage_focus.xml:147(term) ./doc/arch-design/storage_focus/section_architecture_storage_focus.xml:384(term) ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:35(para) ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:142(para) ./doc/arch-design/multi_site/section_user_requirements_multi_site.xml:99(title) ./doc/arch-design/hybrid/section_user_requirements_hybrid.xml:17(term) ./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/storage_focus/section_architecture_storage_focus.xml:15(para) ./doc/arch-design/storage_focus/section_architecture_storage_focus.xml:35(term) ./doc/arch-design/storage_focus/section_architecture_storage_focus.xml:147(term) ./doc/arch-design/storage_focus/section_architecture_storage_focus.xml:384(term) ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:35(para) ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:142(para) ./doc/arch-design/multi_site/section_user_requirements_multi_site.xml:99(title) ./doc/arch-design/hybrid/section_user_requirements_hybrid.xml:17(term) ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:95(term) ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:229(term) ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:534(term) ./doc/arch-design/generalpurpose/section_user_requirements_general_purpose.xml:24(term)
|
||||
msgid "Cost"
|
||||
msgstr ""
|
||||
|
||||
@ -1931,7 +1931,7 @@ msgstr ""
|
||||
msgid "The latency of storage I/O requests indicates performance. Performance requirements affect which solution you choose."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/storage_focus/section_architecture_storage_focus.xml:49(term) ./doc/arch-design/hybrid/section_architecture_hybrid.xml:117(para) ./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/storage_focus/section_architecture_storage_focus.xml:49(term) ./doc/arch-design/hybrid/section_architecture_hybrid.xml:117(para) ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:243(term) ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:472(term)
|
||||
msgid "Scalability"
|
||||
msgstr ""
|
||||
|
||||
@ -1955,7 +1955,7 @@ msgstr ""
|
||||
msgid "Considerations affecting storage architecture (and corresponding storage hardware) of a Storage-focused OpenStack cloud include:"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/storage_focus/section_architecture_storage_focus.xml:81(term) ./doc/arch-design/introduction/section_methodology.xml:102(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/storage_focus/section_architecture_storage_focus.xml:81(term) ./doc/arch-design/introduction/section_methodology.xml:102(term) ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:281(term) ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:459(term)
|
||||
msgid "Connectivity"
|
||||
msgstr ""
|
||||
|
||||
@ -1979,7 +1979,7 @@ msgstr ""
|
||||
msgid "Ensure that the storage solution throughput is optimized for your application requirements."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/storage_focus/section_architecture_storage_focus.xml:109(term) ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:351(term)
|
||||
#: ./doc/arch-design/storage_focus/section_architecture_storage_focus.xml:109(term) ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:311(term)
|
||||
msgid "Server hardware"
|
||||
msgstr ""
|
||||
|
||||
@ -1995,15 +1995,15 @@ msgstr ""
|
||||
msgid "Four opposing factors determine the compute (server) hardware selection:"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/storage_focus/section_architecture_storage_focus.xml:125(term) ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:26(para) ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:75(term)
|
||||
#: ./doc/arch-design/storage_focus/section_architecture_storage_focus.xml:125(term) ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:26(para) ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:73(term)
|
||||
msgid "Server density"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/storage_focus/section_architecture_storage_focus.xml:127(para) ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:77(para)
|
||||
#: ./doc/arch-design/storage_focus/section_architecture_storage_focus.xml:127(para) ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:75(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/storage_focus/section_architecture_storage_focus.xml:133(term) ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:29(para) ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:83(term)
|
||||
#: ./doc/arch-design/storage_focus/section_architecture_storage_focus.xml:133(term) ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:29(para) ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:81(term)
|
||||
msgid "Resource capacity"
|
||||
msgstr ""
|
||||
|
||||
@ -2011,7 +2011,7 @@ msgstr ""
|
||||
msgid "The number of CPU cores, how much RAM, or how much storage a given server delivers."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/storage_focus/section_architecture_storage_focus.xml:140(term) ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:32(para) ./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/storage_focus/section_architecture_storage_focus.xml:140(term) ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:32(para) ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:88(term) ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:255(term)
|
||||
msgid "Expandability"
|
||||
msgstr ""
|
||||
|
||||
@ -2079,7 +2079,7 @@ msgstr ""
|
||||
msgid "Other factors that influence server hardware selection for a storage-focused OpenStack design architecture include:"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/storage_focus/section_architecture_storage_focus.xml:237(term) ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:93(para) ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:172(term)
|
||||
#: ./doc/arch-design/storage_focus/section_architecture_storage_focus.xml:237(term) ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:93(para) ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:161(term)
|
||||
msgid "Instance density"
|
||||
msgstr ""
|
||||
|
||||
@ -2087,7 +2087,7 @@ msgstr ""
|
||||
msgid "In this architecture, instance density and CPU-RAM oversubscription are lower. You require more hosts to support the anticipated scale, especially if the design uses dual-socket hardware designs."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/storage_focus/section_architecture_storage_focus.xml:247(term) ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:96(para) ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:184(term)
|
||||
#: ./doc/arch-design/storage_focus/section_architecture_storage_focus.xml:247(term) ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:96(para) ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:173(term)
|
||||
msgid "Host density"
|
||||
msgstr ""
|
||||
|
||||
@ -2115,7 +2115,7 @@ msgstr ""
|
||||
msgid "Key considerations for the selection of networking hardware include:"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/storage_focus/section_architecture_storage_focus.xml:283(term) ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:109(para) ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:446(term)
|
||||
#: ./doc/arch-design/storage_focus/section_architecture_storage_focus.xml:283(term) ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:109(para) ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:397(term)
|
||||
msgid "Port count"
|
||||
msgstr ""
|
||||
|
||||
@ -2123,7 +2123,7 @@ msgstr ""
|
||||
msgid "The user requires networking hardware that has the requisite port count."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/storage_focus/section_architecture_storage_focus.xml:290(term) ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:112(para) ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:453(term)
|
||||
#: ./doc/arch-design/storage_focus/section_architecture_storage_focus.xml:290(term) ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:112(para) ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:404(term)
|
||||
msgid "Port density"
|
||||
msgstr ""
|
||||
|
||||
@ -2131,15 +2131,15 @@ msgstr ""
|
||||
msgid "The physical space required to provide the requisite port count affects the network design. A switch that provides 48 10GbE ports in 1U has a much higher port density than a switch that provides 24 10GbE ports in 2U. On a general scale, a higher port density leaves more rack space for compute or storage components which is preferred. It is also important to consider fault domains and power density. Finally, higher density switches are more expensive, therefore it is important not to over design the network."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/storage_focus/section_architecture_storage_focus.xml:306(term) ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:115(para) ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:468(term)
|
||||
#: ./doc/arch-design/storage_focus/section_architecture_storage_focus.xml:306(term) ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:115(para) ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:419(term)
|
||||
msgid "Port speed"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/storage_focus/section_architecture_storage_focus.xml:308(para) ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:470(para)
|
||||
#: ./doc/arch-design/storage_focus/section_architecture_storage_focus.xml:308(para) ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:421(para)
|
||||
msgid "The networking hardware must support the proposed network speed, for example: 1GbE, 10GbE, or 40GbE (or even 100GbE)."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/storage_focus/section_architecture_storage_focus.xml:314(term) ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:118(para) ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:477(term)
|
||||
#: ./doc/arch-design/storage_focus/section_architecture_storage_focus.xml:314(term) ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:118(para) ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:428(term)
|
||||
msgid "Redundancy"
|
||||
msgstr ""
|
||||
|
||||
@ -2151,7 +2151,7 @@ msgstr ""
|
||||
msgid "If this is a requirement, the hardware must support this configuration. User requirements determine if a completely redundant network infrastructure is required."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/storage_focus/section_architecture_storage_focus.xml:329(term) ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:121(para) ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:488(term)
|
||||
#: ./doc/arch-design/storage_focus/section_architecture_storage_focus.xml:329(term) ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:121(para) ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:439(term)
|
||||
msgid "Power requirements"
|
||||
msgstr ""
|
||||
|
||||
@ -2167,7 +2167,7 @@ msgstr ""
|
||||
msgid "It is possible to gain more performance out of a single storage system by using specialized network technologies such as RDMA, SRP, iSER and SCST. The specifics for using these technologies is beyond the scope of this book."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/storage_focus/section_architecture_storage_focus.xml:353(title) ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:552(title) ./doc/arch-design/generalpurpose/section_tech_considerations_general_purpose.xml:278(title)
|
||||
#: ./doc/arch-design/storage_focus/section_architecture_storage_focus.xml:353(title) ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:504(title) ./doc/arch-design/generalpurpose/section_tech_considerations_general_purpose.xml:278(title)
|
||||
msgid "Software selection"
|
||||
msgstr ""
|
||||
|
||||
@ -2175,11 +2175,11 @@ msgstr ""
|
||||
msgid "Factors that influence the software selection for a storage-focused OpenStack architecture design include:"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/storage_focus/section_architecture_storage_focus.xml:358(para) ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:557(para)
|
||||
#: ./doc/arch-design/storage_focus/section_architecture_storage_focus.xml:358(para) ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:509(para)
|
||||
msgid "Operating system (OS) and hypervisor"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/storage_focus/section_architecture_storage_focus.xml:364(para) ./doc/arch-design/storage_focus/section_architecture_storage_focus.xml:524(title) ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:563(para) ./doc/arch-design/generalpurpose/section_tech_considerations_general_purpose.xml:484(title)
|
||||
#: ./doc/arch-design/storage_focus/section_architecture_storage_focus.xml:364(para) ./doc/arch-design/storage_focus/section_architecture_storage_focus.xml:524(title) ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:515(para) ./doc/arch-design/generalpurpose/section_tech_considerations_general_purpose.xml:484(title)
|
||||
msgid "Supplemental software"
|
||||
msgstr ""
|
||||
|
||||
@ -2187,7 +2187,7 @@ msgstr ""
|
||||
msgid "Design decisions made in each of these areas impacts the rest of the OpenStack architecture design."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/storage_focus/section_architecture_storage_focus.xml:372(title) ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:136(title) ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:568(title)
|
||||
#: ./doc/arch-design/storage_focus/section_architecture_storage_focus.xml:372(title) ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:136(title) ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:521(title)
|
||||
msgid "Operating system and hypervisor"
|
||||
msgstr ""
|
||||
|
||||
@ -2203,7 +2203,7 @@ msgstr ""
|
||||
msgid "Selecting a commercially supported hypervisor, such as Microsoft Hyper-V, results in a different cost model than a community-supported open source hypervisor like Kinstance or Xen. Similarly, choosing Ubuntu over Red Hat (or vice versa) impacts cost due to support contracts. However, business or application requirements might dictate a specific or commercially supported hypervisor."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/storage_focus/section_architecture_storage_focus.xml:398(term) ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:145(para) ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:597(term)
|
||||
#: ./doc/arch-design/storage_focus/section_architecture_storage_focus.xml:398(term) ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:145(para) ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:548(term)
|
||||
msgid "Supportability"
|
||||
msgstr ""
|
||||
|
||||
@ -2211,7 +2211,7 @@ msgstr ""
|
||||
msgid "Staff must have training with the chosen hypervisor. Consider the cost of training when choosing a solution. The support of a commercial product such as Red Hat, SUSE, or Windows, is the responsibility of the OS vendor. If an open source platform is chosen, the support comes from in-house resources."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/storage_focus/section_architecture_storage_focus.xml:410(term) ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:148(para) ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:608(term)
|
||||
#: ./doc/arch-design/storage_focus/section_architecture_storage_focus.xml:410(term) ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:148(para) ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:559(term)
|
||||
msgid "Management tools"
|
||||
msgstr ""
|
||||
|
||||
@ -2219,7 +2219,7 @@ msgstr ""
|
||||
msgid "Ubuntu and Kinstance use different management tools than VMware vSphere. Although both OS and hypervisor combinations are supported by OpenStack, there are varying impacts to the rest of the design as a result of the selection of one combination versus the other."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/storage_focus/section_architecture_storage_focus.xml:421(term) ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:151(para) ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:620(term)
|
||||
#: ./doc/arch-design/storage_focus/section_architecture_storage_focus.xml:421(term) ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:151(para) ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:571(term)
|
||||
msgid "Scale and performance"
|
||||
msgstr ""
|
||||
|
||||
@ -2231,7 +2231,7 @@ msgstr ""
|
||||
msgid "Ensure the design can accommodate the regular periodic installation of application security patches while maintaining the required workloads. The frequency of security patches for the proposed OS-hypervisor combination impacts performance and the patch installation process could affect maintenance windows."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/storage_focus/section_architecture_storage_focus.xml:444(term) ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:157(para) ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:642(term)
|
||||
#: ./doc/arch-design/storage_focus/section_architecture_storage_focus.xml:444(term) ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:157(para) ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:593(term)
|
||||
msgid "Supported features"
|
||||
msgstr ""
|
||||
|
||||
@ -2239,7 +2239,7 @@ msgstr ""
|
||||
msgid "Selecting the OS-hypervisor combination often determines the required features of OpenStack. Certain features are only available with specific OSes or hypervisors. For example, if certain features are not available, you might need to modify the design to meet user requirements."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/storage_focus/section_architecture_storage_focus.xml:454(term) ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:160(para) ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:653(term) ./doc/arch-design/generalpurpose/section_tech_considerations_general_purpose.xml:366(term)
|
||||
#: ./doc/arch-design/storage_focus/section_architecture_storage_focus.xml:454(term) ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:160(para) ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:602(term) ./doc/arch-design/generalpurpose/section_tech_considerations_general_purpose.xml:366(term)
|
||||
msgid "Interoperability"
|
||||
msgstr ""
|
||||
|
||||
@ -2295,7 +2295,7 @@ msgstr ""
|
||||
msgid "While OpenStack is a fairly complete collection of software projects for building a platform for cloud services, you may need to add other pieces of software."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/storage_focus/section_architecture_storage_focus.xml:531(title) ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:209(title) ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:688(title)
|
||||
#: ./doc/arch-design/storage_focus/section_architecture_storage_focus.xml:531(title) ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:209(title) ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:631(title)
|
||||
msgid "Networking software"
|
||||
msgstr ""
|
||||
|
||||
@ -2303,7 +2303,7 @@ msgstr ""
|
||||
msgid "OpenStack Networking (neutron) provides a wide variety of networking services for instances. There are many additional networking software packages that may be useful to manage the OpenStack components themselves. Some examples include HAProxy, Keepalived, and various routing daemons (like Quagga). The <citetitle>OpenStack High Availability Guide</citetitle> describes some of these software packages, HAProxy in particular. See the <link xlink: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/storage_focus/section_architecture_storage_focus.xml:545(title) ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:224(title) ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:723(title)
|
||||
#: ./doc/arch-design/storage_focus/section_architecture_storage_focus.xml:545(title) ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:224(title) ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:667(title)
|
||||
msgid "Management software"
|
||||
msgstr ""
|
||||
|
||||
@ -2347,11 +2347,11 @@ msgstr ""
|
||||
msgid "OS-Hypervisor combination: Ensure that the selected logging, monitoring, or alerting tools support the proposed OS-hypervisor combination."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/storage_focus/section_architecture_storage_focus.xml:605(para) ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:760(para)
|
||||
#: ./doc/arch-design/storage_focus/section_architecture_storage_focus.xml:605(para) ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:697(para)
|
||||
msgid "Network hardware: The network hardware selection needs to be supported by the logging, monitoring, and alerting software."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/storage_focus/section_architecture_storage_focus.xml:613(title) ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:254(title) ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:767(title)
|
||||
#: ./doc/arch-design/storage_focus/section_architecture_storage_focus.xml:613(title) ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:254(title) ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:705(title)
|
||||
msgid "Database software"
|
||||
msgstr ""
|
||||
|
||||
@ -2659,7 +2659,7 @@ msgstr ""
|
||||
msgid "Consider these when choosing server hardware for a compute- focused OpenStack design architecture:"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:104(title) ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:424(title)
|
||||
#: ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:104(title) ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:382(title)
|
||||
msgid "Selecting networking hardware"
|
||||
msgstr ""
|
||||
|
||||
@ -4888,7 +4888,7 @@ msgid "Hardware selection involves three key areas:"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:25(para)
|
||||
msgid "Selecting hardware for a general purpose OpenStack cloud should reflect a cloud with no pre-defined usage model. General purpose clouds are designed to run a wide variety of applications with varying resource usage requirements. These applications include any of the following:"
|
||||
msgid "Hardware for a general purpose OpenStack cloud should reflect a cloud with no pre-defined usage model, designed to run a wide variety of applications with varying resource usage requirements. These applications include any of the following:"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:32(para)
|
||||
@ -4904,373 +4904,317 @@ msgid "Storage-intensive"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:47(para)
|
||||
msgid "Choosing hardware for a general purpose OpenStack cloud must provide balanced access to all major resources."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:49(para)
|
||||
msgid "Certain hardware form factors may better suit a general purpose OpenStack cloud due to the requirement for equal (or nearly equal) balance of resources. Server hardware must provide the following:"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:55(para)
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:53(para)
|
||||
msgid "Equal (or nearly equal) balance of compute capacity (RAM and CPU)"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:60(para)
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:58(para)
|
||||
msgid "Network capacity (number and speed of links)"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:65(para)
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:63(para)
|
||||
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:71(para)
|
||||
msgid "Server hardware is evaluated around four conflicting dimensions."
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:69(para)
|
||||
msgid "Evaluate server hardware around four conflicting dimensions:"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:85(para)
|
||||
msgid "The number of CPU cores, how much RAM, or how much storage a given server will deliver."
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:83(para)
|
||||
msgid "The number of CPU cores, amount of RAM, or amount of deliverable storage."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:93(para)
|
||||
msgid "The number of additional resources that can be added to a server before it has reached its limit."
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:90(para)
|
||||
msgid "Limit of additional resources you can add to a server."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:101(para)
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:97(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:107(para)
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:103(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: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."
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:113(para)
|
||||
msgid "Blade servers typically support dual-socket multi-core CPUs. Blades also offer outstanding density."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:129(para)
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:118(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:137(para)
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:126(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:144(para)
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:133(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: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."
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:142(para)
|
||||
msgid "<emphasis>Sled servers</emphasis> 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: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:"
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:151(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 applies 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:174(para)
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:163(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 meter 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:186(para)
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:175(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:199(term)
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:188(term)
|
||||
msgid "Power density"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:201(para)
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:190(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:211(term)
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:200(term)
|
||||
msgid "Network connectivity"
|
||||
msgstr ""
|
||||
|
||||
#: ./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."
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:202(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."
|
||||
msgstr ""
|
||||
|
||||
#: ./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."
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:212(para)
|
||||
msgid "The selection of form factors or architectures affects the selection of server hardware. 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. Similarly, the network architecture impacts the server hardware selection and vice versa."
|
||||
msgstr ""
|
||||
|
||||
#: ./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: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:249(title)
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:220(title)
|
||||
msgid "Selecting storage hardware"
|
||||
msgstr ""
|
||||
|
||||
#: ./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:"
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:221(para)
|
||||
msgid "Determine storage hardware architecture by selecting specific storage architecture. Determine the selection of storage architecture by evaluating possible solutions against the critical factors, the user requirements, technical considerations, and operational considerations. Incorporate the following facts into your storage architecture:"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:261(para)
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:231(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:275(para)
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:245(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: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 meter 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."
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:257(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 meter is related to scalability, which is the measure of a solution's performance as it expands."
|
||||
msgstr ""
|
||||
|
||||
#: ./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."
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:267(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. Cloud services requirements determine your choice of scale-out solution. You need to determine if a single, highly expandable and highly vertical, scalable, centralized storage array is suitable for your design. After determining an approach, select the storage hardware based on this criteria."
|
||||
msgstr ""
|
||||
|
||||
#: ./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:315(para)
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:275(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:323(para)
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:283(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:332(term)
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:292(term)
|
||||
msgid "Usage"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:334(para)
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:294(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:343(term)
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:303(term)
|
||||
msgid "Instance and image locations"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:345(para)
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:305(para)
|
||||
msgid "Where instances and images will be stored will influence the architecture."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:353(para)
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:313(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:362(para)
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:322(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:368(term)
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:328(term)
|
||||
msgid "Capacity"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:370(para)
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:330(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: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."
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:349(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."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:404(term)
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:361(term)
|
||||
msgid "Fault tolerance"
|
||||
msgstr ""
|
||||
|
||||
#: ./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."
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:363(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: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."
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:383(para)
|
||||
msgid "Selecting network architecture determines which network hardware will be used. Networking software is determined by the selected networking hardware."
|
||||
msgstr ""
|
||||
|
||||
#: ./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."
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:386(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 <emphasis>open</emphasis> 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."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:442(para)
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:393(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:448(para)
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:399(para)
|
||||
msgid "The design will require networking hardware that has the requisite port count."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:455(para)
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:406(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:479(para)
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:430(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:490(para)
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:441(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:494(para)
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:445(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:501(para)
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:452(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:510(para)
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:461(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:523(para)
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:474(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:531(term) ./doc/arch-design/generalpurpose/section_tech_considerations_general_purpose.xml:631(title)
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:482(term) ./doc/arch-design/generalpurpose/section_tech_considerations_general_purpose.xml:631(title)
|
||||
msgid "Availability"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:533(para)
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:484(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:553(para)
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:505(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: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."
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:522(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."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:579(para)
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:530(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:585(para)
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:536(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:599(para)
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:550(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:610(para)
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:561(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:622(para)
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:573(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:632(para)
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:583(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: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."
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:595(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 operating systems or hypervisors."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:655(para)
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:604(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: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."
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:618(para)
|
||||
msgid "Selecting which OpenStack components are included in the overall design is important. 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:672(para)
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:622(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:680(title)
|
||||
msgid "Supplemental components"
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:632(para)
|
||||
msgid "OpenStack Networking (neutron) 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: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: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:695(para)
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:638(para)
|
||||
msgid "Software to provide load balancing"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:700(para)
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:643(para)
|
||||
msgid "Network redundancy protocols"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:705(para)
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:648(para)
|
||||
msgid "Routing daemons"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:710(para)
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:653(para)
|
||||
msgid "Some of these software packages are described in more detail in the <citetitle>OpenStack High Availability Guide</citetitle> (refer to the <link xlink: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:716(para)
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:659(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:724(para)
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:668(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:728(para)
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:672(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 xlink: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: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."
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:683(para)
|
||||
msgid "Requirements for logging, monitoring, and alerting are determined by operational considerations. Each of these sub-categories includes a number of various options."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:749(para)
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:686(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:755(para)
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:692(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:768(para)
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:706(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:782(title)
|
||||
msgid "Addressing performance-sensitive workloads"
|
||||
msgstr ""
|
||||
|
||||
#: ./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:795(title)
|
||||
msgid "Compute-focused workloads"
|
||||
msgstr ""
|
||||
|
||||
#: ./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:804(title)
|
||||
msgid "Network-focused workloads"
|
||||
msgstr ""
|
||||
|
||||
#: ./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:813(title)
|
||||
msgid "Storage-focused workloads"
|
||||
msgstr ""
|
||||
|
||||
#: ./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 ""
|
||||
|
||||
#: ./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 a general purpose cloud, and operations staff are often tasked with the maintenance of cloud environments for larger installations."
|
||||
msgstr ""
|
||||
|
||||
@ -9,8 +9,8 @@
|
||||
msgid ""
|
||||
msgstr ""
|
||||
"Project-Id-Version: OpenStack Manuals\n"
|
||||
"POT-Creation-Date: 2015-08-28 10:14+0000\n"
|
||||
"PO-Revision-Date: 2015-08-28 07:15+0000\n"
|
||||
"POT-Creation-Date: 2015-09-03 05:54+0000\n"
|
||||
"PO-Revision-Date: 2015-09-02 14:18+0000\n"
|
||||
"Last-Translator: openstackjenkins <jenkins@openstack.org>\n"
|
||||
"Language-Team: Chinese (China) (http://www.transifex.com/openstack/openstack-"
|
||||
"manuals-i18n/language/zh_CN/)\n"
|
||||
@ -20,17 +20,6 @@ msgstr ""
|
||||
"Language: zh_CN\n"
|
||||
"Plural-Forms: nplurals=1; plural=0;\n"
|
||||
|
||||
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 ""
|
||||
"“雪撬服务器”亦是机架式服务器的一种，支持在单个2U或3U的空间放置多个独立的服务"
|
||||
"器。此种类型增加的密度超过典型的1U-2U机架服务器，但是单个服务器支持的存储和网"
|
||||
"络容量往往受到限制。"
|
||||
|
||||
msgid ""
|
||||
"10 GbE horizontally scalable spine leaf back-end storage and front end "
|
||||
"network."
|
||||
@ -691,9 +680,6 @@ msgstr ""
|
||||
"\">Kibana</link>, 以及CERN开发的项目<link xlink:href=\"http://lemon.web.cern."
|
||||
"ch/lemon/index.shtml\">Lemon</link>。"
|
||||
|
||||
msgid "Addressing performance-sensitive workloads"
|
||||
msgstr "针对性能敏感的负载"
|
||||
|
||||
msgid "Agility"
|
||||
msgstr "敏捷性"
|
||||
|
||||
@ -740,20 +726,6 @@ msgstr ""
|
||||
"存在其他一些场景独特到无法归类入主要场景中的任何一个之中。本章将讨论一些这种"
|
||||
"特殊的应用场景，以及每种场景的细节和设计的考虑因素。"
|
||||
|
||||
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 ""
|
||||
"虽然性能对于通用型OpenStack云是一个至为关键的因素，但不是决定性的因素，但是仍"
|
||||
"然有一些性能敏感的负载部署。关于设计性能敏感负载的想到，我们建议用户参考本书"
|
||||
"后面针对专用场景的描述。某些针对不同资源的向导可以帮助解决性能敏感负载的问"
|
||||
"题。"
|
||||
|
||||
msgid ""
|
||||
"An OpenStack general purpose cloud is often considered a starting point for "
|
||||
"building a cloud deployment. They are designed to balance the components and "
|
||||
@ -999,20 +971,6 @@ msgstr "大数据"
|
||||
msgid "Big data analytics using Hadoop or other distributed data stores"
|
||||
msgstr "使用Hadoop或其他分布式数据处理程序来分析大数据"
|
||||
|
||||
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 ""
|
||||
"刀片服务通常都支持双插槽多核的CPU，对于通用型云部署此配置通常被考虑为“甜点“。"
|
||||
"刀片拥有卓越的密度。举例，无论是 HP BladeSystem 还是 Dell PowerEdge M1000e，"
|
||||
"均支持在占用10U的机柜空间下达到16台服务器的密度。尽管如此，刀片服务器本身具有"
|
||||
"有限的存储和网络容量，另外扩展到多台刀片服务器也是有局限的。"
|
||||
|
||||
msgid "Block Storage fault tolerance and availability"
|
||||
msgstr "块存储的容错和可用性"
|
||||
|
||||
@ -1141,11 +1099,6 @@ msgstr "选择Hypervisor"
|
||||
msgid "Choice of operating system"
|
||||
msgstr "选择操作系统"
|
||||
|
||||
msgid ""
|
||||
"Choosing hardware for a general purpose OpenStack cloud must provide "
|
||||
"balanced access to all major resources."
|
||||
msgstr "为通用型OpenStack云选择硬件必须提供所有主要资源的平衡性。"
|
||||
|
||||
msgid "Cloud storage"
|
||||
msgstr "云存储"
|
||||
|
||||
@ -1300,9 +1253,6 @@ msgstr ""
|
||||
msgid "Compute resources"
|
||||
msgstr "计算资源"
|
||||
|
||||
msgid "Compute-focused workloads"
|
||||
msgstr "计算型的负载"
|
||||
|
||||
msgid ""
|
||||
"Configuration management tools such as Puppet and Chef enable operations "
|
||||
"staff to categorize systems into groups based on their roles and thus create "
|
||||
@ -1564,17 +1514,6 @@ msgstr "决定的是如果用例中拥有并行或高度变化的延迟。"
|
||||
msgid "Determine the most effective configuration for block storage network."
|
||||
msgstr "确定块存储网络的最高效配置。"
|
||||
|
||||
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 ""
|
||||
"决定那些特性是需要OpenStack提供的。这通常也决定了操作系统-hypervisor组合的选"
|
||||
"择。一些特性仅在特定的操作系统和hypervisor中是可用的。举例，如果确认某些特性"
|
||||
"无法实现，设计也许需要修改代码去满足用户的需求。"
|
||||
|
||||
msgid "Determining whether an application is cloud-ready"
|
||||
msgstr "决定那些应用程序是可在云中运行"
|
||||
|
||||
@ -1590,24 +1529,6 @@ msgstr "服务水平协议比较"
|
||||
msgid "Disaster recovery"
|
||||
msgstr "灾难恢复"
|
||||
|
||||
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 ""
|
||||
"对于对象存储的磁盘选择来说，不需要速度太快的磁盘。我们建议对象存储节点利用最"
|
||||
"佳的每TB开销比即可。与此相反，为块存储服务选择磁盘，则须利用提高性能的特性来"
|
||||
"选择，比如使用SSD或flash磁盘来提供高性能的块存储池。即使是为实例运行的临时的"
|
||||
"磁盘也得考虑性能。如果计算池希望大量采用临时存储，或者是要求非常高的性能，就"
|
||||
"需要部署上述块存储硬件的解决方案。"
|
||||
|
||||
msgid ""
|
||||
"Divide and conquer: Pursue partitioning and parallel layering wherever "
|
||||
"possible. Make components as small and portable as possible. Use load "
|
||||
@ -1675,20 +1596,6 @@ msgstr ""
|
||||
"没有什么影响，但是spine交换机的叶和fabric以及排尾交换机(EoR)就可能发生问题，"
|
||||
"假如电力不足的话。"
|
||||
|
||||
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 ""
|
||||
"确保选择的服务器硬件的配置支持足够的存储容量(或存储扩展性)，以满足所选择的横"
|
||||
"向扩展存储解决方案的需求。举例，如果需求是基于集中存储解决方案，比如存储厂商"
|
||||
"的集中存储阵列需要InfiniBand或FDDI连接，那么服务器硬件就需要安装对应的网卡来"
|
||||
"兼容此特定厂商的存储阵列。"
|
||||
|
||||
msgid ""
|
||||
"Ensure that, if storage protocols other than Ethernet are part of the "
|
||||
"storage solution, the appropriate hardware has been selected. If a "
|
||||
@ -1779,22 +1686,6 @@ msgstr ""
|
||||
msgid "Expandability"
|
||||
msgstr "延伸性"
|
||||
|
||||
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 "
|
||||
"meter 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 ""
|
||||
"对于通用型OpenStack云存储解决方案来说，可扩展性也是主要的架构因素。一个存储解"
|
||||
"决方案能够扩展到50PB,而另外一个只能扩到10PB,前者明显比后者的扩展性强好多倍。"
|
||||
"此扩展与scalability有关，但是不一样，scalability更加倾向于解决方案的性能衡"
|
||||
"量。举例，一个存储架构为专注于开发者平台的云和商业产品云在expandability和"
|
||||
"scalability上就不可能一样。"
|
||||
|
||||
msgid "Expansion planning"
|
||||
msgstr "扩展计划"
|
||||
|
||||
@ -2299,28 +2190,6 @@ msgstr ""
|
||||
"能力，以及它们分别对软、硬件特殊的需求等。这些功能需要明确暴露给最终用户，或"
|
||||
"者通过为实例类型定义的元数据来访问。"
|
||||
|
||||
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 ""
|
||||
"在网络型OpenStack云中，一些设计选择能够改进这些类型负载的性能。网络型"
|
||||
"OpenStack的负载对于网络带宽和服务有着苛刻的需求，所以需要特别的考量和规划。关"
|
||||
"于此类型云的设计指南，请参考 <xref linkend=\"network_focus\"/>。"
|
||||
|
||||
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 ""
|
||||
"在计算型OpenStack云中的一些设计选择是可以帮助满足他们的负载的。计算型云的负载"
|
||||
"要求有更多的CPU和内存资源，相对存储和网络的性能优先级要低的多。关于设计此类型"
|
||||
"云的指南，请参考 <xref linkend=\"compute_focus\"/>。"
|
||||
|
||||
msgid ""
|
||||
"In environments that place extreme demands on Block Storage, we recommend "
|
||||
"using multiple storage pools. In this case, each pool of devices should have "
|
||||
@ -3104,9 +2973,6 @@ msgid ""
|
||||
msgstr ""
|
||||
"网络运行时间保证影响这交换机的设计，需要交换机的冗余，以及其电源的冗余。"
|
||||
|
||||
msgid "Network-focused workloads"
|
||||
msgstr "网络型负载"
|
||||
|
||||
msgid "Network:"
|
||||
msgstr "网络："
|
||||
|
||||
@ -3212,22 +3078,6 @@ msgstr ""
|
||||
"储服务是一种频繁交互的协议，因此确定使用多个处理器，而且要多核的，这样才可确"
|
||||
"保不至于因为IO请求将服务器搞垮。"
|
||||
|
||||
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 ""
|
||||
"对象存储资源节点对于硬件容错或RAID控制器没有任何的要求。没必要为对象存储硬件"
|
||||
"规划容错是因为对象存储服务本身就提供了在zone之间的复制。块存储节点、计算节点"
|
||||
"以及云控制器节点都须在硬件层有容错机制，使用硬件RAID控制器的话请确认RAID配置"
|
||||
"的级别。RAID级别的选择对于云的需求来说须性能和可用性兼顾。"
|
||||
|
||||
msgid ""
|
||||
"On large layer-2 networks, configuring ARP learning can also be complicated. "
|
||||
"The setting for the MAC address timer on switches is critical and, if set "
|
||||
@ -3413,14 +3263,6 @@ msgstr ""
|
||||
"控制硬件负载均衡池以及作为池的成员的实例，但是使用它们在生产环境的话要小心权"
|
||||
"衡它的稳定程度。"
|
||||
|
||||
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 ""
|
||||
"OpenStack联网为实例提供各种各样的联网服务。有许多联网软件包可用于管理"
|
||||
"OpenStack组件，举几个例子："
|
||||
|
||||
msgid ""
|
||||
"OpenStack Networking versus legacy networking (nova-network) considerations"
|
||||
msgstr "OpenStack 联网方式对传统联网(nova-network) 的考虑"
|
||||
@ -3870,23 +3712,6 @@ msgstr ""
|
||||
"胜过冗余。这种场景下的应用必须依据这个原则进行修改，依赖于整个环境的规模和扩"
|
||||
"展性和同质性以提供可靠性，而不是使用非商品的硬件解决方案提供的冗余基础设施。"
|
||||
|
||||
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 ""
|
||||
"对日志、监测以及报警的需求是由运维考虑决定的。它们的每个子类别都包含了大量的"
|
||||
"属性。举例，在日志子类别中，某些情况考虑使用Logstash,Splunk，instanceware "
|
||||
"Log Insight等，或者其他的日志聚合-合并工具。日志需要存放在中心地带，使分析数"
|
||||
"据变得更为简单。日志数据分析引擎亦得提供自动化和问题通知，通过提供一致的预警"
|
||||
"和自动修复某些常见的已知问题。"
|
||||
|
||||
msgid ""
|
||||
"Resiliency of overall system and individual components are going to be "
|
||||
"dictated by the requirements of the SLA, meaning designing for high "
|
||||
@ -4111,28 +3936,6 @@ msgstr ""
|
||||
"比较开源操作系统解决方案时，选择了Ubuntu而不是红帽(反之亦然)，由于支持的合同"
|
||||
"不同，开销也会不一样。"
|
||||
|
||||
msgid ""
|
||||
"Selecting hardware for a general purpose OpenStack cloud should reflect a "
|
||||
"cloud with no pre-defined usage model. General purpose clouds are designed "
|
||||
"to run a wide variety of applications with varying resource usage "
|
||||
"requirements. These applications include any of the following:"
|
||||
msgstr ""
|
||||
"为通用型OpenStack云选择硬件，印证了云是没有预先定义的使用模型的。通用型云为运"
|
||||
"行广泛的应用而设计，而每种应用对资源利用有着各自不同的需求。这些应用不会是下"
|
||||
"面分类以外的类型："
|
||||
|
||||
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 ""
|
||||
"选择网络架构决定了那些网络硬件将会被使用。而网络的软件是由选择好的网络硬件所"
|
||||
"决定的。举例，选择了网络硬件仅支持千兆以太网 (GbE)会影响到整个设计。同样地，"
|
||||
"决定使用 万兆以太网(10GbE)仅会影响到整个设计的局部一些区域。 "
|
||||
|
||||
msgid "Selecting networking hardware"
|
||||
msgstr "选择网络硬件"
|
||||
|
||||
@ -4150,16 +3953,6 @@ msgstr ""
|
||||
"统。进一步讲，也许还需要根据不同的需求配置存储的策略，这些策略包括副本，保留"
|
||||
"以及其它在特定区域会严重影响到存储设计的因素。"
|
||||
|
||||
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 ""
|
||||
"选择包含那些OpenStack组件对整个设计有着显著的影响。一些OpenStack组件，如计算"
|
||||
"和镜像服务，在每个架构中都是硬性需求，但另外一些组件，如编排，就不经常被用户"
|
||||
"所需要。"
|
||||
|
||||
msgid "Selection of OpenStack software components"
|
||||
msgstr "选择OpenStack软件组件"
|
||||
|
||||
@ -4175,9 +3968,6 @@ msgstr "服务器密度"
|
||||
msgid "Server hardware"
|
||||
msgstr "服务器硬件"
|
||||
|
||||
msgid "Server hardware is evaluated around four conflicting dimensions."
|
||||
msgstr "服务器硬件是围绕4个冲突的维度来进行评估的。"
|
||||
|
||||
msgid "Signal processing for network function virtualization (NFV)"
|
||||
msgstr "专门处理网络功能虚拟化(NFV)"
|
||||
|
||||
@ -4190,18 +3980,6 @@ msgstr ""
|
||||
"同样的，默认的内存超分配比例是1.5:1，这意味着调度器为实例分配的内存总量要少于"
|
||||
"物理节点内存的1.5倍。"
|
||||
|
||||
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 ""
|
||||
"同样的，网络架构会影响到服务器硬件的选择，反之亦然。举例，确保服务器配置了足"
|
||||
"够的网络端口和扩展卡，以支持所有的网络需求。因为有网络扩展卡的兼容性问题，所"
|
||||
"以要意识到潜在影响和兼容性问题，以及架构中的其他组件。"
|
||||
|
||||
msgid "Simple, single agent"
|
||||
msgstr "简单，单独一个代理程序"
|
||||
|
||||
@ -4379,27 +4157,6 @@ msgstr "存储能力(每秒输入/输入操作(<glossterm>IOPS</glossterm>)，GB
|
||||
msgid "Storage focused"
|
||||
msgstr "存储型"
|
||||
|
||||
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 ""
|
||||
"存储型OpenStack云需要被设计成可容纳对对象存储和块存储服务有着苛刻需求的负载。"
|
||||
"关于设计此类型云的指南，请参考<xref linkend=\"storage_focus\"/>。"
|
||||
|
||||
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 ""
|
||||
"存储硬件结构主要是由所选择的存储体系结构来确定。存储架构的选择，以及相应的存"
|
||||
"储硬件， 通过评估可能的解决方案，即针对关键的因素，用户需求，技术因素和运维因"
|
||||
"素来做决定。需要被并入存储体系架构的因素包括："
|
||||
|
||||
msgid "Storage hardware:"
|
||||
msgstr "存储硬件："
|
||||
|
||||
@ -4412,18 +4169,12 @@ msgstr "存储管理"
|
||||
msgid "Storage performance"
|
||||
msgstr "存储性能"
|
||||
|
||||
msgid "Storage-focused workloads"
|
||||
msgstr "存储型负载"
|
||||
|
||||
msgid "Storage-intensive"
|
||||
msgstr "存储密集型"
|
||||
|
||||
msgid "Structure"
|
||||
msgstr "结构"
|
||||
|
||||
msgid "Supplemental components"
|
||||
msgstr "支撑组件"
|
||||
|
||||
msgid "Supplemental software"
|
||||
msgstr "增强软件"
|
||||
|
||||
@ -4553,18 +4304,6 @@ msgstr ""
|
||||
"<citetitle>OpenStack 高可用指南</citetitle></link> 提供了更加详细的安装和配置"
|
||||
"Corosync和Pacemaker，所以在设计中这些软件包需要被包含。 "
|
||||
|
||||
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 ""
|
||||
"支持通用型OpenStack云的服务器硬件最佳类型，是由外部的业务和成本因素所驱动的。"
|
||||
"没有那个单一的参考架构可以满足所有的实现，决定一定要依据用户需求，技术因素，"
|
||||
"以及运维因素。这里有一些能够影响到服务器硬件的选择的关键的因素："
|
||||
|
||||
msgid "The bleeding edge"
|
||||
msgstr "最前沿"
|
||||
|
||||
@ -4830,19 +4569,9 @@ msgid ""
|
||||
"delivers."
|
||||
msgstr "CPU核数，多少内存，或者多少存储可以交付。"
|
||||
|
||||
msgid ""
|
||||
"The number of CPU cores, how much RAM, or how much storage a given server "
|
||||
"will deliver."
|
||||
msgstr "一个给定的服务器能够提供的 CPU 数目、内存大小以及存储大小。"
|
||||
|
||||
msgid "The number of MACs stored in switch tables is limited."
|
||||
msgstr "存储在交换表中的 MAC 地址数目是有限的。"
|
||||
|
||||
msgid ""
|
||||
"The number of additional resources that can be added to a server before it "
|
||||
"has reached its limit."
|
||||
msgstr "服务器上还能够继续添加直到到达其限制的资源数目。"
|
||||
|
||||
msgid ""
|
||||
"The number of additional resources you can add to a server before it reaches "
|
||||
"capacity."
|
||||
@ -4862,22 +4591,6 @@ msgstr ""
|
||||
"景下才会出现，所以能够重现和验证该问题的组织是为数不多的，因此将问题良好地文"
|
||||
"档化并且为问题的解决贡献一些必要的资源，是尤为重要的。"
|
||||
|
||||
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 ""
|
||||
"操作系统(OS)和hypervisor对于整个设计有着深刻的影响。选择一个特定的操作系统和"
|
||||
"hypervisor能够直接影响到服务器硬件的选择。确保存储硬件和拓扑支持选择好的操作"
|
||||
"系统和Hypervisor组合。也得确保网络硬件的选择和拓扑可在选定的操作系统和"
|
||||
"Hypervisor组合下正常工作。例如，如果设计中使用了链路聚合控制协议(LACP)的话，"
|
||||
"操作系统和hypervisor都需要支持它才可正常工作。"
|
||||
|
||||
msgid "The performance of the applications running on virtual desktops"
|
||||
msgstr "在提供的虚拟桌面中运行的应用的性能"
|
||||
|
||||
@ -4932,20 +4645,6 @@ msgid ""
|
||||
"The selected OS-hypervisor combination needs to be supported by OpenStack."
|
||||
msgstr "选择操作系统-虚拟机管理程序组合需要OpenStack支持。"
|
||||
|
||||
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 ""
|
||||
"已选择的服务器硬件必须有合适数量的网络连接，以及恰当的类型，目的是支持建议的"
|
||||
"架构。为了确保这点，最小的情况也需要至少为每个机架连接两条网络。如果架构要求"
|
||||
"更多的冗余，也许就需要和电信供应商确认有多少线路可以连接。大多数的数据中心具"
|
||||
"备这个能力。"
|
||||
|
||||
msgid ""
|
||||
"The selected supplemental software solution impacts and affects the overall "
|
||||
"OpenStack cloud design. This includes software for providing clustering, "
|
||||
@ -4959,16 +4658,6 @@ msgid ""
|
||||
"support the user requirements."
|
||||
msgstr "选择操作系统-虚拟机管理程序组合，首先且最重要的是支持用户的需求。"
|
||||
|
||||
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 ""
|
||||
"形式因素或体系结构的选择会影响服务器硬件的选择，例如，假如设计一个横向扩展的"
|
||||
"存储架构，那么服务器硬件的选择就得小心谨慎的考虑需求，以匹配商业解决方案的需"
|
||||
"求。"
|
||||
|
||||
msgid ""
|
||||
"The software selection process plays a large role in the architecture of a "
|
||||
"general purpose cloud. The following have a large impact on the design of "
|
||||
@ -5008,22 +4697,6 @@ msgid ""
|
||||
"manage traffic."
|
||||
msgstr "有很多经过完善测试的工具，例如 ICMP，来监控和管理流量。"
|
||||
|
||||
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 ""
|
||||
"有许多设计上的细节需要被考虑。选择好了网络硬件(或网络软件)会影响到管理工具的"
|
||||
"使用。除非出现下面情况：越来越多的用户倾向于使用\"开放“的网络软件来支持广泛的"
|
||||
"网络硬件，意味着某些情况下网络硬件和软件之间的关系是不是被严格定义。关于此类"
|
||||
"型的软件Cumulus Linux即是个例子，Cumulus Linux具有运行多数交换机供应商的硬件"
|
||||
"的能力。"
|
||||
|
||||
msgid ""
|
||||
"There are several factors to take into consideration when looking at whether "
|
||||
"an application is a good fit for the cloud."
|
||||
@ -5260,18 +4933,6 @@ msgstr ""
|
||||
"OpenStack对它们都支持。这也会对其他的设计有着非常不同的影响，结果就是选择了一"
|
||||
"种组合，然后再据此做出后面的选择。"
|
||||
|
||||
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 ""
|
||||
"正确理解云服务的需求对于决定该使用什么横向扩展解决方案有非常大的帮助。假如现"
|
||||
"在需要一个单一的，高度可扩展，高度垂直化，可扩展的性能等需求，那么在设计中采"
|
||||
"用中心化的存储阵列就应该被考虑。一旦一种方法已经被确定，存储硬件需要在此基础"
|
||||
"上的标准来进行选择。"
|
||||
|
||||
msgid ""
|
||||
"Unfortunately, Compute is the only OpenStack service that provides good "
|
||||
"support for cells. In addition, cells do not adequately support some "
|
||||
@ -5391,20 +5052,6 @@ msgid ""
|
||||
"following requirements:"
|
||||
msgstr "跟上面的例子相关的 Ceph 的一个可能架构需要如下组件："
|
||||
|
||||
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 ""
|
||||
"使用在服务器直接挂接存储(DAS)来作为横向扩展存储解决方案，是比较适合通用型"
|
||||
"OpenStack云的。举例，无论是采用计算主机类似的网格计算解决方案，还是给主机提供"
|
||||
"专用的块存储，这样的存储方式是可能的。当在计算主机合适的硬件上部署存储时，需"
|
||||
"要支持存储和计算服务在同一台硬件。"
|
||||
|
||||
msgid "Utilization"
|
||||
msgstr "量力而行"
|
||||
|
||||
@ -5696,14 +5343,6 @@ msgstr ""
|
||||
"用Pacemaker会影响到设计，假定有至少2台控制器基础设施，其中一个节点可在待机模"
|
||||
"式下运行的某些服务。"
|
||||
|
||||
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 ""
|
||||
"OpenStack为了构建一个平台提供云服务，是完全公平的收集软件的项目。在任何给定的"
|
||||
"OpenStack设计中都需要考虑那些附加的软件。"
|
||||
|
||||
msgid ""
|
||||
"While OpenStack is a fairly complete collection of software projects for "
|
||||
"building a platform for cloud services, you may need to add other pieces of "
|
||||
|
||||
File diff suppressed because one or more lines are too long
@ -16,7 +16,7 @@ msgid "(RADOS)"
|
||||
msgstr ""
|
||||
|
||||
#: ../common/app_support.rst:233 ../common/app_support.rst:230
|
||||
#: ../common/app_support.rst:228
|
||||
#: ../common/app_support.rst:228 ../common/app_support.rst:234
|
||||
msgid ""
|
||||
"**CentOS, Fedora, and Red Hat Enterprise Linux:** https://www.rdoproject.org/"
|
||||
msgstr ""
|
||||
@ -30,7 +30,7 @@ msgid "**Debian:** http://wiki.debian.org/OpenStack"
|
||||
msgstr ""
|
||||
|
||||
#: ../common/app_support.rst:231 ../common/app_support.rst:228
|
||||
#: ../common/app_support.rst:226
|
||||
#: ../common/app_support.rst:226 ../common/app_support.rst:232
|
||||
msgid "**Debian:** https://wiki.debian.org/OpenStack"
|
||||
msgstr ""
|
||||
|
||||
@ -81,7 +81,7 @@ msgid "**Ubuntu and Debian**"
|
||||
msgstr ""
|
||||
|
||||
#: ../common/app_support.rst:239 ../common/app_support.rst:236
|
||||
#: ../common/app_support.rst:234
|
||||
#: ../common/app_support.rst:234 ../common/app_support.rst:240
|
||||
msgid "**Ubuntu:** https://wiki.ubuntu.com/ServerTeam/CloudArchive"
|
||||
msgstr ""
|
||||
|
||||
@ -96,7 +96,7 @@ msgid ""
|
||||
msgstr ""
|
||||
|
||||
#: ../common/app_support.rst:236 ../common/app_support.rst:233
|
||||
#: ../common/app_support.rst:231
|
||||
#: ../common/app_support.rst:231 ../common/app_support.rst:237
|
||||
msgid ""
|
||||
"**openSUSE and SUSE Linux Enterprise Server:** https://en.opensuse.org/"
|
||||
"Portal:OpenStack"
|
||||
@ -2633,7 +2633,7 @@ msgstr ""
|
||||
msgid "Application Service Provider (ASP)"
|
||||
msgstr ""
|
||||
|
||||
#: ../common/glossary.rst:227
|
||||
#: ../common/glossary.rst:227 ../common/cli_overview.rst:34
|
||||
msgid "Application catalog"
|
||||
msgstr ""
|
||||
|
||||
@ -2823,6 +2823,7 @@ msgid ""
|
||||
msgstr ""
|
||||
|
||||
#: ../common/cli_install_openstack_command_line_clients.rst:243
|
||||
#: ../common/cli_install_openstack_command_line_clients.rst:249
|
||||
msgid ""
|
||||
"Before you can run client commands, you must create and source the :file:"
|
||||
"`PROJECT-openrc.sh` file to set environment variables. See :doc:`../common/"
|
||||
@ -2852,6 +2853,7 @@ msgid "Bexar"
|
||||
msgstr ""
|
||||
|
||||
#: ../common/glossary.rst:463 ../common/cli_overview.rst:34
|
||||
#: ../common/cli_overview.rst:37
|
||||
msgid "Block Storage"
|
||||
msgstr ""
|
||||
|
||||
@ -3114,11 +3116,11 @@ msgstr ""
|
||||
msgid "Command prompts"
|
||||
msgstr ""
|
||||
|
||||
#: ../common/cli_overview.rst:80
|
||||
#: ../common/cli_overview.rst:80 ../common/cli_overview.rst:89
|
||||
msgid "Common client"
|
||||
msgstr ""
|
||||
|
||||
#: ../common/cli_overview.rst:80
|
||||
#: ../common/cli_overview.rst:80 ../common/cli_overview.rst:89
|
||||
msgid "Common client for the OpenStack project."
|
||||
msgstr ""
|
||||
|
||||
@ -3174,6 +3176,7 @@ msgid ""
|
||||
msgstr ""
|
||||
|
||||
#: ../common/glossary.rst:780 ../common/cli_overview.rst:37
|
||||
#: ../common/cli_overview.rst:40
|
||||
msgid "Compute"
|
||||
msgstr ""
|
||||
|
||||
@ -3232,7 +3235,7 @@ msgid ""
|
||||
"the CONF object for the current process."
|
||||
msgstr ""
|
||||
|
||||
#: ../common/cli_overview.rst:52
|
||||
#: ../common/cli_overview.rst:52 ../common/cli_overview.rst:58
|
||||
msgid "Configure networks for guest servers."
|
||||
msgstr ""
|
||||
|
||||
@ -3247,7 +3250,7 @@ msgstr ""
|
||||
msgid "Container servers (swift-container-server)"
|
||||
msgstr ""
|
||||
|
||||
#: ../common/glossary.rst:865
|
||||
#: ../common/glossary.rst:865 ../common/cli_overview.rst:44
|
||||
msgid "Containers service"
|
||||
msgstr ""
|
||||
|
||||
@ -3329,31 +3332,43 @@ msgid ""
|
||||
"one for MongoDB."
|
||||
msgstr ""
|
||||
|
||||
#: ../common/cli_overview.rst:72
|
||||
#: ../common/cli_overview.rst:72 ../common/cli_overview.rst:81
|
||||
msgid "Create and collect measurements across OpenStack."
|
||||
msgstr ""
|
||||
|
||||
#: ../common/cli_overview.rst:76
|
||||
#: ../common/cli_overview.rst:76 ../common/cli_overview.rst:85
|
||||
msgid "Create and manage Hadoop clusters on OpenStack."
|
||||
msgstr ""
|
||||
|
||||
#: ../common/cli_overview.rst:41
|
||||
msgid "Create and manage databases."
|
||||
msgstr ""
|
||||
|
||||
#: ../common/cli_overview.rst:37
|
||||
msgid "Create and manage images, instances, and flavors."
|
||||
msgstr ""
|
||||
|
||||
#: ../common/cli_overview.rst:49
|
||||
msgid "Create and manage images."
|
||||
#: ../common/cli_overview.rst:34
|
||||
msgid "Create and manage applications."
|
||||
msgstr ""
|
||||
|
||||
#: ../common/cli_overview.rst:44
|
||||
msgid "Create and manage containers."
|
||||
msgstr ""
|
||||
|
||||
#: ../common/cli_overview.rst:41 ../common/cli_overview.rst:47
|
||||
msgid "Create and manage databases."
|
||||
msgstr ""
|
||||
|
||||
#: ../common/cli_overview.rst:37 ../common/cli_overview.rst:40
|
||||
msgid "Create and manage images, instances, and flavors."
|
||||
msgstr ""
|
||||
|
||||
#: ../common/cli_overview.rst:49 ../common/cli_overview.rst:55
|
||||
msgid "Create and manage images."
|
||||
msgstr ""
|
||||
|
||||
#: ../common/cli_overview.rst:78
|
||||
msgid "Create and manage shared file systems"
|
||||
msgstr ""
|
||||
|
||||
#: ../common/cli_overview.rst:44 ../common/cli_overview.rst:50
|
||||
msgid "Create and manage users, tenants, roles, endpoints, and credentials."
|
||||
msgstr ""
|
||||
|
||||
#: ../common/cli_overview.rst:34
|
||||
#: ../common/cli_overview.rst:34 ../common/cli_overview.rst:37
|
||||
msgid "Create and manage volumes."
|
||||
msgstr ""
|
||||
|
||||
@ -3454,7 +3469,7 @@ msgid ""
|
||||
"networks."
|
||||
msgstr ""
|
||||
|
||||
#: ../common/cli_overview.rst:76
|
||||
#: ../common/cli_overview.rst:76 ../common/cli_overview.rst:85
|
||||
msgid "Data processing"
|
||||
msgstr ""
|
||||
|
||||
@ -3490,6 +3505,7 @@ msgid "Database"
|
||||
msgstr ""
|
||||
|
||||
#: ../common/glossary.rst:982 ../common/cli_overview.rst:41
|
||||
#: ../common/cli_overview.rst:47
|
||||
msgid "Database service"
|
||||
msgstr ""
|
||||
|
||||
@ -3658,7 +3674,7 @@ msgid "Documentation"
|
||||
msgstr ""
|
||||
|
||||
#: ../common/app_support.rst:216 ../common/app_support.rst:213
|
||||
#: ../common/app_support.rst:211
|
||||
#: ../common/app_support.rst:211 ../common/app_support.rst:217
|
||||
msgid "Documentation feedback"
|
||||
msgstr ""
|
||||
|
||||
@ -4085,14 +4101,17 @@ msgid "Folsom"
|
||||
msgstr ""
|
||||
|
||||
#: ../common/cli_install_openstack_command_line_clients.rst:191
|
||||
#: ../common/cli_install_openstack_command_line_clients.rst:197
|
||||
msgid "For Mac OS X or Linux::"
|
||||
msgstr ""
|
||||
|
||||
#: ../common/cli_install_openstack_command_line_clients.rst:195
|
||||
#: ../common/cli_install_openstack_command_line_clients.rst:201
|
||||
msgid "For Microsoft Windows::"
|
||||
msgstr ""
|
||||
|
||||
#: ../common/cli_install_openstack_command_line_clients.rst:218
|
||||
#: ../common/cli_install_openstack_command_line_clients.rst:224
|
||||
msgid ""
|
||||
"For SUSE Linux Enterprise Server, use zypper to install the clients from the "
|
||||
"distribution packages in the Open Build Service. First, add the Open Build "
|
||||
@ -4183,6 +4202,7 @@ msgid ""
|
||||
msgstr ""
|
||||
|
||||
#: ../common/cli_install_openstack_command_line_clients.rst:213
|
||||
#: ../common/cli_install_openstack_command_line_clients.rst:219
|
||||
msgid ""
|
||||
"For openSUSE, use zypper to install the clients from the distribution "
|
||||
"packages service::"
|
||||
@ -4228,7 +4248,7 @@ msgid ""
|
||||
"from the CURRENT PROJECT list at the top of the tab."
|
||||
msgstr ""
|
||||
|
||||
#: ../common/cli_overview.rst:55
|
||||
#: ../common/cli_overview.rst:55 ../common/cli_overview.rst:61
|
||||
msgid ""
|
||||
"Gather statistics, list items, update metadata, and upload, download, and "
|
||||
"delete files stored by the Object Storage service. Gain access to an Object "
|
||||
@ -4478,6 +4498,7 @@ msgid "Icehouse"
|
||||
msgstr ""
|
||||
|
||||
#: ../common/glossary.rst:1788 ../common/cli_overview.rst:44
|
||||
#: ../common/cli_overview.rst:50
|
||||
msgid "Identity"
|
||||
msgstr ""
|
||||
|
||||
@ -4652,6 +4673,7 @@ msgid "Image API"
|
||||
msgstr ""
|
||||
|
||||
#: ../common/glossary.rst:1844 ../common/cli_overview.rst:49
|
||||
#: ../common/cli_overview.rst:55
|
||||
msgid "Image service"
|
||||
msgstr ""
|
||||
|
||||
@ -4816,6 +4838,7 @@ msgid "Injection problems"
|
||||
msgstr ""
|
||||
|
||||
#: ../common/cli_install_openstack_command_line_clients.rst:189
|
||||
#: ../common/cli_install_openstack_command_line_clients.rst:195
|
||||
msgid "Install each client separately by using the following command:"
|
||||
msgstr ""
|
||||
|
||||
@ -4851,10 +4874,12 @@ msgid "Installed by default on Mac OS X."
|
||||
msgstr ""
|
||||
|
||||
#: ../common/cli_install_openstack_command_line_clients.rst:202
|
||||
#: ../common/cli_install_openstack_command_line_clients.rst:208
|
||||
msgid "Installing from packages"
|
||||
msgstr ""
|
||||
|
||||
#: ../common/cli_install_openstack_command_line_clients.rst:181
|
||||
#: ../common/cli_install_openstack_command_line_clients.rst:187
|
||||
msgid "Installing with pip"
|
||||
msgstr ""
|
||||
|
||||
@ -5006,7 +5031,7 @@ msgid ""
|
||||
"command, TCP, and HTTP/HTTPS GET."
|
||||
msgstr ""
|
||||
|
||||
#: ../common/cli_overview.rst:65
|
||||
#: ../common/cli_overview.rst:65 ../common/cli_overview.rst:71
|
||||
msgid ""
|
||||
"Launch stacks from templates, view details of running stacks including "
|
||||
"events and resources, and update and delete stacks."
|
||||
@ -5462,6 +5487,7 @@ msgstr ""
|
||||
|
||||
#: ../common/glossary.rst:2422 ../common/cli_overview.rst:52
|
||||
#: ../common/glossary.rst:2429 ../common/glossary.rst:2428
|
||||
#: ../common/cli_overview.rst:58
|
||||
msgid "Networking"
|
||||
msgstr ""
|
||||
|
||||
@ -5527,6 +5553,7 @@ msgstr ""
|
||||
|
||||
#: ../common/glossary.rst:2535 ../common/cli_overview.rst:55
|
||||
#: ../common/glossary.rst:2542 ../common/glossary.rst:2541
|
||||
#: ../common/cli_overview.rst:61
|
||||
msgid "Object Storage"
|
||||
msgstr ""
|
||||
|
||||
@ -5572,6 +5599,7 @@ msgid "On Fedora, RHEL, CentOS::"
|
||||
msgstr ""
|
||||
|
||||
#: ../common/cli_install_openstack_command_line_clients.rst:207
|
||||
#: ../common/cli_install_openstack_command_line_clients.rst:213
|
||||
msgid ""
|
||||
"On Red Hat Enterprise Linux, CentOS, or Fedora, use ``yum`` to install the "
|
||||
"clients from the packaged versions available in `RDO <https://www.rdoproject."
|
||||
@ -5909,7 +5937,7 @@ msgid "OpenStack dashboard—:guilabel:`Settings` tab"
|
||||
msgstr ""
|
||||
|
||||
#: ../common/app_support.rst:226 ../common/app_support.rst:223
|
||||
#: ../common/app_support.rst:221
|
||||
#: ../common/app_support.rst:221 ../common/app_support.rst:227
|
||||
msgid "OpenStack distribution packages"
|
||||
msgstr ""
|
||||
|
||||
@ -6130,7 +6158,7 @@ msgid ""
|
||||
msgstr ""
|
||||
|
||||
#: ../common/glossary.rst:2620 ../common/cli_overview.rst:65
|
||||
#: ../common/glossary.rst:2627
|
||||
#: ../common/glossary.rst:2627 ../common/cli_overview.rst:71
|
||||
msgid "Orchestration"
|
||||
msgstr ""
|
||||
|
||||
@ -6520,6 +6548,7 @@ msgid "RAM overcommit"
|
||||
msgstr ""
|
||||
|
||||
#: ../common/cli_install_openstack_command_line_clients.rst:204
|
||||
#: ../common/cli_install_openstack_command_line_clients.rst:210
|
||||
msgid ""
|
||||
"RDO, openSUSE and SUSE Linux Enterprise have client packages that can be "
|
||||
"installed without ``pip``."
|
||||
@ -6821,6 +6850,10 @@ msgid ""
|
||||
"transient or persistent."
|
||||
msgstr ""
|
||||
|
||||
#: ../common/cli_overview.rst:78
|
||||
msgid "Shared file systems"
|
||||
msgstr ""
|
||||
|
||||
#: ../common/glossary.rst:3244 ../common/glossary.rst:3251
|
||||
msgid "Sheepdog"
|
||||
msgstr ""
|
||||
@ -7072,7 +7105,7 @@ msgid ""
|
||||
msgstr ""
|
||||
|
||||
#: ../common/glossary.rst:3428 ../common/cli_overview.rst:72
|
||||
#: ../common/glossary.rst:3435
|
||||
#: ../common/glossary.rst:3435 ../common/cli_overview.rst:81
|
||||
msgid "Telemetry"
|
||||
msgstr ""
|
||||
|
||||
@ -7390,7 +7423,7 @@ msgid ""
|
||||
msgstr ""
|
||||
|
||||
#: ../common/app_support.rst:198 ../common/app_support.rst:195
|
||||
#: ../common/app_support.rst:193
|
||||
#: ../common/app_support.rst:193 ../common/app_support.rst:199
|
||||
msgid "The OpenStack IRC channel"
|
||||
msgstr ""
|
||||
|
||||
@ -7443,7 +7476,7 @@ msgid ""
|
||||
msgstr ""
|
||||
|
||||
#: ../common/app_support.rst:200 ../common/app_support.rst:197
|
||||
#: ../common/app_support.rst:195
|
||||
#: ../common/app_support.rst:195 ../common/app_support.rst:201
|
||||
msgid ""
|
||||
"The OpenStack community lives in the #openstack IRC channel on the Freenode "
|
||||
"network. You can hang out, ask questions, or get immediate feedback for "
|
||||
@ -7915,6 +7948,7 @@ msgid "The fibre channel protocol tunneled within Ethernet."
|
||||
msgstr ""
|
||||
|
||||
#: ../common/cli_install_openstack_command_line_clients.rst:168
|
||||
#: ../common/cli_install_openstack_command_line_clients.rst:174
|
||||
msgid ""
|
||||
"The following CLIs are deprecated in favor of ``openstack``, the Common "
|
||||
"OpenStack client supporting multiple services:"
|
||||
@ -7926,7 +7960,7 @@ msgid "The following Launchpad Bugs areas are available:"
|
||||
msgstr ""
|
||||
|
||||
#: ../common/app_support.rst:228 ../common/app_support.rst:225
|
||||
#: ../common/app_support.rst:223
|
||||
#: ../common/app_support.rst:223 ../common/app_support.rst:229
|
||||
msgid ""
|
||||
"The following Linux distributions provide community-supported packages for "
|
||||
"OpenStack:"
|
||||
@ -7980,6 +8014,7 @@ msgid ""
|
||||
msgstr ""
|
||||
|
||||
#: ../common/cli_install_openstack_command_line_clients.rst:173
|
||||
#: ../common/cli_install_openstack_command_line_clients.rst:179
|
||||
msgid ""
|
||||
"The following example shows the command for installing the nova client with "
|
||||
"``pip``."
|
||||
@ -8452,6 +8487,7 @@ msgid "Then install pip and use it to manage client installation:"
|
||||
msgstr ""
|
||||
|
||||
#: ../common/cli_install_openstack_command_line_clients.rst:224
|
||||
#: ../common/cli_install_openstack_command_line_clients.rst:230
|
||||
msgid "Then you can install the packages::"
|
||||
msgstr ""
|
||||
|
||||
@ -8653,6 +8689,7 @@ msgstr ""
|
||||
#: ../common/get_started_with_openstack.rst:143
|
||||
#: ../common/get_started_feedback.rst:5 ../common/app_support.rst:215
|
||||
#: ../common/app_support.rst:17 ../common/app_support.rst:213
|
||||
#: ../common/app_support.rst:219
|
||||
msgid ""
|
||||
"To provide feedback on documentation, join and use the openstack-docs@lists."
|
||||
"openstack.org mailing list at `OpenStack Documentation Mailing List <http://"
|
||||
@ -8661,6 +8698,7 @@ msgid ""
|
||||
msgstr ""
|
||||
|
||||
#: ../common/cli_install_openstack_command_line_clients.rst:236
|
||||
#: ../common/cli_install_openstack_command_line_clients.rst:242
|
||||
msgid "To remove the client, run the ``pip uninstall`` command::"
|
||||
msgstr ""
|
||||
|
||||
@ -8713,6 +8751,7 @@ msgid "To update an image by name or ID, use ``glance image-update``:"
|
||||
msgstr ""
|
||||
|
||||
#: ../common/cli_install_openstack_command_line_clients.rst:231
|
||||
#: ../common/cli_install_openstack_command_line_clients.rst:237
|
||||
msgid ""
|
||||
"To upgrade a client, add the ``--upgrade`` option to the ``pip install`` "
|
||||
"command::"
|
||||
@ -8886,6 +8925,7 @@ msgid "Uniquely ID for an Object Storage object."
|
||||
msgstr ""
|
||||
|
||||
#: ../common/cli_install_openstack_command_line_clients.rst:229
|
||||
#: ../common/cli_install_openstack_command_line_clients.rst:235
|
||||
msgid "Upgrade or remove clients"
|
||||
msgstr ""
|
||||
|
||||
@ -8921,6 +8961,7 @@ msgid ""
|
||||
msgstr ""
|
||||
|
||||
#: ../common/cli_install_openstack_command_line_clients.rst:183
|
||||
#: ../common/cli_install_openstack_command_line_clients.rst:189
|
||||
msgid ""
|
||||
"Use pip to install the OpenStack clients on a Linux, Mac OS X, or Microsoft "
|
||||
"Windows system. It is easy to use and ensures that you get the latest "
|
||||
@ -9231,6 +9272,7 @@ msgid ""
|
||||
msgstr ""
|
||||
|
||||
#: ../common/cli_install_openstack_command_line_clients.rst:241
|
||||
#: ../common/cli_install_openstack_command_line_clients.rst:247
|
||||
msgid "What's next"
|
||||
msgstr ""
|
||||
|
||||
@ -9482,31 +9524,41 @@ msgid ""
|
||||
"`Block Storage <http://www.openstack.org/software/openstack-storage/>`__"
|
||||
msgstr ""
|
||||
|
||||
#: ../common/app_support.rst:171
|
||||
msgid ""
|
||||
"`Bugs: Application catalog (murano) <https://bugs.launchpad.net/murano>`__"
|
||||
msgstr ""
|
||||
|
||||
#: ../common/app_support.rst:176 ../common/app_support.rst:173
|
||||
#: ../common/app_support.rst:171
|
||||
msgid ""
|
||||
"`Bugs: Bare metal service (ironic) <https://bugs.launchpad.net/ironic>`__"
|
||||
msgstr ""
|
||||
|
||||
#: ../common/app_support.rst:175
|
||||
msgid ""
|
||||
"`Bugs: Containers service (magnum) <https://bugs.launchpad.net/magnum>`__"
|
||||
msgstr ""
|
||||
|
||||
#: ../common/app_support.rst:178 ../common/app_support.rst:175
|
||||
#: ../common/app_support.rst:173
|
||||
#: ../common/app_support.rst:173 ../common/app_support.rst:177
|
||||
msgid ""
|
||||
"`Bugs: Data processing service (sahara) <https://bugs.launchpad.net/"
|
||||
"sahara>`__"
|
||||
msgstr ""
|
||||
|
||||
#: ../common/app_support.rst:181 ../common/app_support.rst:178
|
||||
#: ../common/app_support.rst:176
|
||||
#: ../common/app_support.rst:176 ../common/app_support.rst:180
|
||||
msgid "`Bugs: Database service (trove) <https://bugs.launchpad.net/trove>`__"
|
||||
msgstr ""
|
||||
|
||||
#: ../common/app_support.rst:188 ../common/app_support.rst:185
|
||||
#: ../common/app_support.rst:183
|
||||
#: ../common/app_support.rst:183 ../common/app_support.rst:189
|
||||
msgid "`Bugs: Messaging service (zaqar) <https://bugs.launchpad.net/zaqar>`__"
|
||||
msgstr ""
|
||||
|
||||
#: ../common/app_support.rst:191 ../common/app_support.rst:188
|
||||
#: ../common/app_support.rst:186
|
||||
#: ../common/app_support.rst:186 ../common/app_support.rst:192
|
||||
msgid ""
|
||||
"`Bugs: OpenStack API Documentation (developer.openstack.org) <https://bugs."
|
||||
"launchpad.net/openstack-api-site>`__"
|
||||
@ -9531,7 +9583,7 @@ msgid ""
|
||||
msgstr ""
|
||||
|
||||
#: ../common/app_support.rst:194 ../common/app_support.rst:191
|
||||
#: ../common/app_support.rst:189
|
||||
#: ../common/app_support.rst:189 ../common/app_support.rst:195
|
||||
msgid ""
|
||||
"`Bugs: OpenStack Documentation (docs.openstack.org) <https://bugs.launchpad."
|
||||
"net/openstack-manuals>`__"
|
||||
@ -9563,12 +9615,17 @@ msgid ""
|
||||
msgstr ""
|
||||
|
||||
#: ../common/app_support.rst:183 ../common/app_support.rst:180
|
||||
#: ../common/app_support.rst:178
|
||||
#: ../common/app_support.rst:178 ../common/app_support.rst:182
|
||||
msgid "`Bugs: Orchestration (heat) <https://bugs.launchpad.net/heat>`__"
|
||||
msgstr ""
|
||||
|
||||
#: ../common/app_support.rst:184
|
||||
msgid ""
|
||||
"`Bugs: Shared file systems (manila) <https://bugs.launchpad.net/manila>`__"
|
||||
msgstr ""
|
||||
|
||||
#: ../common/app_support.rst:185 ../common/app_support.rst:182
|
||||
#: ../common/app_support.rst:180
|
||||
#: ../common/app_support.rst:180 ../common/app_support.rst:186
|
||||
msgid ""
|
||||
"`Bugs: Telemetry (ceilometer) <https://bugs.launchpad.net/ceilometer>`__"
|
||||
msgstr ""
|
||||
@ -9871,6 +9928,7 @@ msgid "``heat`` command-line client"
|
||||
msgstr ""
|
||||
|
||||
#: ../common/cli_install_openstack_command_line_clients.rst:171
|
||||
#: ../common/cli_install_openstack_command_line_clients.rst:177
|
||||
msgid "``keystone`` - Identity service API and extensions"
|
||||
msgstr ""
|
||||
|
||||
@ -9883,6 +9941,19 @@ msgid "``logging_default_format_string``"
|
||||
msgstr ""
|
||||
|
||||
#: ../common/cli_install_openstack_command_line_clients.rst:156
|
||||
msgid "``magnum`` - Containers service API"
|
||||
msgstr ""
|
||||
|
||||
#: ../common/cli_install_openstack_command_line_clients.rst:158
|
||||
msgid "``manila`` - Shared file systems API"
|
||||
msgstr ""
|
||||
|
||||
#: ../common/cli_install_openstack_command_line_clients.rst:160
|
||||
msgid "``murano`` - Application catalog API"
|
||||
msgstr ""
|
||||
|
||||
#: ../common/cli_install_openstack_command_line_clients.rst:156
|
||||
#: ../common/cli_install_openstack_command_line_clients.rst:162
|
||||
msgid "``neutron`` - Networking API"
|
||||
msgstr ""
|
||||
|
||||
@ -9935,10 +10006,12 @@ msgid "``nova-xvpvncproxy`` daemon"
|
||||
msgstr ""
|
||||
|
||||
#: ../common/cli_install_openstack_command_line_clients.rst:158
|
||||
#: ../common/cli_install_openstack_command_line_clients.rst:164
|
||||
msgid "``nova`` - Compute API and extensions"
|
||||
msgstr ""
|
||||
|
||||
#: ../common/cli_install_openstack_command_line_clients.rst:166
|
||||
#: ../common/cli_install_openstack_command_line_clients.rst:172
|
||||
msgid "``openstack`` - Common OpenStack client supporting multiple services"
|
||||
msgstr ""
|
||||
|
||||
@ -9948,6 +10021,7 @@ msgid "``python-troveclient`` command-line client"
|
||||
msgstr ""
|
||||
|
||||
#: ../common/cli_install_openstack_command_line_clients.rst:160
|
||||
#: ../common/cli_install_openstack_command_line_clients.rst:166
|
||||
msgid "``sahara`` - Data Processing API"
|
||||
msgstr ""
|
||||
|
||||
@ -9960,6 +10034,7 @@ msgid "``show_multiple_locations = True``"
|
||||
msgstr ""
|
||||
|
||||
#: ../common/cli_install_openstack_command_line_clients.rst:162
|
||||
#: ../common/cli_install_openstack_command_line_clients.rst:168
|
||||
msgid "``swift`` - Object Storage API"
|
||||
msgstr ""
|
||||
|
||||
@ -9985,6 +10060,7 @@ msgid "``trove-taskmanager`` service"
|
||||
msgstr ""
|
||||
|
||||
#: ../common/cli_install_openstack_command_line_clients.rst:164
|
||||
#: ../common/cli_install_openstack_command_line_clients.rst:170
|
||||
msgid "``trove`` - Database service API"
|
||||
msgstr ""
|
||||
|
||||
@ -10218,6 +10294,7 @@ msgid "catalog service"
|
||||
msgstr ""
|
||||
|
||||
#: ../common/glossary.rst:603 ../common/cli_overview.rst:72
|
||||
#: ../common/cli_overview.rst:81
|
||||
msgid "ceilometer"
|
||||
msgstr ""
|
||||
|
||||
@ -10250,6 +10327,7 @@ msgid "child cell"
|
||||
msgstr ""
|
||||
|
||||
#: ../common/glossary.rst:675 ../common/cli_overview.rst:34
|
||||
#: ../common/cli_overview.rst:37
|
||||
msgid "cinder"
|
||||
msgstr ""
|
||||
|
||||
@ -10678,6 +10756,7 @@ msgid "generic routing encapsulation (GRE)"
|
||||
msgstr ""
|
||||
|
||||
#: ../common/glossary.rst:1551 ../common/cli_overview.rst:49
|
||||
#: ../common/cli_overview.rst:55
|
||||
msgid "glance"
|
||||
msgstr ""
|
||||
|
||||
@ -10724,6 +10803,7 @@ msgid "health monitor"
|
||||
msgstr ""
|
||||
|
||||
#: ../common/glossary.rst:1638 ../common/cli_overview.rst:65
|
||||
#: ../common/cli_overview.rst:71
|
||||
msgid "heat"
|
||||
msgstr ""
|
||||
|
||||
@ -10888,6 +10968,7 @@ msgid "kernel-based VM (KVM)"
|
||||
msgstr ""
|
||||
|
||||
#: ../common/glossary.rst:2075 ../common/cli_overview.rst:44
|
||||
#: ../common/cli_overview.rst:50
|
||||
msgid "keystone"
|
||||
msgstr ""
|
||||
|
||||
@ -10923,7 +11004,7 @@ msgstr ""
|
||||
msgid "magnetoDB"
|
||||
msgstr ""
|
||||
|
||||
#: ../common/glossary.rst:2184
|
||||
#: ../common/glossary.rst:2184 ../common/cli_overview.rst:44
|
||||
msgid "magnum"
|
||||
msgstr ""
|
||||
|
||||
@ -10947,7 +11028,7 @@ msgstr ""
|
||||
msgid "manifest object"
|
||||
msgstr ""
|
||||
|
||||
#: ../common/glossary.rst:2213
|
||||
#: ../common/glossary.rst:2213 ../common/cli_overview.rst:78
|
||||
msgid "manila"
|
||||
msgstr ""
|
||||
|
||||
@ -11015,7 +11096,7 @@ msgid "multinic"
|
||||
msgstr ""
|
||||
|
||||
#: ../common/glossary.rst:2311 ../common/glossary.rst:2318
|
||||
#: ../common/glossary.rst:2317
|
||||
#: ../common/glossary.rst:2317 ../common/cli_overview.rst:34
|
||||
msgid "murano"
|
||||
msgstr ""
|
||||
|
||||
@ -11079,6 +11160,7 @@ msgstr ""
|
||||
|
||||
#: ../common/glossary.rst:2433 ../common/cli_overview.rst:52
|
||||
#: ../common/glossary.rst:2440 ../common/glossary.rst:2439
|
||||
#: ../common/cli_overview.rst:58
|
||||
msgid "neutron"
|
||||
msgstr ""
|
||||
|
||||
@ -11129,6 +11211,7 @@ msgstr ""
|
||||
|
||||
#: ../common/glossary.rst:2486 ../common/cli_overview.rst:37
|
||||
#: ../common/glossary.rst:2493 ../common/glossary.rst:2492
|
||||
#: ../common/cli_overview.rst:40
|
||||
msgid "nova"
|
||||
msgstr ""
|
||||
|
||||
@ -11189,7 +11272,7 @@ msgstr ""
|
||||
msgid "openSUSE"
|
||||
msgstr ""
|
||||
|
||||
#: ../common/cli_overview.rst:80
|
||||
#: ../common/cli_overview.rst:80 ../common/cli_overview.rst:89
|
||||
msgid "openstack"
|
||||
msgstr ""
|
||||
|
||||
@ -11337,47 +11420,59 @@ msgstr ""
|
||||
msgid "public network"
|
||||
msgstr ""
|
||||
|
||||
#: ../common/cli_overview.rst:72
|
||||
#: ../common/cli_overview.rst:72 ../common/cli_overview.rst:81
|
||||
msgid "python-ceilometerclient"
|
||||
msgstr ""
|
||||
|
||||
#: ../common/cli_overview.rst:34
|
||||
#: ../common/cli_overview.rst:34 ../common/cli_overview.rst:37
|
||||
msgid "python-cinderclient"
|
||||
msgstr ""
|
||||
|
||||
#: ../common/cli_overview.rst:49
|
||||
#: ../common/cli_overview.rst:49 ../common/cli_overview.rst:55
|
||||
msgid "python-glanceclient"
|
||||
msgstr ""
|
||||
|
||||
#: ../common/cli_overview.rst:65
|
||||
#: ../common/cli_overview.rst:65 ../common/cli_overview.rst:71
|
||||
msgid "python-heatclient"
|
||||
msgstr ""
|
||||
|
||||
#: ../common/cli_overview.rst:44
|
||||
#: ../common/cli_overview.rst:44 ../common/cli_overview.rst:50
|
||||
msgid "python-keystoneclient"
|
||||
msgstr ""
|
||||
|
||||
#: ../common/cli_overview.rst:52
|
||||
#: ../common/cli_overview.rst:44
|
||||
msgid "python-magnumclient"
|
||||
msgstr ""
|
||||
|
||||
#: ../common/cli_overview.rst:78
|
||||
msgid "python-manilaclient"
|
||||
msgstr ""
|
||||
|
||||
#: ../common/cli_overview.rst:34
|
||||
msgid "python-muranoclient"
|
||||
msgstr ""
|
||||
|
||||
#: ../common/cli_overview.rst:52 ../common/cli_overview.rst:58
|
||||
msgid "python-neutronclient"
|
||||
msgstr ""
|
||||
|
||||
#: ../common/cli_overview.rst:37
|
||||
#: ../common/cli_overview.rst:37 ../common/cli_overview.rst:40
|
||||
msgid "python-novaclient"
|
||||
msgstr ""
|
||||
|
||||
#: ../common/cli_overview.rst:80
|
||||
#: ../common/cli_overview.rst:80 ../common/cli_overview.rst:89
|
||||
msgid "python-openstackclient"
|
||||
msgstr ""
|
||||
|
||||
#: ../common/cli_overview.rst:76
|
||||
#: ../common/cli_overview.rst:76 ../common/cli_overview.rst:85
|
||||
msgid "python-saharaclient"
|
||||
msgstr ""
|
||||
|
||||
#: ../common/cli_overview.rst:55
|
||||
#: ../common/cli_overview.rst:55 ../common/cli_overview.rst:61
|
||||
msgid "python-swiftclient"
|
||||
msgstr ""
|
||||
|
||||
#: ../common/cli_overview.rst:41
|
||||
#: ../common/cli_overview.rst:41 ../common/cli_overview.rst:47
|
||||
msgid "python-troveclient"
|
||||
msgstr ""
|
||||
|
||||
@ -11514,7 +11609,7 @@ msgid "rtl8139"
|
||||
msgstr ""
|
||||
|
||||
#: ../common/glossary.rst:3098 ../common/cli_overview.rst:76
|
||||
#: ../common/glossary.rst:3105
|
||||
#: ../common/glossary.rst:3105 ../common/cli_overview.rst:85
|
||||
msgid "sahara"
|
||||
msgstr ""
|
||||
|
||||
@ -11683,7 +11778,7 @@ msgid "swawth"
|
||||
msgstr ""
|
||||
|
||||
#: ../common/glossary.rst:3386 ../common/cli_overview.rst:55
|
||||
#: ../common/glossary.rst:3393
|
||||
#: ../common/glossary.rst:3393 ../common/cli_overview.rst:61
|
||||
msgid "swift"
|
||||
msgstr ""
|
||||
|
||||
@ -11790,7 +11885,7 @@ msgid "transient queue"
|
||||
msgstr ""
|
||||
|
||||
#: ../common/glossary.rst:3522 ../common/cli_overview.rst:41
|
||||
#: ../common/glossary.rst:3529
|
||||
#: ../common/glossary.rst:3529 ../common/cli_overview.rst:47
|
||||
msgid "trove"
|
||||
msgstr ""
|
||||
|
||||
|
||||
@ -1,7 +1,7 @@
|
||||
msgid ""
|
||||
msgstr ""
|
||||
"Project-Id-Version: PACKAGE VERSION\n"
|
||||
"POT-Creation-Date: 2015-08-26 06:30+0000\n"
|
||||
"POT-Creation-Date: 2015-09-03 06:15+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"
|
||||
@ -1337,7 +1337,7 @@ msgstr ""
|
||||
msgid "Feedback"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/common/ch_getstart.xml:223(para) ./doc/common/app_support.xml:20(para) ./doc/common/app_support.xml:355(para)
|
||||
#: ./doc/common/ch_getstart.xml:223(para) ./doc/common/app_support.xml:20(para) ./doc/common/app_support.xml:370(para)
|
||||
msgid "To provide feedback on documentation, join and use the <email>openstack-docs@lists.openstack.org</email> mailing list at <link xlink:href=\"http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs\">OpenStack Documentation Mailing List</link>, or <link xlink:href=\"https://bugs.launchpad.net/openstack-manuals/+filebug\">report a bug</link>."
|
||||
msgstr ""
|
||||
|
||||
@ -3462,82 +3462,94 @@ msgid "<literal>trove</literal> - Database service API"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/common/section_cli_install.xml:209(para)
|
||||
msgid "<literal>magnum</literal> - Containers service API"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/common/section_cli_install.xml:213(para)
|
||||
msgid "<literal>manila</literal> - Shared file systems API"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/common/section_cli_install.xml:217(para)
|
||||
msgid "<literal>murano</literal> - Application catalog API"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/common/section_cli_install.xml:221(para)
|
||||
msgid "<literal>openstack</literal> - Common OpenStack client supporting multiple services"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/common/section_cli_install.xml:219(para)
|
||||
#: ./doc/common/section_cli_install.xml:231(para)
|
||||
msgid "<literal>keystone</literal> - Identity service API and extensions"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/common/section_cli_install.xml:214(para)
|
||||
#: ./doc/common/section_cli_install.xml:226(para)
|
||||
msgid "The following CLIs are deprecated in favor of <literal>openstack</literal>, the Common OpenStack client supporting multiple services: <placeholder-1/>"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/common/section_cli_install.xml:225(para)
|
||||
#: ./doc/common/section_cli_install.xml:237(para)
|
||||
msgid "The following example shows the command for installing the nova client with <placeholder-1/>."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/common/section_cli_install.xml:229(title)
|
||||
#: ./doc/common/section_cli_install.xml:241(title)
|
||||
msgid "Installing with pip"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/common/section_cli_install.xml:230(para)
|
||||
#: ./doc/common/section_cli_install.xml:242(para)
|
||||
msgid "Use <package>pip</package> to install the OpenStack clients on a Linux, Mac OS X, or Microsoft Windows system. It is easy to use and ensures that you get the latest version of the client from the <link xlink:href=\"https://pypi.python.org/pypi\">Python Package Index</link>. Also, <package>pip</package> enables you to update or remove a package."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/common/section_cli_install.xml:237(para)
|
||||
#: ./doc/common/section_cli_install.xml:249(para)
|
||||
msgid "Install each client separately by using the following command:"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/common/section_cli_install.xml:240(para)
|
||||
#: ./doc/common/section_cli_install.xml:252(para)
|
||||
msgid "For Mac OS X or Linux:"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/common/section_cli_install.xml:241(replaceable) ./doc/common/section_cli_install.xml:243(replaceable) ./doc/common/section_cli_install.xml:255(replaceable) ./doc/common/section_cli_install.xml:259(replaceable) ./doc/common/section_cli_install.xml:266(replaceable) ./doc/common/section_cli_install.xml:275(replaceable) ./doc/common/section_cli_install.xml:278(replaceable) ./doc/common/section_cli_version.xml:10(replaceable)
|
||||
#: ./doc/common/section_cli_install.xml:253(replaceable) ./doc/common/section_cli_install.xml:255(replaceable) ./doc/common/section_cli_install.xml:267(replaceable) ./doc/common/section_cli_install.xml:271(replaceable) ./doc/common/section_cli_install.xml:278(replaceable) ./doc/common/section_cli_install.xml:287(replaceable) ./doc/common/section_cli_install.xml:290(replaceable) ./doc/common/section_cli_version.xml:10(replaceable)
|
||||
msgid "PROJECT"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/common/section_cli_install.xml:242(para)
|
||||
#: ./doc/common/section_cli_install.xml:254(para)
|
||||
msgid "For Microsoft Windows:"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/common/section_cli_install.xml:247(title)
|
||||
#: ./doc/common/section_cli_install.xml:259(title)
|
||||
msgid "Installing from packages"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/common/section_cli_install.xml:248(para)
|
||||
#: ./doc/common/section_cli_install.xml:260(para)
|
||||
msgid "RDO, openSUSE and SUSE Linux Enterprise have client packages that can be installed without <filename>pip</filename>."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/common/section_cli_install.xml:250(para)
|
||||
#: ./doc/common/section_cli_install.xml:262(para)
|
||||
msgid "On Red Hat Enterprise Linux, CentOS, or Fedora, use <placeholder-1/> to install the clients from the packaged versions available in <link xlink:href=\"https://www.rdoproject.org/\">RDO</link>: <placeholder-2/>"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/common/section_cli_install.xml:256(para)
|
||||
#: ./doc/common/section_cli_install.xml:268(para)
|
||||
msgid "For openSUSE, use <package>zypper</package> to install the clients from the distribution packages Service: <placeholder-1/>"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/common/section_cli_install.xml:260(para)
|
||||
#: ./doc/common/section_cli_install.xml:272(para)
|
||||
msgid "For SUSE Linux Enterprise Server, use <package>zypper</package> to install the clients from the distribution packages in the Open Build Service. First, add the Open Build Service repository: <placeholder-1/> Then you can install the packages: <placeholder-2/>"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/common/section_cli_install.xml:271(title)
|
||||
#: ./doc/common/section_cli_install.xml:283(title)
|
||||
msgid "Upgrade or remove clients"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/common/section_cli_install.xml:272(para)
|
||||
#: ./doc/common/section_cli_install.xml:284(para)
|
||||
msgid "To upgrade a client, add the <literal>--upgrade</literal> option to the <placeholder-1/> command:"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/common/section_cli_install.xml:276(para)
|
||||
#: ./doc/common/section_cli_install.xml:288(para)
|
||||
msgid "To remove the a client, run the <placeholder-1/> command:"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/common/section_cli_install.xml:281(title)
|
||||
#: ./doc/common/section_cli_install.xml:293(title)
|
||||
msgid "What's next"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/common/section_cli_install.xml:282(para)
|
||||
#: ./doc/common/section_cli_install.xml:294(para)
|
||||
msgid "Before you can run client commands, you must create and source the <filename><replaceable>PROJECT</replaceable>-openrc.sh</filename> file to set environment variables. See <xref linkend=\"cli_openrc\"/>."
|
||||
msgstr ""
|
||||
|
||||
@ -4002,86 +4014,98 @@ msgid "Bugs: OpenStack Object Storage (swift)"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/common/app_support.xml:286(link)
|
||||
msgid "Bugs: Bare metal service (ironic)"
|
||||
msgid "Bugs: Application catalog (murano)"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/common/app_support.xml:291(link)
|
||||
msgid "Bugs: Bare metal service (ironic)"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/common/app_support.xml:296(link)
|
||||
msgid "Bugs: Containers service (magnum)"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/common/app_support.xml:301(link)
|
||||
msgid "Bugs: Data processing service (sahara)"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/common/app_support.xml:297(link)
|
||||
#: ./doc/common/app_support.xml:307(link)
|
||||
msgid "Bugs: Database service (trove)"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/common/app_support.xml:302(link)
|
||||
#: ./doc/common/app_support.xml:312(link)
|
||||
msgid "Bugs: Orchestration (heat)"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/common/app_support.xml:307(link)
|
||||
#: ./doc/common/app_support.xml:317(link)
|
||||
msgid "Bugs: Shared file systems (manila)"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/common/app_support.xml:322(link)
|
||||
msgid "Bugs: Telemetry (ceilometer)"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/common/app_support.xml:312(link)
|
||||
#: ./doc/common/app_support.xml:327(link)
|
||||
msgid "Bugs: Message Service (zaqar)"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/common/app_support.xml:318(link)
|
||||
#: ./doc/common/app_support.xml:333(link)
|
||||
msgid "Bugs: OpenStack API Documentation (developer.openstack.org)"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/common/app_support.xml:324(link)
|
||||
#: ./doc/common/app_support.xml:339(link)
|
||||
msgid "Bugs: OpenStack Documentation (docs.openstack.org)"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/common/app_support.xml:330(title)
|
||||
#: ./doc/common/app_support.xml:345(title)
|
||||
msgid "The OpenStack IRC channel"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/common/app_support.xml:331(para)
|
||||
#: ./doc/common/app_support.xml:346(para)
|
||||
msgid "The OpenStack community lives in the #openstack IRC channel on the Freenode network. You can hang out, ask questions, or get immediate feedback for urgent and pressing issues. To install an IRC client or use a browser-based client, go to <link xlink:href=\"https://webchat.freenode.net\">https://webchat.freenode.net/</link>. You can also use Colloquy (Mac OS X, <link xlink:href=\"http://colloquy.info/\">http://colloquy.info/</link>), mIRC (Windows, <link xlink:href=\"http://www.mirc.com/\">http://www.mirc.com/</link>), or XChat (Linux). When you are in the IRC channel and want to share code or command output, the generally accepted method is to use a Paste Bin. The OpenStack project has one at <link xlink:href=\"http://paste.openstack.org\">http://paste.openstack.org</link>. Just paste your longer amounts of text or logs in the web form and you get a URL that you can paste into the channel. The OpenStack IRC channel is <literal>#openstack</literal> on <literal>irc.freenode.net</literal>. You can find a list of all OpenStack IRC channels at <link xlink:href=\"https://wiki.openstack.org/wiki/IRC\">https://wiki.openstack.org/wiki/IRC</link>."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/common/app_support.xml:354(title)
|
||||
#: ./doc/common/app_support.xml:369(title)
|
||||
msgid "Documentation feedback"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/common/app_support.xml:361(title)
|
||||
#: ./doc/common/app_support.xml:376(title)
|
||||
msgid "OpenStack distribution packages"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/common/app_support.xml:362(para)
|
||||
#: ./doc/common/app_support.xml:377(para)
|
||||
msgid "The following Linux distributions provide community-supported packages for OpenStack:"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/common/app_support.xml:366(emphasis)
|
||||
#: ./doc/common/app_support.xml:381(emphasis)
|
||||
msgid "Debian:"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/common/app_support.xml:369(link)
|
||||
#: ./doc/common/app_support.xml:384(link)
|
||||
msgid "https://wiki.debian.org/OpenStack"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/common/app_support.xml:372(emphasis)
|
||||
#: ./doc/common/app_support.xml:387(emphasis)
|
||||
msgid "CentOS, Fedora, and Red Hat Enterprise Linux:"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/common/app_support.xml:375(link)
|
||||
#: ./doc/common/app_support.xml:390(link)
|
||||
msgid "https://www.rdoproject.org/"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/common/app_support.xml:378(emphasis)
|
||||
#: ./doc/common/app_support.xml:393(emphasis)
|
||||
msgid "openSUSE and SUSE Linux Enterprise Server:"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/common/app_support.xml:382(link)
|
||||
#: ./doc/common/app_support.xml:397(link)
|
||||
msgid "https://en.opensuse.org/Portal:OpenStack"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/common/app_support.xml:385(emphasis)
|
||||
#: ./doc/common/app_support.xml:400(emphasis)
|
||||
msgid "Ubuntu:"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/common/app_support.xml:388(link)
|
||||
#: ./doc/common/app_support.xml:403(link)
|
||||
msgid "https://wiki.ubuntu.com/ServerTeam/CloudArchive"
|
||||
msgstr ""
|
||||
|
||||
@ -6003,7 +6027,7 @@ msgstr ""
|
||||
msgid "Identity"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/common/section_cli_overview.xml:68(package) ./doc/common/section_cli_overview.xml:114(package)
|
||||
#: ./doc/common/section_cli_overview.xml:68(package) ./doc/common/section_cli_overview.xml:132(package)
|
||||
msgid "python-openstackclient"
|
||||
msgstr ""
|
||||
|
||||
@ -6060,14 +6084,50 @@ msgid "Creates and manages Hadoop clusters on OpenStack."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/common/section_cli_overview.xml:112(td)
|
||||
msgid "Common client"
|
||||
msgid "Containers service"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/common/section_cli_overview.xml:114(package)
|
||||
msgid "python-magnumclient"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/common/section_cli_overview.xml:115(td)
|
||||
msgid "Create and manage containers."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/common/section_cli_overview.xml:118(td)
|
||||
msgid "Shared file systems"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/common/section_cli_overview.xml:120(package)
|
||||
msgid "python-manilaclient"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/common/section_cli_overview.xml:121(td)
|
||||
msgid "Create and manage shared file systems."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/common/section_cli_overview.xml:124(td)
|
||||
msgid "Application catalog"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/common/section_cli_overview.xml:126(package)
|
||||
msgid "python-muranoclient"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/common/section_cli_overview.xml:127(td)
|
||||
msgid "Create and manage application catalog."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/common/section_cli_overview.xml:130(td)
|
||||
msgid "Common client"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/common/section_cli_overview.xml:133(td)
|
||||
msgid "Common client for the OpenStack project."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/common/section_cli_overview.xml:119(para)
|
||||
#: ./doc/common/section_cli_overview.xml:137(para)
|
||||
msgid "For client installation instructions, see <link xlink:href=\"http://docs.openstack.org/user-guide/common/cli_install_openstack_command_line_clients.html\">Install the OpenStack command-line clients</link>. For information about the OpenStack RC file, see <link xlink:href=\"http://docs.openstack.org/user-guide/common/cli_set_environment_variables_using_openstack_rc.html\">Download and source the OpenStack RC file</link>."
|
||||
msgstr ""
|
||||
|
||||
|
||||
@ -21,9 +21,9 @@
|
||||
msgid ""
|
||||
msgstr ""
|
||||
"Project-Id-Version: OpenStack Manuals\n"
|
||||
"POT-Creation-Date: 2015-08-06 05:14+0000\n"
|
||||
"PO-Revision-Date: 2015-08-05 10:06+0000\n"
|
||||
"Last-Translator: Katerina Katapodi <catcatapo@yahoo.gr>\n"
|
||||
"POT-Creation-Date: 2015-09-03 05:55+0000\n"
|
||||
"PO-Revision-Date: 2015-09-02 12:35+0000\n"
|
||||
"Last-Translator: openstackjenkins <jenkins@openstack.org>\n"
|
||||
"Language-Team: French (http://www.transifex.com/openstack/openstack-manuals-"
|
||||
"i18n/language/fr/)\n"
|
||||
"MIME-Version: 1.0\n"
|
||||
@ -566,6 +566,9 @@ msgstr "Après"
|
||||
msgid "After the instance starts, <filename>console.log</filename>"
|
||||
msgstr "Après le démarrage de l'instance, <filename>console.log</filename>"
|
||||
|
||||
msgid "Application catalog"
|
||||
msgstr "Catalogue d'applications"
|
||||
|
||||
msgid ""
|
||||
"Assuming you have <package>cloud-init</package> installed, the simplest way "
|
||||
"to configure an instance on boot is to pass a shell script as user data. The "
|
||||
@ -748,6 +751,9 @@ msgstr "Pour configurer le tableau de bord pour HTTPS"
|
||||
msgid "Console interface"
|
||||
msgstr "Interface Console"
|
||||
|
||||
msgid "Containers service"
|
||||
msgstr "Service de conteneurs"
|
||||
|
||||
msgid ""
|
||||
"Contains most configuration options. If the documentation for a "
|
||||
"configuration option does not specify its section, assume that it appears in "
|
||||
|
||||
@ -7,8 +7,8 @@
|
||||
msgid ""
|
||||
msgstr ""
|
||||
"Project-Id-Version: OpenStack Manuals\n"
|
||||
"POT-Creation-Date: 2015-08-28 10:14+0000\n"
|
||||
"PO-Revision-Date: 2015-08-28 09:13+0000\n"
|
||||
"POT-Creation-Date: 2015-09-03 05:55+0000\n"
|
||||
"PO-Revision-Date: 2015-09-02 12:35+0000\n"
|
||||
"Last-Translator: openstackjenkins <jenkins@openstack.org>\n"
|
||||
"Language-Team: Japanese (http://www.transifex.com/openstack/openstack-"
|
||||
"manuals-i18n/language/ja/)\n"
|
||||
@ -628,6 +628,9 @@ msgstr ""
|
||||
"<literal>root</literal> ユーザーを含むすべてのユーザーが、<placeholder-1/> プ"
|
||||
"ロンプトから始まるコマンドを実行できます。"
|
||||
|
||||
msgid "Application catalog"
|
||||
msgstr "アプリケーションカタログ"
|
||||
|
||||
msgid "As a result, the following output is returned:"
|
||||
msgstr "結果として、以下の出力が返されます。"
|
||||
|
||||
@ -815,6 +818,9 @@ msgstr "外部サービスへの接続のタイムアウト"
|
||||
msgid "Console interface"
|
||||
msgstr "コンソールインターフェース"
|
||||
|
||||
msgid "Containers service"
|
||||
msgstr "Containers サービス"
|
||||
|
||||
msgid "Conventions"
|
||||
msgstr "表記規則"
|
||||
|
||||
|
||||
@ -1,7 +1,7 @@
|
||||
msgid ""
|
||||
msgstr ""
|
||||
"Project-Id-Version: PACKAGE VERSION\n"
|
||||
"POT-Creation-Date: 2015-08-27 06:16+0000\n"
|
||||
"POT-Creation-Date: 2015-09-03 06:15+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"
|
||||
@ -1195,11 +1195,15 @@ msgstr ""
|
||||
msgid "The <literal>-f <replaceable>format</replaceable></literal> flag is optional. If omitted, <placeholder-1/> will try to infer the image format."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/image-guide/ch_converting.xml:68(title)
|
||||
#: ./doc/image-guide/ch_converting.xml:64(para)
|
||||
msgid "When converting an image file with Windows OS, ensure the virtio driver is installed. Otherwise, you will get a blue screen of death or BSOD when launching the image due to lack of the virtio driver. Another option is to set the image properties as below when you update the image in glance to avoid this issue, but it will reduce performance significantly."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/image-guide/ch_converting.xml:74(title)
|
||||
msgid "VBoxManage: VDI (VirtualBox) to raw"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/image-guide/ch_converting.xml:69(para)
|
||||
#: ./doc/image-guide/ch_converting.xml:75(para)
|
||||
msgid "If you've created a VDI image using VirtualBox, you can convert it to raw format using the <placeholder-1/> command-line tool that ships with VirtualBox. On Mac OS X, and Linux, VirtualBox stores images by default in the <filename>~/VirtualBox VMs/</filename> directory. The following example creates a raw image in the current directory from a VirtualBox VDI image."
|
||||
msgstr ""
|
||||
|
||||
|
||||
@ -6,8 +6,8 @@
|
||||
msgid ""
|
||||
msgstr ""
|
||||
"Project-Id-Version: OpenStack Manuals\n"
|
||||
"POT-Creation-Date: 2015-08-27 05:23+0000\n"
|
||||
"PO-Revision-Date: 2015-08-27 05:04+0000\n"
|
||||
"POT-Creation-Date: 2015-09-03 05:55+0000\n"
|
||||
"PO-Revision-Date: 2015-09-02 22:25+0000\n"
|
||||
"Last-Translator: Tomoyuki KATO <tomo@dream.daynight.jp>\n"
|
||||
"Language-Team: Japanese (http://www.transifex.com/openstack/openstack-"
|
||||
"manuals-i18n/language/ja/)\n"
|
||||
@ -3610,6 +3610,19 @@ msgstr ""
|
||||
"的に設定する必要があります。OpenStack メタデータサーバーは、Amazon EC2 のイ"
|
||||
"メージにより使用される EC2 メタデータサービスを真似ています。"
|
||||
|
||||
msgid ""
|
||||
"When converting an image file with Windows OS, ensure the virtio driver is "
|
||||
"installed. Otherwise, you will get a blue screen of death or BSOD when "
|
||||
"launching the image due to lack of the virtio driver. Another option is to "
|
||||
"set the image properties as below when you update the image in glance to "
|
||||
"avoid this issue, but it will reduce performance significantly."
|
||||
msgstr ""
|
||||
"Windows OS のイメージファイルを変換するとき、virtio ドライバーがインストール"
|
||||
"されていることを確認してください。そうでなければ、イメージの起動時に、virtio "
|
||||
"ドライバー不足により、ブルースクリーンで停止するでしょう。別の方法として、こ"
|
||||
"の問題を避けるために glance にあるイメージを更新するときに、イメージのプロパ"
|
||||
"ティーを設定することです。しかし、これは大幅に性能が悪くなります。"
|
||||
|
||||
msgid ""
|
||||
"When creating Block Storage volumes from images, also consider your "
|
||||
"configured image properties. If you alter the core image properties, you "
|
||||
|
||||
@ -8,7 +8,7 @@ msgid ""
|
||||
msgstr ""
|
||||
"Project-Id-Version: Networking Guide 0.9\n"
|
||||
"Report-Msgid-Bugs-To: \n"
|
||||
"POT-Creation-Date: 2015-09-02 06:16+0000\n"
|
||||
"POT-Creation-Date: 2015-09-03 06:15+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"
|
||||
@ -104,36 +104,36 @@ msgstr ""
|
||||
msgid "1,0,1"
|
||||
msgstr ""
|
||||
|
||||
#: ../adv_config_ipv6.rst:543
|
||||
#: ../adv_config_ipv6.rst:554
|
||||
msgid ":code:`$1`: The operation being performed."
|
||||
msgstr ""
|
||||
|
||||
#: ../adv_config_ipv6.rst:545
|
||||
#: ../adv_config_ipv6.rst:556
|
||||
msgid ""
|
||||
":code:`$IFACE`: The network interface upon which the request was received."
|
||||
msgstr ""
|
||||
|
||||
#: ../adv_config_ipv6.rst:542
|
||||
#: ../adv_config_ipv6.rst:553
|
||||
msgid ":code:`$PREFIX1`: The prefix being added/deleted by the Dibbler server."
|
||||
msgstr ""
|
||||
|
||||
#: ../adv_config_ipv6.rst:544
|
||||
#: ../adv_config_ipv6.rst:555
|
||||
msgid ":code:`$REMOTE_ADDR`: The IP address of the requesting Dibbler client."
|
||||
msgstr ""
|
||||
|
||||
#: ../adv_config_ipv6.rst:515
|
||||
#: ../adv_config_ipv6.rst:526
|
||||
msgid ""
|
||||
":code:`iface`: The name of the network interface on which to listen for "
|
||||
"prefix delegation messages."
|
||||
msgstr ""
|
||||
|
||||
#: ../adv_config_ipv6.rst:521
|
||||
#: ../adv_config_ipv6.rst:532
|
||||
msgid ""
|
||||
":code:`pd-length`: The length that delegated prefixes will be. This must be "
|
||||
"64 to work with the current OpenStack Networking reference implementation."
|
||||
msgstr ""
|
||||
|
||||
#: ../adv_config_ipv6.rst:517
|
||||
#: ../adv_config_ipv6.rst:528
|
||||
msgid ""
|
||||
":code:`pd-pool`: The larger prefix from which you want your delegated "
|
||||
"prefixes to come. The example given is sufficient if you do not need "
|
||||
@ -141,7 +141,7 @@ msgid ""
|
||||
"necessary."
|
||||
msgstr ""
|
||||
|
||||
#: ../adv_config_ipv6.rst:512
|
||||
#: ../adv_config_ipv6.rst:523
|
||||
msgid ""
|
||||
":code:`script`: Points to a script to be run when a prefix is delegated or "
|
||||
"released. This is only needed if you want instances on your subnets to have "
|
||||
@ -425,7 +425,7 @@ msgstr ""
|
||||
msgid "Advanced services"
|
||||
msgstr ""
|
||||
|
||||
#: ../adv_config_ipv6.rst:497
|
||||
#: ../adv_config_ipv6.rst:508
|
||||
msgid ""
|
||||
"After installing Dibbler, edit the :file:`/etc/dibbler/server.conf` file:"
|
||||
msgstr ""
|
||||
@ -1077,7 +1077,7 @@ msgstr ""
|
||||
msgid "Configuring interfaces of the guest"
|
||||
msgstr ""
|
||||
|
||||
#: ../adv_config_ipv6.rst:495
|
||||
#: ../adv_config_ipv6.rst:506
|
||||
msgid "Configuring the Dibbler server"
|
||||
msgstr ""
|
||||
|
||||
@ -1387,7 +1387,7 @@ msgstr ""
|
||||
msgid "Definition"
|
||||
msgstr ""
|
||||
|
||||
#: ../adv_config_ipv6.rst:656
|
||||
#: ../adv_config_ipv6.rst:667
|
||||
msgid ""
|
||||
"Deleting the router interface causes the subnet to be reverted to the "
|
||||
"temporary CIDR, and all ports have their IPs updated. Prefix leases are "
|
||||
@ -1446,6 +1446,12 @@ msgstr ""
|
||||
msgid "Does not cover how to do this"
|
||||
msgstr ""
|
||||
|
||||
#: ../adv_config_ipv6.rst:479
|
||||
msgid ""
|
||||
"Drivers other than the default one may require extra configuration, please "
|
||||
"refer to :ref:`extra-driver-conf`"
|
||||
msgstr ""
|
||||
|
||||
#: ../scenario_l3ha_ovs.rst:33
|
||||
msgid ""
|
||||
"Due to a bug in the Juno (initial) and Kilo releases, VXLAN and GRE project "
|
||||
@ -1627,6 +1633,10 @@ msgid ""
|
||||
"physical network infrastructure and generally use public IP address ranges."
|
||||
msgstr ""
|
||||
|
||||
#: ../adv_config_ipv6.rst:680
|
||||
msgid "Extra configuration"
|
||||
msgstr ""
|
||||
|
||||
#: ../misc_add_ha_for_DHCP.rst:5
|
||||
msgid "FIXME (Simple note, needs to be added.)"
|
||||
msgstr ""
|
||||
@ -1657,7 +1667,7 @@ msgstr ""
|
||||
msgid "Firewalls"
|
||||
msgstr ""
|
||||
|
||||
#: ../adv_config_ipv6.rst:567
|
||||
#: ../adv_config_ipv6.rst:578
|
||||
msgid "First, create a network and IPv6 subnet:"
|
||||
msgstr ""
|
||||
|
||||
@ -2132,7 +2142,7 @@ msgid ""
|
||||
"pci_passhtrough_whitelist entries per host are supported."
|
||||
msgstr ""
|
||||
|
||||
#: ../adv_config_ipv6.rst:652
|
||||
#: ../adv_config_ipv6.rst:663
|
||||
msgid ""
|
||||
"If the prefix delegation server is configured to delegate globally routable "
|
||||
"prefixes and setup routes, then any instance with a port on this subnet "
|
||||
@ -2149,6 +2159,12 @@ msgid ""
|
||||
"only hosts on the matching VLAN are eligible to receive the frame."
|
||||
msgstr ""
|
||||
|
||||
#: ../adv_config_ipv6.rst:473
|
||||
msgid ""
|
||||
"If you are not using the default dibbler-based driver for prefix delegation, "
|
||||
"then you also need to set the driver in :file:`etc/neutron.conf`::"
|
||||
msgstr ""
|
||||
|
||||
#: ../adv_config_sriov.rst:240
|
||||
msgid ""
|
||||
"If you enabled agent_required=True make sure that you run the sriov-agent on "
|
||||
@ -3090,6 +3106,10 @@ msgid ""
|
||||
"load balancers, and other networking infrastructure on the same layer 2 VLAN."
|
||||
msgstr ""
|
||||
|
||||
#: ../adv_config_ipv6.rst:683
|
||||
msgid "Neutron dhcpv6_pd_agent"
|
||||
msgstr ""
|
||||
|
||||
#: ../adv_config_ipv6.rst:284
|
||||
msgid ""
|
||||
"Neutron networks that contain a SLAAC enabled IPv6 subnet will result in all "
|
||||
@ -3445,6 +3465,11 @@ msgid ""
|
||||
"namespaces:"
|
||||
msgstr ""
|
||||
|
||||
#: ../adv_config_ipv6.rst:695
|
||||
msgid ""
|
||||
"Once you have stacked run the command below to start the neutron-pd-agent::"
|
||||
msgstr ""
|
||||
|
||||
# #-#-#-#-# scenario_dvr_ovs.pot (Networking Guide 0.9) #-#-#-#-#
|
||||
# #-#-#-#-# scenario_l3ha_lb.pot (Networking Guide 0.9) #-#-#-#-#
|
||||
# #-#-#-#-# scenario_l3ha_ovs.pot (Networking Guide 0.9) #-#-#-#-#
|
||||
@ -3856,7 +3881,7 @@ msgstr ""
|
||||
msgid "Options"
|
||||
msgstr ""
|
||||
|
||||
#: ../adv_config_ipv6.rst:556
|
||||
#: ../adv_config_ipv6.rst:567
|
||||
msgid "Or to run in headless mode::"
|
||||
msgstr ""
|
||||
|
||||
@ -4148,7 +4173,7 @@ msgstr ""
|
||||
msgid "Reference common configuration items"
|
||||
msgstr ""
|
||||
|
||||
#: ../adv_config_ipv6.rst:661
|
||||
#: ../adv_config_ipv6.rst:672
|
||||
msgid "References"
|
||||
msgstr ""
|
||||
|
||||
@ -4226,7 +4251,7 @@ msgid ""
|
||||
"that handles GRE/VXLAN project networks."
|
||||
msgstr ""
|
||||
|
||||
#: ../adv_config_ipv6.rst:476
|
||||
#: ../adv_config_ipv6.rst:487
|
||||
msgid "Requirements"
|
||||
msgstr ""
|
||||
|
||||
@ -5619,7 +5644,7 @@ msgid ""
|
||||
"architecture does not support project (private) networks."
|
||||
msgstr ""
|
||||
|
||||
#: ../adv_config_ipv6.rst:548
|
||||
#: ../adv_config_ipv6.rst:559
|
||||
msgid ""
|
||||
"The above is all you need in this scenario, but more information on "
|
||||
"installing, configuring, and running Dibbler is available in the Dibbler "
|
||||
@ -5874,7 +5899,7 @@ msgid ""
|
||||
"groups, QoS, and ARP spoofing filtering."
|
||||
msgstr ""
|
||||
|
||||
#: ../adv_config_ipv6.rst:663
|
||||
#: ../adv_config_ipv6.rst:674
|
||||
msgid ""
|
||||
"The following link provides a great step by step tutorial on setting up IPv6 "
|
||||
"with OpenStack: http://www.debug-all.com/?p=52"
|
||||
@ -6207,7 +6232,7 @@ msgid ""
|
||||
"port number. These types of ports are referred to as *ephemeral ports*."
|
||||
msgstr ""
|
||||
|
||||
#: ../adv_config_ipv6.rst:510
|
||||
#: ../adv_config_ipv6.rst:521
|
||||
msgid "The options used in the configuration file above are:"
|
||||
msgstr ""
|
||||
|
||||
@ -6306,7 +6331,7 @@ msgstr ""
|
||||
msgid "The physical tunnel interface forwards the packet to the network node."
|
||||
msgstr ""
|
||||
|
||||
#: ../adv_config_ipv6.rst:624
|
||||
#: ../adv_config_ipv6.rst:635
|
||||
msgid ""
|
||||
"The prefix delegation mechanism then sends a request via the external "
|
||||
"network to your prefix delegation server, which replies with the delegated "
|
||||
@ -6433,7 +6458,7 @@ msgid ""
|
||||
"manufacturers. Currently the following manufactuers are known to work:"
|
||||
msgstr ""
|
||||
|
||||
#: ../adv_config_ipv6.rst:609
|
||||
#: ../adv_config_ipv6.rst:620
|
||||
msgid ""
|
||||
"The subnet is initially created with a temporary CIDR before one can be "
|
||||
"assigned by prefix delegation. Any number of subnets with this temporary "
|
||||
@ -6515,7 +6540,7 @@ msgid ""
|
||||
"``ipv6_gateway`` flag is not set."
|
||||
msgstr ""
|
||||
|
||||
#: ../adv_config_ipv6.rst:540
|
||||
#: ../adv_config_ipv6.rst:551
|
||||
msgid "The variables used in the script file above are:"
|
||||
msgstr ""
|
||||
|
||||
@ -6661,7 +6686,7 @@ msgid ""
|
||||
"Service"
|
||||
msgstr ""
|
||||
|
||||
#: ../adv_config_ipv6.rst:489
|
||||
#: ../adv_config_ipv6.rst:500
|
||||
msgid ""
|
||||
"This guide assumes that you are running a Dibbler server on the network node "
|
||||
"where the external network bridge exists. If you already have a prefix "
|
||||
@ -6797,7 +6822,7 @@ msgid ""
|
||||
"both Networking and Compute."
|
||||
msgstr ""
|
||||
|
||||
#: ../adv_config_ipv6.rst:471
|
||||
#: ../adv_config_ipv6.rst:482
|
||||
msgid ""
|
||||
"This tells OpenStack Networking to use the prefix delegation mechanism for "
|
||||
"subnet allocation when the user does not provide a CIDR or subnet pool id "
|
||||
@ -6823,6 +6848,13 @@ msgstr ""
|
||||
msgid "To activate the network afer it has been deactivated::"
|
||||
msgstr ""
|
||||
|
||||
#: ../adv_config_ipv6.rst:689
|
||||
msgid ""
|
||||
"To allow the neutron-pd-agent to communicate with prefix delegation servers, "
|
||||
"you must set which network interface to use for external communication. In "
|
||||
"DevStack the default for this is br-ex::"
|
||||
msgstr ""
|
||||
|
||||
#: ../intro_basic_networking.rst:157
|
||||
msgid ""
|
||||
"To calculate the network number of an IP address, you must know the "
|
||||
@ -6877,6 +6909,12 @@ msgstr ""
|
||||
msgid "To enable prefix delegation, edit the :file:`etc/neutron.conf` file::"
|
||||
msgstr ""
|
||||
|
||||
#: ../adv_config_ipv6.rst:684
|
||||
msgid ""
|
||||
"To enable the driver for the dhcpv6_pd_agent, set pd_dhcp_driver to this in :"
|
||||
"file:`etc/neutron.conf`::"
|
||||
msgstr ""
|
||||
|
||||
#: ../scenario_legacy_ovs.rst:87
|
||||
msgid ""
|
||||
"To improve understanding of network traffic flow, the network and compute "
|
||||
@ -6921,7 +6959,7 @@ msgstr ""
|
||||
msgid "To prevent the network from automatically starting on boot::"
|
||||
msgstr ""
|
||||
|
||||
#: ../adv_config_ipv6.rst:524
|
||||
#: ../adv_config_ipv6.rst:535
|
||||
msgid ""
|
||||
"To provide external network access to your instances, your Dibbler server "
|
||||
"also needs to create new routes for each delegated prefix. This is done "
|
||||
@ -6937,11 +6975,11 @@ msgid ""
|
||||
"command::"
|
||||
msgstr ""
|
||||
|
||||
#: ../adv_config_ipv6.rst:552
|
||||
#: ../adv_config_ipv6.rst:563
|
||||
msgid "To start your Dibbler server, run::"
|
||||
msgstr ""
|
||||
|
||||
#: ../adv_config_ipv6.rst:614
|
||||
#: ../adv_config_ipv6.rst:625
|
||||
msgid ""
|
||||
"To trigger the prefix delegation process, create a router interface between "
|
||||
"this subnet and a router with an active interface on the external network:"
|
||||
@ -6972,7 +7010,7 @@ msgid ""
|
||||
"VLANs."
|
||||
msgstr ""
|
||||
|
||||
#: ../adv_config_ipv6.rst:478
|
||||
#: ../adv_config_ipv6.rst:489
|
||||
msgid ""
|
||||
"To use this feature, you need a prefix delegation capable DHCPv6 server that "
|
||||
"is reachable from your OpenStack Networking node(s). This could be software "
|
||||
@ -7087,7 +7125,7 @@ msgid ""
|
||||
"scenario in your environment."
|
||||
msgstr ""
|
||||
|
||||
#: ../adv_config_ipv6.rst:565
|
||||
#: ../adv_config_ipv6.rst:576
|
||||
msgid "User workflow"
|
||||
msgstr ""
|
||||
|
||||
@ -7304,7 +7342,7 @@ msgid ""
|
||||
"protocol were carried out for the instance in question."
|
||||
msgstr ""
|
||||
|
||||
#: ../adv_config_ipv6.rst:560
|
||||
#: ../adv_config_ipv6.rst:571
|
||||
msgid ""
|
||||
"When using DevStack, it is important to start your server after the :file:"
|
||||
"`stack.sh` script has finished to ensure that the required network "
|
||||
@ -7321,7 +7359,7 @@ msgid ""
|
||||
"and ``ipv6_address_mode`` are as follows."
|
||||
msgstr ""
|
||||
|
||||
#: ../adv_config_ipv6.rst:485
|
||||
#: ../adv_config_ipv6.rst:496
|
||||
msgid ""
|
||||
"When using the reference implementation of the OpenStack Networking prefix "
|
||||
"delegation driver, Dibbler must also be installed on your OpenStack "
|
||||
|
||||
Loading…
Reference in New Issue
Block a user