diff --git a/doc/arch-design/locale/arch-design.pot b/doc/arch-design/locale/arch-design.pot index 99bfbcd222..29b3a86335 100644 --- a/doc/arch-design/locale/arch-design.pot +++ b/doc/arch-design/locale/arch-design.pot @@ -1,7 +1,7 @@ msgid "" msgstr "" "Project-Id-Version: PACKAGE VERSION\n" -"POT-Creation-Date: 2014-08-03 06:09+0000\n" +"POT-Creation-Date: 2014-08-04 06:09+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -755,7 +755,7 @@ msgstr "" msgid "Data locality, in which specific data or functionality should be close to users." 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:50(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/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 "" @@ -763,19 +763,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:68(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:36(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: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:36(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:73(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: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) 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:78(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: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) 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:82(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: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) msgid "Data sovereignty policies governing the storage of data in foreign countries or otherwise separate jurisdictions." msgstr "" @@ -855,7 +855,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:137(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/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/multi_site/section_user_requirements_multi_site.xml:137(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/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) msgid "Cost" msgstr "" @@ -875,7 +875,7 @@ msgstr "" msgid "Replication" msgstr "" -#: ./doc/arch-design/multi_site/section_user_requirements_multi_site.xml:156(para) ./doc/arch-design/generalpurpose/section_tech_considerations_general_purpose.xml:664(para) ./doc/arch-design/compute_focus/section_tech_considerations_compute_focus.xml:286(para) ./doc/arch-design/hybrid/section_tech_considerations_hybrid.xml:122(para) +#: ./doc/arch-design/multi_site/section_user_requirements_multi_site.xml:156(para) ./doc/arch-design/generalpurpose/section_tech_considerations_general_purpose.xml:664(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 "" @@ -1077,7 +1077,7 @@ msgstr "" msgid "In this example, the application utilizing this multi-site OpenStack install that is location aware would launch web server or content serving instances on the compute cluster in each site. Requests from clients will first be sent to a global services load balancer that determines the location of the client, then routes the request to the closest OpenStack site where the application completes the request." msgstr "" -#: ./doc/arch-design/multi_site/section_tech_considerations_multi_site.xml:8(title) ./doc/arch-design/network_focus/section_tech_considerations_network_focus.xml:8(title) ./doc/arch-design/generalpurpose/section_tech_considerations_general_purpose.xml:12(title) ./doc/arch-design/compute_focus/section_user_requirements_compute_focus.xml:90(title) ./doc/arch-design/compute_focus/section_tech_considerations_compute_focus.xml:12(title) ./doc/arch-design/hybrid/section_tech_considerations_hybrid.xml:8(title) ./doc/arch-design/massively_scalable/section_tech_considerations_massively_scalable.xml:8(title) ./doc/arch-design/storage_focus/section_tech_considerations_storage_focus.xml:8(title) +#: ./doc/arch-design/multi_site/section_tech_considerations_multi_site.xml:8(title) ./doc/arch-design/network_focus/section_tech_considerations_network_focus.xml:8(title) ./doc/arch-design/generalpurpose/section_tech_considerations_general_purpose.xml:12(title) ./doc/arch-design/compute_focus/section_user_requirements_compute_focus.xml:90(title) ./doc/arch-design/compute_focus/section_tech_considerations_compute_focus.xml:12(title) ./doc/arch-design/hybrid/section_tech_considerations_hybrid.xml:12(title) ./doc/arch-design/massively_scalable/section_tech_considerations_massively_scalable.xml:12(title) ./doc/arch-design/storage_focus/section_tech_considerations_storage_focus.xml:8(title) msgid "Technical considerations" msgstr "" @@ -1109,7 +1109,7 @@ msgstr "" msgid "A third form of capacity comes in the multi-region-capable components of OpenStack. Centralized Object Storage is capable of serving objects through a single namespace across multiple regions. Since this works by accessing the object store via swift proxy, it is possible to overload the proxies. There are two options available to mitigate this issue. The first is to deploy a large number of swift proxies. The drawback to this is that the proxies are not load-balanced and a large file request could continually hit the same proxy. The other way to mitigate this is to front-end the proxies with a caching HTTP proxy and load balancer. Since swift objects are returned to the requester via HTTP, this load balancer would alleviate the load required on the swift proxies." msgstr "" -#: ./doc/arch-design/multi_site/section_tech_considerations_multi_site.xml:79(title) ./doc/arch-design/compute_focus/section_tech_considerations_compute_focus.xml:215(title) ./doc/arch-design/hybrid/section_tech_considerations_hybrid.xml:222(title) +#: ./doc/arch-design/multi_site/section_tech_considerations_multi_site.xml:79(title) ./doc/arch-design/compute_focus/section_tech_considerations_compute_focus.xml:215(title) ./doc/arch-design/hybrid/section_tech_considerations_hybrid.xml:230(title) msgid "Utilization" msgstr "" @@ -1129,7 +1129,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 Swift 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:399(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_tech_considerations_compute_focus.xml:257(title) ./doc/arch-design/hybrid/section_tech_considerations_hybrid.xml:245(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/multi_site/section_tech_considerations_multi_site.xml:114(title) ./doc/arch-design/network_focus/section_tech_considerations_network_focus.xml:399(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_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) msgid "Performance" msgstr "" @@ -1145,7 +1145,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:142(title) ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:684(term) ./doc/arch-design/generalpurpose/section_user_requirements_general_purpose.xml:199(term) ./doc/arch-design/generalpurpose/section_tech_considerations_general_purpose.xml:650(title) ./doc/arch-design/compute_focus/section_user_requirements_compute_focus.xml:160(term) ./doc/arch-design/compute_focus/section_tech_considerations_compute_focus.xml:268(title) ./doc/arch-design/hybrid/section_tech_considerations_hybrid.xml:103(title) ./doc/arch-design/storage_focus/section_architecture_storage_focus.xml:471(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:142(title) ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:684(term) ./doc/arch-design/generalpurpose/section_user_requirements_general_purpose.xml:199(term) ./doc/arch-design/generalpurpose/section_tech_considerations_general_purpose.xml:650(title) ./doc/arch-design/compute_focus/section_user_requirements_compute_focus.xml:160(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_architecture_storage_focus.xml:471(term) msgid "Security" msgstr "" @@ -2377,7 +2377,7 @@ msgstr "" 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/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) msgid "Time to market" msgstr "" @@ -2385,7 +2385,7 @@ msgstr "" 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/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) msgid "Revenue opportunity" msgstr "" @@ -2393,7 +2393,7 @@ msgstr "" 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:67(title) ./doc/arch-design/storage_focus/section_user_requirements_storage_focus.xml:35(title) +#: ./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:35(title) msgid "Legal requirements" msgstr "" @@ -2401,7 +2401,7 @@ msgstr "" 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/storage_focus/section_user_requirements_storage_focus.xml:61(para) +#: ./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:61(para) msgid "Examples of such legal frameworks include the data protection framework of the European Union and the requirements of the Financial Industry Regulatory Authority in the United States. Consult a local regulatory body for more information." msgstr "" @@ -2549,7 +2549,7 @@ msgstr "" msgid "An example of an operational consideration is the recovery of a failed compute host. This might mean requiring the restoration of instances from a snapshot or respawning an instance on another available compute host. This could have consequences on the overall application design. A general purpose cloud should not need to provide an ability to migrate instances from one host to another. If the expectation is that the application will be designed to tolerate failure, additional considerations need to be made around supporting instance migration. In this scenario, extra supporting services, including shared storage attached to compute hosts, might need to be deployed." msgstr "" -#: ./doc/arch-design/generalpurpose/section_operational_considerations_general_purpose.xml:96(title) ./doc/arch-design/compute_focus/section_operational_considerations_compute_focus.xml:89(title) ./doc/arch-design/hybrid/section_tech_considerations_hybrid.xml:68(title) +#: ./doc/arch-design/generalpurpose/section_operational_considerations_general_purpose.xml:96(title) ./doc/arch-design/compute_focus/section_operational_considerations_compute_focus.xml:89(title) ./doc/arch-design/hybrid/section_tech_considerations_hybrid.xml:72(title) msgid "Capacity planning" msgstr "" @@ -2803,7 +2803,7 @@ msgstr "" 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:30(title) +#: ./doc/arch-design/generalpurpose/section_tech_considerations_general_purpose.xml:344(title) ./doc/arch-design/specialized/section_openstack_on_openstack_specialized.xml:34(title) msgid "Hypervisor" msgstr "" @@ -2991,15 +2991,15 @@ msgstr "" msgid "These security domains are:" msgstr "" -#: ./doc/arch-design/generalpurpose/section_tech_considerations_general_purpose.xml:658(para) ./doc/arch-design/compute_focus/section_tech_considerations_compute_focus.xml:280(para) ./doc/arch-design/hybrid/section_tech_considerations_hybrid.xml:116(para) +#: ./doc/arch-design/generalpurpose/section_tech_considerations_general_purpose.xml:658(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:661(para) ./doc/arch-design/compute_focus/section_tech_considerations_compute_focus.xml:283(para) ./doc/arch-design/hybrid/section_tech_considerations_hybrid.xml:119(para) +#: ./doc/arch-design/generalpurpose/section_tech_considerations_general_purpose.xml:661(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:667(para) ./doc/arch-design/compute_focus/section_tech_considerations_compute_focus.xml:289(para) ./doc/arch-design/hybrid/section_architecture_hybrid.xml:159(title) ./doc/arch-design/hybrid/section_tech_considerations_hybrid.xml:125(para) +#: ./doc/arch-design/generalpurpose/section_tech_considerations_general_purpose.xml:667(para) ./doc/arch-design/compute_focus/section_tech_considerations_compute_focus.xml:289(para) ./doc/arch-design/hybrid/section_architecture_hybrid.xml:163(title) ./doc/arch-design/hybrid/section_tech_considerations_hybrid.xml:129(para) msgid "Data" msgstr "" @@ -4073,7 +4073,7 @@ msgstr "" msgid "It is strongly recommended that the API services are placed behind hardware that performs SSL termination. API services transmit user names, passwords, and generated tokens between client machines and API endpoints and therefore must be secured." msgstr "" -#: ./doc/arch-design/compute_focus/section_tech_considerations_compute_focus.xml:356(para) ./doc/arch-design/hybrid/section_tech_considerations_hybrid.xml:219(para) +#: ./doc/arch-design/compute_focus/section_tech_considerations_compute_focus.xml:356(para) msgid "More information on OpenStack Security can be found at http://docs.openstack.org/security-guide/" msgstr "" @@ -4279,7 +4279,7 @@ msgstr "" #. When image changes, this message will be marked fuzzy or untranslated for you. #. It doesn't matter what you translate it to: it's not used at all. -#: ./doc/arch-design/specialized/section_hardware_specialized.xml:42(None) +#: ./doc/arch-design/specialized/section_hardware_specialized.xml:46(None) msgid "@@image: '../images/Specialized_Hardware2.png'; md5=8cfa7b2ff63d6fa1413f55de3237137a" msgstr "" @@ -4291,7 +4291,7 @@ msgstr "" msgid "Certain workloads require specialized hardware devices that are either difficult to virtualize or impossible to share. Applications such as load balancers, highly parallel brute force computing, and direct to wire networking may need capabilities that basic OpenStack components do not provide." msgstr "" -#: ./doc/arch-design/specialized/section_hardware_specialized.xml:15(title) ./doc/arch-design/specialized/section_desktop_as_a_service_specialized.xml:21(title) ./doc/arch-design/specialized/section_networking_specialized.xml:14(title) ./doc/arch-design/specialized/section_openstack_on_openstack_specialized.xml:20(title) ./doc/arch-design/specialized/section_software_defined_networking_specialized.xml:18(title) +#: ./doc/arch-design/specialized/section_hardware_specialized.xml:15(title) ./doc/arch-design/specialized/section_desktop_as_a_service_specialized.xml:21(title) ./doc/arch-design/specialized/section_networking_specialized.xml:14(title) ./doc/arch-design/specialized/section_openstack_on_openstack_specialized.xml:24(title) ./doc/arch-design/specialized/section_software_defined_networking_specialized.xml:18(title) msgid "Challenges" msgstr "" @@ -4304,11 +4304,11 @@ msgid "Solutions" msgstr "" #: ./doc/arch-design/specialized/section_hardware_specialized.xml:24(para) -msgid "In order to provide cryptography offloading to a set of instances, it is possible to use Glance configuration options to assign the cryptography chip to a device node in the guest. The documentation at http://docs.openstack.org/cli-reference/content/chapter_cli-glance-property.html contains further information on configuring this solution, but it allows all guests using the configured images to access the hypervisor cryptography device." +msgid "In order to provide cryptography offloading to a set of instances, it is possible to use Image Service configuration options to assign the cryptography chip to a device node in the guest. The OpenStack Command Line Reference contains further information on configuring this solution in the chapter Image Service property keys , but it allows all guests using the configured images to access the hypervisor cryptography device." msgstr "" -#: ./doc/arch-design/specialized/section_hardware_specialized.xml:32(para) -msgid "If direct access to a specific device is required, it can be dedicated to a single instance per hypervisor through the use of PCI pass-through. The OpenStack administrator needs to define a flavor that specifically has the PCI device in order to properly schedule instances. More information regarding PCI pass-through, including instructions for implementing and using it, is available at https://wiki.openstack.org/wiki/Pci_passthrough#How_to_check_PCI_status_with_PCI_api_patches." +#: ./doc/arch-design/specialized/section_hardware_specialized.xml:34(para) +msgid "If direct access to a specific device is required, it can be dedicated to a single instance per hypervisor through the use of PCI pass-through. The OpenStack administrator needs to define a flavor that specifically has the PCI device in order to properly schedule instances. More information regarding PCI pass-through, including instructions for implementing and using it, is available at https://wiki.openstack.org/wiki/Pci_passthrough." msgstr "" #. When image changes, this message will be marked fuzzy or untranslated for you. @@ -4342,7 +4342,7 @@ msgid "Images in the OpenStack Image Service have particular hypervisor metadata msgstr "" #: ./doc/arch-design/specialized/section_multi_hypervisor_specialized.xml:49(para) -msgid "This example has the additional complication that, rather than being spawned directly on a hypervisor simply by calling a specific host aggregate using the metadata of the image, the VMware host aggregate compute nodes communicate with vCenter which then requests that the instance be scheduled to run on an ESXi hypervisor. As of the Icehouse release,this functionality requires that VMware Distributed Resource Scheduler (DRS) be enabled on a cluster and set to \"Fully Automated\"." +msgid "This example has the additional complication that, rather than being spawned directly on a hypervisor simply by calling a specific host aggregate using the metadata of the image, the VMware host aggregate compute nodes communicate with vCenter which then requests that the instance be scheduled to run on an ESXi hypervisor. As of the Icehouse release, this functionality requires that VMware Distributed Resource Scheduler (DRS) be enabled on a cluster and set to \"Fully Automated\"." msgstr "" #: ./doc/arch-design/specialized/section_multi_hypervisor_specialized.xml:58(para) @@ -4359,7 +4359,7 @@ msgstr "" #. When image changes, this message will be marked fuzzy or untranslated for you. #. It doesn't matter what you translate it to: it's not used at all. -#: ./doc/arch-design/specialized/section_desktop_as_a_service_specialized.xml:60(None) +#: ./doc/arch-design/specialized/section_desktop_as_a_service_specialized.xml:62(None) msgid "@@image: '../images/Specialized_VDI1.png'; md5=77729426d59881476de9a03e1ee8a22c" msgstr "" @@ -4376,7 +4376,7 @@ msgid "Designing an infrastructure that is suitable to host virtual desktops is msgstr "" #: ./doc/arch-design/specialized/section_desktop_as_a_service_specialized.xml:28(para) -msgid "Boot storms - What happens when hundreds or thousands of users log in during shift changes, affects the storage design." +msgid "Boot storms: What happens when hundreds or thousands of users log in during shift changes, affects the storage design." msgstr "" #: ./doc/arch-design/specialized/section_desktop_as_a_service_specialized.xml:33(para) @@ -4392,7 +4392,7 @@ msgid "Broker" msgstr "" #: ./doc/arch-design/specialized/section_desktop_as_a_service_specialized.xml:42(para) -msgid "The Connection Broker is a central component of the architecture that determines which Remote Desktop Host will be assigned or connected to the user. The broker is often a full-blown management product allowing for the automated deployment and provisioning of Remote Desktop Hosts." +msgid "The connection broker is a central component of the architecture that determines which remote desktop host will be assigned or connected to the user. The broker is often a full-blown management product allowing for the automated deployment and provisioning of remote desktop hosts." msgstr "" #: ./doc/arch-design/specialized/section_desktop_as_a_service_specialized.xml:48(title) ./doc/arch-design/specialized/section_networking_specialized.xml:21(title) ./doc/arch-design/specialized/section_software_defined_networking_specialized.xml:26(title) @@ -4400,10 +4400,10 @@ msgid "Possible solutions" msgstr "" #: ./doc/arch-design/specialized/section_desktop_as_a_service_specialized.xml:49(para) -msgid "There a number of commercial products available today that provide such a broker solution but nothing that is native in the OpenStack project. There of course is also the option of not providing a broker and managing this manually - but this would not suffice as a large scale, enterprise solution." +msgid "There are a number of commercial products available today that provide such a broker solution but nothing that is native in the OpenStack project. Not providing a broker is also an option, but managing this manually would not suffice as a large scale, enterprise solution." msgstr "" -#: ./doc/arch-design/specialized/section_desktop_as_a_service_specialized.xml:55(title) ./doc/arch-design/specialized/section_openstack_on_openstack_specialized.xml:62(title) ./doc/arch-design/specialized/section_software_defined_networking_specialized.xml:36(title) +#: ./doc/arch-design/specialized/section_desktop_as_a_service_specialized.xml:57(title) ./doc/arch-design/specialized/section_openstack_on_openstack_specialized.xml:69(title) ./doc/arch-design/specialized/section_software_defined_networking_specialized.xml:36(title) msgid "Diagram" msgstr "" @@ -4420,11 +4420,11 @@ msgid "Connecting specialized network applications to their required resources a msgstr "" #: ./doc/arch-design/specialized/section_networking_specialized.xml:22(para) -msgid "Deploying an OpenStack installation using Neutron with a provider network will allow direct layer 2 connectivity to an upstream networking device. This design provides the layer 2 connectivity required to communicate via Intermediate System-to-Intermediate System (ISIS) protocol or to pass packets controlled via an OpenFlow controller. Using the multiple layer 2 plug-in with an agent such as Open vSwitch would allow a private connection through a VLAN directly to a specific port in a layer 3 device. This would allow a BGP point to point link to exist that will join the autonomous system. Avoid using layer 3 plug-ins as they will divide the broadcast domain and prevent router adjacencies from forming." +msgid "Deploying an OpenStack installation using OpenStack Networking with a provider network will allow direct layer 2 connectivity to an upstream networking device. This design provides the layer 2 connectivity required to communicate via Intermediate System-to-Intermediate System (ISIS) protocol or to pass packets controlled via an OpenFlow controller. Using the multiple layer 2 plug-in with an agent such as Open vSwitch would allow a private connection through a VLAN directly to a specific port in a layer 3 device. This would allow a BGP point to point link to exist that will join the autonomous system. Avoid using layer 3 plug-ins as they will divide the broadcast domain and prevent router adjacencies from forming." msgstr "" #: ./doc/arch-design/specialized/section_introduction_specialized.xml:8(para) -msgid "Although most OpenStack architecture designs fall into one of the seven major scenarios outlined in other sections (compute focused, network focused, storage focused, general purpose, multi-site, hybrid cloud, and massively scalable), there are a few other use cases that are unique enough they can't be neatly categorized into one of the other major sections. This section discusses some of these unique use cases with some additional details and design considerations for each use case." +msgid "Although most OpenStack architecture designs fall into one of the seven major scenarios outlined in other sections (compute focused, network focused, storage focused, general purpose, multi-site, hybrid cloud, and massively scalable), there are a few other use cases that are unique enough they can't be neatly categorized into one of the other major sections. This section discusses some of these unique use cases with some additional details and design considerations for each use case:" msgstr "" #: ./doc/arch-design/specialized/section_introduction_specialized.xml:19(para) @@ -4449,48 +4449,48 @@ msgstr "" #. When image changes, this message will be marked fuzzy or untranslated for you. #. It doesn't matter what you translate it to: it's not used at all. -#: ./doc/arch-design/specialized/section_openstack_on_openstack_specialized.xml:67(None) +#: ./doc/arch-design/specialized/section_openstack_on_openstack_specialized.xml:74(None) msgid "@@image: '../images/Specialized_OOO.png'; md5=502fd81a0c5a6429a0dede76ffde02b7" msgstr "" -#: ./doc/arch-design/specialized/section_openstack_on_openstack_specialized.xml:8(title) +#: ./doc/arch-design/specialized/section_openstack_on_openstack_specialized.xml:12(title) msgid "OpenStack on OpenStack" msgstr "" -#: ./doc/arch-design/specialized/section_openstack_on_openstack_specialized.xml:9(para) -msgid "In some cases it is necessary to run OpenStack nested on top of another OpenStack cloud. This scenario allows for complete OpenStack cloud environments to be managed and provisioned on instances running on hypervisors and servers controlled by the underlying OpenStack cloud. Public cloud providers can use this technique to effectively manage the upgrade and maintenance process on complete OpenStack-based clouds. Developers and those testing OpenStack can also use the guidance to provision their own OpenStack environments on available OpenStack Compute resources, whether Public or Private." +#: ./doc/arch-design/specialized/section_openstack_on_openstack_specialized.xml:13(para) +msgid "In some cases it is necessary to run OpenStack nested on top of another OpenStack cloud. This scenario allows for complete OpenStack cloud environments to be managed and provisioned on instances running on hypervisors and servers controlled by the underlying OpenStack cloud. Public cloud providers can use this technique to effectively manage the upgrade and maintenance process on complete OpenStack-based clouds. Developers and those testing OpenStack can also use the guidance to provision their own OpenStack environments on available OpenStack Compute resources, whether public or private." msgstr "" -#: ./doc/arch-design/specialized/section_openstack_on_openstack_specialized.xml:21(para) +#: ./doc/arch-design/specialized/section_openstack_on_openstack_specialized.xml:25(para) msgid "The network aspect of deploying a nested cloud is the most complicated aspect of this architecture. When using VLANs, these will need to be exposed to the physical ports on which the undercloud runs, as the bare metal cloud owns all the hardware, but they also need to be exposed to the nested levels as well. Alternatively, network overlay technologies can be used on the overcloud (the OpenStack cloud running on OpenStack) to provide the required software defined networking for the deployment." msgstr "" -#: ./doc/arch-design/specialized/section_openstack_on_openstack_specialized.xml:31(para) +#: ./doc/arch-design/specialized/section_openstack_on_openstack_specialized.xml:35(para) msgid "A key question to address in this scenario is the decision about which approach should be taken to provide a nested hypervisor in OpenStack. This decision influences which operating systems can be used for the deployment of the nested OpenStack deployments." msgstr "" -#: ./doc/arch-design/specialized/section_openstack_on_openstack_specialized.xml:37(title) +#: ./doc/arch-design/specialized/section_openstack_on_openstack_specialized.xml:41(title) msgid "Possible solutions: deployment" msgstr "" -#: ./doc/arch-design/specialized/section_openstack_on_openstack_specialized.xml:38(para) +#: ./doc/arch-design/specialized/section_openstack_on_openstack_specialized.xml:42(para) msgid "Deployment of a full stack can be challenging but this difficulty can be readily be mitigated by creating a Heat template to deploy the entire stack or a configuration management system. Once the Heat template is created, deploying additional stacks will be a trivial thing and can be performed in an automated fashion." msgstr "" -#: ./doc/arch-design/specialized/section_openstack_on_openstack_specialized.xml:44(para) -msgid "The OpenStack-On-OpenStack project (TripleO) is addressing this issue - although at the current time the project does not provide comprehensive coverage for the nested stacks. More information can be found at https://wiki.openstack.org/wiki/TripleO." +#: ./doc/arch-design/specialized/section_openstack_on_openstack_specialized.xml:48(para) +msgid "The OpenStack-On-OpenStack project (TripleO) is addressing this issuealthough at the current time the project does not provide comprehensive coverage for the nested stacks. More information can be found at https://wiki.openstack.org/wiki/TripleO." msgstr "" -#: ./doc/arch-design/specialized/section_openstack_on_openstack_specialized.xml:50(title) +#: ./doc/arch-design/specialized/section_openstack_on_openstack_specialized.xml:56(title) msgid "Possible solutions: hypervisor" msgstr "" -#: ./doc/arch-design/specialized/section_openstack_on_openstack_specialized.xml:51(para) +#: ./doc/arch-design/specialized/section_openstack_on_openstack_specialized.xml:57(para) msgid "In the case of running TripleO, the underlying OpenStack cloud deploys the Compute nodes as bare-metal. OpenStack would then be deployed on these Compute bare-metal servers with the appropriate hypervisor, such as KVM." msgstr "" -#: ./doc/arch-design/specialized/section_openstack_on_openstack_specialized.xml:55(para) -msgid "In the case of running smaller OpenStack clouds for testing purposes, and performance would not be a critical factor, QEMU can be utilized instead. It is also possible to run a KVM hypervisor in an instance (http://davejingtian.org/2014/03/30/nested-kvm-just-for-fun/), though this is not a supported configuration, and could be a complex solution for such a use case." +#: ./doc/arch-design/specialized/section_openstack_on_openstack_specialized.xml:61(para) +msgid "In the case of running smaller OpenStack clouds for testing purposes, and performance would not be a critical factor, QEMU can be utilized instead. It is also possible to run a KVM hypervisor in an instance (see http://davejingtian.org/2014/03/30/nested-kvm-just-for-fun/), though this is not a supported configuration, and could be a complex solution for such a use case." msgstr "" #. When image changes, this message will be marked fuzzy or untranslated for you. @@ -4506,11 +4506,11 @@ msgid "@@image: '../images/Special_case_SDN_external.png'; md5=12d9e840a0a10a5ab msgstr "" #: ./doc/arch-design/specialized/section_software_defined_networking_specialized.xml:8(title) -msgid "Software Defined Networking (SDN)" +msgid "Software Defined Networking" msgstr "" #: ./doc/arch-design/specialized/section_software_defined_networking_specialized.xml:9(para) -msgid "Software Defined Networking is the separation of the data plane and control plane. SDN has become a popular method of managing and controlling packet flows within networks. SDN uses overlays or directly controlled layer 2 devices to determine flow paths, and as such presents challenges to a cloud environment. Some designers may wish to run their controllers within an OpenStack installation. Others may wish to have their installations participate in an SDN-controlled network." +msgid "Software Defined Networking (SDN) is the separation of the data plane and control plane. SDN has become a popular method of managing and controlling packet flows within networks. SDN uses overlays or directly controlled layer 2 devices to determine flow paths, and as such presents challenges to a cloud environment. Some designers may wish to run their controllers within an OpenStack installation. Others may wish to have their installations participate in an SDN-controlled network." msgstr "" #: ./doc/arch-design/specialized/section_software_defined_networking_specialized.xml:19(para) @@ -4537,140 +4537,164 @@ msgstr "" msgid "Business considerations to make when designing a hybrid cloud deployment include:" msgstr "" -#: ./doc/arch-design/hybrid/section_user_requirements_hybrid.xml:19(para) -msgid "Cost: A hybrid cloud architecture involves multiple vendors and technical architectures. These architectures may be more expensive to deploy and maintain. Operational costs can be higher because of the need for more sophisticated orchestration and brokerage tools than in other architectures. In contrast, overall operational costs might be lower by virtue of using a cloud brokerage tool to deploy the workloads to the most cost effective platform." +#: ./doc/arch-design/hybrid/section_user_requirements_hybrid.xml:21(para) +msgid "A hybrid cloud architecture involves multiple vendors and technical architectures. These architectures may be more expensive to deploy and maintain. Operational costs can be higher because of the need for more sophisticated orchestration and brokerage tools than in other architectures. In contrast, overall operational costs might be lower by virtue of using a cloud brokerage tool to deploy the workloads to the most cost effective platform." msgstr "" -#: ./doc/arch-design/hybrid/section_user_requirements_hybrid.xml:30(para) -msgid "Revenue opportunity: Revenue opportunities vary greatly based on the intent and use case of the cloud. If it is being built as a commercial customer-facing product, consider the drivers for building it over multiple platforms and whether the use of multiple platforms make the design more attractive to target customers, thus enhancing the revenue opportunity." +#: ./doc/arch-design/hybrid/section_user_requirements_hybrid.xml:35(para) +msgid "Revenue opportunities vary greatly based on the intent and use case of the cloud. If it is being built as a commercial customer-facing product, consider the drivers for building it over multiple platforms and whether the use of multiple platforms make the design more attractive to target customers, thus enhancing the revenue opportunity." msgstr "" -#: ./doc/arch-design/hybrid/section_user_requirements_hybrid.xml:40(para) -msgid "Time to Market: One of the most common reasons to use cloud platforms is to speed the time to market of a new product or application. A business requirement to use multiple cloud platforms may be because there is an existing investment in several applications and it is faster to tie them together rather than migrating components and refactoring to a single platform." +#: ./doc/arch-design/hybrid/section_user_requirements_hybrid.xml:48(para) +msgid "One of the most common reasons to use cloud platforms is to speed the time to market of a new product or application. A business requirement to use multiple cloud platforms may be because there is an existing investment in several applications and it is faster to tie them together rather than migrating components and refactoring to a single platform." msgstr "" -#: ./doc/arch-design/hybrid/section_user_requirements_hybrid.xml:50(para) -msgid "Business or technical diversity: Organizations already leveraging cloud-based services may wish to embrace business diversity and utilize a hybrid cloud design to spread their workloads across multiple cloud providers so that no application is hosted in a single cloud provider." +#: ./doc/arch-design/hybrid/section_user_requirements_hybrid.xml:59(term) +msgid "Business or technical diversity" msgstr "" -#: ./doc/arch-design/hybrid/section_user_requirements_hybrid.xml:58(para) -msgid "Application momentum: A business with existing applications that are already in production on multiple cloud environments may find that it is more cost effective to integrate the applications on multiple cloud platforms rather than migrate them to a single platform." +#: ./doc/arch-design/hybrid/section_user_requirements_hybrid.xml:61(para) +msgid "Organizations already leveraging cloud-based services may wish to embrace business diversity and utilize a hybrid cloud design to spread their workloads across multiple cloud providers so that no application is hosted in a single cloud provider." msgstr "" -#: ./doc/arch-design/hybrid/section_user_requirements_hybrid.xml:87(para) ./doc/arch-design/massively_scalable/section_user_requirements_massively_scalable.xml:36(para) +#: ./doc/arch-design/hybrid/section_user_requirements_hybrid.xml:70(term) +msgid "Application momentum" +msgstr "" + +#: ./doc/arch-design/hybrid/section_user_requirements_hybrid.xml:72(para) +msgid "A business with existing applications that are already in production on multiple cloud environments may find that it is more cost effective to integrate the applications on multiple cloud platforms rather than migrate them to a single platform." +msgstr "" + +#: ./doc/arch-design/hybrid/section_user_requirements_hybrid.xml:102(para) ./doc/arch-design/massively_scalable/section_user_requirements_massively_scalable.xml:36(para) msgid "Data compliance policies governing certain types of information needs to reside in certain locations due to regular issues and, more importantly, cannot reside in other locations for the same reason." msgstr "" -#: ./doc/arch-design/hybrid/section_user_requirements_hybrid.xml:93(para) -msgid "Examples of such legal frameworks include the data protection framework of the European Union (http://ec.europa.eu/justice/data-protection/) and the requirements of the Financial Industry Regulatory Authority (http://www.finra.org/Industry/Regulation/FINRARules/) in the United States. Consult a local regulatory body for more information." +#: ./doc/arch-design/hybrid/section_user_requirements_hybrid.xml:108(para) +msgid "Examples of such legal frameworks include the data protection framework of the European Union (http://ec.europa.eu/justice/data-protection/) and the requirements of the Financial Industry Regulatory Authority (http://www.finra.org/Industry/Regulation/FINRARules/) in the United States. Consult a local regulatory body for more information." msgstr "" -#: ./doc/arch-design/hybrid/section_user_requirements_hybrid.xml:101(title) +#: ./doc/arch-design/hybrid/section_user_requirements_hybrid.xml:118(title) msgid "Workload considerations" msgstr "" -#: ./doc/arch-design/hybrid/section_user_requirements_hybrid.xml:102(para) +#: ./doc/arch-design/hybrid/section_user_requirements_hybrid.xml:119(para) msgid "Defining what the word \"workload\" means in the context of a hybrid cloud environment is important. Workload can be defined as the intended way the systems will be utilized, which is often referred to as a \"use case\". A workload can be a single application or a suite of applications that work in concert. It can also be a duplicate set of applications that need to run on multiple cloud environments. In a hybrid cloud deployment, the same workload will often need to function equally well on radically different public and private cloud environments. The architecture needs to address these potential conflicts, complexity, and platform incompatibilities." msgstr "" -#: ./doc/arch-design/hybrid/section_user_requirements_hybrid.xml:114(para) +#: ./doc/arch-design/hybrid/section_user_requirements_hybrid.xml:131(para) msgid "Some possible use cases for a hybrid cloud architecture include:" msgstr "" -#: ./doc/arch-design/hybrid/section_user_requirements_hybrid.xml:118(para) +#: ./doc/arch-design/hybrid/section_user_requirements_hybrid.xml:135(para) msgid "Dynamic resource expansion or \"bursting\": Another common reason to use a multiple cloud architecture is a \"bursty\" application that needs additional resources at times. An example of this case could be a retailer that needs additional resources during the holiday selling season, but does not want to build expensive cloud resources to meet the peak demand. They might have an OpenStack private cloud but want to burst to AWS or some other public cloud for these peak load periods. These bursts could be for long or short cycles ranging from hourly, monthly or yearly." msgstr "" -#: ./doc/arch-design/hybrid/section_user_requirements_hybrid.xml:131(para) +#: ./doc/arch-design/hybrid/section_user_requirements_hybrid.xml:148(para) msgid "Disaster recovery-business continuity: The cheaper storage and instance management makes a good case for using the cloud as a secondary site. The public cloud is already heavily used for these purposes in combination with an OpenStack public or private cloud." msgstr "" -#: ./doc/arch-design/hybrid/section_user_requirements_hybrid.xml:139(para) +#: ./doc/arch-design/hybrid/section_user_requirements_hybrid.xml:156(para) msgid "Federated hypervisor-instance management: Adding self-service, charge back and transparent delivery of the right resources from a federated pool can be cost effective. In a hybrid cloud environment, this is a particularly important consideration. Look for a cloud that provides cross-platform hypervisor support and robust instance management tools." msgstr "" -#: ./doc/arch-design/hybrid/section_user_requirements_hybrid.xml:148(para) +#: ./doc/arch-design/hybrid/section_user_requirements_hybrid.xml:165(para) msgid "Application portfolio integration: An enterprise cloud delivers better application portfolio management and more efficient deployment by leveraging self-service features and rules for deployments based on types of use. A common driver for building hybrid cloud architecture is to stitch together multiple existing cloud environments that are already in production or development." msgstr "" -#: ./doc/arch-design/hybrid/section_user_requirements_hybrid.xml:162(para) +#: ./doc/arch-design/hybrid/section_user_requirements_hybrid.xml:179(para) msgid "Migration scenarios: A common reason to create a hybrid cloud architecture is to allow the migration of applications between different clouds. This may be because the application will be migrated permanently to a new platform, or it might be because the application needs to be supported on multiple platforms going forward." msgstr "" -#: ./doc/arch-design/hybrid/section_user_requirements_hybrid.xml:171(para) +#: ./doc/arch-design/hybrid/section_user_requirements_hybrid.xml:188(para) msgid "High availability: Another important reason for wanting a multiple cloud architecture is to address the needs for high availability. By using a combination of multiple locations and platforms, a design can achieve a level of availability that is not possible with a single platform. This approach does add a significant amount of complexity." msgstr "" -#: ./doc/arch-design/hybrid/section_user_requirements_hybrid.xml:180(para) +#: ./doc/arch-design/hybrid/section_user_requirements_hybrid.xml:197(para) msgid "In addition to thinking about how the workload will work on a single cloud, the design must accommodate the added complexity of needing the workload to run on multiple cloud platforms. The complexity of transferring workloads across clouds needs to be explored at the application, instance, cloud platform, hypervisor, and network levels." msgstr "" -#: ./doc/arch-design/hybrid/section_user_requirements_hybrid.xml:187(title) +#: ./doc/arch-design/hybrid/section_user_requirements_hybrid.xml:204(title) msgid "Tools considerations" msgstr "" -#: ./doc/arch-design/hybrid/section_user_requirements_hybrid.xml:188(para) +#: ./doc/arch-design/hybrid/section_user_requirements_hybrid.xml:205(para) msgid "When working with designs spanning multiple clouds, the design must incorporate tools to facilitate working across those multiple clouds. Some of the user requirements drive the need for tools that will do the following functions:" msgstr "" -#: ./doc/arch-design/hybrid/section_user_requirements_hybrid.xml:194(para) +#: ./doc/arch-design/hybrid/section_user_requirements_hybrid.xml:211(para) msgid "Broker between clouds: Since the multiple cloud architecture assumes that there will be at least two different and possibly incompatible platforms that are likely to have different costs, brokering software is designed to evaluate relative costs between different cloud platforms. These solutions are sometimes referred to as Cloud Management Platforms (CMPs). Examples include Rightscale, Gravitent, Scalr, CloudForms, and ManageIQ. These tools allow the designer to determine the right location for the workload based on predetermined criteria." msgstr "" -#: ./doc/arch-design/hybrid/section_user_requirements_hybrid.xml:207(para) +#: ./doc/arch-design/hybrid/section_user_requirements_hybrid.xml:224(para) msgid "Facilitate orchestration across the clouds: CMPs are tools are used to tie everything together. Cloud orchestration tools are used to improve the management of IT application portfolios as they migrate onto public, private, and hybrid cloud platforms. These tools are an important consideration. Cloud orchestration tools are used for managing a diverse portfolio of installed systems across multiple cloud platforms. The typical enterprise IT application portfolio is still comprised of a few thousand applications scattered over legacy hardware, virtualized infrastructure, and now dozens of disjointed shadow public Infrastructure-as-a-Service (IaaS) and Software-as-a-Service (SaaS) providers and offerings." msgstr "" -#: ./doc/arch-design/hybrid/section_user_requirements_hybrid.xml:225(title) +#: ./doc/arch-design/hybrid/section_user_requirements_hybrid.xml:242(title) msgid "Network considerations" msgstr "" -#: ./doc/arch-design/hybrid/section_user_requirements_hybrid.xml:226(para) +#: ./doc/arch-design/hybrid/section_user_requirements_hybrid.xml:243(para) msgid "The network services functionality is an important factor to assess when choosing a CMP and cloud provider. Considerations are functionality, security, scalability and HA. Verification and ongoing testing of the critical features of the cloud endpoint used by the architecture are important tasks." msgstr "" -#: ./doc/arch-design/hybrid/section_user_requirements_hybrid.xml:233(para) +#: ./doc/arch-design/hybrid/section_user_requirements_hybrid.xml:250(para) msgid "Once the network functionality framework has been decided, a minimum functionality test should be designed. This will ensure testing and functionality persists during and after upgrades." msgstr "" -#: ./doc/arch-design/hybrid/section_user_requirements_hybrid.xml:239(para) +#: ./doc/arch-design/hybrid/section_user_requirements_hybrid.xml:256(para) msgid "Scalability across multiple cloud providers may dictate which underlying network framework you will choose in different cloud providers. It is important to have the network API functions presented and to verify that functionality persists across all cloud endpoints chosen." msgstr "" -#: ./doc/arch-design/hybrid/section_user_requirements_hybrid.xml:247(para) -msgid "High availability implementations vary in functionality and design. Examples of some common methods are Active-Hot-Standby, Active-Passive and Active-Active. High availability and a test framework needs to be developed to insure that the functionality and limitations are well understood." +#: ./doc/arch-design/hybrid/section_user_requirements_hybrid.xml:264(para) +msgid "High availability implementations vary in functionality and design. Examples of some common methods are active-hot-standby, active-passive and active-active. High availability and a test framework needs to be developed to insure that the functionality and limitations are well understood." msgstr "" -#: ./doc/arch-design/hybrid/section_user_requirements_hybrid.xml:255(para) +#: ./doc/arch-design/hybrid/section_user_requirements_hybrid.xml:272(para) msgid "Security considerations include how data is secured between client and endpoint and any traffic that traverses the multiple clouds, from eavesdropping to DoS activities." msgstr "" -#: ./doc/arch-design/hybrid/section_user_requirements_hybrid.xml:262(title) +#: ./doc/arch-design/hybrid/section_user_requirements_hybrid.xml:279(title) msgid "Risk mitigation and management considerations" msgstr "" -#: ./doc/arch-design/hybrid/section_user_requirements_hybrid.xml:264(para) +#: ./doc/arch-design/hybrid/section_user_requirements_hybrid.xml:281(para) msgid "Hybrid cloud architectures introduce additional risk because they add additional complexity and potentially conflicting or incompatible components or tools. However, they also reduce risk by spreading workloads over multiple providers. This means, if one was to go out of business, the organization could remain operational." msgstr "" -#: ./doc/arch-design/hybrid/section_user_requirements_hybrid.xml:270(para) +#: ./doc/arch-design/hybrid/section_user_requirements_hybrid.xml:287(para) msgid "Risks that will be heightened by using a hybrid cloud architecture include:" msgstr "" -#: ./doc/arch-design/hybrid/section_user_requirements_hybrid.xml:274(para) -msgid "Provider availability or implementation details: This can range from the company going out of business to the company changing how it delivers its services. Cloud architectures are inherently designed to be flexible and changeable; paradoxically, the cloud is both perceived to be rock solid and ever flexible at the same time." +#: ./doc/arch-design/hybrid/section_user_requirements_hybrid.xml:291(term) +msgid "Provider availability or implementation details" msgstr "" -#: ./doc/arch-design/hybrid/section_user_requirements_hybrid.xml:283(para) -msgid "Differing SLAs: Users of hybrid cloud environments potentially encounter some losses through differences in service level agreements. A hybrid cloud design needs to accommodate the different SLAs provided by the various clouds involved in the design, and must address the actual enforceability of the providers' SLAs." +#: ./doc/arch-design/hybrid/section_user_requirements_hybrid.xml:293(para) +msgid "This can range from the company going out of business to the company changing how it delivers its services. Cloud architectures are inherently designed to be flexible and changeable; paradoxically, the cloud is both perceived to be rock solid and ever flexible at the same time." msgstr "" -#: ./doc/arch-design/hybrid/section_user_requirements_hybrid.xml:292(para) -msgid "Security levels: Securing multiple cloud environments is more complex than securing a single cloud environment. Concerns need to be addressed at, but not limited to, the application, network, and cloud platform levels. One issue is that different cloud platforms approach security differently, and a hybrid cloud design must address and compensate for differences in security approaches. For example, AWS uses a relatively simple model that relies on user privilege combined with firewalls." +#: ./doc/arch-design/hybrid/section_user_requirements_hybrid.xml:303(term) +msgid "Differing SLAs" msgstr "" -#: ./doc/arch-design/hybrid/section_user_requirements_hybrid.xml:304(para) -msgid "Provider API changes: APIs are crucial in a hybrid cloud environment. As a consumer of a provider's cloud services, an organization will rarely have any control over provider changes to APIs. Cloud services that might have previously had compatible APIs may no longer work. This is particularly a problem with AWS and OpenStack AWS-compatible APIs. OpenStack was originally planned to maintain compatibility with changes in AWS APIs. However, over time, the APIs have become more divergent in functionality. One way to address this issue is to focus on using only the most common and basic APIs to minimize potential conflicts." +#: ./doc/arch-design/hybrid/section_user_requirements_hybrid.xml:305(para) +msgid "Users of hybrid cloud environments potentially encounter some losses through differences in service level agreements. A hybrid cloud design needs to accommodate the different SLAs provided by the various clouds involved in the design, and must address the actual enforceability of the providers' SLAs." +msgstr "" + +#: ./doc/arch-design/hybrid/section_user_requirements_hybrid.xml:315(term) +msgid "Security levels" +msgstr "" + +#: ./doc/arch-design/hybrid/section_user_requirements_hybrid.xml:317(para) +msgid "Securing multiple cloud environments is more complex than securing a single cloud environment. Concerns need to be addressed at, but not limited to, the application, network, and cloud platform levels. One issue is that different cloud platforms approach security differently, and a hybrid cloud design must address and compensate for differences in security approaches. For example, AWS uses a relatively simple model that relies on user privilege combined with firewalls." +msgstr "" + +#: ./doc/arch-design/hybrid/section_user_requirements_hybrid.xml:330(term) +msgid "Provider API changes" +msgstr "" + +#: ./doc/arch-design/hybrid/section_user_requirements_hybrid.xml:332(para) +msgid "APIs are crucial in a hybrid cloud environment. As a consumer of a provider's cloud services, an organization will rarely have any control over provider changes to APIs. Cloud services that might have previously had compatible APIs may no longer work. This is particularly a problem with AWS and OpenStack AWS-compatible APIs. OpenStack was originally planned to maintain compatibility with changes in AWS APIs. However, over time, the APIs have become more divergent in functionality. One way to address this issue is to focus on using only the most common and basic APIs to minimize potential conflicts." msgstr "" #: ./doc/arch-design/hybrid/section_introduction_hybrid.xml:8(para) @@ -4720,7 +4744,7 @@ msgid "@@image: '../images/Multi-Cloud_Priv-AWS4.png'; md5=482ae466a4f95764cb8f1 msgstr "" #: ./doc/arch-design/hybrid/section_architecture_hybrid.xml:9(para) -msgid "Once business and application requirements have been defined, the first step for designing a hybrid cloud solution is to map out the dependencies between the expected workloads and the diverse cloud infrastructures that need to support them. By mapping the applications and the targeted cloud environments, you can architect a solution that enables the broadest compatibility between cloud platforms and minimizes the need to create workarounds and processes to fill identified gaps. Note the evaluation of the monitoring and orchestration APIs available on each cloud platform and the relative levels of support for them in the chosen Cloud Management Platform." +msgid "Once business and application requirements have been defined, the first step for designing a hybrid cloud solution is to map out the dependencies between the expected workloads and the diverse cloud infrastructures that need to support them. By mapping the applications and the targeted cloud environments, you can architect a solution that enables the broadest compatibility between cloud platforms and minimizes the need to create workarounds and processes to fill identified gaps. Note the evaluation of the monitoring and orchestration APIs available on each cloud platform and the relative levels of support for them in the chosen cloud management platform." msgstr "" #: ./doc/arch-design/hybrid/section_architecture_hybrid.xml:29(title) @@ -4732,66 +4756,66 @@ msgid "The majority of cloud workloads currently run on instances using hypervis msgstr "" #: ./doc/arch-design/hybrid/section_architecture_hybrid.xml:40(para) -msgid "There are conversion tools such as virt-v2v (http://libguestfs.org/virt-v2v/) and virt-edit (http://libguestfs.org/virt-edit.1.html) that can be used in those scenarios but they are often not suitable beyond very basic cloud instance specifications. An alternative is to build a thin operating system image as the base for new instances. This facilitates rapid creation of cloud instances using cloud orchestration or configuration management tools, driven by the CMP, for more specific templating. Another more expensive option is to use a commercial image migration tool. The issue of image portability is not just for a one time migration. If the intention is to use the multiple cloud for disaster recovery, application diversity or high availability, the images and instances are likely to be moved between the different cloud platforms regularly." +msgid "There are conversion tools such as virt-v2v (http://libguestfs.org/virt-v2) and virt-edit (http://libguestfs.org/virt-edit.1.html) that can be used in those scenarios but they are often not suitable beyond very basic cloud instance specifications. An alternative is to build a thin operating system image as the base for new instances. This facilitates rapid creation of cloud instances using cloud orchestration or configuration management tools, driven by the CMP, for more specific templating. Another more expensive option is to use a commercial image migration tool. The issue of image portability is not just for a one time migration. If the intention is to use the multiple cloud for disaster recovery, application diversity or high availability, the images and instances are likely to be moved between the different cloud platforms regularly." msgstr "" -#: ./doc/arch-design/hybrid/section_architecture_hybrid.xml:56(title) +#: ./doc/arch-design/hybrid/section_architecture_hybrid.xml:60(title) msgid "Upper-layer services" msgstr "" -#: ./doc/arch-design/hybrid/section_architecture_hybrid.xml:57(para) +#: ./doc/arch-design/hybrid/section_architecture_hybrid.xml:61(para) msgid "Many clouds offer complementary services over and above the basic compute, network, and storage components. These additional services are often used to simplify the deployment and management of applications on a cloud platform." msgstr "" -#: ./doc/arch-design/hybrid/section_architecture_hybrid.xml:61(para) +#: ./doc/arch-design/hybrid/section_architecture_hybrid.xml:65(para) msgid "Consideration is required to be given to moving workloads that may have upper-layer service dependencies on the source cloud platform to a destination cloud platform that may not have a comparable service. Conversely, the user can implement it in a different way or by using a different technology. For example, moving an application that uses a NoSQL database service such as MongoDB that is delivered as a service on the source cloud, to a destination cloud that does not offer that service or may only use a relational database such as MySQL, could cause difficulties in maintaining the application between the platforms." msgstr "" -#: ./doc/arch-design/hybrid/section_architecture_hybrid.xml:72(para) +#: ./doc/arch-design/hybrid/section_architecture_hybrid.xml:76(para) msgid "There are a number of options that might be appropriate for the hybrid cloud use case:" msgstr "" -#: ./doc/arch-design/hybrid/section_architecture_hybrid.xml:76(para) +#: ./doc/arch-design/hybrid/section_architecture_hybrid.xml:80(para) msgid "Create a baseline of upper-layer services that are implemented across all of the cloud platforms. For platforms that do not support a given service, create a service on top of that platform and apply it to the workloads as they are launched on that cloud. For example, OpenStack, via the Database service for OpenStack (trove), supports MySQL as a service but not NoSQL databases in production. To move from or to run alongside on AWS a NoSQL workload would require recreating the NoSQL database on top of OpenStack and automate the process of implementing it using a tool such as the Orchestration module (heat)." msgstr "" -#: ./doc/arch-design/hybrid/section_architecture_hybrid.xml:91(para) +#: ./doc/arch-design/hybrid/section_architecture_hybrid.xml:95(para) msgid "Deploy a Platform-as-a-Service (PaaS) technology such as Cloud Foundry or OpenShift that abstracts the upper-layer services from the underlying cloud platform. The unit of application deployment and migration is the PaaS and leverages the services of the PaaS and only consumes the base infrastructure services of the cloud platform. The downside to this approach is that the PaaS itself then potentially becomes a source of lock-in." msgstr "" -#: ./doc/arch-design/hybrid/section_architecture_hybrid.xml:102(para) +#: ./doc/arch-design/hybrid/section_architecture_hybrid.xml:106(para) msgid "Use only the base infrastructure services that are common across all cloud platforms. Use automation tools to create the required upper-layer services which are portable across all cloud platforms. For example, instead of using any database services that are inherent in the cloud platforms, launch cloud instances and deploy the databases on to those instances using scripts or various configuration and application deployment tools." msgstr "" -#: ./doc/arch-design/hybrid/section_architecture_hybrid.xml:114(title) +#: ./doc/arch-design/hybrid/section_architecture_hybrid.xml:118(title) msgid "Network services" msgstr "" -#: ./doc/arch-design/hybrid/section_architecture_hybrid.xml:115(para) -msgid "Network services functionality is a significant barrier for multiple cloud architectures. It could be an important factor to assess when choosing a CMP and cloud provider. Considerations are: functionality, security, scalability and High availability (HA). Verification and ongoing testing of the critical features of the cloud endpoint used by the architecture are important tasks." +#: ./doc/arch-design/hybrid/section_architecture_hybrid.xml:119(para) +msgid "Network services functionality is a significant barrier for multiple cloud architectures. It could be an important factor to assess when choosing a CMP and cloud provider. Considerations are: functionality, security, scalability and high availability (HA). Verification and ongoing testing of the critical features of the cloud endpoint used by the architecture are important tasks." msgstr "" -#: ./doc/arch-design/hybrid/section_architecture_hybrid.xml:124(para) +#: ./doc/arch-design/hybrid/section_architecture_hybrid.xml:128(para) msgid "Once the network functionality framework has been decided, a minimum functionality test should be designed to confirm that the functionality is in fact compatible. This will ensure testing and functionality persists during and after upgrades. Note that over time, the diverse cloud platforms are likely to de-synchronize if care is not taken to maintain compatibility. This is a particular issue with APIs." msgstr "" -#: ./doc/arch-design/hybrid/section_architecture_hybrid.xml:135(para) +#: ./doc/arch-design/hybrid/section_architecture_hybrid.xml:139(para) msgid "Scalability across multiple cloud providers may dictate which underlying network framework is chosen for the different cloud providers. It is important to have the network API functions presented and to verify that the desired functionality persists across all chosen cloud endpoint." msgstr "" -#: ./doc/arch-design/hybrid/section_architecture_hybrid.xml:143(para) -msgid "High availability (HA) implementations vary in functionality and design. Examples of some common methods are Active-Hot-Standby, Active-Passive and Active-Active. High availability and a test framework need to be developed to insure that the functionality and limitations are well understood." +#: ./doc/arch-design/hybrid/section_architecture_hybrid.xml:147(para) +msgid "High availability (HA) implementations vary in functionality and design. Examples of some common methods are active-hot-standby, active-passive and active-active. High availability and a test framework need to be developed to insure that the functionality and limitations are well understood." msgstr "" -#: ./doc/arch-design/hybrid/section_architecture_hybrid.xml:151(para) +#: ./doc/arch-design/hybrid/section_architecture_hybrid.xml:155(para) msgid "Security considerations, such as how data is secured between client and endpoint and any traffic that traverses the multiple clouds, from eavesdropping to DoS activities must be addressed. Business and regulatory requirements dictate the security approach that needs to be taken." msgstr "" -#: ./doc/arch-design/hybrid/section_architecture_hybrid.xml:160(para) +#: ./doc/arch-design/hybrid/section_architecture_hybrid.xml:164(para) msgid "Replication has been the traditional method for protecting object store implementations. A variety of different implementations have existed in storage architectures. Examples of this are both synchronous and asynchronous mirroring. Most object stores and back-end storage systems have a method for replication that can be implemented at the storage subsystem layer. Object stores also have implemented replication techniques that can be tailored to fit a clouds needs. An organization must find the right balance between data integrity and data availability. Replication strategy may also influence the disaster recovery methods implemented." msgstr "" -#: ./doc/arch-design/hybrid/section_architecture_hybrid.xml:172(para) +#: ./doc/arch-design/hybrid/section_architecture_hybrid.xml:176(para) msgid "Replication across different racks, data centers and geographical regions has led to the increased focus of determining and ensuring data locality. The ability to guarantee data is accessed from the nearest or fastest storage can be necessary for applications to perform well. Examples of this are Hadoop running in a cloud. The user either runs with a native HDFS, when applicable, or on a separate parallel file system such as those provided by Hitachi and IBM. Special consideration should be taken when running embedded object store methods to not cause extra data replication, which can create unnecessary performance issues. Another example of ensuring data locality is by using Ceph. Ceph has a data container abstraction called a pool. Pools can be created with replicas or erasure code. Replica based pools can also have a rule set defined to have data written to a “local” set of hardware which would be the primary access and modification point." msgstr "" @@ -4820,7 +4844,7 @@ msgid "Bursting workloads from private to public non-OpenStack clouds" msgstr "" #: ./doc/arch-design/hybrid/section_prescriptive_examples_hybrid.xml:21(para) -msgid "High Availability across clouds (for technical diversity)" +msgid "High availability across clouds (for technical diversity)" msgstr "" #: ./doc/arch-design/hybrid/section_prescriptive_examples_hybrid.xml:25(para) @@ -4872,7 +4896,7 @@ msgid "For an OpenStack-to-AWS hybrid cloud, the architecture looks similar to t msgstr "" #: ./doc/arch-design/hybrid/section_prescriptive_examples_hybrid.xml:87(para) -msgid "In this scenario CompanyA has an additional requirement in that the developers were already using AWS for some of their work and did not want to change the cloud provider. Primarily due to excessive overhead with network firewall rules that needed to be created and corporate financial procedures that required entering into an agreement with a new provider." +msgid "In this scenario company A has an additional requirement in that the developers were already using AWS for some of their work and did not want to change the cloud provider. Primarily due to excessive overhead with network firewall rules that needed to be created and corporate financial procedures that required entering into an agreement with a new provider." msgstr "" #: ./doc/arch-design/hybrid/section_prescriptive_examples_hybrid.xml:94(para) @@ -4900,14 +4924,14 @@ msgid "The object storage relies on the replication capabilities of the object s msgstr "" #: ./doc/arch-design/hybrid/section_prescriptive_examples_hybrid.xml:147(para) -msgid "For block storage, the replication is a little more difficult, and involves tools outside of OpenStack itself. The OpenStack Block Storage volume is not set as the drive itself but as a logical object that points to a physical back end. The disaster recovery is configured for Block Storage for synchronous backup for the highest level of data protection, but asynchronous backup could have been set as an alternative that is not as latency sensitive. For asynchronous backup, the Cinder API makes it possible to export the data and also the metadata of a particular volume, so that it can be moved and replicated elsewhere. More information can be found here: https://blueprints.launchpad.net/cinder/+spec/cinder-backup-volume-metadata-support." +msgid "For block storage, the replication is a little more difficult, and involves tools outside of OpenStack itself. The OpenStack Block Storage volume is not set as the drive itself but as a logical object that points to a physical back end. The disaster recovery is configured for Block Storage for synchronous backup for the highest level of data protection, but asynchronous backup could have been set as an alternative that is not as latency sensitive. For asynchronous backup, the Block Storage API makes it possible to export the data and also the metadata of a particular volume, so that it can be moved and replicated elsewhere. More information can be found here: https://blueprints.launchpad.net/cinder/+spec/cinder-backup-volume-metadata-support." msgstr "" -#: ./doc/arch-design/hybrid/section_prescriptive_examples_hybrid.xml:159(para) +#: ./doc/arch-design/hybrid/section_prescriptive_examples_hybrid.xml:161(para) msgid "The synchronous backups create an identical volume in both clouds and chooses the appropriate flavor so that each cloud has an identical back end. This was done by creating volumes through the CMP, because the CMP knows to create identical volumes in both clouds. Once this is configured, a solution, involving DRDB, is used to synchronize the actual physical drives." msgstr "" -#: ./doc/arch-design/hybrid/section_prescriptive_examples_hybrid.xml:166(para) +#: ./doc/arch-design/hybrid/section_prescriptive_examples_hybrid.xml:168(para) msgid "The database component is backed up using synchronous backups. MySQL does not support geographically diverse replication, so disaster recovery is provided by replicating the file itself. As it is not possible to use object storage as the back end of a database like MySQL, Swift replication was not an option. It was decided not to store the data on another geo-tiered storage system, such as Ceph, as block storage. This would have given another layer of protection. Another option would have been to store the database on an OpenStack Block Storage volume and backing it up just as any other block storage." msgstr "" @@ -4944,11 +4968,11 @@ msgid "Another consideration is upgrades to the CMP which may need to be complet msgstr "" #: ./doc/arch-design/hybrid/section_operational_considerations_hybrid.xml:73(title) -msgid "Network Operation Center (NOC)" +msgid "Network Operation Center" msgstr "" #: ./doc/arch-design/hybrid/section_operational_considerations_hybrid.xml:74(para) -msgid "When planning the Network Operation Center for a hybrid cloud environment, it is important to recognize where control over each piece of infrastructure resides. If a significant portion of the cloud is on externally managed systems, be prepared for situations in which it may not be possible to make changes at all or at the most convenient time. Additionally, situations of conflict may arise in which multiple providers have differing points of view on the way infrastructure must be managed and exposed. This can lead to delays in root cause and analysis where each insists the blame lies with the other provider." +msgid "When planning the Network Operation Center (NOC) for a hybrid cloud environment, it is important to recognize where control over each piece of infrastructure resides. If a significant portion of the cloud is on externally managed systems, be prepared for situations in which it may not be possible to make changes at all or at the most convenient time. Additionally, situations of conflict may arise in which multiple providers have differing points of view on the way infrastructure must be managed and exposed. This can lead to delays in root cause and analysis where each insists the blame lies with the other provider." msgstr "" #: ./doc/arch-design/hybrid/section_operational_considerations_hybrid.xml:85(para) @@ -4963,167 +4987,171 @@ msgstr "" msgid "Operating hybrid clouds is a situation in which there is a greater reliance on third party systems and processes. As a result of a lack of control of various pieces of a hybrid cloud environment, it is not necessarily possible to guarantee proper maintenance of the overall system. Instead, the user must be prepared to abandon workloads and spin them up again in an improved state. Having a hybrid cloud deployment does, however, provide agility for these situations by allowing the migration of workloads to alternative clouds in response to cloud-specific issues." msgstr "" -#: ./doc/arch-design/hybrid/section_tech_considerations_hybrid.xml:9(para) +#: ./doc/arch-design/hybrid/section_tech_considerations_hybrid.xml:13(para) msgid "A hybrid cloud environment requires inspection and understanding of technical issues that are not only outside of an organization's data center, but potentially outside of an organization's control. In many cases, it is necessary to ensure that the architecture and CMP chosen can adapt to, not only to different environments, but also to the possibility of change. In this situation, applications are crossing diverse platforms and are likely to be located in diverse locations. All of these factors will influence and add complexity to the design of a hybrid cloud architecture." msgstr "" -#: ./doc/arch-design/hybrid/section_tech_considerations_hybrid.xml:19(para) +#: ./doc/arch-design/hybrid/section_tech_considerations_hybrid.xml:23(para) msgid "The only situation where cloud platform incompatibilities are not going to be an issue is when working with clouds that are based on the same version and the same distribution of OpenStack. Otherwise incompatibilities are virtually inevitable." msgstr "" -#: ./doc/arch-design/hybrid/section_tech_considerations_hybrid.xml:24(para) +#: ./doc/arch-design/hybrid/section_tech_considerations_hybrid.xml:28(para) msgid "Incompatibility should be less of an issue for clouds that exclusively use the same version of OpenStack, even if they use different distributions. The newer the distribution in question, the less likely it is that there will be incompatibilities between version. This is due to the fact that the OpenStack community has established an initiative to define core functions that need to remain backward compatible between supported versions. The DefCore initiative defines basic functions that every distribution must support in order to bear the name \"OpenStack\"." msgstr "" -#: ./doc/arch-design/hybrid/section_tech_considerations_hybrid.xml:34(para) +#: ./doc/arch-design/hybrid/section_tech_considerations_hybrid.xml:38(para) msgid "Some vendors, however, add proprietary customizations to their distributions. If an application or architecture makes use of these features, it will be difficult to migrate to or use other types of environments. Anyone considering incorporating older versions of OpenStack prior to Havana should consider carefully before attempting to incorporate functionality between versions. Internal differences in older versions may be so great that the best approach might be to consider the versions to be essentially diverse platforms, as different as OpenStack and Amazon Web Services or Microsoft Azure." msgstr "" -#: ./doc/arch-design/hybrid/section_tech_considerations_hybrid.xml:45(para) +#: ./doc/arch-design/hybrid/section_tech_considerations_hybrid.xml:49(para) msgid "The situation is more predictable if using different cloud platforms is incorporated from inception. If the other clouds are not based on OpenStack, then all pretense of compatibility vanishes, and CMP tools must account for the myriad of differences in the way operations are handled and services are implemented. Some situations in which these incompatibilities can arise include differences between the way in which a cloud:" msgstr "" -#: ./doc/arch-design/hybrid/section_tech_considerations_hybrid.xml:55(para) +#: ./doc/arch-design/hybrid/section_tech_considerations_hybrid.xml:59(para) msgid "Deploys instances" msgstr "" -#: ./doc/arch-design/hybrid/section_tech_considerations_hybrid.xml:58(para) +#: ./doc/arch-design/hybrid/section_tech_considerations_hybrid.xml:62(para) msgid "Manages networks" msgstr "" -#: ./doc/arch-design/hybrid/section_tech_considerations_hybrid.xml:61(para) +#: ./doc/arch-design/hybrid/section_tech_considerations_hybrid.xml:65(para) msgid "Treats applications" msgstr "" -#: ./doc/arch-design/hybrid/section_tech_considerations_hybrid.xml:64(para) +#: ./doc/arch-design/hybrid/section_tech_considerations_hybrid.xml:68(para) msgid "Implements services" msgstr "" -#: ./doc/arch-design/hybrid/section_tech_considerations_hybrid.xml:69(para) +#: ./doc/arch-design/hybrid/section_tech_considerations_hybrid.xml:73(para) msgid "One of the primary reasons many organizations turn to a hybrid cloud system is to increase capacity without having to make large capital investments. However, capacity planning is still necessary when designing an OpenStack installation even if it is augmented with external clouds." msgstr "" -#: ./doc/arch-design/hybrid/section_tech_considerations_hybrid.xml:74(para) +#: ./doc/arch-design/hybrid/section_tech_considerations_hybrid.xml:78(para) msgid "Specifically, overall capacity and placement of workloads need to be accounted for when designing for a mostly internally-operated cloud with the occasional capacity burs. The long-term capacity plan for such a design needs to incorporate growth over time to prevent the need to permanently burst into, and occupy, a potentially more expensive external cloud. In order to avoid this scenario, account for the future applications and capacity requirements and plan growth appropriately." msgstr "" -#: ./doc/arch-design/hybrid/section_tech_considerations_hybrid.xml:83(para) +#: ./doc/arch-design/hybrid/section_tech_considerations_hybrid.xml:87(para) msgid "One of the drawbacks of capacity planning is unpredictability. It is difficult to predict the amount of load a particular application might incur if the number of users fluctuates or the application experiences an unexpected increase in popularity. It is possible to define application requirements in terms of vCPU, RAM, bandwidth or other resources and plan appropriately, but other clouds may not use the same metric or even the same oversubscription rates." msgstr "" -#: ./doc/arch-design/hybrid/section_tech_considerations_hybrid.xml:92(para) -msgid "Oversubscription is a method to emulate more capacity than they may physically be present. For example, a physical hypervisor node with 32 gigabytes of RAM may host 24 instances, each provisioned with 2 gigabytes of RAM. As long as all 24 of them are not concurrently utilizing 2 full gigabytes, this arrangement is a non-issue. However, some hosts take oversubscription to extremes and, as a result, performance can frequently be inconsistent. If at all possible, determine what the oversubscription rates of each host are and plan capacity accordingly." +#: ./doc/arch-design/hybrid/section_tech_considerations_hybrid.xml:96(para) +msgid "Oversubscription is a method to emulate more capacity than they may physically be present. For example, a physical hypervisor node with 32GB RAM may host 24 instances, each provisioned with 2GB RAM. As long as all 24 of them are not concurrently utilizing 2 full gigabytes, this arrangement is a non-issue. However, some hosts take oversubscription to extremes and, as a result, performance can frequently be inconsistent. If at all possible, determine what the oversubscription rates of each host are and plan capacity accordingly." msgstr "" -#: ./doc/arch-design/hybrid/section_tech_considerations_hybrid.xml:104(para) +#: ./doc/arch-design/hybrid/section_tech_considerations_hybrid.xml:108(para) msgid "The nature of a hybrid cloud environment removes complete control over the infrastructure. Security becomes a stronger requirement because data or applications may exist in a cloud that is outside of an organization's control. Security domains become an important distinction when planning for a hybrid cloud environment and its capabilities. A security domain comprises users, applications, servers or networks that share common trust requirements and expectations within a system." msgstr "" -#: ./doc/arch-design/hybrid/section_tech_considerations_hybrid.xml:113(para) +#: ./doc/arch-design/hybrid/section_tech_considerations_hybrid.xml:117(para) msgid "The security domains are:" msgstr "" -#: ./doc/arch-design/hybrid/section_tech_considerations_hybrid.xml:128(para) +#: ./doc/arch-design/hybrid/section_tech_considerations_hybrid.xml:132(para) msgid "These security domains can be mapped individually to the organization's installation or combined. For example, some deployment topologies combine both guest and data domains onto one physical network, whereas other topologies may physically separate these networks. In each case, the cloud operator should be aware of the appropriate security concerns. Security domains should be mapped out against the 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/hybrid/section_tech_considerations_hybrid.xml:138(para) +#: ./doc/arch-design/hybrid/section_tech_considerations_hybrid.xml:142(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 an organization has no authority. This domain should always be considered untrusted. When considering hybrid cloud deployments, any traffic traversing beyond and between the multiple clouds should always be considered to reside in this security domain and is therefore untrusted." msgstr "" -#: ./doc/arch-design/hybrid/section_tech_considerations_hybrid.xml:146(para) +#: ./doc/arch-design/hybrid/section_tech_considerations_hybrid.xml:150(para) msgid "Typically used for instance-to-instance traffic within a single data center, 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 that are used in a hybrid cloud configuration which an organization does not control 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 consider this network as internal and therefore trusted only if there are controls in place to assert that instances and tenants are trusted." msgstr "" -#: ./doc/arch-design/hybrid/section_tech_considerations_hybrid.xml:158(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 deployments behind an organization's firewall, this domain is considered trusted. In a public cloud model which could be part of an architecture, this would have to be assessed with the Public Cloud provider to understand the controls in place." +#: ./doc/arch-design/hybrid/section_tech_considerations_hybrid.xml:162(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 deployments behind an organization's firewall, this domain is considered trusted. In a public cloud model which could be part of an architecture, this would have to be assessed with the public cloud provider to understand the controls in place." msgstr "" -#: ./doc/arch-design/hybrid/section_tech_considerations_hybrid.xml:166(para) +#: ./doc/arch-design/hybrid/section_tech_considerations_hybrid.xml:170(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 there may also be strong availability requirements. The trust level of this network is heavily dependent on deployment decisions and as such this is not assigned a default level of trust." msgstr "" -#: ./doc/arch-design/hybrid/section_tech_considerations_hybrid.xml:174(para) +#: ./doc/arch-design/hybrid/section_tech_considerations_hybrid.xml:178(para) msgid "Consideration must be taken when managing the users of the system, whether operating or utilizing public or private clouds. The identity service allows for LDAP to be part of the authentication process. Including such systems in your OpenStack deployments may ease user management if integrating into existing systems. Be mindful when utilizing 3rd party clouds to explore authentication options applicable to the installation to help manage and keep user authentication consistent." msgstr "" -#: ./doc/arch-design/hybrid/section_tech_considerations_hybrid.xml:183(para) +#: ./doc/arch-design/hybrid/section_tech_considerations_hybrid.xml:187(para) msgid "Due to the process of passing user names, passwords, and generated tokens between client machines and API endpoints, placing API services behind hardware that performs SSL termination is strongly recommended." msgstr "" -#: ./doc/arch-design/hybrid/section_tech_considerations_hybrid.xml:187(para) +#: ./doc/arch-design/hybrid/section_tech_considerations_hybrid.xml:191(para) msgid "Within cloud components themselves, another component that needs security scrutiny is the hypervisor. In a public cloud, organizations typically do not have control over the choice of hypervisor. (Amazon uses its own particular version of Xen, for example.) In some cases, hypervisors may be vulnerable to a type of attack called \"hypervisor breakout\" if they are not properly secured. Hypervisor breakout describes the event of a compromised or malicious instance breaking out of the resource controls of the hypervisor and gaining access to the bare metal operating system and hardware resources." msgstr "" -#: ./doc/arch-design/hybrid/section_tech_considerations_hybrid.xml:197(para) +#: ./doc/arch-design/hybrid/section_tech_considerations_hybrid.xml:201(para) msgid "If the security of instances is not considered important, there may not be an issue. In most cases, however, enterprises need to avoid this kind of vulnerability, and the only way to do that is to avoid a situation in which the instances are running on a public cloud. That does not mean that there is a need to own all of the infrastructure on which an OpenStack installation operates; it suggests avoiding situations in which hardware may be shared with others." msgstr "" -#: ./doc/arch-design/hybrid/section_tech_considerations_hybrid.xml:205(para) +#: ./doc/arch-design/hybrid/section_tech_considerations_hybrid.xml:209(para) msgid "There are other services worth considering that provide a bare metal instance instead of a cloud. In other cases, it is possible to replicate a second private cloud by integrating with a private Cloud-as-a-Service deployment, in which an organization does not buy hardware, but also does not share it with other tenants. It is also possible use a provider that hosts a bare-metal \"public\" cloud instance for which the hardware is dedicated only to one customer, or a provider that offers private Cloud-as-a-Service." msgstr "" -#: ./doc/arch-design/hybrid/section_tech_considerations_hybrid.xml:214(para) +#: ./doc/arch-design/hybrid/section_tech_considerations_hybrid.xml:218(para) msgid "Finally, it is important to realize that each cloud implements services differently. What keeps data secure in one cloud may not do the same in another. Be sure to know the security requirements of every cloud that handles the organization's data or workloads." msgstr "" #: ./doc/arch-design/hybrid/section_tech_considerations_hybrid.xml:223(para) +msgid "More information on OpenStack Security can be found in the OpenStack Security Guide." +msgstr "" + +#: ./doc/arch-design/hybrid/section_tech_considerations_hybrid.xml:231(para) msgid "When it comes to utilization, it is important that the CMP understands what workloads are running, where they are running, and their preferred utilizations. For example, in most cases it is desirable to run as many workloads internally as possible, utilizing other resources only when necessary. On the other hand, situations exist in which the opposite is true. The internal cloud may only be for development and stressing it is undesirable. In most cases, a cost model of various scenarios helps with this decision, however this analysis is heavily influenced by internal priorities. The important thing is the ability to efficiently make those decisions on a programmatic basis." msgstr "" -#: ./doc/arch-design/hybrid/section_tech_considerations_hybrid.xml:235(para) +#: ./doc/arch-design/hybrid/section_tech_considerations_hybrid.xml:243(para) msgid "The Telemetry module (ceilometer) is designed to provide information on the usage of various OpenStack components. There are two limitations to consider: first, if there is to be a large amount of data (for example, if monitoring a large cloud, or a very active one) it is desirable to use a NoSQL back end for Ceilometer, such as MongoDB. Second, when connecting to a non-OpenStack cloud, there will need to be a way to monitor that usage and to provide that monitoring data back to the CMP." msgstr "" -#: ./doc/arch-design/hybrid/section_tech_considerations_hybrid.xml:246(para) +#: ./doc/arch-design/hybrid/section_tech_considerations_hybrid.xml:254(para) msgid "Performance is of primary importance in the design of a cloud. When it comes to a hybrid cloud deployment, many of the same issues for multi-site deployments apply, such as network latency between sites. It is also important to think about the speed at which a workload can be spun up in another cloud, and what can be done to reduce the time necessary to accomplish that task. That may mean moving data closer to applications, or conversely, applications closer to the data they process. It may mean grouping functionality so that connections that require low latency take place over a single cloud rather than spanning clouds. That may also mean ensuring that the CMP has the intelligence to know which cloud can most efficiently run which types of workloads." msgstr "" -#: ./doc/arch-design/hybrid/section_tech_considerations_hybrid.xml:259(para) +#: ./doc/arch-design/hybrid/section_tech_considerations_hybrid.xml:267(para) msgid "As with utilization, native OpenStack tools are available to assist. Ceilometer can measure performance and, if necessary, the Orchestration module can be used to react to changes in demand by spinning up more resources. It is important to note, however, that Orchestration requires special configurations in the client to enable functioning with solution offerings from Amazon Web Services. When dealing with other types of clouds, it is necessary to rely on the features of the CMP." msgstr "" -#: ./doc/arch-design/hybrid/section_tech_considerations_hybrid.xml:269(title) +#: ./doc/arch-design/hybrid/section_tech_considerations_hybrid.xml:277(title) msgid "Components" msgstr "" -#: ./doc/arch-design/hybrid/section_tech_considerations_hybrid.xml:270(para) +#: ./doc/arch-design/hybrid/section_tech_considerations_hybrid.xml:278(para) msgid "The number and types of native OpenStack components that are available for use is dependent on whether the deployment is exclusively an OpenStack cloud or not. If so, all of the OpenStack components will be available for use, and in many ways the issues that need to be considered will be similar to those that need to be considered for a multi-site deployment." msgstr "" -#: ./doc/arch-design/hybrid/section_tech_considerations_hybrid.xml:277(para) +#: ./doc/arch-design/hybrid/section_tech_considerations_hybrid.xml:285(para) msgid "That said, in any situation in which more than one cloud is being used, at least four OpenStack tools will be considered:" msgstr "" -#: ./doc/arch-design/hybrid/section_tech_considerations_hybrid.xml:282(para) -msgid "OpenStack Compute (Nova): Regardless of deployment location, hypervisor choice has a direct effect on how difficult it is to integrate with one or more additional clouds. For example, integrating a Hyper-V based OpenStack cloud with Azure will have less compatibility issues than if KVM is used." -msgstr "" - #: ./doc/arch-design/hybrid/section_tech_considerations_hybrid.xml:290(para) -msgid "Networking: Whether OpenStack Networking (Neutron) or Nova-network is used, the network is one place where integration capabilities need to be understood in order to connect between clouds." +msgid "OpenStack Compute (nova): Regardless of deployment location, hypervisor choice has a direct effect on how difficult it is to integrate with one or more additional clouds. For example, integrating a Hyper-V based OpenStack cloud with Azure will have less compatibility issues than if KVM is used." msgstr "" -#: ./doc/arch-design/hybrid/section_tech_considerations_hybrid.xml:296(para) -msgid "Telemetry module (Ceilometer): Use of Telemetery depends, in large part, on what the other parts of the cloud are using." +#: ./doc/arch-design/hybrid/section_tech_considerations_hybrid.xml:298(para) +msgid "Networking: Whether OpenStack Networking (neutron) or nova-network is used, the network is one place where integration capabilities need to be understood in order to connect between clouds." msgstr "" -#: ./doc/arch-design/hybrid/section_tech_considerations_hybrid.xml:301(para) -msgid "Orchestration module (Heat): Similarly, Orchestration can be a valuable tool in orchestrating tasks a CMP decides are necessary in an OpenStack-based cloud." -msgstr "" - -#: ./doc/arch-design/hybrid/section_tech_considerations_hybrid.xml:308(title) -msgid "Special considerations" +#: ./doc/arch-design/hybrid/section_tech_considerations_hybrid.xml:304(para) +msgid "Telemetry module (ceilometer): Use of Telemetery depends, in large part, on what the other parts of the cloud are using." msgstr "" #: ./doc/arch-design/hybrid/section_tech_considerations_hybrid.xml:309(para) +msgid "Orchestration module (heat): Similarly, Orchestration can be a valuable tool in orchestrating tasks a CMP decides are necessary in an OpenStack-based cloud." +msgstr "" + +#: ./doc/arch-design/hybrid/section_tech_considerations_hybrid.xml:316(title) +msgid "Special considerations" +msgstr "" + +#: ./doc/arch-design/hybrid/section_tech_considerations_hybrid.xml:317(para) msgid "Hybrid cloud deployments also involve two more issues that are not common in other situations:" msgstr "" -#: ./doc/arch-design/hybrid/section_tech_considerations_hybrid.xml:311(para) +#: ./doc/arch-design/hybrid/section_tech_considerations_hybrid.xml:319(para) msgid "Image portability: Note that, as of the Icehouse release, there is no single common image format that is usable by all clouds. This means that images will need to be converted or recreated when porting between clouds. To make things simpler, launch the smallest and simplest images feasible, installing only what is necessary preferably using a deployment manager such as Chef or Puppet. That means not to use golden images for speeding up the process, however if the same images are being repeatedly deployed it may make more sense to utilize this technique instead of provisioning applications on lighter images each time." msgstr "" -#: ./doc/arch-design/hybrid/section_tech_considerations_hybrid.xml:322(para) +#: ./doc/arch-design/hybrid/section_tech_considerations_hybrid.xml:330(para) msgid "API differences: The most profound issue that cannot be avoided when using a hybrid cloud deployment with more than just OpenStack (or with different versions of OpenStack) is that the APIs needed to perform certain functions are different. The CMP needs to know how to handle all necessary versions. To get around this issue, some implementers build portals to achieve a hybrid cloud environment, but a heavily developer-focused organization will get more use out of a hybrid cloud broker SDK such as jClouds." msgstr "" @@ -5131,59 +5159,55 @@ msgstr "" msgid "More so than other scenarios, defining user requirements for a massively scalable OpenStack design architecture dictates approaching the design from two different, yet sometimes opposing, perspectives: the cloud user, and the cloud operator. The expectations and perceptions of the consumption and management of resources of a massively scalable OpenStack cloud from the user point of view is distinctly different from that of the cloud operator." msgstr "" -#: ./doc/arch-design/massively_scalable/section_user_requirements_massively_scalable.xml:42(para) -msgid "Examples of such legal frameworks include the data protection framework of the European Union (http://ec.europa.eu/justice/data-protection/ ) and the requirements of the Financial Industry Regulatory Authority (http://www.finra.org/Industry/Regulation/FINRARules/ ) in the United States. Consult a local regulatory body for more information." -msgstr "" - -#: ./doc/arch-design/massively_scalable/section_user_requirements_massively_scalable.xml:51(para) +#: ./doc/arch-design/massively_scalable/section_user_requirements_massively_scalable.xml:53(para) msgid "Massively scalable OpenStack clouds have the following user requirements:" msgstr "" -#: ./doc/arch-design/massively_scalable/section_user_requirements_massively_scalable.xml:55(para) +#: ./doc/arch-design/massively_scalable/section_user_requirements_massively_scalable.xml:57(para) msgid "The cloud user expects repeatable, dependable, and deterministic processes for launching and deploying cloud resources. This could be delivered through a web-based interface or publicly available API endpoints. All appropriate options for requesting cloud resources need to be available through some type of user interface, a command-line interface (CLI), or API endpoints." msgstr "" -#: ./doc/arch-design/massively_scalable/section_user_requirements_massively_scalable.xml:65(para) +#: ./doc/arch-design/massively_scalable/section_user_requirements_massively_scalable.xml:67(para) msgid "Cloud users expect a fully self-service and on-demand consumption model. When an OpenStack cloud reaches the \"massively scalable\" size, it means it is expected to be consumed \"as a service\" in each and every way." msgstr "" -#: ./doc/arch-design/massively_scalable/section_user_requirements_massively_scalable.xml:72(para) +#: ./doc/arch-design/massively_scalable/section_user_requirements_massively_scalable.xml:74(para) msgid "For a user of a massively scalable OpenStack public cloud, there will be no expectations for control over security, performance, or availability. Only SLAs related to uptime of API services are expected, and very basic SLAs expected of services offered. The user understands it is his or her responsibility to address these issues on their own. The exception to this expectation is the rare case of a massively scalable cloud infrastructure built for a private or government organization that has specific requirements." msgstr "" -#: ./doc/arch-design/massively_scalable/section_user_requirements_massively_scalable.xml:84(para) +#: ./doc/arch-design/massively_scalable/section_user_requirements_massively_scalable.xml:86(para) msgid "As might be expected, the cloud user requirements or expectations that determine the design are all focused on the consumption model. The user expects to be able to easily consume cloud resources in an automated and deterministic way, without any need for knowledge of the capacity, scalability, or other attributes of the cloud's underlying infrastructure." msgstr "" -#: ./doc/arch-design/massively_scalable/section_user_requirements_massively_scalable.xml:92(title) +#: ./doc/arch-design/massively_scalable/section_user_requirements_massively_scalable.xml:94(title) msgid "Operator requirements" msgstr "" -#: ./doc/arch-design/massively_scalable/section_user_requirements_massively_scalable.xml:93(para) +#: ./doc/arch-design/massively_scalable/section_user_requirements_massively_scalable.xml:95(para) msgid "Whereas the cloud user should be completely unaware of the underlying infrastructure of the cloud and its attributes, the operator must be able to build and support the infrastructure, as well as how it needs to operate at scale. This presents a very demanding set of requirements for building such a cloud from the operator's perspective:" msgstr "" -#: ./doc/arch-design/massively_scalable/section_user_requirements_massively_scalable.xml:101(para) +#: ./doc/arch-design/massively_scalable/section_user_requirements_massively_scalable.xml:103(para) msgid "First and foremost, everything must be capable of automation. From the deployment of new hardware, compute hardware, storage hardware, or networking hardware, to the installation and configuration of the supporting software, everything must be capable of being automated. Manual processes will not suffice in a massively scalable OpenStack design architecture." msgstr "" -#: ./doc/arch-design/massively_scalable/section_user_requirements_massively_scalable.xml:111(para) -msgid "The cloud operator requires that capital expenditure (CapEx) is minimized at all layers of the stack. Operators of massively scalable OpenStack clouds require the use of dependable commodity hardware and freely available open source software components to reduce deployment costs and operational expenses. Initiatives like OpenCompute (more information available at http://www.opencompute.org) provide additional information and pointers. To cut costs, many operators sacrifice redundancy. For example, redundant power supplies, redundant network connections, and redundant rack switches." +#: ./doc/arch-design/massively_scalable/section_user_requirements_massively_scalable.xml:113(para) +msgid "The cloud operator requires that capital expenditure (CapEx) is minimized at all layers of the stack. Operators of massively scalable OpenStack clouds require the use of dependable commodity hardware and freely available open source software components to reduce deployment costs and operational expenses. Initiatives like OpenCompute (more information available at http://www.opencompute.org) provide additional information and pointers. To cut costs, many operators sacrifice redundancy. For example, redundant power supplies, redundant network connections, and redundant rack switches." msgstr "" -#: ./doc/arch-design/massively_scalable/section_user_requirements_massively_scalable.xml:125(para) +#: ./doc/arch-design/massively_scalable/section_user_requirements_massively_scalable.xml:128(para) msgid "Companies operating a massively scalable OpenStack cloud also require that operational expenditures (OpEx) be minimized as much as possible. It is recommended that cloud-optimized hardware is a good approach when managing operational overhead. Some of the factors that need to be considered include power, cooling, and the physical design of the chassis. It is possible to customize the hardware and systems so they are optimized for this type of workload because of the scale of these implementations." msgstr "" -#: ./doc/arch-design/massively_scalable/section_user_requirements_massively_scalable.xml:137(para) +#: ./doc/arch-design/massively_scalable/section_user_requirements_massively_scalable.xml:140(para) msgid "Massively scalable OpenStack clouds require extensive metering and monitoring functionality to maximize the operational efficiency by keeping the operator informed about the status and state of the infrastructure. This includes full scale metering of the hardware and software status. A corresponding framework of logging and alerting is also required to store and allow operations to act upon the metrics provided by the metering and monitoring solution(s). The cloud operator also needs a solution that uses the data provided by the metering and monitoring solution to provide capacity planning and capacity trending analysis." msgstr "" -#: ./doc/arch-design/massively_scalable/section_user_requirements_massively_scalable.xml:152(para) -msgid "A massively scalable OpenStack cloud will be a multi-site cloud. Therefore, the user-operator requirements for a multi-site OpenStack architecture design are also applicable here. This includes various legal requirements for data storage, data placement, and data retention; other jurisdictional legal or compliance requirements; image consistency-availability; storage replication and availability (both block and file/object storage); and authentication, authorization, and auditing (AAA), just to name a few. Refer to the \"Multi-Site\" section for more details on requirements and considerations for multi-site OpenStack clouds." +#: ./doc/arch-design/massively_scalable/section_user_requirements_massively_scalable.xml:155(para) +msgid "A massively scalable OpenStack cloud will be a multi-site cloud. Therefore, the user-operator requirements for a multi-site OpenStack architecture design are also applicable here. This includes various legal requirements for data storage, data placement, and data retention; other jurisdictional legal or compliance requirements; image consistency-availability; storage replication and availability (both block and file/object storage); and authentication, authorization, and auditing (AAA), just to name a few. Refer to the for more details on requirements and considerations for multi-site OpenStack clouds." msgstr "" -#: ./doc/arch-design/massively_scalable/section_user_requirements_massively_scalable.xml:167(para) +#: ./doc/arch-design/massively_scalable/section_user_requirements_massively_scalable.xml:170(para) msgid "Considerations around physical facilities such as space, floor weight, rack height and type, environmental considerations, power usage and power usage efficiency (PUE), and physical security must also be addressed by the design architecture of a massively scalable OpenStack cloud." msgstr "" @@ -5268,77 +5292,77 @@ msgid "Skills and training" msgstr "" #: ./doc/arch-design/massively_scalable/section_operational_considerations_massively_scalable.xml:91(para) -msgid "Projecting growth for storage, networking, and compute is only one aspect of a growth plan for running OpenStack at massive scale. Growing and nurturing development and operational staff is an additional consideration. Sending team members to OpenStack conferences, meetup events, and encouraging active participation in the mailing lists and committees is a very important way to maintain skills and forge relationships in the community. A list of OpenStack training providers in the marketplace can be found here: http://www.openstack.org/marketplace/training/." +msgid "Projecting growth for storage, networking, and compute is only one aspect of a growth plan for running OpenStack at massive scale. Growing and nurturing development and operational staff is an additional consideration. Sending team members to OpenStack conferences, meetup events, and encouraging active participation in the mailing lists and committees is a very important way to maintain skills and forge relationships in the community. A list of OpenStack training providers in the marketplace can be found here: http://www.openstack.org/marketplace/training/." msgstr "" #. When image changes, this message will be marked fuzzy or untranslated for you. #. It doesn't matter what you translate it to: it's not used at all. -#: ./doc/arch-design/massively_scalable/section_tech_considerations_massively_scalable.xml:128(None) +#: ./doc/arch-design/massively_scalable/section_tech_considerations_massively_scalable.xml:132(None) msgid "@@image: '../images/Massively_Scalable_Cells_+_regions_+_azs.png'; md5=416477c4bb24cfc5aeb8aa5d4b838f7d" msgstr "" -#: ./doc/arch-design/massively_scalable/section_tech_considerations_massively_scalable.xml:9(para) +#: ./doc/arch-design/massively_scalable/section_tech_considerations_massively_scalable.xml:13(para) msgid "Converting an existing OpenStack environment that was designed for a different purpose to be massively scalable is a formidable task. When building a massively scalable environment from the ground up, make sure the initial deployment is built with the same principles and choices that apply as the environment grows. For example, a good approach is to deploy the first site as a multi-site environment. This allows the same deployment and segregation methods to be used as the environment grows to separate locations across dedicated links or wide area networks. In a hyperscale cloud, scale trumps redundancy. Applications must be modified with this in mind, relying on the scale and homogeneity of the environment to provide reliability rather than redundant infrastructure provided by non-commodity hardware solutions." msgstr "" -#: ./doc/arch-design/massively_scalable/section_tech_considerations_massively_scalable.xml:25(title) +#: ./doc/arch-design/massively_scalable/section_tech_considerations_massively_scalable.xml:29(title) msgid "Infrastructure segregation" msgstr "" -#: ./doc/arch-design/massively_scalable/section_tech_considerations_massively_scalable.xml:26(para) +#: ./doc/arch-design/massively_scalable/section_tech_considerations_massively_scalable.xml:30(para) msgid "Fortunately, OpenStack services are designed to support massive horizontal scale. Be aware that this is not the case for the entire supporting infrastructure. This is particularly a problem for the database management systems and message queues used by the various OpenStack services for data storage and remote procedure call communications." msgstr "" -#: ./doc/arch-design/massively_scalable/section_tech_considerations_massively_scalable.xml:32(para) +#: ./doc/arch-design/massively_scalable/section_tech_considerations_massively_scalable.xml:36(para) msgid "Traditional clustering techniques are typically used to provide high availability and some additional scale for these environments. In the quest for massive scale, however, additional steps need to be taken to relieve the performance pressure on these components to prevent them from negatively impacting the overall performance of the environment. It is important to make sure that all the components are in balance so that, if and when the massively scalable environment fails, all the components are at, or close to, maximum capacity." msgstr "" -#: ./doc/arch-design/massively_scalable/section_tech_considerations_massively_scalable.xml:42(para) +#: ./doc/arch-design/massively_scalable/section_tech_considerations_massively_scalable.xml:46(para) msgid "Regions are used to segregate completely independent installations linked only by an Identity and Dashboard (optional) installation. Services are installed with separate API endpoints for each region, complete with separate database and queue installations. This exposes some awareness of the environment's fault domains to users and gives them the ability to ensure some degree of application resiliency while also imposing the requirement to specify which region their actions must be applied to." msgstr "" -#: ./doc/arch-design/massively_scalable/section_tech_considerations_massively_scalable.xml:51(para) +#: ./doc/arch-design/massively_scalable/section_tech_considerations_massively_scalable.xml:55(para) msgid "Environments operating at massive scale typically need their regions or sites subdivided further without exposing the requirement to specify the failure domain to the user. This provides the ability to further divide the installation into failure domains while also providing a logical unit for maintenance and the addition of new hardware. At hyperscale, instead of adding single compute nodes, administrators may add entire racks or even groups of racks at a time with each new addition of nodes exposed via one of the segregation concepts mentioned herein." msgstr "" -#: ./doc/arch-design/massively_scalable/section_tech_considerations_massively_scalable.xml:61(para) +#: ./doc/arch-design/massively_scalable/section_tech_considerations_massively_scalable.xml:65(para) msgid "Cells provide the ability to subdivide the compute portion of an OpenStack installation, including regions, while still exposing a single endpoint. In each region an API cell is created along with a number of compute cells where the workloads actually run. Each cell gets its own database and message queue setup (ideally clustered), providing the ability to subdivide the load on these subsystems, improving overall performance." msgstr "" -#: ./doc/arch-design/massively_scalable/section_tech_considerations_massively_scalable.xml:69(para) +#: ./doc/arch-design/massively_scalable/section_tech_considerations_massively_scalable.xml:73(para) msgid "Within each compute cell a complete compute installation is provided, complete with full database and queue installations, scheduler, conductor, and multiple compute hosts. The cells scheduler handles placement of user requests from the single API endpoint to a specific cell from those available. The normal filter scheduler then handles placement within the cell." msgstr "" -#: ./doc/arch-design/massively_scalable/section_tech_considerations_massively_scalable.xml:76(para) -msgid "The downside of using cells is that they are not well supported by any of the OpenStack services other than compute. Also, they do not adequately support some relatively standard OpenStack functionality such as security groups and host aggregates. Due to their relative newness and specialized use, they receive relatively little testing in the OpenStack gate. Despite these issues, however, cells are used in some very well known OpenStack installations operating at massive scale including those at CERN and Rackspace." +#: ./doc/arch-design/massively_scalable/section_tech_considerations_massively_scalable.xml:80(para) +msgid "The downside of using cells is that they are not well supported by any of the OpenStack services other than Compute. Also, they do not adequately support some relatively standard OpenStack functionality such as security groups and host aggregates. Due to their relative newness and specialized use, they receive relatively little testing in the OpenStack gate. Despite these issues, however, cells are used in some very well known OpenStack installations operating at massive scale including those at CERN and Rackspace." msgstr "" -#: ./doc/arch-design/massively_scalable/section_tech_considerations_massively_scalable.xml:86(title) +#: ./doc/arch-design/massively_scalable/section_tech_considerations_massively_scalable.xml:90(title) msgid "Host aggregates" msgstr "" -#: ./doc/arch-design/massively_scalable/section_tech_considerations_massively_scalable.xml:87(para) -msgid "Host Aggregates enable partitioning of OpenStack Compute deployments into logical groups for load balancing and instance distribution. Host aggregates may also be used to further partition an availability zone. Consider a cloud which might use host aggregates to partition an availability zone into groups of hosts that either share common resources, such as storage and network, or have a special property, such as trusted computing hardware. Host aggregates are not explicitly user-targetable; instead they are implicitly targeted via the selection of instance flavors with extra specifications that map to host aggregate metadata." +#: ./doc/arch-design/massively_scalable/section_tech_considerations_massively_scalable.xml:91(para) +msgid "Host aggregates enable partitioning of OpenStack Compute deployments into logical groups for load balancing and instance distribution. Host aggregates may also be used to further partition an availability zone. Consider a cloud which might use host aggregates to partition an availability zone into groups of hosts that either share common resources, such as storage and network, or have a special property, such as trusted computing hardware. Host aggregates are not explicitly user-targetable; instead they are implicitly targeted via the selection of instance flavors with extra specifications that map to host aggregate metadata." msgstr "" -#: ./doc/arch-design/massively_scalable/section_tech_considerations_massively_scalable.xml:99(title) +#: ./doc/arch-design/massively_scalable/section_tech_considerations_massively_scalable.xml:103(title) msgid "Availability zones" msgstr "" -#: ./doc/arch-design/massively_scalable/section_tech_considerations_massively_scalable.xml:100(para) -msgid "Availability zones provide another mechanism for subdividing an installation or region. They are, in effect, Host aggregates that are exposed for (optional) explicit targeting by users." -msgstr "" - #: ./doc/arch-design/massively_scalable/section_tech_considerations_massively_scalable.xml:104(para) -msgid "Unlike cells, they do not have their own database server or queue broker but simply represent an arbitrary grouping of compute nodes. Typically, grouping of nodes into availability zones is based on a shared failure domain based on a physical characteristic such as a shared power source, physical network connection, and so on. Availability Zones are exposed to the user because they can be targeted; however, users are not required to target them. An alternate approach is for the operator to set a default availability zone to schedule instances to other than the default availability zone of nova." +msgid "Availability zones provide another mechanism for subdividing an installation or region. They are, in effect, host aggregates that are exposed for (optional) explicit targeting by users." msgstr "" -#: ./doc/arch-design/massively_scalable/section_tech_considerations_massively_scalable.xml:116(title) +#: ./doc/arch-design/massively_scalable/section_tech_considerations_massively_scalable.xml:108(para) +msgid "Unlike cells, they do not have their own database server or queue broker but simply represent an arbitrary grouping of compute nodes. Typically, grouping of nodes into availability zones is based on a shared failure domain based on a physical characteristic such as a shared power source, physical network connection, and so on. Availability zones are exposed to the user because they can be targeted; however, users are not required to target them. An alternate approach is for the operator to set a default availability zone to schedule instances to other than the default availability zone of nova." +msgstr "" + +#: ./doc/arch-design/massively_scalable/section_tech_considerations_massively_scalable.xml:120(title) msgid "Segregation example" msgstr "" -#: ./doc/arch-design/massively_scalable/section_tech_considerations_massively_scalable.xml:117(para) -msgid "In this example the cloud is divided into two regions, one for each site, with two availability zones in each based on the power layout of the data centers. A number of host aggregates have also been defined to allow targeting of virtual machine instances using flavors, that require special capabilities shared by the target hosts such as SSDs, 10 G networks, or GPU cards." +#: ./doc/arch-design/massively_scalable/section_tech_considerations_massively_scalable.xml:121(para) +msgid "In this example the cloud is divided into two regions, one for each site, with two availability zones in each based on the power layout of the data centers. A number of host aggregates have also been defined to allow targeting of virtual machine instances using flavors, that require special capabilities shared by the target hosts such as SSDs, 10GbE networks, or GPU cards." msgstr "" #: ./doc/arch-design/storage_focus/section_tech_considerations_storage_focus.xml:9(para) diff --git a/doc/common/locale/common.pot b/doc/common/locale/common.pot index 7c884d72f0..979e4cb181 100644 --- a/doc/common/locale/common.pot +++ b/doc/common/locale/common.pot @@ -1,7 +1,7 @@ msgid "" msgstr "" "Project-Id-Version: PACKAGE VERSION\n" -"POT-Creation-Date: 2014-07-28 06:07+0000\n" +"POT-Creation-Date: 2014-08-04 06:09+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -6192,35 +6192,27 @@ msgstr "" msgid "regionName" msgstr "" -#: ./doc/common/section_cli_openrc.xml:94(para) -msgid "The following example shows the information for a project called admin, where the OS user name is also admin, and the identity host is located at controller." -msgstr "" - -#: ./doc/common/section_cli_openrc.xml:100(replaceable) -msgid "ADMIN_PASS" -msgstr "" - -#: ./doc/common/section_cli_openrc.xml:105(para) +#: ./doc/common/section_cli_openrc.xml:96(para) msgid "On any shell from which you want to run OpenStack commands, source the PROJECT-openrc.sh file for the respective project. In this example, you source the admin-openrc.sh file for the admin project:" msgstr "" -#: ./doc/common/section_cli_openrc.xml:117(para) +#: ./doc/common/section_cli_openrc.xml:108(para) msgid "You are not prompted for the password with this method. The password lives in clear text format in the PROJECT-openrc.sh file. Restrict the permissions on this file to avoid security problems. You can also remove the OS_PASSWORD variable from the file, and use the --password parameter with OpenStack client commands instead." msgstr "" -#: ./doc/common/section_cli_openrc.xml:129(title) +#: ./doc/common/section_cli_openrc.xml:120(title) msgid "Override environment variable values" msgstr "" -#: ./doc/common/section_cli_openrc.xml:130(para) +#: ./doc/common/section_cli_openrc.xml:121(para) msgid "When you run OpenStack client commands, you can override some environment variable settings by using the options that are listed at the end of the output of the various client commands. For example, you can override the setting in the PROJECT-openrc.sh file by specifying a password on a command, as follows:" msgstr "" -#: ./doc/common/section_cli_openrc.xml:138(replaceable) +#: ./doc/common/section_cli_openrc.xml:129(replaceable) msgid "PASSWORD" msgstr "" -#: ./doc/common/section_cli_openrc.xml:139(para) +#: ./doc/common/section_cli_openrc.xml:130(para) msgid "Where PASSWORD is your password." msgstr "" diff --git a/doc/common/locale/fr.po b/doc/common/locale/fr.po index 63a653f834..5658fbbc72 100644 --- a/doc/common/locale/fr.po +++ b/doc/common/locale/fr.po @@ -18,8 +18,8 @@ msgid "" msgstr "" "Project-Id-Version: OpenStack Manuals\n" -"POT-Creation-Date: 2014-08-01 17:08+0000\n" -"PO-Revision-Date: 2014-08-01 18:51+0000\n" +"POT-Creation-Date: 2014-08-03 23:07+0000\n" +"PO-Revision-Date: 2014-08-03 22:58+0000\n" "Last-Translator: openstackjenkins \n" "Language-Team: French (http://www.transifex.com/projects/p/openstack-manuals-i18n/language/fr/)\n" "MIME-Version: 1.0\n" @@ -9095,19 +9095,7 @@ msgstr "" msgid "regionName" msgstr "" -#: ./doc/common/section_cli_openrc.xml94(para) -msgid "" -"The following example shows the information for a project called " -"admin, where the OS user name is also admin, and the identity host is located at " -"controller." -msgstr "" - -#: ./doc/common/section_cli_openrc.xml100(replaceable) -msgid "ADMIN_PASS" -msgstr "ADMIN_PASS" - -#: ./doc/common/section_cli_openrc.xml105(para) +#: ./doc/common/section_cli_openrc.xml96(para) msgid "" "On any shell from which you want to run OpenStack commands, source the " "PROJECT-openrc.sh file for " @@ -9115,7 +9103,7 @@ msgid "" "openrc.sh file for the admin project:" msgstr "" -#: ./doc/common/section_cli_openrc.xml117(para) +#: ./doc/common/section_cli_openrc.xml108(para) msgid "" "You are not prompted for the password with this method. The password lives " "in clear text format in the " @@ -9126,11 +9114,11 @@ msgid "" "commands instead." msgstr "" -#: ./doc/common/section_cli_openrc.xml129(title) +#: ./doc/common/section_cli_openrc.xml120(title) msgid "Override environment variable values" msgstr "" -#: ./doc/common/section_cli_openrc.xml130(para) +#: ./doc/common/section_cli_openrc.xml121(para) msgid "" "When you run OpenStack client commands, you can override some environment " "variable settings by using the options that are listed at the end of the " @@ -9140,11 +9128,11 @@ msgid "" "specifying a password on a command, as follows:" msgstr "" -#: ./doc/common/section_cli_openrc.xml138(replaceable) +#: ./doc/common/section_cli_openrc.xml129(replaceable) msgid "PASSWORD" msgstr "MOT DE PASSE" -#: ./doc/common/section_cli_openrc.xml139(para) +#: ./doc/common/section_cli_openrc.xml130(para) msgid "Where PASSWORD is your password." msgstr "" diff --git a/doc/common/locale/ja.po b/doc/common/locale/ja.po index 0a915dabf4..ced5ca0e1b 100644 --- a/doc/common/locale/ja.po +++ b/doc/common/locale/ja.po @@ -7,8 +7,8 @@ msgid "" msgstr "" "Project-Id-Version: OpenStack Manuals\n" -"POT-Creation-Date: 2014-07-28 05:37+0000\n" -"PO-Revision-Date: 2014-07-27 19:16+0000\n" +"POT-Creation-Date: 2014-08-03 23:07+0000\n" +"PO-Revision-Date: 2014-08-03 22:58+0000\n" "Last-Translator: openstackjenkins \n" "Language-Team: Japanese (http://www.transifex.com/projects/p/openstack-manuals-i18n/language/ja/)\n" "MIME-Version: 1.0\n" @@ -9084,19 +9084,7 @@ msgstr "tenantIDString" msgid "regionName" msgstr "regionName" -#: ./doc/common/section_cli_openrc.xml94(para) -msgid "" -"The following example shows the information for a project called " -"admin, where the OS user name is also admin, and the identity host is located at " -"controller." -msgstr "" - -#: ./doc/common/section_cli_openrc.xml100(replaceable) -msgid "ADMIN_PASS" -msgstr "ADMIN_PASS" - -#: ./doc/common/section_cli_openrc.xml105(para) +#: ./doc/common/section_cli_openrc.xml96(para) msgid "" "On any shell from which you want to run OpenStack commands, source the " "PROJECT-openrc.sh file for " @@ -9104,7 +9092,7 @@ msgid "" "openrc.sh file for the admin project:" msgstr "OpenStack コマンドを実行したいシェルで、それぞれのプロジェクト用の PROJECT-openrc.sh ファイルを読み込みます。この例では、admin プロジェクト用の admin-openrc.sh ファイルを読み込みます。" -#: ./doc/common/section_cli_openrc.xml117(para) +#: ./doc/common/section_cli_openrc.xml108(para) msgid "" "You are not prompted for the password with this method. The password lives " "in clear text format in the " @@ -9115,11 +9103,11 @@ msgid "" "commands instead." msgstr "この方法を用いると、パスワードを聞かれません。パスワードは PROJECT-openrc.sh ファイルに平文で記載されています。セキュリティ問題を避けるために、このファイルのパーミッションを制限します。このファイルから OS_PASSWORD 変数を削除し、OpenStack クライアントコマンドで --password パラメーターを使用することもできます。" -#: ./doc/common/section_cli_openrc.xml129(title) +#: ./doc/common/section_cli_openrc.xml120(title) msgid "Override environment variable values" msgstr "環境変数値の上書き" -#: ./doc/common/section_cli_openrc.xml130(para) +#: ./doc/common/section_cli_openrc.xml121(para) msgid "" "When you run OpenStack client commands, you can override some environment " "variable settings by using the options that are listed at the end of the " @@ -9129,11 +9117,11 @@ msgid "" "specifying a password on a command, as follows:" msgstr "OpenStack クライアントコマンドを実行するとき、さまざまなクライアントコマンドの 出力の最後に一覧表示されるオプションを使用することにより、いくつかの環境変数を上書きできます。たとえば以下のように、 コマンドにパスワードを指定することにより、PROJECT-openrc.sh ファイルで設定した 設定を上書きできます。" -#: ./doc/common/section_cli_openrc.xml138(replaceable) +#: ./doc/common/section_cli_openrc.xml129(replaceable) msgid "PASSWORD" msgstr "PASSWORD" -#: ./doc/common/section_cli_openrc.xml139(para) +#: ./doc/common/section_cli_openrc.xml130(para) msgid "Where PASSWORD is your password." msgstr "PASSWORD は、お使いのパスワードです。" diff --git a/doc/image-guide/locale/ja.po b/doc/image-guide/locale/ja.po index 2b6ddec5d1..aa178d702b 100644 --- a/doc/image-guide/locale/ja.po +++ b/doc/image-guide/locale/ja.po @@ -5,8 +5,8 @@ msgid "" msgstr "" "Project-Id-Version: OpenStack Manuals\n" -"POT-Creation-Date: 2014-08-02 20:14+0000\n" -"PO-Revision-Date: 2014-08-03 01:00+0000\n" +"POT-Creation-Date: 2014-08-03 23:07+0000\n" +"PO-Revision-Date: 2014-08-04 05:40+0000\n" "Last-Translator: Tomoyuki KATO \n" "Language-Team: Japanese (http://www.transifex.com/projects/p/openstack-manuals-i18n/language/ja/)\n" "MIME-Version: 1.0\n" @@ -273,7 +273,7 @@ msgid "" "can now view the file systems in the image using the " "command:We need to mount the logical volume that contains " "the root partition: " -msgstr "" +msgstr "何かしらの処理を実行する前に、まず guestfish プロンプトで コマンドを実行する必要があります。これにより、すべてのファイル操作を実行するために使用する、仮想マシンが起動します。これで、 コマンドを使用して、イメージにあるファイルシステムを表示できます。ルートパーティションを含む、論理ボリュームをマウントする必要があります。" #: ./doc/image-guide/ch_modifying_images.xml83(para) msgid "" @@ -430,7 +430,7 @@ msgid "" " to resize. We create a new qcow2 image and use the command" " to write a resized copy of the original into the new image: " "" -msgstr "" +msgstr "この場合、容量を変更したいパーティションは /dev/sda2 です。新しい qcow2 イメージを作成し、容量を変更して元の内容を新しいイメージをコピーするために コマンドを使用します。" #: ./doc/image-guide/ch_modifying_images.xml262(title) msgid "Loop devices, kpartx, network block devices" @@ -483,7 +483,7 @@ msgid "" "partitions as separate devices (for example, " "/dev/mapper/loop0p1), then mount the partition that " "corresponds to the root file system:" -msgstr "" +msgstr "イメージが複数のパーティションを持つ場合、パーティションを別々のデバイス (/dev/mapper/loop0p1) として認識させるために を使用します。そして、ルートファイルシステムに対応するパーティションをマウントします。" #: ./doc/image-guide/ch_modifying_images.xml295(para) msgid "" @@ -491,7 +491,7 @@ msgid "" " new device created per partition:To mount the second " "partition, as root:Once you're done, to clean " "up:" -msgstr "" +msgstr "イメージがいわゆる 3 パーティション (/boot、/、swap) を持つ場合、パーティションごとに 1 つの新しいデバイスにすべきです。 2 番目のパーティションをマウントするために、root として次のとおり実行します。完了すると、クリーンアップします。" #: ./doc/image-guide/ch_modifying_images.xml310(title) msgid "Mount a raw image (with LVM)" @@ -501,13 +501,13 @@ msgstr "raw イメージのマウント (LVM あり)" msgid "" "If your partitions are managed with LVM, use losetup and kpartx as in the " "previous example to expose the partitions to the host:" -msgstr "" +msgstr "LVM を用いてパーティションを管理している場合、パーティションをホストに公開するために、前の例にあるとおり losetup と kpartx を使用します。" #: ./doc/image-guide/ch_modifying_images.xml318(para) msgid "" "Next, you need to use the command to identify the LVM " "volume groups and then to expose the volumes as devices:" -msgstr "" +msgstr "次に、LVM ボリュームグループを識別するために、 コマンドを使用する必要があります。また、ボリュームをデバイスとして公開するために を実行します。" #: ./doc/image-guide/ch_modifying_images.xml328(para) msgid "Clean up when you're done:" @@ -2085,7 +2085,7 @@ msgid "" "href=\"http://www.cloudbase.it/ws2012r2/\">OpenStack Windows Server 2012 " "Standard Evaluation image that runs on Hyper-V, KVM, and " "XenServer/XCP." -msgstr "" +msgstr "Cloudbase Solutions は、Hyper-V、KVM、XenServer/XCP で動作する OpenStack Windows Server 2012 Standard 評価イメージ を配布しています。" #. When image changes, this message will be marked fuzzy or untranslated for #. you. @@ -2143,7 +2143,7 @@ msgid "" "/installer-" "amd64/current/images/netboot/mini.iso\">http://archive.ubuntu.com/ubuntu/dists/trusty/main" "/installer-amd64/current/images/netboot/mini.iso." -msgstr "" +msgstr "目標は利用可能な最小のベースイメージを作成することなので、この例はネットワークインストール ISO を使用します。Ubuntu 64 ビット 14.04 ネットワークインストーラー ISO は http://archive.ubuntu.com/ubuntu/dists/trusty/main/installer-amd64/current/images/netboot/mini.iso にあります。" #: ./doc/image-guide/section_ubuntu-example.xml15(title) msgid "Start the install process" @@ -3062,7 +3062,7 @@ msgstr "" #: ./doc/image-guide/ch_creating_images_manually.xml54(title) msgid "Use the virt-manager X11 GUI" -msgstr "" +msgstr "仮想マシンマネージャー X11 GUI の使用" #: ./doc/image-guide/ch_creating_images_manually.xml55(para) msgid "" @@ -3072,7 +3072,7 @@ msgid "" "Fedora-based and Debian-based systems. This GUI has an embedded VNC client " "in it that will let you view and interact with the guest's graphical " "console." -msgstr "" +msgstr "X11 アプリケーションを実行できるマシンに仮想マシンイメージを作成する予定ならば、最も簡単にそうする方法は、 GUI を使用することです。これは、Fedora 系と Debian 系のシステムにおいて、virt-manager パッケージとしてインストールできます。この GUI は、ゲストのグラフィカルコンソールを表示および操作できる、組み込みの VNC クライアントを持ちます。" #: ./doc/image-guide/ch_creating_images_manually.xml63(para) msgid "" @@ -3082,38 +3082,38 @@ msgid "" "libvirt, you typically need to be root to access it. If you can ssh directly" " in as root (or with a user that has permissions to interact with libvirt), " "do:" -msgstr "" +msgstr "コンソールの無いサーバーにイメージを構築していて、ローカルマシンに X サーバーが有る場合、GUI にアクセスするために、SSH の X11 転送を使用して を起動できます。仮想マシンマネージャーは、libvirt と直接通信するため、アクセスするためには、一般的に root になる必要があります。root (または、libvirt と通信する権限を持つユーザー) として直接 SSH できる場合、次のとおり実行します。" #: ./doc/image-guide/ch_creating_images_manually.xml74(para) msgid "" "The -X flag passed to ssh will enable X11 forwarding over" " ssh. If this does not work, try replacing it with the -Y" " flag." -msgstr "" +msgstr "SSH に渡す -X フラグが、SSH 経由の X11 転送を有効化します。これが動作しない場合、-Y フラグに変更してみてください。" #: ./doc/image-guide/ch_creating_images_manually.xml71(para) msgid "" "If the account you use to ssh into your server does not have permissions to " "run libvirt, but has sudo privileges, do:" -msgstr "" +msgstr "サーバーに SSH するために使用するアカウントが、libvirt を実行する権限を持たず、sudo 権限を持つ場合、次のとおり実行します。" #: ./doc/image-guide/ch_creating_images_manually.xml79(para) msgid "" "Click the \"New\" button at the top-left and step through the instructions. " "You will be shown a series of dialog boxes that will allow " "you to specify information about the virtual machine." -msgstr "" +msgstr "画面左上にある「New」ボタンをクリックし、指示にしたがって進めます。仮想マシンに関する情報を指定できる、一連のダイアログボックスが表示されます。" #: ./doc/image-guide/ch_creating_images_manually.xml88(para) msgid "" "When using qcow2 format images you should check the option 'customize before" " install', go to disk properties and explicitly select the qcow2 format. " "This ensures the virtual machine disk size will be correct." -msgstr "" +msgstr "qcow2 形式のイメージを使用している場合、「customize before install」オプションをチェックし、ディスクのプロパティから明示的に qcow2 形式を選択すべきです。これにより、仮想マシンのディスク容量が正しくなります。" #: ./doc/image-guide/ch_creating_images_manually.xml96(title) msgid "Use virt-install and connect by using a local VNC client" -msgstr "" +msgstr "virt-install の使用とローカル VNC クライアントを用いた接続" #: ./doc/image-guide/ch_creating_images_manually.xml98(para) msgid "" diff --git a/doc/install-guide/locale/install-guide.pot b/doc/install-guide/locale/install-guide.pot index 8fa4c8bc13..99983cca11 100644 --- a/doc/install-guide/locale/install-guide.pot +++ b/doc/install-guide/locale/install-guide.pot @@ -1,7 +1,7 @@ msgid "" msgstr "" "Project-Id-Version: PACKAGE VERSION\n" -"POT-Creation-Date: 2014-07-28 06:07+0000\n" +"POT-Creation-Date: 2014-08-04 06:09+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -111,7 +111,7 @@ msgstr "" msgid "In the [database] section, configure database access:" msgstr "" -#: ./doc/install-guide/section_keystone-install.xml:69(replaceable) ./doc/install-guide/section_cinder-controller.xml:51(replaceable) ./doc/install-guide/section_cinder-controller.xml:54(replaceable) ./doc/install-guide/section_cinder-controller.xml:90(replaceable) ./doc/install-guide/section_cinder-controller.xml:92(replaceable) ./doc/install-guide/section_cinder-controller.xml:108(replaceable) ./doc/install-guide/section_cinder-controller.xml:109(replaceable) ./doc/install-guide/section_cinder-controller.xml:127(replaceable) ./doc/install-guide/section_cinder-controller.xml:152(replaceable) ./doc/install-guide/section_cinder-controller.xml:153(replaceable) ./doc/install-guide/section_cinder-controller.xml:154(replaceable) ./doc/install-guide/section_cinder-controller.xml:162(replaceable) ./doc/install-guide/section_cinder-controller.xml:163(replaceable) ./doc/install-guide/section_cinder-controller.xml:164(replaceable) ./doc/install-guide/section_keystone-users.xml:39(replaceable) ./doc/install-guide/section_ceilometer-nova.xml:80(replaceable) ./doc/install-guide/section_ceilometer-nova.xml:87(replaceable) ./doc/install-guide/section_ceilometer-nova.xml:103(replaceable) ./doc/install-guide/section_ceilometer-nova.xml:118(replaceable) ./doc/install-guide/section_basics-networking-neutron.xml:279(replaceable) ./doc/install-guide/section_basics-networking-neutron.xml:323(replaceable) ./doc/install-guide/section_neutron-ovs-compute-node.xml:136(replaceable) ./doc/install-guide/section_neutron-ovs-compute-node.xml:138(replaceable) ./doc/install-guide/section_neutron-ovs-compute-node.xml:172(replaceable) ./doc/install-guide/section_neutron-ovs-compute-node.xml:173(replaceable) ./doc/install-guide/section_neutron-ovs-compute-node.xml:187(replaceable) ./doc/install-guide/section_neutron-ovs-compute-node.xml:198(replaceable) ./doc/install-guide/section_neutron-ovs-compute-node.xml:212(replaceable) ./doc/install-guide/section_neutron-ovs-compute-node.xml:222(replaceable) ./doc/install-guide/section_neutron-ovs-compute-node.xml:233(replaceable) ./doc/install-guide/section_neutron-ovs-compute-node.xml:238(replaceable) ./doc/install-guide/section_ceilometer-install.xml:103(replaceable) ./doc/install-guide/section_ceilometer-install.xml:112(replaceable) ./doc/install-guide/section_ceilometer-install.xml:119(replaceable) ./doc/install-guide/section_ceilometer-install.xml:146(replaceable) ./doc/install-guide/section_ceilometer-install.xml:149(replaceable) ./doc/install-guide/section_ceilometer-install.xml:191(replaceable) ./doc/install-guide/section_ceilometer-install.xml:199(replaceable) ./doc/install-guide/section_ceilometer-install.xml:203(replaceable) ./doc/install-guide/section_ceilometer-install.xml:218(replaceable) ./doc/install-guide/section_ceilometer-install.xml:225(replaceable) ./doc/install-guide/section_ceilometer-install.xml:239(replaceable) ./doc/install-guide/section_ceilometer-install.xml:240(replaceable) ./doc/install-guide/section_ceilometer-install.xml:241(replaceable) ./doc/install-guide/section_basics-ntp.xml:74(replaceable) ./doc/install-guide/ch_clients.xml:43(replaceable) ./doc/install-guide/section_nova-controller-install.xml:72(replaceable) ./doc/install-guide/section_nova-controller-install.xml:73(replaceable) ./doc/install-guide/section_nova-controller-install.xml:74(replaceable) ./doc/install-guide/section_nova-controller-install.xml:109(replaceable) ./doc/install-guide/section_nova-controller-install.xml:121(replaceable) ./doc/install-guide/section_nova-controller-install.xml:122(replaceable) ./doc/install-guide/section_nova-controller-install.xml:154(replaceable) ./doc/install-guide/section_glance-install.xml:79(replaceable) ./doc/install-guide/section_glance-install.xml:80(replaceable) ./doc/install-guide/section_glance-install.xml:81(replaceable) ./doc/install-guide/section_glance-install.xml:101(replaceable) ./doc/install-guide/section_glance-install.xml:111(replaceable) ./doc/install-guide/section_glance-install.xml:123(replaceable) ./doc/install-guide/section_glance-install.xml:124(replaceable) ./doc/install-guide/section_glance-install.xml:149(replaceable) ./doc/install-guide/section_glance-install.xml:159(replaceable) ./doc/install-guide/section_glance-install.xml:160(replaceable) ./doc/install-guide/section_cinder-node.xml:120(replaceable) ./doc/install-guide/section_cinder-node.xml:122(replaceable) ./doc/install-guide/section_cinder-node.xml:138(replaceable) ./doc/install-guide/section_cinder-node.xml:139(replaceable) ./doc/install-guide/section_cinder-node.xml:163(replaceable) ./doc/install-guide/section_cinder-node.xml:175(replaceable) ./doc/install-guide/section_cinder-node.xml:188(replaceable) ./doc/install-guide/section_cinder-node.xml:191(replaceable) ./doc/install-guide/section_cinder-node.xml:207(replaceable) ./doc/install-guide/section_cinder-node.xml:210(replaceable) ./doc/install-guide/section_neutron-ml2-compute-node.xml:60(replaceable) ./doc/install-guide/section_neutron-ml2-compute-node.xml:62(replaceable) ./doc/install-guide/section_neutron-ml2-compute-node.xml:93(replaceable) ./doc/install-guide/section_neutron-ml2-compute-node.xml:94(replaceable) ./doc/install-guide/section_neutron-ml2-compute-node.xml:111(replaceable) ./doc/install-guide/section_neutron-ml2-compute-node.xml:134(replaceable) ./doc/install-guide/section_neutron-ml2-compute-node.xml:280(replaceable) ./doc/install-guide/section_neutron-ml2-compute-node.xml:290(replaceable) ./doc/install-guide/section_neutron-ml2-compute-node.xml:318(replaceable) ./doc/install-guide/section_neutron-ml2-compute-node.xml:323(replaceable) ./doc/install-guide/section_keystone-openrc.xml:27(replaceable) ./doc/install-guide/section_keystone-openrc.xml:37(replaceable) ./doc/install-guide/section_basics-networking-nova.xml:204(replaceable) ./doc/install-guide/section_trove-install.xml:77(replaceable) ./doc/install-guide/section_trove-install.xml:78(replaceable) ./doc/install-guide/section_trove-install.xml:79(replaceable) ./doc/install-guide/section_trove-install.xml:80(replaceable) ./doc/install-guide/section_trove-install.xml:81(replaceable) ./doc/install-guide/section_trove-install.xml:82(replaceable) ./doc/install-guide/section_trove-install.xml:105(replaceable) ./doc/install-guide/section_trove-install.xml:107(replaceable) ./doc/install-guide/section_trove-install.xml:109(replaceable) ./doc/install-guide/section_trove-install.xml:125(replaceable) ./doc/install-guide/section_trove-install.xml:206(replaceable) ./doc/install-guide/section_trove-install.xml:211(replaceable) ./doc/install-guide/section_trove-install.xml:232(replaceable) ./doc/install-guide/section_trove-install.xml:233(replaceable) ./doc/install-guide/section_trove-install.xml:234(replaceable) ./doc/install-guide/section_neutron-ml2-controller-node.xml:50(replaceable) ./doc/install-guide/section_neutron-ml2-controller-node.xml:51(replaceable) ./doc/install-guide/section_neutron-ml2-controller-node.xml:52(replaceable) ./doc/install-guide/section_neutron-ml2-controller-node.xml:114(replaceable) ./doc/install-guide/section_neutron-ml2-controller-node.xml:127(replaceable) ./doc/install-guide/section_neutron-ml2-controller-node.xml:140(replaceable) ./doc/install-guide/section_neutron-ml2-controller-node.xml:142(replaceable) ./doc/install-guide/section_neutron-ml2-controller-node.xml:172(replaceable) ./doc/install-guide/section_neutron-ml2-controller-node.xml:173(replaceable) ./doc/install-guide/section_neutron-ml2-controller-node.xml:209(replaceable) ./doc/install-guide/section_neutron-ml2-controller-node.xml:222(replaceable) ./doc/install-guide/section_neutron-ml2-controller-node.xml:230(replaceable) ./doc/install-guide/section_neutron-ml2-controller-node.xml:249(replaceable) ./doc/install-guide/section_neutron-ml2-controller-node.xml:253(replaceable) ./doc/install-guide/section_neutron-ml2-controller-node.xml:366(replaceable) ./doc/install-guide/section_neutron-ml2-controller-node.xml:376(replaceable) ./doc/install-guide/section_neutron-ml2-controller-node.xml:400(replaceable) ./doc/install-guide/section_neutron-ml2-controller-node.xml:405(replaceable) ./doc/install-guide/section_nova-compute-install.xml:38(replaceable) ./doc/install-guide/section_nova-compute-install.xml:48(replaceable) ./doc/install-guide/section_nova-compute-install.xml:60(replaceable) ./doc/install-guide/section_nova-compute-install.xml:61(replaceable) ./doc/install-guide/section_nova-compute-install.xml:92(replaceable) ./doc/install-guide/section_nova-compute-install.xml:117(replaceable) ./doc/install-guide/section_neutron-ovs-controller-node.xml:56(replaceable) ./doc/install-guide/section_neutron-ovs-controller-node.xml:57(replaceable) ./doc/install-guide/section_neutron-ovs-controller-node.xml:58(replaceable) ./doc/install-guide/section_neutron-ovs-controller-node.xml:82(replaceable) ./doc/install-guide/section_neutron-ovs-controller-node.xml:99(replaceable) ./doc/install-guide/section_neutron-ovs-controller-node.xml:101(replaceable) ./doc/install-guide/section_neutron-ovs-controller-node.xml:134(replaceable) ./doc/install-guide/section_neutron-ovs-controller-node.xml:135(replaceable) ./doc/install-guide/section_neutron-ovs-controller-node.xml:166(replaceable) ./doc/install-guide/section_neutron-ovs-controller-node.xml:216(replaceable) ./doc/install-guide/section_neutron-ovs-controller-node.xml:226(replaceable) ./doc/install-guide/section_neutron-ovs-controller-node.xml:237(replaceable) ./doc/install-guide/section_neutron-ovs-controller-node.xml:242(replaceable) ./doc/install-guide/section_heat-install.xml:63(replaceable) ./doc/install-guide/section_heat-install.xml:64(replaceable) ./doc/install-guide/section_heat-install.xml:65(replaceable) ./doc/install-guide/section_heat-install.xml:68(replaceable) ./doc/install-guide/section_heat-install.xml:69(replaceable) ./doc/install-guide/section_heat-install.xml:70(replaceable) ./doc/install-guide/section_heat-install.xml:89(replaceable) ./doc/install-guide/section_heat-install.xml:99(replaceable) ./doc/install-guide/section_heat-install.xml:111(replaceable) ./doc/install-guide/section_heat-install.xml:112(replaceable) ./doc/install-guide/section_heat-install.xml:121(replaceable) ./doc/install-guide/section_heat-install.xml:131(replaceable) ./doc/install-guide/section_heat-install.xml:132(replaceable) ./doc/install-guide/section_heat-install.xml:177(replaceable) ./doc/install-guide/section_neutron-ml2-network-node.xml:66(replaceable) ./doc/install-guide/section_neutron-ml2-network-node.xml:68(replaceable) ./doc/install-guide/section_neutron-ml2-network-node.xml:99(replaceable) ./doc/install-guide/section_neutron-ml2-network-node.xml:100(replaceable) ./doc/install-guide/section_neutron-ml2-network-node.xml:117(replaceable) ./doc/install-guide/section_neutron-ml2-network-node.xml:137(replaceable) ./doc/install-guide/section_neutron-ml2-network-node.xml:264(replaceable) ./doc/install-guide/section_neutron-ml2-network-node.xml:274(replaceable) ./doc/install-guide/section_neutron-ml2-network-node.xml:296(replaceable) ./doc/install-guide/section_neutron-ml2-network-node.xml:301(replaceable) ./doc/install-guide/section_ceilometer-glance.xml:18(replaceable) ./doc/install-guide/section_ceilometer-glance.xml:24(replaceable) ./doc/install-guide/section_keystone-services.xml:56(replaceable) ./doc/install-guide/section_keystone-services.xml:57(replaceable) ./doc/install-guide/section_keystone-services.xml:58(replaceable) ./doc/install-guide/section_neutron-ovs-network-node.xml:98(replaceable) ./doc/install-guide/section_neutron-ovs-network-node.xml:100(replaceable) ./doc/install-guide/section_neutron-ovs-network-node.xml:131(replaceable) ./doc/install-guide/section_neutron-ovs-network-node.xml:132(replaceable) ./doc/install-guide/section_neutron-ovs-network-node.xml:146(replaceable) ./doc/install-guide/section_neutron-ovs-network-node.xml:157(replaceable) ./doc/install-guide/section_neutron-ovs-network-node.xml:374(replaceable) ./doc/install-guide/section_neutron-ovs-network-node.xml:379(replaceable) ./doc/install-guide/section_neutron-ovs-network-node.xml:384(replaceable) ./doc/install-guide/section_neutron-ovs-network-node.xml:394(replaceable) ./doc/install-guide/object-storage/section_object-storage-install-config-proxy-node.xml:80(replaceable) ./doc/install-guide/object-storage/section_object-storage-install.xml:102(replaceable) ./doc/install-guide/object-storage/section_object-storage-install.xml:103(replaceable) ./doc/install-guide/object-storage/section_object-storage-install.xml:104(replaceable) +#: ./doc/install-guide/section_keystone-install.xml:69(replaceable) ./doc/install-guide/section_cinder-controller.xml:51(replaceable) ./doc/install-guide/section_cinder-controller.xml:54(replaceable) ./doc/install-guide/section_cinder-controller.xml:90(replaceable) ./doc/install-guide/section_cinder-controller.xml:92(replaceable) ./doc/install-guide/section_cinder-controller.xml:108(replaceable) ./doc/install-guide/section_cinder-controller.xml:109(replaceable) ./doc/install-guide/section_cinder-controller.xml:127(replaceable) ./doc/install-guide/section_cinder-controller.xml:152(replaceable) ./doc/install-guide/section_cinder-controller.xml:153(replaceable) ./doc/install-guide/section_cinder-controller.xml:154(replaceable) ./doc/install-guide/section_cinder-controller.xml:162(replaceable) ./doc/install-guide/section_cinder-controller.xml:163(replaceable) ./doc/install-guide/section_cinder-controller.xml:164(replaceable) ./doc/install-guide/section_keystone-users.xml:39(replaceable) ./doc/install-guide/section_ceilometer-nova.xml:80(replaceable) ./doc/install-guide/section_ceilometer-nova.xml:87(replaceable) ./doc/install-guide/section_ceilometer-nova.xml:103(replaceable) ./doc/install-guide/section_ceilometer-nova.xml:118(replaceable) ./doc/install-guide/section_basics-networking-neutron.xml:279(replaceable) ./doc/install-guide/section_basics-networking-neutron.xml:323(replaceable) ./doc/install-guide/section_neutron-ovs-compute-node.xml:136(replaceable) ./doc/install-guide/section_neutron-ovs-compute-node.xml:138(replaceable) ./doc/install-guide/section_neutron-ovs-compute-node.xml:172(replaceable) ./doc/install-guide/section_neutron-ovs-compute-node.xml:173(replaceable) ./doc/install-guide/section_neutron-ovs-compute-node.xml:187(replaceable) ./doc/install-guide/section_neutron-ovs-compute-node.xml:198(replaceable) ./doc/install-guide/section_neutron-ovs-compute-node.xml:212(replaceable) ./doc/install-guide/section_neutron-ovs-compute-node.xml:222(replaceable) ./doc/install-guide/section_neutron-ovs-compute-node.xml:233(replaceable) ./doc/install-guide/section_neutron-ovs-compute-node.xml:238(replaceable) ./doc/install-guide/section_ceilometer-install.xml:103(replaceable) ./doc/install-guide/section_ceilometer-install.xml:112(replaceable) ./doc/install-guide/section_ceilometer-install.xml:119(replaceable) ./doc/install-guide/section_ceilometer-install.xml:146(replaceable) ./doc/install-guide/section_ceilometer-install.xml:149(replaceable) ./doc/install-guide/section_ceilometer-install.xml:191(replaceable) ./doc/install-guide/section_ceilometer-install.xml:199(replaceable) ./doc/install-guide/section_ceilometer-install.xml:203(replaceable) ./doc/install-guide/section_ceilometer-install.xml:218(replaceable) ./doc/install-guide/section_ceilometer-install.xml:225(replaceable) ./doc/install-guide/section_ceilometer-install.xml:239(replaceable) ./doc/install-guide/section_ceilometer-install.xml:240(replaceable) ./doc/install-guide/section_ceilometer-install.xml:241(replaceable) ./doc/install-guide/section_basics-ntp.xml:74(replaceable) ./doc/install-guide/section_nova-controller-install.xml:72(replaceable) ./doc/install-guide/section_nova-controller-install.xml:73(replaceable) ./doc/install-guide/section_nova-controller-install.xml:74(replaceable) ./doc/install-guide/section_nova-controller-install.xml:109(replaceable) ./doc/install-guide/section_nova-controller-install.xml:121(replaceable) ./doc/install-guide/section_nova-controller-install.xml:122(replaceable) ./doc/install-guide/section_nova-controller-install.xml:154(replaceable) ./doc/install-guide/section_glance-install.xml:79(replaceable) ./doc/install-guide/section_glance-install.xml:80(replaceable) ./doc/install-guide/section_glance-install.xml:81(replaceable) ./doc/install-guide/section_glance-install.xml:101(replaceable) ./doc/install-guide/section_glance-install.xml:111(replaceable) ./doc/install-guide/section_glance-install.xml:123(replaceable) ./doc/install-guide/section_glance-install.xml:124(replaceable) ./doc/install-guide/section_glance-install.xml:149(replaceable) ./doc/install-guide/section_glance-install.xml:159(replaceable) ./doc/install-guide/section_glance-install.xml:160(replaceable) ./doc/install-guide/section_cinder-node.xml:120(replaceable) ./doc/install-guide/section_cinder-node.xml:122(replaceable) ./doc/install-guide/section_cinder-node.xml:138(replaceable) ./doc/install-guide/section_cinder-node.xml:139(replaceable) ./doc/install-guide/section_cinder-node.xml:163(replaceable) ./doc/install-guide/section_cinder-node.xml:175(replaceable) ./doc/install-guide/section_cinder-node.xml:188(replaceable) ./doc/install-guide/section_cinder-node.xml:191(replaceable) ./doc/install-guide/section_cinder-node.xml:207(replaceable) ./doc/install-guide/section_cinder-node.xml:210(replaceable) ./doc/install-guide/section_neutron-ml2-compute-node.xml:60(replaceable) ./doc/install-guide/section_neutron-ml2-compute-node.xml:62(replaceable) ./doc/install-guide/section_neutron-ml2-compute-node.xml:93(replaceable) ./doc/install-guide/section_neutron-ml2-compute-node.xml:94(replaceable) ./doc/install-guide/section_neutron-ml2-compute-node.xml:111(replaceable) ./doc/install-guide/section_neutron-ml2-compute-node.xml:134(replaceable) ./doc/install-guide/section_neutron-ml2-compute-node.xml:280(replaceable) ./doc/install-guide/section_neutron-ml2-compute-node.xml:290(replaceable) ./doc/install-guide/section_neutron-ml2-compute-node.xml:318(replaceable) ./doc/install-guide/section_neutron-ml2-compute-node.xml:323(replaceable) ./doc/install-guide/section_keystone-openrc.xml:27(replaceable) ./doc/install-guide/section_keystone-openrc.xml:37(replaceable) ./doc/install-guide/section_basics-networking-nova.xml:204(replaceable) ./doc/install-guide/section_trove-install.xml:77(replaceable) ./doc/install-guide/section_trove-install.xml:78(replaceable) ./doc/install-guide/section_trove-install.xml:79(replaceable) ./doc/install-guide/section_trove-install.xml:80(replaceable) ./doc/install-guide/section_trove-install.xml:81(replaceable) ./doc/install-guide/section_trove-install.xml:82(replaceable) ./doc/install-guide/section_trove-install.xml:105(replaceable) ./doc/install-guide/section_trove-install.xml:107(replaceable) ./doc/install-guide/section_trove-install.xml:109(replaceable) ./doc/install-guide/section_trove-install.xml:125(replaceable) ./doc/install-guide/section_trove-install.xml:206(replaceable) ./doc/install-guide/section_trove-install.xml:211(replaceable) ./doc/install-guide/section_trove-install.xml:232(replaceable) ./doc/install-guide/section_trove-install.xml:233(replaceable) ./doc/install-guide/section_trove-install.xml:234(replaceable) ./doc/install-guide/section_neutron-ml2-controller-node.xml:53(replaceable) ./doc/install-guide/section_neutron-ml2-controller-node.xml:54(replaceable) ./doc/install-guide/section_neutron-ml2-controller-node.xml:55(replaceable) ./doc/install-guide/section_neutron-ml2-controller-node.xml:117(replaceable) ./doc/install-guide/section_neutron-ml2-controller-node.xml:130(replaceable) ./doc/install-guide/section_neutron-ml2-controller-node.xml:143(replaceable) ./doc/install-guide/section_neutron-ml2-controller-node.xml:145(replaceable) ./doc/install-guide/section_neutron-ml2-controller-node.xml:175(replaceable) ./doc/install-guide/section_neutron-ml2-controller-node.xml:176(replaceable) ./doc/install-guide/section_neutron-ml2-controller-node.xml:212(replaceable) ./doc/install-guide/section_neutron-ml2-controller-node.xml:225(replaceable) ./doc/install-guide/section_neutron-ml2-controller-node.xml:233(replaceable) ./doc/install-guide/section_neutron-ml2-controller-node.xml:252(replaceable) ./doc/install-guide/section_neutron-ml2-controller-node.xml:256(replaceable) ./doc/install-guide/section_neutron-ml2-controller-node.xml:369(replaceable) ./doc/install-guide/section_neutron-ml2-controller-node.xml:379(replaceable) ./doc/install-guide/section_neutron-ml2-controller-node.xml:403(replaceable) ./doc/install-guide/section_neutron-ml2-controller-node.xml:408(replaceable) ./doc/install-guide/section_nova-compute-install.xml:38(replaceable) ./doc/install-guide/section_nova-compute-install.xml:48(replaceable) ./doc/install-guide/section_nova-compute-install.xml:60(replaceable) ./doc/install-guide/section_nova-compute-install.xml:61(replaceable) ./doc/install-guide/section_nova-compute-install.xml:92(replaceable) ./doc/install-guide/section_nova-compute-install.xml:117(replaceable) ./doc/install-guide/section_neutron-ovs-controller-node.xml:56(replaceable) ./doc/install-guide/section_neutron-ovs-controller-node.xml:57(replaceable) ./doc/install-guide/section_neutron-ovs-controller-node.xml:58(replaceable) ./doc/install-guide/section_neutron-ovs-controller-node.xml:82(replaceable) ./doc/install-guide/section_neutron-ovs-controller-node.xml:99(replaceable) ./doc/install-guide/section_neutron-ovs-controller-node.xml:101(replaceable) ./doc/install-guide/section_neutron-ovs-controller-node.xml:134(replaceable) ./doc/install-guide/section_neutron-ovs-controller-node.xml:135(replaceable) ./doc/install-guide/section_neutron-ovs-controller-node.xml:166(replaceable) ./doc/install-guide/section_neutron-ovs-controller-node.xml:216(replaceable) ./doc/install-guide/section_neutron-ovs-controller-node.xml:226(replaceable) ./doc/install-guide/section_neutron-ovs-controller-node.xml:237(replaceable) ./doc/install-guide/section_neutron-ovs-controller-node.xml:242(replaceable) ./doc/install-guide/section_heat-install.xml:63(replaceable) ./doc/install-guide/section_heat-install.xml:64(replaceable) ./doc/install-guide/section_heat-install.xml:65(replaceable) ./doc/install-guide/section_heat-install.xml:68(replaceable) ./doc/install-guide/section_heat-install.xml:69(replaceable) ./doc/install-guide/section_heat-install.xml:70(replaceable) ./doc/install-guide/section_heat-install.xml:89(replaceable) ./doc/install-guide/section_heat-install.xml:99(replaceable) ./doc/install-guide/section_heat-install.xml:111(replaceable) ./doc/install-guide/section_heat-install.xml:112(replaceable) ./doc/install-guide/section_heat-install.xml:121(replaceable) ./doc/install-guide/section_heat-install.xml:131(replaceable) ./doc/install-guide/section_heat-install.xml:132(replaceable) ./doc/install-guide/section_heat-install.xml:177(replaceable) ./doc/install-guide/section_neutron-ml2-network-node.xml:67(replaceable) ./doc/install-guide/section_neutron-ml2-network-node.xml:69(replaceable) ./doc/install-guide/section_neutron-ml2-network-node.xml:100(replaceable) ./doc/install-guide/section_neutron-ml2-network-node.xml:101(replaceable) ./doc/install-guide/section_neutron-ml2-network-node.xml:118(replaceable) ./doc/install-guide/section_neutron-ml2-network-node.xml:138(replaceable) ./doc/install-guide/section_neutron-ml2-network-node.xml:265(replaceable) ./doc/install-guide/section_neutron-ml2-network-node.xml:275(replaceable) ./doc/install-guide/section_neutron-ml2-network-node.xml:297(replaceable) ./doc/install-guide/section_neutron-ml2-network-node.xml:302(replaceable) ./doc/install-guide/section_ceilometer-glance.xml:18(replaceable) ./doc/install-guide/section_ceilometer-glance.xml:24(replaceable) ./doc/install-guide/section_keystone-services.xml:56(replaceable) ./doc/install-guide/section_keystone-services.xml:57(replaceable) ./doc/install-guide/section_keystone-services.xml:58(replaceable) ./doc/install-guide/section_neutron-ovs-network-node.xml:98(replaceable) ./doc/install-guide/section_neutron-ovs-network-node.xml:100(replaceable) ./doc/install-guide/section_neutron-ovs-network-node.xml:131(replaceable) ./doc/install-guide/section_neutron-ovs-network-node.xml:132(replaceable) ./doc/install-guide/section_neutron-ovs-network-node.xml:146(replaceable) ./doc/install-guide/section_neutron-ovs-network-node.xml:157(replaceable) ./doc/install-guide/section_neutron-ovs-network-node.xml:374(replaceable) ./doc/install-guide/section_neutron-ovs-network-node.xml:379(replaceable) ./doc/install-guide/section_neutron-ovs-network-node.xml:384(replaceable) ./doc/install-guide/section_neutron-ovs-network-node.xml:394(replaceable) ./doc/install-guide/object-storage/section_object-storage-install-config-proxy-node.xml:80(replaceable) ./doc/install-guide/object-storage/section_object-storage-install.xml:102(replaceable) ./doc/install-guide/object-storage/section_object-storage-install.xml:103(replaceable) ./doc/install-guide/object-storage/section_object-storage-install.xml:104(replaceable) msgid "controller" msgstr "" @@ -155,7 +155,7 @@ msgstr "" msgid "Register the Identity service in the catalog:" msgstr "" -#: ./doc/install-guide/section_keystone-install.xml:186(title) ./doc/install-guide/section_nova-controller-install.xml:197(title) ./doc/install-guide/section_glance-install.xml:211(title) ./doc/install-guide/section_neutron-ml2-controller-node.xml:419(title) ./doc/install-guide/section_nova-compute-install.xml:140(title) ./doc/install-guide/section_heat-install.xml:183(title) +#: ./doc/install-guide/section_keystone-install.xml:186(title) ./doc/install-guide/section_nova-controller-install.xml:197(title) ./doc/install-guide/section_glance-install.xml:211(title) ./doc/install-guide/section_neutron-ml2-controller-node.xml:422(title) ./doc/install-guide/section_nova-compute-install.xml:140(title) ./doc/install-guide/section_heat-install.xml:183(title) msgid "To finalize installation" msgstr "" @@ -351,7 +351,7 @@ msgstr "" msgid "In the [DEFAULT] section in the /etc/cinder/cinder.conf file, set these configuration keys and replace RABBIT_PASS with the password you chose for RabbitMQ:" msgstr "" -#: ./doc/install-guide/section_cinder-controller.xml:130(replaceable) ./doc/install-guide/section_cinder-controller.xml:144(replaceable) ./doc/install-guide/section_ceilometer-nova.xml:77(replaceable) ./doc/install-guide/section_ceilometer-nova.xml:81(replaceable) ./doc/install-guide/section_neutron-ovs-compute-node.xml:191(replaceable) ./doc/install-guide/section_neutron-ovs-compute-node.xml:200(replaceable) ./doc/install-guide/section_ceilometer-install.xml:147(replaceable) ./doc/install-guide/section_ceilometer-install.xml:150(replaceable) ./doc/install-guide/section_nova-controller-install.xml:110(replaceable) ./doc/install-guide/section_glance-install.xml:112(replaceable) ./doc/install-guide/section_cinder-node.xml:166(replaceable) ./doc/install-guide/section_cinder-node.xml:179(replaceable) ./doc/install-guide/section_neutron-ml2-compute-node.xml:115(replaceable) ./doc/install-guide/section_neutron-ml2-compute-node.xml:135(replaceable) ./doc/install-guide/section_trove-install.xml:91(replaceable) ./doc/install-guide/section_trove-install.xml:111(replaceable) ./doc/install-guide/section_trove-install.xml:113(replaceable) ./doc/install-guide/section_trove-install.xml:115(replaceable) ./doc/install-guide/section_trove-install.xml:207(replaceable) ./doc/install-guide/section_neutron-ml2-controller-node.xml:194(replaceable) ./doc/install-guide/section_neutron-ml2-controller-node.xml:210(replaceable) ./doc/install-guide/section_nova-compute-install.xml:49(replaceable) ./doc/install-guide/section_neutron-ovs-controller-node.xml:154(replaceable) ./doc/install-guide/section_neutron-ovs-controller-node.xml:167(replaceable) ./doc/install-guide/section_heat-install.xml:100(replaceable) ./doc/install-guide/section_neutron-ml2-network-node.xml:121(replaceable) ./doc/install-guide/section_neutron-ml2-network-node.xml:138(replaceable) ./doc/install-guide/section_ceilometer-glance.xml:19(replaceable) ./doc/install-guide/section_ceilometer-glance.xml:25(replaceable) ./doc/install-guide/section_basics-queue.xml:58(replaceable) ./doc/install-guide/section_neutron-ovs-network-node.xml:150(replaceable) ./doc/install-guide/section_neutron-ovs-network-node.xml:159(replaceable) +#: ./doc/install-guide/section_cinder-controller.xml:130(replaceable) ./doc/install-guide/section_cinder-controller.xml:144(replaceable) ./doc/install-guide/section_ceilometer-nova.xml:77(replaceable) ./doc/install-guide/section_ceilometer-nova.xml:81(replaceable) ./doc/install-guide/section_neutron-ovs-compute-node.xml:191(replaceable) ./doc/install-guide/section_neutron-ovs-compute-node.xml:200(replaceable) ./doc/install-guide/section_ceilometer-install.xml:147(replaceable) ./doc/install-guide/section_ceilometer-install.xml:150(replaceable) ./doc/install-guide/section_nova-controller-install.xml:110(replaceable) ./doc/install-guide/section_glance-install.xml:112(replaceable) ./doc/install-guide/section_cinder-node.xml:166(replaceable) ./doc/install-guide/section_cinder-node.xml:179(replaceable) ./doc/install-guide/section_neutron-ml2-compute-node.xml:115(replaceable) ./doc/install-guide/section_neutron-ml2-compute-node.xml:135(replaceable) ./doc/install-guide/section_trove-install.xml:91(replaceable) ./doc/install-guide/section_trove-install.xml:111(replaceable) ./doc/install-guide/section_trove-install.xml:113(replaceable) ./doc/install-guide/section_trove-install.xml:115(replaceable) ./doc/install-guide/section_trove-install.xml:207(replaceable) ./doc/install-guide/section_neutron-ml2-controller-node.xml:197(replaceable) ./doc/install-guide/section_neutron-ml2-controller-node.xml:213(replaceable) ./doc/install-guide/section_nova-compute-install.xml:49(replaceable) ./doc/install-guide/section_neutron-ovs-controller-node.xml:154(replaceable) ./doc/install-guide/section_neutron-ovs-controller-node.xml:167(replaceable) ./doc/install-guide/section_heat-install.xml:100(replaceable) ./doc/install-guide/section_neutron-ml2-network-node.xml:122(replaceable) ./doc/install-guide/section_neutron-ml2-network-node.xml:139(replaceable) ./doc/install-guide/section_ceilometer-glance.xml:19(replaceable) ./doc/install-guide/section_ceilometer-glance.xml:25(replaceable) ./doc/install-guide/section_basics-queue.xml:58(replaceable) ./doc/install-guide/section_neutron-ovs-network-node.xml:150(replaceable) ./doc/install-guide/section_neutron-ovs-network-node.xml:159(replaceable) msgid "RABBIT_PASS" msgstr "" @@ -623,7 +623,7 @@ msgstr "" msgid "Create the demo user:" msgstr "" -#: ./doc/install-guide/section_keystone-users.xml:144(replaceable) ./doc/install-guide/section_keystone-verify.xml:89(replaceable) ./doc/install-guide/section_keystone-verify.xml:101(replaceable) ./doc/install-guide/ch_clients.xml:41(replaceable) ./doc/install-guide/section_keystone-openrc.xml:36(replaceable) +#: ./doc/install-guide/section_keystone-users.xml:144(replaceable) ./doc/install-guide/section_keystone-verify.xml:89(replaceable) ./doc/install-guide/section_keystone-verify.xml:101(replaceable) ./doc/install-guide/section_keystone-openrc.xml:36(replaceable) msgid "DEMO_PASS" msgstr "" @@ -889,7 +889,7 @@ msgstr "" msgid "The external interface uses a special configuration without an IP address assigned to it. Configure the third interface as the external interface:" msgstr "" -#: ./doc/install-guide/section_basics-networking-neutron.xml:102(para) ./doc/install-guide/section_neutron-ml2-network-node.xml:450(para) +#: ./doc/install-guide/section_basics-networking-neutron.xml:102(para) ./doc/install-guide/section_neutron-ml2-network-node.xml:451(para) msgid "Replace INTERFACE_NAME with the actual interface name. For example, eth2 or ens256." msgstr "" @@ -897,7 +897,7 @@ msgstr "" msgid "Edit the /etc/network/interfaces file to contain the following:" msgstr "" -#: ./doc/install-guide/section_basics-networking-neutron.xml:110(replaceable) ./doc/install-guide/section_basics-networking-neutron.xml:111(replaceable) ./doc/install-guide/section_basics-networking-neutron.xml:121(replaceable) ./doc/install-guide/section_nova-networking-compute-node.xml:52(replaceable) ./doc/install-guide/section_nova-networking-compute-node.xml:54(replaceable) ./doc/install-guide/section_nova-networking-compute-node.xml:75(replaceable) ./doc/install-guide/section_nova-networking-compute-node.xml:76(replaceable) ./doc/install-guide/section_basics-networking-nova.xml:101(replaceable) ./doc/install-guide/section_basics-networking-nova.xml:102(replaceable) ./doc/install-guide/section_basics-networking-nova.xml:112(replaceable) ./doc/install-guide/section_neutron-ml2-network-node.xml:453(replaceable) ./doc/install-guide/section_neutron-ml2-network-node.xml:461(replaceable) +#: ./doc/install-guide/section_basics-networking-neutron.xml:110(replaceable) ./doc/install-guide/section_basics-networking-neutron.xml:111(replaceable) ./doc/install-guide/section_basics-networking-neutron.xml:121(replaceable) ./doc/install-guide/section_nova-networking-compute-node.xml:52(replaceable) ./doc/install-guide/section_nova-networking-compute-node.xml:54(replaceable) ./doc/install-guide/section_nova-networking-compute-node.xml:75(replaceable) ./doc/install-guide/section_nova-networking-compute-node.xml:76(replaceable) ./doc/install-guide/section_basics-networking-nova.xml:101(replaceable) ./doc/install-guide/section_basics-networking-nova.xml:102(replaceable) ./doc/install-guide/section_basics-networking-nova.xml:112(replaceable) ./doc/install-guide/section_neutron-ml2-network-node.xml:454(replaceable) ./doc/install-guide/section_neutron-ml2-network-node.xml:462(replaceable) msgid "INTERFACE_NAME" msgstr "" @@ -1441,7 +1441,7 @@ msgstr "" msgid "Set the neutron configuration for keystone authentication:" msgstr "" -#: ./doc/install-guide/section_neutron-ovs-compute-node.xml:148(replaceable) ./doc/install-guide/section_neutron-ovs-compute-node.xml:178(replaceable) ./doc/install-guide/section_neutron-ovs-compute-node.xml:220(replaceable) ./doc/install-guide/section_neutron-ovs-compute-node.xml:237(replaceable) ./doc/install-guide/section_neutron-ml2-compute-node.xml:72(replaceable) ./doc/install-guide/section_neutron-ml2-compute-node.xml:99(replaceable) ./doc/install-guide/section_neutron-ml2-compute-node.xml:288(replaceable) ./doc/install-guide/section_neutron-ml2-compute-node.xml:322(replaceable) ./doc/install-guide/section_neutron-ml2-controller-node.xml:34(replaceable) ./doc/install-guide/section_neutron-ml2-controller-node.xml:152(replaceable) ./doc/install-guide/section_neutron-ml2-controller-node.xml:178(replaceable) ./doc/install-guide/section_neutron-ml2-controller-node.xml:374(replaceable) ./doc/install-guide/section_neutron-ml2-controller-node.xml:404(replaceable) ./doc/install-guide/section_neutron-ovs-controller-node.xml:47(replaceable) ./doc/install-guide/section_neutron-ovs-controller-node.xml:111(replaceable) ./doc/install-guide/section_neutron-ovs-controller-node.xml:140(replaceable) ./doc/install-guide/section_neutron-ovs-controller-node.xml:224(replaceable) ./doc/install-guide/section_neutron-ovs-controller-node.xml:241(replaceable) ./doc/install-guide/section_neutron-ml2-network-node.xml:78(replaceable) ./doc/install-guide/section_neutron-ml2-network-node.xml:105(replaceable) ./doc/install-guide/section_neutron-ml2-network-node.xml:272(replaceable) ./doc/install-guide/section_neutron-ml2-network-node.xml:300(replaceable) ./doc/install-guide/section_neutron-ovs-network-node.xml:110(replaceable) ./doc/install-guide/section_neutron-ovs-network-node.xml:137(replaceable) ./doc/install-guide/section_neutron-ovs-network-node.xml:378(replaceable) ./doc/install-guide/section_neutron-ovs-network-node.xml:392(replaceable) +#: ./doc/install-guide/section_neutron-ovs-compute-node.xml:148(replaceable) ./doc/install-guide/section_neutron-ovs-compute-node.xml:178(replaceable) ./doc/install-guide/section_neutron-ovs-compute-node.xml:220(replaceable) ./doc/install-guide/section_neutron-ovs-compute-node.xml:237(replaceable) ./doc/install-guide/section_neutron-ml2-compute-node.xml:72(replaceable) ./doc/install-guide/section_neutron-ml2-compute-node.xml:99(replaceable) ./doc/install-guide/section_neutron-ml2-compute-node.xml:288(replaceable) ./doc/install-guide/section_neutron-ml2-compute-node.xml:322(replaceable) ./doc/install-guide/section_neutron-ml2-controller-node.xml:34(replaceable) ./doc/install-guide/section_neutron-ml2-controller-node.xml:155(replaceable) ./doc/install-guide/section_neutron-ml2-controller-node.xml:181(replaceable) ./doc/install-guide/section_neutron-ml2-controller-node.xml:377(replaceable) ./doc/install-guide/section_neutron-ml2-controller-node.xml:407(replaceable) ./doc/install-guide/section_neutron-ovs-controller-node.xml:47(replaceable) ./doc/install-guide/section_neutron-ovs-controller-node.xml:111(replaceable) ./doc/install-guide/section_neutron-ovs-controller-node.xml:140(replaceable) ./doc/install-guide/section_neutron-ovs-controller-node.xml:224(replaceable) ./doc/install-guide/section_neutron-ovs-controller-node.xml:241(replaceable) ./doc/install-guide/section_neutron-ml2-network-node.xml:79(replaceable) ./doc/install-guide/section_neutron-ml2-network-node.xml:106(replaceable) ./doc/install-guide/section_neutron-ml2-network-node.xml:273(replaceable) ./doc/install-guide/section_neutron-ml2-network-node.xml:301(replaceable) ./doc/install-guide/section_neutron-ovs-network-node.xml:110(replaceable) ./doc/install-guide/section_neutron-ovs-network-node.xml:137(replaceable) ./doc/install-guide/section_neutron-ovs-network-node.xml:378(replaceable) ./doc/install-guide/section_neutron-ovs-network-node.xml:392(replaceable) msgid "NEUTRON_PASS" msgstr "" @@ -1911,38 +1911,6 @@ msgstr "" msgid "Ping the tenant router gateway:" msgstr "" -#: ./doc/install-guide/ch_clients.xml:7(title) -msgid "Install and configure the OpenStack clients" -msgstr "" - -#: ./doc/install-guide/ch_clients.xml:8(para) -msgid "The following sections contain information about working with the OpenStack clients. Recall: in the previous section, you used the client." -msgstr "" - -#: ./doc/install-guide/ch_clients.xml:11(para) -msgid "You must install the client tools to complete the rest of the installation." -msgstr "" - -#: ./doc/install-guide/ch_clients.xml:13(para) -msgid "Configure the clients on your desktop rather than on the server so that you have a similar experience to your users." -msgstr "" - -#: ./doc/install-guide/ch_clients.xml:21(title) -msgid "Create openrc.sh files" -msgstr "" - -#: ./doc/install-guide/ch_clients.xml:23(para) -msgid "As explained in , use the credentials from and create the following PROJECT-openrc.sh files:" -msgstr "" - -#: ./doc/install-guide/ch_clients.xml:33(para) -msgid "admin-openrc.sh for the administrative user" -msgstr "" - -#: ./doc/install-guide/ch_clients.xml:38(para) -msgid "demo-openrc.sh for the normal user: " -msgstr "" - #: ./doc/install-guide/ch_basics.xml:8(title) msgid "Basic environment configuration" msgstr "" @@ -2011,7 +1979,7 @@ msgstr "" msgid "Create the nova user:" msgstr "" -#: ./doc/install-guide/section_nova-controller-install.xml:51(replaceable) ./doc/install-guide/section_nova-controller-install.xml:127(replaceable) ./doc/install-guide/section_neutron-ml2-controller-node.xml:228(replaceable) ./doc/install-guide/section_neutron-ml2-controller-node.xml:252(replaceable) ./doc/install-guide/section_nova-compute-install.xml:66(replaceable) +#: ./doc/install-guide/section_nova-controller-install.xml:51(replaceable) ./doc/install-guide/section_nova-controller-install.xml:127(replaceable) ./doc/install-guide/section_neutron-ml2-controller-node.xml:231(replaceable) ./doc/install-guide/section_neutron-ml2-controller-node.xml:255(replaceable) ./doc/install-guide/section_nova-compute-install.xml:66(replaceable) msgid "NOVA_PASS" msgstr "" @@ -2051,7 +2019,7 @@ msgstr "" msgid "In the [DEFAULT] section, configure RabbitMQ message broker access:" msgstr "" -#: ./doc/install-guide/section_nova-controller-install.xml:111(para) ./doc/install-guide/section_glance-install.xml:113(para) ./doc/install-guide/section_neutron-ml2-compute-node.xml:116(para) ./doc/install-guide/section_neutron-ml2-compute-node.xml:128(para) ./doc/install-guide/section_neutron-ml2-controller-node.xml:184(para) ./doc/install-guide/section_neutron-ml2-controller-node.xml:203(para) ./doc/install-guide/section_nova-compute-install.xml:50(para) ./doc/install-guide/section_heat-install.xml:101(para) ./doc/install-guide/section_neutron-ml2-network-node.xml:111(para) ./doc/install-guide/section_neutron-ml2-network-node.xml:131(para) +#: ./doc/install-guide/section_nova-controller-install.xml:111(para) ./doc/install-guide/section_glance-install.xml:113(para) ./doc/install-guide/section_neutron-ml2-compute-node.xml:116(para) ./doc/install-guide/section_neutron-ml2-compute-node.xml:128(para) ./doc/install-guide/section_neutron-ml2-controller-node.xml:187(para) ./doc/install-guide/section_neutron-ml2-controller-node.xml:206(para) ./doc/install-guide/section_nova-compute-install.xml:50(para) ./doc/install-guide/section_heat-install.xml:101(para) ./doc/install-guide/section_neutron-ml2-network-node.xml:112(para) ./doc/install-guide/section_neutron-ml2-network-node.xml:132(para) msgid "Replace RABBIT_PASS with the password you chose for the guest account in RabbitMQ." msgstr "" @@ -2083,11 +2051,11 @@ msgstr "" msgid "To install and configure the Compute controller components" msgstr "" -#: ./doc/install-guide/section_nova-controller-install.xml:171(para) ./doc/install-guide/section_glance-install.xml:189(para) ./doc/install-guide/section_neutron-ml2-compute-node.xml:46(para) ./doc/install-guide/section_neutron-ml2-controller-node.xml:78(para) ./doc/install-guide/section_heat-install.xml:156(para) ./doc/install-guide/section_neutron-ml2-network-node.xml:49(para) +#: ./doc/install-guide/section_nova-controller-install.xml:171(para) ./doc/install-guide/section_glance-install.xml:189(para) ./doc/install-guide/section_neutron-ml2-compute-node.xml:46(para) ./doc/install-guide/section_neutron-ml2-controller-node.xml:81(para) ./doc/install-guide/section_heat-install.xml:156(para) ./doc/install-guide/section_neutron-ml2-network-node.xml:50(para) msgid "Respond to prompts for database management, Identity service credentials, service endpoint registration, and message broker credentials." msgstr "" -#: ./doc/install-guide/section_nova-controller-install.xml:199(para) ./doc/install-guide/section_nova-networking-controller-node.xml:29(para) ./doc/install-guide/section_neutron-ml2-controller-node.xml:441(para) ./doc/install-guide/section_neutron-ovs-controller-node.xml:318(para) +#: ./doc/install-guide/section_nova-controller-install.xml:199(para) ./doc/install-guide/section_nova-networking-controller-node.xml:29(para) ./doc/install-guide/section_neutron-ml2-controller-node.xml:444(para) ./doc/install-guide/section_neutron-ovs-controller-node.xml:318(para) msgid "Restart the Compute services:" msgstr "" @@ -2327,7 +2295,7 @@ msgstr "" msgid "To configure legacy networking" msgstr "" -#: ./doc/install-guide/section_nova-networking-compute-node.xml:25(para) ./doc/install-guide/section_neutron-ml2-compute-node.xml:184(para) ./doc/install-guide/section_neutron-ml2-compute-node.xml:276(para) ./doc/install-guide/section_nova-networking-controller-node.xml:14(para) ./doc/install-guide/section_neutron-ml2-controller-node.xml:315(para) ./doc/install-guide/section_neutron-ml2-controller-node.xml:359(para) ./doc/install-guide/section_neutron-ml2-network-node.xml:186(para) ./doc/install-guide/section_neutron-ml2-network-node.xml:220(para) ./doc/install-guide/section_neutron-ml2-network-node.xml:257(para) ./doc/install-guide/section_neutron-ml2-network-node.xml:351(para) ./doc/install-guide/section_ceilometer-glance.xml:21(para) +#: ./doc/install-guide/section_nova-networking-compute-node.xml:25(para) ./doc/install-guide/section_neutron-ml2-compute-node.xml:184(para) ./doc/install-guide/section_neutron-ml2-compute-node.xml:276(para) ./doc/install-guide/section_nova-networking-controller-node.xml:14(para) ./doc/install-guide/section_neutron-ml2-controller-node.xml:318(para) ./doc/install-guide/section_neutron-ml2-controller-node.xml:362(para) ./doc/install-guide/section_neutron-ml2-network-node.xml:187(para) ./doc/install-guide/section_neutron-ml2-network-node.xml:221(para) ./doc/install-guide/section_neutron-ml2-network-node.xml:258(para) ./doc/install-guide/section_neutron-ml2-network-node.xml:352(para) ./doc/install-guide/section_ceilometer-glance.xml:21(para) msgid "Run the following commands:" msgstr "" @@ -2797,7 +2765,7 @@ msgstr "" msgid "Implement the changes:" msgstr "" -#: ./doc/install-guide/section_neutron-ml2-compute-node.xml:24(title) ./doc/install-guide/section_neutron-ml2-controller-node.xml:58(title) ./doc/install-guide/section_neutron-ml2-network-node.xml:25(title) +#: ./doc/install-guide/section_neutron-ml2-compute-node.xml:24(title) ./doc/install-guide/section_neutron-ml2-controller-node.xml:61(title) ./doc/install-guide/section_neutron-ml2-network-node.xml:25(title) msgid "To install the Networking components" msgstr "" @@ -2805,51 +2773,51 @@ msgstr "" msgid "Ubuntu installations that use Linux kernel version 3.11 or later do not require the openvswitch-datapath-dkms package." msgstr "" -#: ./doc/install-guide/section_neutron-ml2-compute-node.xml:37(para) ./doc/install-guide/section_neutron-ml2-controller-node.xml:65(para) ./doc/install-guide/section_neutron-ml2-network-node.xml:40(para) +#: ./doc/install-guide/section_neutron-ml2-compute-node.xml:37(para) ./doc/install-guide/section_neutron-ml2-controller-node.xml:68(para) ./doc/install-guide/section_neutron-ml2-network-node.xml:41(para) msgid "SUSE does not use a separate ML2 plug-in package." msgstr "" -#: ./doc/install-guide/section_neutron-ml2-compute-node.xml:42(title) ./doc/install-guide/section_neutron-ml2-network-node.xml:45(title) +#: ./doc/install-guide/section_neutron-ml2-compute-node.xml:42(title) ./doc/install-guide/section_neutron-ml2-network-node.xml:46(title) msgid "To configure the Networking common components" msgstr "" -#: ./doc/install-guide/section_neutron-ml2-compute-node.xml:43(para) ./doc/install-guide/section_neutron-ml2-network-node.xml:46(para) +#: ./doc/install-guide/section_neutron-ml2-compute-node.xml:43(para) ./doc/install-guide/section_neutron-ml2-network-node.xml:47(para) msgid "The Networking common component configuration includes the authentication mechanism, message broker, and plug-in." msgstr "" -#: ./doc/install-guide/section_neutron-ml2-compute-node.xml:55(para) ./doc/install-guide/section_neutron-ml2-compute-node.xml:78(para) ./doc/install-guide/section_neutron-ml2-controller-node.xml:132(para) ./doc/install-guide/section_neutron-ml2-controller-node.xml:155(para) ./doc/install-guide/section_neutron-ml2-network-node.xml:58(para) ./doc/install-guide/section_neutron-ml2-network-node.xml:81(para) +#: ./doc/install-guide/section_neutron-ml2-compute-node.xml:55(para) ./doc/install-guide/section_neutron-ml2-compute-node.xml:78(para) ./doc/install-guide/section_neutron-ml2-controller-node.xml:135(para) ./doc/install-guide/section_neutron-ml2-controller-node.xml:158(para) ./doc/install-guide/section_neutron-ml2-network-node.xml:59(para) ./doc/install-guide/section_neutron-ml2-network-node.xml:82(para) msgid "Configure Networking to use the Identity service for authentication:" msgstr "" -#: ./doc/install-guide/section_neutron-ml2-compute-node.xml:73(para) ./doc/install-guide/section_neutron-ml2-compute-node.xml:100(para) ./doc/install-guide/section_neutron-ml2-compute-node.xml:297(para) ./doc/install-guide/section_neutron-ml2-compute-node.xml:312(para) ./doc/install-guide/section_neutron-ml2-controller-node.xml:134(para) ./doc/install-guide/section_neutron-ml2-controller-node.xml:167(para) ./doc/install-guide/section_neutron-ml2-controller-node.xml:360(para) ./doc/install-guide/section_neutron-ml2-controller-node.xml:394(para) ./doc/install-guide/section_neutron-ml2-network-node.xml:60(para) ./doc/install-guide/section_neutron-ml2-network-node.xml:94(para) +#: ./doc/install-guide/section_neutron-ml2-compute-node.xml:73(para) ./doc/install-guide/section_neutron-ml2-compute-node.xml:100(para) ./doc/install-guide/section_neutron-ml2-compute-node.xml:297(para) ./doc/install-guide/section_neutron-ml2-compute-node.xml:312(para) ./doc/install-guide/section_neutron-ml2-controller-node.xml:137(para) ./doc/install-guide/section_neutron-ml2-controller-node.xml:170(para) ./doc/install-guide/section_neutron-ml2-controller-node.xml:363(para) ./doc/install-guide/section_neutron-ml2-controller-node.xml:397(para) ./doc/install-guide/section_neutron-ml2-network-node.xml:61(para) ./doc/install-guide/section_neutron-ml2-network-node.xml:95(para) msgid "Replace NEUTRON_PASS with the password you chose for the neutron user in the Identity service." msgstr "" -#: ./doc/install-guide/section_neutron-ml2-compute-node.xml:82(para) ./doc/install-guide/section_neutron-ml2-controller-node.xml:159(para) ./doc/install-guide/section_neutron-ml2-network-node.xml:85(para) +#: ./doc/install-guide/section_neutron-ml2-compute-node.xml:82(para) ./doc/install-guide/section_neutron-ml2-controller-node.xml:162(para) ./doc/install-guide/section_neutron-ml2-network-node.xml:86(para) msgid "Edit the /etc/neutron/neutron.conf file and add the following key to the [DEFAULT] section:" msgstr "" -#: ./doc/install-guide/section_neutron-ml2-compute-node.xml:89(para) ./doc/install-guide/section_neutron-ml2-controller-node.xml:165(para) ./doc/install-guide/section_neutron-ml2-network-node.xml:92(para) +#: ./doc/install-guide/section_neutron-ml2-compute-node.xml:89(para) ./doc/install-guide/section_neutron-ml2-controller-node.xml:168(para) ./doc/install-guide/section_neutron-ml2-network-node.xml:93(para) msgid "Add the following keys to the [keystone_authtoken] section:" msgstr "" -#: ./doc/install-guide/section_neutron-ml2-compute-node.xml:107(para) ./doc/install-guide/section_neutron-ml2-compute-node.xml:121(para) ./doc/install-guide/section_neutron-ml2-controller-node.xml:183(para) ./doc/install-guide/section_neutron-ml2-controller-node.xml:197(para) ./doc/install-guide/section_neutron-ml2-network-node.xml:110(para) ./doc/install-guide/section_neutron-ml2-network-node.xml:124(para) +#: ./doc/install-guide/section_neutron-ml2-compute-node.xml:107(para) ./doc/install-guide/section_neutron-ml2-compute-node.xml:121(para) ./doc/install-guide/section_neutron-ml2-controller-node.xml:186(para) ./doc/install-guide/section_neutron-ml2-controller-node.xml:200(para) ./doc/install-guide/section_neutron-ml2-network-node.xml:111(para) ./doc/install-guide/section_neutron-ml2-network-node.xml:125(para) msgid "Configure Networking to use the message broker:" msgstr "" -#: ./doc/install-guide/section_neutron-ml2-compute-node.xml:124(para) ./doc/install-guide/section_neutron-ml2-compute-node.xml:158(para) ./doc/install-guide/section_neutron-ml2-controller-node.xml:200(para) ./doc/install-guide/section_neutron-ml2-controller-node.xml:242(para) ./doc/install-guide/section_neutron-ml2-controller-node.xml:290(para) ./doc/install-guide/section_neutron-ml2-network-node.xml:127(para) ./doc/install-guide/section_neutron-ml2-network-node.xml:161(para) +#: ./doc/install-guide/section_neutron-ml2-compute-node.xml:124(para) ./doc/install-guide/section_neutron-ml2-compute-node.xml:158(para) ./doc/install-guide/section_neutron-ml2-controller-node.xml:203(para) ./doc/install-guide/section_neutron-ml2-controller-node.xml:245(para) ./doc/install-guide/section_neutron-ml2-controller-node.xml:293(para) ./doc/install-guide/section_neutron-ml2-network-node.xml:128(para) ./doc/install-guide/section_neutron-ml2-network-node.xml:162(para) msgid "Edit the /etc/neutron/neutron.conf file and add the following keys to the [DEFAULT] section:" msgstr "" -#: ./doc/install-guide/section_neutron-ml2-compute-node.xml:140(para) ./doc/install-guide/section_neutron-ml2-compute-node.xml:154(para) ./doc/install-guide/section_neutron-ml2-controller-node.xml:272(para) ./doc/install-guide/section_neutron-ml2-controller-node.xml:286(para) ./doc/install-guide/section_neutron-ml2-network-node.xml:143(para) ./doc/install-guide/section_neutron-ml2-network-node.xml:157(para) +#: ./doc/install-guide/section_neutron-ml2-compute-node.xml:140(para) ./doc/install-guide/section_neutron-ml2-compute-node.xml:154(para) ./doc/install-guide/section_neutron-ml2-controller-node.xml:275(para) ./doc/install-guide/section_neutron-ml2-controller-node.xml:289(para) ./doc/install-guide/section_neutron-ml2-network-node.xml:144(para) ./doc/install-guide/section_neutron-ml2-network-node.xml:158(para) msgid "Configure Networking to use the Modular Layer 2 (ML2) plug-in and associated services:" msgstr "" -#: ./doc/install-guide/section_neutron-ml2-compute-node.xml:147(para) ./doc/install-guide/section_neutron-ml2-compute-node.xml:168(para) ./doc/install-guide/section_neutron-ml2-network-node.xml:150(para) ./doc/install-guide/section_neutron-ml2-network-node.xml:171(para) +#: ./doc/install-guide/section_neutron-ml2-compute-node.xml:147(para) ./doc/install-guide/section_neutron-ml2-compute-node.xml:168(para) ./doc/install-guide/section_neutron-ml2-network-node.xml:151(para) ./doc/install-guide/section_neutron-ml2-network-node.xml:172(para) msgid "To assist with troubleshooting, add verbose = True to the [DEFAULT] section in the /etc/neutron/neutron.conf file." msgstr "" -#: ./doc/install-guide/section_neutron-ml2-compute-node.xml:179(title) ./doc/install-guide/section_neutron-ml2-controller-node.xml:309(title) ./doc/install-guide/section_neutron-ml2-network-node.xml:346(title) +#: ./doc/install-guide/section_neutron-ml2-compute-node.xml:179(title) ./doc/install-guide/section_neutron-ml2-controller-node.xml:312(title) ./doc/install-guide/section_neutron-ml2-network-node.xml:347(title) msgid "To configure the Modular Layer 2 (ML2) plug-in" msgstr "" @@ -2857,7 +2825,7 @@ msgstr "" msgid "The ML2 plug-in uses the Open vSwitch (OVS) mechanism (agent) to build the virtual networking framework for instances." msgstr "" -#: ./doc/install-guide/section_neutron-ml2-compute-node.xml:194(replaceable) ./doc/install-guide/section_neutron-ml2-compute-node.xml:234(replaceable) ./doc/install-guide/section_neutron-ml2-network-node.xml:367(replaceable) ./doc/install-guide/section_neutron-ml2-network-node.xml:401(replaceable) +#: ./doc/install-guide/section_neutron-ml2-compute-node.xml:194(replaceable) ./doc/install-guide/section_neutron-ml2-compute-node.xml:234(replaceable) ./doc/install-guide/section_neutron-ml2-network-node.xml:368(replaceable) ./doc/install-guide/section_neutron-ml2-network-node.xml:402(replaceable) msgid "INSTANCE_TUNNELS_INTERFACE_IP_ADDRESS" msgstr "" @@ -2869,11 +2837,11 @@ msgstr "" msgid "Edit the /etc/neutron/plugins/ml2/ml2_conf.ini file and add the following keys to the [ml2] section:" msgstr "" -#: ./doc/install-guide/section_neutron-ml2-compute-node.xml:221(para) ./doc/install-guide/section_neutron-ml2-network-node.xml:388(para) +#: ./doc/install-guide/section_neutron-ml2-compute-node.xml:221(para) ./doc/install-guide/section_neutron-ml2-network-node.xml:389(para) msgid "Add the following keys to the [ml2_type_gre] section:" msgstr "" -#: ./doc/install-guide/section_neutron-ml2-compute-node.xml:226(para) ./doc/install-guide/section_neutron-ml2-network-node.xml:393(para) +#: ./doc/install-guide/section_neutron-ml2-compute-node.xml:226(para) ./doc/install-guide/section_neutron-ml2-network-node.xml:394(para) msgid "Add the [ovs] section and the following keys to it:" msgstr "" @@ -2881,11 +2849,11 @@ msgstr "" msgid "Replace INSTANCE_TUNNELS_INTERFACE_IP_ADDRESS with the IP address of the instance tunnels network interface on your compute node." msgstr "" -#: ./doc/install-guide/section_neutron-ml2-compute-node.xml:237(para) ./doc/install-guide/section_neutron-ml2-controller-node.xml:345(para) ./doc/install-guide/section_neutron-ml2-network-node.xml:404(para) +#: ./doc/install-guide/section_neutron-ml2-compute-node.xml:237(para) ./doc/install-guide/section_neutron-ml2-controller-node.xml:348(para) ./doc/install-guide/section_neutron-ml2-network-node.xml:405(para) msgid "Add the [securitygroup] section and the following keys to it:" msgstr "" -#: ./doc/install-guide/section_neutron-ml2-compute-node.xml:246(title) ./doc/install-guide/section_neutron-ml2-network-node.xml:413(title) +#: ./doc/install-guide/section_neutron-ml2-compute-node.xml:246(title) ./doc/install-guide/section_neutron-ml2-network-node.xml:414(title) msgid "To configure the Open vSwitch (OVS) service" msgstr "" @@ -2893,44 +2861,44 @@ msgstr "" msgid "The OVS service provides the underlying virtual networking framework for instances." msgstr "" -#: ./doc/install-guide/section_neutron-ml2-compute-node.xml:250(para) ./doc/install-guide/section_neutron-ml2-compute-node.xml:256(para) ./doc/install-guide/section_neutron-ml2-network-node.xml:424(para) ./doc/install-guide/section_neutron-ml2-network-node.xml:430(para) +#: ./doc/install-guide/section_neutron-ml2-compute-node.xml:250(para) ./doc/install-guide/section_neutron-ml2-compute-node.xml:256(para) ./doc/install-guide/section_neutron-ml2-network-node.xml:425(para) ./doc/install-guide/section_neutron-ml2-network-node.xml:431(para) msgid "Start the OVS service and configure it to start when the system boots:" msgstr "" -#: ./doc/install-guide/section_neutron-ml2-compute-node.xml:262(para) ./doc/install-guide/section_neutron-ml2-compute-node.xml:266(para) ./doc/install-guide/section_neutron-ml2-network-node.xml:436(para) ./doc/install-guide/section_neutron-ml2-network-node.xml:440(para) +#: ./doc/install-guide/section_neutron-ml2-compute-node.xml:262(para) ./doc/install-guide/section_neutron-ml2-compute-node.xml:266(para) ./doc/install-guide/section_neutron-ml2-network-node.xml:437(para) ./doc/install-guide/section_neutron-ml2-network-node.xml:441(para) msgid "Restart the OVS service:" msgstr "" -#: ./doc/install-guide/section_neutron-ml2-compute-node.xml:271(title) ./doc/install-guide/section_neutron-ml2-controller-node.xml:354(title) +#: ./doc/install-guide/section_neutron-ml2-compute-node.xml:271(title) ./doc/install-guide/section_neutron-ml2-controller-node.xml:357(title) msgid "To configure Compute to use Networking" msgstr "" -#: ./doc/install-guide/section_neutron-ml2-compute-node.xml:272(para) ./doc/install-guide/section_neutron-ml2-controller-node.xml:355(para) +#: ./doc/install-guide/section_neutron-ml2-compute-node.xml:272(para) ./doc/install-guide/section_neutron-ml2-controller-node.xml:358(para) msgid "By default, most distributions configure Compute to use legacy networking. You must reconfigure Compute to manage networks through Networking." msgstr "" -#: ./doc/install-guide/section_neutron-ml2-compute-node.xml:301(para) ./doc/install-guide/section_neutron-ml2-compute-node.xml:328(para) ./doc/install-guide/section_neutron-ml2-controller-node.xml:384(para) ./doc/install-guide/section_neutron-ml2-controller-node.xml:410(para) +#: ./doc/install-guide/section_neutron-ml2-compute-node.xml:301(para) ./doc/install-guide/section_neutron-ml2-compute-node.xml:328(para) ./doc/install-guide/section_neutron-ml2-controller-node.xml:387(para) ./doc/install-guide/section_neutron-ml2-controller-node.xml:413(para) msgid "By default, Compute uses an internal firewall service. Since Networking includes a firewall service, you must disable the Compute firewall service by using the nova.virt.firewall.NoopFirewallDriver firewall driver." msgstr "" -#: ./doc/install-guide/section_neutron-ml2-compute-node.xml:309(para) ./doc/install-guide/section_neutron-ml2-controller-node.xml:392(para) +#: ./doc/install-guide/section_neutron-ml2-compute-node.xml:309(para) ./doc/install-guide/section_neutron-ml2-controller-node.xml:395(para) msgid "Edit the /etc/nova/nova.conf and add the following keys to the [DEFAULT] section:" msgstr "" -#: ./doc/install-guide/section_neutron-ml2-compute-node.xml:337(title) ./doc/install-guide/section_neutron-ml2-network-node.xml:466(title) +#: ./doc/install-guide/section_neutron-ml2-compute-node.xml:337(title) ./doc/install-guide/section_neutron-ml2-network-node.xml:467(title) msgid "To finalize the installation" msgstr "" -#: ./doc/install-guide/section_neutron-ml2-compute-node.xml:339(para) ./doc/install-guide/section_neutron-ml2-network-node.xml:468(para) +#: ./doc/install-guide/section_neutron-ml2-compute-node.xml:339(para) ./doc/install-guide/section_neutron-ml2-network-node.xml:469(para) msgid "The Networking service initialization scripts expect a symbolic link /etc/neutron/plugin.ini pointing to the configuration file associated with your chosen plug-in. Using the ML2 plug-in, for example, the symbolic link must point to /etc/neutron/plugins/ml2/ml2_conf.ini. If this symbolic link does not exist, create it using the following commands:" msgstr "" #. https://bugzilla.redhat.com/show_bug.cgi?id=1087647 -#: ./doc/install-guide/section_neutron-ml2-compute-node.xml:349(para) ./doc/install-guide/section_neutron-ml2-network-node.xml:478(para) +#: ./doc/install-guide/section_neutron-ml2-compute-node.xml:349(para) ./doc/install-guide/section_neutron-ml2-network-node.xml:479(para) msgid "Due to a packaging bug, the Open vSwitch agent initialization script explicitly looks for the Open vSwitch plug-in configuration file rather than a symbolic link /etc/neutron/plugin.ini pointing to the ML2 plug-in configuration file. Run the following commands to resolve this issue:" msgstr "" -#: ./doc/install-guide/section_neutron-ml2-compute-node.xml:359(para) ./doc/install-guide/section_neutron-ml2-network-node.xml:488(para) +#: ./doc/install-guide/section_neutron-ml2-compute-node.xml:359(para) ./doc/install-guide/section_neutron-ml2-network-node.xml:489(para) msgid "The Networking service initialization scripts expect the variable NEUTRON_PLUGIN_CONF in the /etc/sysconfig/neutron file to reference the configuration file associated with your chosen plug-in. Using ML2, for example, edit the /etc/sysconfig/neutron file and add the following:" msgstr "" @@ -3304,7 +3272,7 @@ msgstr "" #. When image changes, this message will be marked fuzzy or untranslated for you. #. It doesn't matter what you translate it to: it's not used at all. -#: ./doc/install-guide/section_neutron-ml2-controller-node.xml:97(None) +#: ./doc/install-guide/section_neutron-ml2-controller-node.xml:100(None) msgid "@@image: 'figures/debconf-screenshots/neutron_1_plugin_selection.png'; md5=adf41c33778a691a560b7098908792db" msgstr "" @@ -3316,11 +3284,11 @@ msgstr "" msgid "Connect to the database as the root user, create the neutron database, and grant the proper access to it:" msgstr "" -#: ./doc/install-guide/section_neutron-ml2-controller-node.xml:17(para) ./doc/install-guide/section_neutron-ml2-controller-node.xml:111(para) +#: ./doc/install-guide/section_neutron-ml2-controller-node.xml:17(para) ./doc/install-guide/section_neutron-ml2-controller-node.xml:114(para) msgid "Replace NEUTRON_DBPASS with a suitable password." msgstr "" -#: ./doc/install-guide/section_neutron-ml2-controller-node.xml:22(replaceable) ./doc/install-guide/section_neutron-ml2-controller-node.xml:24(replaceable) ./doc/install-guide/section_neutron-ml2-controller-node.xml:114(replaceable) ./doc/install-guide/section_neutron-ml2-controller-node.xml:127(replaceable) ./doc/install-guide/section_neutron-ovs-controller-node.xml:39(replaceable) ./doc/install-guide/section_neutron-ovs-controller-node.xml:41(replaceable) ./doc/install-guide/section_neutron-ovs-controller-node.xml:72(replaceable) ./doc/install-guide/section_neutron-ovs-controller-node.xml:82(replaceable) +#: ./doc/install-guide/section_neutron-ml2-controller-node.xml:22(replaceable) ./doc/install-guide/section_neutron-ml2-controller-node.xml:24(replaceable) ./doc/install-guide/section_neutron-ml2-controller-node.xml:117(replaceable) ./doc/install-guide/section_neutron-ml2-controller-node.xml:130(replaceable) ./doc/install-guide/section_neutron-ovs-controller-node.xml:39(replaceable) ./doc/install-guide/section_neutron-ovs-controller-node.xml:41(replaceable) ./doc/install-guide/section_neutron-ovs-controller-node.xml:72(replaceable) ./doc/install-guide/section_neutron-ovs-controller-node.xml:82(replaceable) msgid "NEUTRON_DBPASS" msgstr "" @@ -3336,103 +3304,103 @@ msgstr "" msgid "Replace NEUTRON_PASS with a suitable password and neutron@example.com with a suitable e-mail address." msgstr "" -#: ./doc/install-guide/section_neutron-ml2-controller-node.xml:34(replaceable) ./doc/install-guide/section_neutron-ovs-controller-node.xml:47(replaceable) +#: ./doc/install-guide/section_neutron-ml2-controller-node.xml:35(replaceable) ./doc/install-guide/section_neutron-ovs-controller-node.xml:47(replaceable) msgid "neutron@example.com" msgstr "" -#: ./doc/install-guide/section_neutron-ml2-controller-node.xml:37(para) +#: ./doc/install-guide/section_neutron-ml2-controller-node.xml:38(para) msgid "Link the neutron user to the service tenant and admin role:" msgstr "" -#: ./doc/install-guide/section_neutron-ml2-controller-node.xml:43(para) +#: ./doc/install-guide/section_neutron-ml2-controller-node.xml:44(para) msgid "Create the neutron service:" msgstr "" -#: ./doc/install-guide/section_neutron-ml2-controller-node.xml:47(para) +#: ./doc/install-guide/section_neutron-ml2-controller-node.xml:49(para) msgid "Create the service endpoint:" msgstr "" -#: ./doc/install-guide/section_neutron-ml2-controller-node.xml:68(para) +#: ./doc/install-guide/section_neutron-ml2-controller-node.xml:71(para) msgid "Debian does not use a separate ML2 plug-in package." msgstr "" -#: ./doc/install-guide/section_neutron-ml2-controller-node.xml:73(title) +#: ./doc/install-guide/section_neutron-ml2-controller-node.xml:76(title) msgid "To configure the Networking server component" msgstr "" -#: ./doc/install-guide/section_neutron-ml2-controller-node.xml:74(para) +#: ./doc/install-guide/section_neutron-ml2-controller-node.xml:77(para) msgid "The Networking server component configuration includes the database, authentication mechanism, message broker, topology change notifier, and plug-in." msgstr "" -#: ./doc/install-guide/section_neutron-ml2-controller-node.xml:88(para) +#: ./doc/install-guide/section_neutron-ml2-controller-node.xml:91(para) msgid "During the installation, you will also be prompted for which Networking plug-in to use. This will automatically fill the directive in the /etc/neutron/neutron.conf file." msgstr "" -#: ./doc/install-guide/section_neutron-ml2-controller-node.xml:101(para) +#: ./doc/install-guide/section_neutron-ml2-controller-node.xml:104(para) msgid "If the ML2 plug-in is selected, then the option will be filled with neutron.plugins.ml2.plugin.Ml2Plugin, which is the full class name for the ML2 plug-in. In Debian, you cannot (yet) use the short names for the plug-ins. The and options are filled with the appropriate values by default, so it is fine to not touch them." msgstr "" -#: ./doc/install-guide/section_neutron-ml2-controller-node.xml:110(para) ./doc/install-guide/section_neutron-ml2-controller-node.xml:117(para) +#: ./doc/install-guide/section_neutron-ml2-controller-node.xml:113(para) ./doc/install-guide/section_neutron-ml2-controller-node.xml:120(para) msgid "Configure Networking to use the database:" msgstr "" -#: ./doc/install-guide/section_neutron-ml2-controller-node.xml:120(para) +#: ./doc/install-guide/section_neutron-ml2-controller-node.xml:123(para) msgid "Edit the /etc/neutron/neutron.conf file and add the following key to the [database] section:" msgstr "" -#: ./doc/install-guide/section_neutron-ml2-controller-node.xml:123(para) +#: ./doc/install-guide/section_neutron-ml2-controller-node.xml:126(para) msgid "Replace NEUTRON_DBPASS with the password you chose for the database." msgstr "" -#: ./doc/install-guide/section_neutron-ml2-controller-node.xml:215(para) ./doc/install-guide/section_neutron-ml2-controller-node.xml:233(para) +#: ./doc/install-guide/section_neutron-ml2-controller-node.xml:218(para) ./doc/install-guide/section_neutron-ml2-controller-node.xml:236(para) msgid "Configure Networking to notify Compute about network topology changes:" msgstr "" -#: ./doc/install-guide/section_neutron-ml2-controller-node.xml:235(para) +#: ./doc/install-guide/section_neutron-ml2-controller-node.xml:238(para) msgid "Replace SERVICE_TENANT_ID with the service tenant identifier (id) in the Identity service and NOVA_PASS with the password you chose for the nova user in the Identity service." msgstr "" -#: ./doc/install-guide/section_neutron-ml2-controller-node.xml:251(replaceable) +#: ./doc/install-guide/section_neutron-ml2-controller-node.xml:254(replaceable) msgid "SERVICE_TENANT_ID" msgstr "" -#: ./doc/install-guide/section_neutron-ml2-controller-node.xml:257(para) +#: ./doc/install-guide/section_neutron-ml2-controller-node.xml:260(para) msgid "To obtain the service tenant identifier (id):" msgstr "" -#: ./doc/install-guide/section_neutron-ml2-controller-node.xml:279(para) ./doc/install-guide/section_neutron-ml2-controller-node.xml:299(para) +#: ./doc/install-guide/section_neutron-ml2-controller-node.xml:282(para) ./doc/install-guide/section_neutron-ml2-controller-node.xml:302(para) msgid "We recommend adding verbose = True to the [DEFAULT] section in /etc/neutron/neutron.conf to assist with troubleshooting." msgstr "" -#: ./doc/install-guide/section_neutron-ml2-controller-node.xml:310(para) +#: ./doc/install-guide/section_neutron-ml2-controller-node.xml:313(para) msgid "The ML2 plug-in uses the Open vSwitch (OVS) mechanism (agent) to build the virtual networking framework for instances. However, the controller node does not need the OVS agent or service because it does not handle instance network traffic." msgstr "" -#: ./doc/install-guide/section_neutron-ml2-controller-node.xml:330(para) +#: ./doc/install-guide/section_neutron-ml2-controller-node.xml:333(para) msgid "Edit the /etc/neutron/plugins/ml2/ml2_conf.ini file:" msgstr "" -#: ./doc/install-guide/section_neutron-ml2-controller-node.xml:333(para) ./doc/install-guide/section_neutron-ml2-network-node.xml:381(para) +#: ./doc/install-guide/section_neutron-ml2-controller-node.xml:336(para) ./doc/install-guide/section_neutron-ml2-network-node.xml:382(para) msgid "Add the following keys to the [ml2] section:" msgstr "" -#: ./doc/install-guide/section_neutron-ml2-controller-node.xml:340(para) +#: ./doc/install-guide/section_neutron-ml2-controller-node.xml:343(para) msgid "Add the following key to the [ml2_type_gre] section:" msgstr "" -#: ./doc/install-guide/section_neutron-ml2-controller-node.xml:421(para) +#: ./doc/install-guide/section_neutron-ml2-controller-node.xml:424(para) msgid "The Networking service initialization scripts expect a symbolic link /etc/neutron/plugin.ini pointing to the configuration file associated with your chosen plug-in. Using ML2, for example, the symbolic link must point to /etc/neutron/plugins/ml2/ml2_conf.ini. If this symbolic link does not exist, create it using the following commands:" msgstr "" -#: ./doc/install-guide/section_neutron-ml2-controller-node.xml:431(para) +#: ./doc/install-guide/section_neutron-ml2-controller-node.xml:434(para) msgid "The Networking service initialization scripts expect the variable NEUTRON_PLUGIN_CONF in file /etc/sysconfig/neutron to reference the configuration file associated with your chosen plug-in. Using ML2, for example, edit the /etc/sysconfig/neutron file and add the following:" msgstr "" -#: ./doc/install-guide/section_neutron-ml2-controller-node.xml:450(para) ./doc/install-guide/section_neutron-ovs-controller-node.xml:324(para) +#: ./doc/install-guide/section_neutron-ml2-controller-node.xml:453(para) ./doc/install-guide/section_neutron-ovs-controller-node.xml:324(para) msgid "Start the Networking service and configure it to start when the system boots:" msgstr "" -#: ./doc/install-guide/section_neutron-ml2-controller-node.xml:458(para) +#: ./doc/install-guide/section_neutron-ml2-controller-node.xml:461(para) msgid "Restart the Networking service:" msgstr "" @@ -3996,127 +3964,127 @@ msgstr "" msgid "Edit /etc/sysctl.conf to contain the following:" msgstr "" -#: ./doc/install-guide/section_neutron-ml2-network-node.xml:34(para) +#: ./doc/install-guide/section_neutron-ml2-network-node.xml:35(para) msgid "Ubuntu installations using Linux kernel version 3.11 or newer do not require the openvswitch-datapath-dkms package." msgstr "" -#: ./doc/install-guide/section_neutron-ml2-network-node.xml:182(title) +#: ./doc/install-guide/section_neutron-ml2-network-node.xml:183(title) msgid "To configure the Layer-3 (L3) agent" msgstr "" -#: ./doc/install-guide/section_neutron-ml2-network-node.xml:183(para) +#: ./doc/install-guide/section_neutron-ml2-network-node.xml:184(para) msgid "The Layer-3 (L3) agent provides routing services for instance virtual networks." msgstr "" -#: ./doc/install-guide/section_neutron-ml2-network-node.xml:192(para) ./doc/install-guide/section_neutron-ml2-network-node.xml:207(para) +#: ./doc/install-guide/section_neutron-ml2-network-node.xml:193(para) ./doc/install-guide/section_neutron-ml2-network-node.xml:208(para) msgid "To assist with troubleshooting, add verbose = True to the [DEFAULT] section in the /etc/neutron/l3_agent.ini file." msgstr "" -#: ./doc/install-guide/section_neutron-ml2-network-node.xml:199(para) +#: ./doc/install-guide/section_neutron-ml2-network-node.xml:200(para) msgid "Edit the /etc/neutron/l3_agent.ini file and add the following keys to the [DEFAULT] section:" msgstr "" -#: ./doc/install-guide/section_neutron-ml2-network-node.xml:215(title) +#: ./doc/install-guide/section_neutron-ml2-network-node.xml:216(title) msgid "To configure the DHCP agent" msgstr "" -#: ./doc/install-guide/section_neutron-ml2-network-node.xml:216(para) +#: ./doc/install-guide/section_neutron-ml2-network-node.xml:217(para) msgid "The DHCP agent provides DHCP services for instance virtual networks." msgstr "" -#: ./doc/install-guide/section_neutron-ml2-network-node.xml:228(para) ./doc/install-guide/section_neutron-ml2-network-node.xml:244(para) +#: ./doc/install-guide/section_neutron-ml2-network-node.xml:229(para) ./doc/install-guide/section_neutron-ml2-network-node.xml:245(para) msgid "To assist with troubleshooting, add verbose = True to the [DEFAULT] section in the /etc/neutron/dhcp_agent.ini file." msgstr "" -#: ./doc/install-guide/section_neutron-ml2-network-node.xml:235(para) +#: ./doc/install-guide/section_neutron-ml2-network-node.xml:236(para) msgid "Edit the /etc/neutron/dhcp_agent.ini file and add the following keys to the [DEFAULT] section:" msgstr "" -#: ./doc/install-guide/section_neutron-ml2-network-node.xml:252(title) +#: ./doc/install-guide/section_neutron-ml2-network-node.xml:253(title) msgid "To configure the metadata agent" msgstr "" -#: ./doc/install-guide/section_neutron-ml2-network-node.xml:253(para) +#: ./doc/install-guide/section_neutron-ml2-network-node.xml:254(para) msgid "The metadata agent provides configuration information such as credentials for remote access to instances." msgstr "" -#: ./doc/install-guide/section_neutron-ml2-network-node.xml:258(para) ./doc/install-guide/section_neutron-ml2-network-node.xml:289(para) +#: ./doc/install-guide/section_neutron-ml2-network-node.xml:259(para) ./doc/install-guide/section_neutron-ml2-network-node.xml:290(para) msgid "Replace NEUTRON_PASS with the password you chose for the neutron user in the Identity service. Replace METADATA_SECRET with a suitable secret for the metadata proxy." msgstr "" -#: ./doc/install-guide/section_neutron-ml2-network-node.xml:276(replaceable) ./doc/install-guide/section_neutron-ml2-network-node.xml:302(replaceable) ./doc/install-guide/section_neutron-ml2-network-node.xml:324(replaceable) ./doc/install-guide/section_neutron-ml2-network-node.xml:336(replaceable) +#: ./doc/install-guide/section_neutron-ml2-network-node.xml:277(replaceable) ./doc/install-guide/section_neutron-ml2-network-node.xml:303(replaceable) ./doc/install-guide/section_neutron-ml2-network-node.xml:325(replaceable) ./doc/install-guide/section_neutron-ml2-network-node.xml:337(replaceable) msgid "METADATA_SECRET" msgstr "" -#: ./doc/install-guide/section_neutron-ml2-network-node.xml:278(para) ./doc/install-guide/section_neutron-ml2-network-node.xml:304(para) +#: ./doc/install-guide/section_neutron-ml2-network-node.xml:279(para) ./doc/install-guide/section_neutron-ml2-network-node.xml:305(para) msgid "To assist with troubleshooting, add verbose = True to the [DEFAULT] section in the /etc/neutron/metadata_agent.ini file." msgstr "" -#: ./doc/install-guide/section_neutron-ml2-network-node.xml:285(para) +#: ./doc/install-guide/section_neutron-ml2-network-node.xml:286(para) msgid "Edit the /etc/neutron/metadata_agent.ini file and add the following keys to the [DEFAULT] section:" msgstr "" -#: ./doc/install-guide/section_neutron-ml2-network-node.xml:312(para) +#: ./doc/install-guide/section_neutron-ml2-network-node.xml:313(para) msgid "Perform the next two steps on the controller node." msgstr "" -#: ./doc/install-guide/section_neutron-ml2-network-node.xml:317(para) +#: ./doc/install-guide/section_neutron-ml2-network-node.xml:318(para) msgid "On the controller node, configure Compute to use the metadata service:" msgstr "" -#: ./doc/install-guide/section_neutron-ml2-network-node.xml:319(para) ./doc/install-guide/section_neutron-ml2-network-node.xml:331(para) +#: ./doc/install-guide/section_neutron-ml2-network-node.xml:320(para) ./doc/install-guide/section_neutron-ml2-network-node.xml:332(para) msgid "Replace METADATA_SECRET with the secret you chose for the metadata proxy." msgstr "" -#: ./doc/install-guide/section_neutron-ml2-network-node.xml:327(para) +#: ./doc/install-guide/section_neutron-ml2-network-node.xml:328(para) msgid "On the controller node, edit the /etc/nova/nova.conf file and add the following keys to the [DEFAULT] section:" msgstr "" -#: ./doc/install-guide/section_neutron-ml2-network-node.xml:339(para) +#: ./doc/install-guide/section_neutron-ml2-network-node.xml:340(para) msgid "On the controller node, restart the Compute API service:" msgstr "" -#: ./doc/install-guide/section_neutron-ml2-network-node.xml:347(para) +#: ./doc/install-guide/section_neutron-ml2-network-node.xml:348(para) msgid "The ML2 plug-in uses the Open vSwitch (OVS) mechanism (agent) to build virtual networking framework for instances." msgstr "" -#: ./doc/install-guide/section_neutron-ml2-network-node.xml:352(para) +#: ./doc/install-guide/section_neutron-ml2-network-node.xml:353(para) msgid "Replace INSTANCE_TUNNELS_INTERFACE_IP_ADDRESS with the IP address of the instance tunnels network interface on your network node. This guide uses 10.0.1.21 for the IP address of the instance tunnels network interface on the network node." msgstr "" -#: ./doc/install-guide/section_neutron-ml2-network-node.xml:378(para) +#: ./doc/install-guide/section_neutron-ml2-network-node.xml:379(para) msgid "Edit the /etc/neutron/plugins/ml2/ml2_conf.ini file." msgstr "" -#: ./doc/install-guide/section_neutron-ml2-network-node.xml:395(para) +#: ./doc/install-guide/section_neutron-ml2-network-node.xml:396(para) msgid "Replace INSTANCE_TUNNELS_INTERFACE_IP_ADDRESS with the IP address of the instance tunnels network interface on your network node." msgstr "" -#: ./doc/install-guide/section_neutron-ml2-network-node.xml:414(para) +#: ./doc/install-guide/section_neutron-ml2-network-node.xml:415(para) msgid "The OVS service provides the underlying virtual networking framework for instances. The integration bridge br-int handles internal instance network traffic within OVS. The external bridge br-ex handles external instance network traffic within OVS. The external bridge requires a port on the physical external network interface to provide instances with external network access. In essence, this port bridges the virtual and physical external networks in your environment." msgstr "" -#: ./doc/install-guide/section_neutron-ml2-network-node.xml:444(para) +#: ./doc/install-guide/section_neutron-ml2-network-node.xml:445(para) msgid "Add the external bridge:" msgstr "" -#: ./doc/install-guide/section_neutron-ml2-network-node.xml:448(para) +#: ./doc/install-guide/section_neutron-ml2-network-node.xml:449(para) msgid "Add a port to the external bridge that connects to the physical external network interface:" msgstr "" -#: ./doc/install-guide/section_neutron-ml2-network-node.xml:455(para) +#: ./doc/install-guide/section_neutron-ml2-network-node.xml:456(para) msgid "Depending on your network interface driver, you may need to disable Generic Receive Offload (GRO) to achieve suitable throughput between your instances and the external network." msgstr "" -#: ./doc/install-guide/section_neutron-ml2-network-node.xml:459(para) +#: ./doc/install-guide/section_neutron-ml2-network-node.xml:460(para) msgid "To temporarily disable GRO on the external network interface while testing your environment:" msgstr "" -#: ./doc/install-guide/section_neutron-ml2-network-node.xml:498(para) +#: ./doc/install-guide/section_neutron-ml2-network-node.xml:499(para) msgid "Start the Networking services and configure them to start when the system boots:" msgstr "" -#: ./doc/install-guide/section_neutron-ml2-network-node.xml:520(para) +#: ./doc/install-guide/section_neutron-ml2-network-node.xml:521(para) msgid "Restart the Networking services:" msgstr "" diff --git a/doc/install-guide/locale/ja.po b/doc/install-guide/locale/ja.po index 560e70c84e..bf1a0029d9 100644 --- a/doc/install-guide/locale/ja.po +++ b/doc/install-guide/locale/ja.po @@ -5,9 +5,9 @@ msgid "" msgstr "" "Project-Id-Version: OpenStack Manuals\n" -"POT-Creation-Date: 2014-07-31 21:35+0000\n" -"PO-Revision-Date: 2014-07-30 12:34+0000\n" -"Last-Translator: Tomoyuki KATO \n" +"POT-Creation-Date: 2014-08-03 23:07+0000\n" +"PO-Revision-Date: 2014-08-03 22:58+0000\n" +"Last-Translator: openstackjenkins \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" @@ -218,7 +218,6 @@ msgstr "[database] セクションに、データベースの #: ./doc/install-guide/section_ceilometer-install.xml240(replaceable) #: ./doc/install-guide/section_ceilometer-install.xml241(replaceable) #: ./doc/install-guide/section_basics-ntp.xml74(replaceable) -#: ./doc/install-guide/ch_clients.xml43(replaceable) #: ./doc/install-guide/section_nova-controller-install.xml72(replaceable) #: ./doc/install-guide/section_nova-controller-install.xml73(replaceable) #: ./doc/install-guide/section_nova-controller-install.xml74(replaceable) @@ -274,24 +273,24 @@ msgstr "[database] セクションに、データベースの #: ./doc/install-guide/section_trove-install.xml232(replaceable) #: ./doc/install-guide/section_trove-install.xml233(replaceable) #: ./doc/install-guide/section_trove-install.xml234(replaceable) -#: ./doc/install-guide/section_neutron-ml2-controller-node.xml50(replaceable) -#: ./doc/install-guide/section_neutron-ml2-controller-node.xml51(replaceable) -#: ./doc/install-guide/section_neutron-ml2-controller-node.xml52(replaceable) -#: ./doc/install-guide/section_neutron-ml2-controller-node.xml114(replaceable) -#: ./doc/install-guide/section_neutron-ml2-controller-node.xml127(replaceable) -#: ./doc/install-guide/section_neutron-ml2-controller-node.xml140(replaceable) -#: ./doc/install-guide/section_neutron-ml2-controller-node.xml142(replaceable) -#: ./doc/install-guide/section_neutron-ml2-controller-node.xml172(replaceable) -#: ./doc/install-guide/section_neutron-ml2-controller-node.xml173(replaceable) -#: ./doc/install-guide/section_neutron-ml2-controller-node.xml209(replaceable) -#: ./doc/install-guide/section_neutron-ml2-controller-node.xml222(replaceable) -#: ./doc/install-guide/section_neutron-ml2-controller-node.xml230(replaceable) -#: ./doc/install-guide/section_neutron-ml2-controller-node.xml249(replaceable) -#: ./doc/install-guide/section_neutron-ml2-controller-node.xml253(replaceable) -#: ./doc/install-guide/section_neutron-ml2-controller-node.xml366(replaceable) -#: ./doc/install-guide/section_neutron-ml2-controller-node.xml376(replaceable) -#: ./doc/install-guide/section_neutron-ml2-controller-node.xml400(replaceable) -#: ./doc/install-guide/section_neutron-ml2-controller-node.xml405(replaceable) +#: ./doc/install-guide/section_neutron-ml2-controller-node.xml53(replaceable) +#: ./doc/install-guide/section_neutron-ml2-controller-node.xml54(replaceable) +#: ./doc/install-guide/section_neutron-ml2-controller-node.xml55(replaceable) +#: ./doc/install-guide/section_neutron-ml2-controller-node.xml117(replaceable) +#: ./doc/install-guide/section_neutron-ml2-controller-node.xml130(replaceable) +#: ./doc/install-guide/section_neutron-ml2-controller-node.xml143(replaceable) +#: ./doc/install-guide/section_neutron-ml2-controller-node.xml145(replaceable) +#: ./doc/install-guide/section_neutron-ml2-controller-node.xml175(replaceable) +#: ./doc/install-guide/section_neutron-ml2-controller-node.xml176(replaceable) +#: ./doc/install-guide/section_neutron-ml2-controller-node.xml212(replaceable) +#: ./doc/install-guide/section_neutron-ml2-controller-node.xml225(replaceable) +#: ./doc/install-guide/section_neutron-ml2-controller-node.xml233(replaceable) +#: ./doc/install-guide/section_neutron-ml2-controller-node.xml252(replaceable) +#: ./doc/install-guide/section_neutron-ml2-controller-node.xml256(replaceable) +#: ./doc/install-guide/section_neutron-ml2-controller-node.xml369(replaceable) +#: ./doc/install-guide/section_neutron-ml2-controller-node.xml379(replaceable) +#: ./doc/install-guide/section_neutron-ml2-controller-node.xml403(replaceable) +#: ./doc/install-guide/section_neutron-ml2-controller-node.xml408(replaceable) #: ./doc/install-guide/section_nova-compute-install.xml38(replaceable) #: ./doc/install-guide/section_nova-compute-install.xml48(replaceable) #: ./doc/install-guide/section_nova-compute-install.xml60(replaceable) @@ -325,16 +324,16 @@ msgstr "[database] セクションに、データベースの #: ./doc/install-guide/section_heat-install.xml131(replaceable) #: ./doc/install-guide/section_heat-install.xml132(replaceable) #: ./doc/install-guide/section_heat-install.xml177(replaceable) -#: ./doc/install-guide/section_neutron-ml2-network-node.xml66(replaceable) -#: ./doc/install-guide/section_neutron-ml2-network-node.xml68(replaceable) -#: ./doc/install-guide/section_neutron-ml2-network-node.xml99(replaceable) +#: ./doc/install-guide/section_neutron-ml2-network-node.xml67(replaceable) +#: ./doc/install-guide/section_neutron-ml2-network-node.xml69(replaceable) #: ./doc/install-guide/section_neutron-ml2-network-node.xml100(replaceable) -#: ./doc/install-guide/section_neutron-ml2-network-node.xml117(replaceable) -#: ./doc/install-guide/section_neutron-ml2-network-node.xml137(replaceable) -#: ./doc/install-guide/section_neutron-ml2-network-node.xml264(replaceable) -#: ./doc/install-guide/section_neutron-ml2-network-node.xml274(replaceable) -#: ./doc/install-guide/section_neutron-ml2-network-node.xml296(replaceable) -#: ./doc/install-guide/section_neutron-ml2-network-node.xml301(replaceable) +#: ./doc/install-guide/section_neutron-ml2-network-node.xml101(replaceable) +#: ./doc/install-guide/section_neutron-ml2-network-node.xml118(replaceable) +#: ./doc/install-guide/section_neutron-ml2-network-node.xml138(replaceable) +#: ./doc/install-guide/section_neutron-ml2-network-node.xml265(replaceable) +#: ./doc/install-guide/section_neutron-ml2-network-node.xml275(replaceable) +#: ./doc/install-guide/section_neutron-ml2-network-node.xml297(replaceable) +#: ./doc/install-guide/section_neutron-ml2-network-node.xml302(replaceable) #: ./doc/install-guide/section_ceilometer-glance.xml18(replaceable) #: ./doc/install-guide/section_ceilometer-glance.xml24(replaceable) #: ./doc/install-guide/section_keystone-services.xml56(replaceable) @@ -410,7 +409,7 @@ msgstr "Identity をカタログに登録します。" #: ./doc/install-guide/section_keystone-install.xml186(title) #: ./doc/install-guide/section_nova-controller-install.xml197(title) #: ./doc/install-guide/section_glance-install.xml211(title) -#: ./doc/install-guide/section_neutron-ml2-controller-node.xml419(title) +#: ./doc/install-guide/section_neutron-ml2-controller-node.xml422(title) #: ./doc/install-guide/section_nova-compute-install.xml140(title) #: ./doc/install-guide/section_heat-install.xml183(title) msgid "To finalize installation" @@ -739,14 +738,14 @@ msgstr "/etc/cinder/cinder.conf ファイルの [D #: ./doc/install-guide/section_trove-install.xml113(replaceable) #: ./doc/install-guide/section_trove-install.xml115(replaceable) #: ./doc/install-guide/section_trove-install.xml207(replaceable) -#: ./doc/install-guide/section_neutron-ml2-controller-node.xml194(replaceable) -#: ./doc/install-guide/section_neutron-ml2-controller-node.xml210(replaceable) +#: ./doc/install-guide/section_neutron-ml2-controller-node.xml197(replaceable) +#: ./doc/install-guide/section_neutron-ml2-controller-node.xml213(replaceable) #: ./doc/install-guide/section_nova-compute-install.xml49(replaceable) #: ./doc/install-guide/section_neutron-ovs-controller-node.xml154(replaceable) #: ./doc/install-guide/section_neutron-ovs-controller-node.xml167(replaceable) #: ./doc/install-guide/section_heat-install.xml100(replaceable) -#: ./doc/install-guide/section_neutron-ml2-network-node.xml121(replaceable) -#: ./doc/install-guide/section_neutron-ml2-network-node.xml138(replaceable) +#: ./doc/install-guide/section_neutron-ml2-network-node.xml122(replaceable) +#: ./doc/install-guide/section_neutron-ml2-network-node.xml139(replaceable) #: ./doc/install-guide/section_ceilometer-glance.xml19(replaceable) #: ./doc/install-guide/section_ceilometer-glance.xml25(replaceable) #: ./doc/install-guide/section_basics-queue.xml58(replaceable) @@ -1198,7 +1197,6 @@ msgstr "demo ユーザーを作成します。" #: ./doc/install-guide/section_keystone-users.xml144(replaceable) #: ./doc/install-guide/section_keystone-verify.xml89(replaceable) #: ./doc/install-guide/section_keystone-verify.xml101(replaceable) -#: ./doc/install-guide/ch_clients.xml41(replaceable) #: ./doc/install-guide/section_keystone-openrc.xml36(replaceable) msgid "DEMO_PASS" msgstr "DEMO_PASS" @@ -1617,7 +1615,7 @@ msgid "" msgstr "外部インターフェースは、IP アドレスを割り当てない特別な設定を使用します。外部インターフェースとして 3 番目のインターフェースを設定します。" #: ./doc/install-guide/section_basics-networking-neutron.xml102(para) -#: ./doc/install-guide/section_neutron-ml2-network-node.xml450(para) +#: ./doc/install-guide/section_neutron-ml2-network-node.xml451(para) msgid "" "Replace INTERFACE_NAME with the actual interface " "name. For example, eth2 or ens256." @@ -1640,8 +1638,8 @@ msgstr "/etc/network/interfaces ファイルを編集し、 #: ./doc/install-guide/section_basics-networking-nova.xml101(replaceable) #: ./doc/install-guide/section_basics-networking-nova.xml102(replaceable) #: ./doc/install-guide/section_basics-networking-nova.xml112(replaceable) -#: ./doc/install-guide/section_neutron-ml2-network-node.xml453(replaceable) -#: ./doc/install-guide/section_neutron-ml2-network-node.xml461(replaceable) +#: ./doc/install-guide/section_neutron-ml2-network-node.xml454(replaceable) +#: ./doc/install-guide/section_neutron-ml2-network-node.xml462(replaceable) msgid "INTERFACE_NAME" msgstr "INTERFACE_NAME" @@ -2581,19 +2579,19 @@ msgstr "keystone 認証用に " -"client." -msgstr "以降のセクションには、OpenStack クライアントを利用するための情報があります。前のセクションで クライアントを使用したことを思い出してください。" - -#: ./doc/install-guide/ch_clients.xml11(para) -msgid "" -"You must install the client tools to complete the rest of the installation." -msgstr "残りのインストールを完了するために、クライアントツールをインストールする必要があります。" - -#: ./doc/install-guide/ch_clients.xml13(para) -msgid "" -"Configure the clients on your desktop rather than on the server so that you " -"have a similar experience to your users." -msgstr "ユーザーと同じように使用するために、サーバーではなく、デスクトップでクライアントを設定します。" - -#: ./doc/install-guide/ch_clients.xml21(title) -msgid "Create openrc.sh files" -msgstr "openrc.sh ファイルの作成" - -#: ./doc/install-guide/ch_clients.xml23(para) -msgid "" -"As explained in , use the credentials from " -" and create the following " -"PROJECT-openrc.sh files:" -msgstr " で説明したように、 にあるクレデンシャルを使用し、以下の PROJECT-openrc.shファイルを作成します。" - -#: ./doc/install-guide/ch_clients.xml33(para) -msgid "admin-openrc.sh for the administrative user" -msgstr "管理ユーザー用の admin-openrc.sh" - -#: ./doc/install-guide/ch_clients.xml38(para) -msgid "" -"demo-openrc.sh for the normal user: " -msgstr "一般ユーザー用の demo-openrc.sh: " - #: ./doc/install-guide/ch_basics.xml8(title) msgid "Basic environment configuration" msgstr "環境の基本設定" @@ -3478,8 +3433,8 @@ msgstr "nova ユーザーを作成します。" #: ./doc/install-guide/section_nova-controller-install.xml51(replaceable) #: ./doc/install-guide/section_nova-controller-install.xml127(replaceable) -#: ./doc/install-guide/section_neutron-ml2-controller-node.xml228(replaceable) -#: ./doc/install-guide/section_neutron-ml2-controller-node.xml252(replaceable) +#: ./doc/install-guide/section_neutron-ml2-controller-node.xml231(replaceable) +#: ./doc/install-guide/section_neutron-ml2-controller-node.xml255(replaceable) #: ./doc/install-guide/section_nova-compute-install.xml66(replaceable) msgid "NOVA_PASS" msgstr "NOVA_PASS" @@ -3545,12 +3500,12 @@ msgstr "[DEFAULT] セクションで、RabbitMQ< #: ./doc/install-guide/section_glance-install.xml113(para) #: ./doc/install-guide/section_neutron-ml2-compute-node.xml116(para) #: ./doc/install-guide/section_neutron-ml2-compute-node.xml128(para) -#: ./doc/install-guide/section_neutron-ml2-controller-node.xml184(para) -#: ./doc/install-guide/section_neutron-ml2-controller-node.xml203(para) +#: ./doc/install-guide/section_neutron-ml2-controller-node.xml187(para) +#: ./doc/install-guide/section_neutron-ml2-controller-node.xml206(para) #: ./doc/install-guide/section_nova-compute-install.xml50(para) #: ./doc/install-guide/section_heat-install.xml101(para) -#: ./doc/install-guide/section_neutron-ml2-network-node.xml111(para) -#: ./doc/install-guide/section_neutron-ml2-network-node.xml131(para) +#: ./doc/install-guide/section_neutron-ml2-network-node.xml112(para) +#: ./doc/install-guide/section_neutron-ml2-network-node.xml132(para) msgid "" "Replace RABBIT_PASS with the password you chose " "for the guest account in " @@ -3602,9 +3557,9 @@ msgstr "Compute のコントローラーのコンポーネントをインスト #: ./doc/install-guide/section_nova-controller-install.xml171(para) #: ./doc/install-guide/section_glance-install.xml189(para) #: ./doc/install-guide/section_neutron-ml2-compute-node.xml46(para) -#: ./doc/install-guide/section_neutron-ml2-controller-node.xml78(para) +#: ./doc/install-guide/section_neutron-ml2-controller-node.xml81(para) #: ./doc/install-guide/section_heat-install.xml156(para) -#: ./doc/install-guide/section_neutron-ml2-network-node.xml49(para) +#: ./doc/install-guide/section_neutron-ml2-network-node.xml50(para) msgid "" "Respond to prompts for database " "management, Identity " @@ -3615,7 +3570,7 @@ msgstr "データベース管理openvswitch-datapath-dkms パッケージを必要としません。" #: ./doc/install-guide/section_neutron-ml2-compute-node.xml37(para) -#: ./doc/install-guide/section_neutron-ml2-controller-node.xml65(para) -#: ./doc/install-guide/section_neutron-ml2-network-node.xml40(para) +#: ./doc/install-guide/section_neutron-ml2-controller-node.xml68(para) +#: ./doc/install-guide/section_neutron-ml2-network-node.xml41(para) msgid "SUSE does not use a separate ML2 plug-in package." msgstr "SUSE は ML2 プラグイン固有のパッケージを使用しません。" #: ./doc/install-guide/section_neutron-ml2-compute-node.xml42(title) -#: ./doc/install-guide/section_neutron-ml2-network-node.xml45(title) +#: ./doc/install-guide/section_neutron-ml2-network-node.xml46(title) msgid "To configure the Networking common components" msgstr "Networking 共通コンポーネントの設定方法" #: ./doc/install-guide/section_neutron-ml2-compute-node.xml43(para) -#: ./doc/install-guide/section_neutron-ml2-network-node.xml46(para) +#: ./doc/install-guide/section_neutron-ml2-network-node.xml47(para) msgid "" "The Networking common component configuration includes the authentication " "mechanism, message broker, and plug-in." @@ -4760,10 +4715,10 @@ msgstr "Networking 共通コンポーネントの設定には、認証機構、 #: ./doc/install-guide/section_neutron-ml2-compute-node.xml55(para) #: ./doc/install-guide/section_neutron-ml2-compute-node.xml78(para) -#: ./doc/install-guide/section_neutron-ml2-controller-node.xml132(para) -#: ./doc/install-guide/section_neutron-ml2-controller-node.xml155(para) -#: ./doc/install-guide/section_neutron-ml2-network-node.xml58(para) -#: ./doc/install-guide/section_neutron-ml2-network-node.xml81(para) +#: ./doc/install-guide/section_neutron-ml2-controller-node.xml135(para) +#: ./doc/install-guide/section_neutron-ml2-controller-node.xml158(para) +#: ./doc/install-guide/section_neutron-ml2-network-node.xml59(para) +#: ./doc/install-guide/section_neutron-ml2-network-node.xml82(para) msgid "Configure Networking to use the Identity service for authentication:" msgstr "Networking が認証用に Identity Service を使用するよう設定します。" @@ -4771,28 +4726,28 @@ msgstr "Networking が認証用に Identity Service を使用するよう設定 #: ./doc/install-guide/section_neutron-ml2-compute-node.xml100(para) #: ./doc/install-guide/section_neutron-ml2-compute-node.xml297(para) #: ./doc/install-guide/section_neutron-ml2-compute-node.xml312(para) -#: ./doc/install-guide/section_neutron-ml2-controller-node.xml134(para) -#: ./doc/install-guide/section_neutron-ml2-controller-node.xml167(para) -#: ./doc/install-guide/section_neutron-ml2-controller-node.xml360(para) -#: ./doc/install-guide/section_neutron-ml2-controller-node.xml394(para) -#: ./doc/install-guide/section_neutron-ml2-network-node.xml60(para) -#: ./doc/install-guide/section_neutron-ml2-network-node.xml94(para) +#: ./doc/install-guide/section_neutron-ml2-controller-node.xml137(para) +#: ./doc/install-guide/section_neutron-ml2-controller-node.xml170(para) +#: ./doc/install-guide/section_neutron-ml2-controller-node.xml363(para) +#: ./doc/install-guide/section_neutron-ml2-controller-node.xml397(para) +#: ./doc/install-guide/section_neutron-ml2-network-node.xml61(para) +#: ./doc/install-guide/section_neutron-ml2-network-node.xml95(para) msgid "" "Replace NEUTRON_PASS with the password you chose " "for the neutron user in the Identity service." msgstr "Identity で neutron ユーザー用に選択したパスワードで NEUTRON_PASS を置き換えます。" #: ./doc/install-guide/section_neutron-ml2-compute-node.xml82(para) -#: ./doc/install-guide/section_neutron-ml2-controller-node.xml159(para) -#: ./doc/install-guide/section_neutron-ml2-network-node.xml85(para) +#: ./doc/install-guide/section_neutron-ml2-controller-node.xml162(para) +#: ./doc/install-guide/section_neutron-ml2-network-node.xml86(para) msgid "" "Edit the /etc/neutron/neutron.conf file and add the " "following key to the [DEFAULT] section:" msgstr "/etc/neutron/neutron.conf ファイルを編集し、以下のキーを [DEFAULT] セクションに追加します。" #: ./doc/install-guide/section_neutron-ml2-compute-node.xml89(para) -#: ./doc/install-guide/section_neutron-ml2-controller-node.xml165(para) -#: ./doc/install-guide/section_neutron-ml2-network-node.xml92(para) +#: ./doc/install-guide/section_neutron-ml2-controller-node.xml168(para) +#: ./doc/install-guide/section_neutron-ml2-network-node.xml93(para) msgid "" "Add the following keys to the [keystone_authtoken] " "section:" @@ -4800,20 +4755,20 @@ msgstr "以下のキーを [keystone_authtoken] セクショ #: ./doc/install-guide/section_neutron-ml2-compute-node.xml107(para) #: ./doc/install-guide/section_neutron-ml2-compute-node.xml121(para) -#: ./doc/install-guide/section_neutron-ml2-controller-node.xml183(para) -#: ./doc/install-guide/section_neutron-ml2-controller-node.xml197(para) -#: ./doc/install-guide/section_neutron-ml2-network-node.xml110(para) -#: ./doc/install-guide/section_neutron-ml2-network-node.xml124(para) +#: ./doc/install-guide/section_neutron-ml2-controller-node.xml186(para) +#: ./doc/install-guide/section_neutron-ml2-controller-node.xml200(para) +#: ./doc/install-guide/section_neutron-ml2-network-node.xml111(para) +#: ./doc/install-guide/section_neutron-ml2-network-node.xml125(para) msgid "Configure Networking to use the message broker:" msgstr "Networking がメッセージブローカーを使用するよう設定します。" #: ./doc/install-guide/section_neutron-ml2-compute-node.xml124(para) #: ./doc/install-guide/section_neutron-ml2-compute-node.xml158(para) -#: ./doc/install-guide/section_neutron-ml2-controller-node.xml200(para) -#: ./doc/install-guide/section_neutron-ml2-controller-node.xml242(para) -#: ./doc/install-guide/section_neutron-ml2-controller-node.xml290(para) -#: ./doc/install-guide/section_neutron-ml2-network-node.xml127(para) -#: ./doc/install-guide/section_neutron-ml2-network-node.xml161(para) +#: ./doc/install-guide/section_neutron-ml2-controller-node.xml203(para) +#: ./doc/install-guide/section_neutron-ml2-controller-node.xml245(para) +#: ./doc/install-guide/section_neutron-ml2-controller-node.xml293(para) +#: ./doc/install-guide/section_neutron-ml2-network-node.xml128(para) +#: ./doc/install-guide/section_neutron-ml2-network-node.xml162(para) msgid "" "Edit the /etc/neutron/neutron.conf file and add the " "following keys to the [DEFAULT] section:" @@ -4821,10 +4776,10 @@ msgstr "/etc/neutron/neutron.conf ファイルを編集し #: ./doc/install-guide/section_neutron-ml2-compute-node.xml140(para) #: ./doc/install-guide/section_neutron-ml2-compute-node.xml154(para) -#: ./doc/install-guide/section_neutron-ml2-controller-node.xml272(para) -#: ./doc/install-guide/section_neutron-ml2-controller-node.xml286(para) -#: ./doc/install-guide/section_neutron-ml2-network-node.xml143(para) -#: ./doc/install-guide/section_neutron-ml2-network-node.xml157(para) +#: ./doc/install-guide/section_neutron-ml2-controller-node.xml275(para) +#: ./doc/install-guide/section_neutron-ml2-controller-node.xml289(para) +#: ./doc/install-guide/section_neutron-ml2-network-node.xml144(para) +#: ./doc/install-guide/section_neutron-ml2-network-node.xml158(para) msgid "" "Configure Networking to use the Modular Layer 2 (ML2) plug-in and associated" " services:" @@ -4832,8 +4787,8 @@ msgstr "Modular Layer 2 (ML2) プラグインと関連サービスを使用す #: ./doc/install-guide/section_neutron-ml2-compute-node.xml147(para) #: ./doc/install-guide/section_neutron-ml2-compute-node.xml168(para) -#: ./doc/install-guide/section_neutron-ml2-network-node.xml150(para) -#: ./doc/install-guide/section_neutron-ml2-network-node.xml171(para) +#: ./doc/install-guide/section_neutron-ml2-network-node.xml151(para) +#: ./doc/install-guide/section_neutron-ml2-network-node.xml172(para) msgid "" "To assist with troubleshooting, add verbose = True to the" " [DEFAULT] section in the " @@ -4841,8 +4796,8 @@ msgid "" msgstr "" #: ./doc/install-guide/section_neutron-ml2-compute-node.xml179(title) -#: ./doc/install-guide/section_neutron-ml2-controller-node.xml309(title) -#: ./doc/install-guide/section_neutron-ml2-network-node.xml346(title) +#: ./doc/install-guide/section_neutron-ml2-controller-node.xml312(title) +#: ./doc/install-guide/section_neutron-ml2-network-node.xml347(title) msgid "To configure the Modular Layer 2 (ML2) plug-in" msgstr "ML2 プラグインの設定方法" @@ -4854,8 +4809,8 @@ msgstr "ML2 プラグインは、インスタンスの仮想ネットワーク #: ./doc/install-guide/section_neutron-ml2-compute-node.xml194(replaceable) #: ./doc/install-guide/section_neutron-ml2-compute-node.xml234(replaceable) -#: ./doc/install-guide/section_neutron-ml2-network-node.xml367(replaceable) -#: ./doc/install-guide/section_neutron-ml2-network-node.xml401(replaceable) +#: ./doc/install-guide/section_neutron-ml2-network-node.xml368(replaceable) +#: ./doc/install-guide/section_neutron-ml2-network-node.xml402(replaceable) msgid "INSTANCE_TUNNELS_INTERFACE_IP_ADDRESS" msgstr "INSTANCE_TUNNELS_INTERFACE_IP_ADDRESS" @@ -4874,13 +4829,13 @@ msgid "" msgstr "/etc/neutron/plugins/ml2/ml2_conf.ini ファイルを編集し、以下のキーを [ml2] セクションに追加します。" #: ./doc/install-guide/section_neutron-ml2-compute-node.xml221(para) -#: ./doc/install-guide/section_neutron-ml2-network-node.xml388(para) +#: ./doc/install-guide/section_neutron-ml2-network-node.xml389(para) msgid "" "Add the following keys to the [ml2_type_gre] section:" msgstr "以下のキーを [ml2_type_gre] セクションに追加します。" #: ./doc/install-guide/section_neutron-ml2-compute-node.xml226(para) -#: ./doc/install-guide/section_neutron-ml2-network-node.xml393(para) +#: ./doc/install-guide/section_neutron-ml2-network-node.xml394(para) msgid "Add the [ovs] section and the following keys to it:" msgstr "[ovs] セクションを追加し、そこに以下のキーを追加します。" @@ -4892,15 +4847,15 @@ msgid "" msgstr "コンピュートノードのインスタンストンネルネットワークインターフェースの IP アドレスで INSTANCE_TUNNELS_INTERFACE_IP_ADDRESS を置き換えます。" #: ./doc/install-guide/section_neutron-ml2-compute-node.xml237(para) -#: ./doc/install-guide/section_neutron-ml2-controller-node.xml345(para) -#: ./doc/install-guide/section_neutron-ml2-network-node.xml404(para) +#: ./doc/install-guide/section_neutron-ml2-controller-node.xml348(para) +#: ./doc/install-guide/section_neutron-ml2-network-node.xml405(para) msgid "" "Add the [securitygroup] section and the following keys to" " it:" msgstr "[securitygroup] セクションを追加し、そこに以下のキーを追加します。" #: ./doc/install-guide/section_neutron-ml2-compute-node.xml246(title) -#: ./doc/install-guide/section_neutron-ml2-network-node.xml413(title) +#: ./doc/install-guide/section_neutron-ml2-network-node.xml414(title) msgid "To configure the Open vSwitch (OVS) service" msgstr "Open vSwitch (OVS) サービスの設定方法" @@ -4912,25 +4867,25 @@ msgstr "" #: ./doc/install-guide/section_neutron-ml2-compute-node.xml250(para) #: ./doc/install-guide/section_neutron-ml2-compute-node.xml256(para) -#: ./doc/install-guide/section_neutron-ml2-network-node.xml424(para) -#: ./doc/install-guide/section_neutron-ml2-network-node.xml430(para) +#: ./doc/install-guide/section_neutron-ml2-network-node.xml425(para) +#: ./doc/install-guide/section_neutron-ml2-network-node.xml431(para) msgid "Start the OVS service and configure it to start when the system boots:" msgstr "OVS サービスを起動し、システム起動時に起動するよう設定します。" #: ./doc/install-guide/section_neutron-ml2-compute-node.xml262(para) #: ./doc/install-guide/section_neutron-ml2-compute-node.xml266(para) -#: ./doc/install-guide/section_neutron-ml2-network-node.xml436(para) -#: ./doc/install-guide/section_neutron-ml2-network-node.xml440(para) +#: ./doc/install-guide/section_neutron-ml2-network-node.xml437(para) +#: ./doc/install-guide/section_neutron-ml2-network-node.xml441(para) msgid "Restart the OVS service:" msgstr "OVS サービスを再起動します。" #: ./doc/install-guide/section_neutron-ml2-compute-node.xml271(title) -#: ./doc/install-guide/section_neutron-ml2-controller-node.xml354(title) +#: ./doc/install-guide/section_neutron-ml2-controller-node.xml357(title) msgid "To configure Compute to use Networking" msgstr "Networking を使用するための Compute の設定方法" #: ./doc/install-guide/section_neutron-ml2-compute-node.xml272(para) -#: ./doc/install-guide/section_neutron-ml2-controller-node.xml355(para) +#: ./doc/install-guide/section_neutron-ml2-controller-node.xml358(para) msgid "" "By default, most distributions configure Compute to use legacy networking. " "You must reconfigure Compute to manage networks through Networking." @@ -4938,8 +4893,8 @@ msgstr "多くのディストリビューションは標準で、レガシーネ #: ./doc/install-guide/section_neutron-ml2-compute-node.xml301(para) #: ./doc/install-guide/section_neutron-ml2-compute-node.xml328(para) -#: ./doc/install-guide/section_neutron-ml2-controller-node.xml384(para) -#: ./doc/install-guide/section_neutron-ml2-controller-node.xml410(para) +#: ./doc/install-guide/section_neutron-ml2-controller-node.xml387(para) +#: ./doc/install-guide/section_neutron-ml2-controller-node.xml413(para) msgid "" "By default, Compute uses an internal firewall service. Since Networking " "includes a firewall service, you must disable the Compute firewall service " @@ -4948,19 +4903,19 @@ msgid "" msgstr "デフォルトで、Compute は内部ファイアウォールサービスを使用します。Networking がファイアウォールサービスを含むため、nova.virt.firewall.NoopFirewallDriver ファイアウォールドライバーを使用して、Compute のファイアウォールサービスを無効化する必要があります。" #: ./doc/install-guide/section_neutron-ml2-compute-node.xml309(para) -#: ./doc/install-guide/section_neutron-ml2-controller-node.xml392(para) +#: ./doc/install-guide/section_neutron-ml2-controller-node.xml395(para) msgid "" "Edit the /etc/nova/nova.conf and add the following keys" " to the [DEFAULT] section:" msgstr "/etc/nova/nova.conf ファイルを編集し、以下のキーを [DEFAULT] セクションに追加します。" #: ./doc/install-guide/section_neutron-ml2-compute-node.xml337(title) -#: ./doc/install-guide/section_neutron-ml2-network-node.xml466(title) +#: ./doc/install-guide/section_neutron-ml2-network-node.xml467(title) msgid "To finalize the installation" msgstr "インストールの最終手順" #: ./doc/install-guide/section_neutron-ml2-compute-node.xml339(para) -#: ./doc/install-guide/section_neutron-ml2-network-node.xml468(para) +#: ./doc/install-guide/section_neutron-ml2-network-node.xml469(para) msgid "" "The Networking service initialization scripts expect a symbolic link " "/etc/neutron/plugin.ini pointing to the configuration " @@ -4972,7 +4927,7 @@ msgstr "Networking のサービス初期化スクリプトは、選択したプ #. https://bugzilla.redhat.com/show_bug.cgi?id=1087647 #: ./doc/install-guide/section_neutron-ml2-compute-node.xml349(para) -#: ./doc/install-guide/section_neutron-ml2-network-node.xml478(para) +#: ./doc/install-guide/section_neutron-ml2-network-node.xml479(para) msgid "" "Due to a packaging bug, the Open vSwitch agent initialization script " "explicitly looks for the Open vSwitch plug-in configuration file rather than" @@ -4982,7 +4937,7 @@ msgid "" msgstr "パッケージ化のバグのため、Open vSwitch エージェントの初期化スクリプトは、ML2 プラグイン設定ファイルを指し示すシンボリックリンク /etc/neutron/plugin.ini ではなく、Open vSwitch プラグイン設定ファイルを明示的に検索します。この問題を解決するために、以下のコマンドを実行します。" #: ./doc/install-guide/section_neutron-ml2-compute-node.xml359(para) -#: ./doc/install-guide/section_neutron-ml2-network-node.xml488(para) +#: ./doc/install-guide/section_neutron-ml2-network-node.xml489(para) msgid "" "The Networking service initialization scripts expect the variable " "NEUTRON_PLUGIN_CONF in the " @@ -5567,7 +5522,7 @@ msgstr "基本的なインスタンスを起動するために必要なコンポ #. When image changes, this message will be marked fuzzy or untranslated for #. you. #. It doesn't matter what you translate it to: it's not used at all. -#: ./doc/install-guide/section_neutron-ml2-controller-node.xml97(None) +#: ./doc/install-guide/section_neutron-ml2-controller-node.xml100(None) msgid "" "@@image: 'figures/debconf-screenshots/neutron_1_plugin_selection.png'; " "md5=adf41c33778a691a560b7098908792db" @@ -5586,15 +5541,15 @@ msgid "" msgstr "データベースに root ユーザーとして接続し、neutron データベースを作成し、適切なアクセス権限を与えます。" #: ./doc/install-guide/section_neutron-ml2-controller-node.xml17(para) -#: ./doc/install-guide/section_neutron-ml2-controller-node.xml111(para) +#: ./doc/install-guide/section_neutron-ml2-controller-node.xml114(para) msgid "" "Replace NEUTRON_DBPASS with a suitable password." msgstr "NEUTRON_PASS を適切なパスワードに置き換えます。" #: ./doc/install-guide/section_neutron-ml2-controller-node.xml22(replaceable) #: ./doc/install-guide/section_neutron-ml2-controller-node.xml24(replaceable) -#: ./doc/install-guide/section_neutron-ml2-controller-node.xml114(replaceable) -#: ./doc/install-guide/section_neutron-ml2-controller-node.xml127(replaceable) +#: ./doc/install-guide/section_neutron-ml2-controller-node.xml117(replaceable) +#: ./doc/install-guide/section_neutron-ml2-controller-node.xml130(replaceable) #: ./doc/install-guide/section_neutron-ovs-controller-node.xml39(replaceable) #: ./doc/install-guide/section_neutron-ovs-controller-node.xml41(replaceable) #: ./doc/install-guide/section_neutron-ovs-controller-node.xml72(replaceable) @@ -5617,41 +5572,41 @@ msgid "" "address." msgstr "NEUTRON_PASS を適切なパスワードで置き換え、neutron@example.com を適切な電子メールアドレスに置き換えます。" -#: ./doc/install-guide/section_neutron-ml2-controller-node.xml34(replaceable) +#: ./doc/install-guide/section_neutron-ml2-controller-node.xml35(replaceable) #: ./doc/install-guide/section_neutron-ovs-controller-node.xml47(replaceable) msgid "neutron@example.com" msgstr "neutron@example.com" -#: ./doc/install-guide/section_neutron-ml2-controller-node.xml37(para) +#: ./doc/install-guide/section_neutron-ml2-controller-node.xml38(para) msgid "" "Link the neutron user to the service " "tenant and admin role:" msgstr "neutron ユーザーを service テナントおよび admin ロールにリンクします。" -#: ./doc/install-guide/section_neutron-ml2-controller-node.xml43(para) +#: ./doc/install-guide/section_neutron-ml2-controller-node.xml44(para) msgid "Create the neutron service:" msgstr "neutron サービスを作成します。" -#: ./doc/install-guide/section_neutron-ml2-controller-node.xml47(para) +#: ./doc/install-guide/section_neutron-ml2-controller-node.xml49(para) msgid "Create the service endpoint:" msgstr "サービスエンドポイントを作成します。" -#: ./doc/install-guide/section_neutron-ml2-controller-node.xml68(para) +#: ./doc/install-guide/section_neutron-ml2-controller-node.xml71(para) msgid "Debian does not use a separate ML2 plug-in package." msgstr "Debian は ML2 プラグイン固有のパッケージを使用しません。" -#: ./doc/install-guide/section_neutron-ml2-controller-node.xml73(title) +#: ./doc/install-guide/section_neutron-ml2-controller-node.xml76(title) msgid "To configure the Networking server component" msgstr "Networking サーバーコンポーネントの設定方法" -#: ./doc/install-guide/section_neutron-ml2-controller-node.xml74(para) +#: ./doc/install-guide/section_neutron-ml2-controller-node.xml77(para) msgid "" "The Networking server component configuration includes the database, " "authentication mechanism, message broker, topology change notifier, and " "plug-in." msgstr "Networking サーバーコンポーネントの設定には、データベース、認証機構、メッセージブローカー、トポロジー変更通知、プラグインがあります。" -#: ./doc/install-guide/section_neutron-ml2-controller-node.xml88(para) +#: ./doc/install-guide/section_neutron-ml2-controller-node.xml91(para) msgid "" "During the installation, you will also be prompted for which Networking " "plug-in to use. This will automatically fill the " @@ -5659,7 +5614,7 @@ msgid "" "/etc/neutron/neutron.conf file." msgstr "インストール中に、使用する Networking プラグインのプロンプトが表示されるでしょう。これにより、/etc/neutron/neutron.conf ファイルの ディレクティブが自動的に埋められます。" -#: ./doc/install-guide/section_neutron-ml2-controller-node.xml101(para) +#: ./doc/install-guide/section_neutron-ml2-controller-node.xml104(para) msgid "" "If the ML2 plug-in is selected, then the option" " will be filled with " @@ -5670,29 +5625,29 @@ msgid "" "appropriate values by default, so it is fine to not touch them." msgstr "ML2 プラグインを選択した場合、 オプションは neutron.plugins.ml2.plugin.Ml2Plugin になります。これは、ML2 プラグインの完全クラス名です。Debian の場合、今のところプラグインの短縮名を使用できません。 と のオプションは、デフォルトで適切な値が入力されるため、変更しないほうがいいです。" -#: ./doc/install-guide/section_neutron-ml2-controller-node.xml110(para) -#: ./doc/install-guide/section_neutron-ml2-controller-node.xml117(para) +#: ./doc/install-guide/section_neutron-ml2-controller-node.xml113(para) +#: ./doc/install-guide/section_neutron-ml2-controller-node.xml120(para) msgid "Configure Networking to use the database:" msgstr "Networking がデータベースに使用するよう設定します。" -#: ./doc/install-guide/section_neutron-ml2-controller-node.xml120(para) +#: ./doc/install-guide/section_neutron-ml2-controller-node.xml123(para) msgid "" "Edit the /etc/neutron/neutron.conf file and add the " "following key to the [database] section:" msgstr "/etc/neutron/neutron.conf ファイルを編集し、以下のキーを [database] セクションに追加します。" -#: ./doc/install-guide/section_neutron-ml2-controller-node.xml123(para) +#: ./doc/install-guide/section_neutron-ml2-controller-node.xml126(para) msgid "" "Replace NEUTRON_DBPASS with the password you " "chose for the database." msgstr "NEUTRON_PASS をデータベース用に選んだパスワードで置き換えます。" -#: ./doc/install-guide/section_neutron-ml2-controller-node.xml215(para) -#: ./doc/install-guide/section_neutron-ml2-controller-node.xml233(para) +#: ./doc/install-guide/section_neutron-ml2-controller-node.xml218(para) +#: ./doc/install-guide/section_neutron-ml2-controller-node.xml236(para) msgid "Configure Networking to notify Compute about network topology changes:" msgstr "ネットワークトポロジーの変更を Compute に通知するよう Networking を設定します。" -#: ./doc/install-guide/section_neutron-ml2-controller-node.xml235(para) +#: ./doc/install-guide/section_neutron-ml2-controller-node.xml238(para) msgid "" "Replace SERVICE_TENANT_ID with the " "service tenant identifier (id) in the Identity service " @@ -5700,16 +5655,16 @@ msgid "" " nova user in the Identity service." msgstr "Identity にある service テナント ID で SERVICE_TENANT_ID を置き換えます。Identity で nova ユーザー用に選択したパスワードで NOVA_PASS を置き換えます。" -#: ./doc/install-guide/section_neutron-ml2-controller-node.xml251(replaceable) +#: ./doc/install-guide/section_neutron-ml2-controller-node.xml254(replaceable) msgid "SERVICE_TENANT_ID" msgstr "SERVICE_TENANT_ID" -#: ./doc/install-guide/section_neutron-ml2-controller-node.xml257(para) +#: ./doc/install-guide/section_neutron-ml2-controller-node.xml260(para) msgid "To obtain the service tenant identifier (id):" msgstr "service テナント ID の取得方法:" -#: ./doc/install-guide/section_neutron-ml2-controller-node.xml279(para) -#: ./doc/install-guide/section_neutron-ml2-controller-node.xml299(para) +#: ./doc/install-guide/section_neutron-ml2-controller-node.xml282(para) +#: ./doc/install-guide/section_neutron-ml2-controller-node.xml302(para) msgid "" "We recommend adding verbose = True to the " "[DEFAULT] section in " @@ -5717,7 +5672,7 @@ msgid "" "troubleshooting." msgstr "トラブルシューティングに役立てるため、/etc/neutron/neutron.conf の [DEFAULT] セクションに verbose = True を追加することを推奨します。" -#: ./doc/install-guide/section_neutron-ml2-controller-node.xml310(para) +#: ./doc/install-guide/section_neutron-ml2-controller-node.xml313(para) msgid "" "The ML2 plug-in uses the Open vSwitch (OVS) mechanism (agent) to build the " "virtual networking framework for instances. However, the controller node " @@ -5725,22 +5680,22 @@ msgid "" "network traffic." msgstr "ML2 プラグインは、インスタンスの仮想ネットワークフレームワークを構築するために、Open vSwitch 機能 (エージェント) を使用します。しかしながら、コントローラーノードはインスタンスのネットワーク通信を処理しないため、OVS エージェントやサービスが必要ありません。" -#: ./doc/install-guide/section_neutron-ml2-controller-node.xml330(para) +#: ./doc/install-guide/section_neutron-ml2-controller-node.xml333(para) msgid "" "Edit the /etc/neutron/plugins/ml2/ml2_conf.ini file:" msgstr "/etc/neutron/plugins/ml2/ml2_conf.ini ファイルを編集します。" -#: ./doc/install-guide/section_neutron-ml2-controller-node.xml333(para) -#: ./doc/install-guide/section_neutron-ml2-network-node.xml381(para) +#: ./doc/install-guide/section_neutron-ml2-controller-node.xml336(para) +#: ./doc/install-guide/section_neutron-ml2-network-node.xml382(para) msgid "Add the following keys to the [ml2] section:" msgstr "以下のキーを [ml2] セクションに追加します。" -#: ./doc/install-guide/section_neutron-ml2-controller-node.xml340(para) +#: ./doc/install-guide/section_neutron-ml2-controller-node.xml343(para) msgid "" "Add the following key to the [ml2_type_gre] section:" msgstr "以下のキーを [ml2_type_gre] セクションに追加します。" -#: ./doc/install-guide/section_neutron-ml2-controller-node.xml421(para) +#: ./doc/install-guide/section_neutron-ml2-controller-node.xml424(para) msgid "" "The Networking service initialization scripts expect a symbolic link " "/etc/neutron/plugin.ini pointing to the configuration " @@ -5750,7 +5705,7 @@ msgid "" " link does not exist, create it using the following commands:" msgstr "Networking のサービス初期化スクリプトは、選択したプラグインと関連する設定ファイルを指し示すシンボリックリンク /etc/neutron/plugin.ini を予期しています。例えば、ML2 を使用する場合、シンボリックリンクが /etc/neutron/plugins/ml2/ml2_conf.ini を指し示す必要があります。このシンボリックリンクが存在しなければ、以下のコマンドを使用して作成します。" -#: ./doc/install-guide/section_neutron-ml2-controller-node.xml431(para) +#: ./doc/install-guide/section_neutron-ml2-controller-node.xml434(para) msgid "" "The Networking service initialization scripts expect the variable " "NEUTRON_PLUGIN_CONF in file " @@ -5759,14 +5714,14 @@ msgid "" "/etc/sysconfig/neutron file and add the following:" msgstr "Networking のサービス初期化スクリプトは、/etc/sysconfig/neutron ファイルの NEUTRON_PLUGIN_CONF 変数が、使用するプラグインに関連する設定ファイルを参照していることを想定します。例えば、ML2 を使用する場合、/etc/sysconfig/neutron ファイルを編集し、以下を追加します。" -#: ./doc/install-guide/section_neutron-ml2-controller-node.xml450(para) +#: ./doc/install-guide/section_neutron-ml2-controller-node.xml453(para) #: ./doc/install-guide/section_neutron-ovs-controller-node.xml324(para) msgid "" "Start the Networking service and configure it to start when the system " "boots:" msgstr "Networking サービスを起動し、システム起動時に起動するよう設定します。" -#: ./doc/install-guide/section_neutron-ml2-controller-node.xml458(para) +#: ./doc/install-guide/section_neutron-ml2-controller-node.xml461(para) msgid "Restart the Networking service:" msgstr "Networking のサービスを再起動します。" @@ -6564,72 +6519,72 @@ msgstr "ネットワークノードの設定" msgid "Edit /etc/sysctl.conf to contain the following:" msgstr "/etc/sysctl.conf を編集し、以下の内容を含めます。" -#: ./doc/install-guide/section_neutron-ml2-network-node.xml34(para) +#: ./doc/install-guide/section_neutron-ml2-network-node.xml35(para) msgid "" "Ubuntu installations using Linux kernel version 3.11 or newer do not require" " the openvswitch-datapath-dkms package." msgstr "Linux カーネル 3.11 以降の Ubuntu インストール環境は、openvswitch-datapath-dkms パッケージを必要としません。" -#: ./doc/install-guide/section_neutron-ml2-network-node.xml182(title) +#: ./doc/install-guide/section_neutron-ml2-network-node.xml183(title) msgid "To configure the Layer-3 (L3) agent" msgstr "L3 エージェントの設定方法" -#: ./doc/install-guide/section_neutron-ml2-network-node.xml183(para) +#: ./doc/install-guide/section_neutron-ml2-network-node.xml184(para) msgid "" "The Layer-3 (L3) agent provides routing services for " "instance virtual networks." msgstr "L3 エージェント は、インスタンスの仮想ネットワーク向けルーティングサービスを提供します。" -#: ./doc/install-guide/section_neutron-ml2-network-node.xml192(para) -#: ./doc/install-guide/section_neutron-ml2-network-node.xml207(para) +#: ./doc/install-guide/section_neutron-ml2-network-node.xml193(para) +#: ./doc/install-guide/section_neutron-ml2-network-node.xml208(para) msgid "" "To assist with troubleshooting, add verbose = True to the" " [DEFAULT] section in the " "/etc/neutron/l3_agent.ini file." msgstr "" -#: ./doc/install-guide/section_neutron-ml2-network-node.xml199(para) +#: ./doc/install-guide/section_neutron-ml2-network-node.xml200(para) msgid "" "Edit the /etc/neutron/l3_agent.ini file and add the " "following keys to the [DEFAULT] section:" msgstr "/etc/neutron/l3_agent.ini ファイルを編集し、以下のキーを [DEFAULT] セクションに追加します。" -#: ./doc/install-guide/section_neutron-ml2-network-node.xml215(title) +#: ./doc/install-guide/section_neutron-ml2-network-node.xml216(title) msgid "To configure the DHCP agent" msgstr "DHCP エージェントの設定方法" -#: ./doc/install-guide/section_neutron-ml2-network-node.xml216(para) +#: ./doc/install-guide/section_neutron-ml2-network-node.xml217(para) msgid "" "The DHCP agent provides DHCP " "services for instance virtual networks." msgstr "DHCP エージェント はインスタンスの仮想ネットワーク向け DHCP サービスを提供します。" -#: ./doc/install-guide/section_neutron-ml2-network-node.xml228(para) -#: ./doc/install-guide/section_neutron-ml2-network-node.xml244(para) +#: ./doc/install-guide/section_neutron-ml2-network-node.xml229(para) +#: ./doc/install-guide/section_neutron-ml2-network-node.xml245(para) msgid "" "To assist with troubleshooting, add verbose = True to the" " [DEFAULT] section in the " "/etc/neutron/dhcp_agent.ini file." msgstr "" -#: ./doc/install-guide/section_neutron-ml2-network-node.xml235(para) +#: ./doc/install-guide/section_neutron-ml2-network-node.xml236(para) msgid "" "Edit the /etc/neutron/dhcp_agent.ini file and add the " "following keys to the [DEFAULT] section:" msgstr "/etc/neutron/dhcp_agent.ini ファイルを編集し、以下のキーを [DEFAULT] セクションに追加します。" -#: ./doc/install-guide/section_neutron-ml2-network-node.xml252(title) +#: ./doc/install-guide/section_neutron-ml2-network-node.xml253(title) msgid "To configure the metadata agent" msgstr "メタデータエージェントの設定方法" -#: ./doc/install-guide/section_neutron-ml2-network-node.xml253(para) +#: ./doc/install-guide/section_neutron-ml2-network-node.xml254(para) msgid "" "The metadata agent provides configuration information" " such as credentials for remote access to instances." msgstr "メタデータエージェントは、インスタンスへのリモートアクセス用の設定情報を提供します。" -#: ./doc/install-guide/section_neutron-ml2-network-node.xml258(para) -#: ./doc/install-guide/section_neutron-ml2-network-node.xml289(para) +#: ./doc/install-guide/section_neutron-ml2-network-node.xml259(para) +#: ./doc/install-guide/section_neutron-ml2-network-node.xml290(para) msgid "" "Replace NEUTRON_PASS with the password you chose " "for the neutron user in the Identity service. Replace " @@ -6637,65 +6592,65 @@ msgid "" "metadata proxy." msgstr "Identity で neutron ユーザー用に選択したパスワードで NEUTRON_PASS を置き換えます。METADATA_SECRET をメタデータプロキシ用の適切なシークレットで置き換えます。" -#: ./doc/install-guide/section_neutron-ml2-network-node.xml276(replaceable) -#: ./doc/install-guide/section_neutron-ml2-network-node.xml302(replaceable) -#: ./doc/install-guide/section_neutron-ml2-network-node.xml324(replaceable) -#: ./doc/install-guide/section_neutron-ml2-network-node.xml336(replaceable) +#: ./doc/install-guide/section_neutron-ml2-network-node.xml277(replaceable) +#: ./doc/install-guide/section_neutron-ml2-network-node.xml303(replaceable) +#: ./doc/install-guide/section_neutron-ml2-network-node.xml325(replaceable) +#: ./doc/install-guide/section_neutron-ml2-network-node.xml337(replaceable) msgid "METADATA_SECRET" msgstr "METADATA_SECRET" -#: ./doc/install-guide/section_neutron-ml2-network-node.xml278(para) -#: ./doc/install-guide/section_neutron-ml2-network-node.xml304(para) +#: ./doc/install-guide/section_neutron-ml2-network-node.xml279(para) +#: ./doc/install-guide/section_neutron-ml2-network-node.xml305(para) msgid "" "To assist with troubleshooting, add verbose = True to the" " [DEFAULT] section in the " "/etc/neutron/metadata_agent.ini file." msgstr "" -#: ./doc/install-guide/section_neutron-ml2-network-node.xml285(para) +#: ./doc/install-guide/section_neutron-ml2-network-node.xml286(para) msgid "" "Edit the /etc/neutron/metadata_agent.ini file and add " "the following keys to the [DEFAULT] section:" msgstr "/etc/neutron/metadata_agent.ini ファイルを編集し、以下のキーを [DEFAULT] セクションに追加します。" -#: ./doc/install-guide/section_neutron-ml2-network-node.xml312(para) +#: ./doc/install-guide/section_neutron-ml2-network-node.xml313(para) msgid "" "Perform the next two steps on the controller node." msgstr "コントローラーノードで次の 2 つの手順を実行します。" -#: ./doc/install-guide/section_neutron-ml2-network-node.xml317(para) +#: ./doc/install-guide/section_neutron-ml2-network-node.xml318(para) msgid "" "On the controller node, configure Compute to use the " "metadata service:" msgstr "コントローラーノードで、メタデータサービスを使用するよう Compute を設定します。" -#: ./doc/install-guide/section_neutron-ml2-network-node.xml319(para) -#: ./doc/install-guide/section_neutron-ml2-network-node.xml331(para) +#: ./doc/install-guide/section_neutron-ml2-network-node.xml320(para) +#: ./doc/install-guide/section_neutron-ml2-network-node.xml332(para) msgid "" "Replace METADATA_SECRET with the secret you chose" " for the metadata proxy." msgstr "メタデータプロキシ用に選択した適切なシークレットで METADATA_SECRET を置き換えます。" -#: ./doc/install-guide/section_neutron-ml2-network-node.xml327(para) +#: ./doc/install-guide/section_neutron-ml2-network-node.xml328(para) msgid "" "On the controller node, edit the " "/etc/nova/nova.conf file and add the following keys to " "the [DEFAULT] section:" msgstr "コントローラーノードで、/etc/nova/nova.conf ファイルを編集し、以下のキーを [DEFAULT] セクションに追加します。" -#: ./doc/install-guide/section_neutron-ml2-network-node.xml339(para) +#: ./doc/install-guide/section_neutron-ml2-network-node.xml340(para) msgid "" "On the controller node, restart the Compute " "API service:" msgstr "コントローラーノードで、Compute API サービスを再起動します。" -#: ./doc/install-guide/section_neutron-ml2-network-node.xml347(para) +#: ./doc/install-guide/section_neutron-ml2-network-node.xml348(para) msgid "" "The ML2 plug-in uses the Open vSwitch (OVS) mechanism (agent) to build " "virtual networking framework for instances." msgstr "ML2 プラグインは、インスタンスの仮想ネットワークフレームワークを構築するために、Open vSwitch 機能 (エージェント) を使用します。" -#: ./doc/install-guide/section_neutron-ml2-network-node.xml352(para) +#: ./doc/install-guide/section_neutron-ml2-network-node.xml353(para) msgid "" "Replace INSTANCE_TUNNELS_INTERFACE_IP_ADDRESS " "with the IP address of the instance tunnels network interface on your " @@ -6703,19 +6658,19 @@ msgid "" "address of the instance tunnels network interface on the network node." msgstr "ネットワークノードのインスタンストンネルネットワークインターフェースの IP アドレスで INSTANCE_TUNNELS_INTERFACE_IP_ADDRESS を置き換えます。このガイドは、ネットワークノードのインスタンストンネルネットワークインターフェースの IP アドレスに 10.0.1.21 を使用します。" -#: ./doc/install-guide/section_neutron-ml2-network-node.xml378(para) +#: ./doc/install-guide/section_neutron-ml2-network-node.xml379(para) msgid "" "Edit the /etc/neutron/plugins/ml2/ml2_conf.ini file." msgstr "/etc/neutron/plugins/ml2/ml2_conf.ini ファイルを編集します。" -#: ./doc/install-guide/section_neutron-ml2-network-node.xml395(para) +#: ./doc/install-guide/section_neutron-ml2-network-node.xml396(para) msgid "" "Replace INSTANCE_TUNNELS_INTERFACE_IP_ADDRESS " "with the IP address of the instance tunnels network interface on your " "network node." msgstr "ネットワークノードのインスタンストンネルネットワークインターフェースの IP アドレスで INSTANCE_TUNNELS_INTERFACE_IP_ADDRESS を置き換えます。" -#: ./doc/install-guide/section_neutron-ml2-network-node.xml414(para) +#: ./doc/install-guide/section_neutron-ml2-network-node.xml415(para) msgid "" "The OVS service provides the underlying virtual networking framework for " "instances. The integration bridge br-int handles internal" @@ -6726,36 +6681,36 @@ msgid "" "bridges the virtual and physical external networks in your environment." msgstr "OVS サービスは、バックエンドの仮想ネットワークフレームワークをインスタンスに提供します。統合ブリッジ br-int は OVS 内のインスタンスの内部ネットワーク通信を処理します。外部ブリッジ br-ex は OVS 内のインスタンスの外部ネットワーク通信を処理します。外部ブリッジは、インスタンスに外部ネットワークアクセスを提供するために、外部物理ネットワークインターフェースにポートが必要です。このポートは本質的に、お使いの環境で仮想外部ネットワークと物理外部ネットワークをブリッジします。" -#: ./doc/install-guide/section_neutron-ml2-network-node.xml444(para) +#: ./doc/install-guide/section_neutron-ml2-network-node.xml445(para) msgid "Add the external bridge:" msgstr "外部ブリッジを追加します。" -#: ./doc/install-guide/section_neutron-ml2-network-node.xml448(para) +#: ./doc/install-guide/section_neutron-ml2-network-node.xml449(para) msgid "" "Add a port to the external bridge that connects to the physical external " "network interface:" msgstr "外部ネットワークの物理インターフェースに接続する外部ブリッジに、ポートを追加します。" -#: ./doc/install-guide/section_neutron-ml2-network-node.xml455(para) +#: ./doc/install-guide/section_neutron-ml2-network-node.xml456(para) msgid "" "Depending on your network interface driver, you may need to disable " "Generic Receive Offload (GRO) to achieve suitable " "throughput between your instances and the external network." msgstr "お使いのネットワークインターフェースドライバーによっては、インスタンスと外部ネットワーク間の適切なスループットを達成するために、GRO を無効化する必要があるかもしれません。" -#: ./doc/install-guide/section_neutron-ml2-network-node.xml459(para) +#: ./doc/install-guide/section_neutron-ml2-network-node.xml460(para) msgid "" "To temporarily disable GRO on the external network interface while testing " "your environment:" msgstr "環境のテスト中、外部ネットワークインターフェースで一時的に GRO を無効化する場合:" -#: ./doc/install-guide/section_neutron-ml2-network-node.xml498(para) +#: ./doc/install-guide/section_neutron-ml2-network-node.xml499(para) msgid "" "Start the Networking services and configure them to start when the system " "boots:" msgstr "Networking サービスを起動し、システム起動時に起動するよう設定します。" -#: ./doc/install-guide/section_neutron-ml2-network-node.xml520(para) +#: ./doc/install-guide/section_neutron-ml2-network-node.xml521(para) msgid "Restart the Networking services:" msgstr "Networking サービスを再起動します。"