Imported Translations from Transifex
Change-Id: Ie77a3113238d8a93fec25fd65e92599cf805e19e
This commit is contained in:
OpenStack Proposal Bot
parent
a16447c990
commit
718f0acce1
@ -1,7 +1,7 @@
|
||||
msgid ""
|
||||
msgstr ""
|
||||
"Project-Id-Version: PACKAGE VERSION\n"
|
||||
"POT-Creation-Date: 2014-08-15 06:09+0000\n"
|
||||
"POT-Creation-Date: 2014-08-16 06:08+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"
|
||||
@ -254,7 +254,7 @@ msgid "Similarly, the degree to which the architecture is OpenStack-based will h
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/ch_hybrid.xml:61(para)
|
||||
msgid "There are commercially available options, such as Rightscale, and open source options, such as ManageIQ (http://manageiq.org/), but there is no single CMP that can address all needs in all scenarios. Whereas most of the sections of this book talk about the aspects of OpenStack, an architect needs to consider when designing an OpenStack architecture. This section will also discuss the things the architect must address when choosing or building a CMP to run a hybrid cloud design, even if the CMP will be a manually built solution."
|
||||
msgid "There are commercially available options, such as Rightscale, and open source options, such as ManageIQ (<link href=\"http://manageiq.org/\">http://manageiq.org</link>), but there is no single CMP that can address all needs in all scenarios. Whereas most of the sections of this book talk about the aspects of OpenStack, an architect needs to consider when designing an OpenStack architecture. This section will also discuss the things the architect must address when choosing or building a CMP to run a hybrid cloud design, even if the CMP will be a manually built solution."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/ch_multi_site.xml:7(title)
|
||||
@ -731,7 +731,7 @@ msgstr ""
|
||||
msgid "For the Block Storage service, the most important decisions are the selection of the storage technology and whether or not a dedicated network is used to carry storage traffic from the storage service to the compute nodes."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/multi_site/section_architecture_multi_site.xml:86(title) ./doc/arch-design/compute_focus/section_tech_considerations_compute_focus.xml:416(para)
|
||||
#: ./doc/arch-design/multi_site/section_architecture_multi_site.xml:86(title) ./doc/arch-design/compute_focus/section_tech_considerations_compute_focus.xml:417(para)
|
||||
msgid "Networking"
|
||||
msgstr ""
|
||||
|
||||
@ -751,7 +751,7 @@ msgstr ""
|
||||
msgid "Networking decisions include the encapsulation mechanism that will be used for the tenant networks, how large the broadcast domains should be, and the contracted SLAs for the interconnects."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/multi_site/section_user_requirements_multi_site.xml:8(title) ./doc/arch-design/network_focus/section_user_requirements_network_focus.xml:8(title) ./doc/arch-design/generalpurpose/section_user_requirements_general_purpose.xml:8(title) ./doc/arch-design/compute_focus/section_user_requirements_compute_focus.xml:12(title) ./doc/arch-design/hybrid/section_user_requirements_hybrid.xml:8(title) ./doc/arch-design/massively_scalable/section_user_requirements_massively_scalable.xml:8(title) ./doc/arch-design/massively_scalable/section_user_requirements_massively_scalable.xml:52(title) ./doc/arch-design/storage_focus/section_user_requirements_storage_focus.xml:8(title)
|
||||
#: ./doc/arch-design/multi_site/section_user_requirements_multi_site.xml:8(title) ./doc/arch-design/network_focus/section_user_requirements_network_focus.xml:8(title) ./doc/arch-design/generalpurpose/section_user_requirements_general_purpose.xml:8(title) ./doc/arch-design/generalpurpose/section_tech_considerations_general_purpose.xml:328(term) ./doc/arch-design/compute_focus/section_user_requirements_compute_focus.xml:12(title) ./doc/arch-design/hybrid/section_user_requirements_hybrid.xml:8(title) ./doc/arch-design/massively_scalable/section_user_requirements_massively_scalable.xml:8(title) ./doc/arch-design/massively_scalable/section_user_requirements_massively_scalable.xml:52(title) ./doc/arch-design/storage_focus/section_user_requirements_storage_focus.xml:8(title)
|
||||
msgid "User requirements"
|
||||
msgstr ""
|
||||
|
||||
@ -759,19 +759,19 @@ msgstr ""
|
||||
msgid "A multi-site architecture is complex and has its own risks and considerations, therefore it is important to make sure when contemplating the design such an architecture that it meets the user and business requirements."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/multi_site/section_user_requirements_multi_site.xml:13(para) ./doc/arch-design/network_focus/section_user_requirements_network_focus.xml:42(para) ./doc/arch-design/generalpurpose/section_user_requirements_general_purpose.xml:88(para) ./doc/arch-design/compute_focus/section_user_requirements_compute_focus.xml:55(para) ./doc/arch-design/hybrid/section_user_requirements_hybrid.xml:83(para) ./doc/arch-design/massively_scalable/section_user_requirements_massively_scalable.xml:17(para) ./doc/arch-design/storage_focus/section_user_requirements_storage_focus.xml:42(para)
|
||||
#: ./doc/arch-design/multi_site/section_user_requirements_multi_site.xml:13(para) ./doc/arch-design/network_focus/section_user_requirements_network_focus.xml:42(para) ./doc/arch-design/generalpurpose/section_user_requirements_general_purpose.xml:89(para) ./doc/arch-design/compute_focus/section_user_requirements_compute_focus.xml:55(para) ./doc/arch-design/hybrid/section_user_requirements_hybrid.xml:83(para) ./doc/arch-design/massively_scalable/section_user_requirements_massively_scalable.xml:17(para) ./doc/arch-design/storage_focus/section_user_requirements_storage_focus.xml:42(para)
|
||||
msgid "Many jurisdictions have legislative and regulatory requirements governing the storage and management of data in cloud environments. Common areas of regulation include:"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/multi_site/section_user_requirements_multi_site.xml:18(para) ./doc/arch-design/network_focus/section_user_requirements_network_focus.xml:47(para) ./doc/arch-design/generalpurpose/section_user_requirements_general_purpose.xml:93(para) ./doc/arch-design/compute_focus/section_user_requirements_compute_focus.xml:60(para) ./doc/arch-design/hybrid/section_user_requirements_hybrid.xml:88(para) ./doc/arch-design/massively_scalable/section_user_requirements_massively_scalable.xml:22(para)
|
||||
#: ./doc/arch-design/multi_site/section_user_requirements_multi_site.xml:18(para) ./doc/arch-design/network_focus/section_user_requirements_network_focus.xml:47(para) ./doc/arch-design/generalpurpose/section_user_requirements_general_purpose.xml:94(para) ./doc/arch-design/compute_focus/section_user_requirements_compute_focus.xml:60(para) ./doc/arch-design/hybrid/section_user_requirements_hybrid.xml:88(para) ./doc/arch-design/massively_scalable/section_user_requirements_massively_scalable.xml:22(para)
|
||||
msgid "Data retention policies ensuring storage of persistent data and records management to meet data archival requirements."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/multi_site/section_user_requirements_multi_site.xml:23(para) ./doc/arch-design/network_focus/section_user_requirements_network_focus.xml:52(para) ./doc/arch-design/generalpurpose/section_user_requirements_general_purpose.xml:98(para) ./doc/arch-design/compute_focus/section_user_requirements_compute_focus.xml:65(para) ./doc/arch-design/hybrid/section_user_requirements_hybrid.xml:93(para) ./doc/arch-design/massively_scalable/section_user_requirements_massively_scalable.xml:27(para)
|
||||
#: ./doc/arch-design/multi_site/section_user_requirements_multi_site.xml:23(para) ./doc/arch-design/network_focus/section_user_requirements_network_focus.xml:52(para) ./doc/arch-design/generalpurpose/section_user_requirements_general_purpose.xml:99(para) ./doc/arch-design/compute_focus/section_user_requirements_compute_focus.xml:65(para) ./doc/arch-design/hybrid/section_user_requirements_hybrid.xml:93(para) ./doc/arch-design/massively_scalable/section_user_requirements_massively_scalable.xml:27(para)
|
||||
msgid "Data ownership policies governing the possession and responsibility for data."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/multi_site/section_user_requirements_multi_site.xml:27(para) ./doc/arch-design/network_focus/section_user_requirements_network_focus.xml:56(para) ./doc/arch-design/generalpurpose/section_user_requirements_general_purpose.xml:102(para) ./doc/arch-design/compute_focus/section_user_requirements_compute_focus.xml:69(para) ./doc/arch-design/hybrid/section_user_requirements_hybrid.xml:97(para) ./doc/arch-design/massively_scalable/section_user_requirements_massively_scalable.xml:31(para)
|
||||
#: ./doc/arch-design/multi_site/section_user_requirements_multi_site.xml:27(para) ./doc/arch-design/network_focus/section_user_requirements_network_focus.xml:56(para) ./doc/arch-design/generalpurpose/section_user_requirements_general_purpose.xml:103(para) ./doc/arch-design/compute_focus/section_user_requirements_compute_focus.xml:69(para) ./doc/arch-design/hybrid/section_user_requirements_hybrid.xml:97(para) ./doc/arch-design/massively_scalable/section_user_requirements_massively_scalable.xml:31(para)
|
||||
msgid "Data sovereignty policies governing the storage of data in foreign countries or otherwise separate jurisdictions."
|
||||
msgstr ""
|
||||
|
||||
@ -847,7 +847,7 @@ msgstr ""
|
||||
msgid "Some applications are tolerant of the lack of synchronized object storage, while others may need those objects to be replicated and available across regions. Understanding of how the cloud implementation impacts new and existing applications is important for risk mitigation and the overall success of a cloud project. Applications may have to be written to expect an infrastructure with little to no redundancy. Existing applications not developed with the cloud in mind may need to be rewritten."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/multi_site/section_user_requirements_multi_site.xml:139(title) ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:72(term) ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:234(term) ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:637(term) ./doc/arch-design/generalpurpose/section_user_requirements_general_purpose.xml:24(term) ./doc/arch-design/compute_focus/section_user_requirements_compute_focus.xml:20(term) ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:55(term) ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:174(term) ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:396(term) ./doc/arch-design/hybrid/section_user_requirements_hybrid.xml:19(term) ./doc/arch-design/storage_focus/section_architecture_storage_focus.xml:16(para) ./doc/arch-design/storage_focus/section_architecture_storage_focus.xml:40(term) ./doc/arch-design/storage_focus/section_architecture_storage_focus.xml:184(term) ./doc/arch-design/storage_focus/section_architecture_storage_focus.xml:417(term) ./doc/arch-design/storage_focus/section_user_requirements_storage_focus.xml:16(term)
|
||||
#: ./doc/arch-design/multi_site/section_user_requirements_multi_site.xml:139(title) ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:72(term) ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:234(term) ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:637(term) ./doc/arch-design/generalpurpose/section_user_requirements_general_purpose.xml:25(term) ./doc/arch-design/compute_focus/section_user_requirements_compute_focus.xml:20(term) ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:55(term) ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:174(term) ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:396(term) ./doc/arch-design/hybrid/section_user_requirements_hybrid.xml:19(term) ./doc/arch-design/storage_focus/section_architecture_storage_focus.xml:16(para) ./doc/arch-design/storage_focus/section_architecture_storage_focus.xml:40(term) ./doc/arch-design/storage_focus/section_architecture_storage_focus.xml:184(term) ./doc/arch-design/storage_focus/section_architecture_storage_focus.xml:417(term) ./doc/arch-design/storage_focus/section_user_requirements_storage_focus.xml:16(term)
|
||||
msgid "Cost"
|
||||
msgstr ""
|
||||
|
||||
@ -867,7 +867,7 @@ msgstr ""
|
||||
msgid "Replication"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/multi_site/section_user_requirements_multi_site.xml:158(para) ./doc/arch-design/generalpurpose/section_tech_considerations_general_purpose.xml:666(para) ./doc/arch-design/compute_focus/section_tech_considerations_compute_focus.xml:286(para) ./doc/arch-design/hybrid/section_tech_considerations_hybrid.xml:126(para)
|
||||
#: ./doc/arch-design/multi_site/section_user_requirements_multi_site.xml:158(para) ./doc/arch-design/generalpurpose/section_tech_considerations_general_purpose.xml:685(para) ./doc/arch-design/compute_focus/section_tech_considerations_compute_focus.xml:286(para) ./doc/arch-design/hybrid/section_tech_considerations_hybrid.xml:126(para)
|
||||
msgid "Management"
|
||||
msgstr ""
|
||||
|
||||
@ -1121,7 +1121,7 @@ msgstr ""
|
||||
msgid "Depending on the storage model chosen during site design, storage replication and availability will also be a concern for end-users. If an application is capable of understanding regions, then it is possible to keep the object storage system separated by region. In this case, users who want to have an object available to more than one region will need to do the cross-site replication themselves. With a centralized swift proxy, however, the user may need to benchmark the replication timing of the Object Storage back end. Benchmarking allows the operational staff to provide users with an understanding of the amount of time required for a stored or modified object to become available to the entire environment."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/multi_site/section_tech_considerations_multi_site.xml:114(title) ./doc/arch-design/network_focus/section_tech_considerations_network_focus.xml:412(title) ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:249(term) ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:420(term) ./doc/arch-design/generalpurpose/section_user_requirements_general_purpose.xml:130(term) ./doc/arch-design/generalpurpose/section_tech_considerations_general_purpose.xml:474(title) ./doc/arch-design/compute_focus/section_user_requirements_compute_focus.xml:96(term) ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:182(term) ./doc/arch-design/compute_focus/section_tech_considerations_compute_focus.xml:257(title) ./doc/arch-design/hybrid/section_tech_considerations_hybrid.xml:253(title) ./doc/arch-design/storage_focus/section_architecture_storage_focus.xml:19(para) ./doc/arch-design/storage_focus/section_architecture_storage_focus.xml:48(term) ./doc/arch-design/storage_focus/section_user_requirements_storage_focus.xml:105(term)
|
||||
#: ./doc/arch-design/multi_site/section_tech_considerations_multi_site.xml:114(title) ./doc/arch-design/network_focus/section_tech_considerations_network_focus.xml:412(title) ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:249(term) ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:420(term) ./doc/arch-design/generalpurpose/section_user_requirements_general_purpose.xml:131(term) ./doc/arch-design/generalpurpose/section_tech_considerations_general_purpose.xml:493(title) ./doc/arch-design/compute_focus/section_user_requirements_compute_focus.xml:96(term) ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:182(term) ./doc/arch-design/compute_focus/section_tech_considerations_compute_focus.xml:257(title) ./doc/arch-design/hybrid/section_tech_considerations_hybrid.xml:253(title) ./doc/arch-design/storage_focus/section_architecture_storage_focus.xml:19(para) ./doc/arch-design/storage_focus/section_architecture_storage_focus.xml:48(term) ./doc/arch-design/storage_focus/section_user_requirements_storage_focus.xml:105(term)
|
||||
msgid "Performance"
|
||||
msgstr ""
|
||||
|
||||
@ -1137,7 +1137,7 @@ msgstr ""
|
||||
msgid "Storage availability can also be impacted by the architecture of a multi-site deployment. A centralized Object Storage service requires more time for an object to be available to instances locally in regions where the object was not created. Some applications may need to be tuned to account for this effect. Block Storage does not currently have a method for replicating data across multiple regions, so applications that depend on available block storage will need to manually cope with this limitation by creating duplicate block storage entries in each region."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/multi_site/section_tech_considerations_multi_site.xml:139(title) ./doc/arch-design/network_focus/section_user_requirements_network_focus.xml:163(title) ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:686(term) ./doc/arch-design/generalpurpose/section_user_requirements_general_purpose.xml:199(term) ./doc/arch-design/generalpurpose/section_tech_considerations_general_purpose.xml:652(title) ./doc/arch-design/compute_focus/section_user_requirements_compute_focus.xml:160(term) ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:440(term) ./doc/arch-design/compute_focus/section_tech_considerations_compute_focus.xml:268(title) ./doc/arch-design/hybrid/section_tech_considerations_hybrid.xml:107(title) ./doc/arch-design/storage_focus/section_tech_considerations_storage_focus.xml:50(term) ./doc/arch-design/storage_focus/section_architecture_storage_focus.xml:471(term) ./doc/arch-design/storage_focus/section_user_requirements_storage_focus.xml:123(term)
|
||||
#: ./doc/arch-design/multi_site/section_tech_considerations_multi_site.xml:139(title) ./doc/arch-design/network_focus/section_user_requirements_network_focus.xml:163(title) ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:686(term) ./doc/arch-design/generalpurpose/section_user_requirements_general_purpose.xml:200(term) ./doc/arch-design/generalpurpose/section_tech_considerations_general_purpose.xml:671(title) ./doc/arch-design/compute_focus/section_user_requirements_compute_focus.xml:160(term) ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:440(term) ./doc/arch-design/compute_focus/section_tech_considerations_compute_focus.xml:268(title) ./doc/arch-design/hybrid/section_tech_considerations_hybrid.xml:107(title) ./doc/arch-design/storage_focus/section_tech_considerations_storage_focus.xml:50(term) ./doc/arch-design/storage_focus/section_architecture_storage_focus.xml:471(term) ./doc/arch-design/storage_focus/section_user_requirements_storage_focus.xml:123(term)
|
||||
msgid "Security"
|
||||
msgstr ""
|
||||
|
||||
@ -1153,7 +1153,7 @@ msgstr ""
|
||||
msgid "Just as tenants in a single-site deployment need isolation from each other, so do tenants in multi-site installations. The extra challenges in multi-site designs revolve around ensuring that tenant networks function across regions. Unfortunately, OpenStack Networking does not presently support a mechanism to provide this functionality, therefore an external system may be necessary to manage these mappings. Tenant networks may contain sensitive information requiring that this mapping be accurate and consistent to ensure that a tenant in one site does not connect to a different tenant in another site."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/multi_site/section_tech_considerations_multi_site.xml:169(title) ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:611(para) ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:727(title) ./doc/arch-design/generalpurpose/section_tech_considerations_general_purpose.xml:404(title) ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:371(para) ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:477(title) ./doc/arch-design/compute_focus/section_tech_considerations_compute_focus.xml:360(title) ./doc/arch-design/storage_focus/section_architecture_storage_focus.xml:394(para) ./doc/arch-design/storage_focus/section_architecture_storage_focus.xml:512(title)
|
||||
#: ./doc/arch-design/multi_site/section_tech_considerations_multi_site.xml:169(title) ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:611(para) ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:727(title) ./doc/arch-design/generalpurpose/section_tech_considerations_general_purpose.xml:414(title) ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:371(para) ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:477(title) ./doc/arch-design/compute_focus/section_tech_considerations_compute_focus.xml:360(title) ./doc/arch-design/storage_focus/section_architecture_storage_focus.xml:394(para) ./doc/arch-design/storage_focus/section_architecture_storage_focus.xml:512(title)
|
||||
msgid "OpenStack components"
|
||||
msgstr ""
|
||||
|
||||
@ -2145,7 +2145,7 @@ msgstr ""
|
||||
msgid "The chosen 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:582(term) ./doc/arch-design/generalpurpose/section_tech_considerations_general_purpose.xml:569(title) ./doc/arch-design/storage_focus/section_user_requirements_storage_focus.xml:113(term)
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:582(term) ./doc/arch-design/generalpurpose/section_tech_considerations_general_purpose.xml:588(title) ./doc/arch-design/storage_focus/section_user_requirements_storage_focus.xml:113(term)
|
||||
msgid "Availability"
|
||||
msgstr ""
|
||||
|
||||
@ -2165,7 +2165,7 @@ msgstr ""
|
||||
msgid "Operating system (OS) and hypervisor"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:614(para) ./doc/arch-design/generalpurpose/section_tech_considerations_general_purpose.xml:435(title) ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:374(para) ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:529(title) ./doc/arch-design/storage_focus/section_architecture_storage_focus.xml:397(para) ./doc/arch-design/storage_focus/section_architecture_storage_focus.xml:562(title)
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:614(para) ./doc/arch-design/generalpurpose/section_tech_considerations_general_purpose.xml:454(title) ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:374(para) ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:529(title) ./doc/arch-design/storage_focus/section_architecture_storage_focus.xml:397(para) ./doc/arch-design/storage_focus/section_architecture_storage_focus.xml:562(title)
|
||||
msgid "Supplemental software"
|
||||
msgstr ""
|
||||
|
||||
@ -2209,7 +2209,7 @@ msgstr ""
|
||||
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:688(para)
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:688(para) ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:442(para)
|
||||
msgid "Ensure that 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 will have an impact on performance and the patch installation process could affect maintenance windows."
|
||||
msgstr ""
|
||||
|
||||
@ -2221,7 +2221,7 @@ msgstr ""
|
||||
msgid "Determine which features of OpenStack are required. This will often determine the selection of the OS-hypervisor combination. Certain features are only available with specific OSs or hypervisors. For example, if certain features are not available, the design might need to be modified to meet the user requirements."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:710(term) ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:462(term) ./doc/arch-design/storage_focus/section_architecture_storage_focus.xml:495(term)
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:710(term) ./doc/arch-design/generalpurpose/section_tech_considerations_general_purpose.xml:343(term) ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:462(term) ./doc/arch-design/storage_focus/section_architecture_storage_focus.xml:495(term)
|
||||
msgid "Interoperability"
|
||||
msgstr ""
|
||||
|
||||
@ -2230,186 +2230,186 @@ msgid "Consideration should be given to the ability of the selected OS-hyperviso
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:728(para)
|
||||
msgid "The selection of which OpenStack components are included has a significant impact on the overall design. While there are certain components that will always be present, (Compute and Image Service, for example) there are other services that may not be required. As an example, a certain design might not need Orchestration. Omitting Orchestration would not have a significant impact on the overall design of a cloud; however, if the architecture uses a replacement for OpenStack Object Storage for its storage component, it could potentially have significant impacts on the rest of the design."
|
||||
msgid "The selection of which OpenStack components are included has a significant impact on the overall design. While there are certain components that will always be present, (Compute and Image Service, for example) there are other services that may not be required. As an example, a certain design might not need <glossterm>Orchestration</glossterm>. Omitting Orchestration would not have a significant impact on the overall design of a cloud; however, if the architecture uses a replacement for OpenStack Object Storage for its storage component, it could potentially have significant impacts on the rest of the design."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:738(para)
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:739(para)
|
||||
msgid "The exclusion of certain OpenStack components might also limit or constrain the functionality of other components. If the architecture includes Orchestration but excludes Telemetry, then the design will not be able to take advantage of Orchestrations' auto scaling functionality (which relies on information from Telemetry). It is important to research the component interdependencies in conjunction with the technical requirements before deciding what components need to be included and what components can be dropped from the final architecture."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:750(title)
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:751(title)
|
||||
msgid "Supplemental components"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:751(para)
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:752(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:757(title) ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:535(title) ./doc/arch-design/storage_focus/section_architecture_storage_focus.xml:568(title)
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:758(title) ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:535(title) ./doc/arch-design/storage_focus/section_architecture_storage_focus.xml:568(title)
|
||||
msgid "Networking software"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:758(para)
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:759(para)
|
||||
msgid "OpenStack Networking provides a wide variety of networking services for instances. There are many additional networking software packages that might be useful to manage the OpenStack components themselves. Some examples include software to provide load balancing, network redundancy protocols, and routing daemons. Some of these software packages are described in more detail in the <citetitle>OpenStack High Availability Guide</citetitle> (refer to the <link href=\"http://docs.openstack.org/high-availability-guide/content/ch-network.html\">Network controller cluster stack chapter</link> of the OpenStack High Availability Guide)."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:769(para)
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:770(para)
|
||||
msgid "For a general purpose OpenStack cloud, the OpenStack infrastructure components will 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:776(title) ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:551(title) ./doc/arch-design/storage_focus/section_architecture_storage_focus.xml:585(title)
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:777(title) ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:551(title) ./doc/arch-design/storage_focus/section_architecture_storage_focus.xml:585(title)
|
||||
msgid "Management software"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:777(para) ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:552(para)
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:778(para) ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:552(para)
|
||||
msgid "The 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:781(para)
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:782(para)
|
||||
msgid "Inclusion of clustering software, such as Corosync or Pacemaker, is determined primarily by the availability requirements. Therefore, the impact of including (or not including) these software packages is primarily determined by the availability of the cloud infrastructure and the complexity of supporting the configuration after it is deployed. The <link href=\"http://docs.openstack.org/high-availability-guide/\"><citetitle>OpenStack High Availability Guide</citetitle></link> provides more details on the installation and configuration of Corosync and Pacemaker, should these packages need to be included in the design."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:792(para)
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:793(para)
|
||||
msgid "Requirements for logging, monitoring, and alerting are determined by operational considerations. Each of these sub-categories includes a number of various options. For example, in the logging sub-category one might consider Logstash, Splunk, instanceware Log Insight, or some other log aggregation-consolidation tool. Logs should be stored in a centralized location to make it easier to perform analytics against the data. Log data analytics engines can also provide automation and issue notification by providing a mechanism to both alert and automatically attempt to remediate some of the more commonly known issues."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:803(para)
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:804(para)
|
||||
msgid "If any of these software packages are required, then the design must account for the additional resource consumption (CPU, RAM, storage, and network bandwidth for a log aggregation solution, for example). Some other potential design impacts include:"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:810(para) ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:578(para)
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:811(para) ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:578(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:815(para) ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:583(para) ./doc/arch-design/storage_focus/section_architecture_storage_focus.xml:625(para)
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:816(para) ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:583(para) ./doc/arch-design/storage_focus/section_architecture_storage_focus.xml:625(para)
|
||||
msgid "Network hardware: The network hardware selection needs to be supported by the logging, monitoring, and alerting software."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:822(title) ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:589(title) ./doc/arch-design/storage_focus/section_architecture_storage_focus.xml:631(title)
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:823(title) ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:589(title) ./doc/arch-design/storage_focus/section_architecture_storage_focus.xml:631(title)
|
||||
msgid "Database software"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:823(para)
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:824(para)
|
||||
msgid "A large majority of the OpenStack components require access to back-end database services to store state and configuration information. Selection of an appropriate back-end database that will satisfy the availability and fault tolerance requirements of the OpenStack services is required. OpenStack services supports connecting to any database that is supported by the SQLAlchemy python drivers, however, most common database deployments make use of MySQL or variations of it. It is recommended 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. Some of the more common software solutions used include Galera, MariaDB and MySQL with multi-master replication."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:839(title)
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:840(title)
|
||||
msgid "Addressing performance-sensitive workloads"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:840(para)
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:841(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, it is recommended to 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:852(title)
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:853(title)
|
||||
msgid "Compute-focused workloads"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:853(para)
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:854(para)
|
||||
msgid "In an OpenStack cloud that is compute-focused, there are some design choices that can help accommodate those workloads. Compute-focused workloads are generally those that would place a higher demand on CPU and memory resources with lower priority given to storage and network performance, other than what is required to support the intended compute workloads. 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:863(title)
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:864(title)
|
||||
msgid "Network-focused workloads"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:864(para)
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:865(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:872(title)
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:873(title)
|
||||
msgid "Storage-focused workloads"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:873(para)
|
||||
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:874(para)
|
||||
msgid "Storage focused OpenStack clouds need to be designed to accommodate workloads that have extreme demands on either object or block storage services that require specialized consideration and planning. For guidance on designing for this type of cloud, please refer to <xref linkend=\"storage_focus\"/>."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/generalpurpose/section_user_requirements_general_purpose.xml:9(para)
|
||||
msgid "The general purpose cloud is built following the Infrastructure-as-a-Service (IaaS) model; as a platform best suited for use cases with simple requirements. The general purpose cloud user requirements themselves are typically not complex. However, it is still important to capture them even if the project has minimum business and technical requirements such as a Proof of Concept (PoC) or a small lab platform."
|
||||
msgid "The general purpose cloud is built following the <glossterm baseform=\"IaaS\">Infrastructure-as-a-Service (IaaS)</glossterm> model; as a platform best suited for use cases with simple requirements. The general purpose cloud user requirements themselves are typically not complex. However, it is still important to capture them even if the project has minimum business and technical requirements such as a proof of concept (PoC) or a small lab platform."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/generalpurpose/section_user_requirements_general_purpose.xml:17(para)
|
||||
#: ./doc/arch-design/generalpurpose/section_user_requirements_general_purpose.xml:18(para)
|
||||
msgid "These user considerations are written from the perspective of the organization that is building the cloud, not from the perspective of the end-users who will consume cloud services provided by this design."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/generalpurpose/section_user_requirements_general_purpose.xml:26(para)
|
||||
#: ./doc/arch-design/generalpurpose/section_user_requirements_general_purpose.xml:27(para)
|
||||
msgid "Financial factors are a primary concern for any organization. Since general purpose clouds are considered the baseline from which all other cloud architecture environments derive, cost will commonly be an important criteria. This type of cloud, however, does not always provide the most cost-effective environment for a specialized application or situation. Unless razor-thin margins and costs have been mandated as a critical factor, cost should not be the sole consideration when choosing or designing a general purpose architecture."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/generalpurpose/section_user_requirements_general_purpose.xml:40(term) ./doc/arch-design/compute_focus/section_user_requirements_compute_focus.xml:31(term) ./doc/arch-design/hybrid/section_user_requirements_hybrid.xml:46(term)
|
||||
#: ./doc/arch-design/generalpurpose/section_user_requirements_general_purpose.xml:41(term) ./doc/arch-design/compute_focus/section_user_requirements_compute_focus.xml:31(term) ./doc/arch-design/hybrid/section_user_requirements_hybrid.xml:46(term)
|
||||
msgid "Time to market"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/generalpurpose/section_user_requirements_general_purpose.xml:42(para)
|
||||
#: ./doc/arch-design/generalpurpose/section_user_requirements_general_purpose.xml:43(para)
|
||||
msgid "Another common business factor in building a general purpose cloud is the ability to deliver a service or product more quickly and flexibly. In the modern hyper-fast business world, being able to deliver a product in six months instead of two years is often a major driving force behind the decision to build a general purpose cloud. General purpose clouds allow users to self-provision and gain access to compute, network, and storage resources on-demand thus decreasing time to market. It may potentially make more sense to build a general purpose PoC as opposed to waiting to finalize the ultimate use case for the system. The tradeoff with taking this approach is the risk that the general purpose cloud is not optimized for the actual final workloads. The final decision on which approach to take will be dependent on the specifics of the business objectives and time frame for the project."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/generalpurpose/section_user_requirements_general_purpose.xml:63(term) ./doc/arch-design/compute_focus/section_user_requirements_compute_focus.xml:40(term) ./doc/arch-design/hybrid/section_user_requirements_hybrid.xml:33(term)
|
||||
#: ./doc/arch-design/generalpurpose/section_user_requirements_general_purpose.xml:64(term) ./doc/arch-design/compute_focus/section_user_requirements_compute_focus.xml:40(term) ./doc/arch-design/hybrid/section_user_requirements_hybrid.xml:33(term)
|
||||
msgid "Revenue opportunity"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/generalpurpose/section_user_requirements_general_purpose.xml:65(para)
|
||||
#: ./doc/arch-design/generalpurpose/section_user_requirements_general_purpose.xml:66(para)
|
||||
msgid "The revenue opportunity for a given cloud will vary greatly based on the intended use case of that particular cloud. Some general purpose clouds are built for commercial customer facing products, but there are plenty of other reasons that might make the general purpose cloud the right choice. A small cloud service provider (CSP) might want to build a general purpose cloud rather than a massively scalable cloud because they do not have the deep financial resources needed, or because they do not or will not know in advance the purposes for which their customers are going to use the cloud. For some users, the advantages cloud itself offers mean an enhancement of revenue opportunity. For others, the fact that a general purpose cloud provides only baseline functionality will be a disincentive for use, leading to a potential stagnation of potential revenue opportunities."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/generalpurpose/section_user_requirements_general_purpose.xml:87(title) ./doc/arch-design/compute_focus/section_user_requirements_compute_focus.xml:54(title) ./doc/arch-design/hybrid/section_user_requirements_hybrid.xml:82(title) ./doc/arch-design/storage_focus/section_user_requirements_storage_focus.xml:30(term) ./doc/arch-design/storage_focus/section_user_requirements_storage_focus.xml:41(title)
|
||||
#: ./doc/arch-design/generalpurpose/section_user_requirements_general_purpose.xml:88(title) ./doc/arch-design/compute_focus/section_user_requirements_compute_focus.xml:54(title) ./doc/arch-design/hybrid/section_user_requirements_hybrid.xml:82(title) ./doc/arch-design/storage_focus/section_user_requirements_storage_focus.xml:30(term) ./doc/arch-design/storage_focus/section_user_requirements_storage_focus.xml:41(title)
|
||||
msgid "Legal requirements"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/generalpurpose/section_user_requirements_general_purpose.xml:107(para)
|
||||
#: ./doc/arch-design/generalpurpose/section_user_requirements_general_purpose.xml:108(para)
|
||||
msgid "Data compliance policies governing certain types of information need to reside in certain locations due to regular issues - and more important cannot reside in other locations for the same reason."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/generalpurpose/section_user_requirements_general_purpose.xml:113(para) ./doc/arch-design/compute_focus/section_user_requirements_compute_focus.xml:80(para) ./doc/arch-design/massively_scalable/section_user_requirements_massively_scalable.xml:42(para) ./doc/arch-design/storage_focus/section_user_requirements_storage_focus.xml:79(para)
|
||||
#: ./doc/arch-design/generalpurpose/section_user_requirements_general_purpose.xml:114(para) ./doc/arch-design/compute_focus/section_user_requirements_compute_focus.xml:80(para) ./doc/arch-design/massively_scalable/section_user_requirements_massively_scalable.xml:42(para) ./doc/arch-design/storage_focus/section_user_requirements_storage_focus.xml:79(para)
|
||||
msgid "Examples of such legal frameworks include the <link href=\"http://ec.europa.eu/justice/data-protection/\">data protection framework</link> of the European Union and the requirements of the <link href=\"http://www.finra.org/Industry/Regulation/FINRARules/\">Financial Industry Regulatory Authority</link> in the United States. Consult a local regulatory body for more information."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/generalpurpose/section_user_requirements_general_purpose.xml:124(title) ./doc/arch-design/storage_focus/section_user_requirements_storage_focus.xml:90(title)
|
||||
#: ./doc/arch-design/generalpurpose/section_user_requirements_general_purpose.xml:125(title) ./doc/arch-design/storage_focus/section_user_requirements_storage_focus.xml:90(title)
|
||||
msgid "Technical requirements"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/generalpurpose/section_user_requirements_general_purpose.xml:125(para)
|
||||
#: ./doc/arch-design/generalpurpose/section_user_requirements_general_purpose.xml:126(para)
|
||||
msgid "Technical cloud architecture requirements should be weighted against the business requirements."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/generalpurpose/section_user_requirements_general_purpose.xml:132(para)
|
||||
#: ./doc/arch-design/generalpurpose/section_user_requirements_general_purpose.xml:133(para)
|
||||
msgid "As a baseline product, general purpose clouds do not provide optimized performance for any particular function. While a general purpose cloud should provide enough performance to satisfy average user considerations, performance is not a general purpose cloud customer driver."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/generalpurpose/section_user_requirements_general_purpose.xml:141(term)
|
||||
#: ./doc/arch-design/generalpurpose/section_user_requirements_general_purpose.xml:142(term)
|
||||
msgid "No predefined usage model"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/generalpurpose/section_user_requirements_general_purpose.xml:143(para)
|
||||
#: ./doc/arch-design/generalpurpose/section_user_requirements_general_purpose.xml:144(para)
|
||||
msgid "The lack of a pre-defined usage model enables the user to run a wide variety of applications without having to know the application requirements in advance. This provides a degree of independence and flexibility that no other cloud scenarios are able to provide."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/generalpurpose/section_user_requirements_general_purpose.xml:152(term)
|
||||
#: ./doc/arch-design/generalpurpose/section_user_requirements_general_purpose.xml:153(term)
|
||||
msgid "On-demand and self-service application"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/generalpurpose/section_user_requirements_general_purpose.xml:154(para)
|
||||
#: ./doc/arch-design/generalpurpose/section_user_requirements_general_purpose.xml:155(para)
|
||||
msgid "By definition, a cloud provides end users with the ability to self-provision computing power, storage, networks, and software in a simple and flexible way. The user must be able to scale their resources up to a substantial level without disrupting the underlying host operations. One of the benefits of using a general purpose cloud architecture is the ability to start with limited resources and increase them over time as the user demand grows."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/generalpurpose/section_user_requirements_general_purpose.xml:167(term)
|
||||
#: ./doc/arch-design/generalpurpose/section_user_requirements_general_purpose.xml:168(term)
|
||||
msgid "Public cloud"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/generalpurpose/section_user_requirements_general_purpose.xml:169(para)
|
||||
#: ./doc/arch-design/generalpurpose/section_user_requirements_general_purpose.xml:170(para)
|
||||
msgid "For a company interested in building a commercial public cloud offering based on OpenStack, the general purpose architecture model might be the best choice because the designers are not going to know the purposes or workloads for which the end users will use the cloud."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/generalpurpose/section_user_requirements_general_purpose.xml:178(term)
|
||||
#: ./doc/arch-design/generalpurpose/section_user_requirements_general_purpose.xml:179(term)
|
||||
msgid "Internal consumption (private) cloud"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/generalpurpose/section_user_requirements_general_purpose.xml:180(para)
|
||||
#: ./doc/arch-design/generalpurpose/section_user_requirements_general_purpose.xml:181(para)
|
||||
msgid "Organizations need to determine if it makes the most sense to create their own clouds internally. The main advantage of a private cloud is that it allows the organization to maintain complete control over all the architecture and the cloud components. One caution is to think about the possibility that users will want to combine using the internal cloud with access to an external cloud. If that case is likely, it might be worth exploring the possibility of taking a multi-cloud approach with regard to at least some of the architectural elements. Designs that incorporate the use of multiple clouds, such as a private cloud and a public cloud offering, are described in the \"Multi-Cloud\" scenario, see <xref linkend=\"multi_site\"/>."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/generalpurpose/section_user_requirements_general_purpose.xml:201(para)
|
||||
#: ./doc/arch-design/generalpurpose/section_user_requirements_general_purpose.xml:202(para)
|
||||
msgid "Security should be implemented according to asset, threat, and vulnerability risk assessment matrices. For cloud domains that require increased computer security, network security, or information security, general purpose cloud is not considered an appropriate choice."
|
||||
msgstr ""
|
||||
|
||||
@ -2552,10 +2552,10 @@ msgid "In this scenario, additional capabilities can be realized by moving stati
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/generalpurpose/section_prescriptive_example_general_purpose.xml:89(para)
|
||||
msgid "There is also a potential to leverage the Orchestration and Telemetry modules to provide an auto-scaling, orchestrated web application environment. Defining the web applications in Heat Orchestration Templates (HOT) would negate the reliance on the scripted Puppet solution currently employed."
|
||||
msgid "There is also a potential to leverage the Orchestration and Telemetry modules to provide an auto-scaling, orchestrated web application environment. Defining the web applications in <glossterm baseform=\"Heat Orchestration Template (HOT)\">Heat Orchestration Templates (HOT)</glossterm> would negate the reliance on the scripted Puppet solution currently employed."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/generalpurpose/section_prescriptive_example_general_purpose.xml:95(para)
|
||||
#: ./doc/arch-design/generalpurpose/section_prescriptive_example_general_purpose.xml:97(para)
|
||||
msgid "OpenStack Networking can be used to control hardware load balancers through the use of plug-ins and the Networking API. This would allow a user to control hardware load balance pools and instances as members in these pools, but their use in production environments must be carefully weighed against current stability."
|
||||
msgstr ""
|
||||
|
||||
@ -2612,7 +2612,7 @@ msgid "An OpenStack cloud traditionally has multiple network segments, each of w
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/generalpurpose/section_tech_considerations_general_purpose.xml:130(para)
|
||||
msgid "Based on the requirements of instances being serviced in the cloud, the next design choice which will affect your design is the choice of network service which will be used to service instances in the cloud. The choice between legacy networking (nova-network), as a part of OpenStack Compute Service, and OpenStack Networking (neutron), has tremendous implications and will have a huge impact on the architecture and design of the cloud network infrastructure."
|
||||
msgid "Based on the requirements of instances being serviced in the cloud, the next design choice which will affect your design is the choice of network service which will be used to service instances in the cloud. The choice between legacy networking (nova-network), as a part of OpenStack Compute, and OpenStack Networking (neutron), has tremendous implications and will have a huge impact on the architecture and design of the cloud network infrastructure."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/generalpurpose/section_tech_considerations_general_purpose.xml:138(para)
|
||||
@ -2700,258 +2700,262 @@ msgid "Operating system (OS) selection plays a large role in the design and arch
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/generalpurpose/section_tech_considerations_general_purpose.xml:315(para)
|
||||
msgid "OS selection also directly influences hypervisor selection. A cloud architect who selects Ubuntu or RHEL has some flexibility in hypervisor; KVM, Xen, and LXC are supported virtualization methods available under OpenStack Compute (nova) on these Linux distributions. A cloud architect who selects Hyper-V, on the other hand, is limited to Windows Server. Similarly, a cloud architect who selects XenServer is limited to the CentOS-based dom0 operating system provided with XenServer."
|
||||
msgid "OS selection also directly influences hypervisor selection. A cloud architect who selects Ubuntu, RHEL, or SLES has some flexibility in hypervisor; KVM, Xen, and LXC are supported virtualization methods available under OpenStack Compute (nova) on these Linux distributions. A cloud architect who selects Hyper-V, on the other hand, is limited to Windows Server. Similarly, a cloud architect who selects XenServer is limited to the CentOS-based dom0 operating system provided with XenServer."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/generalpurpose/section_tech_considerations_general_purpose.xml:324(para)
|
||||
msgid "The primary factors that play into OS/hypervisor selection include:"
|
||||
msgid "The primary factors that play into OS-hypervisor selection include:"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/generalpurpose/section_tech_considerations_general_purpose.xml:328(para)
|
||||
msgid "User requirements: The selection of OS/hypervisor combination first and foremost needs to support the user requirements."
|
||||
#: ./doc/arch-design/generalpurpose/section_tech_considerations_general_purpose.xml:330(para)
|
||||
msgid "The selection of OS-hypervisor combination first and foremost needs to support the user requirements."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/generalpurpose/section_tech_considerations_general_purpose.xml:333(para)
|
||||
msgid "Support: The selected OS/hypervisor combination needs to be supported by OpenStack."
|
||||
#: ./doc/arch-design/generalpurpose/section_tech_considerations_general_purpose.xml:336(term)
|
||||
msgid "Support"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/generalpurpose/section_tech_considerations_general_purpose.xml:337(para)
|
||||
msgid "Interoperability: The OS/hypervisor needs to be interoperable with other features and services in the OpenStack design in order to meet the user requirements."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/generalpurpose/section_tech_considerations_general_purpose.xml:344(title) ./doc/arch-design/specialized/section_openstack_on_openstack_specialized.xml:37(title)
|
||||
msgid "Hypervisor"
|
||||
#: ./doc/arch-design/generalpurpose/section_tech_considerations_general_purpose.xml:338(para)
|
||||
msgid "The selected OS-hypervisor combination needs to be supported by OpenStack."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/generalpurpose/section_tech_considerations_general_purpose.xml:345(para)
|
||||
msgid "The OS-hypervisor needs to be interoperable with other features and services in the OpenStack design in order to meet the user requirements."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/generalpurpose/section_tech_considerations_general_purpose.xml:354(title) ./doc/arch-design/specialized/section_openstack_on_openstack_specialized.xml:37(title)
|
||||
msgid "Hypervisor"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/generalpurpose/section_tech_considerations_general_purpose.xml:355(para)
|
||||
msgid "OpenStack supports a wide variety of hypervisors, one or more of which can be used in a single cloud. These hypervisors include:"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/generalpurpose/section_tech_considerations_general_purpose.xml:350(para)
|
||||
msgid "KVM (and Qemu)"
|
||||
#: ./doc/arch-design/generalpurpose/section_tech_considerations_general_purpose.xml:360(para)
|
||||
msgid "KVM (and QEMU)"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/generalpurpose/section_tech_considerations_general_purpose.xml:353(para)
|
||||
#: ./doc/arch-design/generalpurpose/section_tech_considerations_general_purpose.xml:363(para)
|
||||
msgid "XCP/XenServer"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/generalpurpose/section_tech_considerations_general_purpose.xml:356(para)
|
||||
#: ./doc/arch-design/generalpurpose/section_tech_considerations_general_purpose.xml:366(para)
|
||||
msgid "vSphere (vCenter and ESXi)"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/generalpurpose/section_tech_considerations_general_purpose.xml:359(para)
|
||||
#: ./doc/arch-design/generalpurpose/section_tech_considerations_general_purpose.xml:369(para)
|
||||
msgid "Hyper-V"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/generalpurpose/section_tech_considerations_general_purpose.xml:362(para)
|
||||
#: ./doc/arch-design/generalpurpose/section_tech_considerations_general_purpose.xml:372(para)
|
||||
msgid "LXC"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/generalpurpose/section_tech_considerations_general_purpose.xml:365(para)
|
||||
#: ./doc/arch-design/generalpurpose/section_tech_considerations_general_purpose.xml:375(para)
|
||||
msgid "Docker"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/generalpurpose/section_tech_considerations_general_purpose.xml:368(para)
|
||||
#: ./doc/arch-design/generalpurpose/section_tech_considerations_general_purpose.xml:378(para)
|
||||
msgid "Bare-metal"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/generalpurpose/section_tech_considerations_general_purpose.xml:371(para)
|
||||
#: ./doc/arch-design/generalpurpose/section_tech_considerations_general_purpose.xml:381(para)
|
||||
msgid "A complete list of supported hypervisors and their capabilities can be found at <link href=\"https://wiki.openstack.org/wiki/HypervisorSupportMatrix\">https://wiki.openstack.org/wiki/HypervisorSupportMatrix</link>."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/generalpurpose/section_tech_considerations_general_purpose.xml:375(para)
|
||||
#: ./doc/arch-design/generalpurpose/section_tech_considerations_general_purpose.xml:385(para)
|
||||
msgid "General purpose clouds should make use of hypervisors that support the most general purpose use cases, such as KVM and Xen. More specific hypervisors should then be chosen to account for specific functionality or a supported feature requirement. In some cases, there may also be a mandated requirement to run software on a certified hypervisor including solutions from VMware, Microsoft, and Citrix."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/generalpurpose/section_tech_considerations_general_purpose.xml:382(para)
|
||||
#: ./doc/arch-design/generalpurpose/section_tech_considerations_general_purpose.xml:392(para)
|
||||
msgid "The features offered through the OpenStack cloud platform determine the best choice of a hypervisor. As an example, for a general purpose cloud that predominantly supports a Microsoft-based migration, or is managed by staff that has a particular skill for managing certain hypervisors and operating systems, Hyper-V might be the best available choice. While the decision to use Hyper-V does not limit the ability to run alternative operating systems, be mindful of those that are deemed supported. Each different hypervisor also has their own hardware requirements which may affect the decisions around designing a general purpose cloud. For example, to utilize the live migration feature of VMware, vMotion, this requires an installation of vCenter/vSphere and the use of the ESXi hypervisor, which increases the infrastructure requirements."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/generalpurpose/section_tech_considerations_general_purpose.xml:397(para)
|
||||
#: ./doc/arch-design/generalpurpose/section_tech_considerations_general_purpose.xml:407(para)
|
||||
msgid "In a mixed hypervisor environment, specific aggregates of compute resources, each with defined capabilities, enable workloads to utilize software and hardware specific to their particular requirements. This functionality can be exposed explicitly to the end user, or accessed through defined metadata within a particular flavor of an instance."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/generalpurpose/section_tech_considerations_general_purpose.xml:405(para)
|
||||
#: ./doc/arch-design/generalpurpose/section_tech_considerations_general_purpose.xml:415(para)
|
||||
msgid "A general purpose OpenStack cloud design should incorporate the core OpenStack services to provide a wide range of services to end-users. The OpenStack core services recommended in a general purpose cloud are:"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/generalpurpose/section_tech_considerations_general_purpose.xml:411(para) ./doc/arch-design/compute_focus/section_tech_considerations_compute_focus.xml:367(para)
|
||||
msgid "OpenStack Compute (nova)"
|
||||
#: ./doc/arch-design/generalpurpose/section_tech_considerations_general_purpose.xml:421(para)
|
||||
msgid "OpenStack <glossterm>Compute</glossterm> (<glossterm>nova</glossterm>)"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/generalpurpose/section_tech_considerations_general_purpose.xml:414(para)
|
||||
msgid "OpenStack Networking (neutron)"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/generalpurpose/section_tech_considerations_general_purpose.xml:417(para) ./doc/arch-design/compute_focus/section_tech_considerations_compute_focus.xml:370(para) ./doc/arch-design/storage_focus/section_architecture_storage_focus.xml:546(para)
|
||||
msgid "OpenStack Image Service (glance)"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/generalpurpose/section_tech_considerations_general_purpose.xml:420(para) ./doc/arch-design/compute_focus/section_tech_considerations_compute_focus.xml:373(para) ./doc/arch-design/storage_focus/section_architecture_storage_focus.xml:530(para)
|
||||
msgid "OpenStack Identity (keystone)"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/generalpurpose/section_tech_considerations_general_purpose.xml:423(para) ./doc/arch-design/storage_focus/section_architecture_storage_focus.xml:533(para)
|
||||
msgid "OpenStack dashboard (horizon)"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/generalpurpose/section_tech_considerations_general_purpose.xml:426(para) ./doc/arch-design/compute_focus/section_tech_considerations_compute_focus.xml:391(para)
|
||||
msgid "Telemetry module (ceilometer)"
|
||||
#: ./doc/arch-design/generalpurpose/section_tech_considerations_general_purpose.xml:425(para)
|
||||
msgid "OpenStack <glossterm>Networking</glossterm> (<glossterm>neutron</glossterm>)"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/generalpurpose/section_tech_considerations_general_purpose.xml:429(para)
|
||||
msgid "A general purpose cloud may also include OpenStack Object Storage (swift). OpenStack Block Storage (cinder) may be selected to provide persistent storage to applications and instances although, depending on the use case, this could be optional."
|
||||
msgid "OpenStack <glossterm>Image Service</glossterm> (<glossterm>glance</glossterm>)"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/generalpurpose/section_tech_considerations_general_purpose.xml:436(para)
|
||||
#: ./doc/arch-design/generalpurpose/section_tech_considerations_general_purpose.xml:433(para)
|
||||
msgid "OpenStack <glossterm>Identity</glossterm> (<glossterm>keystone</glossterm>)"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/generalpurpose/section_tech_considerations_general_purpose.xml:437(para)
|
||||
msgid "OpenStack <glossterm>dashboard</glossterm> (<glossterm>horizon</glossterm>)"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/generalpurpose/section_tech_considerations_general_purpose.xml:441(para)
|
||||
msgid "<glossterm>Telemetry</glossterm> module (<glossterm>ceilometer</glossterm>)"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/generalpurpose/section_tech_considerations_general_purpose.xml:445(para)
|
||||
msgid "A general purpose cloud may also include OpenStack <glossterm>Object Storage</glossterm> (<glossterm>swift</glossterm>). OpenStack <glossterm>Block Storage</glossterm> (<glossterm>cinder</glossterm>) may be selected to provide persistent storage to applications and instances although, depending on the use case, this could be optional."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/generalpurpose/section_tech_considerations_general_purpose.xml:455(para)
|
||||
msgid "A general purpose OpenStack deployment consists of more than just OpenStack-specific components. A typical deployment involves services that provide supporting functionality, including databases and message queues, and may also involve software to provide high availability of the OpenStack environment. Design decisions around the underlying message queue might affect the required number of controller services, as well as the technology to provide highly resilient database functionality, such as MariaDB with Galera. In such a scenario, replication of services relies on quorum. Therefore, the underlying database nodes, for example, should consist of at least 3 nodes to account for the recovery of a failed Galera node. When increasing the number of nodes to support a feature of the software, consideration of rack space and switch port density becomes important."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/generalpurpose/section_tech_considerations_general_purpose.xml:451(para)
|
||||
msgid "Where many general purpose deployments use hardware load balancers to provide highly available API access and SSL termination, software solutions, for example HAProxy, can also be considered. It is vital to ensure that such software implementations are also made highly available. This high availability can be achieved by using software such as Keepalived or Pacemaker with Corosync. Pacemaker and Corosync can provide Active-Active or Active-Passive highly available configuration depending on the specific service in the OpenStack environment. Using this software can affect the design as it assumes at least a 2-node controller infrastructure where one of those nodes may be running certain services in standby mode."
|
||||
#: ./doc/arch-design/generalpurpose/section_tech_considerations_general_purpose.xml:470(para)
|
||||
msgid "Where many general purpose deployments use hardware load balancers to provide highly available API access and SSL termination, software solutions, for example HAProxy, can also be considered. It is vital to ensure that such software implementations are also made highly available. This high availability can be achieved by using software such as Keepalived or Pacemaker with Corosync. Pacemaker and Corosync can provide active-active or active-passive highly available configuration depending on the specific service in the OpenStack environment. Using this software can affect the design as it assumes at least a 2-node controller infrastructure where one of those nodes may be running certain services in standby mode."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/generalpurpose/section_tech_considerations_general_purpose.xml:464(para)
|
||||
#: ./doc/arch-design/generalpurpose/section_tech_considerations_general_purpose.xml:483(para)
|
||||
msgid "Memcached is a distributed memory object caching system, and Redis is a key-value store. Both are usually deployed on general purpose clouds to assist in alleviating load to the Identity service. The memcached service caches tokens, and due to its distributed nature it can help alleviate some bottlenecks to the underlying authentication system. Using memcached or Redis does not affect the overall design of your architecture as they tend to be deployed onto the infrastructure nodes providing the OpenStack services."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/generalpurpose/section_tech_considerations_general_purpose.xml:475(para)
|
||||
#: ./doc/arch-design/generalpurpose/section_tech_considerations_general_purpose.xml:494(para)
|
||||
msgid "Performance of an OpenStack deployment is dependent on a number of factors related to the infrastructure and controller services. The user requirements can be split into general network performance, performance of compute resources, and performance of storage systems."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/generalpurpose/section_tech_considerations_general_purpose.xml:481(title)
|
||||
#: ./doc/arch-design/generalpurpose/section_tech_considerations_general_purpose.xml:500(title)
|
||||
msgid "Controller infrastructure"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/generalpurpose/section_tech_considerations_general_purpose.xml:482(para)
|
||||
#: ./doc/arch-design/generalpurpose/section_tech_considerations_general_purpose.xml:501(para)
|
||||
msgid "The Controller infrastructure nodes provide management services to the end-user as well as providing services internally for the operating of the cloud. The Controllers typically run message queuing services that carry system messages between each service. Performance issues related to the message bus would lead to delays in sending that message to where it needs to go. The result of this condition would be delays in operation functions such as spinning up and deleting instances, provisioning new storage volumes and managing network resources. Such delays could adversely affect an application’s ability to react to certain conditions, especially when using auto-scaling features. It is important to properly design the hardware used to run the controller infrastructure as outlined above in the Hardware Selection section."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/generalpurpose/section_tech_considerations_general_purpose.xml:497(para)
|
||||
#: ./doc/arch-design/generalpurpose/section_tech_considerations_general_purpose.xml:516(para)
|
||||
msgid "Performance of the controller services is not just limited to processing power, but restrictions may emerge in serving concurrent users. Ensure that the APIs and Horizon services are load tested to ensure that you are able to serve your customers. Particular attention should be made to the OpenStack Identity Service (Keystone), which provides the authentication and authorization for all services, both internally to OpenStack itself and to end-users. This service can lead to a degradation of overall performance if this is not sized appropriately."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/generalpurpose/section_tech_considerations_general_purpose.xml:508(title)
|
||||
#: ./doc/arch-design/generalpurpose/section_tech_considerations_general_purpose.xml:527(title)
|
||||
msgid "Network performance"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/generalpurpose/section_tech_considerations_general_purpose.xml:509(para)
|
||||
#: ./doc/arch-design/generalpurpose/section_tech_considerations_general_purpose.xml:528(para)
|
||||
msgid "In a general purpose OpenStack cloud, the requirements of the network help determine its performance capabilities. For example, small deployments may employ 1 Gigabit Ethernet (GbE) networking, whereas larger installations serving multiple departments or many users would be better architected with 10GbE networking. The performance of the running instances will be limited by these speeds. It is possible to design OpenStack environments that run a mix of networking capabilities. By utilizing the different interface speeds, the users of the OpenStack environment can choose networks that are fit for their purpose. For example, web application instances may run on a public network presented through OpenStack Networking that has 1 GbE capability, whereas the back-end database uses an OpenStack Networking network that has 10GbE capability to replicate its data or, in some cases, the design may incorporate link aggregation for greater throughput."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/generalpurpose/section_tech_considerations_general_purpose.xml:525(para)
|
||||
#: ./doc/arch-design/generalpurpose/section_tech_considerations_general_purpose.xml:544(para)
|
||||
msgid "Network performance can be boosted considerably by implementing hardware load balancers to provide front-end service to the cloud APIs. The hardware load balancers also perform SSL termination if that is a requirement of your environment. When implementing SSL offloading, it is important to understand the SSL offloading capabilities of the devices selected."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/generalpurpose/section_tech_considerations_general_purpose.xml:533(title)
|
||||
#: ./doc/arch-design/generalpurpose/section_tech_considerations_general_purpose.xml:552(title)
|
||||
msgid "Compute host"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/generalpurpose/section_tech_considerations_general_purpose.xml:534(para)
|
||||
#: ./doc/arch-design/generalpurpose/section_tech_considerations_general_purpose.xml:553(para)
|
||||
msgid "The choice of hardware specifications used in compute nodes including CPU, memory and disk type directly affects the performance of the instances. Other factors which can directly affect performance include tunable parameters within the OpenStack services, for example the overcommit ratio applied to resources. The defaults in OpenStack Compute set a 16:1 over-commit of the CPU and 1.5 over-commit of the memory. Running at such high ratios leads to an increase in \"noisy-neighbor\" activity. Care must be taken when sizing your Compute environment to avoid this scenario. For running general purpose OpenStack environments it is possible to keep to the defaults, but make sure to monitor your environment as usage increases."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/generalpurpose/section_tech_considerations_general_purpose.xml:548(title)
|
||||
#: ./doc/arch-design/generalpurpose/section_tech_considerations_general_purpose.xml:567(title)
|
||||
msgid "Storage performance"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/generalpurpose/section_tech_considerations_general_purpose.xml:549(para)
|
||||
#: ./doc/arch-design/generalpurpose/section_tech_considerations_general_purpose.xml:568(para)
|
||||
msgid "When considering performance of OpenStack Block Storage, hardware and architecture choice is important. Block Storage can use enterprise back-end systems such as NetApp or EMC, use scale out storage such as GlusterFS and Ceph, or simply use the capabilities of directly attached storage in the nodes themselves. Block Storage may be deployed so that traffic traverses the host network, which could affect, and be adversely affected by, the front-side API traffic performance. As such, consider using a dedicated data storage network with dedicated interfaces on the Controller and Compute hosts."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/generalpurpose/section_tech_considerations_general_purpose.xml:560(para)
|
||||
#: ./doc/arch-design/generalpurpose/section_tech_considerations_general_purpose.xml:579(para)
|
||||
msgid "When considering performance of OpenStack Object Storage, a number of design choices will affect performance. A user’s access to the Object Storage is through the proxy services, which typically sit behind hardware load balancers. By the very nature of a highly resilient storage system, replication of the data would affect performance of the overall system. In this case, 10 GbE (or better) networking is recommended throughout the storage network architecture."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/generalpurpose/section_tech_considerations_general_purpose.xml:570(para)
|
||||
#: ./doc/arch-design/generalpurpose/section_tech_considerations_general_purpose.xml:589(para)
|
||||
msgid "In OpenStack, the infrastructure is integral to providing services and should always be available, especially when operating with SLAs. Ensuring network availability is accomplished by designing the network architecture so that no single point of failure exists. A consideration of the number of switches, routes and redundancies of power should be factored into core infrastructure, as well as the associated bonding of networks to provide diverse routes to your highly available switch infrastructure."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/generalpurpose/section_tech_considerations_general_purpose.xml:579(para)
|
||||
#: ./doc/arch-design/generalpurpose/section_tech_considerations_general_purpose.xml:598(para)
|
||||
msgid "The OpenStack services themselves should be deployed across multiple servers that do not represent a single point of failure. Ensuring API availability can be achieved by placing these services behind highly available load balancers that have multiple OpenStack servers as members."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/generalpurpose/section_tech_considerations_general_purpose.xml:584(para)
|
||||
#: ./doc/arch-design/generalpurpose/section_tech_considerations_general_purpose.xml:603(para)
|
||||
msgid "OpenStack lends itself to deployment in a highly available manner where it is expected that at least 2 servers be utilized. These can run all the services involved from the message queuing service, for example RabbitMQ or QPID, and an appropriately deployed database service such as MySQL or MariaDB. As services in the cloud are scaled out, back-end services will need to scale too. Monitoring and reporting on server utilization and response times, as well as load testing your systems, will help determine scale out decisions."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/generalpurpose/section_tech_considerations_general_purpose.xml:593(para)
|
||||
#: ./doc/arch-design/generalpurpose/section_tech_considerations_general_purpose.xml:612(para)
|
||||
msgid "Care must be taken when deciding network functionality. Currently, OpenStack supports both the legacy networking (nova-network) system and the newer, extensible OpenStack Networking. Both have their pros and cons when it comes to providing highly available access. Legacy networking, which provides networking access maintained in the OpenStack Compute code, provides a feature that removes a single point of failure when it comes to routing, and this feature is currently missing in OpenStack Networking. The effect of legacy networking’s multi-host functionality restricts failure domains to the host running that instance."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/generalpurpose/section_tech_considerations_general_purpose.xml:604(para)
|
||||
#: ./doc/arch-design/generalpurpose/section_tech_considerations_general_purpose.xml:623(para)
|
||||
msgid "On the other hand, when using OpenStack Networking, the OpenStack controller servers or separate Networking hosts handle routing. For a deployment that requires features available in only Networking, it is possible to remove this restriction by using third party software that helps maintain highly available L3 routes. Doing so allows for common APIs to control network hardware, or to provide complex multi-tier web applications in a secure manner. It is also possible to completely remove routing from Networking, and instead rely on hardware routing capabilities. In this case, the switching infrastructure must support L3 routing."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/generalpurpose/section_tech_considerations_general_purpose.xml:616(para)
|
||||
#: ./doc/arch-design/generalpurpose/section_tech_considerations_general_purpose.xml:635(para)
|
||||
msgid "OpenStack Networking (neutron) and legacy networking (nova-network) both have their advantages and disadvantages. They are both valid and supported options that fit different network deployment models described in the <citetitle><link href=\"http://docs.openstack.org/openstack-ops/content/network_design.html#network_deployment_options\">OpenStack Operations Guide</link></citetitle>."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/generalpurpose/section_tech_considerations_general_purpose.xml:624(para)
|
||||
#: ./doc/arch-design/generalpurpose/section_tech_considerations_general_purpose.xml:643(para)
|
||||
msgid "Ensure your deployment has adequate back-up capabilities. As an example, in a deployment that has two infrastructure controller nodes, the design should include controller availability. In the event of the loss of a single controller, cloud services will run from a single controller in the event of failure. Where the design has higher availability requirements, it is important to meet those requirements by designing the proper redundancy and availability of controller nodes."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/generalpurpose/section_tech_considerations_general_purpose.xml:633(para)
|
||||
#: ./doc/arch-design/generalpurpose/section_tech_considerations_general_purpose.xml:652(para)
|
||||
msgid "Application design must also be factored into the capabilities of the underlying cloud infrastructure. If the compute hosts do not provide a seamless live migration capability, then it must be expected that when a compute host fails, that instance and any data local to that instance will be deleted. Conversely, when providing an expectation to users that instances have a high-level of uptime guarantees, the infrastructure must be deployed in a way that eliminates any single point of failure when a compute host disappears. This may include utilizing shared file systems on enterprise storage or OpenStack Block storage to provide a level of guarantee to match service features."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/generalpurpose/section_tech_considerations_general_purpose.xml:645(para)
|
||||
#: ./doc/arch-design/generalpurpose/section_tech_considerations_general_purpose.xml:664(para)
|
||||
msgid "For more information on high availability in OpenStack, see the <link href=\"http://docs.openstack.org/high-availability-guide\"><citetitle>OpenStack High Availability Guide</citetitle></link>."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/generalpurpose/section_tech_considerations_general_purpose.xml:653(para) ./doc/arch-design/compute_focus/section_tech_considerations_compute_focus.xml:272(para)
|
||||
#: ./doc/arch-design/generalpurpose/section_tech_considerations_general_purpose.xml:672(para) ./doc/arch-design/compute_focus/section_tech_considerations_compute_focus.xml:272(para)
|
||||
msgid "A security domain comprises users, applications, servers or networks that share common trust requirements and expectations within a system. Typically they have the same authentication and authorization requirements and users."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/generalpurpose/section_tech_considerations_general_purpose.xml:657(para) ./doc/arch-design/compute_focus/section_tech_considerations_compute_focus.xml:277(para)
|
||||
#: ./doc/arch-design/generalpurpose/section_tech_considerations_general_purpose.xml:676(para) ./doc/arch-design/compute_focus/section_tech_considerations_compute_focus.xml:277(para)
|
||||
msgid "These security domains are:"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/generalpurpose/section_tech_considerations_general_purpose.xml:660(para) ./doc/arch-design/compute_focus/section_tech_considerations_compute_focus.xml:280(para) ./doc/arch-design/hybrid/section_tech_considerations_hybrid.xml:120(para)
|
||||
#: ./doc/arch-design/generalpurpose/section_tech_considerations_general_purpose.xml:679(para) ./doc/arch-design/compute_focus/section_tech_considerations_compute_focus.xml:280(para) ./doc/arch-design/hybrid/section_tech_considerations_hybrid.xml:120(para)
|
||||
msgid "Public"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/generalpurpose/section_tech_considerations_general_purpose.xml:663(para) ./doc/arch-design/compute_focus/section_tech_considerations_compute_focus.xml:283(para) ./doc/arch-design/hybrid/section_tech_considerations_hybrid.xml:123(para)
|
||||
#: ./doc/arch-design/generalpurpose/section_tech_considerations_general_purpose.xml:682(para) ./doc/arch-design/compute_focus/section_tech_considerations_compute_focus.xml:283(para) ./doc/arch-design/hybrid/section_tech_considerations_hybrid.xml:123(para)
|
||||
msgid "Guest"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/generalpurpose/section_tech_considerations_general_purpose.xml:669(para) ./doc/arch-design/compute_focus/section_tech_considerations_compute_focus.xml:289(para) ./doc/arch-design/hybrid/section_architecture_hybrid.xml:166(title) ./doc/arch-design/hybrid/section_tech_considerations_hybrid.xml:129(para)
|
||||
#: ./doc/arch-design/generalpurpose/section_tech_considerations_general_purpose.xml:688(para) ./doc/arch-design/compute_focus/section_tech_considerations_compute_focus.xml:289(para) ./doc/arch-design/hybrid/section_architecture_hybrid.xml:166(title) ./doc/arch-design/hybrid/section_tech_considerations_hybrid.xml:129(para)
|
||||
msgid "Data"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/generalpurpose/section_tech_considerations_general_purpose.xml:672(para)
|
||||
#: ./doc/arch-design/generalpurpose/section_tech_considerations_general_purpose.xml:691(para)
|
||||
msgid "These security domains can be mapped to an OpenStack deployment individually, or combined. For example, some deployment topologies combine both guest and data domains onto one physical network, whereas in other cases these networks are physically separated. In each case, the cloud operator should be aware of the appropriate security concerns. Security domains should be mapped out against your specific OpenStack deployment topology. The domains and their trust requirements depend upon whether the cloud instance is public, private, or hybrid."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/generalpurpose/section_tech_considerations_general_purpose.xml:682(para)
|
||||
#: ./doc/arch-design/generalpurpose/section_tech_considerations_general_purpose.xml:701(para)
|
||||
msgid "The public security domain is an entirely untrusted area of the cloud infrastructure. It can refer to the Internet as a whole or simply to networks over which you have no authority. This domain should always be considered untrusted."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/generalpurpose/section_tech_considerations_general_purpose.xml:686(para)
|
||||
#: ./doc/arch-design/generalpurpose/section_tech_considerations_general_purpose.xml:705(para)
|
||||
msgid "Typically used for compute instance-to-instance traffic, the guest security domain handles compute data generated by instances on the cloud but not services that support the operation of the cloud, such as API calls. Public cloud providers and private cloud providers who do not have stringent controls on instance use or who allow unrestricted Internet access to instances should consider this domain to be untrusted. Private cloud providers may want to consider this network as internal and therefore trusted only if they have controls in place to assert that they trust instances and all their tenants."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/generalpurpose/section_tech_considerations_general_purpose.xml:697(para) ./doc/arch-design/compute_focus/section_tech_considerations_compute_focus.xml:318(para)
|
||||
#: ./doc/arch-design/generalpurpose/section_tech_considerations_general_purpose.xml:716(para) ./doc/arch-design/compute_focus/section_tech_considerations_compute_focus.xml:318(para)
|
||||
msgid "The management security domain is where services interact. Sometimes referred to as the \"control plane\", the networks in this domain transport confidential data such as configuration parameters, user names, and passwords. In most deployments this domain is considered trusted."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/generalpurpose/section_tech_considerations_general_purpose.xml:702(para)
|
||||
#: ./doc/arch-design/generalpurpose/section_tech_considerations_general_purpose.xml:721(para)
|
||||
msgid "The data security domain is concerned primarily with information pertaining to the storage services within OpenStack. Much of the data that crosses this network has high integrity and confidentiality requirements and, depending on the type of deployment, may also have strong availability requirements. The trust level of this network is heavily dependent on other deployment decisions."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/generalpurpose/section_tech_considerations_general_purpose.xml:709(para)
|
||||
#: ./doc/arch-design/generalpurpose/section_tech_considerations_general_purpose.xml:728(para)
|
||||
msgid "When deploying OpenStack in an enterprise as a private cloud it is usually behind the firewall and within the trusted network alongside existing systems. Users of the cloud are, traditionally, employees that are bound by the security requirements set forth by the company. This tends to push most of the security domains towards a more trusted model. However, when deploying OpenStack in a public facing role, no assumptions can be made and the attack vectors significantly increase. For example, the API endpoints, along with the software behind them, become vulnerable to bad actors wanting to gain unauthorized access or prevent access to services, which could lead to loss of data, functionality, and reputation. These services must be protected against through auditing and appropriate filtering."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/generalpurpose/section_tech_considerations_general_purpose.xml:723(para)
|
||||
#: ./doc/arch-design/generalpurpose/section_tech_considerations_general_purpose.xml:742(para)
|
||||
msgid "Consideration must be taken when managing the users of the system for both public and private clouds. The identity service allows for LDAP to be part of the authentication process. Including such systems in an OpenStack deployment may ease user management if integrating into existing systems."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/generalpurpose/section_tech_considerations_general_purpose.xml:729(para)
|
||||
#: ./doc/arch-design/generalpurpose/section_tech_considerations_general_purpose.xml:748(para)
|
||||
msgid "It's important to understand that user authentication requests include sensitive information including user names, passwords and authentication tokens. For this reason, placing the API services behind hardware that performs SSL termination is strongly recommended."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/generalpurpose/section_tech_considerations_general_purpose.xml:734(para)
|
||||
#: ./doc/arch-design/generalpurpose/section_tech_considerations_general_purpose.xml:753(para)
|
||||
msgid "For more information OpenStack Security, see the <link href=\"http://docs.openstack.org/security-guide/\"><citetitle>OpenStack Security Guide</citetitle></link>"
|
||||
msgstr ""
|
||||
|
||||
@ -3250,70 +3254,70 @@ msgid "How this book is organized"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/introduction/section_how_this_book_is_organized.xml:8(para)
|
||||
msgid "This book has been organized into various chapters that help define the use cases associated with making architectural choices related to an OpenStack cloud installation. Each chapter is intended to stand alone to encourage individual chapter readability, however each chapter is designed to contain useful information that may be applicable in situations covered by other chapters. Cloud architects may use this book as a comprehensive guide by reading all of the use cases, but it is also possible to review only the chapters which pertain to a specific use case. When choosing to read specific use cases, note that it may be necessary to read more than one section of the guide to formulate a complete design for the cloud. The use cases covered in this guide include:"
|
||||
msgid "This book has been organized into various chapters that help define the use cases associated with making architectural choices related to an <glossterm>OpenStack</glossterm> cloud installation. Each chapter is intended to stand alone to encourage individual chapter readability, however each chapter is designed to contain useful information that may be applicable in situations covered by other chapters. Cloud architects may use this book as a comprehensive guide by reading all of the use cases, but it is also possible to review only the chapters which pertain to a specific use case. When choosing to read specific use cases, note that it may be necessary to read more than one section of the guide to formulate a complete design for the cloud. The use cases covered in this guide include:"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/introduction/section_how_this_book_is_organized.xml:24(para)
|
||||
#: ./doc/arch-design/introduction/section_how_this_book_is_organized.xml:25(para)
|
||||
msgid "<link linkend=\"generalpurpose\">General purpose</link>: A cloud built with common components that should address 80% of common use cases."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/introduction/section_how_this_book_is_organized.xml:31(para)
|
||||
#: ./doc/arch-design/introduction/section_how_this_book_is_organized.xml:32(para)
|
||||
msgid "<link linkend=\"compute_focus\">Compute focused</link>: A cloud designed to address compute intensive workloads such as high performance computing (HPC)."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/introduction/section_how_this_book_is_organized.xml:38(para)
|
||||
#: ./doc/arch-design/introduction/section_how_this_book_is_organized.xml:39(para)
|
||||
msgid "<link linkend=\"storage_focus\">Storage focused</link>: A cloud focused on storage intensive workloads such as data analytics with parallel file systems."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/introduction/section_how_this_book_is_organized.xml:45(para)
|
||||
#: ./doc/arch-design/introduction/section_how_this_book_is_organized.xml:46(para)
|
||||
msgid "<link linkend=\"network_focus\">Network focused</link>: A cloud depending on high performance and reliable networking, such as a <glossterm>content delivery network (CDN)</glossterm>."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/introduction/section_how_this_book_is_organized.xml:53(para)
|
||||
#: ./doc/arch-design/introduction/section_how_this_book_is_organized.xml:54(para)
|
||||
msgid "<link linkend=\"multi_site\">Multi-site</link>: A cloud built with multiple sites available for application deployments for geographical, reliability or data locality reasons."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/introduction/section_how_this_book_is_organized.xml:61(para)
|
||||
#: ./doc/arch-design/introduction/section_how_this_book_is_organized.xml:62(para)
|
||||
msgid "<link linkend=\"hybrid\">Hybrid cloud</link>: An architecture where multiple disparate clouds are connected either for failover, hybrid cloud bursting, or availability."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/introduction/section_how_this_book_is_organized.xml:69(para)
|
||||
#: ./doc/arch-design/introduction/section_how_this_book_is_organized.xml:70(para)
|
||||
msgid "<link linkend=\"massively_scalable\">Massively scalable</link>: An architecture that is intended for cloud service providers or other extremely large installations."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/introduction/section_how_this_book_is_organized.xml:77(para)
|
||||
#: ./doc/arch-design/introduction/section_how_this_book_is_organized.xml:78(para)
|
||||
msgid "A chapter titled <link linkend=\"specialized\">Specialized cases</link> provides information on architectures that have not previously been covered in the defined use cases."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/introduction/section_how_this_book_is_organized.xml:82(para)
|
||||
#: ./doc/arch-design/introduction/section_how_this_book_is_organized.xml:83(para)
|
||||
msgid "Each chapter in the guide is then further broken down into the following sections:"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/introduction/section_how_this_book_is_organized.xml:86(para)
|
||||
#: ./doc/arch-design/introduction/section_how_this_book_is_organized.xml:87(para)
|
||||
msgid "Introduction: Provides an overview of the architectural use case."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/introduction/section_how_this_book_is_organized.xml:90(para)
|
||||
#: ./doc/arch-design/introduction/section_how_this_book_is_organized.xml:91(para)
|
||||
msgid "User requirements: Defines the set of user considerations that typically come into play for that use case."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/introduction/section_how_this_book_is_organized.xml:95(para)
|
||||
#: ./doc/arch-design/introduction/section_how_this_book_is_organized.xml:96(para)
|
||||
msgid "Technical considerations: Covers the technical issues that must be accounted when dealing with this use case."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/introduction/section_how_this_book_is_organized.xml:100(para)
|
||||
#: ./doc/arch-design/introduction/section_how_this_book_is_organized.xml:101(para)
|
||||
msgid "Operational considerations: Covers the ongoing operational tasks associated with this use case and architecture."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/introduction/section_how_this_book_is_organized.xml:105(para)
|
||||
#: ./doc/arch-design/introduction/section_how_this_book_is_organized.xml:106(para)
|
||||
msgid "Architecture: Covers the overall architecture associated with the use case."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/introduction/section_how_this_book_is_organized.xml:109(para)
|
||||
#: ./doc/arch-design/introduction/section_how_this_book_is_organized.xml:110(para)
|
||||
msgid "Prescriptive examples: Presents one or more scenarios where this architecture could be deployed."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/introduction/section_how_this_book_is_organized.xml:114(para)
|
||||
#: ./doc/arch-design/introduction/section_how_this_book_is_organized.xml:115(para)
|
||||
msgid "A glossary covers the terms used in the book."
|
||||
msgstr ""
|
||||
|
||||
@ -3609,10 +3613,6 @@ msgstr ""
|
||||
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 combination."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:442(para)
|
||||
msgid "Ensure that 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 will have an impact on performance and the patch installation process could affect maintenance windows."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:453(para) ./doc/arch-design/storage_focus/section_architecture_storage_focus.xml:485(para)
|
||||
msgid "Determine what features of OpenStack are required. This will often determine the selection of the OS-hypervisor combination. Certain 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 ""
|
||||
@ -3929,35 +3929,51 @@ msgstr ""
|
||||
msgid "Due to the nature of the workloads that will be used in this scenario, a number of components will be highly beneficial in a Compute-focused cloud. This includes the typical OpenStack components:"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/compute_focus/section_tech_considerations_compute_focus.xml:367(para)
|
||||
msgid "OpenStack Compute (nova)"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/compute_focus/section_tech_considerations_compute_focus.xml:370(para) ./doc/arch-design/storage_focus/section_architecture_storage_focus.xml:546(para)
|
||||
msgid "OpenStack Image Service (glance)"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/compute_focus/section_tech_considerations_compute_focus.xml:373(para) ./doc/arch-design/storage_focus/section_architecture_storage_focus.xml:530(para)
|
||||
msgid "OpenStack Identity (keystone)"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/compute_focus/section_tech_considerations_compute_focus.xml:376(para)
|
||||
msgid "Also consider several specialized components:"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/compute_focus/section_tech_considerations_compute_focus.xml:379(para)
|
||||
msgid "Orchestration module (heat)"
|
||||
msgid "<glossterm>Orchestration</glossterm> module (<glossterm>heat</glossterm>)"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/compute_focus/section_tech_considerations_compute_focus.xml:382(para)
|
||||
#: ./doc/arch-design/compute_focus/section_tech_considerations_compute_focus.xml:383(para)
|
||||
msgid "It is safe to assume that, given the nature of the applications involved in this scenario, these will be heavily automated deployments. Making use of Orchestration will be highly beneficial in this case. Deploying a batch of instances and running an automated set of tests can be scripted, however it makes sense to use the Orchestration module to handle all these actions."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/compute_focus/section_tech_considerations_compute_focus.xml:394(para)
|
||||
#: ./doc/arch-design/compute_focus/section_tech_considerations_compute_focus.xml:392(para)
|
||||
msgid "Telemetry module (ceilometer)"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/compute_focus/section_tech_considerations_compute_focus.xml:395(para)
|
||||
msgid "Telemetry and the alarms it generates are required to support autoscaling of instances using Orchestration. Users that are not using the Orchestration module do not need to deploy the Telemetry module and may choose to use other external solutions to fulfill their metering and monitoring requirements."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/compute_focus/section_tech_considerations_compute_focus.xml:400(para)
|
||||
#: ./doc/arch-design/compute_focus/section_tech_considerations_compute_focus.xml:401(para)
|
||||
msgid "See also: <link href=\"http://docs.openstack.org/openstack-ops/content/logging_monitoring.html\">http://docs.openstack.org/openstack-ops/content/logging_monitoring.html</link>"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/compute_focus/section_tech_considerations_compute_focus.xml:404(para) ./doc/arch-design/storage_focus/section_architecture_storage_focus.xml:543(para)
|
||||
#: ./doc/arch-design/compute_focus/section_tech_considerations_compute_focus.xml:405(para) ./doc/arch-design/storage_focus/section_architecture_storage_focus.xml:543(para)
|
||||
msgid "OpenStack Block Storage (cinder)"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/compute_focus/section_tech_considerations_compute_focus.xml:407(para)
|
||||
#: ./doc/arch-design/compute_focus/section_tech_considerations_compute_focus.xml:408(para)
|
||||
msgid "Due to the burst-able nature of the workloads and the applications and instances that will be used for batch processing, this cloud will utilize mainly memory or CPU, so the need for add-on storage to each instance is not a likely requirement. This does not mean that OpenStack Block Storage (cinder) will not be used in the infrastructure, but typically it will not be used as a central component."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/compute_focus/section_tech_considerations_compute_focus.xml:419(para)
|
||||
#: ./doc/arch-design/compute_focus/section_tech_considerations_compute_focus.xml:420(para)
|
||||
msgid "When choosing a networking platform, ensure that it either works with all desired hypervisor and container technologies and their OpenStack drivers, or includes an implementation of an ML2 mechanism driver. Networking platforms that provide ML2 mechanisms drivers can be mixed."
|
||||
msgstr ""
|
||||
|
||||
@ -5647,6 +5663,10 @@ msgstr ""
|
||||
msgid "For a storage-focused OpenStack design architecture, the following components would typically be used:"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/storage_focus/section_architecture_storage_focus.xml:533(para)
|
||||
msgid "OpenStack dashboard (horizon)"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/arch-design/storage_focus/section_architecture_storage_focus.xml:536(para)
|
||||
msgid "OpenStack Compute (nova) (including the use of multiple hypervisor drivers)"
|
||||
msgstr ""
|
||||
|
||||
@ -1,7 +1,7 @@
|
||||
msgid ""
|
||||
msgstr ""
|
||||
"Project-Id-Version: PACKAGE VERSION\n"
|
||||
"POT-Creation-Date: 2014-08-15 06:09+0000\n"
|
||||
"POT-Creation-Date: 2014-08-16 06:09+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"
|
||||
@ -890,7 +890,7 @@ msgid "Firewall-as-a-Service driver"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/networking/section_networking-options-reference.xml:64(para)
|
||||
msgid "Use the following options in the <filename>fwaas_driver.ini</filename> file for the FwaaS driver."
|
||||
msgid "Use the following options in the <filename>fwaas_driver.ini</filename> file for the FWaaS driver."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/networking/section_networking-options-reference.xml:70(title)
|
||||
@ -906,7 +906,7 @@ msgid "Load-Balancer-as-a-Service agent"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/networking/section_networking-options-reference.xml:78(para)
|
||||
msgid "Use the following options in the <filename>lbaas_agent.ini</filename> file for the LbaaS agent."
|
||||
msgid "Use the following options in the <filename>lbaas_agent.ini</filename> file for the LBaaS agent."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/networking/section_networking-options-reference.xml:87(title)
|
||||
@ -994,7 +994,7 @@ msgid "vArmour Firewall-as-a-Service driver"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/networking/section_networking-options-reference.xml:156(para)
|
||||
msgid "Use the following options in the <filename>l3_agent.ini</filename> file for the vArmour FwaaS driver."
|
||||
msgid "Use the following options in the <filename>l3_agent.ini</filename> file for the vArmour FWaaS driver."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/networking/section_networking-options-reference.xml:162(title)
|
||||
@ -1178,7 +1178,7 @@ msgid "A simple workaround is to increase the MTU value of the physical interfac
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/networking/section_networking-plugins-ml2.xml:30(para)
|
||||
msgid "Another workaround is to decrease the virtual ethernet devices' MTU. Set the <option>network_device_mtu</option> option to 1450 in the <filename>neutron.conf</filename> file, and set all guest virtual machines' MTU to the same value by using a DHCP option. For information about how to use this option, see <link href=\"http://docs.openstack.org/admin-guide-cloud/content/ch_networking.html#openvswitch_plugin\">Configure OVS plug-in</link>."
|
||||
msgid "Another workaround is to decrease the virtual Ethernet devices' MTU. Set the <option>network_device_mtu</option> option to 1450 in the <filename>neutron.conf</filename> file, and set all guest virtual machines' MTU to the same value by using a DHCP option. For information about how to use this option, see <link href=\"http://docs.openstack.org/admin-guide-cloud/content/ch_networking.html#openvswitch_plugin\">Configure OVS plug-in</link>."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/networking/section_networking-plugins-ml2.xml:45(title)
|
||||
@ -1522,7 +1522,7 @@ msgid "Object Storage general service configuration"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/object-storage/section_object-storage-general-service-conf.xml:8(para)
|
||||
msgid "Most Object Storage services fall into two categories, Object Storage's wsgi servers and background daemons."
|
||||
msgid "Most Object Storage services fall into two categories, Object Storage's WSGI servers and background daemons."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/object-storage/section_object-storage-general-service-conf.xml:12(para)
|
||||
@ -1858,7 +1858,7 @@ msgid "You can see the health of the objects in the cluster has gone down signif
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/object-storage/section_object-storage-features.xml:438(para)
|
||||
msgid "Alternatively, the dispersion report can also be output in json format. This allows it to be more easily consumed by third-party utilities:"
|
||||
msgid "Alternatively, the dispersion report can also be output in JSON format. This allows it to be more easily consumed by third-party utilities:"
|
||||
msgstr ""
|
||||
|
||||
#. Usage documented in http://docs.openstack.org/developer/swift/overview_large_objects.html
|
||||
@ -1883,7 +1883,7 @@ msgid "Any object PUT operations that exceed these quotas return a 413 response
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/object-storage/section_object-storage-features.xml:474(para)
|
||||
msgid "Quotas are subject to several limitations: eventual consistency, the timeliness of the cached container_info (60 second ttl by default), and it is unable to reject chunked transfer uploads that exceed the quota (though once the quota is exceeded, new chunked transfers are refused)."
|
||||
msgid "Quotas are subject to several limitations: eventual consistency, the timeliness of the cached container_info (60 second TTL by default), and it is unable to reject chunked transfer uploads that exceed the quota (though once the quota is exceeded, new chunked transfers are refused)."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/object-storage/section_object-storage-features.xml:480(para)
|
||||
@ -3091,7 +3091,7 @@ msgid "Sheepdog is an open-source distributed storage system that provides a vir
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/block-storage/drivers/sheepdog-driver.xml:10(para)
|
||||
msgid "Sheepdog scales to several hundred nodes, and has powerful virtual disk management features like snapshot, cloning, rollback, thin proisioning."
|
||||
msgid "Sheepdog scales to several hundred nodes, and has powerful virtual disk management features like snapshot, cloning, rollback, thin provisioning."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/block-storage/drivers/sheepdog-driver.xml:13(para)
|
||||
@ -3231,7 +3231,7 @@ msgid "Register the node"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/block-storage/drivers/emc-volume-driver.xml:157(para)
|
||||
msgid "On the Compute node or Volume node <literal>1.1.1.1</literal>, do the following (assume <literal>10.10.61.35</literal> is the iscsi target):"
|
||||
msgid "On the Compute node or Volume node <literal>1.1.1.1</literal>, do the following (assume <literal>10.10.61.35</literal> is the iSCSI target):"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/block-storage/drivers/emc-volume-driver.xml:165(para) ./doc/config-reference/block-storage/drivers/emc-vnx-direct-driver.xml:109(para)
|
||||
@ -3469,7 +3469,7 @@ msgid "<emphasis>RADOS</emphasis>. Use as an object, default storage mechanism."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/block-storage/drivers/ceph-rbd-volume-driver.xml:81(para)
|
||||
msgid "<emphasis>RBD</emphasis>. Use as a block device. The Linux kernel RBD (rados block device) driver allows striping a Linux block device over multiple distributed object store data objects. It is compatible with the KVM RBD image."
|
||||
msgid "<emphasis>RBD</emphasis>. Use as a block device. The Linux kernel RBD (RADOS block device) driver allows striping a Linux block device over multiple distributed object store data objects. It is compatible with the KVM RBD image."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/block-storage/drivers/ceph-rbd-volume-driver.xml:88(para)
|
||||
@ -3489,7 +3489,7 @@ msgid "<emphasis>librados</emphasis>, and its related C/C++ bindings."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/block-storage/drivers/ceph-rbd-volume-driver.xml:104(para)
|
||||
msgid "<emphasis>rbd and QEMU-RBD</emphasis>. Linux kernel and QEMU block devices that stripe data across multiple objects."
|
||||
msgid "<emphasis>RBD and QEMU-RBD</emphasis>. Linux kernel and QEMU block devices that stripe data across multiple objects."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/block-storage/drivers/ceph-rbd-volume-driver.xml:111(title)
|
||||
@ -3521,7 +3521,7 @@ msgid "Use the HDS <placeholder-1/> command to communicate with an HUS array. Yo
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/block-storage/drivers/hds-hus-driver.xml:21(para) ./doc/config-reference/block-storage/drivers/hds-hnas-driver.xml:21(para)
|
||||
msgid "Platform: Ubuntu 12.04LTS or newer."
|
||||
msgid "Platform: Ubuntu 12.04 LTS or newer."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/block-storage/drivers/hds-hus-driver.xml:25(para)
|
||||
@ -4661,7 +4661,7 @@ msgid "Install NaviSecCLI"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/block-storage/drivers/emc-vnx-direct-driver.xml:90(para)
|
||||
msgid "On Ubuntu x64, download the NaviSecCLI deb package from <link href=\"https://github.com/emc-openstack/naviseccli\">EMC's OpenStack Github</link> web site."
|
||||
msgid "On Ubuntu x64, download the NaviSecCLI deb package from <link href=\"https://github.com/emc-openstack/naviseccli\">EMC's OpenStack GitHub</link> web site."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/block-storage/drivers/emc-vnx-direct-driver.xml:92(para)
|
||||
@ -5565,15 +5565,15 @@ msgid "The default volume back-end uses local volumes managed by LVM."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/block-storage/drivers/lvm-volume-driver.xml:8(para)
|
||||
msgid "This driver supports different transport protocols to attach volumes, currently ISCSI and ISER."
|
||||
msgid "This driver supports different transport protocols to attach volumes, currently iSCSI and iSER."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/block-storage/drivers/lvm-volume-driver.xml:10(para)
|
||||
msgid "Set the following in your <filename>cinder.conf</filename>, and use the following options to configure for ISCSI transport:"
|
||||
msgid "Set the following in your <filename>cinder.conf</filename>, and use the following options to configure for iSCSI transport:"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/block-storage/drivers/lvm-volume-driver.xml:16(para)
|
||||
msgid "and for the ISER transport:"
|
||||
msgid "and for the iSER transport:"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/block-storage/drivers/xen-sm-driver.xml:4(title)
|
||||
@ -8967,7 +8967,7 @@ msgid "The VMware driver supports networking with the <systemitem class=\"servic
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/compute/section_hypervisor_vmware.xml:871(para)
|
||||
msgid "<emphasis role=\"bold\"> The <systemitem class=\"service\">nova-network</systemitem> service with the FlatManager or FlatDHCPManager</emphasis>. Create a port group with the same name as the <literal>flat_network_bridge</literal> value in the <filename>nova.conf</filename> file. The default value is <literal>br100</literal>. If you specify another value, the new value must be a valid linux bridge identifier that adheres to linux bridge naming conventions."
|
||||
msgid "<emphasis role=\"bold\"> The <systemitem class=\"service\">nova-network</systemitem> service with the FlatManager or FlatDHCPManager</emphasis>. Create a port group with the same name as the <literal>flat_network_bridge</literal> value in the <filename>nova.conf</filename> file. The default value is <literal>br100</literal>. If you specify another value, the new value must be a valid Linux bridge identifier that adheres to Linux bridge naming conventions."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/compute/section_hypervisor_vmware.xml:880(para)
|
||||
@ -8999,7 +8999,7 @@ msgid "Volumes with VMware vSphere"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/compute/section_hypervisor_vmware.xml:914(para)
|
||||
msgid "The VMware driver supports attaching volumes from the OpenStack Block Storage service. The VMware VMDK driver for OpenStack Block Storage is recommended and should be used for managing volumes based on vSphere data stores. For more information about the VMware VMDK driver, see <link href=\"http://docs.openstack.org/trunk/config-reference/content/vmware-vmdk-driver.html\">VMware VMDK Driver</link>. Also an iscsi volume driver provides limited support and can be used only for attachments."
|
||||
msgid "The VMware driver supports attaching volumes from the OpenStack Block Storage service. The VMware VMDK driver for OpenStack Block Storage is recommended and should be used for managing volumes based on vSphere data stores. For more information about the VMware VMDK driver, see <link href=\"http://docs.openstack.org/trunk/config-reference/content/vmware-vmdk-driver.html\">VMware VMDK Driver</link>. Also an iSCSI volume driver provides limited support and can be used only for attachments."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/compute/section_hypervisor_vmware.xml:923(title)
|
||||
@ -9563,7 +9563,7 @@ msgid "DifferentHostFilter"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:305(para)
|
||||
msgid "Schedules the instance on a different host from a set of instances. To take advantage of this filter, the requester must pass a scheduler hint, using <literal>different_host</literal> as the key and a list of instance uuids as the value. This filter is the opposite of the <literal>SameHostFilter</literal>. Using the <placeholder-1/> command-line tool, use the <literal>--hint</literal> flag. For example:"
|
||||
msgid "Schedules the instance on a different host from a set of instances. To take advantage of this filter, the requester must pass a scheduler hint, using <literal>different_host</literal> as the key and a list of instance UUIDs as the value. This filter is the opposite of the <literal>SameHostFilter</literal>. Using the <placeholder-1/> command-line tool, use the <literal>--hint</literal> flag. For example:"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:317(para)
|
||||
@ -9759,7 +9759,7 @@ msgid "SameHostFilter"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:527(para)
|
||||
msgid "Schedules the instance on the same host as another instance in a set of instances. To take advantage of this filter, the requester must pass a scheduler hint, using <literal>same_host</literal> as the key and a list of instance uuids as the value. This filter is the opposite of the <literal>DifferentHostFilter</literal>. Using the <placeholder-1/> command-line tool, use the <literal>--hint</literal> flag:"
|
||||
msgid "Schedules the instance on the same host as another instance in a set of instances. To take advantage of this filter, the requester must pass a scheduler hint, using <literal>same_host</literal> as the key and a list of instance UUIDs as the value. This filter is the opposite of the <literal>DifferentHostFilter</literal>. Using the <placeholder-1/> command-line tool, use the <literal>--hint</literal> flag:"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/compute/section_compute-scheduler.xml:544(title)
|
||||
@ -10075,19 +10075,19 @@ msgid "Create an ISO-typed SR, such as an NFS ISO library, for instance. For thi
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/compute/section_xen-install.xml:147(para)
|
||||
msgid "On the compute host, find and record the uuid of this ISO SR:"
|
||||
msgid "On the compute host, find and record the UUID of this ISO SR:"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/compute/section_xen-install.xml:152(para)
|
||||
msgid "Locate the uuid of the NFS ISO library:"
|
||||
msgid "Locate the UUID of the NFS ISO library:"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/compute/section_xen-install.xml:156(para)
|
||||
msgid "Set the uuid and configuration. Even if an NFS mount point is not local, you must specify <literal>local-storage-iso</literal>."
|
||||
msgid "Set the UUID and configuration. Even if an NFS mount point is not local, you must specify <literal>local-storage-iso</literal>."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/compute/section_xen-install.xml:162(para)
|
||||
msgid "Make sure the host-uuid from <literal>xe pbd-list</literal> equals the uuid of the host you found previously:"
|
||||
msgid "Make sure the host-UUID from <literal>xe pbd-list</literal> equals the UUID of the host you found previously:"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/compute/section_xen-install.xml:168(para)
|
||||
@ -10111,7 +10111,7 @@ msgid "Create temporary files/directories:"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/compute/section_xapi-install-plugins.xml:28(para)
|
||||
msgid "Get the source from github. The example assumes the master branch is used. Amend the URL to match the version being used:"
|
||||
msgid "Get the source from GitHub. The example assumes the master branch is used. Amend the URL to match the version being used:"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/compute/section_xapi-install-plugins.xml:33(para)
|
||||
@ -10267,7 +10267,7 @@ msgid "Firewall"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/compute/section_compute-configure-xen.xml:45(para)
|
||||
msgid "If using nova-network, IPTables is supported: <placeholder-1/> Alternately, doing the isolation in Dom0: <placeholder-2/>"
|
||||
msgid "If using nova-network, iptables is supported: <placeholder-1/> Alternately, doing the isolation in Dom0: <placeholder-2/>"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/config-reference/compute/section_compute-configure-xen.xml:51(title)
|
||||
|
||||
@ -5,8 +5,8 @@
|
||||
msgid ""
|
||||
msgstr ""
|
||||
"Project-Id-Version: OpenStack Manuals\n"
|
||||
"POT-Creation-Date: 2014-08-15 05:33+0000\n"
|
||||
"PO-Revision-Date: 2014-08-14 15:39+0000\n"
|
||||
"POT-Creation-Date: 2014-08-15 18:55+0000\n"
|
||||
"PO-Revision-Date: 2014-08-15 18:44+0000\n"
|
||||
"Last-Translator: openstackjenkins <jenkins@openstack.org>\n"
|
||||
"Language-Team: German (http://www.transifex.com/projects/p/openstack-manuals-i18n/language/de/)\n"
|
||||
"MIME-Version: 1.0\n"
|
||||
@ -2262,7 +2262,7 @@ msgstr ""
|
||||
msgid ""
|
||||
"A platform that provides a suite of desktop environments that users may log "
|
||||
"in to receive a desktop experience from any location. This may provide "
|
||||
"general use, development, or even homogenous testing environments."
|
||||
"general use, development, or even homogeneous testing environments."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/glossary/glossary-terms.xml2372(glossterm)
|
||||
|
||||
@ -1,7 +1,7 @@
|
||||
msgid ""
|
||||
msgstr ""
|
||||
"Project-Id-Version: PACKAGE VERSION\n"
|
||||
"POT-Creation-Date: 2014-08-15 06:09+0000\n"
|
||||
"POT-Creation-Date: 2014-08-16 06:09+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"
|
||||
@ -1658,7 +1658,7 @@ msgid "Desktop-as-a-Service"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/glossary/glossary-terms.xml:2362(para)
|
||||
msgid "A platform that provides a suite of desktop environments that users may log in to receive a desktop experience from any location. This may provide general use, development, or even homogenous testing environments."
|
||||
msgid "A platform that provides a suite of desktop environments that users may log in to receive a desktop experience from any location. This may provide general use, development, or even homogeneous testing environments."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/glossary/glossary-terms.xml:2372(glossterm) ./doc/glossary/glossary-terms.xml:2374(primary)
|
||||
|
||||
@ -6,8 +6,8 @@
|
||||
msgid ""
|
||||
msgstr ""
|
||||
"Project-Id-Version: OpenStack Manuals\n"
|
||||
"POT-Creation-Date: 2014-08-15 05:33+0000\n"
|
||||
"PO-Revision-Date: 2014-08-14 15:39+0000\n"
|
||||
"POT-Creation-Date: 2014-08-15 18:55+0000\n"
|
||||
"PO-Revision-Date: 2014-08-15 18:44+0000\n"
|
||||
"Last-Translator: openstackjenkins <jenkins@openstack.org>\n"
|
||||
"Language-Team: Japanese (http://www.transifex.com/projects/p/openstack-manuals-i18n/language/ja/)\n"
|
||||
"MIME-Version: 1.0\n"
|
||||
@ -2263,7 +2263,7 @@ msgstr ""
|
||||
msgid ""
|
||||
"A platform that provides a suite of desktop environments that users may log "
|
||||
"in to receive a desktop experience from any location. This may provide "
|
||||
"general use, development, or even homogenous testing environments."
|
||||
"general use, development, or even homogeneous testing environments."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/glossary/glossary-terms.xml2372(glossterm)
|
||||
|
||||
@ -5,8 +5,8 @@
|
||||
msgid ""
|
||||
msgstr ""
|
||||
"Project-Id-Version: OpenStack Manuals\n"
|
||||
"POT-Creation-Date: 2014-08-15 05:33+0000\n"
|
||||
"PO-Revision-Date: 2014-08-14 15:39+0000\n"
|
||||
"POT-Creation-Date: 2014-08-15 18:55+0000\n"
|
||||
"PO-Revision-Date: 2014-08-15 18:44+0000\n"
|
||||
"Last-Translator: openstackjenkins <jenkins@openstack.org>\n"
|
||||
"Language-Team: Korean (Korea) (http://www.transifex.com/projects/p/openstack-manuals-i18n/language/ko_KR/)\n"
|
||||
"MIME-Version: 1.0\n"
|
||||
@ -2262,7 +2262,7 @@ msgstr ""
|
||||
msgid ""
|
||||
"A platform that provides a suite of desktop environments that users may log "
|
||||
"in to receive a desktop experience from any location. This may provide "
|
||||
"general use, development, or even homogenous testing environments."
|
||||
"general use, development, or even homogeneous testing environments."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/glossary/glossary-terms.xml2372(glossterm)
|
||||
|
||||
@ -1,7 +1,7 @@
|
||||
msgid ""
|
||||
msgstr ""
|
||||
"Project-Id-Version: PACKAGE VERSION\n"
|
||||
"POT-Creation-Date: 2014-08-07 06:04+0000\n"
|
||||
"POT-Creation-Date: 2014-08-16 06:09+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"
|
||||
@ -290,7 +290,7 @@ msgid "Both nodes should have the same hostname since the Networking scheduler w
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/high-availability-guide/ch_ha_aa_haproxy.xml:8(title)
|
||||
msgid "HAproxy nodes"
|
||||
msgid "HAProxy nodes"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/high-availability-guide/ch_ha_aa_haproxy.xml:10(para)
|
||||
@ -298,15 +298,15 @@ msgid "HAProxy is a very fast and reliable solution offering high availability,
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/high-availability-guide/ch_ha_aa_haproxy.xml:14(para)
|
||||
msgid "For installing HAproxy on your nodes, you should consider its <link href=\"http://haproxy.1wt.eu/#docs\">official documentation</link>. Also, you have to consider that this service should not be a single point of failure, so you need at least two nodes running HAproxy."
|
||||
msgid "For installing HAProxy on your nodes, you should consider its <link href=\"http://haproxy.1wt.eu/#docs\">official documentation</link>. Also, you have to consider that this service should not be a single point of failure, so you need at least two nodes running HAProxy."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/high-availability-guide/ch_ha_aa_haproxy.xml:17(para)
|
||||
msgid "Here is an example for HAproxy configuration file:"
|
||||
msgid "Here is an example for HAProxy configuration file:"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/high-availability-guide/ch_ha_aa_haproxy.xml:157(para)
|
||||
msgid "After each change of this file, you should restart HAproxy."
|
||||
msgid "After each change of this file, you should restart HAProxy."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/high-availability-guide/ch_ha_aa_controllers.xml:8(title)
|
||||
@ -1142,7 +1142,7 @@ msgid "API services"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/high-availability-guide/ha_aa_controllers/section_run_openstack_api_and_schedulers.xml:13(para)
|
||||
msgid "All OpenStack projects have an API service for controlling all the resources in the Cloud. In Active / Active mode, the most common setup is to scale-out these services on at least two nodes and use load balancing and virtual IP (with HAproxy & Keepalived in this setup)."
|
||||
msgid "All OpenStack projects have an API service for controlling all the resources in the Cloud. In Active / Active mode, the most common setup is to scale-out these services on at least two nodes and use load balancing and virtual IP (with HAProxy & Keepalived in this setup)."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/high-availability-guide/ha_aa_controllers/section_run_openstack_api_and_schedulers.xml:17(emphasis)
|
||||
@ -1462,7 +1462,7 @@ msgid "Here we are building a cluster of RabbitMQ nodes to construct a RabbitMQ
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/high-availability-guide/ha_aa_rabbitmq/section_configure_rabbitmq.xml:14(para)
|
||||
msgid "We consider that we run (at least) two RabbitMQ servers. To build a broker, we need to ensure that all nodes have the same erlang cookie file. To do so, stop RabbitMQ everywhere and copy the cookie from rabbit1 server to other server(s):"
|
||||
msgid "We consider that we run (at least) two RabbitMQ servers. To build a broker, we need to ensure that all nodes have the same Erlang cookie file. To do so, stop RabbitMQ everywhere and copy the cookie from rabbit1 server to other server(s):"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/high-availability-guide/ha_aa_rabbitmq/section_configure_rabbitmq.xml:19(para)
|
||||
|
||||
@ -4,9 +4,9 @@
|
||||
msgid ""
|
||||
msgstr ""
|
||||
"Project-Id-Version: OpenStack Manuals\n"
|
||||
"POT-Creation-Date: 2014-08-15 05:33+0000\n"
|
||||
"PO-Revision-Date: 2014-08-11 17:49+0000\n"
|
||||
"Last-Translator: Tomoyuki KATO <tomo@dream.daynight.jp>\n"
|
||||
"POT-Creation-Date: 2014-08-15 18:55+0000\n"
|
||||
"PO-Revision-Date: 2014-08-15 18:44+0000\n"
|
||||
"Last-Translator: openstackjenkins <jenkins@openstack.org>\n"
|
||||
"Language-Team: Japanese (http://www.transifex.com/projects/p/openstack-manuals-i18n/language/ja/)\n"
|
||||
"MIME-Version: 1.0\n"
|
||||
"Content-Type: text/plain; charset=UTF-8\n"
|
||||
@ -403,8 +403,8 @@ msgid ""
|
||||
msgstr "Networking スケジューラーが 1 つのノードに認識するよう、両方のノードが同じホスト名を持つべきです。たとえば、単一の L3 ノードに接続された仮想ルーターです。"
|
||||
|
||||
#: ./doc/high-availability-guide/ch_ha_aa_haproxy.xml8(title)
|
||||
msgid "HAproxy nodes"
|
||||
msgstr "HAproxy ノード"
|
||||
msgid "HAProxy nodes"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/high-availability-guide/ch_ha_aa_haproxy.xml10(para)
|
||||
msgid ""
|
||||
@ -417,19 +417,19 @@ msgstr "HAProxy は高可用性、負荷分散、TCP と HTTP ベースのアプ
|
||||
|
||||
#: ./doc/high-availability-guide/ch_ha_aa_haproxy.xml14(para)
|
||||
msgid ""
|
||||
"For installing HAproxy on your nodes, you should consider its <link "
|
||||
"For installing HAProxy on your nodes, you should consider its <link "
|
||||
"href=\"http://haproxy.1wt.eu/#docs\">official documentation</link>. Also, "
|
||||
"you have to consider that this service should not be a single point of "
|
||||
"failure, so you need at least two nodes running HAproxy."
|
||||
msgstr "ノードに HAproxy をインストールするために、<link href=\"http://haproxy.1wt.eu/#docs\">公式ドキュメント</link>を参照すべきです。また、このサービスが単一障害点にならないように、少なくとも 2 つのノードで HAproxy を実行すべきであることを考慮する必要があります。"
|
||||
"failure, so you need at least two nodes running HAProxy."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/high-availability-guide/ch_ha_aa_haproxy.xml17(para)
|
||||
msgid "Here is an example for HAproxy configuration file:"
|
||||
msgstr "これは HAproxy 設定ファイルの例です。"
|
||||
msgid "Here is an example for HAProxy configuration file:"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/high-availability-guide/ch_ha_aa_haproxy.xml157(para)
|
||||
msgid "After each change of this file, you should restart HAproxy."
|
||||
msgstr "このファイルをそれぞれ変更した後、HAproxy を再起動しなければいけません。"
|
||||
msgid "After each change of this file, you should restart HAProxy."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/high-availability-guide/ch_ha_aa_controllers.xml8(title)
|
||||
msgid "OpenStack controller nodes"
|
||||
@ -1702,8 +1702,8 @@ msgid ""
|
||||
"All OpenStack projects have an API service for controlling all the resources"
|
||||
" in the Cloud. In Active / Active mode, the most common setup is to scale-"
|
||||
"out these services on at least two nodes and use load balancing and virtual "
|
||||
"IP (with HAproxy & Keepalived in this setup)."
|
||||
msgstr "すべての OpenStack プロジェクトは、クラウドにあるすべてのリソースを制御するための API サービスを持ちます。アクティブ / アクティブモードの場合、最も一般的なセットアップ環境は、少なくとも 2 つのノードにこれらのサービスをスケールアウトし、(このセットアップで HAproxy と Keepalived を用いて) 負荷分散および仮想 IP を使用します。"
|
||||
"IP (with HAProxy & Keepalived in this setup)."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/high-availability-guide/ha_aa_controllers/section_run_openstack_api_and_schedulers.xml17(emphasis)
|
||||
msgid "Configure API OpenStack services"
|
||||
@ -2153,10 +2153,10 @@ msgstr "これから RabbitMQ ブローカーを構築するために RabbitMQ
|
||||
#: ./doc/high-availability-guide/ha_aa_rabbitmq/section_configure_rabbitmq.xml14(para)
|
||||
msgid ""
|
||||
"We consider that we run (at least) two RabbitMQ servers. To build a broker, "
|
||||
"we need to ensure that all nodes have the same erlang cookie file. To do so,"
|
||||
"we need to ensure that all nodes have the same Erlang cookie file. To do so,"
|
||||
" stop RabbitMQ everywhere and copy the cookie from rabbit1 server to other "
|
||||
"server(s):"
|
||||
msgstr "(少なくとも) 2 つの RabbitMQ サーバーを実行することを考えます。ブローカーを構築するために、すべてのノードが必ず同じ erlang クッキーファイルを持つ必要があります。そうするために、すべての RabbitMQ を停止し、クッキーを rabbit1 サーバーから他のサーバーにコピーします。"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/high-availability-guide/ha_aa_rabbitmq/section_configure_rabbitmq.xml19(para)
|
||||
msgid ""
|
||||
|
||||
@ -4,8 +4,8 @@
|
||||
msgid ""
|
||||
msgstr ""
|
||||
"Project-Id-Version: OpenStack Manuals\n"
|
||||
"POT-Creation-Date: 2014-08-15 05:33+0000\n"
|
||||
"PO-Revision-Date: 2014-08-14 21:58+0000\n"
|
||||
"POT-Creation-Date: 2014-08-15 18:55+0000\n"
|
||||
"PO-Revision-Date: 2014-08-15 18:44+0000\n"
|
||||
"Last-Translator: openstackjenkins <jenkins@openstack.org>\n"
|
||||
"Language-Team: French (http://www.transifex.com/projects/p/openstack-manuals-i18n/language/fr/)\n"
|
||||
"MIME-Version: 1.0\n"
|
||||
@ -50,7 +50,7 @@ msgid ""
|
||||
"us/library/cc766049(v=ws.10).aspx\">Sysprep</link> that must be run inside "
|
||||
"of a Windows guest to prepare it for use as a virtual machine image. On "
|
||||
"Windows, invoke sysprep, as follows: <placeholder-1/>"
|
||||
msgstr ""
|
||||
msgstr "Microsoft dispose d'un outil spécial dénommé <link href=\"http://technet.microsoft.com/en-us/library/cc766049(v=ws.10).aspx\">Sysprep</link> qui doit être lancé au sein d'un invité Windows pour le préparer à être utilisé en tant qu'image de machine virtuelle. Sur Windows, invoquez sysprep, comme suit: <placeholder-1/>"
|
||||
|
||||
#: ./doc/image-guide/section_windows-example.xml27(title)
|
||||
msgid "cloudbase-init"
|
||||
@ -61,8 +61,8 @@ msgid ""
|
||||
"<link href=\"http://www.cloudbase.it/cloud-init-for-windows-instances"
|
||||
"/\">cloudbase-init</link> is a Windows port of cloud-init that should be "
|
||||
"installed inside of the guest. The <link href=\"https://github.com/cloudbase"
|
||||
"/cloudbase-init\">source code</link> is available on github."
|
||||
msgstr "<link href=\"http://www.cloudbase.it/cloud-init-for-windows-instances/\">cloudbase-init</link> est un port Windows de cloud-init qui devrait être installé à l'intérieur du client. Le <link href=\"https://github.com/cloudbase/cloudbase-init\">code source</link> est disponible sur github."
|
||||
"/cloudbase-init\">source code</link> is available on GitHub."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/image-guide/section_windows-example.xml34(title)
|
||||
msgid "Jordan Rinke's OpenStack Windows resources"
|
||||
@ -1645,13 +1645,13 @@ msgstr "Nettoyage (enlever les informations d'adresse MAC)"
|
||||
|
||||
#: ./doc/image-guide/section_centos-example.xml307(para)
|
||||
msgid ""
|
||||
"The operating system records the MAC address of the virtual ethernet card in"
|
||||
"The operating system records the MAC address of the virtual Ethernet card in"
|
||||
" locations such as <filename>/etc/sysconfig/network-scripts/ifcfg-"
|
||||
"eth0</filename> and <filename>/etc/udev/rules.d/70-persistent-"
|
||||
"net.rules</filename> during the instance process. However, each time the "
|
||||
"image boots up, the virtual ethernet card will have a different MAC address,"
|
||||
"image boots up, the virtual Ethernet card will have a different MAC address,"
|
||||
" so this information must be deleted from the configuration file."
|
||||
msgstr "Le système d'exploitation enregistre l'adresse MAC de la carte ethernet virtuelle dans des endroits comme <filename>/etc/sysconfig/network-scripts/ifcfg-eth0</filename> et <filename>/etc/udev/rules.d/70-persistent-net.rules</filename> durant le processus de l'instance. Cependant, à chaque fois que l'image boot, la carte ethernet virtuelle aura une adresse MAC différente, donc cette information doit être supprimée du fichier de configuration."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/image-guide/section_centos-example.xml313(para)
|
||||
#: ./doc/image-guide/section_ubuntu-example.xml187(para)
|
||||
@ -1797,10 +1797,10 @@ msgstr "<link href=\"https://github.com/clalancette/oz/wiki\">Oz</link> est un o
|
||||
msgid ""
|
||||
"A full treatment of Oz is beyond the scope of this document, but we will "
|
||||
"provide an example. You can find additional examples of Oz template files on"
|
||||
" github at <link href=\"https://github.com/rackerjoe/oz-image-"
|
||||
" GitHub at <link href=\"https://github.com/rackerjoe/oz-image-"
|
||||
"build/tree/master/templates\">rackerjoe/oz-image-build/templates</link>. "
|
||||
"Here's how you would create a CentOS 6.4 image with Oz."
|
||||
msgstr "Un exposé complet de Oz sortirait du cadre de ce document, mais nous allons fournir un exemple. Vous pouvez trouver des exemples supplémentaires de fichiers modèles Oz sur github ici: <link href=\"https://github.com/rackerjoe/oz-image-build/tree/master/templates\">rackerjoe/oz-image-build/templates</link>. Voici comment vous pouvez créer une image CentOS 6.4 avec Oz."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/image-guide/ch_creating_images_automatically.xml34(para)
|
||||
msgid ""
|
||||
@ -2085,8 +2085,8 @@ msgid ""
|
||||
"Rackspace Cloud Builders maintains a list of pre-built images from various "
|
||||
"distributions (Red Hat, CentOS, Fedora, Ubuntu). Links to these images can "
|
||||
"be found at <link href=\"https://github.com/rackerjoe/oz-image-"
|
||||
"build\">rackerjoe/oz-image-build on Github</link>."
|
||||
msgstr "Rackspace Cloud Builders maintiennent une liste d'images pré-construites à partir de distributions variées (Red Hat, CentOS, Fedora, Ubuntu). Des liens sur ces images peuvent être trouvés sur <link href=\"https://github.com/rackerjoe/oz-image-build\">rackerjoe/oz-image-build on Github</link>."
|
||||
"build\">rackerjoe/oz-image-build on GitHub</link>."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/image-guide/ch_obtaining_images.xml103(title)
|
||||
msgid "Microsoft Windows images"
|
||||
@ -2242,7 +2242,7 @@ msgid ""
|
||||
"system. This option depends on your specific use case. If your virtual "
|
||||
"machine instances will be connected to the Internet, we recommend \"Install "
|
||||
"security updates automatically\"."
|
||||
msgstr ""
|
||||
msgstr "L'installeur Ubuntu vous demandera comment vous souhaitez gérer les mises à jour sur votre système. Cette option dépend de votre cas spécifique d'utilisation. Si vos instances de machines virtuelles seront reliées à Internet, nous recommandons l'option \"Installer les mises à jour de sécurité automatiquement\"."
|
||||
|
||||
#: ./doc/image-guide/section_ubuntu-example.xml80(title)
|
||||
msgid "Software selection: OpenSSH server"
|
||||
@ -2353,12 +2353,12 @@ msgstr "Vous pouvez modifier le nom du compte utilisé par cloud-init en éditan
|
||||
|
||||
#: ./doc/image-guide/section_ubuntu-example.xml182(para)
|
||||
msgid ""
|
||||
"The operating system records the MAC address of the virtual ethernet card in"
|
||||
"The operating system records the MAC address of the virtual Ethernet card in"
|
||||
" locations such as <filename>/etc/udev/rules.d/70-persistent-"
|
||||
"net.rules</filename> during the instance process. However, each time the "
|
||||
"image boots up, the virtual ethernet card will have a different MAC address,"
|
||||
"image boots up, the virtual Ethernet card will have a different MAC address,"
|
||||
" so this information must be deleted from the configuration file."
|
||||
msgstr "Le système d'exploitation enregistre l'adresse MAC de la carte ethernet virtuelle dans des endroits comme <filename>/etc/udev/rules.d/70-persistent-net.rules</filename> durant le fonctionnement de l'instance. Cependant, à chaque fois que l'image boot, la carte virtuelle ethernet possèdera une adresse MAC différente, donc cette information doit être supprimée du fichier de configuration."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/image-guide/section_ubuntu-example.xml194(para)
|
||||
msgid ""
|
||||
@ -2602,11 +2602,11 @@ msgstr "La manière la plus simple de supporter cela dans votre image est d'inst
|
||||
#: ./doc/image-guide/ch_openstack_images.xml161(para)
|
||||
msgid ""
|
||||
"If you cannot install <literal>cloud-initramfs-tools</literal>, Robert "
|
||||
"Plestenjak has a github project called <link "
|
||||
"Plestenjak has a GitHub project called <link "
|
||||
"href=\"https://github.com/flegmatik/linux-rootfs-resize\">linux-rootfs-"
|
||||
"resize</link> that contains scripts that update a ramdisk by using "
|
||||
"<placeholder-1/> so that the image resizes properly on boot."
|
||||
msgstr "Si vous ne pouvez pas installer <literal>cloud-initramfs-tools</literal>, Robert Plestenjak dispose d'un projet github appelé <link href=\"https://github.com/flegmatik/linux-rootfs-resize\">linux-rootfs-resize</link> qui contient les scripts qui mettent à jour un disque RAM en utilisant <placeholder-1/> afin que l'image soit redimensionnée proprement au démarrage."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/image-guide/ch_openstack_images.xml169(para)
|
||||
msgid ""
|
||||
@ -3198,11 +3198,11 @@ msgstr "Utilisez la commande <placeholder-1/> pour obtenir le numéro de port VN
|
||||
#: ./doc/image-guide/ch_creating_images_manually.xml172(para)
|
||||
msgid ""
|
||||
"In the example above, the guest <literal>centos-6.4</literal> uses VNC "
|
||||
"display <literal>:1</literal>, which corresponds to tcp port "
|
||||
"display <literal>:1</literal>, which corresponds to TCP port "
|
||||
"<literal>5901</literal>. You should be able to connect to a VNC client "
|
||||
"running on your local machine to display :1 on the remote machine and step "
|
||||
"through the installation process."
|
||||
msgstr "Dans l'exemple au-dessus, l'invité <literal>centos-6.4</literal> utilise l'affichage VNC <literal>:1</literal>, qui correspond au port tcp <literal>5901</literal>. Vous devriez pouvoir vous connecter à un client VNC fonctionnant sur votre machine locale pour afficher :1 sur la machine distante et continuer à travers les étapes du processus d'installation."
|
||||
msgstr ""
|
||||
|
||||
#. Put one translator per line, in the form of NAME <EMAIL>, YEAR1, YEAR2
|
||||
#: ./doc/image-guide/ch_creating_images_manually.xml0(None)
|
||||
|
||||
@ -1,7 +1,7 @@
|
||||
msgid ""
|
||||
msgstr ""
|
||||
"Project-Id-Version: PACKAGE VERSION\n"
|
||||
"POT-Creation-Date: 2014-08-15 06:09+0000\n"
|
||||
"POT-Creation-Date: 2014-08-16 06:09+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"
|
||||
@ -38,7 +38,7 @@ msgid "cloudbase-init"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/image-guide/section_windows-example.xml:28(para)
|
||||
msgid "<link href=\"http://www.cloudbase.it/cloud-init-for-windows-instances/\">cloudbase-init</link> is a Windows port of cloud-init that should be installed inside of the guest. The <link href=\"https://github.com/cloudbase/cloudbase-init\">source code</link> is available on github."
|
||||
msgid "<link href=\"http://www.cloudbase.it/cloud-init-for-windows-instances/\">cloudbase-init</link> is a Windows port of cloud-init that should be installed inside of the guest. The <link href=\"https://github.com/cloudbase/cloudbase-init\">source code</link> is available on GitHub."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/image-guide/section_windows-example.xml:34(title)
|
||||
@ -1110,7 +1110,7 @@ msgid "Clean up (remove MAC address details)"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/image-guide/section_centos-example.xml:307(para)
|
||||
msgid "The operating system records the MAC address of the virtual ethernet card in locations such as <filename>/etc/sysconfig/network-scripts/ifcfg-eth0</filename> and <filename>/etc/udev/rules.d/70-persistent-net.rules</filename> during the instance process. However, each time the image boots up, the virtual ethernet card will have a different MAC address, so this information must be deleted from the configuration file."
|
||||
msgid "The operating system records the MAC address of the virtual Ethernet card in locations such as <filename>/etc/sysconfig/network-scripts/ifcfg-eth0</filename> and <filename>/etc/udev/rules.d/70-persistent-net.rules</filename> during the instance process. However, each time the image boots up, the virtual Ethernet card will have a different MAC address, so this information must be deleted from the configuration file."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/image-guide/section_centos-example.xml:313(para) ./doc/image-guide/section_ubuntu-example.xml:187(para)
|
||||
@ -1226,7 +1226,7 @@ msgid "<link href=\"https://github.com/clalancette/oz/wiki\">Oz</link> is a comm
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/image-guide/ch_creating_images_automatically.xml:27(para)
|
||||
msgid "A full treatment of Oz is beyond the scope of this document, but we will provide an example. You can find additional examples of Oz template files on github at <link href=\"https://github.com/rackerjoe/oz-image-build/tree/master/templates\">rackerjoe/oz-image-build/templates</link>. Here's how you would create a CentOS 6.4 image with Oz."
|
||||
msgid "A full treatment of Oz is beyond the scope of this document, but we will provide an example. You can find additional examples of Oz template files on GitHub at <link href=\"https://github.com/rackerjoe/oz-image-build/tree/master/templates\">rackerjoe/oz-image-build/templates</link>. Here's how you would create a CentOS 6.4 image with Oz."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/image-guide/ch_creating_images_automatically.xml:34(para)
|
||||
@ -1410,7 +1410,7 @@ msgid "Rackspace Cloud Builders (multiple distros) images"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/image-guide/ch_obtaining_images.xml:97(para)
|
||||
msgid "Rackspace Cloud Builders maintains a list of pre-built images from various distributions (Red Hat, CentOS, Fedora, Ubuntu). Links to these images can be found at <link href=\"https://github.com/rackerjoe/oz-image-build\">rackerjoe/oz-image-build on Github</link>."
|
||||
msgid "Rackspace Cloud Builders maintains a list of pre-built images from various distributions (Red Hat, CentOS, Fedora, Ubuntu). Links to these images can be found at <link href=\"https://github.com/rackerjoe/oz-image-build\">rackerjoe/oz-image-build on GitHub</link>."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/image-guide/ch_obtaining_images.xml:103(title)
|
||||
@ -1586,7 +1586,7 @@ msgid "You can change the name of the account used by cloud-init by editing the
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/image-guide/section_ubuntu-example.xml:182(para)
|
||||
msgid "The operating system records the MAC address of the virtual ethernet card in locations such as <filename>/etc/udev/rules.d/70-persistent-net.rules</filename> during the instance process. However, each time the image boots up, the virtual ethernet card will have a different MAC address, so this information must be deleted from the configuration file."
|
||||
msgid "The operating system records the MAC address of the virtual Ethernet card in locations such as <filename>/etc/udev/rules.d/70-persistent-net.rules</filename> during the instance process. However, each time the image boots up, the virtual Ethernet card will have a different MAC address, so this information must be deleted from the configuration file."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/image-guide/section_ubuntu-example.xml:194(para)
|
||||
@ -1746,7 +1746,7 @@ msgid "The simplest way to support this in your image is to install the <link hr
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/image-guide/ch_openstack_images.xml:161(para)
|
||||
msgid "If you cannot install <literal>cloud-initramfs-tools</literal>, Robert Plestenjak has a github project called <link href=\"https://github.com/flegmatik/linux-rootfs-resize\">linux-rootfs-resize</link> that contains scripts that update a ramdisk by using <placeholder-1/> so that the image resizes properly on boot."
|
||||
msgid "If you cannot install <literal>cloud-initramfs-tools</literal>, Robert Plestenjak has a GitHub project called <link href=\"https://github.com/flegmatik/linux-rootfs-resize\">linux-rootfs-resize</link> that contains scripts that update a ramdisk by using <placeholder-1/> so that the image resizes properly on boot."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/image-guide/ch_openstack_images.xml:169(para)
|
||||
@ -2100,7 +2100,7 @@ msgid "Use the <placeholder-1/> command to get the VNC port number."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/image-guide/ch_creating_images_manually.xml:172(para)
|
||||
msgid "In the example above, the guest <literal>centos-6.4</literal> uses VNC display <literal>:1</literal>, which corresponds to tcp port <literal>5901</literal>. You should be able to connect to a VNC client running on your local machine to display :1 on the remote machine and step through the installation process."
|
||||
msgid "In the example above, the guest <literal>centos-6.4</literal> uses VNC display <literal>:1</literal>, which corresponds to TCP port <literal>5901</literal>. You should be able to connect to a VNC client running on your local machine to display :1 on the remote machine and step through the installation process."
|
||||
msgstr ""
|
||||
|
||||
#. Put one translator per line, in the form of NAME <EMAIL>, YEAR1, YEAR2
|
||||
|
||||
@ -5,8 +5,8 @@
|
||||
msgid ""
|
||||
msgstr ""
|
||||
"Project-Id-Version: OpenStack Manuals\n"
|
||||
"POT-Creation-Date: 2014-08-15 05:33+0000\n"
|
||||
"PO-Revision-Date: 2014-08-14 21:58+0000\n"
|
||||
"POT-Creation-Date: 2014-08-15 18:55+0000\n"
|
||||
"PO-Revision-Date: 2014-08-15 18:44+0000\n"
|
||||
"Last-Translator: openstackjenkins <jenkins@openstack.org>\n"
|
||||
"Language-Team: Japanese (http://www.transifex.com/projects/p/openstack-manuals-i18n/language/ja/)\n"
|
||||
"MIME-Version: 1.0\n"
|
||||
@ -62,8 +62,8 @@ msgid ""
|
||||
"<link href=\"http://www.cloudbase.it/cloud-init-for-windows-instances"
|
||||
"/\">cloudbase-init</link> is a Windows port of cloud-init that should be "
|
||||
"installed inside of the guest. The <link href=\"https://github.com/cloudbase"
|
||||
"/cloudbase-init\">source code</link> is available on github."
|
||||
msgstr "<link href=\"http://www.cloudbase.it/cloud-init-for-windows-instances/\">cloudbase-init</link> は cloud-init の Windows 移植版です。ゲスト内にインストールします。<link href=\"https://github.com/cloudbase/cloudbase-init\">ソースコード</link> が github に公開されています。"
|
||||
"/cloudbase-init\">source code</link> is available on GitHub."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/image-guide/section_windows-example.xml34(title)
|
||||
msgid "Jordan Rinke's OpenStack Windows resources"
|
||||
@ -1646,13 +1646,13 @@ msgstr "クリーンアップ (MAC アドレスの詳細の削除)"
|
||||
|
||||
#: ./doc/image-guide/section_centos-example.xml307(para)
|
||||
msgid ""
|
||||
"The operating system records the MAC address of the virtual ethernet card in"
|
||||
"The operating system records the MAC address of the virtual Ethernet card in"
|
||||
" locations such as <filename>/etc/sysconfig/network-scripts/ifcfg-"
|
||||
"eth0</filename> and <filename>/etc/udev/rules.d/70-persistent-"
|
||||
"net.rules</filename> during the instance process. However, each time the "
|
||||
"image boots up, the virtual ethernet card will have a different MAC address,"
|
||||
"image boots up, the virtual Ethernet card will have a different MAC address,"
|
||||
" so this information must be deleted from the configuration file."
|
||||
msgstr "オペレーティングシステムは、インスタンスの動作中、<filename>/etc/sysconfig/network-scripts/ifcfg-eth0</filename> や <filename>/etc/udev/rules.d/70-persistent-net.rules</filename> などの場所に、仮想 NIC の MAC アドレスを記録します。しかしながら、イメージが起動するたびに、仮想 NIC が別の MAC アドレスを持ちます。そのため、この情報は設定ファイルから削除する必要があります。"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/image-guide/section_centos-example.xml313(para)
|
||||
#: ./doc/image-guide/section_ubuntu-example.xml187(para)
|
||||
@ -1798,10 +1798,10 @@ msgstr "<link href=\"https://github.com/clalancette/oz/wiki\">Oz</link> は、
|
||||
msgid ""
|
||||
"A full treatment of Oz is beyond the scope of this document, but we will "
|
||||
"provide an example. You can find additional examples of Oz template files on"
|
||||
" github at <link href=\"https://github.com/rackerjoe/oz-image-"
|
||||
" GitHub at <link href=\"https://github.com/rackerjoe/oz-image-"
|
||||
"build/tree/master/templates\">rackerjoe/oz-image-build/templates</link>. "
|
||||
"Here's how you would create a CentOS 6.4 image with Oz."
|
||||
msgstr "Oz の全機能は、このドキュメントの範囲を超えていますが、例を示します。github の <link href=\"https://github.com/rackerjoe/oz-image-build/tree/master/templates\">rackerjoe/oz-image-build/templates</link> に Oz テンプレートファイルの別の例があります。これは、Oz を用いて CentOS 6.4 イメージを作成する方法です。"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/image-guide/ch_creating_images_automatically.xml34(para)
|
||||
msgid ""
|
||||
@ -2086,8 +2086,8 @@ msgid ""
|
||||
"Rackspace Cloud Builders maintains a list of pre-built images from various "
|
||||
"distributions (Red Hat, CentOS, Fedora, Ubuntu). Links to these images can "
|
||||
"be found at <link href=\"https://github.com/rackerjoe/oz-image-"
|
||||
"build\">rackerjoe/oz-image-build on Github</link>."
|
||||
msgstr "Rackspace Cloud Builders は、さまざまなディストリビューション（Red Hat、CentOS、Fedora、Ubuntu）の構築済みイメージの一覧を作成しています。これらのイメージへのリンクが <link href=\"https://github.com/rackerjoe/oz-image-build\">GitHub の rackerjoe/oz-image-build</link> にあります。"
|
||||
"build\">rackerjoe/oz-image-build on GitHub</link>."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/image-guide/ch_obtaining_images.xml103(title)
|
||||
msgid "Microsoft Windows images"
|
||||
@ -2354,12 +2354,12 @@ msgstr "<filename>/etc/cloud/cloud.cfg</filename> ファイルを編集し、別
|
||||
|
||||
#: ./doc/image-guide/section_ubuntu-example.xml182(para)
|
||||
msgid ""
|
||||
"The operating system records the MAC address of the virtual ethernet card in"
|
||||
"The operating system records the MAC address of the virtual Ethernet card in"
|
||||
" locations such as <filename>/etc/udev/rules.d/70-persistent-"
|
||||
"net.rules</filename> during the instance process. However, each time the "
|
||||
"image boots up, the virtual ethernet card will have a different MAC address,"
|
||||
"image boots up, the virtual Ethernet card will have a different MAC address,"
|
||||
" so this information must be deleted from the configuration file."
|
||||
msgstr "オペレーティングシステムは、インスタンスの動作中、<filename>/etc/udev/rules.d/70-persistent-net.rules</filename> などの場所に、仮想 NIC の MAC アドレスを記録します。しかしながら、イメージが起動するたびに、仮想 NIC が別の MAC アドレスを持ちます。そのため、この情報は設定ファイルから削除する必要があります。"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/image-guide/section_ubuntu-example.xml194(para)
|
||||
msgid ""
|
||||
@ -2603,11 +2603,11 @@ msgstr "これをサポートする最も簡単な方法は、<link href=\"https
|
||||
#: ./doc/image-guide/ch_openstack_images.xml161(para)
|
||||
msgid ""
|
||||
"If you cannot install <literal>cloud-initramfs-tools</literal>, Robert "
|
||||
"Plestenjak has a github project called <link "
|
||||
"Plestenjak has a GitHub project called <link "
|
||||
"href=\"https://github.com/flegmatik/linux-rootfs-resize\">linux-rootfs-"
|
||||
"resize</link> that contains scripts that update a ramdisk by using "
|
||||
"<placeholder-1/> so that the image resizes properly on boot."
|
||||
msgstr "<literal>cloud-initramfs-tools</literal> をインストールできない場合、Robert Plestenjak 氏が <link href=\"https://github.com/flegmatik/linux-rootfs-resize\">linux-rootfs-resize</link> という github プロジェクトを持っています。これは、イメージの起動時に正しくリサイズされるよう、<placeholder-1/> を使用してラムディスクを更新するスクリプトを含みます。"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/image-guide/ch_openstack_images.xml169(para)
|
||||
msgid ""
|
||||
@ -3199,11 +3199,11 @@ msgstr "<placeholder-1/> コマンドを使用して、VNC ポート番号を取
|
||||
#: ./doc/image-guide/ch_creating_images_manually.xml172(para)
|
||||
msgid ""
|
||||
"In the example above, the guest <literal>centos-6.4</literal> uses VNC "
|
||||
"display <literal>:1</literal>, which corresponds to tcp port "
|
||||
"display <literal>:1</literal>, which corresponds to TCP port "
|
||||
"<literal>5901</literal>. You should be able to connect to a VNC client "
|
||||
"running on your local machine to display :1 on the remote machine and step "
|
||||
"through the installation process."
|
||||
msgstr "上の例では、ゲスト <literal>centos-6.4</literal> が VNC ディスプレイ <literal>:1</literal> を使用しています。これは、TCP ポート <literal>5901</literal> に対応します。ローカルマシンの VNC クライアントがリモートマシンのディスプレイ :1 に接続して、インストールプロセスを実行できるでしょう。"
|
||||
msgstr ""
|
||||
|
||||
#. Put one translator per line, in the form of NAME <EMAIL>, YEAR1, YEAR2
|
||||
#: ./doc/image-guide/ch_creating_images_manually.xml0(None)
|
||||
|
||||
@ -1,7 +1,7 @@
|
||||
msgid ""
|
||||
msgstr ""
|
||||
"Project-Id-Version: PACKAGE VERSION\n"
|
||||
"POT-Creation-Date: 2014-08-15 06:09+0000\n"
|
||||
"POT-Creation-Date: 2014-08-16 06:09+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"
|
||||
@ -13,14 +13,147 @@ msgstr ""
|
||||
msgid "Networking architecture"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/networking-guide/ch_networking-architecture.xml:8(para) ./doc/networking-guide/ch_scalability-HA.xml:8(para) ./doc/networking-guide/section_ha-dvr.xml:12(para) ./doc/networking-guide/section_ha-l3.xml:12(para) ./doc/networking-guide/section_intro-namespaces.xml:12(para) ./doc/networking-guide/section_ha-dhcp.xml:12(para) ./doc/networking-guide/section_architecture-overview.xml:12(para) ./doc/networking-guide/section_intro-routers.xml:12(para) ./doc/networking-guide/section_intro-tunnel.xml:12(para) ./doc/networking-guide/ch_deployment.xml:8(para) ./doc/networking-guide/section_architecture-plug-in.xml:12(para) ./doc/networking-guide/section_intro-firewalls.xml:12(para) ./doc/networking-guide/section_intro-switches.xml:12(para) ./doc/networking-guide/section_intro-layers.xml:12(para) ./doc/networking-guide/ch_debugging.xml:8(para) ./doc/networking-guide/ch_networking-data-model.xml:12(para) ./doc/networking-guide/section_architecture-agents.xml:12(para) ./doc/networking-guide/ch_advanced.xml:8(para) ./doc/networking-guide/ch_plugins.xml:8(para) ./doc/networking-guide/section_architecture-server.xml:12(para)
|
||||
msgid "Bacon ipsum dolor sit amet biltong meatloaf andouille, turducken bresaola pork belly beef ribs ham hock capicola tail prosciutto landjaeger meatball pork loin. Swine turkey jowl, porchetta doner boudin meatloaf. Shoulder capicola prosciutto, shank landjaeger short ribs sirloin turducken pork belly boudin frankfurter chuck. Salami shankle bresaola cow filet mignon ham hock shank."
|
||||
#: ./doc/networking-guide/ch_networking-architecture.xml:8(para)
|
||||
msgid "A standard network architecture design includes a cloud controller host, a network gateway host, and a number of hypervisors for hosting virtual machines. The cloud controller and network gateway can be on the same host. However, if you expect VMs to send significant traffic to or from the Internet, a dedicated network gateway host helps avoid CPU contention between the <systemitem class=\"service\">neutron-l3-agent</systemitem> and other OpenStack services that forward packets."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/networking-guide/ch_networking-architecture.xml:18(para)
|
||||
msgid "You can run OpenStack Networking across multiple physical devices. It is also possible to run all service daemons on a single physical host for evaluation purposes, however this is not generally robust enough for production purposes. For greater redundancy, you can run each service on a dedicated physical host and replicate any essential services across multiple hosts."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/networking-guide/ch_networking-architecture.xml:26(para)
|
||||
msgid "For more information about networking architecture options, see the <link href=\"http://docs.openstack.org/openstack-ops/content/network_design.html\">Network Design</link> section of the <citetitle>OpenStack Operations Guide</citetitle>."
|
||||
msgstr ""
|
||||
|
||||
#. <mediaobject>
|
||||
#. <imageobject>
|
||||
#. <imagedata scale="50" fileref="../../common/figures/Neutron-PhysNet-Diagram.png"/>
|
||||
#. </imageobject>
|
||||
#. </mediaobject>
|
||||
#: ./doc/networking-guide/ch_networking-architecture.xml:39(para)
|
||||
msgid "A standard OpenStack Networking deployment usually includes one or more of the following physical networks:"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/networking-guide/ch_networking-architecture.xml:47(caption)
|
||||
msgid "General distinct physical data center networks"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/networking-guide/ch_networking-architecture.xml:53(th)
|
||||
msgid "Network"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/networking-guide/ch_networking-architecture.xml:54(th) ./doc/networking-guide/ch_advanced.xml:58(th) ./doc/networking-guide/ch_advanced.xml:149(th) ./doc/networking-guide/ch_advanced.xml:274(th) ./doc/networking-guide/ch_advanced.xml:332(th) ./doc/networking-guide/ch_advanced.xml:632(th) ./doc/networking-guide/ch_advanced.xml:675(th) ./doc/networking-guide/ch_advanced.xml:886(th) ./doc/networking-guide/ch_advanced.xml:1008(th) ./doc/networking-guide/ch_advanced.xml:1076(th) ./doc/networking-guide/ch_advanced.xml:1197(th) ./doc/networking-guide/ch_advanced.xml:1512(th) ./doc/networking-guide/ch_advanced.xml:1601(th) ./doc/networking-guide/ch_advanced.xml:1642(th)
|
||||
msgid "Description"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/networking-guide/ch_networking-architecture.xml:59(emphasis)
|
||||
msgid "Management network"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/networking-guide/ch_networking-architecture.xml:61(td)
|
||||
msgid "Provides internal communication between OpenStack components. IP addresses on this network should be reachable only within the data center."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/networking-guide/ch_networking-architecture.xml:67(emphasis)
|
||||
msgid "Data network"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/networking-guide/ch_networking-architecture.xml:69(td)
|
||||
msgid "Provides VM data communication within the cloud deployment. The IP addressing requirements of this network depend on the Networking plug-in that is used."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/networking-guide/ch_networking-architecture.xml:76(emphasis)
|
||||
msgid "External network"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/networking-guide/ch_networking-architecture.xml:78(td)
|
||||
msgid "Provides VMs with Internet access in some deployment scenarios. Anyone on the Internet can reach IP addresses on this network."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/networking-guide/ch_networking-architecture.xml:84(emphasis)
|
||||
msgid "API network"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/networking-guide/ch_networking-architecture.xml:86(td)
|
||||
msgid "Exposes all OpenStack APIs, including the Networking API, to tenants. IP addresses on this network should be reachable by anyone on the Internet. The API network might be the same as the external network, because it is possible to create an external-network subnet that has allocated IP ranges that use less than the full range of IP addresses in an IP block."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/networking-guide/ch_networking-architecture.xml:101(title)
|
||||
msgid "Tenant and provider networks"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/networking-guide/ch_networking-architecture.xml:102(para)
|
||||
msgid "The following diagram presents an overview of the tenant and provider network types, and illustrates how they interact within the overall Networking topology:"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/networking-guide/ch_networking-architecture.xml:119(title)
|
||||
msgid "Tenant networks"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/networking-guide/ch_networking-architecture.xml:120(para)
|
||||
msgid "Users create tenant networks for connectivity within projects; they are fully isolated by default and are not shared with other projects. Networking supports a range of tenant network types:"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/networking-guide/ch_networking-architecture.xml:128(term) ./doc/networking-guide/section_plugins-ml2.xml:23(term)
|
||||
msgid "Flat"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/networking-guide/ch_networking-architecture.xml:130(para)
|
||||
msgid "All instances reside on the same network, which can also be shared with the hosts. No VLAN tagging or other network segregation takes place."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/networking-guide/ch_networking-architecture.xml:137(term) ./doc/networking-guide/section_plugins-ml2.xml:52(para)
|
||||
msgid "Local"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/networking-guide/ch_networking-architecture.xml:139(para)
|
||||
msgid "Instances reside on the local compute host and are effectively isolated from any external networks."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/networking-guide/ch_networking-architecture.xml:145(term) ./doc/networking-guide/section_intro-tunnel.xml:25(term) ./doc/networking-guide/section_intro-tunnel.xml:43(term) ./doc/networking-guide/section_plugins-ml2.xml:29(term)
|
||||
msgid "VLAN"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/networking-guide/ch_networking-architecture.xml:147(para)
|
||||
msgid "Networking allows users to create multiple provider or tenant networks using VLAN IDs (802.1Q tagged) that correspond to VLANs present in the physical network. This allows instances to communicate with each other across the environment. They can also communicate with dedicated servers, firewalls, load balancers, and other networking infrastructure on the same layer 2 VLAN."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/networking-guide/ch_networking-architecture.xml:157(term)
|
||||
msgid "VXLAN and GRE"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/networking-guide/ch_networking-architecture.xml:159(para)
|
||||
msgid "VXLAN and GRE use network overlays to support private communication between instances. A Networking router is required to enable traffic to traverse outside of the GRE or VXLAN tenant network. A router is also required to connect directly-connected tenant networks with external networks, including the Internet; the router provides the ability to connect to instances directly from an external network using floating IP addresses."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/networking-guide/ch_networking-architecture.xml:172(title) ./doc/networking-guide/ch_advanced.xml:28(title)
|
||||
msgid "Provider networks"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/networking-guide/ch_networking-architecture.xml:173(para)
|
||||
msgid "The OpenStack administrator creates provider networks. These networks map to existing physical networks in the data center. Useful network types in this category are flat (untagged) and VLAN (802.1Q tagged). It is possible to allow provider networks to be shared among tenants as part of the network creation process."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/networking-guide/ch_networking-architecture.xml:181(title)
|
||||
msgid "VMware NSX integration"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/networking-guide/ch_networking-architecture.xml:182(para)
|
||||
msgid "OpenStack Networking uses the NSX plug-in for Networking to integrate with an existing VMware vCenter deployment. When installed on the network nodes, the NSX plug-in enables a NSX controller to centrally manage configuration settings and push them to managed network nodes. Network nodes are considered managed when they're added as hypervisors to the NSX controller."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/networking-guide/ch_networking-architecture.xml:188(para)
|
||||
msgid "The following diagram depicts an example NSX deployment and illustrates the route inter-VM traffic takes between separate Compute nodes. Note the placement of the VMware NSX plug-in and the <systemitem class=\"service\">neutron-server</systemitem> service on the network node. The NSX controller features centrally with a green line to the network node to indicate the management relationship:"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/networking-guide/ch_scalability-HA.xml:7(title)
|
||||
msgid "Scalability and high availability"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/networking-guide/ch_scalability-HA.xml:8(para) ./doc/networking-guide/section_ha-dvr.xml:12(para) ./doc/networking-guide/section_ha-l3.xml:12(para) ./doc/networking-guide/section_intro-namespaces.xml:12(para) ./doc/networking-guide/section_ha-dhcp.xml:12(para) ./doc/networking-guide/section_architecture-overview.xml:12(para) ./doc/networking-guide/section_intro-routers.xml:12(para) ./doc/networking-guide/section_intro-tunnel.xml:12(para) ./doc/networking-guide/section_intro-firewalls.xml:12(para) ./doc/networking-guide/section_intro-switches.xml:12(para) ./doc/networking-guide/section_intro-layers.xml:12(para) ./doc/networking-guide/ch_debugging.xml:8(para) ./doc/networking-guide/ch_networking-data-model.xml:12(para) ./doc/networking-guide/ch_advanced.xml:8(para) ./doc/networking-guide/ch_plugins.xml:8(para) ./doc/networking-guide/section_architecture-server.xml:12(para)
|
||||
msgid "Bacon ipsum dolor sit amet biltong meatloaf andouille, turducken bresaola pork belly beef ribs ham hock capicola tail prosciutto landjaeger meatball pork loin. Swine turkey jowl, porchetta doner boudin meatloaf. Shoulder capicola prosciutto, shank landjaeger short ribs sirloin turducken pork belly boudin frankfurter chuck. Salami shankle bresaola cow filet mignon ham hock shank."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/networking-guide/section_plugins-proprietary.xml:11(title) ./doc/networking-guide/section_plugins-ml2.xml:89(term)
|
||||
msgid "Proprietary"
|
||||
msgstr ""
|
||||
@ -45,7 +178,7 @@ msgstr ""
|
||||
msgid "DHCP Agents"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/networking-guide/section_architecture-overview.xml:11(title) ./doc/networking-guide/section_plugins-ml2.xml:14(title) ./doc/networking-guide/section_architecture-agents.xml:22(title)
|
||||
#: ./doc/networking-guide/section_architecture-overview.xml:11(title) ./doc/networking-guide/section_plugins-ml2.xml:14(title) ./doc/networking-guide/section_architecture-agents.xml:71(title)
|
||||
msgid "Overview"
|
||||
msgstr ""
|
||||
|
||||
@ -73,14 +206,10 @@ msgstr ""
|
||||
msgid "Tunnel (segmentation) technologies"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/networking-guide/section_intro-tunnel.xml:22(title) ./doc/networking-guide/section_architecture-agents.xml:28(title)
|
||||
#: ./doc/networking-guide/section_intro-tunnel.xml:22(title) ./doc/networking-guide/section_architecture-agents.xml:77(title)
|
||||
msgid "Layer 2"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/networking-guide/section_intro-tunnel.xml:25(term) ./doc/networking-guide/section_intro-tunnel.xml:43(term) ./doc/networking-guide/section_plugins-ml2.xml:29(term)
|
||||
msgid "VLAN"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/networking-guide/section_intro-tunnel.xml:34(title)
|
||||
msgid "Layer 3"
|
||||
msgstr ""
|
||||
@ -105,10 +234,6 @@ msgstr ""
|
||||
msgid "Network type drivers"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/networking-guide/section_plugins-ml2.xml:23(term)
|
||||
msgid "Flat"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/networking-guide/section_plugins-ml2.xml:41(term)
|
||||
msgid "VXLAN"
|
||||
msgstr ""
|
||||
@ -117,10 +242,6 @@ msgstr ""
|
||||
msgid "Tenant network types"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/networking-guide/section_plugins-ml2.xml:52(para)
|
||||
msgid "Local"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/networking-guide/section_plugins-ml2.xml:53(para)
|
||||
msgid "VLAN, VLAN ID ranges"
|
||||
msgstr ""
|
||||
@ -141,11 +262,11 @@ msgstr ""
|
||||
msgid "Mechanisms"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/networking-guide/section_plugins-ml2.xml:65(term) ./doc/networking-guide/section_architecture-agents.xml:31(term)
|
||||
#: ./doc/networking-guide/section_plugins-ml2.xml:65(term) ./doc/networking-guide/section_architecture-agents.xml:80(term)
|
||||
msgid "Linux Bridge"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/networking-guide/section_plugins-ml2.xml:71(term) ./doc/networking-guide/section_architecture-agents.xml:38(term)
|
||||
#: ./doc/networking-guide/section_plugins-ml2.xml:71(term) ./doc/networking-guide/section_architecture-agents.xml:87(term)
|
||||
msgid "Open vSwitch"
|
||||
msgstr ""
|
||||
|
||||
@ -241,14 +362,45 @@ msgstr ""
|
||||
msgid "Creation of document."
|
||||
msgstr ""
|
||||
|
||||
#. When image changes, this message will be marked fuzzy or untranslated for you.
|
||||
#. It doesn't matter what you translate it to: it's not used at all.
|
||||
#: ./doc/networking-guide/ch_deployment.xml:17(None)
|
||||
msgid "@@image: '../common/figures/Neutron-PhysNet-Diagram.png'; md5=ea581fd58c57da1a6c9512b82027a195"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/networking-guide/ch_deployment.xml:7(title)
|
||||
msgid "Deployment"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/networking-guide/ch_deployment.xml:8(para)
|
||||
msgid "OpenStack Networking provides an extreme amount of flexibility when deploying networking in support of a compute environment. As a result, the exact layout of a deployment will depend on a combination of expected workloads, expected scale, and available hardware."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/networking-guide/ch_deployment.xml:20(para)
|
||||
msgid "For demonstration purposes, this chapter concentrates on a networking deployment that consists of these types of nodes:"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/networking-guide/ch_deployment.xml:26(para)
|
||||
msgid "<emphasis>Service node:</emphasis> The service node exposes the networking API to clients and handles incoming requests before forwarding them to a message queue to be actioned by the other nodes. The service node hosts both the networking service itself and the active networking plug-in. In environments that use controller nodes to host the client-facing APIs and schedulers for all services, the controller node would also fulfill the role of service node as it is applied in this chapter."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/networking-guide/ch_deployment.xml:37(para)
|
||||
msgid "<emphasis>Network node:</emphasis> The network node handles the majority of the networking workload. It hosts the DHCP agent, the Layer-3 (L3) agent, the Layer-2 (L2) agent, and the metadata proxy. In addition to plug-ins that require an agent, it runs an instance of the plug-in agent (as do all other systems that handle data packets in an environment where such plug-ins are in use). Both the Open vSwitch and Linux Bridge mechanism drivers include an agent."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/networking-guide/ch_deployment.xml:48(para)
|
||||
msgid "<emphasis>Compute node:</emphasis> The compute node hosts the compute instances themselves. To connect compute instances to the networking services, compute nodes must also run the L2 agent. Like all other systems that handle data packets it must also run an instance of the plug-in agent."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/networking-guide/section_architecture-plug-in.xml:11(title)
|
||||
msgid "Plug-ins"
|
||||
msgstr ""
|
||||
|
||||
#. This section has not yet been edited. LKB
|
||||
#: ./doc/networking-guide/section_architecture-plug-in.xml:13(para)
|
||||
msgid "The legacy networking (nova-network) implementation assumed a basic model of isolation through Linux VLANs and IP tables. Networking introduces support for vendor plug-ins, which offer a custom back-end implementation of the Networking API. A plugin can use a variety of technologies to implement the logical API requests. Some networking plug-ins might use basic Linux VLANs and IP tables, while others might use more advanced technologies, such as L2-in-L3 tunneling or OpenFlow, to provide similar benefits."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/networking-guide/section_intro-firewalls.xml:11(title) ./doc/networking-guide/ch_advanced.xml:1066(caption)
|
||||
msgid "Firewalls"
|
||||
msgstr ""
|
||||
@ -341,35 +493,80 @@ msgstr ""
|
||||
msgid "Agents"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/networking-guide/section_architecture-agents.xml:23(para)
|
||||
#. This section has not yet been edited. LKB
|
||||
#: ./doc/networking-guide/section_architecture-agents.xml:13(para)
|
||||
msgid "Bacon ipsum dolor sit amet ribeye rump pork loin shankle jowl pancetta bacon. Chicken andouille capicola filet mignon shoulder, turducken corned beef boudin hamburger fatback pork chop t-bone kevin. Leberkas turducken short loin t-bone pork belly pig prosciutto chicken beef ribs pork loin short ribs shoulder jerky bacon strip steak."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/networking-guide/section_architecture-agents.xml:22(systemitem)
|
||||
msgid "neutron-server"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/networking-guide/section_architecture-agents.xml:24(para)
|
||||
msgid "A Python daemon, which manages user requests (and exposes the API). It is configured with a plugin that implements the OpenStack Networking API operations using a specific set of networking mechanisms. A wide choice of plugins are also available. For example, the openvswitch and linuxbridge plugins utilize native Linux networking mechanisms, while other plugins interface with external devices or SDN controllers."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/networking-guide/section_architecture-agents.xml:36(systemitem)
|
||||
msgid "neutron-l3-agent"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/networking-guide/section_architecture-agents.xml:38(para)
|
||||
msgid "An agent providing L3/NAT forwarding."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/networking-guide/section_architecture-agents.xml:44(systemitem)
|
||||
msgid "neutron-*-agent"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/networking-guide/section_architecture-agents.xml:46(para)
|
||||
msgid "A plug-in agent that runs on each node to perform local networking configuration for the node's virtual machines and networking services."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/networking-guide/section_architecture-agents.xml:53(systemitem)
|
||||
msgid "neutron-dhcp-agent"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/networking-guide/section_architecture-agents.xml:55(para)
|
||||
msgid "An agent providing DHCP services to tenant networks."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/networking-guide/section_architecture-agents.xml:61(term)
|
||||
msgid "Database"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/networking-guide/section_architecture-agents.xml:63(para)
|
||||
msgid "Provides persistent storage."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/networking-guide/section_architecture-agents.xml:72(para)
|
||||
msgid "provide layer-2/3 connectivity to instances, handle physical-virtual network transition, handle metadata, etc"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/networking-guide/section_architecture-agents.xml:33(para) ./doc/networking-guide/section_architecture-agents.xml:40(para) ./doc/networking-guide/section_architecture-agents.xml:53(para) ./doc/networking-guide/section_architecture-agents.xml:60(para) ./doc/networking-guide/section_architecture-agents.xml:73(para)
|
||||
#: ./doc/networking-guide/section_architecture-agents.xml:82(para) ./doc/networking-guide/section_architecture-agents.xml:89(para) ./doc/networking-guide/section_architecture-agents.xml:102(para) ./doc/networking-guide/section_architecture-agents.xml:109(para) ./doc/networking-guide/section_architecture-agents.xml:122(para)
|
||||
msgid "overview/concepts"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/networking-guide/section_architecture-agents.xml:34(para) ./doc/networking-guide/section_architecture-agents.xml:41(para) ./doc/networking-guide/section_architecture-agents.xml:54(para) ./doc/networking-guide/section_architecture-agents.xml:61(para) ./doc/networking-guide/section_architecture-agents.xml:74(para)
|
||||
#: ./doc/networking-guide/section_architecture-agents.xml:83(para) ./doc/networking-guide/section_architecture-agents.xml:90(para) ./doc/networking-guide/section_architecture-agents.xml:103(para) ./doc/networking-guide/section_architecture-agents.xml:110(para) ./doc/networking-guide/section_architecture-agents.xml:123(para)
|
||||
msgid "configuration file"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/networking-guide/section_architecture-agents.xml:48(title)
|
||||
#: ./doc/networking-guide/section_architecture-agents.xml:97(title)
|
||||
msgid "Layer 3 (IP/Routing)"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/networking-guide/section_architecture-agents.xml:51(term)
|
||||
#: ./doc/networking-guide/section_architecture-agents.xml:100(term)
|
||||
msgid "l3"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/networking-guide/section_architecture-agents.xml:58(term)
|
||||
#: ./doc/networking-guide/section_architecture-agents.xml:107(term)
|
||||
msgid "DHCP"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/networking-guide/section_architecture-agents.xml:68(title)
|
||||
#: ./doc/networking-guide/section_architecture-agents.xml:117(title)
|
||||
msgid "Miscellaneous"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/networking-guide/section_architecture-agents.xml:71(term)
|
||||
#: ./doc/networking-guide/section_architecture-agents.xml:120(term)
|
||||
msgid "Metadata"
|
||||
msgstr ""
|
||||
|
||||
@ -405,10 +602,6 @@ msgstr ""
|
||||
msgid "provider networks:"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/networking-guide/ch_advanced.xml:28(title)
|
||||
msgid "Provider networks"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/networking-guide/ch_advanced.xml:29(para)
|
||||
msgid "Networks can be categorized as either tenant networks or provider networks. Tenant networks are created by normal users and details about how they are physically realized are hidden from those users. Provider networks are created with administrative credentials, specifying the details of how the network is physically realized, usually to match some existing network in the data center."
|
||||
msgstr ""
|
||||
@ -441,10 +634,6 @@ msgstr ""
|
||||
msgid "Term"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/networking-guide/ch_advanced.xml:58(th) ./doc/networking-guide/ch_advanced.xml:149(th) ./doc/networking-guide/ch_advanced.xml:274(th) ./doc/networking-guide/ch_advanced.xml:332(th) ./doc/networking-guide/ch_advanced.xml:632(th) ./doc/networking-guide/ch_advanced.xml:675(th) ./doc/networking-guide/ch_advanced.xml:886(th) ./doc/networking-guide/ch_advanced.xml:1008(th) ./doc/networking-guide/ch_advanced.xml:1076(th) ./doc/networking-guide/ch_advanced.xml:1197(th) ./doc/networking-guide/ch_advanced.xml:1512(th) ./doc/networking-guide/ch_advanced.xml:1601(th) ./doc/networking-guide/ch_advanced.xml:1642(th)
|
||||
msgid "Description"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/networking-guide/ch_advanced.xml:63(emphasis)
|
||||
msgid "virtual network"
|
||||
msgstr ""
|
||||
@ -1266,7 +1455,7 @@ msgid "uuid-str or None"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/networking-guide/ch_advanced.xml:920(td)
|
||||
msgid "This is a read-only attribute that gets populated with the uuid of the firewall policy when this firewall rule is associated with a firewall policy. A firewall rule can be associated with only one firewall policy at a time. However, the association can be changed to a different firewall policy."
|
||||
msgid "This is a read-only attribute that gets populated with the UUID of the firewall policy when this firewall rule is associated with a firewall policy. A firewall rule can be associated with only one firewall policy at a time. However, the association can be changed to a different firewall policy."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/networking-guide/ch_advanced.xml:927(td) ./doc/networking-guide/ch_advanced.xml:1039(td)
|
||||
@ -1406,7 +1595,7 @@ msgid "List of uuid-str or None"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/networking-guide/ch_advanced.xml:1050(td)
|
||||
msgid "This is an ordered list of firewall rule uuids. The firewall applies the rules in the order in which they appear in this list."
|
||||
msgid "This is an ordered list of firewall rule UUIDs. The firewall applies the rules in the order in which they appear in this list."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/networking-guide/ch_advanced.xml:1054(td)
|
||||
@ -1466,7 +1655,7 @@ msgid "ERROR"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/networking-guide/ch_advanced.xml:1146(td)
|
||||
msgid "The firewall policy uuid that this firewall is associated with. This firewall implements the rules contained in the firewall policy represented by this uuid."
|
||||
msgid "The firewall policy UUID that this firewall is associated with. This firewall implements the rules contained in the firewall policy represented by this UUID."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/networking-guide/ch_advanced.xml:1156(title)
|
||||
|
||||
@ -4,8 +4,8 @@
|
||||
msgid ""
|
||||
msgstr ""
|
||||
"Project-Id-Version: OpenStack Manuals\n"
|
||||
"POT-Creation-Date: 2014-08-15 05:33+0000\n"
|
||||
"PO-Revision-Date: 2014-08-09 17:01+0000\n"
|
||||
"POT-Creation-Date: 2014-08-15 18:55+0000\n"
|
||||
"PO-Revision-Date: 2014-08-15 12:49+0000\n"
|
||||
"Last-Translator: openstackjenkins <jenkins@openstack.org>\n"
|
||||
"Language-Team: Japanese (http://www.transifex.com/projects/p/openstack-manuals-i18n/language/ja/)\n"
|
||||
"MIME-Version: 1.0\n"
|
||||
@ -434,8 +434,8 @@ msgstr "引数の順番は決まっています。そして、\"from-port\" と
|
||||
#: ./doc/user-guide-admin/section_cli_nova_manage_projects_security.xml140(para)
|
||||
msgid ""
|
||||
"You can create complex rule sets by creating additional rules. For example, "
|
||||
"if you want to pass both http and https traffic, run:"
|
||||
msgstr "追加ルールを作成することにより、複雑なルールセットを作成できます。例えば、http と https の通信をどちらも許可したい場合、以下を実行します。"
|
||||
"if you want to pass both HTTP and HTTPS traffic, run:"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/user-guide-admin/section_cli_nova_manage_projects_security.xml149(para)
|
||||
msgid ""
|
||||
|
||||
@ -1,7 +1,7 @@
|
||||
msgid ""
|
||||
msgstr ""
|
||||
"Project-Id-Version: PACKAGE VERSION\n"
|
||||
"POT-Creation-Date: 2014-08-15 06:09+0000\n"
|
||||
"POT-Creation-Date: 2014-08-16 06:09+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"
|
||||
@ -302,7 +302,7 @@ msgid "The arguments are positional, and the \"from-port\" and \"to-port\" argum
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/user-guide-admin/section_cli_nova_manage_projects_security.xml:140(para)
|
||||
msgid "You can create complex rule sets by creating additional rules. For example, if you want to pass both http and https traffic, run:"
|
||||
msgid "You can create complex rule sets by creating additional rules. For example, if you want to pass both HTTP and HTTPS traffic, run:"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/user-guide-admin/section_cli_nova_manage_projects_security.xml:149(para)
|
||||
|
||||
@ -11,9 +11,9 @@
|
||||
msgid ""
|
||||
msgstr ""
|
||||
"Project-Id-Version: OpenStack Manuals\n"
|
||||
"POT-Creation-Date: 2014-08-15 05:33+0000\n"
|
||||
"PO-Revision-Date: 2014-08-14 06:30+0000\n"
|
||||
"Last-Translator: Andreas Jaeger <jaegerandi@gmail.com>\n"
|
||||
"POT-Creation-Date: 2014-08-15 18:55+0000\n"
|
||||
"PO-Revision-Date: 2014-08-15 18:42+0000\n"
|
||||
"Last-Translator: openstackjenkins <jenkins@openstack.org>\n"
|
||||
"Language-Team: French (http://www.transifex.com/projects/p/openstack-manuals-i18n/language/fr/)\n"
|
||||
"MIME-Version: 1.0\n"
|
||||
"Content-Type: text/plain; charset=UTF-8\n"
|
||||
@ -1039,6 +1039,7 @@ msgid "To create a server"
|
||||
msgstr "Pour créer un serveur"
|
||||
|
||||
#: ./doc/user-guide/section_sdk_nova.xml91(para)
|
||||
#: ./doc/user-guide/section_sdk_nova.xml353(para)
|
||||
#: ./doc/user-guide/section_sdk_nova.xml417(para)
|
||||
#: ./doc/user-guide/section_sdk_nova.xml478(para)
|
||||
msgid ""
|
||||
@ -1183,12 +1184,6 @@ msgid ""
|
||||
"<filename>utils.py</filename> and prints the flavor details:"
|
||||
msgstr "La méthode <literal>print_flavors</literal> est définie dans <filename>utils.py</filename> est imprime les détails d'un type d'instance."
|
||||
|
||||
#: ./doc/user-guide/section_sdk_nova.xml353(para)
|
||||
msgid ""
|
||||
"Get openStack credentials. See <xref "
|
||||
"linkend=\"sdk_compute_get_openstack_credentials_v2\"/>."
|
||||
msgstr "Pour obtenir les identifiants openStack. Voir <xref linkend=\"sdk_compute_get_openstack_credentials_v2\"/>."
|
||||
|
||||
#: ./doc/user-guide/section_sdk_nova.xml365(para)
|
||||
msgid ""
|
||||
"List flavors by calling <literal>list()</literal> on "
|
||||
|
||||
@ -7,9 +7,9 @@
|
||||
msgid ""
|
||||
msgstr ""
|
||||
"Project-Id-Version: OpenStack Manuals\n"
|
||||
"POT-Creation-Date: 2014-08-15 05:33+0000\n"
|
||||
"PO-Revision-Date: 2014-08-11 17:49+0000\n"
|
||||
"Last-Translator: Tomoyuki KATO <tomo@dream.daynight.jp>\n"
|
||||
"POT-Creation-Date: 2014-08-15 18:55+0000\n"
|
||||
"PO-Revision-Date: 2014-08-15 18:42+0000\n"
|
||||
"Last-Translator: openstackjenkins <jenkins@openstack.org>\n"
|
||||
"Language-Team: Japanese (http://www.transifex.com/projects/p/openstack-manuals-i18n/language/ja/)\n"
|
||||
"MIME-Version: 1.0\n"
|
||||
"Content-Type: text/plain; charset=UTF-8\n"
|
||||
@ -1035,6 +1035,7 @@ msgid "To create a server"
|
||||
msgstr "サーバーの作成方法"
|
||||
|
||||
#: ./doc/user-guide/section_sdk_nova.xml91(para)
|
||||
#: ./doc/user-guide/section_sdk_nova.xml353(para)
|
||||
#: ./doc/user-guide/section_sdk_nova.xml417(para)
|
||||
#: ./doc/user-guide/section_sdk_nova.xml478(para)
|
||||
msgid ""
|
||||
@ -1179,12 +1180,6 @@ msgid ""
|
||||
"<filename>utils.py</filename> and prints the flavor details:"
|
||||
msgstr "<literal>print_flavors</literal> メソッドは、<filename>utils.py</filename> で定義され、フレーバーの詳細を表示します。"
|
||||
|
||||
#: ./doc/user-guide/section_sdk_nova.xml353(para)
|
||||
msgid ""
|
||||
"Get openStack credentials. See <xref "
|
||||
"linkend=\"sdk_compute_get_openstack_credentials_v2\"/>."
|
||||
msgstr "OpenStack クレデンシャルを取得します。<xref linkend=\"sdk_compute_get_openstack_credentials_v2\"/> を参照してください。"
|
||||
|
||||
#: ./doc/user-guide/section_sdk_nova.xml365(para)
|
||||
msgid ""
|
||||
"List flavors by calling <literal>list()</literal> on "
|
||||
|
||||
@ -1,7 +1,7 @@
|
||||
msgid ""
|
||||
msgstr ""
|
||||
"Project-Id-Version: PACKAGE VERSION\n"
|
||||
"POT-Creation-Date: 2014-08-15 06:09+0000\n"
|
||||
"POT-Creation-Date: 2014-08-16 06:09+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"
|
||||
@ -757,7 +757,7 @@ msgstr ""
|
||||
msgid "To create a server"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/user-guide/section_sdk_nova.xml:91(para) ./doc/user-guide/section_sdk_nova.xml:417(para) ./doc/user-guide/section_sdk_nova.xml:478(para)
|
||||
#: ./doc/user-guide/section_sdk_nova.xml:91(para) ./doc/user-guide/section_sdk_nova.xml:353(para) ./doc/user-guide/section_sdk_nova.xml:417(para) ./doc/user-guide/section_sdk_nova.xml:478(para)
|
||||
msgid "Get OpenStack credentials. See <xref linkend=\"sdk_compute_get_openstack_credentials_v2\"/>."
|
||||
msgstr ""
|
||||
|
||||
@ -869,10 +869,6 @@ msgstr ""
|
||||
msgid "The <literal>print_flavors</literal> method is defined in <filename>utils.py</filename> and prints the flavor details:"
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/user-guide/section_sdk_nova.xml:353(para)
|
||||
msgid "Get openStack credentials. See <xref linkend=\"sdk_compute_get_openstack_credentials_v2\"/>."
|
||||
msgstr ""
|
||||
|
||||
#: ./doc/user-guide/section_sdk_nova.xml:365(para)
|
||||
msgid "List flavors by calling <literal>list()</literal> on <literal>nova_client.flavors</literal> object:"
|
||||
msgstr ""
|
||||
|
||||
Loading…
x
Reference in New Issue
Block a user