openstack
/
openstack-manuals
Code Issues Proposed changes

Imported Translations from Transifex 

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

Change-Id: Id920e88e4778b9d0a4904ffa721fcfc8e00ad00d
This commit is contained in:
OpenStack Proposal Bot 2015-01-30 06:29:09 +00:00
parent 2a8e74e59f
commit f94b723c94
12 changed files with 11043 additions and 10448 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

242
doc/arch-design/locale/arch-design.pot
View File

@ -1,7 +1,7 @@
msgid ""
msgstr ""
"Project-Id-Version: PACKAGE VERSION\n"
"POT-Creation-Date: 2015-01-24 06:11+0000\n"
"POT-Creation-Date: 2015-01-30 06:27+0000\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
@ -887,7 +887,7 @@ msgstr ""
msgid "Some applications are tolerant of the lack of synchronized object storage, while others may need those objects to be replicated and available across regions. Understanding of how the cloud implementation impacts new and existing applications is important for risk mitigation and the overall success of a cloud project. Applications may have to be written to expect an infrastructure with little to no redundancy. Existing applications not developed with the cloud in mind may need to be rewritten."
msgstr ""
#: ./doc/arch-design/multi_site/section_user_requirements_multi_site.xml:139(title) ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:103(term) ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:263(term) ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:587(term) ./doc/arch-design/generalpurpose/section_user_requirements_general_purpose.xml:24(term) ./doc/arch-design/compute_focus/section_user_requirements_compute_focus.xml:20(term) ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:55(term) ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:174(term) ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:396(term) ./doc/arch-design/hybrid/section_user_requirements_hybrid.xml:19(term) ./doc/arch-design/storage_focus/section_architecture_storage_focus.xml:16(para) ./doc/arch-design/storage_focus/section_architecture_storage_focus.xml:40(term) ./doc/arch-design/storage_focus/section_architecture_storage_focus.xml:184(term) ./doc/arch-design/storage_focus/section_architecture_storage_focus.xml:417(term) ./doc/arch-design/storage_focus/section_user_requirements_storage_focus.xml:16(term)
#: ./doc/arch-design/multi_site/section_user_requirements_multi_site.xml:139(title) ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:103(term) ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:263(term) ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:587(term) ./doc/arch-design/generalpurpose/section_user_requirements_general_purpose.xml:24(term) ./doc/arch-design/compute_focus/section_user_requirements_compute_focus.xml:20(term) ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:56(term) ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:169(term) ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:391(term) ./doc/arch-design/hybrid/section_user_requirements_hybrid.xml:19(term) ./doc/arch-design/storage_focus/section_architecture_storage_focus.xml:16(para) ./doc/arch-design/storage_focus/section_architecture_storage_focus.xml:40(term) ./doc/arch-design/storage_focus/section_architecture_storage_focus.xml:184(term) ./doc/arch-design/storage_focus/section_architecture_storage_focus.xml:417(term) ./doc/arch-design/storage_focus/section_user_requirements_storage_focus.xml:16(term)
msgid "Cost"
msgstr ""
@ -1161,7 +1161,7 @@ msgstr ""
msgid "Depending on the storage model chosen during site design, storage replication and availability will also be a concern for end-users. If an application is capable of understanding regions, then it is possible to keep the object storage system separated by region. In this case, users who want to have an object available to more than one region will need to do the cross-site replication themselves. With a centralized swift proxy, however, the user may need to benchmark the replication timing of the Object Storage back end. Benchmarking allows the operational staff to provide users with an understanding of the amount of time required for a stored or modified object to become available to the entire environment."
msgstr ""
#: ./doc/arch-design/multi_site/section_tech_considerations_multi_site.xml:114(title) ./doc/arch-design/network_focus/section_tech_considerations_network_focus.xml:432(title) ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:391(term) ./doc/arch-design/generalpurpose/section_user_requirements_general_purpose.xml:120(term) ./doc/arch-design/generalpurpose/section_tech_considerations_general_purpose.xml:493(title) ./doc/arch-design/compute_focus/section_user_requirements_compute_focus.xml:96(term) ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:182(term) ./doc/arch-design/compute_focus/section_tech_considerations_compute_focus.xml:257(title) ./doc/arch-design/hybrid/section_tech_considerations_hybrid.xml:253(title) ./doc/arch-design/storage_focus/section_architecture_storage_focus.xml:19(para) ./doc/arch-design/storage_focus/section_architecture_storage_focus.xml:48(term) ./doc/arch-design/storage_focus/section_user_requirements_storage_focus.xml:105(term)
#: ./doc/arch-design/multi_site/section_tech_considerations_multi_site.xml:114(title) ./doc/arch-design/network_focus/section_tech_considerations_network_focus.xml:432(title) ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:391(term) ./doc/arch-design/generalpurpose/section_user_requirements_general_purpose.xml:120(term) ./doc/arch-design/generalpurpose/section_tech_considerations_general_purpose.xml:493(title) ./doc/arch-design/compute_focus/section_user_requirements_compute_focus.xml:96(term) ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:177(term) ./doc/arch-design/compute_focus/section_tech_considerations_compute_focus.xml:257(title) ./doc/arch-design/hybrid/section_tech_considerations_hybrid.xml:253(title) ./doc/arch-design/storage_focus/section_architecture_storage_focus.xml:19(para) ./doc/arch-design/storage_focus/section_architecture_storage_focus.xml:48(term) ./doc/arch-design/storage_focus/section_user_requirements_storage_focus.xml:105(term)
msgid "Performance"
msgstr ""
@ -1177,7 +1177,7 @@ msgstr ""
msgid "Storage availability can also be impacted by the architecture of a multi-site deployment. A centralized Object Storage service requires more time for an object to be available to instances locally in regions where the object was not created. Some applications may need to be tuned to account for this effect. Block Storage does not currently have a method for replicating data across multiple regions, so applications that depend on available block storage will need to manually cope with this limitation by creating duplicate block storage entries in each region."
msgstr ""
#: ./doc/arch-design/multi_site/section_tech_considerations_multi_site.xml:139(title) ./doc/arch-design/network_focus/section_user_requirements_network_focus.xml:163(title) ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:634(term) ./doc/arch-design/generalpurpose/section_user_requirements_general_purpose.xml:191(term) ./doc/arch-design/generalpurpose/section_tech_considerations_general_purpose.xml:671(title) ./doc/arch-design/compute_focus/section_user_requirements_compute_focus.xml:160(term) ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:440(term) ./doc/arch-design/compute_focus/section_tech_considerations_compute_focus.xml:268(title) ./doc/arch-design/hybrid/section_tech_considerations_hybrid.xml:107(title) ./doc/arch-design/storage_focus/section_tech_considerations_storage_focus.xml:50(term) ./doc/arch-design/storage_focus/section_architecture_storage_focus.xml:471(term) ./doc/arch-design/storage_focus/section_user_requirements_storage_focus.xml:123(term)
#: ./doc/arch-design/multi_site/section_tech_considerations_multi_site.xml:139(title) ./doc/arch-design/network_focus/section_user_requirements_network_focus.xml:163(title) ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:634(term) ./doc/arch-design/generalpurpose/section_user_requirements_general_purpose.xml:191(term) ./doc/arch-design/generalpurpose/section_tech_considerations_general_purpose.xml:671(title) ./doc/arch-design/compute_focus/section_user_requirements_compute_focus.xml:160(term) ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:435(term) ./doc/arch-design/compute_focus/section_tech_considerations_compute_focus.xml:268(title) ./doc/arch-design/hybrid/section_tech_considerations_hybrid.xml:107(title) ./doc/arch-design/storage_focus/section_tech_considerations_storage_focus.xml:50(term) ./doc/arch-design/storage_focus/section_architecture_storage_focus.xml:471(term) ./doc/arch-design/storage_focus/section_user_requirements_storage_focus.xml:123(term)
msgid "Security"
msgstr ""
@ -1193,7 +1193,7 @@ msgstr ""
msgid "Just as tenants in a single-site deployment need isolation from each other, so do tenants in multi-site installations. The extra challenges in multi-site designs revolve around ensuring that tenant networks function across regions. Unfortunately, OpenStack Networking does not presently support a mechanism to provide this functionality, therefore an external system may be necessary to manage these mappings. Tenant networks may contain sensitive information requiring that this mapping be accurate and consistent to ensure that a tenant in one site does not connect to a different tenant in another site."
msgstr ""
#: ./doc/arch-design/multi_site/section_tech_considerations_multi_site.xml:169(title) ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:564(para) ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:671(title) ./doc/arch-design/generalpurpose/section_tech_considerations_general_purpose.xml:414(title) ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:371(para) ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:477(title) ./doc/arch-design/compute_focus/section_tech_considerations_compute_focus.xml:360(title) ./doc/arch-design/storage_focus/section_architecture_storage_focus.xml:394(para) ./doc/arch-design/storage_focus/section_architecture_storage_focus.xml:512(title)
#: ./doc/arch-design/multi_site/section_tech_considerations_multi_site.xml:169(title) ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:564(para) ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:671(title) ./doc/arch-design/generalpurpose/section_tech_considerations_general_purpose.xml:414(title) ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:366(para) ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:472(title) ./doc/arch-design/compute_focus/section_tech_considerations_compute_focus.xml:360(title) ./doc/arch-design/storage_focus/section_architecture_storage_focus.xml:394(para) ./doc/arch-design/storage_focus/section_architecture_storage_focus.xml:512(title)
msgid "OpenStack components"
msgstr ""
@ -1969,31 +1969,31 @@ msgstr ""
msgid "Server hardware is evaluated around four conflicting dimensions."
msgstr ""
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:79(term) ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:34(term) ./doc/arch-design/storage_focus/section_architecture_storage_focus.xml:160(term)
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:79(term) ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:35(term) ./doc/arch-design/storage_focus/section_architecture_storage_focus.xml:160(term)
msgid "Server density"
msgstr ""
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:81(para) ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:36(para) ./doc/arch-design/storage_focus/section_architecture_storage_focus.xml:162(para)
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:81(para) ./doc/arch-design/storage_focus/section_architecture_storage_focus.xml:162(para)
msgid "A measure of how many servers can fit into a given measure of physical space, such as a rack unit [U]."
msgstr ""
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:87(term) ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:41(term) ./doc/arch-design/storage_focus/section_architecture_storage_focus.xml:168(term)
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:87(term) ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:42(term) ./doc/arch-design/storage_focus/section_architecture_storage_focus.xml:168(term)
msgid "Resource capacity"
msgstr ""
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:89(para) ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:43(para) ./doc/arch-design/storage_focus/section_architecture_storage_focus.xml:170(para)
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:89(para) ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:44(para) ./doc/arch-design/storage_focus/section_architecture_storage_focus.xml:170(para)
msgid "The number of CPU cores, how much RAM, or how much storage a given server will deliver."
msgstr ""
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:95(term) ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:289(term) ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:48(term) ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:206(term) ./doc/arch-design/storage_focus/section_architecture_storage_focus.xml:76(term) ./doc/arch-design/storage_focus/section_architecture_storage_focus.xml:176(term)
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:95(term) ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:289(term) ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:49(term) ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:201(term) ./doc/arch-design/storage_focus/section_architecture_storage_focus.xml:76(term) ./doc/arch-design/storage_focus/section_architecture_storage_focus.xml:176(term)
msgid "Expandability"
msgstr ""
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:97(para) ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:50(para) ./doc/arch-design/storage_focus/section_architecture_storage_focus.xml:178(para)
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:97(para) ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:51(para) ./doc/arch-design/storage_focus/section_architecture_storage_focus.xml:178(para)
msgid "The number of additional resources that can be added to a server before it has reached its limit."
msgstr ""
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:105(para) ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:57(para)
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:105(para) ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:58(para)
msgid "The relative purchase price of the hardware weighted against the level of design effort needed to build the system."
msgstr ""
@ -2025,7 +2025,7 @@ msgstr ""
msgid "The best form factor for server hardware supporting a general purpose OpenStack cloud is driven by outside business and cost factors. No single reference architecture will apply to all implementations; the decision must flow from user requirements, technical considerations, and operational considerations. Here are some of the key factors that influence the selection of server hardware:"
msgstr ""
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:176(term) ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:129(term) ./doc/arch-design/storage_focus/section_architecture_storage_focus.xml:274(term)
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:176(term) ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:124(term) ./doc/arch-design/storage_focus/section_architecture_storage_focus.xml:274(term)
msgid "Instance density"
msgstr ""
@ -2033,7 +2033,7 @@ msgstr ""
msgid "Sizing is an important consideration for a general purpose OpenStack cloud. The expected or anticipated number of instances that each hypervisor can host is a common metric used in sizing the deployment. The selected server hardware needs to support the expected or anticipated instance density."
msgstr ""
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:188(term) ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:139(term) ./doc/arch-design/storage_focus/section_architecture_storage_focus.xml:284(term)
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:188(term) ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:134(term) ./doc/arch-design/storage_focus/section_architecture_storage_focus.xml:284(term)
msgid "Host density"
msgstr ""
@ -2081,7 +2081,7 @@ msgstr ""
msgid "Storage can be a significant portion of the overall system cost. For an organization that is concerned with vendor support, a commercial storage solution is advisable, although it comes with a higher price tag. If initial capital expenditure requires minimization, designing a system based on commodity hardware would apply. The trade-off is potentially higher support costs and a greater risk of incompatibility and interoperability issues."
msgstr ""
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:277(term) ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:525(term) ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:194(term) ./doc/arch-design/storage_focus/section_architecture_storage_focus.xml:62(term)
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:277(term) ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:525(term) ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:189(term) ./doc/arch-design/storage_focus/section_architecture_storage_focus.xml:62(term)
msgid "Scalability"
msgstr ""
@ -2105,7 +2105,7 @@ msgstr ""
msgid "This list expands upon the potential impacts for including a particular storage architecture (and corresponding storage hardware) into the design for a general purpose OpenStack cloud:"
msgstr ""
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:325(term) ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:512(term) ./doc/arch-design/introduction/section_methodology.xml:182(term) ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:242(term) ./doc/arch-design/storage_focus/section_architecture_storage_focus.xml:116(term)
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:325(term) ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:512(term) ./doc/arch-design/introduction/section_methodology.xml:182(term) ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:237(term) ./doc/arch-design/storage_focus/section_architecture_storage_focus.xml:116(term)
msgid "Connectivity"
msgstr ""
@ -2161,7 +2161,7 @@ msgstr ""
msgid "Object storage resource nodes have no requirements for hardware fault tolerance or RAID controllers. It is not necessary to plan for fault tolerance within the object storage hardware because the object storage service provides replication between zones as a feature of the service. Block storage nodes, compute nodes and cloud controllers should all have fault tolerance built in at the hardware level by making use of hardware RAID controllers and varying levels of RAID configuration. The level of RAID chosen should be consistent with the performance and availability requirements of the cloud."
msgstr ""
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:428(title) ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:286(title)
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:428(title) ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:281(title)
msgid "Selecting networking hardware"
msgstr ""
@ -2173,19 +2173,19 @@ msgstr ""
msgid "There are more subtle design impacts that need to be considered. The selection of certain networking hardware (and the networking software) affects the management tools that can be used. There are exceptions to this; the rise of \"open\" networking software that supports a range of networking hardware means that there are instances where the relationship between networking hardware and networking software are not as tightly defined. An example of this type of software is Cumulus Linux, which is capable of running on a number of switch vendor's hardware solutions."
msgstr ""
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:446(para) ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:287(para) ./doc/arch-design/storage_focus/section_architecture_storage_focus.xml:315(para)
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:446(para) ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:282(para) ./doc/arch-design/storage_focus/section_architecture_storage_focus.xml:315(para)
msgid "Some of the key considerations that should be included in the selection of networking hardware include:"
msgstr ""
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:450(term) ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:291(term) ./doc/arch-design/storage_focus/section_architecture_storage_focus.xml:319(term)
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:450(term) ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:286(term) ./doc/arch-design/storage_focus/section_architecture_storage_focus.xml:319(term)
msgid "Port count"
msgstr ""
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:452(para) ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:293(para)
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:452(para) ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:288(para)
msgid "The design will require networking hardware that has the requisite port count."
msgstr ""
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:457(term) ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:298(term) ./doc/arch-design/storage_focus/section_architecture_storage_focus.xml:326(term)
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:457(term) ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:293(term) ./doc/arch-design/storage_focus/section_architecture_storage_focus.xml:326(term)
msgid "Port density"
msgstr ""
@ -2193,7 +2193,7 @@ msgstr ""
msgid "The network design will be affected by the physical space that is required to provide the requisite port count. A higher port density is preferred, as it leaves more rack space for compute or storage components that may be required by the design. This can also lead into concerns about fault domains and power density that should be considered. Higher density switches are more expensive and should also be considered, as it is important not to over design the network if it is not required."
msgstr ""
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:472(term) ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:313(term) ./doc/arch-design/storage_focus/section_architecture_storage_focus.xml:342(term)
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:472(term) ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:308(term) ./doc/arch-design/storage_focus/section_architecture_storage_focus.xml:342(term)
msgid "Port speed"
msgstr ""
@ -2201,7 +2201,7 @@ msgstr ""
msgid "The networking hardware must support the proposed network speed, for example: 1GbE, 10GbE, or 40GbE (or even 100GbE)."
msgstr ""
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:481(term) ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:321(term) ./doc/arch-design/storage_focus/section_architecture_storage_focus.xml:350(term)
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:481(term) ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:316(term) ./doc/arch-design/storage_focus/section_architecture_storage_focus.xml:350(term)
msgid "Redundancy"
msgstr ""
@ -2209,7 +2209,7 @@ msgstr ""
msgid "The level of network hardware redundancy required is influenced by the user requirements for high availability and cost considerations. Network redundancy can be achieved by adding redundant power supplies or paired switches. If this is a requirement, the hardware will need to support this configuration."
msgstr ""
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:492(term) ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:333(term) ./doc/arch-design/storage_focus/section_architecture_storage_focus.xml:363(term)
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:492(term) ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:328(term) ./doc/arch-design/storage_focus/section_architecture_storage_focus.xml:363(term)
msgid "Power requirements"
msgstr ""
@ -2241,7 +2241,7 @@ msgstr ""
msgid "To ensure that access to nodes within the cloud is not interrupted, we recommend that the network architecture identify any single points of failure and provide some level of redundancy or fault tolerance. With regard to the network infrastructure itself, this often involves use of networking protocols such as LACP, VRRP or others to achieve a highly available network connection. In addition, it is important to consider the networking implications on API availability. In order to ensure that the APIs, and potentially other services in the cloud are highly available, we recommend you design load balancing solution within the network architecture to accommodate for these requirements."
msgstr ""
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:556(title) ./doc/arch-design/generalpurpose/section_tech_considerations_general_purpose.xml:294(title) ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:363(title) ./doc/arch-design/storage_focus/section_architecture_storage_focus.xml:386(title)
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:556(title) ./doc/arch-design/generalpurpose/section_tech_considerations_general_purpose.xml:294(title) ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:358(title) ./doc/arch-design/storage_focus/section_architecture_storage_focus.xml:386(title)
msgid "Software selection"
msgstr ""
@ -2249,15 +2249,15 @@ msgstr ""
msgid "Software selection for a general purpose OpenStack architecture design needs to include these three areas:"
msgstr ""
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:561(para) ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:368(para) ./doc/arch-design/storage_focus/section_architecture_storage_focus.xml:391(para)
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:561(para) ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:363(para) ./doc/arch-design/storage_focus/section_architecture_storage_focus.xml:391(para)
msgid "Operating system (OS) and hypervisor"
msgstr ""
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:567(para) ./doc/arch-design/generalpurpose/section_tech_considerations_general_purpose.xml:454(title) ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:374(para) ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:529(title) ./doc/arch-design/storage_focus/section_architecture_storage_focus.xml:397(para) ./doc/arch-design/storage_focus/section_architecture_storage_focus.xml:562(title)
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:567(para) ./doc/arch-design/generalpurpose/section_tech_considerations_general_purpose.xml:454(title) ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:369(para) ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:524(title) ./doc/arch-design/storage_focus/section_architecture_storage_focus.xml:397(para) ./doc/arch-design/storage_focus/section_architecture_storage_focus.xml:562(title)
msgid "Supplemental software"
msgstr ""
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:572(title) ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:381(title) ./doc/arch-design/storage_focus/section_architecture_storage_focus.xml:403(title)
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:572(title) ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:376(title) ./doc/arch-design/storage_focus/section_architecture_storage_focus.xml:403(title)
msgid "Operating system and hypervisor"
msgstr ""
@ -2265,7 +2265,7 @@ msgstr ""
msgid "The operating system (OS) and hypervisor have a significant impact on the overall design. Selecting a particular operating system and hypervisor can directly affect server hardware selection. Make sure the storage hardware and topology support the selected operating system and hypervisor combination. Also ensure the networking hardware selection and topology will work with the chosen operating system and hypervisor combination. For example, if the design uses Link Aggregation Control Protocol (LACP), the OS and hypervisor both need to support it."
msgstr ""
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:583(para) ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:392(para) ./doc/arch-design/storage_focus/section_architecture_storage_focus.xml:413(para)
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:583(para) ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:387(para) ./doc/arch-design/storage_focus/section_architecture_storage_focus.xml:413(para)
msgid "Some areas that could be impacted by the selection of OS and hypervisor include:"
msgstr ""
@ -2273,7 +2273,7 @@ msgstr ""
msgid "Selecting a commercially supported hypervisor, such as Microsoft Hyper-V, will result in a different cost model rather than community-supported open source hypervisors including <glossterm baseform=\"kernel-based VM (KVM)\">KVM</glossterm>, Kinstance or <glossterm>Xen</glossterm>. When comparing open source OS solutions, choosing Ubuntu over Red Hat (or vice versa) will have an impact on cost due to support contracts."
msgstr ""
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:601(term) ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:409(term) ./doc/arch-design/storage_focus/section_architecture_storage_focus.xml:431(term)
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:601(term) ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:404(term) ./doc/arch-design/storage_focus/section_architecture_storage_focus.xml:431(term)
msgid "Supportability"
msgstr ""
@ -2281,15 +2281,15 @@ msgstr ""
msgid "Depending on the selected hypervisor, staff should have the appropriate training and knowledge to support the selected OS and hypervisor combination. If they do not, training will need to be provided which could have a cost impact on the design."
msgstr ""
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:612(term) ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:419(term) ./doc/arch-design/storage_focus/section_architecture_storage_focus.xml:448(term)
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:612(term) ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:414(term) ./doc/arch-design/storage_focus/section_architecture_storage_focus.xml:448(term)
msgid "Management tools"
msgstr ""
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:614(para) ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:421(para)
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:614(para) ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:416(para)
msgid "The management tools used for Ubuntu and Kinstance differ from the management tools for VMware vSphere. Although both OS and hypervisor combinations are supported by OpenStack, there will be very different impacts to the rest of the design as a result of the selection of one combination versus the other."
msgstr ""
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:624(term) ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:430(term) ./doc/arch-design/storage_focus/section_architecture_storage_focus.xml:460(term)
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:624(term) ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:425(term) ./doc/arch-design/storage_focus/section_architecture_storage_focus.xml:460(term)
msgid "Scale and performance"
msgstr ""
@ -2301,7 +2301,7 @@ msgstr ""
msgid "Ensure that the design can accommodate regular periodic installations of application security patches while maintaining required workloads. The frequency of security patches for the proposed OS-hypervisor combination will have an impact on performance and the patch installation process could affect maintenance windows."
msgstr ""
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:646(term) ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:451(term) ./doc/arch-design/storage_focus/section_architecture_storage_focus.xml:483(term)
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:646(term) ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:446(term) ./doc/arch-design/storage_focus/section_architecture_storage_focus.xml:483(term)
msgid "Supported features"
msgstr ""
@ -2309,7 +2309,7 @@ msgstr ""
msgid "Determine which features of OpenStack are required. This will often determine the selection of the OS-hypervisor combination. Some features are only available with specific OSs or hypervisors. For example, if certain features are not available, the design might need to be modified to meet the user requirements."
msgstr ""
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:657(term) ./doc/arch-design/generalpurpose/section_tech_considerations_general_purpose.xml:343(term) ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:462(term) ./doc/arch-design/storage_focus/section_architecture_storage_focus.xml:495(term)
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:657(term) ./doc/arch-design/generalpurpose/section_tech_considerations_general_purpose.xml:343(term) ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:457(term) ./doc/arch-design/storage_focus/section_architecture_storage_focus.xml:495(term)
msgid "Interoperability"
msgstr ""
@ -2333,7 +2333,7 @@ msgstr ""
msgid "While OpenStack is a fairly complete collection of software projects for building a platform for cloud services, there are invariably additional pieces of software that need to be considered in any given OpenStack design."
msgstr ""
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:692(title) ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:535(title) ./doc/arch-design/storage_focus/section_architecture_storage_focus.xml:568(title)
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:692(title) ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:530(title) ./doc/arch-design/storage_focus/section_architecture_storage_focus.xml:568(title)
msgid "Networking software"
msgstr ""
@ -2361,7 +2361,7 @@ msgstr ""
msgid "For a general purpose OpenStack cloud, the OpenStack infrastructure components need to be highly available. If the design does not include hardware load balancing, networking software packages like HAProxy will need to be included."
msgstr ""
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:727(title) ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:551(title) ./doc/arch-design/storage_focus/section_architecture_storage_focus.xml:585(title)
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:727(title) ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:546(title) ./doc/arch-design/storage_focus/section_architecture_storage_focus.xml:585(title)
msgid "Management software"
msgstr ""
@ -2381,15 +2381,15 @@ msgstr ""
msgid "If these software packages are required, the design must account for the additional resource consumption (CPU, RAM, storage, and network bandwidth). Some other potential design impacts include:"
msgstr ""
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:759(para) ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:578(para)
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:759(para) ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:573(para)
msgid "OS-hypervisor combination: Ensure that the selected logging, monitoring, or alerting tools support the proposed OS-hypervisor combination."
msgstr ""
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:764(para) ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:583(para) ./doc/arch-design/storage_focus/section_architecture_storage_focus.xml:625(para)
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:764(para) ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:578(para) ./doc/arch-design/storage_focus/section_architecture_storage_focus.xml:625(para)
msgid "Network hardware: The network hardware selection needs to be supported by the logging, monitoring, and alerting software."
msgstr ""
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:771(title) ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:589(title) ./doc/arch-design/storage_focus/section_architecture_storage_focus.xml:631(title)
#: ./doc/arch-design/generalpurpose/section_architecture_general_purpose.xml:771(title) ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:584(title) ./doc/arch-design/storage_focus/section_architecture_storage_focus.xml:631(title)
msgid "Database software"
msgstr ""
@ -3602,270 +3602,274 @@ msgid "The hardware selection covers three areas:"
msgstr ""
#: ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:21(para)
msgid "In a compute-focused OpenStack cloud the hardware selection must reflect the workloads being compute intensive. Compute-focused is defined as having extreme demands on processor and memory resources. The hardware selection for a compute-focused OpenStack architecture design must reflect this preference for compute-intensive workloads, as these workloads are not storage intensive, nor are they consistently network intensive. The network and storage may be heavily utilized while loading a data set into the computational cluster, but they are not otherwise intensive."
msgid "An OpenStack cloud with extreme demands on processor and memory resources is considered to be compute-focused, and requires hardware that can handle these demands. This can mean choosing hardware which might not perform as well on storage or network capabilities. In a compute- focused architecture, storage and networking are required while loading a data set into the computational cluster, but are not otherwise in heavy demand."
msgstr ""
#: ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:30(para) ./doc/arch-design/storage_focus/section_architecture_storage_focus.xml:156(para)
msgid "Compute (server) hardware must be evaluated against four opposing dimensions:"
#: ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:30(para)
msgid "Compute (server) hardware must be evaluated against four dimensions:"
msgstr ""
#: ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:62(para)
msgid "The dimensions need to be weighted against each other to determine the best design for the desired purpose. For example, increasing server density means sacrificing resource capacity or expandability. Increasing resource capacity and expandability can increase cost but decreases server density. Decreasing cost can mean decreasing supportability, server density, resource capacity, and expandability."
#: ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:37(para)
msgid "A measure of how many servers can fit into a given amount of physical space, such as a rack unit (U)."
msgstr ""
#: ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:68(para)
msgid "Selection of hardware for a compute-focused cloud should have an emphasis on server hardware that can offer more CPU sockets, more CPU cores, and more RAM; network connectivity and storage capacity are less critical. The hardware will need to be configured to provide enough network connectivity and storage capacity to meet minimum user requirements, but they are not the primary consideration."
#: ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:63(para)
msgid "The dimensions need to be weighed against each other to determine the best design for the desired purpose. For example, increasing server density means sacrificing resource capacity or expandability. Increasing resource capacity and expandability can increase cost but decreases server density. Decreasing cost can mean decreasing supportability, server density, resource capacity, and expandability."
msgstr ""
#: ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:74(para)
msgid "Some server hardware form factors are better suited than others, as CPU and RAM capacity have the highest priority."
#: ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:69(para)
msgid "A compute-focused cloud should have an emphasis on server hardware that can offer more CPU sockets, more CPU cores, and more RAM. Network connectivity and storage capacity are less critical. The hardware will need to be configured to provide enough network connectivity and storage capacity to meet minimum user requirements, but they are not the primary consideration."
msgstr ""
#: ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:78(para)
msgid "Most blade servers can support dual-socket multi-core CPUs. To avoid the limit means selecting \"full width\" or \"full height\" blades, which consequently loses server density. As an example, using high density blade servers including HP BladeSystem and Dell PowerEdge M1000e) which support up to 16 servers in only 10 rack units using half-height blades, suddenly decreases the density by 50% by selecting full-height blades resulting in only 8 servers per 10 rack units."
#: ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:75(para)
msgid "Some server hardware form factors are better suited than others, as CPU and RAM capacity have the highest priority. Some considerations for selecting hardware:"
msgstr ""
#: ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:88(para)
msgid "1U rack-mounted servers (servers that occupy only a single rack unit) may be able to offer greater server density than a blade server solution. It is possible to place 40 servers in a rack, providing space for the top of rack [ToR] switches, versus 32 \"full width\" or \"full height\" blade servers in a rack), but often are limited to dual-socket, multi-core CPU configurations. Note that, as of the Icehouse release, neither HP, IBM, nor Dell offered 1U rack servers with more than 2 CPU sockets. To obtain greater than dual-socket support in a 1U rack-mount form factor, customers need to buy their systems from Original Design Manufacturers (ODMs) or second-tier manufacturers. This may cause issues for organizations that have preferred vendor policies or concerns with support and hardware warranties of non-tier 1 vendors."
#: ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:80(para)
msgid "Most blade servers can support dual-socket multi-core CPUs. To avoid this CPU limit, select \"full width\" or \"full height\" blades, however this will also decrease the server density. For example, high density blade servers (like HP BladeSystem or Dell PowerEdge M1000e) which support up to 16 servers in only ten rack units. Using half-height blades is twice as dense as using full-height blades, which results in only eight servers per ten rack units."
msgstr ""
#: ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:103(para)
#: ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:89(para)
msgid "1U rack-mounted servers (servers that occupy only a single rack unit) may be able to offer greater server density than a blade server solution. It is possible to place forty 1U servers in a rack, providing space for the top of rack (ToR) switches, compared to 32 full width blade servers. However, as of the Icehouse release, 1U servers from the major vendors are limited to dual-socket, multi-core CPU configurations. To obtain greater than dual-socket support in a 1U rack-mount form factor, you will need to buy systems from original design (ODMs) or second-tier manufacturers."
msgstr ""
#: ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:100(para)
msgid "2U rack-mounted servers provide quad-socket, multi-core CPU support, but with a corresponding decrease in server density (half the density offered by 1U rack-mounted servers)."
msgstr ""
#: ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:108(para)
msgid "Larger rack-mounted servers, such as 4U servers, often provide even greater CPU capacity, commonly supporting four or even eight CPU sockets. These servers have greater expandability, but such servers have much lower server density and usually greater hardware cost."
#: ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:105(para)
msgid "Larger rack-mounted servers, such as 4U servers, often provide even greater CPU capacity, commonly supporting four or even eight CPU sockets. These servers have greater expandability, but such servers have much lower server density and are often more expensive."
msgstr ""
#: ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:115(para)
msgid "\"Sled servers\" (rack-mounted servers that support multiple independent servers in a single 2U or 3U enclosure) deliver increased density as compared to typical 1U or 2U rack-mounted servers. For example, many sled servers offer four independent dual-socket nodes in 2U for a total of 8 CPU sockets in 2U. However, the dual-socket limitation on individual nodes may not be sufficient to offset their additional cost and configuration complexity."
#: ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:111(para)
msgid "\"Sled servers\" (rack-mounted servers that support multiple independent servers in a single 2U or 3U enclosure) deliver increased density as compared to typical 1U or 2U rack-mounted servers. For example, many sled servers offer four independent dual-socket nodes in 2U for a total of eight CPU sockets in 2U. However, the dual-socket limitation on individual nodes may not be sufficient to offset their additional cost and configuration complexity."
msgstr ""
#: ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:124(para)
msgid "The following facts will strongly influence server hardware selection for a compute-focused OpenStack design architecture:"
#: ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:120(para)
msgid "Consider these facts when choosing server hardware for a compute- focused OpenStack design architecture:"
msgstr ""
#: ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:131(para)
msgid "In this architecture instance density is considered lower; therefore CPU and RAM over-subscription ratios are also lower. More hosts will be required to support the anticipated scale due to instance density being lower, especially if the design uses dual-socket hardware designs."
#: ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:126(para)
msgid "In a compute-focused architecture, instance density is lower, which means CPU and RAM over-subscription ratios are also lower. More hosts will be required to support the anticipated scale due to instance density being lower, especially if the design uses dual-socket hardware designs."
msgstr ""
#: ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:141(para)
#: ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:136(para)
msgid "Another option to address the higher host count that might be needed with dual socket designs is to use a quad socket platform. Taking this approach will decrease host density, which increases rack count. This configuration may affect the network requirements, the number of power connections, and possibly impact the cooling requirements."
msgstr ""
#: ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:150(term) ./doc/arch-design/storage_focus/section_architecture_storage_focus.xml:295(term)
#: ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:145(term) ./doc/arch-design/storage_focus/section_architecture_storage_focus.xml:295(term)
msgid "Power and cooling density"
msgstr ""
#: ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:152(para)
#: ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:147(para)
msgid "The power and cooling density requirements might be lower than with blade, sled, or 1U server designs because of lower host density (by using 2U, 3U or even 4U server designs). For data centers with older infrastructure, this may be a desirable feature."
msgstr ""
#: ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:160(para)
#: ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:155(para)
msgid "Compute-focused OpenStack design architecture server hardware selection results in a \"scale up\" versus \"scale out\" decision. Selecting a better solution, smaller number of larger hosts, or a larger number of smaller hosts depends on a combination of factors: cost, power, cooling, physical rack and floor space, support-warranty, and manageability."
msgstr ""
#: ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:167(title)
#: ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:162(title)
msgid "Storage hardware selection"
msgstr ""
#: ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:168(para)
#: ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:163(para)
msgid "For a compute-focused OpenStack design architecture, the selection of storage hardware is not critical as it is not primary criteria, however it is still important. There are a number of different factors that a cloud architect must consider:"
msgstr ""
#: ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:176(para)
#: ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:171(para)
msgid "The overall cost of the solution will play a major role in what storage architecture (and resulting storage hardware) is selected."
msgstr ""
#: ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:184(para)
#: ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:179(para)
msgid "The performance of the solution is also a big role and can be measured by observing the latency of storage I-O requests. In a compute-focused OpenStack cloud, storage latency can be a major consideration. In some compute-intensive workloads, minimizing the delays that the CPU experiences while fetching data from the storage can have a significant impact on the overall performance of the application."
msgstr ""
#: ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:196(para)
#: ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:191(para)
msgid "This section will refer to the term \"scalability\" to refer to how well the storage solution performs as it is expanded up to its maximum size. A storage solution that performs well in small configurations but has degrading performance as it expands would not be considered scalable. On the other hand, a solution that continues to perform well at maximum expansion would be considered scalable."
msgstr ""
#: ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:208(para)
#: ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:203(para)
msgid "Expandability refers to the overall ability of the solution to grow. A storage solution that expands to 50 PB is considered more expandable than a solution that only scales to 10PB. Note that this metric is related to, but different from, scalability, which is a measure of the solution's performance as it expands."
msgstr ""
#: ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:217(para)
#: ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:212(para)
msgid "For a compute-focused OpenStack cloud, latency of storage is a major consideration. Using solid-state disks (SSDs) to minimize latency for instance storage and reduce CPU delays caused by waiting for the storage will increase performance. Consider using RAID controller cards in compute hosts to improve the performance of the underlying disk subsystem."
msgstr ""
#: ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:223(para)
#: ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:218(para)
msgid "The selection of storage architecture, and the corresponding storage hardware (if there is the option), is determined by evaluating possible solutions against the key factors listed above. This will determine if a scale-out solution (such as Ceph, GlusterFS, or similar) should be used, or if a single, highly expandable and scalable centralized storage array would be a better choice. If a centralized storage array is the right fit for the requirements, the hardware will be determined by the array vendor. It is also possible to build a storage array using commodity hardware with Open Source software, but there needs to be access to people with expertise to build such a system. Conversely, a scale-out storage solution that uses direct-attached storage (DAS) in the servers may be an appropriate choice. If so, then the server hardware needs to be configured to support the storage solution."
msgstr ""
#: ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:237(para)
#: ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:232(para)
msgid "The following lists some of the potential impacts that may affect a particular storage architecture, and the corresponding storage hardware, of a compute-focused OpenStack cloud:"
msgstr ""
#: ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:244(para)
#: ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:239(para)
msgid "Based on the storage solution selected, ensure the connectivity matches the storage solution requirements. If a centralized storage array is selected, it is important to determine how the hypervisors will connect to the storage array. Connectivity could affect latency and thus performance, so check that the network characteristics will minimize latency to boost the overall performance of the design."
msgstr ""
#: ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:254(term) ./doc/arch-design/storage_focus/section_architecture_storage_focus.xml:130(term)
#: ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:249(term) ./doc/arch-design/storage_focus/section_architecture_storage_focus.xml:130(term)
msgid "Latency"
msgstr ""
#: ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:256(para) ./doc/arch-design/storage_focus/section_architecture_storage_focus.xml:132(para)
#: ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:251(para) ./doc/arch-design/storage_focus/section_architecture_storage_focus.xml:132(para)
msgid "Determine if the use case will have consistent or highly variable latency."
msgstr ""
#: ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:261(term) ./doc/arch-design/storage_focus/section_architecture_storage_focus.xml:137(term)
#: ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:256(term) ./doc/arch-design/storage_focus/section_architecture_storage_focus.xml:137(term)
msgid "Throughput"
msgstr ""
#: ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:263(para)
#: ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:258(para)
msgid "To improve overall performance, make sure that the storage solution throughout is optimized. While it is not likely that a compute-focused cloud will have major data I-O to and from storage, this is an important factor to consider."
msgstr ""
#: ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:270(term)
#: ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:265(term)
msgid "Server Hardware"
msgstr ""
#: ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:272(para)
#: ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:267(para)
msgid "If the solution uses DAS, this impacts, and is not limited to, the server hardware choice that will ripple into host density, instance density, power density, OS-hypervisor, and management tools."
msgstr ""
#: ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:279(para)
#: ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:274(para)
msgid "Where instances need to be made highly available, or they need to be capable of migration between hosts, use of a shared storage file-system to store instance ephemeral data should be employed to ensure that compute services can run uninterrupted in the event of a node failure."
msgstr ""
#: ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:300(para)
#: ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:295(para)
msgid "The network design will be affected by the physical space that is required to provide the requisite port count. A switch that can provide 48 10 GbE ports in 1U has a much higher port density than a switch that provides 24 10 GbE ports in 2U. A higher port density is preferred, as it leaves more rack space for compute or storage components that might be required by the design. This also leads into concerns about fault domains and power density that must also be considered. Higher density switches are more expensive and should also be considered, as it is important not to over design the network if it is not required."
msgstr ""
#: ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:315(para)
#: ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:310(para)
msgid "The networking hardware must support the proposed network speed, for example: 1 GbE, 10 GbE, or 40 GbE (or even 100 GbE)."
msgstr ""
#: ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:323(para)
#: ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:318(para)
msgid "The level of network hardware redundancy required is influenced by the user requirements for high availability and cost considerations. Network redundancy can be achieved by adding redundant power supplies or paired switches. If this is a requirement, the hardware will need to support this configuration. User requirements will determine if a completely redundant network infrastructure is required."
msgstr ""
#: ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:335(para)
#: ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:330(para)
msgid "Ensure that the physical data center provides the necessary power for the selected network hardware. This is not an issue for top of rack (ToR) switches, but may be an issue for spine switches in a leaf and spine fabric, or end of row (EoR) switches."
msgstr ""
#: ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:343(para)
#: ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:338(para)
msgid "It is important to first understand additional factors as well as the use case because these additional factors heavily influence the cloud network architecture. Once these key considerations have been decided, the proper network can be designed to best serve the workloads being placed in the cloud."
msgstr ""
#: ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:348(para)
#: ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:343(para)
msgid "We recommend designing the network architecture using a scalable network model that makes it easy to add capacity and bandwidth. A good example of such a model is the leaf-spline model. In this type of network design, it is possible to easily add additional bandwidth as well as scale out to additional racks of gear. It is important to select network hardware that will support the required port count, port speed and port density while also allowing for future growth as workload demands increase. It is also important to evaluate where in the network architecture it is valuable to provide redundancy. Increased network availability and redundancy comes at a cost, therefore we recommend to weigh the cost versus the benefit gained from utilizing and deploying redundant network switches and using bonded interfaces at the host level."
msgstr ""
#: ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:364(para)
#: ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:359(para)
msgid "Selecting software to be included in a compute-focused OpenStack architecture design must include three main areas:"
msgstr ""
#: ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:377(para)
#: ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:372(para)
msgid "Design decisions made in each of these areas impact the rest of the OpenStack architecture design."
msgstr ""
#: ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:382(para)
#: ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:377(para)
msgid "The selection of operating system (OS) and hypervisor has a significant impact on the end point design. Selecting a particular operating system and hypervisor could affect server hardware selection. For example, a selected combination needs to be supported on the selected hardware. Ensuring the storage hardware selection and topology supports the selected operating system and hypervisor combination should also be considered. Additionally, make sure that the networking hardware selection and topology will work with the chosen operating system and hypervisor combination. For example, if the design uses Link Aggregation Control Protocol (LACP), the hypervisor needs to support it."
msgstr ""
#: ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:398(para)
#: ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:393(para)
msgid "Selecting a commercially supported hypervisor such as Microsoft Hyper-V will result in a different cost model rather than chosen a community-supported open source hypervisor like Kinstance or Xen. Even within the ranks of open source solutions, choosing Ubuntu over Red Hat (or vice versa) will have an impact on cost due to support contracts. On the other hand, business or application requirements might dictate a specific or commercially supported hypervisor."
msgstr ""
#: ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:411(para)
#: ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:406(para)
msgid "Depending on the selected hypervisor, the staff should have the appropriate training and knowledge to support the selected OS and hypervisor combination. If they do not, training will need to be provided which could have a cost impact on the design."
msgstr ""
#: ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:432(para)
#: ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:427(para)
msgid "Ensure that selected OS and hypervisor combinations meet the appropriate scale and performance requirements. The chosen architecture will need to meet the targeted instance-host ratios with the selected OS-hypervisor combination."
msgstr ""
#: ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:442(para)
#: ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:437(para)
msgid "Ensure that the design can accommodate the regular periodic installation of application security patches while maintaining the required workloads. The frequency of security patches for the proposed OS-hypervisor combination will have an impact on performance and the patch installation process could affect maintenance windows."
msgstr ""
#: ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:453(para) ./doc/arch-design/storage_focus/section_architecture_storage_focus.xml:485(para)
#: ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:448(para) ./doc/arch-design/storage_focus/section_architecture_storage_focus.xml:485(para)
msgid "Determine what features of OpenStack are required. This will often determine the selection of the OS-hypervisor combination. Certain features are only available with specific OSs or hypervisors. For example, if certain features are not available, the design might need to be modified to meet the user requirements."
msgstr ""
#: ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:464(para)
#: ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:459(para)
msgid "Consideration should be given to the ability of the selected OS-hypervisor combination to interoperate or co-exist with other OS-hypervisors, or other software solutions in the overall design (if required). Operational and troubleshooting tools for one OS-hypervisor combination may differ from the tools used for another OS-hypervisor combination and, as a result, the design will need to address if the two sets of tools need to interoperate."
msgstr ""
#: ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:478(para)
#: ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:473(para)
msgid "The selection of which OpenStack components will actually be included in the design and deployed has significant impact. There are certain components that will always be present, (Compute and Image Service, for example) yet there are other services that might not need to be present. For example, a certain design may not require the Orchestration module. Omitting Heat would not typically have a significant impact on the overall design. However, if the architecture uses a replacement for OpenStack Object Storage for its storage component, this could potentially have significant impacts on the rest of the design."
msgstr ""
#: ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:487(para)
#: ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:482(para)
msgid "For a compute-focused OpenStack design architecture, the following components would be used:"
msgstr ""
#: ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:491(para)
#: ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:486(para)
msgid "Identity (keystone)"
msgstr ""
#: ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:494(para)
#: ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:489(para)
msgid "Dashboard (horizon)"
msgstr ""
#: ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:497(para)
#: ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:492(para)
msgid "Compute (nova)"
msgstr ""
#: ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:500(para)
#: ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:495(para)
msgid "Object Storage (swift, ceph or a commercial solution)"
msgstr ""
#: ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:503(para)
#: ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:498(para)
msgid "Image (glance)"
msgstr ""
#: ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:506(para)
#: ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:501(para)
msgid "Networking (neutron)"
msgstr ""
#: ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:509(para)
#: ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:504(para)
msgid "Orchestration (heat)"
msgstr ""
#: ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:512(para)
#: ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:507(para)
msgid "OpenStack Block Storage would potentially not be incorporated into a compute-focused design due to persistent block storage not being a significant requirement for the types of workloads that would be deployed onto instances running in a compute-focused cloud. However, there may be some situations where the need for performance dictates that a block storage component be used to improve data I-O."
msgstr ""
#: ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:518(para)
#: ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:513(para)
msgid "The exclusion of certain OpenStack components might also limit or constrain the functionality of other components. If a design opts to include the Orchestration module but exclude the Telemetry module, then the design will not be able to take advantage of Orchestration's auto scaling functionality (which relies on information from Telemetry). Due to the fact that you can use Orchestration to spin up a large number of instances to perform the compute-intensive processing, including Orchestration in a compute-focused architecture design is strongly recommended."
msgstr ""
#: ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:530(para)
#: ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:525(para)
msgid "While OpenStack is a fairly complete collection of software projects for building a platform for cloud services, there are invariably additional pieces of software that might need to be added to any given OpenStack design."
msgstr ""
#: ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:536(para)
#: ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:531(para)
msgid "OpenStack Networking provides a wide variety of networking services for instances. There are many additional networking software packages that might be useful to manage the OpenStack components themselves. Some examples include software to provide load balancing, network redundancy protocols, and routing daemons. Some of these software packages are described in more detail in the <citetitle>OpenStack High Availability Guide</citetitle> (<link href=\"http://docs.openstack.org/high-availability-guide/content\">http://docs.openstack.org/high-availability-guide/content</link>)."
msgstr ""
#: ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:545(para)
#: ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:540(para)
msgid "For a compute-focused OpenStack cloud, the OpenStack infrastructure components will need to be highly available. If the design does not include hardware load balancing, networking software packages like HAProxy will need to be included."
msgstr ""
#: ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:552(para)
#: ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:547(para)
msgid "The selected supplemental software solution impacts and affects the overall OpenStack cloud design. This includes software for providing clustering, logging, monitoring and alerting."
msgstr ""
#: ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:555(para)
#: ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:550(para)
msgid "Inclusion of clustering Software, such as Corosync or Pacemaker, is determined primarily by the availability design requirements. Therefore, the impact of including (or not including) these software packages is primarily determined by the availability of the cloud infrastructure and the complexity of supporting the configuration after it is deployed. The OpenStack High Availability Guide provides more details on the installation and configuration of Corosync and Pacemaker, should these packages need to be included in the design."
msgstr ""
#: ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:563(para)
#: ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:558(para)
msgid "Requirements for logging, monitoring, and alerting are determined by operational considerations. Each of these sub-categories includes a number of various options. For example, in the logging sub-category one might consider Logstash, Splunk, Log Insight, or some other log aggregation-consolidation tool. Logs should be stored in a centralized location to make it easier to perform analytics against the data. Log data analytics engines can also provide automation and issue notification by providing a mechanism to both alert and automatically attempt to remediate some of the more commonly known issues."
msgstr ""
#: ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:572(para) ./doc/arch-design/storage_focus/section_architecture_storage_focus.xml:613(para)
#: ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:567(para) ./doc/arch-design/storage_focus/section_architecture_storage_focus.xml:613(para)
msgid "If any of these software packages are needed, then the design must account for the additional resource consumption (CPU, RAM, storage, and network bandwidth for a log aggregation solution, for example). Some other potential design impacts include:"
msgstr ""
#: ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:590(para)
#: ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:585(para)
msgid "A large majority of the OpenStack components require access to back-end database services to store state and configuration information. Selection of an appropriate back-end database that will satisfy the availability and fault tolerance requirements of the OpenStack services is required. OpenStack services support connecting to any database that is supported by the SQLAlchemy Python drivers, however most common database deployments make use of MySQL or some variation of it. We recommend that the database which provides back-end service within a general purpose cloud be made highly available using an available technology which can accomplish that goal. Some of the more common software solutions used include Galera, MariaDB and MySQL with multi-master replication."
msgstr ""
@ -5707,6 +5711,10 @@ msgstr ""
msgid "Compute (server) hardware selection"
msgstr ""
#: ./doc/arch-design/storage_focus/section_architecture_storage_focus.xml:156(para)
msgid "Compute (server) hardware must be evaluated against four opposing dimensions:"
msgstr ""
#: ./doc/arch-design/storage_focus/section_architecture_storage_focus.xml:186(para)
msgid "The relative of the hardware weighted against the level of design effort needed to build the system."
msgstr ""

372
doc/arch-design/locale/zh_CN.po
View File

File diff suppressed because it is too large Load Diff

166
doc/config-reference/locale/config-reference.pot
View File

@ -1,7 +1,7 @@
msgid ""
msgstr ""
"Project-Id-Version: PACKAGE VERSION\n"
"POT-Creation-Date: 2015-01-29 06:29+0000\n"
"POT-Creation-Date: 2015-01-30 06:28+0000\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
@ -1037,35 +1037,47 @@ msgstr ""
msgid "Use the following options in the configuration file for your driver to change security group settings."
msgstr ""
#: ./doc/config-reference/networking/section_networking-options-reference.xml:164(title)
#: ./doc/config-reference/networking/section_networking-options-reference.xml:162(para)
msgid "Now Networking uses iptables to achieve security group functions. In L2 agent with <placeholder-1/> option enabled, it makes use of IPset to improve security group's performance, as it represents a hash set which is insensitive to the number of elements."
msgstr ""
#: ./doc/config-reference/networking/section_networking-options-reference.xml:166(para)
msgid "When a port is created, L2 agent will add an additional IPset chain to it's iptables chain, if the security group that this port belongs to has rules between other security group, the member of that security group will be added to the ipset chain."
msgstr ""
#: ./doc/config-reference/networking/section_networking-options-reference.xml:170(para)
msgid "If a member of a security group is changed, it used to reload iptables rules which is expensive. However, when IPset option is enabled on L2 agent, it does not need to reload iptables if only members of security group were changed, it should just update an IPset."
msgstr ""
#: ./doc/config-reference/networking/section_networking-options-reference.xml:178(title)
msgid "SSL and Certification Authority"
msgstr ""
#: ./doc/config-reference/networking/section_networking-options-reference.xml:165(para)
#: ./doc/config-reference/networking/section_networking-options-reference.xml:179(para)
msgid "Use the following options in the <filename>neutron.conf</filename> file to enable SSL."
msgstr ""
#: ./doc/config-reference/networking/section_networking-options-reference.xml:171(title)
#: ./doc/config-reference/networking/section_networking-options-reference.xml:185(title)
msgid "Testing"
msgstr ""
#: ./doc/config-reference/networking/section_networking-options-reference.xml:172(para)
#: ./doc/config-reference/networking/section_networking-options-reference.xml:186(para)
msgid "Use the following options to alter testing-related features."
msgstr ""
#: ./doc/config-reference/networking/section_networking-options-reference.xml:177(title)
#: ./doc/config-reference/networking/section_networking-options-reference.xml:191(title)
msgid "vArmour Firewall-as-a-Service driver"
msgstr ""
#: ./doc/config-reference/networking/section_networking-options-reference.xml:178(para)
#: ./doc/config-reference/networking/section_networking-options-reference.xml:192(para)
msgid "Use the following options in the <filename>l3_agent.ini</filename> file for the vArmour FWaaS driver."
msgstr ""
#: ./doc/config-reference/networking/section_networking-options-reference.xml:184(title)
#: ./doc/config-reference/networking/section_networking-options-reference.xml:198(title)
msgid "VPN"
msgstr ""
#: ./doc/config-reference/networking/section_networking-options-reference.xml:185(para)
#: ./doc/config-reference/networking/section_networking-options-reference.xml:199(para)
msgid "Use the following options in the <filename>vpn_agent.ini</filename> file for the VPN agent."
msgstr ""
@ -3138,7 +3150,7 @@ msgstr ""
msgid "This driver does not access the NFS share directly. It accesses the share only through XenAPI Storage Manager. Consider this driver as a reference implementation for use of the XenAPI Storage Manager in OpenStack (present in XenServer and XCP)."
msgstr ""
#: ./doc/config-reference/block-storage/drivers/xenapi-nfs.xml:14(title) ./doc/config-reference/block-storage/drivers/coraid-driver.xml:85(title) ./doc/config-reference/compute/section_hypervisor_hyper-v.xml:193(title)
#: ./doc/config-reference/block-storage/drivers/xenapi-nfs.xml:14(title) ./doc/config-reference/block-storage/drivers/coraid-driver.xml:85(title) ./doc/config-reference/compute/section_hypervisor_hyper-v.xml:192(title)
msgid "Requirements"
msgstr ""
@ -3968,7 +3980,7 @@ msgstr ""
msgid "Git can be used to download the necessary source code. The installer to run Git on Windows can be downloaded here:"
msgstr ""
#: ./doc/config-reference/block-storage/drivers/windows-iscsi-volume-driver.xml:88(link) ./doc/config-reference/compute/section_hypervisor_hyper-v.xml:320(link)
#: ./doc/config-reference/block-storage/drivers/windows-iscsi-volume-driver.xml:88(link) ./doc/config-reference/compute/section_hypervisor_hyper-v.xml:319(link)
msgid "https://github.com/msysgit/msysgit/releases/download/Git-1.9.2-preview20140411/Git-1.9.2-preview20140411.exe"
msgstr ""
@ -3984,7 +3996,7 @@ msgstr ""
msgid "The <filename>cinder.conf</filename> file may be placed in <filename>C:\\etc\\cinder</filename>. Below is a config sample for using the Windows iSCSI Driver:"
msgstr ""
#: ./doc/config-reference/block-storage/drivers/windows-iscsi-volume-driver.xml:108(replaceable) ./doc/config-reference/block-storage/drivers/windows-iscsi-volume-driver.xml:109(replaceable) ./doc/config-reference/block-storage/drivers/windows-iscsi-volume-driver.xml:111(replaceable) ./doc/config-reference/compute/section_hypervisor_hyper-v.xml:161(replaceable) ./doc/config-reference/compute/section_hypervisor_hyper-v.xml:360(replaceable) ./doc/config-reference/compute/section_hypervisor_hyper-v.xml:375(replaceable) ./doc/config-reference/compute/section_hypervisor_hyper-v.xml:384(replaceable) ./doc/config-reference/compute/section_hypervisor_hyper-v.xml:400(replaceable)
#: ./doc/config-reference/block-storage/drivers/windows-iscsi-volume-driver.xml:108(replaceable) ./doc/config-reference/block-storage/drivers/windows-iscsi-volume-driver.xml:109(replaceable) ./doc/config-reference/block-storage/drivers/windows-iscsi-volume-driver.xml:111(replaceable) ./doc/config-reference/compute/section_hypervisor_hyper-v.xml:161(replaceable) ./doc/config-reference/compute/section_hypervisor_hyper-v.xml:359(replaceable) ./doc/config-reference/compute/section_hypervisor_hyper-v.xml:374(replaceable) ./doc/config-reference/compute/section_hypervisor_hyper-v.xml:383(replaceable) ./doc/config-reference/compute/section_hypervisor_hyper-v.xml:399(replaceable)
msgid "IP_ADDRESS"
msgstr ""
@ -8631,7 +8643,7 @@ msgid "You can specify vCenter data stores directly by using the data store name
msgstr ""
#: ./doc/config-reference/image-service/section_image-service-backend-vmware.xml:33(para)
msgid "In the <literal>DEFAULT</literal> section, set the <parameter>default_store</parameter> parameter to <placeholder-1/>, as shown in this code sample:"
msgid "In the <literal>glance_store</literal> section, set the <parameter>default_store</parameter> parameter to <placeholder-1/>, as shown in this code sample:"
msgstr ""
#: ./doc/config-reference/image-service/section_image-service-backend-vmware.xml:43(para)
@ -9359,258 +9371,258 @@ msgid "To enable 'shared nothing live' migration, run the 3 PowerShell instructi
msgstr ""
#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml:164(para)
msgid "Please replace the <replaceable>IP_ADDRESS</replaceable> with the address of the interface which will provide the virtual switching for nova-network."
msgid "Please replace the <replaceable>IP_ADDRESS</replaceable> with the address of the interface which will provide live migration."
msgstr ""
#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml:167(emphasis)
#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml:166(emphasis)
msgid "Additional Reading"
msgstr ""
#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml:168(para)
#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml:167(para)
msgid "Here's an article that clarifies the various live migration options in Hyper-V:"
msgstr ""
#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml:172(link)
#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml:171(link)
msgid "http://ariessysadmin.blogspot.ro/2012/04/hyper-v-live-migration-of-windows.html"
msgstr ""
#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml:177(title)
#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml:176(title)
msgid "Install nova-compute using OpenStack Hyper-V installer"
msgstr ""
#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml:179(para)
#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml:178(para)
msgid "In case you want to avoid all the manual setup, you can use Cloudbase Solutions' installer. You can find it here:"
msgstr ""
#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml:183(link)
#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml:182(link)
msgid "https://www.cloudbase.it/downloads/HyperVNovaCompute_Beta.msi"
msgstr ""
#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml:185(para)
#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml:184(para)
msgid "It installs an independent Python environment, in order to avoid conflicts with existing applications, generates dynamically a <filename>nova.conf</filename> file based on the parameters provided by you."
msgstr ""
#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml:187(para)
#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml:186(para)
msgid "The installer can also be used for an automated and unattended mode for deployments on a massive number of servers. More details about how to use the installer and its features can be found here:"
msgstr ""
#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml:190(link)
#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml:189(link)
msgid "https://www.cloudbase.it"
msgstr ""
#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml:195(title)
#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml:194(title)
msgid "Python"
msgstr ""
#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml:196(para)
#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml:195(para)
msgid "Python 2.7 32bit must be installed as most of the libraries are not working properly on the 64bit version."
msgstr ""
#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml:199(title)
#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml:198(title)
msgid "Setting up Python prerequisites"
msgstr ""
#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml:201(para)
#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml:200(para)
msgid "Download and then install it using the MSI installer from here:"
msgstr ""
#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml:204(link)
#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml:203(link)
msgid "http://www.python.org/ftp/python/2.7.3/python-2.7.3.msi"
msgstr ""
#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml:213(para)
#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml:212(para)
msgid "Make sure that the <filename>Python</filename> and <filename>Python\\Scripts</filename> paths are set up in the <envar>PATH</envar> environment variable."
msgstr ""
#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml:223(title)
#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml:222(title)
msgid "Python dependencies"
msgstr ""
#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml:224(para)
#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml:223(para)
msgid "The following packages need to be downloaded and manually installed:"
msgstr ""
#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml:228(package)
#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml:227(package)
msgid "setuptools"
msgstr ""
#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml:231(link)
#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml:230(link)
msgid "http://pypi.python.org/packages/2.7/s/setuptools/setuptools-0.6c11.win32-py2.7.exel"
msgstr ""
#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml:236(package)
#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml:235(package)
msgid "pip"
msgstr ""
#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml:239(link)
#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml:238(link)
msgid "http://pip.readthedocs.org/en/latest/installing.html"
msgstr ""
#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml:244(package)
#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml:243(package)
msgid "MySQL-python"
msgstr ""
#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml:246(link)
#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml:245(link)
msgid "http://codegood.com/download/10/"
msgstr ""
#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml:251(package)
#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml:250(package)
msgid "PyWin32"
msgstr ""
#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml:254(link)
#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml:253(link)
msgid "http://sourceforge.net/projects/pywin32/files/pywin32/Build%20217/pywin32-217.win32-py2.7.exe"
msgstr ""
#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml:259(package)
#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml:258(package)
msgid "Greenlet"
msgstr ""
#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml:262(link)
#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml:261(link)
msgid "http://www.lfd.uci.edu/~gohlke/pythonlibs/#greenlet"
msgstr ""
#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml:267(package)
#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml:266(package)
msgid "PyCryto"
msgstr ""
#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml:270(link)
#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml:269(link)
msgid "http://www.voidspace.org.uk/downloads/pycrypto26/pycrypto-2.6.win32-py2.7.exe"
msgstr ""
#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml:275(para)
#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml:274(para)
msgid "The following packages must be installed with pip:"
msgstr ""
#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml:278(package)
#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml:277(package)
msgid "ecdsa"
msgstr ""
#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml:281(package)
#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml:280(package)
msgid "amqp"
msgstr ""
#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml:284(package)
#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml:283(package)
msgid "wmi"
msgstr ""
#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml:292(title)
#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml:291(title)
msgid "Other dependencies"
msgstr ""
#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml:293(para)
#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml:292(para)
msgid "<literal>qemu-img</literal> is required for some of the image related operations. You can get it from here: <link href=\"http://qemu.weilnetz.de/\">http://qemu.weilnetz.de/</link>. You must make sure that the <literal>qemu-img</literal> path is set in the PATH environment variable."
msgstr ""
#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml:298(para)
#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml:297(para)
msgid "Some Python packages need to be compiled, so you may use MinGW or Visual Studio. You can get MinGW from here: <link href=\"http://sourceforge.net/projects/mingw/\"> http://sourceforge.net/projects/mingw/</link>. You must configure which compiler to be used for this purpose by using the <filename>distutils.cfg</filename> file in <filename>$Python27\\Lib\\distutils</filename>, which can contain:"
msgstr ""
#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml:307(para)
#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml:306(para)
msgid "As a last step for setting up MinGW, make sure that the MinGW binaries' directories are set up in PATH."
msgstr ""
#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml:312(title)
#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml:311(title)
msgid "Install Nova-compute"
msgstr ""
#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml:314(title)
#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml:313(title)
msgid "Download the nova code"
msgstr ""
#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml:317(para)
#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml:316(para)
msgid "Use Git to download the necessary source code. The installer to run Git on Windows can be downloaded here:"
msgstr ""
#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml:324(para)
#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml:323(para)
msgid "Download the installer. Once the download is complete, run the installer and follow the prompts in the installation wizard. The default should be acceptable for the needs of the document."
msgstr ""
#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml:333(para)
#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml:332(para)
msgid "Run the following to clone the Nova code."
msgstr ""
#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml:339(title)
#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml:338(title)
msgid "Install nova-compute service"
msgstr ""
#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml:340(para)
#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml:339(para)
msgid "To install <systemitem class=\"service\">Nova-compute</systemitem>, run:"
msgstr ""
#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml:348(title)
#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml:347(title)
msgid "Configure nova-compute"
msgstr ""
#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml:349(para)
#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml:348(para)
msgid "The <filename>nova.conf</filename> file must be placed in <filename>C:\\etc\\nova</filename> for running OpenStack on Hyper-V. Below is a sample <filename>nova.conf</filename> for Windows:"
msgstr ""
#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml:389(replaceable)
#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml:388(replaceable)
msgid "IP_ADDRESS:35357"
msgstr ""
#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml:401(para)
#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml:400(para)
msgid "<xref linkend=\"config_table_nova_hyperv\"/> contains a reference of all options for hyper-v."
msgstr ""
#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml:405(title)
#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml:404(title)
msgid "Prepare images for use with Hyper-V"
msgstr ""
#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml:406(para)
#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml:405(para)
msgid "Hyper-V currently supports only the VHD and VHDX file format for virtual machine instances. Detailed instructions for installing virtual machines on Hyper-V can be found here:"
msgstr ""
#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml:410(link)
#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml:409(link)
msgid "http://technet.microsoft.com/en-us/library/cc772480.aspx"
msgstr ""
#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml:411(para)
#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml:410(para)
msgid "Once you have successfully created a virtual machine, you can then upload the image to glance using the native glance-client:"
msgstr ""
#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml:413(replaceable)
#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml:412(replaceable)
msgid "VM_IMAGE_NAME"
msgstr ""
#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml:415(para)
#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml:414(para)
msgid "VHD and VHDX files sizes can be bigger than their maximum internal size, as such you need to boot instances using a flavor with a slightly bigger disk size than the internal size of the disk file. To create VHDs, use the following PowerShell cmdlet:"
msgstr ""
#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml:417(replaceable)
#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml:416(replaceable)
msgid "DISK_NAME.vhd"
msgstr ""
#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml:417(replaceable)
#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml:416(replaceable)
msgid "VHD_SIZE"
msgstr ""
#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml:421(title)
#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml:420(title)
msgid "Run Compute with Hyper-V"
msgstr ""
#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml:422(para)
#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml:421(para)
msgid "To start the <systemitem class=\"service\">nova-compute</systemitem> service, run this command from a console in the Windows server:"
msgstr ""
#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml:428(title)
#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml:427(title)
msgid "Troubleshoot Hyper-V configuration"
msgstr ""
#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml:432(para)
#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml:431(para)
msgid "I ran the <placeholder-1/> command from my controller; however, I'm not seeing smiley faces for Hyper-V compute nodes, what do I do?"
msgstr ""
#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml:436(emphasis)
#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml:435(emphasis)
msgid "Verify that you are synchronized with a network time source. For instructions about how to configure NTP on your Hyper-V compute node, see <xref linkend=\"configure-ntp-windows\"/>."
msgstr ""
#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml:443(para)
#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml:442(para)
msgid "How do I restart the compute service?"
msgstr ""
#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml:450(para)
#: ./doc/config-reference/compute/section_hypervisor_hyper-v.xml:449(para)
msgid "How do I restart the iSCSI initiator service?"
msgstr ""

3557
doc/glossary/locale/de.po
View File

File diff suppressed because it is too large Load Diff

3557
doc/glossary/locale/fr.po
View File

File diff suppressed because it is too large Load Diff

2430
doc/glossary/locale/glossary.pot
View File

File diff suppressed because it is too large Load Diff

3523
doc/glossary/locale/ja.po
View File

File diff suppressed because it is too large Load Diff

3567
doc/glossary/locale/ko_KR.po
View File

File diff suppressed because it is too large Load Diff

3567
doc/glossary/locale/zh_CN.po
View File

File diff suppressed because it is too large Load Diff

194
doc/user-guide/locale/fr.po
View File

@ -11,8 +11,8 @@
msgid ""
msgstr ""
"Project-Id-Version: OpenStack Manuals\n"
"POT-Creation-Date: 2015-01-23 18:23+0000\n"
"PO-Revision-Date: 2015-01-23 07:11+0000\n"
"POT-Creation-Date: 2015-01-30 04:51+0000\n"
"PO-Revision-Date: 2015-01-30 04:52+0000\n"
"Last-Translator: openstackjenkins <jenkins@openstack.org>\n"
"Language-Team: French (http://www.transifex.com/projects/p/openstack-manuals-i18n/language/fr/)\n"
"MIME-Version: 1.0\n"
@ -358,6 +358,156 @@ msgid ""
"instance is not possible."
msgstr ""
#: ./doc/user-guide/section_object-api-create-website.xml6(title)
msgid "Create static website"
msgstr ""
#: ./doc/user-guide/section_object-api-create-website.xml7(para)
msgid ""
"You can use your Object Storage account to create a static website. This "
"static website is created with staticweb middleware and serves container "
"data with a specified index file, error file resolution, and optional file "
"listings. This mode is normally active only for anonymous requests, which "
"provide no authentication token. To use it with authenticated requests, set "
"the header <literal>X-Web-Mode</literal> to <literal>TRUE</literal> on the "
"request."
msgstr ""
#: ./doc/user-guide/section_object-api-create-website.xml15(para)
msgid ""
"The staticweb filter must be added to the pipeline in your "
"<filename>/etc/swift/proxy-server.conf</filename> file below any "
"authentication middleware. You must also add a staticweb middleware "
"configuration section."
msgstr ""
#: ./doc/user-guide/section_object-api-create-website.xml19(para)
msgid ""
"For an example of the staticweb configuration syntax see the <link "
"href=\"http://docs.openstack.org/juno/config-reference/content/object-"
"storage-static-web.html\">Cloud Administrator Guide</link>."
msgstr ""
#: ./doc/user-guide/section_object-api-create-website.xml23(para)
msgid ""
"For a complete example of the <filename>/etc/swift/proxy-"
"server.conf</filename> file (including staticweb), see the <link "
"href=\"http://docs.openstack.org/juno/config-reference/content/proxy-server-"
"conf.html\">Cloud Administrator Guide</link>."
msgstr ""
#: ./doc/user-guide/section_object-api-create-website.xml28(para)
msgid ""
"Your publicly readable containers are checked for two headers, <literal>X"
"-Container-Meta-Web-Index</literal> and <literal>X-Container-Meta-Web-"
"Error</literal>. The <literal>X-Container-Meta-Web-Error</literal> header is"
" discussed below, in <xref linkend=\"Set_Error_Pages_for_Static_Website-"
"dle4005\"/>."
msgstr ""
#: ./doc/user-guide/section_object-api-create-website.xml35(para)
msgid ""
"Use <literal>X-Container-Meta-Web-Index</literal> to determine the index "
"file (or default page served, such as <filename>index.html</filename>) for "
"your website. When someone initially enters your site, the "
"<filename>index.html</filename> file displays automatically. If you create "
"sub-directories for your site by creating pseudo-directories in your "
"container, the index page for each sub-directory is displayed by default. If"
" your pseudo-directory does not have a file with the same name as your index"
" file, visits to the sub-directory return a 404 error."
msgstr ""
#: ./doc/user-guide/section_object-api-create-website.xml46(para)
msgid ""
"You also have the option of displaying a list of files in your pseudo-"
"directory instead of a web page. To do this, set the <literal>X-Container-"
"Meta-Web-Listings</literal> header to <literal>TRUE</literal>. You may add "
"styles to your file listing by setting <literal>X-Container-Meta-Web-"
"Listings-CSS:</literal> to a style sheet (for example, "
"<literal>lists.css</literal>)."
msgstr ""
#: ./doc/user-guide/section_object-api-create-website.xml55(title)
msgid "Static web middleware through Object Storage"
msgstr ""
#: ./doc/user-guide/section_object-api-create-website.xml57(title)
msgid "Make container publicly readable"
msgstr ""
#: ./doc/user-guide/section_object-api-create-website.xml58(para)
msgid ""
"Make the container publicly readable. Once the container is publicly "
"readable, you can access your objects directly, but you must set the index "
"file to browse the main site URL and its sub-directories."
msgstr ""
#: ./doc/user-guide/section_object-api-create-website.xml66(title)
msgid "Set site index file"
msgstr ""
#: ./doc/user-guide/section_object-api-create-website.xml67(para)
msgid ""
"Set the index file. In this case, <filename>index.html</filename> is the "
"default file displayed when the site appears."
msgstr ""
#: ./doc/user-guide/section_object-api-create-website.xml73(title)
msgid "Enable file listing"
msgstr ""
#: ./doc/user-guide/section_object-api-create-website.xml74(para)
msgid ""
"Turn on file listing. If you do not set the index file, the URL displays a "
"list of the objects in the container. Instructions on styling the list with "
"a CSS follow."
msgstr ""
#: ./doc/user-guide/section_object-api-create-website.xml81(title)
msgid "Enable CSS for file listing"
msgstr ""
#: ./doc/user-guide/section_object-api-create-website.xml82(para)
msgid "Style the file listing using a CSS."
msgstr ""
#: ./doc/user-guide/section_object-api-create-website.xml87(title)
msgid "Set error pages for static website"
msgstr ""
#: ./doc/user-guide/section_object-api-create-website.xml88(para)
msgid ""
"You can create and set custom error pages for visitors to your website; "
"currently, only 401 (Unauthorized) and 404 (Not Found) errors are supported."
" To do this, set the metadata header, <literal>X-Container-Meta-Web-"
"Error</literal>."
msgstr ""
#: ./doc/user-guide/section_object-api-create-website.xml93(para)
msgid ""
"Error pages are served with the &lt;status&gt; code pre-pended to the name "
"of the error page you set. For instance, if you set <literal>X-Container-"
"Meta-Web-Error</literal> to <filename>error.html</filename>, 401 errors will"
" display the page <filename>401error.html</filename>. Similarly, 404 errors "
"will display <filename>404error.html</filename>. You must have both of these"
" pages created in your container when you set the <literal>X-Container-Meta-"
"Web-Error</literal> metadata, or your site will display generic error pages."
msgstr ""
#: ./doc/user-guide/section_object-api-create-website.xml105(para)
msgid ""
"You only have to set the <literal>X-Container-Meta-Web-Error</literal> "
"metadata once for your entire static website."
msgstr ""
#: ./doc/user-guide/section_object-api-create-website.xml109(title)
msgid "Set error pages for static website request"
msgstr ""
#: ./doc/user-guide/section_object-api-create-website.xml112(para)
msgid "Any 2<varname>nn</varname> response indicates success."
msgstr ""
#: ./doc/user-guide/section_cli_nova_baremetal.xml7(title)
msgid "Manage bare-metal nodes"
msgstr ""
@ -6222,6 +6372,46 @@ msgid ""
" reboot, or terminate it."
msgstr "Vous pouvez redimensionner ou reconstruire une instance. Vous pouvez aussi choisir d'afficher le journal de la console de l'instance. Suivant l'état courant de l'instance, vous pouvez faire une pause, reprendre, suspendre, faire un redémarrage soft ou hard ou mettre fin à l'instance. "
#: ./doc/user-guide/section_object-api-discoverability.xml7(title)
msgid "Discoverability"
msgstr ""
#: ./doc/user-guide/section_object-api-discoverability.xml8(para)
msgid ""
"Your Object Storage system might not enable all features that this document "
"describes. These features are:"
msgstr ""
#: ./doc/user-guide/section_object-api-discoverability.xml21(para)
msgid ""
"To discover which features are enabled in your Object Storage system, use "
"the <literal>/info</literal> request."
msgstr ""
#: ./doc/user-guide/section_object-api-discoverability.xml23(para)
msgid ""
"To use the <literal>/info</literal> request, send a request using the /info "
"path to the Object Store endpoint as shown in this example:"
msgstr ""
#: ./doc/user-guide/section_object-api-discoverability.xml27(para)
msgid "This example shows a truncated response body:"
msgstr ""
#: ./doc/user-guide/section_object-api-discoverability.xml39(para)
msgid ""
"This output shows that the Object Storage system has enabled the static "
"website and temporary URL features."
msgstr ""
#: ./doc/user-guide/section_object-api-discoverability.xml43(para)
msgid ""
"In some cases, the <literal>/info</literal> request will return an error. "
"This could be because your service provider has disabled the "
"<literal>/info</literal> request function, or because you are using an older"
" version that does not support it."
msgstr ""
#: ./doc/user-guide/section_cli_nova_userdata.xml7(title)
msgid "Provide user data to instances"
msgstr ""

194
doc/user-guide/locale/ja.po
View File

@ -7,8 +7,8 @@
msgid ""
msgstr ""
"Project-Id-Version: OpenStack Manuals\n"
"POT-Creation-Date: 2015-01-23 18:23+0000\n"
"PO-Revision-Date: 2015-01-23 07:11+0000\n"
"POT-Creation-Date: 2015-01-30 04:51+0000\n"
"PO-Revision-Date: 2015-01-30 04:52+0000\n"
"Last-Translator: openstackjenkins <jenkins@openstack.org>\n"
"Language-Team: Japanese (http://www.transifex.com/projects/p/openstack-manuals-i18n/language/ja/)\n"
"MIME-Version: 1.0\n"
@ -354,6 +354,156 @@ msgid ""
"instance is not possible."
msgstr "キーペア、セキュリティグループ、またはルールを指定しない場合、VNC 経由でクラウド内からしかインスタンスにアクセスすることができません。インスタンスの ping さえも不可となっています。"
#: ./doc/user-guide/section_object-api-create-website.xml6(title)
msgid "Create static website"
msgstr ""
#: ./doc/user-guide/section_object-api-create-website.xml7(para)
msgid ""
"You can use your Object Storage account to create a static website. This "
"static website is created with staticweb middleware and serves container "
"data with a specified index file, error file resolution, and optional file "
"listings. This mode is normally active only for anonymous requests, which "
"provide no authentication token. To use it with authenticated requests, set "
"the header <literal>X-Web-Mode</literal> to <literal>TRUE</literal> on the "
"request."
msgstr ""
#: ./doc/user-guide/section_object-api-create-website.xml15(para)
msgid ""
"The staticweb filter must be added to the pipeline in your "
"<filename>/etc/swift/proxy-server.conf</filename> file below any "
"authentication middleware. You must also add a staticweb middleware "
"configuration section."
msgstr ""
#: ./doc/user-guide/section_object-api-create-website.xml19(para)
msgid ""
"For an example of the staticweb configuration syntax see the <link "
"href=\"http://docs.openstack.org/juno/config-reference/content/object-"
"storage-static-web.html\">Cloud Administrator Guide</link>."
msgstr ""
#: ./doc/user-guide/section_object-api-create-website.xml23(para)
msgid ""
"For a complete example of the <filename>/etc/swift/proxy-"
"server.conf</filename> file (including staticweb), see the <link "
"href=\"http://docs.openstack.org/juno/config-reference/content/proxy-server-"
"conf.html\">Cloud Administrator Guide</link>."
msgstr ""
#: ./doc/user-guide/section_object-api-create-website.xml28(para)
msgid ""
"Your publicly readable containers are checked for two headers, <literal>X"
"-Container-Meta-Web-Index</literal> and <literal>X-Container-Meta-Web-"
"Error</literal>. The <literal>X-Container-Meta-Web-Error</literal> header is"
" discussed below, in <xref linkend=\"Set_Error_Pages_for_Static_Website-"
"dle4005\"/>."
msgstr ""
#: ./doc/user-guide/section_object-api-create-website.xml35(para)
msgid ""
"Use <literal>X-Container-Meta-Web-Index</literal> to determine the index "
"file (or default page served, such as <filename>index.html</filename>) for "
"your website. When someone initially enters your site, the "
"<filename>index.html</filename> file displays automatically. If you create "
"sub-directories for your site by creating pseudo-directories in your "
"container, the index page for each sub-directory is displayed by default. If"
" your pseudo-directory does not have a file with the same name as your index"
" file, visits to the sub-directory return a 404 error."
msgstr ""
#: ./doc/user-guide/section_object-api-create-website.xml46(para)
msgid ""
"You also have the option of displaying a list of files in your pseudo-"
"directory instead of a web page. To do this, set the <literal>X-Container-"
"Meta-Web-Listings</literal> header to <literal>TRUE</literal>. You may add "
"styles to your file listing by setting <literal>X-Container-Meta-Web-"
"Listings-CSS:</literal> to a style sheet (for example, "
"<literal>lists.css</literal>)."
msgstr ""
#: ./doc/user-guide/section_object-api-create-website.xml55(title)
msgid "Static web middleware through Object Storage"
msgstr ""
#: ./doc/user-guide/section_object-api-create-website.xml57(title)
msgid "Make container publicly readable"
msgstr ""
#: ./doc/user-guide/section_object-api-create-website.xml58(para)
msgid ""
"Make the container publicly readable. Once the container is publicly "
"readable, you can access your objects directly, but you must set the index "
"file to browse the main site URL and its sub-directories."
msgstr ""
#: ./doc/user-guide/section_object-api-create-website.xml66(title)
msgid "Set site index file"
msgstr ""
#: ./doc/user-guide/section_object-api-create-website.xml67(para)
msgid ""
"Set the index file. In this case, <filename>index.html</filename> is the "
"default file displayed when the site appears."
msgstr ""
#: ./doc/user-guide/section_object-api-create-website.xml73(title)
msgid "Enable file listing"
msgstr ""
#: ./doc/user-guide/section_object-api-create-website.xml74(para)
msgid ""
"Turn on file listing. If you do not set the index file, the URL displays a "
"list of the objects in the container. Instructions on styling the list with "
"a CSS follow."
msgstr ""
#: ./doc/user-guide/section_object-api-create-website.xml81(title)
msgid "Enable CSS for file listing"
msgstr ""
#: ./doc/user-guide/section_object-api-create-website.xml82(para)
msgid "Style the file listing using a CSS."
msgstr ""
#: ./doc/user-guide/section_object-api-create-website.xml87(title)
msgid "Set error pages for static website"
msgstr ""
#: ./doc/user-guide/section_object-api-create-website.xml88(para)
msgid ""
"You can create and set custom error pages for visitors to your website; "
"currently, only 401 (Unauthorized) and 404 (Not Found) errors are supported."
" To do this, set the metadata header, <literal>X-Container-Meta-Web-"
"Error</literal>."
msgstr ""
#: ./doc/user-guide/section_object-api-create-website.xml93(para)
msgid ""
"Error pages are served with the &lt;status&gt; code pre-pended to the name "
"of the error page you set. For instance, if you set <literal>X-Container-"
"Meta-Web-Error</literal> to <filename>error.html</filename>, 401 errors will"
" display the page <filename>401error.html</filename>. Similarly, 404 errors "
"will display <filename>404error.html</filename>. You must have both of these"
" pages created in your container when you set the <literal>X-Container-Meta-"
"Web-Error</literal> metadata, or your site will display generic error pages."
msgstr ""
#: ./doc/user-guide/section_object-api-create-website.xml105(para)
msgid ""
"You only have to set the <literal>X-Container-Meta-Web-Error</literal> "
"metadata once for your entire static website."
msgstr ""
#: ./doc/user-guide/section_object-api-create-website.xml109(title)
msgid "Set error pages for static website request"
msgstr ""
#: ./doc/user-guide/section_object-api-create-website.xml112(para)
msgid "Any 2<varname>nn</varname> response indicates success."
msgstr ""
#: ./doc/user-guide/section_cli_nova_baremetal.xml7(title)
msgid "Manage bare-metal nodes"
msgstr "ベアメタルノードの管理"
@ -6218,6 +6368,46 @@ msgid ""
" reboot, or terminate it."
msgstr "インスタンスのリサイズや再構築をできます。インスタンスのコンソールログを表示するため、インスタンスやセキュリティグループを編集するためにも選択できます。インスタンスの現在の状態によって、インスタンスを一時停止、再開、サスペンド、ソフトリブート、ハードリブート、終了できます。"
#: ./doc/user-guide/section_object-api-discoverability.xml7(title)
msgid "Discoverability"
msgstr ""
#: ./doc/user-guide/section_object-api-discoverability.xml8(para)
msgid ""
"Your Object Storage system might not enable all features that this document "
"describes. These features are:"
msgstr ""
#: ./doc/user-guide/section_object-api-discoverability.xml21(para)
msgid ""
"To discover which features are enabled in your Object Storage system, use "
"the <literal>/info</literal> request."
msgstr ""
#: ./doc/user-guide/section_object-api-discoverability.xml23(para)
msgid ""
"To use the <literal>/info</literal> request, send a request using the /info "
"path to the Object Store endpoint as shown in this example:"
msgstr ""
#: ./doc/user-guide/section_object-api-discoverability.xml27(para)
msgid "This example shows a truncated response body:"
msgstr ""
#: ./doc/user-guide/section_object-api-discoverability.xml39(para)
msgid ""
"This output shows that the Object Storage system has enabled the static "
"website and temporary URL features."
msgstr ""
#: ./doc/user-guide/section_object-api-discoverability.xml43(para)
msgid ""
"In some cases, the <literal>/info</literal> request will return an error. "
"This could be because your service provider has disabled the "
"<literal>/info</literal> request function, or because you are using an older"
" version that does not support it."
msgstr ""
#: ./doc/user-guide/section_cli_nova_userdata.xml7(title)
msgid "Provide user data to instances"
msgstr "インスタンスへのユーザーデータの提供"

122
doc/user-guide/locale/user-guide.pot
View File

@ -1,7 +1,7 @@
msgid ""
msgstr ""
"Project-Id-Version: PACKAGE VERSION\n"
"POT-Creation-Date: 2015-01-24 06:11+0000\n"
"POT-Creation-Date: 2015-01-30 06:28+0000\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
@ -237,6 +237,98 @@ msgstr ""
msgid "If you did not provide a key pair, security groups, or rules, you can access the instance only from inside the cloud through VNC. Even pinging the instance is not possible."
msgstr ""
#: ./doc/user-guide/section_object-api-create-website.xml:6(title)
msgid "Create static website"
msgstr ""
#: ./doc/user-guide/section_object-api-create-website.xml:7(para)
msgid "You can use your Object Storage account to create a static website. This static website is created with staticweb middleware and serves container data with a specified index file, error file resolution, and optional file listings. This mode is normally active only for anonymous requests, which provide no authentication token. To use it with authenticated requests, set the header <literal>X-Web-Mode</literal> to <literal>TRUE</literal> on the request."
msgstr ""
#: ./doc/user-guide/section_object-api-create-website.xml:15(para)
msgid "The staticweb filter must be added to the pipeline in your <filename>/etc/swift/proxy-server.conf</filename> file below any authentication middleware. You must also add a staticweb middleware configuration section."
msgstr ""
#: ./doc/user-guide/section_object-api-create-website.xml:19(para)
msgid "For an example of the staticweb configuration syntax see the <link href=\"http://docs.openstack.org/juno/config-reference/content/object-storage-static-web.html\">Cloud Administrator Guide</link>."
msgstr ""
#: ./doc/user-guide/section_object-api-create-website.xml:23(para)
msgid "For a complete example of the <filename>/etc/swift/proxy-server.conf</filename> file (including staticweb), see the <link href=\"http://docs.openstack.org/juno/config-reference/content/proxy-server-conf.html\">Cloud Administrator Guide</link>."
msgstr ""
#: ./doc/user-guide/section_object-api-create-website.xml:28(para)
msgid "Your publicly readable containers are checked for two headers, <literal>X-Container-Meta-Web-Index</literal> and <literal>X-Container-Meta-Web-Error</literal>. The <literal>X-Container-Meta-Web-Error</literal> header is discussed below, in <xref linkend=\"Set_Error_Pages_for_Static_Website-dle4005\"/>."
msgstr ""
#: ./doc/user-guide/section_object-api-create-website.xml:35(para)
msgid "Use <literal>X-Container-Meta-Web-Index</literal> to determine the index file (or default page served, such as <filename>index.html</filename>) for your website. When someone initially enters your site, the <filename>index.html</filename> file displays automatically. If you create sub-directories for your site by creating pseudo-directories in your container, the index page for each sub-directory is displayed by default. If your pseudo-directory does not have a file with the same name as your index file, visits to the sub-directory return a 404 error."
msgstr ""
#: ./doc/user-guide/section_object-api-create-website.xml:46(para)
msgid "You also have the option of displaying a list of files in your pseudo-directory instead of a web page. To do this, set the <literal>X-Container-Meta-Web-Listings</literal> header to <literal>TRUE</literal>. You may add styles to your file listing by setting <literal>X-Container-Meta-Web-Listings-CSS:</literal> to a style sheet (for example, <literal>lists.css</literal>)."
msgstr ""
#: ./doc/user-guide/section_object-api-create-website.xml:55(title)
msgid "Static web middleware through Object Storage"
msgstr ""
#: ./doc/user-guide/section_object-api-create-website.xml:57(title)
msgid "Make container publicly readable"
msgstr ""
#: ./doc/user-guide/section_object-api-create-website.xml:58(para)
msgid "Make the container publicly readable. Once the container is publicly readable, you can access your objects directly, but you must set the index file to browse the main site URL and its sub-directories."
msgstr ""
#: ./doc/user-guide/section_object-api-create-website.xml:66(title)
msgid "Set site index file"
msgstr ""
#: ./doc/user-guide/section_object-api-create-website.xml:67(para)
msgid "Set the index file. In this case, <filename>index.html</filename> is the default file displayed when the site appears."
msgstr ""
#: ./doc/user-guide/section_object-api-create-website.xml:73(title)
msgid "Enable file listing"
msgstr ""
#: ./doc/user-guide/section_object-api-create-website.xml:74(para)
msgid "Turn on file listing. If you do not set the index file, the URL displays a list of the objects in the container. Instructions on styling the list with a CSS follow."
msgstr ""
#: ./doc/user-guide/section_object-api-create-website.xml:81(title)
msgid "Enable CSS for file listing"
msgstr ""
#: ./doc/user-guide/section_object-api-create-website.xml:82(para)
msgid "Style the file listing using a CSS."
msgstr ""
#: ./doc/user-guide/section_object-api-create-website.xml:87(title)
msgid "Set error pages for static website"
msgstr ""
#: ./doc/user-guide/section_object-api-create-website.xml:88(para)
msgid "You can create and set custom error pages for visitors to your website; currently, only 401 (Unauthorized) and 404 (Not Found) errors are supported. To do this, set the metadata header, <literal>X-Container-Meta-Web-Error</literal>."
msgstr ""
#: ./doc/user-guide/section_object-api-create-website.xml:93(para)
msgid "Error pages are served with the &lt;status&gt; code pre-pended to the name of the error page you set. For instance, if you set <literal>X-Container-Meta-Web-Error</literal> to <filename>error.html</filename>, 401 errors will display the page <filename>401error.html</filename>. Similarly, 404 errors will display <filename>404error.html</filename>. You must have both of these pages created in your container when you set the <literal>X-Container-Meta-Web-Error</literal> metadata, or your site will display generic error pages."
msgstr ""
#: ./doc/user-guide/section_object-api-create-website.xml:105(para)
msgid "You only have to set the <literal>X-Container-Meta-Web-Error</literal> metadata once for your entire static website."
msgstr ""
#: ./doc/user-guide/section_object-api-create-website.xml:109(title)
msgid "Set error pages for static website request"
msgstr ""
#: ./doc/user-guide/section_object-api-create-website.xml:112(para)
msgid "Any 2<varname>nn</varname> response indicates success."
msgstr ""
#: ./doc/user-guide/section_cli_nova_baremetal.xml:7(title)
msgid "Manage bare-metal nodes"
msgstr ""
@ -4545,6 +4637,34 @@ msgstr ""
msgid "You can resize or rebuild an instance. You can also choose to view the instance console log, edit instance or the security groups. Depending on the current state of the instance, you can pause, resume, suspend, soft or hard reboot, or terminate it."
msgstr ""
#: ./doc/user-guide/section_object-api-discoverability.xml:7(title)
msgid "Discoverability"
msgstr ""
#: ./doc/user-guide/section_object-api-discoverability.xml:8(para)
msgid "Your Object Storage system might not enable all features that this document describes. These features are:"
msgstr ""
#: ./doc/user-guide/section_object-api-discoverability.xml:21(para)
msgid "To discover which features are enabled in your Object Storage system, use the <literal>/info</literal> request."
msgstr ""
#: ./doc/user-guide/section_object-api-discoverability.xml:23(para)
msgid "To use the <literal>/info</literal> request, send a request using the /info path to the Object Store endpoint as shown in this example:"
msgstr ""
#: ./doc/user-guide/section_object-api-discoverability.xml:27(para)
msgid "This example shows a truncated response body:"
msgstr ""
#: ./doc/user-guide/section_object-api-discoverability.xml:39(para)
msgid "This output shows that the Object Storage system has enabled the static website and temporary URL features."
msgstr ""
#: ./doc/user-guide/section_object-api-discoverability.xml:43(para)
msgid "In some cases, the <literal>/info</literal> request will return an error. This could be because your service provider has disabled the <literal>/info</literal> request function, or because you are using an older version that does not support it."
msgstr ""
#: ./doc/user-guide/section_cli_nova_userdata.xml:7(title)
msgid "Provide user data to instances"
msgstr ""